On 07.01.2017 21:24, Julian Andres Klode wrote: > On Sat, Jan 07, 2017 at 09:15:15PM +0100, Sven Hartge wrote: >> On Mon, 26 Dec 2016 14:40:05 +0100 (CET) <34tg535@tutanota.com> wrote: >> >>> I use Debian 8 64bit with GNOME installed with standard install >>> procedure from netinstall and using tasksel. This occured to me the >>> second time. First time was a year ago, I reinstalled Debian then and >>> a year after this happens again. Both occurences were on Debian 8, >>> stable at the time. >> >> I have seen this as well and know under which circumstances this happens: >> >> a) backports repository is enabled in source.list (obviously) >> b) "apt update" is run and all normal repositories fail to download or >> are invalid >> >> When this happens, apt will happily upgrade all packages where a >> backported version exists to that version. > > This should not happen. The old repository state should be used, and thus > the pinning should not change. That's what I thought as well. > That said, maybe that only works right in 1.1 and newer, I don't > really know. I have definitely seen this in Jessie, maybe even Wheezy (memory a bit fuzzy in that regard). I run apticron on all our servers (~250) and it happened about once a month that one (a different one every time) of the server prompted to upgrade all packages to their backports-version. But after switching from httpredir.debian.org to deb.debian.org this problem did not occur again, so far at least. But there is absolutely something problematic with the version in Jessie where it is possible to trigger the behavior from this bug report. Grüße, Sven.
Attachment:
signature.asc
Description: OpenPGP digital signature