Re: Bug#417622: NTFS-3g way too old, can cause data corrumption in rare conditions

Steve Langasek wrote: > Michael, > > Please keep the Cc: list intact when replying. > > On Tue, Apr 03, 2007 at 11:01:00PM +0200, Michael Fritscher wrote: >>> From my POV, the question is not whether ntfs-3g 1.0.0 should be included >>> in >>> etch (it won't be), but whether the risk of this data

Re: w3mmee still needed?

Moritz Muehlenhoff wrote: > Do we need to include w3mmee (a forked, old copy of w3m with multi-byte > support) in Etch or can w3m handle these nowadays? (w3mee in Etch is > from 2002) Weird, upstream's [1] latest release was Sep 2006 but there's no "newer upstream available" wishlist bug against w

Re: BIND 8 deprecation for the release notes

Roberto C. Sanchez wrote: > That got me wondering and it appears that Etch will ship with Apache > 1.3.34? Why? It is considered a legacy release by ASF? Is the Debian > security team really willing to support it for another 2-3 years? > I'm sure that there are other examples. (Funnily enough,

Re: aiccu is now under 3-clause BSD license

Steve Langasek wrote: > On Mon, Jan 08, 2007 at 11:01:35AM +1100, Paul TBBle Hampson wrote: > >> OK. As per [1] in the 388759 buglog and the upstream >> website [2] the 2007.01.07 release of aiccu is now >> under the 3-clause BSD license. ... >> CC'd to debian-release to see if the Etch-response

FreeRADIUS 1.0.2-4 security fix upload for sponsorship

Horms, Here's FreeRADIUS 1.0.2-4 for sponsorship. It's a set of security fixes SQL driver, one a two-byte buffer overflow, and one an SQL injection attack. I've already discussed this on debian-release, although I am CCing this there in case the release team feels that only the SQL injection atta