[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: wget for sarge update



On Sat, Oct 02, 2004 at 02:59:13PM +0200, Noèl Köthe wrote:
> Hello,
> 
> wget <= 1.9.1-4 (which is in sarge and frozen) had a security problem
> (#261755) which is fixed in -6 and -7 (right now in incoming). -5 had
> the first fixing patch but was not multibyte aware (#271931).
> Jan Minar <jjminar fastmail.fm> wrote the fixing patches (Thanks!).
> Upstream author doesn't respond to this and other things/mails since
> weeks so right now he is MIA.:(

> If you (release and security team) don't have any objections I will
> upload -7 to testing-proposed-updates in the next 2 days.

You might want to fix the build dependencies first.

dpkg-buildpackage: host architecture is s390
 /usr/bin/fakeroot debian/rules clean
debian/rules:11: /usr/share/dpatch/dpatch.make: No such file or directory
make: *** No rule to make target `/usr/share/dpatch/dpatch.make'.  Stop.

(http://buildd.debian.org/fetch.php?&pkg=wget&ver=1.9.1-7&arch=s390&stamp=1096740331&file=log&as=raw)

I'm not going to accept an upload to t-p-u that makes off-point,
substantial changes to the build rules.  Pushing this from unstable to
testing might be doable, but being free of severity: serious FTBFS bugs
is an obvious prerequisite.

Moving patches around like you have here also makes it more difficult to
use tools like interdiff and debdiff to review the changes.  This is an
absolute non-starter for t-p-u; for unstable->testing propagation, it
means I'm likely to let the source age in unstable for a bit before
pushing it in, since I don't have the time to fully review the changes
directly.

-- 
Steve Langasek
postmodern programmer

Attachment: signature.asc
Description: Digital signature


Reply to: