Summary: | uncaught UnsupportedAPIException during unmerge prerm phase | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Stefan G. Weichinger <lists> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 162453 |
Description
Stefan G. Weichinger
2007-01-21 16:16:29 UTC
# emerge -Ca "=dev-libs/glib-2.10.3" >>> These are the packages that would be unmerged: dev-libs/glib selected: 2.10.3 protected: none omitted: 2.12.4-r1 1.2.10-r5 >>> 'Selected' packages are slated for removal. >>> 'Protected' and 'omitted' packages will not be removed. Would you like to unmerge these packages? [Yes/No] >>> Waiting 5 seconds before starting... >>> (Control-C to abort)... >>> Unmerging in: 5 4 3 2 1 >>> Unmerging dev-libs/glib-2.10.3... Traceback (most recent call last): File "/usr/bin/emerge", line 5270, in ? retval = emerge_main() File "/usr/bin/emerge", line 5251, in emerge_main mtimedb["ldpath"]): File "/usr/bin/emerge", line 3416, in unmerge vartree=vartree, ldpath_mtimes=ldpath_mtimes) File "/usr/lib/portage/pym/portage.py", line 3887, in unmerge ldpath_mtimes=ldpath_mtimes) File "/usr/lib/portage/pym/portage.py", line 6813, in unmerge self.settings, 0, 0, self.vartree.dbapi) File "/usr/lib/portage/pym/portage.py", line 2966, in doebuild_environment raise portage_exception.UnsupportedAPIException(mycpv, eapi) Apparently /var/db/pkg/dev-libs/glib-2.10.3 is corrupt. What does the content look like? Normally, it should just contain the number 0. Go ahead and remove that file, then the unmerge will probably succeed. (In reply to comment #2) > Apparently /var/db/pkg/dev-libs/glib-2.10.3 is corrupt. I meant to say '/var/db/pkg/dev-libs/glib-2.10.3/EAPI'. This exception is handled in svn r5749. This has been released in 2.1.2-r2. (In reply to comment #3) > (In reply to comment #2) > > Apparently /var/db/pkg/dev-libs/glib-2.10.3 is corrupt. > > I meant to say '/var/db/pkg/dev-libs/glib-2.10.3/EAPI'. I removed that file and got another error: # emerge -Ca "=dev-libs/glib-2.10.3" >>> These are the packages that would be unmerged: dev-libs/glib selected: 2.10.3 protected: none omitted: 2.12.4-r1 1.2.10-r5 >>> 'Selected' packages are slated for removal. >>> 'Protected' and 'omitted' packages will not be removed. Would you like to unmerge these packages? [Yes/No] >>> Waiting 5 seconds before starting... >>> (Control-C to abort)... >>> Unmerging in: 5 4 3 2 1 >>> Unmerging dev-libs/glib-2.10.3... /var/db/pkg/dev-libs/glib-2.10.3/glib-2.10.3.ebuild: line 1: ¤V: command not found !!! ERROR: dev-libs/glib-2.10.3 failed. Call stack: ebuild.sh, line 1508: Called die !!! error sourcing ebuild !!! If you need support, post the topmost build error, and the call stack if relevant. !!! A complete build log is located at '/var/tmp/binpkgs/dev-libs/glib-2.10.3/temp/build.log'. !!! FAILED prerm: 1 A removal phase of the 'dev-libs/glib-2.10.3' package has failed with exit value 1. The problem occurred while executing the ebuild located at '/var/db/pkg/dev-libs/glib-2.10.3/glib-2.10.3.ebuild'. If necessary, manually remove the ebuild in order to skip the execution of removal phases. -- Then I removed '/var/db/pkg/dev-libs/glib-2.10.3/glib-2.10.3.ebuild' and the unmerge succeeded. Thank you, Stefan. |