`emerge world -up`: These are the packages that I would merge, in order. Calculating world dependencies ...done! [ebuild N ] sys-apps/texinfo-4.2-r4 to / [ebuild U ] sys-devel/automake-1.6.1-r6 to / [ebuild U ] media-gfx/imagemagick-5.4.6 to / [ebuild U ] net-print/gimp-print-cups-4.3.0-r2 to / [ebuild U ] net-misc/openssh-3.4_p1-r1 to / [ebuild U ] sys-devel/libtool-1.4.1-r9 to / [ebuild U ] dev-libs/libmcrypt-2.5.1-r4 to / [ebuild U ] app-admin/analog-5.24 to / [ebuild U ] sys-apps/lsof-4.64 to / `emerge world -uk`: Calculating world dependencies ...done! >>> emerge sys-apps/texinfo-4.2-r4 to / >>> md5 ;-) texinfo-4.2.tar.gz >>> Unpacking source... >>> Unpacking texinfo-4.2.tar.gz this is wrong ... binary installs/updates do not extract source and compile and all that fun stuff ... `emerge texinfo -k` Calculating dependencies ...done! >>> emerge sys-apps/texinfo-4.2-r4 to / >>> extracting info >>> extracting texinfo-4.2-r4 ahh ... so much better ... portage *does* use the binary packages w/out a problem if the pkg is already on the system (and thus upgrading). its the fact its a new pkg that makes it freak
also, it would appear that doing -k with a specific ebuild/version does not work either home db # ls /var/tmp/pkgdir/All/db-* -1 /var/tmp/pkgdir/All/db-1.85-r1.tbz2 /var/tmp/pkgdir/All/db-3.2.9.tbz2 home db # emerge -k db Calculating dependencies ...done! >>> emerge sys-libs/db-3.2.9 to / >>> extracting info >>> extracting db-3.2.9 home db # emerge -k db-3.2.9.ebuild Calculating dependencies ...done! >>> emerge sys-libs/db-3.2.9 to / >>> md5 ;-) db-3.2.9.tar.gz >>> Unpacking source... >>> Unpacking db-3.2.9.tar.gz home db # emerge -k db-1.85-r1.ebuild Calculating dependencies ...done! >>> emerge sys-libs/db-1.85-r1 to / >>> md5 ;-) db.1.85.tar.gz >>> Unpacking source... >>> Unpacking db.1.85.tar.gz home db # emerge -k =db-1.85-r1 Calculating dependencies ...done! >>> emerge sys-libs/db-1.85-r1 to / >>> md5 ;-) db.1.85.tar.gz >>> Unpacking source... >>> Unpacking db.1.85.tar.gz home db # emerge -k =db-3.2.9 Calculating dependencies ...done! >>> emerge sys-libs/db-3.2.9 to / >>> md5 ;-) db-3.2.9.tar.gz >>> Unpacking source... >>> Unpacking db-3.2.9.tar.gz
not sure how to describe this one (portage-2.0.10) ... home root # emerge glib -up These are the packages that I would merge, in order. Calculating dependencies ...done! [ebuild N ] app-text/sgml-common-0.6.3-r1 to / [ebuild N ] app-text/docbook-sgml-dtd-4.1 to / [ebuild N ] app-text/docbook-sgml-dtd-3.1 to / [ebuild N ] app-text/docbook-sgml-dtd-3.0 to / [ebuild N ] app-text/docbook-xml-simple-dtd-4.1.2.4 to / [ebuild N ] app-text/openjade-1.3.1-r4 to / [ebuild N ] dev-perl/SGMLSpm-1.03-r1 to / [ebuild U ] dev-libs/libxml2-2.4.23 to / [ebuild N ] app-text/docbook-xsl-stylesheets-1.50.0 to / [ebuild N ] app-text/docbook-xml-dtd-4.1.2-r2 to / [ebuild N ] app-text/docbook-dsssl-stylesheets-1.64 to / [ebuild N ] app-text/docbook-sgml-dtd-4.0 to / [ebuild N ] app-text/docbook-sgml-utils-0.6.11 to / [ebuild N ] app-text/docbook-sgml-1.0 to / [ebuild N ] dev-util/pkgconfig-0.12.0 to / [ebuild N ] dev-util/gtk-doc-0.9-r2 to / [ebuild U ] dev-libs/glib-2.0.4-r1 to / home root # emerge glib -uk Calculating dependencies ...done! * Regenerating GNU info directory index... * Processed 54 info files. * IMPORTANT: 8 config files in /etc need updating. * Type emerge --help config to learn how to update config files. home root # emerge glib -k Calculating dependencies ...done! >>> emerge dev-libs/glib-1.2.10-r4 to / *** installs glib-1.2.10-r4 from binary package, but no dependencies *** home root # emerge glib Calculating dependencies ...done! >>> emerge app-text/sgml-common-0.6.3-r1 to / *** installs all of glib's dependencies from source ***
this looks like it might be because of the older package version that it freaks on ... i did `emerge portage -uk` and it worked fine (had 2.0.13 installed, 2.0.22 was latest) home root # env | grep PKGDIR PKGDIR=/var/tmp/pkgdir home root # emerge world -up These are the packages that I would merge, in order. Calculating world dependencies ...done! [ebuild U ] sys-apps/groff-1.16.1-r1 to / [ebuild U ] sys-apps/man-1.5k to / [ebuild U ] sys-apps/man-pages-1.52 to / [ebuild U ] sys-apps/portage-2.0.22 to / [ebuild U ] sys-libs/pam-0.75-r7 to / [ebuild U ] sys-devel/perl-5.6.1-r5 to / home root # emerge world -uk Calculating world dependencies ...done! >>> emerge sys-apps/groff-1.16.1-r1 to / ^C home root # emerge groff -uk Calculating dependencies ...done! * Regenerating GNU info directory index... ^C home root # emerge -s groff [ Results for search key : groff ] [ Applications found : 1 ] * sys-apps/groff Latest version Available: 1.16.1-r1 Latest version Installed: 1.17.2-r1 Homepage: http://www.gnu.org/software/groff/groff.html Description: Text formatter used for man pages home root # emerge groff -k <installs v1.17.2-r1 from binary package> home root # emerge =groff-1.16.1-r1 -k Calculating dependencies ...done! >>> emerge sys-apps/groff-1.16.1-r1 to / ^C
similar to the last one i posted home root # emerge world -up These are the packages that I would merge, in order. Calculating world dependencies ...done! [ebuild U ] sys-apps/groff-1.16.1-r1 to / [ebuild U ] sys-apps/man-1.5k to / [ebuild U ] sys-apps/man-pages-1.52 to / [ebuild U ] sys-libs/pam-0.75-r7 to / [ebuild U ] sys-devel/perl-5.6.1-r5 to / home root # emerge world -uk Calculating world dependencies \Traceback (most recent call last): File "/usr/bin/emerge", line 1390, in ? if not mydepgraph.xcreate(myaction): File "/usr/bin/emerge", line 837, in xcreate if not self.create(myk): File "/usr/bin/emerge", line 699, in create mydep["/"]=edepend[0]+" "+edepend[1] UnboundLocalError: local variable 'edepend' referenced before assignment
if you have an older version of a binary package and you run `emerge <pkg> -k`, then the emerge will not function properly, and die at the end example: latest version of ppp installed is 2.4.0 (binary package exists for 2.4.0) latest version of ppp available is 2.4.1 (binary package does not exist) `emerge ppp -k` will use the binary package for the older version, then die because it could not find the correct ebuild (it looked for the ebuild of ppp- 2.4.1 that *should* have been in the binary package *if* it had been the correct version, but instead, ppp-2.4.0.ebuild existed)
*** Bug 5977 has been marked as a duplicate of this bug. ***
techdirt root # emerge world -up These are the packages that I would merge, in order. Calculating world dependencies ...done! [ebuild U ] dev-libs/openssl-0.9.6e to / [ebuild U ] net-mail/mailbase-0.00-r4 to / [ebuild U ] net-libs/libwww-5.4.0 to / [ebuild N ] app-text/sgml-common-0.6.3-r2 to / [ebuild N ] app-text/docbook-sgml-dtd-4.1 to / [ebuild N ] app-text/docbook-sgml-dtd-3.1 to / [ebuild N ] app-text/docbook-sgml-dtd-3.0 to / [ebuild N ] app-text/docbook-xml-simple-dtd-4.1.2.4 to / [ebuild N ] app-text/openjade-1.3.1-r4 to / [ebuild N ] dev-perl/SGMLSpm-1.03-r1 to / [ebuild N ] app-text/docbook-xsl-stylesheets-1.52.2 to / [ebuild N ] app-text/docbook-xml-dtd-4.1.2-r2 to / [ebuild N ] app-text/docbook-dsssl-stylesheets-1.77 to / [ebuild N ] app-text/docbook-sgml-dtd-4.0 to / [ebuild N ] app-text/docbook-sgml-utils-0.6.11 to / [ebuild N ] app-text/docbook-sgml-1.0 to / [ebuild N ] dev-util/pkgconfig-0.12.0 to / [ebuild N ] dev-util/gtk-doc-0.9-r2 to / [ebuild U ] dev-libs/glib-2.0.4-r1 to / [ebuild U ] dev-libs/expat-1.95.4 to / [ebuild U ] dev-java/java-config-0.2.4-r1 to / [ebuild U ] dev-libs/gmp-4.1-r1 to / [ebuild U ] sys-apps/miscfiles-1.3 to / [ebuild U ] dev-libs/mm-1.2.1 to / [ebuild U ] sys-apps/ucspi-tcp-0.88-r2 to / techdirt root # emerge world -uk Calculating world dependencies Traceback (most recent call last): File "/usr/bin/emerge", line 1315, in ? if not mydepgraph.xcreate(myaction): File "/usr/bin/emerge", line 756, in xcreate mypk=portage.db[portage.root]["bintree"].dep_bestmatch(mydep) File "/usr/lib/python2.2/site-packages/portage.py", line 3103, in dep_bestmatch self.populate() File "/usr/lib/python2.2/site-packages/portage.py", line 3082, in populate mycat=mytbz2.getfile("CATEGORY") File "/usr/lib/python2.2/site-packages/xpak.py", line 182, in getfile self.scan() File "/usr/lib/python2.2/site-packages/xpak.py", line 160, in scan a.seek(-16,2) IOError: [Errno 22] Invalid argument
i dont know how many of these are still valid in the latest versions (i know some are because i continue to see some of the described behavior), but i dont know how much you really test the binary package aspect of portage. at the very least, the examples ive posted provide a nice set of tests to use ...
*** Bug 6325 has been marked as a duplicate of this bug. ***
*** Bug 6529 has been marked as a duplicate of this bug. ***
some of these bugs still exist in 2.0.28 :/
so -k doesnt work at all now ? root@home root # set | grep PKGDIR PKGDIR=/var/tmp/pkgdir root@home root # ls /var/tmp/pkgdir/All/ipta* /var/tmp/pkgdir/All/iptables-1.2.6a-r1.tbz2 /var/tmp/pkgdir/All/iptables-1.2.7.tbz2 root@home root # emerge iptables --usepkg Calculating dependencies ...done! >>> emerge sys-apps/iptables-1.2.7 to / >>> md5 ;-) iptables-1.2.7.tar.bz2 >>> Unpacking source... root@home root # emerge iptables -k Calculating dependencies ...done! >>> emerge sys-apps/iptables-1.2.7 to / >>> md5 ;-) iptables-1.2.7.tar.bz2 >>> Unpacking source... this saddens me very much due to the fact that some computers here die if i try to compile on them ... plus seeing as how i build my binary packages on a p3 800, its a lot faster than building them on a 486/586 ...
i dont know python so i cant really track down the source of this edepend bug buuuuuuut, i found this much out at line 612 in /usr/bin/emerge: if mytype=="binary": when you run `emerge world -uk`, mytype has the value 'binary ' ... not sure where that trailing space came from, but its there ... so, my fix (just so i can update some packages on this system) is to do: if mytype=="binary" or mytype=="binary ": at this point, `emerge world -uk` worked just as it used to i would use a trim function if i knew what the equiv of trim in python is :/
same as #6718
*** Bug 6718 has been marked as a duplicate of this bug. ***
*** Bug 7061 has been marked as a duplicate of this bug. ***
Should be fixed in Portage 2.0.30 (final version)