On Fri, 2012-08-10 at 23:16 +0100, peter green wrote:
> Philipp Kern wrote:
> > Uhm, is it really required by policy to delete backup files that weren't
> > created by the package in the first place?
> >
> > diff -Nru fpc-2.6.0/debian/fp-compiler.postrm.in
> > fpc-2.6.0/debian/fp-compiler.postrm.in
> > --- fpc-2.6.0/debian/fp-compiler.postrm.in 2012-05-06
> > 21:43:32.000000000 +0000
> > +++ fpc-2.6.0/debian/fp-compiler.postrm.in 2012-08-09
> > 22:55:10.000000000 +0000
> > @@ -4,12 +4,14 @@
> >
> > ACTION=$1
> >
> > -CFG_FILE="/etc/fpc-${VERSION}.cfg"
> > +CFG_FILE="/etc/fpc-${VERSION}"
> >
> > # Debhelper code
> > #DEBHELPER#
> >
> > if test "${ACTION}" = "purge"
> > then
> > - rm -f ${CFG_FILE}
> > + rm -f "${CFG_FILE}".cfg
> > + rm -f "${CFG_FILE}".bak
> > + rm -f "${CFG_FILE}".*dpkg*
> > fi
> >
> > The second part does not make me happy.
> >
> The .bak file is created by the package under some circumstances
> (certain upgrade scenarios I believe).
>
> I don't understand why abou put in the .*dpkg* line though. ccing
> him to ask.Sorry for late replay. The *.dpkg* are crated when upgrading with conflicts between local modifications and new supplied default script. These are normally to be removed by user, but when you are purging a file you are getting rid of all configuration, so I thought it was no need to keep these files. Cheers,
signature.asc
Description: This is a digitally signed message part
