| Summary: | schroot is in updates_testing but there is no update candidate bug report assigned to qa-bugs@ml.mageia.org | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Samuel Verschelde <stormi-mageia> |
| Component: | RPM Packages | Assignee: | Philippe Makowski <makowski.mageia> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | 1 | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | schroot | CVE: | |
| Status comment: | |||
|
Description
Samuel Verschelde
2011-07-29 23:53:04 CEST
hum yes, no initial bug report, so no bug report to reassign to qa-bugs If I look at Debian, in fact it should go into backport and if we put it in testing (as Fedora did), it have to be rebuild to take care of the updates policy about release and subrel but now there is even a version 1.4.23 so, what to do ? I depends : - if 1.4.22 (or 1.4.23) is a bugfix only release then providing an update could be a good idea - otherwise it's a backport and we should remove it from updates_testing and wait for the backports media to open update build and bug report done #2370 Status:
NEW =>
RESOLVED |