Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 14748 - Emerging twice problem
Summary: Emerging twice problem
Status: RESOLVED INVALID
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Unclassified (show other bugs)
Hardware: All All
: High critical (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-01-29 14:56 UTC by Pierre-Henri Jondot
Modified: 2011-10-30 22:19 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 Pierre-Henri Jondot 2003-01-29 14:56:21 UTC
I accidentally emerged twice some packages but portage did not make a good job overwriting the previous installation... The result is the missing of important files or entire directories (that pretend to be there according to /var/db/pkg/.../CONTENTS file).

I've seen this happening for two packages (well, I guess the majority of ebuilds might be affected, as they are the only two packages I accidentally emerged twice in a row...)

xemacs-21.4.12 (can't be verbose about the files that did disappear or not, but clearly there must be a lot of things missing...)
scilab-2.6 (for this one : emerging it twice make the directories /usr/lib/scilab-2.6/bin and utils simply disappear)

I had to properly unmerge these before emerging then again in order to have a working installaion.

The portage I used is :

2.0.46-r9 (from a fresh 1.4_rc2 install)

It might be that the bug I'm describing might have been fixed by now, but looking at the Changelog in the cvs, didn't read anything relevant.

I suspect a cleaning made by portage AFTER the installation of the relevant files to be the culprit...

Pierre-Henri.
Comment 1 Pierre-Henri Jondot 2003-01-29 15:03:55 UTC
Oups...I was wrong about the portage version : 

I used 2.0.44, not 2.0.46-r9.

Comment 2 Nicholas Jones (RETIRED) gentoo-dev 2003-01-29 19:35:43 UTC
I'd assume this isn't a problem then?
Reopen if it still is.