[Aptitude-devel] Bug#619811: updates silently ignored

[Manuel A. Fernandez Montecelo]

2016-01-10 19:17 To Harald Dunkel:
>Control: tags -1 + moreinfo
>
>
>Hi Harri,
>
>2011-03-27 12:20 Harald Dunkel:
>>-----BEGIN PGP SIGNED MESSAGE-----
>>Hash: SHA1
>>
>>Package: aptitude
>>Version: 0.6.3-3.2
>>
>>My sources.list contained
>>
>>	deb http://mysite.de/debian unstable main contrib non-free
>>
>>The "contrib" and "non-free" repositories are not defined in
>>my package database. "aptitude update" didn't print an error message,
>>but silently fell back to an old Packages file.
>>
>>
>>Regards
>
>2013-07-14 09:32 Harald Dunkel:
>>Can you reproduce this?
>
>
>With 0.7.5, it seems that the errors are printed now (I don't know if
>they are the same or not, but I guess that they are equivalent for the
>purpose of this bug).  So it seems that the bug is not present now.
>
>Can you please confirm?
>
>
> # aptitude update
> Hit http://ftp.uk.debian.org/debian unstable InRelease
> Hit http://debug.mirrors.debian.org/debian-debug unstable-debug InRelease
> Hit http://ftp.uk.debian.org/debian experimental InRelease
> Get: 1 http://mysite.de/debian unstable InRelease
> Err http://mysite.de/debian unstable InRelease
> Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)
> Hit http://debug.mirrors.debian.org/debian-debug experimental-debug InRelease
> W: Failed to fetch http://mysite.de/debian/dists/unstable/InRelease: Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)
> E: Some index files failed to download. They have been ignored, or old ones used instead.

Probably relevant to this bug report, David Kalnischkies from APT's fame
told me about a similar bug report that:

  "629449 you can probably close. apt < 1.1 had this behaviour, >= 1.1
   should still cry loudly about the one broken repo, but update the
   others just fine"

Applied to this bug report, I guess that if you have several repos
enabled the "Packages" file would be different, as long as one of them
has been updated and (lib)apt cannot find any fault with it.


Cheers.
-- 
Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>