Hi, the according patch adressing this issue is attached to this mail.
PS: Actually I'm wondering why the dist-upgrade isn't executed *always*, and instead possibly provide an option to skip its execution. The dist-upgrade logic hardcoded into the piuparts script itself without even telling/logging anything about it when/why it's executed isn't really transparent for the user IMHO. I'd be happy to implement an according patch if that would be considered useful. regards, -mika-
From a1629dec9d01e1688d0fe075802a1c52f802aaee Mon Sep 17 00:00:00 2001
From: Michael Prokop <m...@debian.org>
Date: Mon, 7 Sep 2015 15:52:07 +0200
Subject: [PATCH] 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 3c82407..0be4d4d 100644
--- a/piuparts.py
+++ b/piuparts.py
@@ -749,7 +749,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()
--
2.1.4
signature.asc
Description: Digital signature
