Summary: | dispatch-conf broken: OSError: [Errno 21] Is a directory | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Evgeny <worklord> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | njsg, patrick |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Evgeny
2013-02-03 16:05:08 UTC
It looks like a file/directory name conflict in /etc/config-archive is triggering this, like bug 342171. You can temporarily move your old /etc/config-archive to a different location like this: mv /etc/config-archive /etc/config-archive.old Then you should be able to run dispatch-conf successfully. Afterwards, you can manually merge the new directory with the old one (and please report any file/directory name conflict(s) that you find). (In reply to comment #1) > It looks like a file/directory name conflict in /etc/config-archive is > triggering this, like bug 342171. You can temporarily move your old > /etc/config-archive to a different location like this: > > mv /etc/config-archive /etc/config-archive.old Thank you. It resolve my problem. > Then you should be able to run dispatch-conf successfully. Afterwards, you > can manually merge the new directory with the old one (and please report any > file/directory name conflict(s) that you find). Sorry. After run dispatch-conf on clean config-archive and moving back from backup no error shows. I can reproduce - /etc/portage/package.use was a file. Something migrated it to a directory and left a package.use/package.use.old file Tadaah. File-Directory mismatch! I could reproduce with an older version of portage. But, after upgrading portage, dispatch-conf did not crash anymore. Perhaps there was some fix somewhere? *** This bug has been marked as a duplicate of bug 342171 *** *** This bug has been marked as a duplicate of bug 256376 *** |