-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
After FC3 final has been released several updates have been pushed out to the mirrors and yet again we haven't seen any announcement for some of them. Some announcements for FC2 and even FC1 are still missing too:
FC1: gaim-0.77-2.FC1 gaim-0.80-1.FC1 gaim-0.81-1.FC1 postfix-2.0.16-1 recode-3.6-12.0
FC2: devhelp-0.9.1-0.2.2 epiphany-1.2.7-0.2.0 epiphany-1.2.7-0.2.2 fam-2.6.10-9.FC2 gaim-0.77-7 gaim-0.80-1.FC2 gaim-0.81-1.FC2 gaim-1.0.2-0.FC2 gnome-session-2.6.0-4 kernel-2.6.9-1.3_FC2 libxml-1.8.17-10.1.2 man-1.5o1-6 mozilla-1.7.2-0.2.0 mozilla-1.7.3-0.2.0 nfs-utils-1.0.6-22 ruby-1.8.1-5 slang-1.4.9-12 xinitrc-3.41-1 xorg-x11-6.7.0-9
FC3: aspell-bg-0.50-7 bash-3.0-18 brltty-3.2-6 cvs-1.11.17-4 firefox-1.0-2.fc3 gamin-0.0.17-1.FC3 iptables-1.2.11-3.1.FC3 kernel-2.6.9-1.678_FC3 kernel-2.6.9-1.681_FC3 libselinux-1.19.1-3 libxml-1.8.17-12 man-1.5o1-7 man-pages-pl-0.23-4 policycoreutils-1.18.1-2 postfix-2.1.5-2.3.FC3 rhgb-0.15.1-1.FC3 shadow-utils-4.0.3-38 shadow-utils-4.0.3-40 slang-1.4.9-7 slang-1.4.9-13 udev-039-10.FC3.2 words-3.0-2
Besides this there were twice two announcements that had the same id:
FEDORA-2004-378: kdelibs-3.3.1-2.2 for FC3 kdegraphics-3.3.1-2.1 for FC3
FEDORA-2004-407: libxml2-2.6.16-3 for FC3 libxml2-2.6.16-2 for FC2
Best regards.
- -- Dipl.-Ing. (FH) Bernd Bartmann Bernd.Bartmann@sohanet.de I.S. Security and Network Engineer SoHaNet Technology GmbH / Kaiserin-Augusta-Allee 10-11 / 10553 Berlin Fon: +49 30 214783-44 / Fax: +49 30 214783-46
On Mon, 22 Nov 2004 23:14:54 +0100, Bernd Bartmann wrote:
After FC3 final has been released several updates have been pushed out to the mirrors and yet again we haven't seen any announcement for some of them. Some announcements for FC2 and even FC1 are still missing too:
as this list points out, this is a continuing process problem. The only garunteed engineered solution to prevent this from happening is to make filing an annoucement text a blocking requirement for submitting an package as an update. But that will require a level of automation and red-tape that I don't think anyone inside the fenceline really wants to or has time to implement.
It's my understanding that the primary reason these annoucements aren't making it out the door is that individual maintainers are simply forgetting to create an annoucement text and submit it to the annouce list.
As a compromise, i would like to suggest that a autobug filer script be created that would file a bugreport against a component if an update goes unannouced for 3+ days in an effort to make the individual package maintainer aware of the problem in a timely fashion. While the summary reports to the public lists are somewhat useful.... finding a way to poke the individual package maintainers more directly seems to be needed. All the information needed should be available from the master mirror.. maybe just parsing the repository metadata would be enough.
And I realize the existance of security issues greatly complicates when and how information is released. I'm trying to come up with discreet solution that makes sure annoucements don't fall through the cracks and are completely forgotten.
thoughts? is a script designed to automate filing missing update announcement bugs a realistic and useful way forward?
-jef