Bug#861889: apt: apt.systemd.daily runs before network comes up

[Julian Andres Klode <jak@debian.org>]

Control: reassign -1 systemd
Control: retitle -1 systemd: network-online.target remains active after resume
Control: affects -1 apt

On Sun, May 07, 2017 at 09:09:23PM +0200, Hendrik Tews wrote:
> 
> > Note that this only applies on boot. Resume does not work.
> 
> What do you mean with "Resume does not work"? I usually wake up
> my laptop from suspend or hibernate in the morning, then
> apt.systemd.daily runs before the network comes up. Now and then
> I reboot the system later, but then the time stamps prevent
> apt.system.daily from doing anything.

Once the network has been activated at boot, it is considered
active for the rest of the uptime, so services won't wait for
it when resuming the machine.

If the time stamps prevent apt from doing anything, then
apt ran successfully and all is well.

All in all, there's nothing to be done here on the APT
side, that's a bug (design decision?) in systemd.

> 
> > You could look at 
> >
> >  /var/lib/systemd/deb-systemd-helper-enabled/network-online.target.wants/
> >  /{usr/,}lib/systemd/system/network-online.target.wants/ 
> >  /etc/systemd/system/network-online.target.wants
> 
> I have the first and the last and they both contain files
> networking.service and NetworkManager-wait-online.service and I
> use NetworkManager.

Great, then everything works fine.
-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev
                  |  Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline').  Thank you.