| 1 |
On 12/11/2015 18:42, Grant Edwards wrote: |
| 2 |
> On 2015-11-12, <wabenbau@×××××.com> <wabenbau@×××××.com> wrote: |
| 3 |
>> Grant Edwards <grant.b.edwards@×××××.com> wrote: |
| 4 |
>> |
| 5 |
>>> After an emerge --sync that appeared to work with no problems, my |
| 6 |
>>> "emerge -auvND world" command is reporting that the Changelong files |
| 7 |
>>> are broken for about 2/3 of the packages it wants to update: |
| 8 |
>>> |
| 9 |
>>> !!! Digest verification failed: |
| 10 |
>>> !!! /usr/portage/dev-libs/libxml2/ChangeLog |
| 11 |
>>> !!! Reason: Filesize does not match recorded size |
| 12 |
>>> !!! Got: 5221 |
| 13 |
>>> !!! Expected: 5038 |
| 14 |
>>> |
| 15 |
>>> !!! Digest verification failed: |
| 16 |
>>> !!! /usr/portage/app-text/iso-codes/ChangeLog |
| 17 |
>>> !!! Reason: Filesize does not match recorded size |
| 18 |
>>> !!! Got: 4195 |
| 19 |
>>> !!! Expected: 4014 |
| 20 |
>>> |
| 21 |
>>> [ ... and so on for another dozen or so packages ... ] |
| 22 |
>>> |
| 23 |
>>> I removed the emerge timestamp, sync'ed again, and got the same |
| 24 |
>>> result. Based on past experiences, I'm guessing that if I wait a day |
| 25 |
>>> or two and sync again the problems will go away. |
| 26 |
>>> |
| 27 |
>>> But I am curious what causes these temporary breakages. Does anybody |
| 28 |
>>> know how this happens? |
| 29 |
>> |
| 30 |
>> Try it again. I just synced and received new Manifest and Changelog |
| 31 |
>> files for every(?) package of the portage tree. But no report of bad |
| 32 |
>> digest. |
| 33 |
> |
| 34 |
> Just for fun, I removed the files from the portage tree that were |
| 35 |
> reported as bad, and did another sync. Apparently, the rsync host |
| 36 |
> that got chosen that time had just been updated, because it downloaded |
| 37 |
> 313 files (I didn't pay much attention to which files exactly), and |
| 38 |
> now emerge is happy again. |
| 39 |
> |
| 40 |
> I assume that the portage trees on the rsync servers from my first two |
| 41 |
> attempts were in some intermediate state with new manifist files and |
| 42 |
> old ChangeLog files or vice versa. |
| 43 |
> |
| 44 |
> In the past I've wondered how portage tree updates and rsync servers |
| 45 |
> are managed so that people don't run into problems like this more |
| 46 |
> often. |
| 47 |
> |
| 48 |
|
| 49 |
The dev are doing some $MAGIC to reinstate ChangeLogs and the first run |
| 50 |
is expected to take a while (i.e. several hours). I suppose you can |
| 51 |
expect some breakage till it finishes. |
| 52 |
|
| 53 |
It's being discussed and tracked on gentoo-dev, you can drop a mail |
| 54 |
there with specifics to let the devs know what's happening. |
| 55 |
|
| 56 |
-- |
| 57 |
Alan McKinnon |
| 58 |
alan.mckinnon@×××××.com |
Archives