| Summary: | if a package was renamed it appers twice on the maintdb list | ||
|---|---|---|---|
| Product: | Infrastructure | Reporter: | Kamil Rytarowski <n54> |
| Component: | BuildSystem | Assignee: | Sysadmin Team <sysadmin-bugs> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | marja11, sysadmin-bugs |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Kamil Rytarowski
2011-11-07 21:16:42 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 (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 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
Nicolas Vigier
2014-05-08 18:07:28 CEST
CC:
boklm =>
(none) |