| 1 |
On Sunday 01 Sep 2013 19:25:45 Alan McKinnon wrote: |
| 2 |
> That overlay hasn't been manifested properly, the checksums and file |
| 3 |
> sizes don't match. You have two options: |
| 4 |
> |
| 5 |
> redigest every ebuild in the entire overlay |
| 6 |
|
| 7 |
I wasn't going to do this, given that one machine is happy. |
| 8 |
|
| 9 |
|
| 10 |
> resync and hope it's fixed (maybe report a bug) |
| 11 |
|
| 12 |
Right, I tried that already, but I can wait a bit longer and resync again. |
| 13 |
With regards to filing a bug, I spoke to Thomas Sachau and he can't reproduce |
| 14 |
the problem on his side. Hence I ended up blaming something being wrong with |
| 15 |
my machine ... |
| 16 |
|
| 17 |
|
| 18 |
> Just to confirm, this is vapier's overlay you are using? Not niifaq? |
| 19 |
|
| 20 |
Yes, this is vapier's overlay. |
| 21 |
|
| 22 |
|
| 23 |
> I recall manifest problems with niifaq overlay a while ago, but can't |
| 24 |
> recall issues with vapier's. It isn't the portage tree though, so I |
| 25 |
> imagine it can be easy to forget the manifest step when committing files. |
| 26 |
> |
| 27 |
> What I can't explain is why one pc is happy using the overlay files and |
| 28 |
> the other not. AFAIK portage doesn't allow digest checks to be disabled. |
| 29 |
|
| 30 |
Right, I can't explain this either. It's not as if each machine is using a |
| 31 |
somehow unique digest mechanism. I really don't understand how this can be |
| 32 |
happening, especially when I removed the whole /var/lib/layman/enlightenment/* |
| 33 |
tree on the dodgy PC and resync'ed. |
| 34 |
|
| 35 |
-- |
| 36 |
Regards, |
| 37 |
Mick |
Archives