
I don't know if this has come up yet, I don't recall it, but if it has, sorry. Debian's security updates for sarge are broken, http://www.infodrom.org/~joey/log/?200506142140 and the mailing list, http://lists.debian.org/debian-security/2005/06/msg00142.html just a heads up for those running sarge in production. Mike

On 05/07/05, Michael Honeyfield <mhoneyfield(a)orcon.net.nz> wrote:
I don't know if this has come up yet, I don't recall it, but if it has, sorry.
Debian's security updates for sarge are broken,
This was fixed fairly quickly and new version was released within a couple of days of original release. You should check your media or version is 3.1r0a if you're using media or distributing. Ian

Ian McDonald wrote:
On 05/07/05, Michael Honeyfield <mhoneyfield(a)orcon.net.nz> wrote:
I don't know if this has come up yet, I don't recall it, but if it has, sorry.
Debian's security updates for sarge are broken,
This was fixed fairly quickly and new version was released within a couple of days of original release. You should check your media or version is 3.1r0a if you're using media or distributing.
The fix was not fairly quickly as it is not yet resolved. Media coverage as of today: http://distrowatch.com/weekly.php?issue=20050704#2 Also, did you review the mailing list link I provided? The first email about this issue on the debian-security list was posted Mon, 27 Jun 2005, a long time *after* sarge was released. To also quote the first url I gave: "At the time of the release, security.debian.org broke, since the suites stable/testing on the security host did not match the ones on the main archive. In fact, trying to release a security update before the sarge release resulted in a crashed katie program and a half-baked archive. ... So, it looks like we'll be without security updates for quite a while." That was dated 14/06/05, sarge was released a week early, with fisrt "issue" being corrected inside a day or two. So, no, its not my media ;) Thanks Mike
participants (2)
-
Ian McDonald
-
Michael Honeyfield