Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 281884 - Cannot emerge packages with sys-libs/i6fork-1.0.1
Summary: Cannot emerge packages with sys-libs/i6fork-1.0.1
Status: RESOLVED FIXED
Alias: None
Product: Gentoo/Alt
Classification: Unclassified
Component: Prefix Support (show other bugs)
Hardware: All Interix
: High major
Assignee: Gentoo Prefix
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-18 09:41 UTC by Christian Faulhammer (RETIRED)
Modified: 2009-08-20 08:24 UTC (History)
0 users

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 Christian Faulhammer (RETIRED) gentoo-dev 2009-08-18 09:41:18 UTC
This is what I get for every single program in different phases (depending on package and if I am on an X terminal or not) since the upgrade to above version.  Reproducable in a virtual machine (yes, the one from LinuxTag :) and on a "normal" system, both with Windows Server 2008 and Interix 6.0

 * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * The 'postrm' phase of the 'media-libs/libpng-1.2.37' package has failed
 * with exit value 35584.
 *
 * The problem occurred while executing the ebuild file named
 * 'libpng-1.2.37.ebuild' located in the '/opt/gentoo/var/db/pkg/media-
 * libs/libpng-1.2.37' 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()
Comment 1 Markus Duft (RETIRED) gentoo-dev 2009-08-18 16:18:18 UTC
oh man - you just hit a bug i've been hunting for days now.

1) do you have a snapshot you can revert to?
   if yes, revert, sync, and do:
    emerge -v1 i6fork
     (close all shells, and re-open them)
    emerge -v1 bash
     (close all shells again, and re-open)
    emerge -vuD system world (or whatever)

   if no... phew... let's see...
    check wether there is a /opt/gentoo/bin/bash.removedbyportage* file.
     if yes move it back to /opt/gentoo/bin/bash, overwrite the existing.
    comment out the LD_PRELOAD= in /opt/gentoo/etc/profile.env and
     /opt/gentoo/etc/env.d/00i6fork.
     (close all shells and re-open)
    (proceed as described above when reverting to the snapshot...)

hope that works... further help would require a hands-on i guess ;)

damn - i knew this bug would hunt me down.... :(

btw. portage is not the bad one - i6fork is the one having a problem. but re-installing is not that easy since it is more or less viral - it infects your environment through LD_PRELOAD, and makes sure you cannot unset it by adding itself back on every exec - thats to fix the totally broken fork in interix 6. additional to the LD_PRELOAD, bash 4 directly links to the library - just to make sure and also catch the login shell, where LD_PRELOAD is not yet set.

although it is technically fixed, i'll leave this bug open, until you made it :)
Comment 2 Christian Faulhammer (RETIRED) gentoo-dev 2009-08-18 21:17:41 UTC
(In reply to comment #1)
> oh man - you just hit a bug i've been hunting for days now.

 I hit it some time ago already, but had no time to work on it.>    if no... phew... let's see...
>     check wether there is a /opt/gentoo/bin/bash.removedbyportage* file.
>      if yes move it back to /opt/gentoo/bin/bash, overwrite the existing.
>     comment out the LD_PRELOAD= in /opt/gentoo/etc/profile.env and
>      /opt/gentoo/etc/env.d/00i6fork.
>      (close all shells and re-open)
>     (proceed as described above when reverting to the snapshot...)

 Works!  Thanks.

> hope that works... further help would require a hands-on i guess ;)
> 
> damn - i knew this bug would hunt me down.... :(
> 
> btw. portage is not the bad one - i6fork is the one having a problem. but
> re-installing is not that easy since it is more or less viral - it infects your
> environment through LD_PRELOAD, and makes sure you cannot unset it by adding
> itself back on every exec - thats to fix the totally broken fork in interix 6.
> additional to the LD_PRELOAD, bash 4 directly links to the library - just to
> make sure and also catch the login shell, where LD_PRELOAD is not yet set.
> 
> although it is technically fixed, i'll leave this bug open, until you made it
> :)
> 

Comment 3 Christian Faulhammer (RETIRED) gentoo-dev 2009-08-19 07:28:53 UTC
You should add the i6fork thing to the documentation, so people know early on what this library is about.