Summary: | sys-auth/elogind: ninja: error: manifest 'build.ninja' still dirty after 100 tries | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | xuanloct4 <xuanloct4> |
Component: | Current packages | Assignee: | Chromium Project <chromium> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | asturm, kensington, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | ARM64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build log of the sys-auth/elogind package |
Description
xuanloct4
2020-06-26 04:03:59 UTC
Please check your system clock. This problem is almost always because of an incorrect clock, as many arm(64)/embedded devices do not have a hardware clock. I have tried syncing system clock with ntpdate pool.ntp.org and emerge sys-auth/elogind again. But the error still remains. (In reply to Sam James (sec padawan) from comment #1) > Please check your system clock. This problem is almost always because of an > incorrect clock, as many arm(64)/embedded devices do not have a hardware > clock. I have tried syncing system clock with ntpdate pool.ntp.org and emerge sys-auth/elogind again. But the error still remains. (In reply to xuanloct4 from comment #3) > (In reply to Sam James (sec padawan) from comment #1) > > Please check your system clock. This problem is almost always because of an > > incorrect clock, as many arm(64)/embedded devices do not have a hardware > > clock. > > I have tried syncing system clock with ntpdate pool.ntp.org > and emerge sys-auth/elogind again. > But the error still remains. Please compare the 'date' command value with your current time. I already did that and I confirm the system clock is correct. (In reply to Sam James (sec padawan) from comment #4) > (In reply to xuanloct4 from comment #3) > > (In reply to Sam James (sec padawan) from comment #1) > > > Please check your system clock. This problem is almost always because of an > > > incorrect clock, as many arm(64)/embedded devices do not have a hardware > > > clock. > > > > I have tried syncing system clock with ntpdate pool.ntp.org > > and emerge sys-auth/elogind again. > > But the error still remains. > > Please compare the 'date' command value with your current time. I already did that and I confirm the system clock is correct. *** Bug 731056 has been marked as a duplicate of this bug. *** *** Bug 731056 has been marked as a duplicate of this bug. *** Is there any ninja maintainer who can help this user? Are you building on remote filesystem like nfs? If yes, then check that the remote filesystem time is synchronized to build machine time. Also why is this marked FIXED, if it is still an issue? (In reply to stha09 from comment #10) > Are you building on remote filesystem like nfs? If yes, then check that the > remote filesystem time is synchronized to build machine time. > > Also why is this marked FIXED, if it is still an issue? No, I am building the system on QEMU and the clock is correct because I used ntp to synchronize the system time. (In reply to xuanloct4 from comment #11) > (In reply to stha09 from comment #10) > > Are you building on remote filesystem like nfs? If yes, then check that the > > remote filesystem time is synchronized to build machine time. > > > > Also why is this marked FIXED, if it is still an issue? > > No, I am building the system on QEMU and the clock is correct because I used > ntp to synchronize the system time. This bug was resolved by running emerge --sync and re-emerge. But the issue is the same for the bug https://bugs.gentoo.org/731056 but was not resolved! Thanks Please try upgrading to the latest ninja release. That is 1.10.0 as of this writing. Closing since you can no longer reproduce this. *** Bug 731056 has been marked as a duplicate of this bug. *** *** Bug 737818 has been marked as a duplicate of this bug. *** |