Bug 141351
| Summary: | libxml2 updates for FC2 and FC3 have the same advisory id | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bernd Bartmann <bernd.bartmann> |
| Component: | libxml2 | Assignee: | Daniel Veillard <veillard> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-11-30 17:29:43 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
It is the same code base. The number is 407 for DC3 and 408 for FC3. It's a stupid typo, it's not fixable, it should be harmless. Daniel I guess this should read 407 is for FC2 and 408 is for FC3? ouch :-) Yes How much of a pain is it ? I don't really see the need to do something. I forgot to upgrade the update number as I generated the second announcement. Daniel This is certainly not a major problem. I'm maintaining my own database of all the update announcements and just want to make sure that everything is correct. For me what's still lacking is a central place where all these annoucemnet are kept (like e.g. https://rhn.redhat.com/errata/rhel3es-errata.html for RHES3). There are still several updates that already appeared on the download mirrors but were never announced on fedora-announce-list. I try to get more attention from the package maintainers inside Red Hat on this problem so I've created some tracker bugs on missing update announcements: FC1: 141259 FC2: 141258 FC3: 141256 What I'd really like to see is a central final instance (person) that does some simple QA (md5sum checking, testing if update install is successful, id checking) before the announcements go out to fedora-announce-list. Also all announcements should be gpg signed using a central key from Fedora or Red Hat. I've already posted an RFE on this topic to fedora-devel-list when FC1 came out. Your help to get this topic dicussed inside Red Hat would be much appreciated. But I think Bugzilla is the wrong for a discussion. So please make any comments as answers to my "Missing update announcement" thread on fedor-devel-list. Anyway, thanks Daniel for the missing information. |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0 Description of problem: The updates libxml2-2.6.16-3 for FC3 and libxml2-2.6.16-2 for FC2 share the same advisory id FEDORA-2004-407. Every other FC update had a separate advisory id if it was released for more than one FC version. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. look at the two FEDORA-2004-407 update announcements 2. 3. Additional info: