Your message dated Fri, 23 Aug 2013 17:02:20 +0200
with message-id <[email protected]>
and subject line Re: Bug#720300: gridsite: some shipped files are not included
in md5sums
has caused the Debian Bug report #720300,
regarding gridsite: some shipped files are not included in md5sums
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
720300: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720300
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gridsite
Version: 1.7.21-3
Severity: important
User: [email protected]
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package does not include
md5sums for all the files it ships:
gridsite: FILE WITHOUT MD5SUM /var/lib/gridsite/.gacl
gridsite: FILE WITHOUT MD5SUM /var/lib/gridsite/gridsitefoot.txt
gridsite: FILE WITHOUT MD5SUM /var/lib/gridsite/gridsitehead.txt
If these files are intended to be modified, they should be managed by
maintainer scripts instead of being shipped.
Currently they will be overwritten on every upgrade.
Andreas
--- End Message ---
--- Begin Message ---
tis 2013-08-20 klockan 10:40 +0200 skrev Andreas Beckmann:
> Hi,
>
> during a test with piuparts I noticed your package does not include
> md5sums for all the files it ships:
>
> gridsite: FILE WITHOUT MD5SUM /var/lib/gridsite/.gacl
> gridsite: FILE WITHOUT MD5SUM /var/lib/gridsite/gridsitefoot.txt
> gridsite: FILE WITHOUT MD5SUM /var/lib/gridsite/gridsitehead.txt
>
> If these files are intended to be modified, they should be managed by
> maintainer scripts instead of being shipped.
> Currently they will be overwritten on every upgrade.
These files are properly listed as configuration files in the dpkg
metadata of the package:
$ cat /var/lib/dpkg/info/gridsite.conffiles
/var/lib/gridsite/.gacl
/var/lib/gridsite/gridsitefoot.txt
/var/lib/gridsite/gridsitehead.txt
/etc/apache2/sites-available/gridsite.conf
/etc/apache2/mods-available/zgridsite.load
/etc/apache2/mods-available/zgridsite.conf
They are handled by the normal configure file mechanism in dpkg, and the
md5sums are tracked in the package status, the same way it is for other
configuration files.
$ dpkg --status gridsite
Package: gridsite
Status: install ok installed
[ ... ]
Conffiles:
/var/lib/gridsite/.gacl 88f4b45b6569fac47298439f2c911db5
/var/lib/gridsite/gridsitefoot.txt 45ae35fb1a24a05bfbea36c3500ed5ba
/var/lib/gridsite/gridsitehead.txt 80aaad7a677d7bd24c8e7e7594befa06
/etc/apache2/sites-available/gridsite.conf a7a43c456129084c6fb1c538e01ed0ae
/etc/apache2/mods-available/zgridsite.load 8841babc5836a6b0264cffd6b4be1582
/etc/apache2/mods-available/zgridsite.conf 500abc73c2856aa23af9bf3a33f45caf
[ ... ]
On package upgrade the files are managed correctly by dpkg. There is no
need for any additional managing using maintainer scripts. If the file
in the new package differs from the file in the old package the file is
replaced if the installed file has not been changed and otherwise not.
Which is the expected behaviour.
I don't see where the bug is here.
Mattias
smime.p7s
Description: S/MIME cryptographic signature
--- End Message ---
