[Bug 1716973] Re: Don't pull in network-online.target in apt-daily.timer

Timo Aaltonen tjaalton at ubuntu.com
Fri Sep 29 13:14:18 UTC 2017


Hello Julian, or anyone else affected,

Accepted apt into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.4.8 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. In either case, details of your testing
will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: apt (Ubuntu Zesty)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-zesty

** Changed in: apt (Ubuntu Xenial)
       Status: Triaged => Fix Committed

** Tags added: verification-needed-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1716973

Title:
  Don't pull in network-online.target in apt-daily.timer

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  apt-daily.timer is enabled on every boot and pulls in network-online.target via Wants and After. While nothing has an After=apt-daily.timer (or rather an After=timers.target) and this should thus not impact boot performance, the rc-local.service specifies an After=network-online.target and the login stuff (getty, gdm, etc) is ordered After=rc-local, thus severely increasing the time to login if nothing else pulls in network-online (like an LSB script).

  This works around the problem on most boots, the problem will only
  occur if the timer would have elapsed while the machine was off.

  [Test case]
  Well, the change is fairly obvious. Actually testing that is pointless, and depending on the system configuration, network-online.target might be pulled in by something else. So just look at the file and check that the network-online.target dependency moved to the service.

  [Regression potential]
  Literally none. We just move the dependency to the service which actually needs it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1716973/+subscriptions



More information about the foundations-bugs mailing list