Summary: | portage-2.2_rc33 depclean crashes with cannot allocate memory. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Chad A. Simmons <chad.simmons> |
Component: | [OLD] Core system | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | minor | Keywords: | InVCS |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 210077 |
Description
Chad A. Simmons
2009-06-26 20:23:48 UTC
In svn r13698:13700 it's fixed to free memory from the dep calculation before doing the unmerge. The patch doesn't apply to rc33, so you'll have to wait for the next release or else use an svn checkout to test it: http://www.gentoo.org/proj/en/portage/doc/testing.xml#doc_chap3 Still getting the same traceback/crash with r13700 Are you sure that it was executing the latest version (not 2.2_rc33)? The traceback should have looked at least a little different due to changed line numbers and file names. I think so for some reason its saying its r13694 but I did a checkout of 13700. Also I should have said similar not same. chadgentoo trunk # emerge --version Portage 13694-svn (default/linux/amd64/2008.0/desktop, gcc-4.3.3, glibc-2.10.1-r0, 2.6.30-gentoo-r1 x86_64) chadgentoo trunk # emerge --depclean @kde-3.5 Calculating dependencies... done! >>> Checking for lib consumers... >>> Assigning files to packages... kde-base/kpersonalizer selected: 3.5.10 protected: none omitted: none kde-base/kdeprint selected: 3.5.10 protected: none omitted: none kde-base/khotkeys selected: 3.5.10 protected: none omitted: 4.2.4 kde-base/kdesu selected: 3.5.10 protected: none omitted: 4.2.4 kde-base/kdebase-kioslaves selected: 3.5.10-r1 protected: none omitted: 4.2.4 kde-base/kooka selected: 3.5.10 protected: none omitted: none kde-base/ksplashml selected: 3.5.10 protected: none omitted: none kde-base/kfind selected: 3.5.10 protected: none omitted: 4.2.4 kde-base/kdesktop selected: 3.5.10 protected: none omitted: none kde-base/kicker selected: 3.5.10-r1 protected: none omitted: none kde-base/kcminit selected: 3.5.10 protected: none omitted: 4.2.4 kde-base/kghostview selected: 3.5.10 protected: none omitted: none kde-base/libkscan selected: 3.5.10 protected: none omitted: none kde-base/kcheckpass selected: 3.5.10 protected: none omitted: 4.2.4 kde-base/kmenuedit selected: 3.5.10 protected: none omitted: none kde-base/kdialog selected: 3.5.10 protected: none omitted: 4.2.4 kde-base/libkonq selected: 3.5.10 protected: none omitted: 4.2.4 >>> 'Selected' packages are slated for removal. >>> 'Protected' and 'omitted' packages will not be removed. >>> Waiting 5 seconds before starting... >>> (Control-C to abort)... >>> Unmerging in: 5 4 3 2 1 >>> Unmerging kde-base/kpersonalizer-3.5.10... !!! Error extracting saved environment: '/var/db/pkg/kde-base/kpersonalizer-3.5.10/environment.bz2' * The 'prerm' phase of the 'kde-base/kpersonalizer-3.5.10' package has * failed with exit value -1. * * The problem occurred while executing the ebuild file named * 'kpersonalizer-3.5.10.ebuild' located in the '/var/db/pkg/kde- * base/kpersonalizer-3.5.10' directory. If necessary, manually remove the * environment.bz2 file and/or the ebuild file located in that directory. * * Removal of the environment.bz2 file is preferred since it may allow the * removal phases to execute successfully. The ebuild will be sourced and * the eclasses from the current portage tree will be used when necessary. * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm() * removal phases to be skipped entirely. Traceback (most recent call last): File "/root/portage/trunk/bin/emerge", line 40, in <module> retval = emerge_main() File "/root/portage/trunk/pym/_emerge/main.py", line 1215, in emerge_main myopts, myaction, myfiles, spinner) File "/root/portage/trunk/pym/_emerge/actions.py", line 2318, in action_uninstall opts, action, valid_atoms, spinner) File "/root/portage/trunk/pym/_emerge/actions.py", line 612, in action_depclean cleanlist, ldpath_mtimes, ordered=ordered) File "/root/portage/trunk/pym/_emerge/unmerge.py", line 512, in unmerge scheduler=scheduler) File "/root/portage/trunk/pym/portage/__init__.py", line 6822, in unmerge ldpath_mtimes=ldpath_mtimes) File "/root/portage/trunk/pym/portage/dbapi/vartree.py", line 2058, in unmerge vartree=self.vartree) File "/root/portage/trunk/pym/portage/__init__.py", line 6304, in doebuild fd_pipes=fd_pipes, returnpid=returnpid) File "/root/portage/trunk/pym/portage/__init__.py", line 3416, in spawn _create_pty_or_pipe(copy_term_size=fd_pipes_orig[1]) File "/root/portage/trunk/pym/portage/__init__.py", line 3324, in _create_pty_or_pipe set_term_size(rows, columns, slave_fd) File "/root/portage/trunk/pym/portage/output.py", line 421, in set_term_size spawn(cmd, env=os.environ, fd_pipes={0:fd}) File "/root/portage/trunk/pym/portage/process.py", line 225, in spawn pid = os.fork() OSError: [Errno 12] Cannot allocate memory I got this to work for some reason on my system 4GB of memory isn't enough to run this command. I added an additional 4GB of swap and now it succeeds. Hopefully this is fixed in 2.2_rc68, by the following commits: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=c4fdf0e53398e4917c64901da626ced4c6357010 http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=0faca588d881865be6eafc9b6401124bb927bee5 Please re-open if the problem persists. |