I use supermount (and as the gentoo-sources do have this enabled, you should think there are others that have so) for my cdrom. As I update baselayout, it tries to create a new /mnt/cdrom folder which results in a i/o-error in the portage python-script. Unregarded that there is no need to create mountpoints that I do not want (why the heck do I ned /mnt/floppy), this should not break emerge at all. I would prefer if baselayout does not create any mountpoint.
I have the same grievance against baselayout. It is not compatable with supermount mounted filesystems.
> I have the same grievance against baselayout. It is not compatable with > supermount mounted filesystems. Huh? Anyhow, this issue is fixed (or should be) in baselayout-1.8.6.7.
I emerged baselayout 1.8.6.7 this morning (app. 7:00am GMT) and the error occured. I will try to re-emerge it tomorrow. Could it be that autoclean tries to remove the mountpoints because they were part of the older baselayout-version? Just another suggestion... I did not see when the error was exactly, I just saw the error message there.
Hey, what's going on! I thought it was fixed (it worked one day), but now I have to see this! ======================================================= Traceback (most recent call last): File "/usr/bin/emerge", line 1949, in ? unmerge("clean", ["world"]) File "/usr/bin/emerge", line 1445, in unmerge retval=portage.unmerge(mysplit[0],mysplit[1],portage.root,unmerge_action not in ["clean","prune"]) File "/usr/lib/python2.2/site-packages/portage.py", line 1825, in unmerge mylink.unmerge(trimworld=mytrimworld) File "/usr/lib/python2.2/site-packages/portage.py", line 4131, in unmerge objld=listdir(obj) File "/usr/lib/python2.2/site-packages/portage.py", line 93, in listdir list = os.listdir(mypath) OSError: [Errno 123] No medium found: '/mnt/cdrom' ======================================================= It's really buggin at all!
this has nothing todo with supermount and is an issue with portage.
