Hello. Portage ignores some binary packages when invoked with "--usepkg y" option, i.e. it re-emerges them from sources rather than emerging them from binary. Binary package is in /var/portage/packages and entry is present in /var/portage/packages/Packages. Here is a list of packages that affected: virtual/libiconv-0 virtual/libffi-3.0.11 media-libs/freetype-2.4.11:2 x11-proto/xf86driproto-2.1.1 x11-proto/dri2proto-2.8 media-libs/flac-1.2.1-r3 x11-proto/glproto-1.4.16 Reproducible: Always Steps to Reproduce: 1. emerge any package from the list with "--buildpkg y" 2. re-emerge the same package with "--usepkg y" Actual Results: The said package is re-emerged from sources. Expected Results: The said packages is re-emerged from binary. If you need any other info I'll provide it. Please fix.
Created attachment 367390 [details] emerge --info portage
Please post the output the "--usepkg y" command with --debug added.
Hmm, I've noticed this bug during world set rebuild (emerge -bk1ev world). This is not reproducible if I simply do "emerge -pk1v package", where package is any of the packages mentioned above. Also, this is not 100% reproducible if I run "emerge -pk1ev package", where package is one of the packages mentioned above. Sometimes the said package is marked as being emerged from binary, sometimes not. I'll attach some example emerge outputs without --debug, as it produce too much output. If later you need some output with --debug I'll attach it as well.
(In reply to Coacher from comment #3) > Hmm, I've noticed this bug during world set rebuild (emerge -bk1ev world). > This is not reproducible if I simply do "emerge -pk1v package", where > package is any of the packages mentioned above. > > Also, this is not 100% reproducible if I run "emerge -pk1ev package", where > package is one of the packages mentioned above. Sometimes the said package > is marked as being emerged from binary, sometimes not. > > I'll attach some example emerge outputs without --debug, as it produce too > much output. If later you need some output with --debug I'll attach it as > well. It's not useful without --debug. You'll need to compress the output and attach it. Would be nice to get one run where it takes a binary and one where it doesn't.
Created attachment 367416 [details] emerge -pk1ev virtual/libffi
Created attachment 367418 [details] emerge -pk1ev freetype
Created attachment 367422 [details] emerge -pk1ev flac
(In reply to Sebastian Luther (few) from comment #4) > It's not useful without --debug. You'll need to compress the output and > attach it. Would be nice to get one run where it takes a binary and one > where it doesn't. Oops, I've already attached it without --debug. Will reattach now.
Created attachment 367426 [details] emerge -pk1ev virtual/libffi --debug Here virtual/libffi is picked up as binary.
Created attachment 367430 [details] gzipped output of emerge -pk1ev freetype --debug Here all of the following packages are not picked up as binaries virtual/libiconv-0 virtual/libffi-3.0.11 media-libs/freetype-2.4.11:2 x11-proto/xf86driproto-2.1.1 x11-proto/dri2proto-2.8 x11-proto/glproto-1.4.16
Sorry I didn't notice that you're using 2.2.7. That's most likely bug 485920. Please update to portage-2.2.8.
Created attachment 367434 [details] gzipped output of emerge -pk1ev flac --debug Here all of the following packages are not picked up as binaries virtual/libiconv-0 virtual/libffi-3.0.11 media-libs/freetype-2.4.11:2 x11-proto/xf86driproto-2.1.1 x11-proto/dri2proto-2.8 x11-proto/glproto-1.4.16 flac itself is picked up as a binary, though.
(In reply to Sebastian Luther (few) from comment #11) > Sorry I didn't notice that you're using 2.2.7. That's most likely bug > 485920. Please update to portage-2.2.8. Hmm, I'll try to upgrade and give you the results though there are no multilib problems on my system as in bug you've mentioned.
(In reply to Coacher from comment #13) > (In reply to Sebastian Luther (few) from comment #11) > > Sorry I didn't notice that you're using 2.2.7. That's most likely bug > > 485920. Please update to portage-2.2.8. > > Hmm, I'll try to upgrade and give you the results though there are no > multilib problems on my system as in bug you've mentioned. Yes, upgrading to portage-2.2.8 solves this issue. Thanks a lot for your help. Hope to see new stable version of portage in the near future. *** This bug has been marked as a duplicate of bug 485920 ***