Patrick Schoenfeld wrote: > On Wed, Sep 23, 2009 at 04:53:13PM +0300, Eugene V. Lyubimkin wrote: >> Patrick Schoenfeld wrote: >>> Indeed. The second download is sucessful. Wouldn't it make sense to >>> not print a warning in this case? Because actually thats the most >>> common case (at least now). >>> >> Hm. This makes some sense, but. What if download failed not because de_DE >> didn't exist, but some download error? The warning in this case would be good >> to print. > > Hmm. Good point. Wouldn't it make sense to take the HTTP Response Code > into account, then? HTTP is not only source. It can be FTP, or file://, or maybe someone will write pet p2p download module for cupt. Too much guessings...
> Something like: > - File not found (404), but de_DE found => No warning > - Access forbidden (403) or any other response code, but de can be downloaded > => Warning > So, if you still insist you want this get fixed nevertheless, I will convert a bug to wishlist then. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer
signature.asc
Description: OpenPGP digital signature
