Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 6605 - emerge clean on cdrtools: Wrong version?
Summary: emerge clean on cdrtools: Wrong version?
Status: RESOLVED FIXED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Unclassified (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Seemant Kulleen (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on: 6425
Blocks:
  Show dependency tree
 
Reported: 2002-08-16 14:50 UTC by Klaus Kusche
Modified: 2011-10-30 22:21 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 Klaus Kusche 2002-08-16 14:50:25 UTC
I just emerged cdrtools 1.11.29, had 1.11.28 before. Everything went fine.

Then I tried emerge --pretend clean, and for cdrtools, it says:
selected: 1.11.29
protected: 1.11.28
(so it wants to delete the new version and keep the old one!)
prune instead of clean does the same.

I grepped the portage trees for dependencies on 1.11.28, but as far as I can
tell, there are none.

What's going on?
How can I find out what is protecting 1.11.28?
How do I overcome the situation?
Comment 1 Proteus 2002-08-16 17:39:54 UTC
Cdrtools version 1.11.29 has been masked due to bug #6425.
Comment 2 SpanKY gentoo-dev 2002-08-16 17:52:52 UTC
see Bug 6425 and Bug 3903

*** This bug has been marked as a duplicate of 3903 ***
Comment 3 Klaus Kusche 2002-08-17 03:19:06 UTC
Please undo the masking of 1.11.29:
a) Bug 6425 happens for *both* 1.11.28 and 1.11.29. There is no reason for
having 1.11.29 masked and 1.11.28 not masked.
b) I have kernel krypto/gentoo 2.4.19r7 as described in bug 6425, and I'm *not*
affected by the bug.
Comment 4 Seemant Kulleen (RETIRED) gentoo-dev 2002-08-18 01:22:07 UTC
apparently it's been unmasked already.
Comment 5 Klaus Kusche 2002-08-20 05:47:39 UTC
Something is still broken.

Just rsync'ed the portage tree (cdrtools definitely not masked in current tree),
emerged a new portage (2.0.28), tried "emerge --pretend clean", same effect:

It want's to delete 1.11.29 and keep 1.11.28!
Comment 6 Klaus Kusche 2002-08-22 05:55:03 UTC
Installing 1.11.30 did the trick: 28 and 29 both got cleaned afterwards.