On Thu, Sep 12, 2013 at 9:31 AM, Charlie Smotherman <cj...@cableone.net>wrote:
> On Thu, Sep 12, 2013 at 3:19 AM, Andreas Beckmann <a...@debian.org> wrote: > >> Package: ampache >> Version: 3.6-rzb2752+dfsg-1 >> 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. >> >> Like a plain failure on initial install this makes the package too buggy >> for a release, thus the severity. >> >> >From the attached log (scroll to the bottom...): >> >> Removing ampache ... >> Purging configuration files for ampache ... >> ucfr: Corrupt registry: Duplicate entries for /etc/ampache/ampache.conf >> ampache /etc/ampache/ampache.conf >> ampache /etc/ampache/ampache.conf >> dpkg: error processing ampache (--purge): >> subprocess installed post-removal script returned error exit status 2 >> Errors were encountered while processing: >> ampache >> >> >> I added ucf to the packaging to mange this file in a Debian compliant > way. Unless I have ucf configured incorrectly (which is quite possible) I > can't see how this is a bug in ampache, but instead should be forwarded to > the ucf package instead. > > > Would possibly using ucfr --force --purge ampache /etc/ampache/ampache.conf help in ampache.postrm? -- Charlie Smotherman Debian Contributor Ubuntu Developer
