portage 2.0.49-r15: the failed emerge of baselayout makes the portage database corrupt. example: x root # emerge -u world [...compiles and...] >>> /bin/rc-status --- /dev/ --- /dev/pts/ !!! copy /var/tmp/portage/baselayout-1.8.6.10-r1/image/dev/pts/.keep -> /dev/pts/.keep failed. !!! [Errno 13] Permission denied: '/dev/pts/.keep#new' [... and now query the portage database ..] x root # emerge -up world These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild U ] app-editors/quanta-3.1.4 [3.1.2] [ebuild U ] dev-db/postgresql-7.3.4 [7.3.2] [ebuild U ] media-video/kmplayer-0.8b [0.7.3] [ebuild U ] app-office/openoffice-1.1.0 [1.0.3-r1] Traceback (most recent call last): File "/usr/bin/emerge", line 2133, in ? mydepgraph.display(mydepgraph.altlist()) File "/usr/bin/emerge", line 1103, in display elif (not "--emptytree" in myopts) and portage.db[x[1]]["vartree"].exists_specific_cat(x[2]): File "/usr/lib/python2.2/site-packages/portage.py", line 3469, in exists_specific_cat self.invalidentry(self.root+"var/db/pkg/"+a[0]+"/"+x) AttributeError: vartree instance has no attribute 'invalidentry' Reproducible: Always Steps to Reproduce: see 'details' for version numbers and portage version Expected Results: no database integrity errors
*** This bug has been marked as a duplicate of 31901 ***