When running python-updater, it tries to emerge this: app-office/-MERGING-openoffice-bin:0 The package name '-MERGING-openoffice-bin' is invalid, and so the process dies with this message: !!! 'app-office/-MERGING-openoffice-bin:0' is not a valid package atom. Reproducible: Always Steps to Reproduce: Actual Results: # python-updater * Starting Python Updater... * Main active version of Python: 2.6 * Active version of Python 2: 2.6 * Active version of Python 3: 3.1 * Adding to list: app-office/-MERGING-openoffice-bin:0 * Adding to list: app-office/openoffice-bin:0 * Adding to list: dev-java/java-config:2 * Adding to list: dev-libs/boost:1.41 * check: manual [Added to list manually, see CHECKS in manpage for more information.] * Adding to list: x11-libs/vte:0 * check: manual [Added to list manually, see CHECKS in manpage for more information.] * emerge -Dv1 --keep-going app-office/-MERGING-openoffice-bin:0 app-office/openoffice-bin:0 dev-java/java-config:2 dev-libs/boost:1.41 x11-libs/vte:0 !!! 'app-office/-MERGING-openoffice-bin:0' is not a valid package atom. !!! Please check ebuild(5) for full details. Expected Results: I expected it to emerge 'openoffice-bin' without the false '-MERGING-openoffice-bin'
Your VDB (/var/db/pkg) contains -MERGING-* directory. It was caused by interruption of merging of files of that package from "${D}" to "${ROOT}".
(In reply to comment #1) > Your VDB (/var/db/pkg) contains -MERGING-* directory. It was caused by > interruption of merging of files of that package from "${D}" to "${ROOT}". Thank you. I do find that I have a '/var/db/pkg/app-office/-MERGING-openoffice-bin-3.1.1/' directory (even though I have openoffice-bin-3.2.0 installed). The average user probably won't know the cause (or solution) for this issue. So, I believe that python-updater should catch the fact that '-MERGING-openoffice-bin' is an invalid package atom, and not try to emerge it. Or, it seems that some process (eclean, or portage itself) could have removed the unneeded '-MERGING-openoffice-bin-3.1.1' directory. I will venture to reopen the bug, hoping that a user-friendly option could be created to (perhaps automatically) deal with this issue, so that it doesn't catch other Gentoo users off guard.
It would be a duplicate of bug #192778 and bug #217345.
