43270 – emerge linux-headers doesn't unmerge older headers

Bug 43270 - emerge linux-headers doesn't unmerge older headers

Summary: emerge linux-headers doesn't unmerge older headers

Status:	RESOLVED INVALID

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	New packages (show other bugs)
Hardware:	All Linux

Importance:	High normal (vote)
Assignee:	x86-kernel@gentoo.org (DEPRECATED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2004-02-29 04:15 UTC by Sven
Modified:	2004-02-29 10:07 UTC (History)
CC List:	0 users

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Sven 2004-02-29 04:15:17 UTC

hi,

i had linux-headers-2.4.19 installed, and emerged linux-headers-2.4.21.
i noticed, that both versions were listes when i do "qpkg --dups -v".
i took a look at the ebuilds and both say SLOT="0".

Reproducible: Always
Steps to Reproduce:
1. emerge linux-headers-2.4.19
2. emerge linux-headers-2.4.21
3. qpkg --dups -v

Comment 1 Tim Yamin (RETIRED) gentoo-dev

2004-02-29 10:07:40 UTC

Portage does not read the ebuild when it decides SLOTs and what packages should be unmerged: it reads the database entry in /var/db/pkg/${category}/${ebuild}-${version}/SLOT which used to be set to ${KV} for 2.4.19; giving it a slot of 2.4.19. This was resolved a while ago: http://www.gentoo.org/cgi-bin/viewcvs.cgi/sys-kernel/linux-headers/linux-headers-2.4.19.ebuild?r1=1.19&r2=1.20 so it seems that you just had the "SLOT=${KV}" version installed.

Thanks.