On Fri, 27 Jan 2017, Michael Lange wrote:
On Fri, 27 Jan 2017 07:00:19 +0100
Matthias Bodenbinder wrote:
I created that file with this line but it does not help. Still the same
odd pinning after boot.
So my problem might not be related to /etc/cron.daily/apt. I guess I
have to start searchin
On Fri, 27 Jan 2017, Matthias Bodenbinder wrote:
Am 25.01.2017 um 20:04 schrieb Michael Lange:
Hi,
On Wed, 25 Jan 2017 07:18:07 +0100
Matthias Bodenbinder wrote:
(...)
I do not have that file /etc/apt/apt.conf.d/02periodic. I put
/etc/cron.daily/apt back where it belongs and this morning th
On Fri, 27 Jan 2017 07:00:19 +0100
Matthias Bodenbinder wrote:
> I created that file with this line but it does not help. Still the same
> odd pinning after boot.
>
> So my problem might not be related to /etc/cron.daily/apt. I guess I
> have to start searching again :-(
Though the fact that
Am 25.01.2017 um 20:04 schrieb Michael Lange:
Hi,
On Wed, 25 Jan 2017 07:18:07 +0100
Matthias Bodenbinder wrote:
(...)
I do not have that file /etc/apt/apt.conf.d/02periodic. I put
/etc/cron.daily/apt back where it belongs and this morning the pinning
was screwed up again. This is really wei
Hi,
On Wed, 25 Jan 2017 07:18:07 +0100
Matthias Bodenbinder wrote:
(...)
>
> I do not have that file /etc/apt/apt.conf.d/02periodic. I put
> /etc/cron.daily/apt back where it belongs and this morning the pinning
> was screwed up again. This is really weird.
Then you could try to create the f
Am 23.01.2017 um 11:47 schrieb Michael Lange:
Hi,
On Mon, 23 Jan 2017 08:40:32 +0100
Matthias Bodenbinder wrote:
(...)Yes, this is exactly what happens on my PC. But it has no solution.
In the meantime I found a workaround. I moved /etc/cron.daily/apt out
of the way. It looks like this scrip
Hi,
On Mon, 23 Jan 2017 08:40:32 +0100
Matthias Bodenbinder wrote:
(...)Yes, this is exactly what happens on my PC. But it has no solution.
>
> In the meantime I found a workaround. I moved /etc/cron.daily/apt out
> of the way. It looks like this script is being executed during boot
> before th
Am 12.01.2017 um 20:31 schrieb Sven Hartge:
Matthias Bodenbinder wrote:
What is going wrong here? Any idea?
Possibly https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849382
Grüße,
Sven.
Yes, this is exactly what happens on my PC. But it has no solution.
In the meantime I found a workar
On Fri, 13 Jan 2017 10:16:06 +0100
Michael Lange wrote:
(...)
> Not sure, you might try to grep through the files in /etc/init
> and /etc/init.d if you find the one that calls apt-get update , then see
> which package it belongs to and consider removing that package (or maybe
> if possible config
Hi,
On Fri, 13 Jan 2017 09:16:50 +0100
Matthias Bodenbinder wrote:
(...)
> I gave it a try. I unplugged the network and did an apt-get update.
> This is throwing all the errors that the repos are not available. But
> in the end the next "apt-get dist-upgrade" indeed wants to update all
> package
On Friday 13 January 2017 03:16:50 Matthias Bodenbinder wrote:
> Am 12.01.2017 um 19:43 schrieb Michael Lange:
> > 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
Am 12.01.2017 um 19:43 schrieb Michael Lange:
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
Matthias Bodenbinder wrote:
> What is going wrong here? Any idea?
Possibly https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849382
Grüße,
Sven.
--
Sigmentation fault. Core dumped.
Hi,
On Thu, 12 Jan 2017 19:35:59 +0100
Matthias Bodenbinder 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 prior
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
15 matches
Mail list logo