| 1 |
I think I finally cracked it. I basically rewrote hashgen because it |
| 2 |
was needlessly complex and interwoven for some reason. I just did an |
| 3 |
emerge --sync (against rsync1) and ran hashverify after it (emerge |
| 4 |
hashgen). It fails because of found excess file: srf-ip-conn-srv.pid |
| 5 |
but that's the only complaint it has. |
| 6 |
|
| 7 |
I hope the same happens for you when you try. |
| 8 |
|
| 9 |
Fabian |
| 10 |
|
| 11 |
|
| 12 |
On 01-03-2018 20:02:00 +0100, Michael Weiser wrote: |
| 13 |
> Hi Fabian, |
| 14 |
> |
| 15 |
> On Thu, Mar 01, 2018 at 02:12:16PM +0100, Fabian Groffen wrote: |
| 16 |
> |
| 17 |
> > > I synced at 11:56 from rsync2. |
| 18 |
> > By the way. Syncing at 11:56 means you need to finish within 25 seconds |
| 19 |
> |
| 20 |
> <facepalm> Good that I put the time in there. I totally failed to |
| 21 |
> connect the sync time to the regen time. But: It was only this one time. |
| 22 |
> The other tries before I was careful to stay away from 26,56 of the |
| 23 |
> hour. |
| 24 |
> |
| 25 |
> I just tried again at 19:15 and 19:21 and hashverify is now back to |
| 26 |
> reporting hash mismatches on basically every single Manifest. |
| 27 |
> |
| 28 |
> I've also verified that my compiler output isn't totally broken by |
| 29 |
> hashgen-ing my local tree and hashverify-ing as well as gemato-verifying |
| 30 |
> it. gemato croaks on srf-ip-conn-srv.pid being there. After deleting and |
| 31 |
> re-hashgen-ing it, gemato verifies the tree fine. Then I gemato-create-d |
| 32 |
> it and hashverify-d successfully. |
| 33 |
> |
| 34 |
> So it all seems consistent and valid locally but to break somehow in |
| 35 |
> transit. |
| 36 |
> |
| 37 |
> BTW: gemato verify takes 90s on my MacBook Air where hasverify takes 7 |
| 38 |
> to 9 seconds. So I'm still sold on the speed. :) |
| 39 |
> -- |
| 40 |
> Thanks, |
| 41 |
> Michael |
| 42 |
> |
| 43 |
|
| 44 |
-- |
| 45 |
Fabian Groffen |
| 46 |
Gentoo on a different level |
Archives