When running emerge --sync I got this trace back: Performing Global Updates: /usr/portage/profiles/updates/1Q-2007 (Could take a couple of minutes if you have a lot of binary packages.) .='update pass' *='binary update' @='/var/db move' s='/var/db SLOT move' S='binary SLOT move' p='update /etc/portage/package.*' .......... Traceback (most recent call last): File "/usr/bin/emerge", line 5289, in ? retval = emerge_main() File "/usr/bin/emerge", line 5246, in emerge_main action_sync(settings, trees, mtimedb, myopts, myaction) File "/usr/bin/emerge", line 3988, in action_sync if portage.global_updates(settings, trees, mtimedb["updates"]): File "/usr/lib/portage/pym/portage.py", line 7899, in global_updates trees["/"]["bintree"].move_ent(update_cmd) File "/usr/lib/portage/pym/portage.py", line 6100, in move_ent self.populate() File "/usr/lib/portage/pym/portage.py", line 6363, in populate if mypkg != mytbz2.getfile("PF").strip(): AttributeError: 'NoneType' object has no attribute 'strip' real 4m35.850s user 0m11.670s sys 0m13.785s * emerge --sync failed Reproducible: Always Steps to Reproduce: Could this have anything to do with the fact that the binpkgs are from a 32 bit chroot and not from the host system?
Created attachment 107771 [details, diff] handle binpkgs that have missing PF metadata You seem to have a corrupt binary package. If this patch is saved as /tmp/corrupt_binpkg.patch, then it can be applied as follows: cd /usr/lib/prtage patch -p0 < /tmp/corrupt_binpkg.patch
Thanks! Btw that was a really fast bug squash :)
This has been released in 2.1.2-r3.
