I have install sys-apps/baselayout-1.6.9 and can't unmerge sys-apps/baselayout-1.6.7-r1. sys-apps/portage-1.8.5 ------------------------------------------- --- !found dev /dev/xda1 --- !found dev /dev/xda --- !found dev /dev/vcsa9 Traceback (most recent call last): File "/usr/sbin/ebuild", line 33, in ? a=portage.doebuild(pargs[0],x,getroot(),debug=debug) File "/usr/lib/python2.0/site-packages/portage.py", line 704, in doebuild return unmerge(settings["CATEGORY"],settings["PF"],myroot) File "/usr/lib/python2.0/site-packages/portage.py", line 805, in unmerge mylink.unmerge() File "/usr/lib/python2.0/site-packages/portage.py", line 2049, in unmerge if not isdev(obj): File "/usr/lib/python2.0/site-packages/portage.py", line 738, in isdev mymode=os.stat(x)[ST_MODE] OSError: [Errno 2] No such file or directory: '/dev/vcsa8' >>> sys-apps/baselayout-1.6.7-r1 unmerged
If /dev/vcsa8 is a removable drive please insert a disk to work around this bug. For me this solves the problem temp, also it should be fixed in the software. Hope it helps Nils Ohlmeier
The problem is that portage.py in 'isdev' can't check/unlink invalid symbolic link. /dev/vcsa8 is symbolic link to /dev/vcc/a8 that is invalid. rm /dev/vcsa8 And then: rm /dev/vcs8 rm /dev/midi00 rm /dev/sg0 ... --- !empty dir /boot >>> sys-apps/baselayout-1.6.7-r1 unmerged And the unmerge was done :-).
fixed on cvs. This bug was silly since we don't unmerge device nodes anyway.