-
unattended-upgrades (1.5ubuntu3.18.10.4) cosmic; urgency=medium
* Detect changes to moved conffiles (LP: #1823872)
* Add tests for checking conffile moves.
Build depend on and use equivs to generate new test packages
* Detect unchanged moved conffiles.
When a package moves a conffile properly without any change no conffile
prompt needs to be shown thus the package can be upgraded unattended.
(LP: #1823872)
- Split() conffile data to set of names only once
- Don't parse dpkg conffile db when there are no conffiles in the package
* Skip sending email when no package had to be installed, upgraded or removed
(LP: #1821103) (Closes: #924554)
* Make sure autoremovals don't start with a dirty cache and remove other
packages (LP: #1824341)
* Continue applying minimal sets when one set can't be marked for upgrade.
Thanks to Anderson Luiz Alves for the patch, it needed minor modifications
(LP: #1824341)
* Stop raising NoAllowedOriginError when marking packages to upgrade/install
fails (LP: #1824876)
* Adjust only transitive dependencies in the fallback when a package from an
allowed origin can't be marked to install/upgrade.
This is a much lighter approach than marking every upgradable package
because the full fallback was triggered on packages held back as well,
using an excessive amount of CPU time.
Also it crashed with packages not having any version in allowed origins.
(LP: #1824804, #1824949)
- Follow all kinds of transitive dependencies when adjusting dependencies
- Don't crash collecting transitive dependencies when package has no
candidate (LP: #1825886)
* Skip trying to upgrade held packages in call_adjusted() (LP: #1824804)
* Use mark_install_adjusted() in rewind_cache()
The original cache had packages marked with adjustments thus rewinding
should also do adjustments to reach the same state.
Also not using mark_install_adjusted() crashes when apt raises error on
held packages. (LP: #1826157)
- test_rewind: Update test to check if adjustend rewinding took place
-- Balint Reczey <email address hidden> Fri, 26 Apr 2019 18:55:30 +0200
-
unattended-upgrades (1.5ubuntu3.18.10.3) cosmic; urgency=medium
* Compare apt.package.Version objects and not the versions' string
representation. (LP: #1820888)
This prevented adjusting candidates when the strings sorted differently.
Also extend tests to catch issue.
* Fall back to adjusting more packages' candidates
when a package from an allowed origin can't be marked to install/upgrade.
(LP: #1821101)
-- Balint Reczey <email address hidden> Mon, 25 Mar 2019 17:10:19 +0100
-
unattended-upgrades (1.5ubuntu3.18.10.2) cosmic; urgency=medium
* Clear cache when autoremoval fails (LP: #1779157)
* Find autoremovable kernel packages using the patterns in APT's way
(LP: #1815494)
* Filter out progress indicator from dpkg log (LP: #1599646)
-- Balint Reczey <email address hidden> Thu, 21 Feb 2019 15:10:13 +0100
-
unattended-upgrades (1.5ubuntu3.18.10.1) cosmic; 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)
-- Balint Reczey <email address hidden> Thu, 13 Dec 2018 14:39:12 +0100
-
unattended-upgrades (1.5ubuntu3.18.10.0) cosmic; urgency=medium
* Revert to running unattended-upgrades.service in multi-user.target
* 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, LP: #1803137)
* Handle reverting to WantedBy=multi-user.target
* Increase logind's InhibitDelayMaxSec to 30s.
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 mode are advised to increase
InhibitDelayMaxSec even further possibly to 30 minutes.
* Cache polling result for PreparingForShutdown after it becomes true
* debian/tests/test-systemd.py: Reboot system with dbus call to honor
inhibitor locks
* Add NEWS entry about increasing InhibitDelayMaxSec and InstallOnShutdown
changes
* 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 ther 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)
-- Balint Reczey <email address hidden> Mon, 26 Nov 2018 12:28:55 +0100
-
unattended-upgrades (1.5ubuntu3) cosmic; urgency=medium
* 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: #1790687)
* Fix PEP 8 warnings.
Also ignore "W503 line break before binary operator" because it will
become the best practice.
* Don't crash on missing dpkg log file (LP: #1795692)
* do_auto_remove() is successful unless a commit() operation fails
(LP: #1795696)
* Check only dowloaded .deb files for conffile prompts (LP: #1796100)
-- Balint Reczey <email address hidden> Sun, 07 Oct 2018 23:16:17 +0200
-
unattended-upgrades (1.5ubuntu2) cosmic; urgency=medium
* Reopen Cache after commit() even when frontend locking is supported.
This fixes build and operation with latest python-apt.
-- Balint Reczey <email address hidden> Tue, 28 Aug 2018 15:46:25 +0200
-
unattended-upgrades (1.5ubuntu1) cosmic; urgency=medium
* Merge from Debian unstable
- Remaining changes:
- unattended-upgrades: Do not automatically upgrade the development
release of Ubuntu unless Unattended-Upgrade::DevRelease is true.
- Dropped changes, included in Debian:
- Redirect stderr output in upgrade-all-security and
upgrade-between-snapshots otherwise it breaks the test
- Skip rebuilding python-apt in upgrade autopkgtests
unattended-upgrades (1.5) unstable; urgency=medium
* Redirect stderr output in upgrade-all-security and upgrade-between-snapshots
otherwise it breaks the test (LP: #1781446)
* 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)
* Install release's latest python-apt in upgrade-all-security
* Don't check blacklist too early and report updates from not allowed origins as kept back.
This fixes #116 again that was fixed but regressed with 18d23402aae24febb6bda539ac7c410fd86ae80d
(LP: #1781176)
* Run unattended-upgrades.service before shutdown.target as a oneshot service.
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. (LP: #1778219)
* Use os.environ[] to set debconf to NON_INTERACTIVE instead of os.putenv()
os.putenv() does not change os.environ but os.environ can be used in python-apt
to set environment for subprocesses in which case os.putenv()'s effect is
ignored.
* Use valgrind in upgrade autopkgtest when it is installed in the autopkgtest environment
* Stop trying when no adjustment could be made and adjust package candidates only to lower versions
(LP: #1785093)
* List Unattended-Upgrade::Remove-New-Unused-Dependencies option the config file.
Also fix description of Unattended-Upgrade::Remove-Unused-Dependencies.
-- Balint Reczey <email address hidden> Thu, 23 Aug 2018 11:02:51 +0200
-
unattended-upgrades (1.4ubuntu2) cosmic; urgency=medium
* Redirect stderr output in upgrade-all-security and
upgrade-between-snapshots otherwise it breaks the test (LP: #1781446)
* 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, install release's latest python-apt in upgrade-all-security
instead (LP: #1781586)
-- Balint Reczey <email address hidden> Fri, 13 Jul 2018 17:08:54 +0200
-
unattended-upgrades (1.4ubuntu1) cosmic; urgency=medium
* Merge from Debian unstable
- Remaining changes:
- unattended-upgrades: Do not automatically upgrade the development
release of Ubuntu unless Unattended-Upgrade::DevRelease is true.
- Dropped changes, included in Debian:
- Stop rewriting test apt.conf in test_untrusted.py.
- Fix test_on_battery on Ubuntu development releases
unattended-upgrades (1.4) unstable; urgency=medium
* Skip starting init.d script in debhelper-generated postinst part
(LP: #1778800)
* Use "deb-systemd-invoke start" instead of "systemctl start" in postinst.
It is used only in a workaround applied for a Debian bug and for upgrading
from pre-bionic versions.
* Clear cache when autoremoval is invalid for a package set marked for
removal (LP: #1779157)
* Clear cache after failed commits to return from a possibly invalid state
* Unlock for dpkg operations with apt_pkg.pkgsystem_unlock_inner() when it
is available, also stop running when reacquiring the lock fails.
Thanks to to Julian Andres Klode for original partial patch
* Use fully qualified domain name in email subject.
* Send email about all failures and crashes (Closes: #898607)
* Add short textual summary of the results in the summary email
* Recommend overriding configuration in a separate file.
This can be better than changing /etc/apt/apt.conf.d/50unattended-upgrades
because package updates don't conflict with local changes this way.
* Adjust candidates only for packages to be possibly installed
(Closes: #892028, #899366) (LP: #1396787)
* Add Unattended-Upgrade::OnlyOnACPower config file example for all
distributions
* debian/control: Drop redundant Testsuite: autopkgtest field to keep Lintian
happy
* Bump Standards-Version to 4.1.4
* Add debian/tests/upgrade-all-security to install all current security
updates. On development releases this tests latest stable, on stable
releases it tests the release itself.
* Skip updates on metered connections (Closes: #855570)
* Quote shell variables in autopkgtest
* Stop u-u early when it should stop later anyway
* Measure time for --dry-run and after all updates are installed in
autopkgtests
* Filter out packages cheaper when they are not from allowed origins
* Collect autoremovable packages, too, when looking for upgradable ones
-- Balint Reczey <email address hidden> Fri, 06 Jul 2018 13:33:29 +0200
-
unattended-upgrades (1.3ubuntu3) cosmic; urgency=medium
* Stop rewriting test apt.conf in test_untrusted.py.
This fixes overwriting Unattended-Upgrade::OnlyOnACPower "false" accidentally
and breaking the build.
-- Balint Reczey <email address hidden> Tue, 19 Jun 2018 21:24:40 +0200
-
unattended-upgrades (1.3ubuntu2) cosmic; urgency=medium
* Fix test_on_battery on Ubuntu development releases
-- Balint Reczey <email address hidden> Tue, 19 Jun 2018 19:31:14 +0200
-
unattended-upgrades (1.3ubuntu1) cosmic; urgency=medium
* Merge from Debian unstable
- Now candidate adjustment is really fixed (LP: #1775292)
- Remaining changes:
- unattended-upgrades: Do not automatically upgrade the development
release of Ubuntu unless Unattended-Upgrade::DevRelease is true.
unattended-upgrades (1.3) unstable; urgency=medium
[ Balint Reczey ]
* Fix crashing while adjusting candidates and save candidates to adjust only
in first sweep run, not emptying the set later
(LP: #1775307) (Closes: #901258)
* Don't start or gracefully stop upgrade on battery (LP: #1773033)
* Add test for skipping upgrade on battery
[ Ivan Kurnosov ]
* Fixed is_pkgname_in_blacklist() to be side-effect free.
Otherwise is_pkgname_in_blacklist() mutates the pkgs_kept_back list and
unattended-upgrades treats the package as a blacklisted candidate
[ Frans Spiesschaert ]
* Dutch translation update (Closes: #896123)
-- Balint Reczey <email address hidden> Tue, 19 Jun 2018 15:08:21 +0200
-
unattended-upgrades (1.2ubuntu1) cosmic; urgency=medium
* Merge from Debian unstable
- Remaining changes:
- unattended-upgrades: Do not automatically upgrade the development
release of Ubuntu unless Unattended-Upgrade::DevRelease is true.
unattended-upgrades (1.2) unstable; urgency=medium
[ Michael Vogt ]
* unattended-upgrades: fix Unlocked context manager.
The Unlocked context manager did correctly unlock but did not
reacquire the lock which means that in minimal-upgrade step
mode it is possible to run apt code without a lock. If something
else (like landscape, apt, synaptic, packagekit) locks the cache
in the meantime this will work and u-u will get dpkg errors
because dpkg will not be able to perform its operations. It is
less of an issue in non-minimal mode, but even then the auto-remove
step may fail in this way.
[ Balint Reczey ]
* Run mypy with --no-strict-optional to keep mypy 0.600 happy.
Older versions does not support Optional[] typing, thus adding it to the
comments would break the build with all old releases.
* End Python 2 support.
* Fix adjusting candidates
* Minor speed optimizations
* Relock apt lock before reopening the cache
-- Balint Reczey <email address hidden> Wed, 23 May 2018 22:37:35 +0200
-
unattended-upgrades (1.1ubuntu1) bionic; urgency=medium
* Merge from Debian unstable (LP: #1764797)
- Remaining changes:
- unattended-upgrades: Do not automatically upgrade the development
release of Ubuntu unless Unattended-Upgrade::DevRelease is true.
- Dropped changes, included in Debian:
- Rename d/NEWS.Debian to d/NEWS to have it shipped
- Fix typo in NEWS file
- d/rules: Exclude mypy cache from source package.
unattended-upgrades (1.1) unstable; urgency=medium
[ cgail914 ]
* Update 50unattended-upgrades.Raspbian
added a semi-column sign on line 86 to facilitate uncommenting the line
for users and not end up with an error message when running
unattended-upgrades. And make the whole file consistent.
[ Tobias Bannert ]
* completed german translation
[ Simon McVittie ]
* d/rules: Exclude mypy cache from source package.
[ Julian Andres Klode ]
* Do not reuse old apt.Version objects after reopening cache (LP: #1737441)
[ Balint Reczey ]
* Rename d/NEWS.Debian to d/NEWS to have it shipped
* Fix typo in NEWS file
* Add missing semicolon to commented-out Remove-Unused-Kernel-Packages option
* Set UnattendedUpgradesCache.allowed_origins before calling
apt.Cache.__init__()
* Find package candidates to adjust sweeping through all packages only once.
Later reuse the list candidates and filter out packages installed in the
meantime. Thanks to Julian Andres Klode for the original patch
* Use updated python-apt in upgrade-between-snapshots test
* upgrade-between-snapshots: Mount /proc, too, in the chroot.
Also clean up chroot properly on exit.
* upgrade-between-snapshots: Use http_proxy environment variable in chroot,
too
* upgrade-between-snapshots: Remove packages installed as the side-effect of
updating apt and python-apt
* Ignore errors from compiling backported packages
* Make is_autoremove_valid() nondestructive.
Also fix autoremoval of packages when one package can't be removed and
keeps back other package removals due to missing cache.clear()
* Fix tracking removed packages
* Suggest default-mta | mail-transport-agent to keep Lintian happy
[ Michael Vogt ]
* unattanded-upgrades: refactor get_candidates_to_adjust() to
adjust_candidates()
-- Balint Reczey <email address hidden> Tue, 17 Apr 2018 16:53:30 +0200
