Since February 8th the last 'emerge --sync' are no more shown by 'genlop -r': root@impala:/root(24)# genlop -r | tail rsync'ed at >>> Tue Feb 3 03:54:11 2015 rsync'ed at >>> Wed Feb 4 01:03:39 2015 rsync'ed at >>> Wed Feb 4 12:02:46 2015 rsync'ed at >>> Fri Feb 6 07:56:31 2015 rsync'ed at >>> Fri Feb 6 09:56:41 2015 rsync'ed at >>> Sat Feb 7 08:24:38 2015 rsync'ed at >>> Sun Feb 8 01:03:38 2015 rsync'ed at >>> Sun Feb 8 07:46:35 2015 rsync'ed at >>> Sun Feb 8 21:58:25 2015 I had every day an 'emerge --sync'.
rsync'ed at >>> Wed Feb 4 18:00:11 2015 rsync'ed at >>> Thu Feb 5 06:03:09 2015 rsync'ed at >>> Thu Feb 5 18:00:43 2015 rsync'ed at >>> Fri Feb 6 06:00:27 2015 rsync'ed at >>> Fri Feb 6 18:00:16 2015 rsync'ed at >>> Sat Feb 7 06:01:34 2015 rsync'ed at >>> Sat Feb 7 18:00:16 2015 rsync'ed at >>> Sun Feb 8 06:00:19 2015 rsync'ed at >>> Sun Feb 8 18:00:21 2015 rsync'ed at >>> Mon Feb 9 06:00:18 2015 rsync'ed at >>> Thu Feb 12 06:00:45 2015 rsync'ed at >>> Thu Feb 12 18:00:17 2015 rsync'ed at >>> Fri Feb 13 06:00:37 2015 Mine went on for a few more days but that's because of the revert to sys-apps/portage-2.2.15. There is a gap as well when sys-apps/portage-2.2.16 was installed.
It's because it now no longer says: 1423803608: >>> Starting rsync with rsync://88.198.69.178/gentoo-portage 1423803637: === Sync completed with rsync://88.198.69.178/gentoo-portage but: 1423846803: >>> Syncing repository 'gentoo' into '/world/gentoo/portage'... 1423846803: >>> Starting rsync with rsync://129.143.116.10/gentoo-portage instead.
For clarity, this one was the last one that genlop sees: 1423803608: Started emerge on: Feb 13, 2015 06:00:07 1423803608: *** emerge --nospinner --quiet-build=n --autounmask=n --sync 1423803608: === sync 1423803608: >>> Synchronization of repository 'gentoo' located in '/world/gentoo/portag e'... 1423803608: >>> Starting rsync with rsync://88.198.69.178/gentoo-portage 1423803637: === Sync completed with rsync://88.198.69.178/gentoo-portage 1423803642: *** terminating. and this is the first one genlop doesn't see: 1423846803: Started emerge on: Feb 13, 2015 18:00:03 1423846803: *** emerge --nospinner --quiet-build=n --autounmask=n --sync 1423846803: === sync 1423846803: >>> Syncing repository 'gentoo' into '/world/gentoo/portage'... 1423846803: >>> Starting rsync with rsync://129.143.116.10/gentoo-portage 1423846819: === Sync completed for gentoo 1423846822: *** terminating.
similar problem with qlop as well fyi
Yes, the log file entry format was apparently changed.
qlop issue is bug #531332 .. as these are linked issues
(In reply to Derk W te Bokkel from comment #6) > qlop issue is bug #531332 .. as these are linked issues No, that bug isn't about the changed emerge.log entry format.
actually bug # 540400 is the one that directly relates to the sync emerge.log change .. but the other is also related to the new portage .. as the elog changes percolate through all the sync methods .. and effect virtually all the elog analysis tools
Created attachment 396762 [details, diff] genlop-540050.patch Please test this patch. The fix is simple, but want to make sure it isn't too simple.
does not seem to work for me .. customized ebuild to make it work after failing to see a result with /etc/portage/patches usage .. still no go ..
(In reply to Derk W te Bokkel from comment #8) > actually bug # 540400 is the one that directly relates to the sync > emerge.log change > > .. but the other is also related to the new portage .. as the elog changes > percolate through all the sync methods .. and effect virtually all the elog > analysis tools noticed an error here .. should be just log or emerge.log NOT elog :(
(In reply to Derk W te Bokkel from comment #10) > does not seem to work for me .. customized ebuild to make it work after > failing to see a result with /etc/portage/patches usage .. still no go .. Either the patching did not work or for some reason the wording in your emerge.log is different. The easiest way to test the patch is to copy /usr/bin/genlop to a different location then run patch < genlop-540050.patch in that location. Then run genlop from that location. If that still doesn't work, then can you please attach the sections of the emerge.log showing when syncing is started and completed.
okay the direct patch of the executable works on my emerge.log file why the ebuild patch does not apply I do not know as it seems to "compile/install" w/o errors it must not apply in the proper place or is ignored
Fix pushed to repository. https://github.com/gentoo-perl/genlop/commit/46eb6a5a9a90049920ea84018b69b643c2809bfa I will get a -r1 release incorporating the patch as soon as I can.
Released in genlop-0.30.10-r1
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=784e0cddc47130412c37569deb120e542767f4ca commit 784e0cddc47130412c37569deb120e542767f4ca Author: Sam James <sam@gentoo.org> AuthorDate: 2023-07-18 22:06:20 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-07-18 22:09:16 +0000 app-portage/genlop: add 0.30.11 Closes: https://bugs.gentoo.org/283628 Closes: https://bugs.gentoo.org/447436 Closes: https://bugs.gentoo.org/540050 Closes: https://bugs.gentoo.org/658940 Closes: https://bugs.gentoo.org/677890 Closes: https://bugs.gentoo.org/697504 Signed-off-by: Sam James <sam@gentoo.org> app-portage/genlop/Manifest | 1 + app-portage/genlop/genlop-0.30.11.ebuild | 28 ++++++++++++++++++++++++++++ 2 files changed, 29 insertions(+)
