Hello wget developers,
As a long time satisfied user of wget on various platforms I tried out the
announced new betas (on a Linux system). As one test I downloaded the new
beta2 of today with the just compiled beta1 with the following results:
wget.18
Well.. I've sent email to [EMAIL PROTECTED] that didn't work.
I've emailed people here that are top level folks on the list that didn't
work. So... please
just take me off the list the old fashioned way.
Thanks -
Matt
Hiroshi Takekawa [EMAIL PROTECTED] writes:
Please pay attention to po files before the release of wget 1.8.
I'm not sure how that can be done. Strings do change at the last
moment, and it's impossible to wait for all the translators.
I would appreciate if you (or the one in charge) would
Jochen Roderburg [EMAIL PROTECTED] writes:
wget.18 ftp://gnjilux.srk.fer.hr/pub/unix/util/wget/.betas/wget-1.8-beta2.tar.gz
--08:47:50--
ftp://gnjilux.srk.fer.hr/pub/unix/util/wget/.betas/wget-1.8-beta2.tar.gz
= `wget-1.8-beta2.tar.gz/.listing'
Jochen Roderburg [EMAIL PROTECTED] writes:
I think the 'timestamping' is the point, because without that I see
that no .listing file is used at all, and the problem doesn't
appear.
Yes, with the timestamping turned on, I was able to repeat the
problem. This patch should fix it:
2001-12-02
Please pay attention to po files before the release of wget 1.8.
I'm not sure how that can be done. Strings do change at the last
moment, and it's impossible to wait for all the translators.
(snip)
Fair enough. Well... I wonder you could just freeze them before a
release and wait, say, a
