Summary: | sys-apps/portage-2.2_rc20: emerging fails with FEATURES=buildpkg | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Erik Hahn <erik_hahn> |
Component: | New packages | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | Keywords: | InVCS |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 210077, 254662 | ||
Attachments: | fix logic so the AssertionError isn't triggered |
Description
Erik Hahn
2008-12-31 02:01:30 UTC
Created attachment 176936 [details, diff]
fix logic so the AssertionError isn't triggered
If this patch is saved as /tmp/buildpkg_failure.patch, then it can be applied as follows:
patch /usr/lib/portage/pym/_emerge/__init__.py /tmp/buildpkg_failure.patch
That patch didn't help, it just changed the error message a bit: tar: ./usr/lib/xulrunner-1.9/sdk/lib/libxul.so: file changed as we read it * * ERROR: net-libs/xulrunner-1.9.0.5 failed. * Call stack: * misc-functions.sh, line 716: Called dyn_package * misc-functions.sh, line 641: Called die * The specific snippet of code: * assert * The die message: * (no error message) * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/net-libs/xulrunner-1.9.0.5/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/net-libs/xulrunner-1.9.0.5/temp/environment'. * (In reply to comment #2) > That patch didn't help, it just changed the error message a bit: There were two issues and one was triggering the other. Now one issue is fixed and there is one remaining. > tar: ./usr/lib/xulrunner-1.9/sdk/lib/libxul.so: file changed as we read it That file should be located at '/var/tmp/portage/net-libs/xulrunner-1.9.0.5/image/usr/lib/xulrunner-1.9/sdk/lib/libxul.so'. Normally, there shouldn't be anything modifying it while tar is running. Does `lsof | grep /var/tmp/portage/net-libs/xulrunner-1.9.0.5` report any programs with open files inside that directory? It might be a bug in the ebuild which causes some process to be left running. Do you have this problem with any other ebuilds or just xulrunner-1.9.0.5? I retried with mutt (xulrunner needs more than an hour on my system. No problems this time. (In reply to comment #0) > File "//usr/lib/portage/pym/_emerge/__init__.py", line 2692, in > _buildpkg_exit > if self._final_exit(packager) != os.EX_OK or \ > File "//usr/lib/portage/pym/_emerge/__init__.py", line 1949, in _final_exit > self._default_exit(task) > File "//usr/lib/portage/pym/_emerge/__init__.py", line 1937, in _default_exit > self._assert_current(task) > File "//usr/lib/portage/pym/_emerge/__init__.py", line 1925, in > _assert_current > raise AssertionError("Unrecognized task: %s" % (task,)) > AssertionError: Unrecognized task: <_emerge.EbuildBinpkg object at 0x9fb235c> This is fixed in 2.1.6.5 and 2.2_rc21. Please file a separate bug if there are any remaining issues. |