This bug was fixed in the package apt - 1.2.25

---------------
apt (1.2.25) xenial; urgency=medium

  * Microrelease covering 1.4.7 (LP: #1702326) and 1.4.8

  [ Robert Luberda ]
  * fix a "critical" typo in old changelog entry (Closes: 866358)

  [ David Kalnischkies ]
  * use port from SRV record instead of initial port
  * don't ask an uninit _system for supported archs (LP: #1613184)

  [ Julian Andres Klode ]
  * Reset failure reason when connection was successful
  * http: A response with Content-Length: 0 has no content
  * apt-daily: Pull in network-online.target in service, not timer
    (LP: #1716973)

  [ Balint Reczey ]
  * Gracefully terminate process when stopping apt-daily-upgrade (LP: #1690980)

 -- Julian Andres Klode <juli...@ubuntu.com>  Tue, 26 Sep 2017 16:14:54
+0200

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
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 Released
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

_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to     : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

Reply via email to