View previous topic :: View next topic |
Author |
Message |
billydv l33t
Joined: 22 Dec 2006 Posts: 911 Location: Mount Vernon, NY
|
Posted: Mon Feb 06, 2012 4:13 am Post subject: My system is broke, can't emerge anything |
|
|
Linux1 ~ # emerge portage
Calculating dependencies... done!
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) sys-apps/portage-2.2.0_alpha85
* portage-2.2.0_alpha84.tar.bz2 RMD160 SHA1 SHA256 size ... [ ok ]
* portage-2.2.0_alpha85.patch.bz2 RMD160 SHA1 SHA256 size ... [ ok ]
* The ebuild phase 'unpack' has been killed by signal 11.
* The ebuild phase 'die_hooks' has been killed by signal 11.
>>> Failed to emerge sys-apps/portage-2.2.0_alpha85, Log file:
>>> '/var/tmp/portage/sys-apps/portage-2.2.0_alpha85/temp/build.log'
*
* The following package has failed to build or install:
*
* (sys-apps/portage-2.2.0_alpha85::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/sys-apps/portage-2.2.0_alpha85/temp/build.log'
*
Linux1 ~ #
I have no idea what's going on _________________ Billy DeVincentis |
|
Back to top |
|
|
ToeiRei Veteran
Joined: 03 Jan 2005 Posts: 1191 Location: Austria
|
Posted: Mon Feb 06, 2012 8:49 am Post subject: |
|
|
could be a broken library - or tar... just guessing from what I see as you didn't provide any logs _________________ Please stand by - The mailer daemon is busy burning your messages in hell... |
|
Back to top |
|
|
Desrick n00b
Joined: 30 Nov 2011 Posts: 1
|
Posted: Mon Feb 06, 2012 12:52 pm Post subject: |
|
|
I had the same problem. I fixed it by masking =sys-devel/binutils-2.22.52.0.1 and switching my binutils to 2.22-r1. I the ran FEATURES="-sandox" emerge -1 =sys-apps/sandbox-2.5 |
|
Back to top |
|
|
billydv l33t
Joined: 22 Dec 2006 Posts: 911 Location: Mount Vernon, NY
|
Posted: Mon Feb 06, 2012 1:50 pm Post subject: |
|
|
Sure was the binutils problem
1 mask new binutils that was accidentally keyworded
2 manually copy into place files from 2.22-r1 binutils
3 reboot
4 FEATURES="-sandbox" emerge -1 =sys-apps/sandbox-2.5
5 source /etc/profile && env-update
6 emerge binutils
7 source /etc/profile && env-update
8 emerge --emptytree @system
Thanks for the help _________________ Billy DeVincentis |
|
Back to top |
|
|
vfikov n00b
Joined: 11 Jan 2014 Posts: 4 Location: Sofia, Bulgaria
|
Posted: Sat Jan 11, 2014 2:34 pm Post subject: |
|
|
billydv wrote: | Sure was the binutils problem
1 mask new binutils that was accidentally keyworded
2 manually copy into place files from 2.22-r1 binutils
3 reboot
4 FEATURES="-sandbox" emerge -1 =sys-apps/sandbox-2.5
5 source /etc/profile && env-update
6 emerge binutils
7 source /etc/profile && env-update
8 emerge --emptytree @system
Thanks for the help |
Hi,
could you give more info on step 2, because i have the exact same issue and I've now masked the newer binutils, tried rebooting, but i always get the same error on anything i try to emerge:
Code: |
>>> Emerging (1 of 1) sys-apps/portage-2.2.8
* portage-2.2.8.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ]
* Both python2 and python3 USE flags are enabled, but only one
* can be in the shebangs. Using python3.
* The ebuild phase 'unpack' has been killed by signal 11.
* The ebuild phase 'die_hooks' has been killed by signal 11.
|
Thanks in advance! |
|
Back to top |
|
|
dol-sen Retired Dev
Joined: 30 Jun 2002 Posts: 2805 Location: Richmond, BC, Canada
|
Posted: Sat Jan 11, 2014 3:25 pm Post subject: |
|
|
First, It won't be the same problem you are experiencing.
Second, please post your "emerge --info portage" _________________ Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch... |
|
Back to top |
|
|
vfikov n00b
Joined: 11 Jan 2014 Posts: 4 Location: Sofia, Bulgaria
|
Posted: Sun Jan 12, 2014 9:18 am Post subject: ... |
|
|
Hi dol-sen!
Thanks for reply, but I already solved my issue...
I just needed to add FEATURES="-usersandbox" and now everything work fine!
BR,
Fikov |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21431
|
Posted: Sun Jan 12, 2014 6:25 pm Post subject: Re: ... |
|
|
vfikov wrote: | Hi dol-sen!
Thanks for reply, but I already solved my issue...
I just needed to add FEATURES="-usersandbox" and now everything work fine!
BR,
Fikov | That is a nasty workaround, not a fix. You might need to do this if your sandbox is broken, but you should fix the underlying problem and reactivate sandbox. |
|
Back to top |
|
|
vfikov n00b
Joined: 11 Jan 2014 Posts: 4 Location: Sofia, Bulgaria
|
Posted: Mon Jan 13, 2014 12:29 pm Post subject: well... |
|
|
Yeah I know and already did what you have suggested... But since i dont use sandbox I think it will be ok... |
|
Back to top |
|
|
billydv l33t
Joined: 22 Dec 2006 Posts: 911 Location: Mount Vernon, NY
|
Posted: Tue Jan 14, 2014 12:48 am Post subject: |
|
|
vfikov, i really don't think that is a proper solution.
gentoo can be a bit difficult when something breaks but it can usually be fixed with some patience
try these steps
1-get rid of the features line that disables sandbox and then do emerge --emptytree @system
2- reboot and run once again emerge --emptytree @system
3- reboot and run emerge --emptytree @world
hopefully whatever is broken will then be fixed _________________ Billy DeVincentis |
|
Back to top |
|
|
|