On Sat, Jan 21, 2017 at 08:46:22PM +0100, Andreas Beckmann wrote: > Package: redmine > Version: 3.3.1-2 > Severity: serious > User: [email protected] > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package failed to install, > remove (but not purge), and install again. > Before the second installation the package is in config-files-remaining > state. The configuration is remaining from the last version that was > successfully configured - which is the same version that is going to be > installed again.
Hi, First of all thanks for your work on piuparts. However, I am not able to reproduce this without piuparts. I tried install/remove/install by hand on a clean chroot twice, and even automating it with a script like this: export DEBIAN_FRONTEND=noninteractive apt-get install -qy redmine apt-get remove -qy redmine apt-get install -qy redmine The process piuparts uses for these tests seems a little convoluted. I imagine piuparts does things this way for Very Good Reasons™ (trying to minimize false positives, and failures in one package being blamed on another, etc), but I am not sure how well it represents actual usage. Would you have any tips for reproducing this failure outside of piuparts?
signature.asc
Description: PGP signature
