Bug 253176 – app-portage/esearch-0.7.1: esync broken by portage update to sys-apps/portage-2.1.6.4

• Product: Gentoo Linux
• Status: RESOLVED DUPLICATE

[Description Andreas K. Hüttel 2008-12-30 19:04:08 UTC]

bellini ~ # esync
/usr/lib/portage/pym/output.py:39: DeprecationWarning: DEPRECATION NOTICE: The output module was replaced by portage.output
 * Importing old portage tree
 * Doing '/usr/bin/emerge sync' now
 * Error: '/usr/bin/emerge sync' failed, see /var/log/emerge-sync.log for errors

bellini ~ # 
bellini ~ # cat /var/log/emerge-sync.log
Calculating dependencies ... done!

emerge: there are no ebuilds to satisfy "sync".

bellini ~ # 

It seems like the new portage version does not understand "emerge sync" anymore, only "emerge --sync". Fixed by the following one-line patch:

--------------------------------------------------------------------
--- esync.py.orig       2008-12-30 19:58:19.000000000 +0100
+++ esync.py    2008-12-30 19:59:19.000000000 +0100
@@ -22,7 +22,7 @@

 from common import needdbversion

-syncprogram =   "/usr/bin/emerge sync"
+syncprogram =   "/usr/bin/emerge --sync"
 logfile_sync =  "/var/log/emerge-sync.log"
 tmp_prefix =    "/tmp/esync"
--------------------------------------------------------------------


In addition there's this unrelated deprecation warning...

[Comment 1 Jeremy Olexa (darkside) (RETIRED) 2008-12-30 19:29:22 UTC]

esearch is not going to be widely updated but there is a stablereq for a new version. You should have better luck with that.

[Comment 2 Paul Varner (RETIRED) 2008-12-30 20:48:22 UTC]

This is fixed in esearch-0.7.1-r5

*** This bug has been marked as a duplicate of bug 124601 ***

[Comment 3 Andreas K. Hüttel 2008-12-30 21:39:26 UTC]

Well it is not fixed in stable. Just to point that out. Typical Gentoo problem.