-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Raphael Geissert wrote:
> Package: wget
> Version: 1.11.1-1
> Severity: important
> 
> A few days ago I updated to the latest version of the package and it silently 
> broke some data updating scripts.
> 
> wget is executed like this:
>> wget -N -O foo.db.new http://source.tld/foo.db
> 
> And since the latest version it throws the next message:
>> Cannot specify -r, -p or -N if -O is given.
>> Usage: wget [OPTION]... [URL]...
> But it is only sent to stdout, which prevented me from noticing the failure 
> via the cronjob emails.
> 
> It worked just fine in 1.11-1 and previous,

No, the change was introduced in 1.11. You probably mean 1.10.2.

But, in fact, it never "worked", it was just silently _allowed_.
Timestamping was never supported for -O.

> and I see this new 'behaviour' 
> broken. There should be no reason why -O and -N can't both be used at the 
> same time.

Because -O doesn't mean "use this filename", it means "redirect output
to this file", rather like the shell does (see the manpage).

This means the local timestamp will _always_ be "now", regardless of the
last time you'd previously run Wget (and the local file will also
already be empty: it's a redirection). So timestamping is utterly useless.

However, a case could be made that it's better to issue a warning that
the combination is nonsensical, rather than exit (on the other hand, the
error is a much better way to make it clear that -N and -O do not do
what the user expected it to). Also, the message should clearly go to
stderr, not to stdout.

- --
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer,
and GNU Wget Project Maintainer.
http://micah.cowan.name/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFH/qRm7M8hyUobTrERAm7YAJ4vi3Tin4hE9eZUSvFXdro3WxBkMgCfYUK/
vEqUFi1uCajVX4zD8UXDYBU=
=PlDO
-----END PGP SIGNATURE-----



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to