[Piuparts-commits] [piuparts] 01/02: Bug#798266: execute dist-upgrade also when using --existing-chroot option
Holger Levsen
holger at moszumanska.debian.org
Mon Jan 18 15:48:12 UTC 2016
This is an automated email from the git hooks/post-receive script.
holger pushed a commit to branch develop
in repository piuparts.
commit b6f3fe051c192ff9284c8c93d8f121d3570db4d8
Author: Michael Prokop <mika at debian.org>
Date: Mon Sep 7 15:52:07 2015 +0200
Bug#798266: execute dist-upgrade also when using --existing-chroot option
Identified during latest point release update: when the
--existing-chroot=... option is used the `apt-get -yf dist-upgrade`
step is not executed, therefore wrong metadata of the chroot might
be recorded for later comparison (like with aptitude's underlying
dependency libsqlite3-0 which received an update).
Thanks: Sipwise GmbH for sponsoring my development time
Closes: #798266
---
piuparts.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/piuparts.py b/piuparts.py
index a73fd19..942af58 100644
--- a/piuparts.py
+++ b/piuparts.py
@@ -750,7 +750,7 @@ class Chroot:
# Useful for adjusting apt configuration e.g. for internal mirror usage
self.run_scripts("post_chroot_unpack")
- if settings.basetgz or settings.schroot:
+ if settings.basetgz or settings.schroot or settings.existing_chroot:
self.run(["apt-get", "-yf", "dist-upgrade"])
self.minimize()
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/piuparts/piuparts.git
More information about the Piuparts-commits
mailing list