[Piuparts-devel] Bug#798266: Bug#798266: Acknowledgement (piuparts: using --existing-chroot= option fails to dist-upgrade chroot)

[Andreas Beckmann]

On 2015-09-07 16:08, Michael Prokop wrote:
> 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.

I think the logic should be "run distupgrade unless the chroot is a
temporary one that was just created". And enumerating the non-temporary
ways to get a chroot is just wrong since it will break whenever a new
way gets added.


Andreas