Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 279041 - portage does not discard messages from previous failed merges for the same package
Summary: portage does not discard messages from previous failed merges for the same pa...
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core (show other bugs)
Hardware: All All
: High normal (vote)
Assignee: Portage team
Keywords: InVCS
Depends on:
Blocks: 335925
  Show dependency tree
Reported: 2009-07-25 12:41 UTC by Fabian Groffen
Modified: 2010-09-22 04:13 UTC (History)
0 users

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


Note You need to log in before you can comment on or make changes to this bug.
Description Fabian Groffen gentoo-dev 2009-07-25 12:41:55 UTC
I frequently see packages failing.  Then when I fix them and reemerge the package, I end up e.g. like this:

>>> Completed installing ncftp-3.2.2-r1 into /Library/Gentoo/var/tmp/portage/net-ftp/ncftp-3.2.2-r1/image/Library/Gentoo/

ecompressdir: lzma  /Library/Gentoo/usr/share/man

>>> Installing (1 of 1) net-ftp/ncftp-3.2.2-r1
 * checking 29 files for package collisions
--- /Library/Gentoo/etc/
--- /Library/Gentoo/usr/
--- /Library/Gentoo/usr/bin/
>>> /Library/Gentoo/usr/bin/ncftp

>>> Recording net-ftp/ncftp in "world" favorites file...

 * Messages for package net-ftp/ncftp-3.2.2-r1:

 * ERROR: net-ftp/ncftp-3.2.2-r1 failed:
 *   econf failed
 * Call stack:
 *       42: <call src_compile>
 *             environment:2287: <call econf>
 *      538:                        die "econf failed"
 * If you need support, post the topmost build error, and the call stack if relevant.
>>> Auto-cleaning packages...

>>> No outdated packages were found on your system.

 * GNU info directory index is up-to-date.

Now this is confusing, as the merge went fine.  I'm not completely sure if it happens with emerge, alone.  For this case I first used "ebuild ... install" (which failed), and then used emerge for the same package.  It may be related to that, but I thought I observed the same when having a failing emerge on a normal Linux with Portage 2.2
Comment 1 Jeremy Olexa (darkside) (RETIRED) archtester gentoo-dev Security 2010-04-06 02:02:20 UTC
Portage is affected when ebuild <...> install fails and then emerge works (or if emerge fails in a different way, it is a different message)
Comment 3 Zac Medico gentoo-dev 2010-09-22 04:13:13 UTC
This is fixed in 2.1.9.