| View previous topic :: View next topic |
| Author |
Message |
Featherfoot
Veteran
Joined: 28 Dec 2002
Posts: 1108
Location: Stuart, Florida
|
 Posted: Tue Oct 15, 2013 7:20 pm Post subject: emerge is hanging at Unpacking... |
 |
|
Portage has stopped working on my and I need some advice.
The problem is that when I "emerge <package>" emerge hangs in a loop waiting for the unpacking source step to complete. Which it never does.
for example
bopper download # emerge mesa
Calculating dependencies... done!
!!! The following installed packages are masked:
- sci-geosciences/googleearth-7.1.1.1871::gentoo (masked by: package.mask)
/usr/portage/profiles/package.mask:
# Julian Ospald <hasufell@gentoo.org> (21 Jul 2013)
# Mask all unfetchable versions and those with tons of random
# bugs and segfaults (all). Don't ask for a version bump unless
# there is a working release.
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) media-libs/mesa-9.2.1
* MesaLib-9.2.1.tar.bz2 SHA256 SHA512 WHIRLPOOL size  ... [ ok ]
>>> Unpacking source...
>>> Unpacking MesaLib-9.2.1.tar.bz2 to /var/tmp/portage/media-libs/mesa-9.2.1/work
^C
Exiting on signal 2
sandbox:stop caught signal 2 in pid 11022
sandbox:stop signal already caught and busy still cleaning up!
Sandboxed process killed by signal: Interrupt
I have checked MesaLib-9.2.1.bar.bz2 and I can open it with "ark".
/var/tmp/portage/media-libs/mesa-9.2.1/work is empty although other directories in /var/tmp/portage/media-libs/mesa-9.2.1 are not empty.
It seems clear to me that the unpacking routine that emerge uses has a problem. The only idea I can come up with is to chroot into the system and replace something.
Do I replace portage? Unzip? Gzip?
Your advice would be appreciated. |
|
| Back to top |
|
 |
Hu
Moderator
Joined: 06 Mar 2007
Posts: 21602
|
| Posted: Tue Oct 15, 2013 8:09 pm Post subject: |
|
|
| Start with debugging whichever program is actually hung. Check your ps output to find it. |
|
| Back to top |
|
|
666threesixes666
Veteran
Joined: 31 May 2011
Posts: 1248
Location: 42.68n 85.41w
|
| Posted: Tue Oct 15, 2013 8:41 pm Post subject: |
|
|
| heh, i get unzip failed messages @ oracle-jdk-bin on my laptop... i can tar -xf jdk-7-u40.tar.gz just fine is the crazy part.... |
|
| Back to top |
|
|
Featherfoot
Veteran
Joined: 28 Dec 2002
Posts: 1108
Location: Stuart, Florida
|
| Posted: Tue Oct 15, 2013 10:58 pm Post subject: |
|
|
When I do a ps -A while emerge is hung, bzip2 is running. This is odd, because I didn't see an option in bzip2 to compress more than to a tar file.
I was able to use bzip2 to decompress the same MesaLib-9.2.1.tar.bz2 into one of my directories.
Does anybody else like the theory that perhaps bzip2 didn't get a complete command line from emerge? Or else it was operating from stdin and never got an eof? |
|
| Back to top |
|
|
Genone
Retired Dev
Joined: 14 Mar 2003
Posts: 9523
Location: beyond the rim
|
| Posted: Wed Oct 16, 2013 7:33 am Post subject: |
|
|
| If bzip just sits there without any CPU usage then yeah, quite possible that it's just waiting for input which for some reason isn't supplied (I think the input file is piped into stdin, but too lazy to check right now). |
|
| Back to top |
|
|
honp
Guru
Joined: 25 Sep 2006
Posts: 355
Location: Good old Prague, Czech rep.
|
| Posted: Wed Dec 04, 2013 6:50 pm Post subject: |
|
|
Hi, great that i have finaly found this post. I have got exactly the same problem.
here is some more detailed info:
| Code: | LT-ntb ~ # PORTAGE_DEBUG="1" emerge portage
...
...
+ echo '>>> Unpacking portage-2.2.7.tar.bz2 to /var/tmp/portage/sys-apps/portage-2.2.7/work'
>>> Unpacking portage-2.2.7.tar.bz2 to /var/tmp/portage/sys-apps/portage-2.2.7/work
+ suffix=bz2
++ LC_ALL=C
++ tr '[:upper:]' '[:lower:]'
+ suffix_insensitive=bz2
+ y=portage-2.2.7.tar
+ y=tar
++ LC_ALL=C
++ tr '[:upper:]' '[:lower:]'
+ y_insensitive=tar
+ [[ portage-2.2.7.tar.bz2 == \.\/* ]]
+ [[ portage-2.2.7.tar.bz2 == /var/tmp/portage/sys-apps/portage-2.2.7/distdir/* ]]
+ [[ portage-2.2.7.tar.bz2 == \/* ]]
+ srcdir=/var/tmp/portage/sys-apps/portage-2.2.7/distdir/
+ [[ ! -s /var/tmp/portage/sys-apps/portage-2.2.7/distdir/portage-2.2.7.tar.bz2 ]]
+ myfail='failure unpacking portage-2.2.7.tar.bz2'
+ case "${suffix_insensitive}" in
+ ___eapi_unpack_is_case_sensitive
+ [[ 2 =~ ^(0|1|2|3|4|4-python|4-slot-abi|5|5-hdepend)$ ]]
+ [[ bz bz2 != *\ \b\z\2\ * ]]
+ __unpack_tar 'bzip2 -d'
+ [[ tar == tar ]]
+ ___eapi_unpack_is_case_sensitive
+ [[ 2 =~ ^(0|1|2|3|4|4-python|4-slot-abi|5|5-hdepend)$ ]]
+ [[ tar != tar ]]
+ bzip2 -d -c -- /var/tmp/portage/sys-apps/portage-2.2.7/distdir/portage-2.2.7.tar.bz2
+ tar xof - |
| Code: | LT-ntb ~ # ps aux | grep bz
portage 16042 0.1 0.0 316388 1500 pts/0 S+ 19:35 0:00 bzip2 -d -c -- /var/tmp/portage/sys-apps/portage-2.2.7/distdir/portage-2.2.7.tar.bz2 |
Hm, now i have solved my problem... juchuuuuuuuu ))
Problem was that i used parallel lbzip2 and it has this problems. When i switched to normal bzip2 everything works fine.
good luck |
|
| Back to top |
|
|
|
Portage & Programming
