Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 42343 - Portage: emerge crash during unmerge
Summary: Portage: emerge crash during unmerge
Status: RESOLVED FIXED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core (show other bugs)
Hardware: All All
: High normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-21 02:19 UTC by Camille Huot (RETIRED)
Modified: 2005-08-07 18:21 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Camille Huot (RETIRED) gentoo-dev 2004-02-21 02:19:17 UTC
I use  "sys-apps/portage-2.0.50-r1" and emerge is crashing when I unmerge some old apps that were prelinked one day:

>>> Unmerging net-irc/bitchx-1.0.19-r5...
<<<        obj /usr/share/man/man1/BitchX.1.gz
<<<        obj /usr/share/doc/bitchx-1.0.19-r5/watch.gz
<<<        obj /usr/share/doc/bitchx-1.0.19-r5/tcl-ideas.gz
[snip]
<<<        obj /usr/lib/bx/help/4_Misc/set/banner.bz2
<<<        obj /usr/lib/bx/help/4_Misc/set/auto_whowas.bz2
<<<        obj /usr/lib/bx/help/4_Misc/set/auto_unmark_away.bz2
Traceback (most recent call last):
  File "/usr/bin/emerge", line 2366, in ?
    if 1==unmerge(myaction, myfiles):
  File "/usr/bin/emerge", line 1852, in unmerge
    retval=portage.unmerge(mysplit[0],mysplit[1],portage.root,mysettings,unmerge_action not in ["clean","prune"])
  File "/usr/lib/portage/pym/portage.py", line 2496, in unmerge
    mylink.unmerge(trimworld=mytrimworld,cleanup=1)
  File "/usr/lib/portage/pym/portage.py", line 5309, in unmerge
    mymd5=perform_md5(obj, calc_prelink=1)
  File "/usr/lib/portage/pym/portage.py", line 2487, in perform_md5
    return perform_checksum(x, calc_prelink)[0]
  File "/usr/lib/portage/pym/portage.py", line 349, in perform_checksum
    retval = fchksum.fmd5t(prelink_tmpfile)
IOError: [Errno 2] No such file or directory: '/tmp/portage-prelink.tmp'

Then I redo the unmerge and it finishes fine.

[I think this is a backward compatibility issue, but you should know that better than me]
Comment 1 Duke 2004-03-01 17:55:49 UTC
I got a similar error while updating jpilot - during the unmerge of the older package:

<<<        dir /usr/share/gnome/apps/Applications
<<<        dir /usr/doc/jpilot-0.99.5/icons
<<<        dir /usr/doc/jpilot-0.99.5
mydirs[5] /usr/share/doc/jpilot-0.99.5
obj /usr/share/doc/jpilot-0.99.5
objld None
Traceback (most recent call last):
  File "/usr/bin/emerge", line 2599, in ?
    mydepgraph.merge(mydepgraph.altlist())
  File "/usr/bin/emerge", line 1600, in merge
    retval=unmerge("clean", [xsplit[0]])
  File "/usr/bin/emerge", line 1852, in unmerge
    retval=portage.unmerge(mysplit[0],mysplit[1],portage.root,mysettings,unmerge_action not in ["clean","prune"])
  File "/usr/lib/portage/pym/portage.py", line 2496, in unmerge
    mylink.unmerge(trimworld=mytrimworld,cleanup=1)
  File "/usr/lib/portage/pym/portage.py", line 5377, in unmerge
    if len(objld)>0:
TypeError: len() of unsized object


I tried manually cleaning jpilot (emerge -c jpilot), and it worked without error.


Here is my emerge info:

Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.4.22)
=================================================================
System uname: 2.4.22 i686 AMD Athlon(tm) processor
Gentoo Base System version 1.4.3.13
distcc 2.12.1 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled]
Autoconf: sys-devel/autoconf-2.58-r1
Automake: sys-devel/automake-1.7.7
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-march=athlon-tbird -O3 -pipe"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/bind /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-march=athlon-tbird -O3 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache distcc sandbox"
GENTOO_MIRRORS="http://gentoo.mirrors.pair.com/"
MAKEOPTS="-j4"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="3dnow X apache apache2 berkdb crypt foomaticdb gd gdbm gif gpm gtk2 imap jpeg libwww mmx mysql ncurses odbc pam pdflib perl png postgres python readline snmp spell ssl tcltk tcpd tiff truetype x86 xml xml2 zlib"

Comment 2 Howard B. Golden 2004-07-27 13:15:31 UTC
Re: Comment #1: I believe that this crash (in comment #1) is a duplicate of bug 25339.

Note: I don't see how the bug in Comment #1 is "similar" to the first bug Camille is reporting here, so I'm _not_ saying Camille's bug is a duplicate of bug 25339.
Comment 3 Camille Huot (RETIRED) gentoo-dev 2004-08-24 09:33:53 UTC
bump. bug still here with portage-2.0.50-r9.
Comment 4 Brian Harring (RETIRED) gentoo-dev 2004-08-24 11:23:19 UTC
Anyone duplicate this on 2.0.51_pre*?
Comment 5 Peter S. Mazinger 2004-10-26 06:59:09 UTC
can duplicate w/ portage-2.0.51-r2 unmerging gcc-3.4.2-r2 (gcc-3.3.4-r1 still installed)
if I rename the /usr/lib/gcc-lib/i386-pc-linux-uclibc/3.4.2 dir to something else, then it can be unmerged, so it seems some checksum fails in this dir (yes, it is an uclibc based system)
before I rebuilt python, python-fcksum and portage (all from stable) w/ gcc-3.3.4-r1 to be sure that they are ok.
Comment 6 Jason Stubbs (RETIRED) gentoo-dev 2004-10-28 07:44:38 UTC
Can you post the traceback you get with portage-2.0.51-r2 please?
Comment 7 Alec Warner (RETIRED) archtester gentoo-dev Security 2005-08-06 09:01:36 UTC
Can anyone duplicate on stable ( 2.0.51.22-r2 ).  I doubt this was fixed, but 
who knows ;)  A traceback would also be wonderful.
Comment 8 Zac Medico gentoo-dev 2005-08-06 13:53:55 UTC
The traceback in comment #1 is supposed to be fixed since portage-2.0.51 (see
bug 42228) and the traceback in comment #2 is supposed to be fixed since
2.0.51-r2 (see bug 25339).
Comment 9 Alec Warner (RETIRED) archtester gentoo-dev Security 2005-08-07 18:21:38 UTC
Bug has been fixed and released in stable portages on or before 2.0.51-r2 ( the 
latest release of the two tracebacks ).  Please re-open if you can reproduce on 
a stable version.