Hi,
On Thu, 12 Jan 2017 19:35:59 +0100
Matthias Bodenbinder <matth...@bodenbinder.de> wrote:
> Hi,
>
> I have a weird behaviour on one of my debian boxes. It is running Mint
> LMDE and the issue is the following:
>
> I have several additional sources defined: debian testing, debian
> backports, etc. I have defined priorities for the repos so that testing
> has prio 300 and does not replace the stable packages automatically.
> That works fine if I do an "apt-get update" followed by an "apt-get
> dist-upgrade". No issue.
>
> The issue only occurs directly after boot. Somehow there is an "apt-get
> update" excecuted during boot time and this is ignoring the repo
> priorities. If I do a "apt-get dist-upgrade" directly after boot it
> wants to upgrade all packages to the testing version ("1547 upgraded,
> 358 newly installed, 97 to remove and 36 not upgraded."). This is a
> mistake.
(...)
Just a shot in the dark:
maybe the apt-get update at boot time is done before a network connection
has been established? I noticed that this can lead to the exact behavior
you describe when pinning is in use. Apparently a bug in apt.
Regards
Michael
.-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-.
It would be illogical to kill without reason.
-- Spock, "Journey to Babel", stardate 3842.4
