[Group.of.nepali.translators] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to

2019-04-25 Thread Launchpad Bug Tracker 
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2

---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium

  * Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
  * test/test_blacklisted_wrong_origin.py: Fix and enable test
  * Filter out progress indicator from dpkg log (LP: #1599646)
  * Clear cache when autoremoval fails (LP: #1779157)
  * Find autoremovable kernel packages using the patterns in APT's way
(LP: #1815494)

unattended-upgrades (1.1ubuntu1.18.04.7~16.04.1) xenial; urgency=medium

  * Start service after systemd-logind.service to be able to take inhibition
lock (LP: #1806487)
  * Handle gracefully when logind is down (LP: #1806487)

unattended-upgrades (1.1ubuntu1.18.04.7~16.04.0) xenial; urgency=medium

  * Backport to Xenial (LP: #1702793)
  * Revert to build-depending on debhelper (>= 9~) and dh-systemd
  * Revert configuration example changes to avoid triggering a debconf question
  * debian/postinst: Update recovery to be triggered on Xenial's package 
versions

unattended-upgrades (1.1ubuntu1.18.04.7) bionic; urgency=medium

  * Trigger unattended-upgrade-shutdown actions with PrepareForShutdown()
Performing upgrades in service's ExecStop did not work when the upgrades
involved restarting services because systemd blocked other stop/start
actions making maintainer scripts time out and be killed leaving a broken
system behind.
Running unattended-upgrades.service before shutdown.target as a oneshot
service made it run after unmounting filesystems and scheduling services
properly on shutdown is a complex problem and adding more services to the
mix make it even more fragile.
The solution of monitoring PrepareForShutdown() signal from DBus
allows Unattended Upgrade to run _before_ the jobs related to shutdown are
queued thus package upgrades can safely restart services without
risking causing deadlocks or breaking part of the shutdown actions.
Also ask running unattended-upgrades to stop when shutdown starts even in
InstallOnShutdown mode and refactor most of unattended-upgrade-shutdown to
UnattendedUpgradesShutdown class. (LP: #1778219)
  * Increase logind's InhibitDelayMaxSec to 30s. (LP: #1778219)
This allows more time for unattended-upgrades to shut down gracefully
or even install a few packages in InstallOnShutdown mode, but is still a
big step back from the 30 minutes allowed for InstallOnShutdown previously.
Users enabling InstallOnShutdown node are advised to increase
InhibitDelayMaxSec even further possibly to 30 minutes.
- Add NEWS entry about increasing InhibitDelayMaxSec and InstallOnShutdown
  changes
  * Ignore "W503 line break before binary operator"
because it will become the best practice and breaks the build
  * Stop using ActionGroups, they interfere with apt.Cache.clear()
causing all autoremovable packages to be handled as newly autoremovable
ones and be removed by default. Dropping ActionGroup usage does not slow
down the most frequent case of not having anything to upgrade and when
there are packages to upgrade the gain is small compared to the actual
package installation.
Also collect autoremovable packages before adjusting candidates because that
also changed .is_auto_removable attribute of some of them. (LP: #1803749)
(Closes: #910874)

unattended-upgrades (1.1ubuntu1.18.04.6) bionic; urgency=medium

  * Unlock for dpkg operations with apt_pkg.pkgsystem_unlock_inner() when it is
available. Also stop running when reacquiring the lock fails.
Thanks to Julian Andres Klode for original partial patch (LP: #1789637)
  * Skip rebuilding python-apt in upgrade autopkgtests.
Python-apt has a new build dependency making the rebuilding as is failing
and the reference handling issue is worked around in unattended-upgrades
already. (LP: #1781586)
  * Stop trying when no adjustment could be made and adjust package candidates
only to lower versions (LP: #1785093)
  * Skip already adjusted packages from being checked for readjusting.
This makes it clearer that the recursion ends and can also be a bit quicker.
(LP: #1785093)

unattended-upgrades (1.1ubuntu1.18.04.5) bionic; urgency=medium

  * Stop updating the system when reacquiring the dpkg system lock fails.
(LP: #1260041)

unattended-upgrades (1.1ubuntu1.18.04.4) bionic; urgency=medium

  * Redirect stderr output in upgrade-between-snapshots, too, otherwise it
breaks the test sometimes (LP: #1781446)

unattended-upgrades (1.1ubuntu1.18.04.3) bionic; urgency=medium

  * Redirect stderr output in upgrade-all-security, otherwise it breaks the
test (LP: #1781446)

unattended-upgrades (1.1ubuntu1.18.04.2) bionic; urgency=medium

  [ Balint Reczey ]
  * Clear cache when autoremoval is invalid for a package set marked for
removal and

[Group.of.nepali.translators] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to

2018-02-13 Thread Launchpad Bug Tracker 
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   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/1690980

Title:
  unattended-upgrades does not block shutdown of system, as it is
  designed to

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  Triaged
Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  New
Status in apt source package in Zesty:
  Won't Fix
Status in unattended-upgrades source package in Zesty:
  Won't Fix

Bug description:
  Title: No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

  Summary:
  No pop-up window to warn users that system should not reboot or shutdown 
while installing security updates

  Steps:
  1. trigger unattended-upgrades
  2. reboot or shutdown system while installing packages

  Expected results: There is a pop-up window to warn users that system
  should not reboot or shutdown

  Actual results: There is no pop-up window to warn users

  Additional information:
  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
    Installed: 0.90
    Candidate: 0.90ubuntu0.5
  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS

  
  * APT SRU *
  [Impact]
  Stopping apt-daily-upgrade.service terminates dpkg and friends by sending the 
signals to all processes in the cgroup, and will send KILL quickly after.

  [Test case]
  Start apt-daily-upgrade.service and stop it while unattended-upgrades is 
running.

  The upgrade should run to completion or a safe exit point as long as
  it takes less than about 900s (which is the timeout for sending kill).

  [Regression potential]
  Leftover processes might remain in the apt-daily-upgrade cgroup if the 
postinst scripts or some apt hooks do something funny.

  Shutdown might take longer due to the 900 second timeout.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1690980/+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

[Group.of.nepali.translators] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to

2018-01-17 Thread Steve Langasek 
Ubuntu 17.04 has reached end of life.  No further bugfixes will be
applied to this version.

** Changed in: apt (Ubuntu Zesty)
   Status: Fix Committed => Won't Fix

** Changed in: unattended-upgrades (Ubuntu Zesty)
   Status: New => Won't Fix

-- 
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/1690980

Title:
  unattended-upgrades does not block shutdown of system, as it is
  designed to

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  Triaged
Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Xenial:
  New
Status in apt source package in Zesty:
  Won't Fix
Status in unattended-upgrades source package in Zesty:
  Won't Fix

Bug description:
  Title: No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

  Summary:
  No pop-up window to warn users that system should not reboot or shutdown 
while installing security updates

  Steps:
  1. trigger unattended-upgrades
  2. reboot or shutdown system while installing packages

  Expected results: There is a pop-up window to warn users that system
  should not reboot or shutdown

  Actual results: There is no pop-up window to warn users

  Additional information:
  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
    Installed: 0.90
    Candidate: 0.90ubuntu0.5
  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS

  
  * APT SRU *
  [Impact]
  Stopping apt-daily-upgrade.service terminates dpkg and friends by sending the 
signals to all processes in the cgroup, and will send KILL quickly after.

  [Test case]
  Start apt-daily-upgrade.service and stop it while unattended-upgrades is 
running.

  The upgrade should run to completion or a safe exit point as long as
  it takes less than about 900s (which is the timeout for sending kill).

  [Regression potential]
  Leftover processes might remain in the apt-daily-upgrade cgroup if the 
postinst scripts or some apt hooks do something funny.

  Shutdown might take longer due to the 900 second timeout.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1690980/+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