5267 – many KDE ebuilds refer to kdeadmin-3.0-r1.ebuild

Bug 5267 - many KDE ebuilds refer to kdeadmin-3.0-r1.ebuild

Summary: many KDE ebuilds refer to kdeadmin-3.0-r1.ebuild

Status:	RESOLVED INVALID

Alias:	None

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

Importance:	High normal
Assignee:	Dan Armak (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2002-07-19 15:27 UTC by SpanKY
Modified:	2002-07-21 10:33 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 SpanKY gentoo-dev

2002-07-19 15:27:24 UTC

many KDE ebuilds have hardcoded the path to kdeadmin-3.0-r1.ebuild ...
this is bad cause when KDE gets upgraded, the older versions get punted, and the
file no longer exists ... i imagine not many people have seen this because not
everyone does `emerge --clean rsync` ... rather they just do `emerge rsync`
basically the trouble is:
PARENT="kde-base/kdeadmin/kdeadmin-3.0-r1.ebuild"

the ebuilds with this problem:
app-admin/kcmlinuz-0.0.0
app-admin/kcron-3.0
app-admin/ksysv-1.3.8
app-admin/kuser-1.0
app-admin/kwuftpd-0.2.0
app-admin/lilo-config-0.0.0
app-admin/secpolicy-0.0.1
app-arch/kdat-2.0.1
app-arch/kpackage-3.0

k thx dad

Comment 1 Dan Armak (RETIRED) gentoo-dev

2002-07-21 04:24:57 UTC

Al these ebuilds were removed from cvs some time ago. Please emerge sync --clean.

Comment 2 SpanKY gentoo-dev

2002-07-21 10:33:14 UTC

my bad, i swore i did an `emerge --clean rsync` to make sure this affected the 
latest verion