Bug 3285 - if a package was renamed it appers twice on the maintdb list
Summary: if a package was renamed it appers twice on the maintdb list
Status: RESOLVED INVALID
Alias: None
Product: Infrastructure
Classification: Unclassified
Component: BuildSystem (show other bugs)
Version: unspecified
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Sysadmin Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-07 21:16 CET by Kamil Rytarowski
Modified: 2014-05-08 18:07 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:

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

Description Kamil Rytarowski 2011-11-07 21:16:42 CET 
Description of problem:
if a package was renamed it appers twice on the maintdb list.
Examples:
Eterm obgr_seneca eterm anssi
eterm obsoletes Eterm

FileRunner nobody filerunner wally
filerunner obsoletes FileRunner

Steps to reproduce:
Check the list on http://pkgsubmit.mageia.org/data/maintdb.txt
Comment 1 Nicolas Vigier 2011-11-19 15:24:21 CET 
Yes, we should have a script to compare list of packages in cauldron and maintdb, to remove old packages.

But as maintdb is also used for stable distributions, maybe we should wait until no supported distribution provide the obsoleted package ?

CC: (none) => boklm

Comment 2 Marja Van Waes 2012-02-22 13:36:52 CET 
(In reply to comment #1)
> Yes, we should have a script to compare list of packages in cauldron and
> maintdb, to remove old packages.
> 
> But as maintdb is also used for stable distributions, maybe we should wait
> until no supported distribution provide the obsoleted package ?

Yes, please wait :)

CC: (none) => marja11

Comment 3 Nicolas Vigier 2013-09-21 16:24:18 CEST 
Actually it old one should not be removed automatically, as it can still be present in older releases.

Manual removal of packages from maintdb can be asked on sysadmin mailing list.

Status: NEW => RESOLVED
Resolution: (none) => INVALID

Nicolas Vigier 2014-05-08 18:07:28 CEST

CC: boklm => (none)
Note You need to log in before you can comment on or make changes to this bug.