For laptop users in particular, the first run of apt-daily.service each day
is likely to occur on boot or after resume from suspend. Such a run will
fail to update package lists due to a DNS failure because of #834414. The
problem is made worse, however, because of apt's current exit code
Julian Andres Klode:
> On Sat, Jan 24, 2015 at 04:50:04PM +, Patrick Schleizer wrote:
>> Package: apt
>> Severity: important
>>
>> When "apt-get update" fails the program exits with a 0 status.
>> It would be useful if it exited with a non-zero status in that case
>> (or if there were a switch
On Sat, Jan 24, 2015 at 04:50:04PM +, Patrick Schleizer wrote:
> Package: apt
> Severity: important
>
> When "apt-get update" fails the program exits with a 0 status.
> It would be useful if it exited with a non-zero status in that case
> (or if there were a switch to tell it to do so).
I
Package: apt
Severity: important
When apt-get update fails the program exits with a 0 status.
It would be useful if it exited with a non-zero status in that case
(or if there were a switch to tell it to do so).
This is similar to bug 41053 [1] from 1999, that says it's fixed, but it
doesn't say
4 matches
Mail list logo
