Bug 19999 – emerge -f deletes temporary folder

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Bernd Wurst 2003-04-26 08:02:18 UTC]

I did emerge -u kde to install kde and all its dependencies.
After that, I thought it would be good to run emerge -fu kde in another console
(I did this often before with older Versions of portage) to reduce time needed
to fetch all the archives.
But emerge -f deleted and recreated the /var/tmp/... folder of the package that
was in build-process on the other console.
Why does emerge do this? I used to make emerge -f in another console and it
always worked well. Is it deprecated to fetch more archives while another
compiler is running? Is there a better way to save the time needed to fetch big
packages?

I use portage version 2.0.47-r10

Reproducible: Didn't try
Steps to Reproduce:

[Comment 1 Martin Holzer (RETIRED) 2003-04-26 11:17:48 UTC]

*** This bug has been marked as a duplicate of 1661 ***

[Comment 2 Hanno Böck 2003-04-26 13:17:50 UTC]

This is NOT a duplicate of 1661.
As Bernd said, it was working with previous versions of portage.
There is no reason for deleting the tmp-dir when doing emerge -f.

[Comment 3 SpanKY 2003-07-09 12:31:50 UTC]

*** Bug 22582 has been marked as a duplicate of this bug. ***

[Comment 4 SpanKY 2003-07-09 12:39:21 UTC]

*** Bug 23733 has been marked as a duplicate of this bug. ***

[Comment 5 SpanKY 2003-08-02 23:06:37 UTC]

Created attachment 15417 [details, diff]
emerge-make-fetch-non-angry.patch

prevent emerge from cleaning /var/tmp/portage/<pkg>/ if the user is running
with -f

[Comment 6 SpanKY 2003-08-21 23:27:33 UTC]

could someone add this to latest portage ?
the fix adds just 1 extra check to the if statement around cleaning the temp folder ... the check is just to see whether the user is running -f or not ...

[Comment 7 Nicholas Jones (RETIRED) 2003-08-25 12:44:30 UTC]

Fixed in cvs