Control: retitle -1 redmine: fails to install, purge and install again On Sat, Feb 04, 2017 at 11:12:44AM +0100, Gilles Filippini wrote: > Hi, > > On Sun, 22 Jan 2017 14:29:27 -0200 Antonio Terceiro <terce...@debian.org> > wrote: > > On Sat, Jan 21, 2017 at 08:46:22PM +0100, Andreas Beckmann wrote: > > > Package: redmine > > > Version: 3.3.1-2 > > > Severity: serious > > > User: debian...@lists.debian.org > > > 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 > > I can reproduce a similar error without piuparts using the following sequence > in a clean sid chroot: > # export DEBIAN_FRONTEND=noninteractive > # apt-get install -y redmine > ... > # apt-get remove --purge -y redmine > ... > # apt-get install -y redmine
So this means that the original submission was misleading. The piuparts log posted in the bug report says piuparts was called with --install-purge-install, while the bug report itself says "remove (but purge)". So the bug is that redmine fails to install after being *purged*, not just being removed.
signature.asc
Description: PGP signature
