Bug#687788: kfreebsd-image-8.3-1-amd64: unowned files after purge (policy 6.8, 10.8): /boot/kernel/kernel.gz
Package: kfreebsd-image-8.3-1-amd64 Version: 8.3-4 Severity: important User: debian...@lists.debian.org Usertags: piuparts Control: found -1 kfreebsd-8/8.3-4 Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8 (or 10.8): http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails Filing this as important as having a piuparts clean archive is a release goal since lenny. From the attached log (scroll to the bottom...): 0m31.6s ERROR: WARN: Broken symlinks: /boot/kernel/kernel.gz - /boot/kfreebsd-8.3-1-amd64.gz 0m33.6s ERROR: FAIL: Package purging left files on system: /boot/kernel/ not owned /boot/kernel/kernel.gz - /boot/kfreebsd-8.3-1-amd64.gznot owned See #672255 for the corresponding kfreebsd 9 bug. cheers, Andreas kfreebsd-image-8.3-1-amd64_8.3-4.log.gz Description: GNU Zip compressed data
Processed: kfreebsd-image-8.3-1-amd64: unowned files after purge (policy 6.8, 10.8): /boot/kernel/kernel.gz
Processing control commands: found -1 kfreebsd-8/8.3-4 Bug #687788 [kfreebsd-image-8.3-1-amd64] kfreebsd-image-8.3-1-amd64: unowned files after purge (policy 6.8, 10.8): /boot/kernel/kernel.gz Marked as found in versions kfreebsd-8/8.3-4; no longer marked as found in versions kfreebsd-8/8.3-4. -- 687788: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687788 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.b.134774271426292.transcr...@bugs.debian.org
Bug#686013: freebsd-nfs-server: NFSD does not start
On 16/09/12 00:44, Steven Chamberlain wrote: I gather this file is used a bit like transaction log, so must never be created, empty, from an initscript merely because it is missing. Instead, it should be created at install time from postinst as you have done. During a package upgrade, I think that is okay too [...] p.s., upstream references for this: http://lists.freebsd.org/pipermail/freebsd-current/2010-September/019834.html and: http://www.freebsd.org/cgi/man.cgi?query=stablerestartsektion=5 -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/505513c1.4040...@pyro.eu.org
Bug#686013: freebsd-nfs-server: NFSD does not start
On 16.09.2012 01:44, Steven Chamberlain wrote: FWIW I think your fix is correct. I gather this file is used a bit like transaction log, so must never be created, empty, from an initscript merely because it is missing. Instead, it should be created at install time from postinst as you have done. During a package upgrade, I think that is okay too, because it can be assumed that /var is already clean and mounted by then. Please forgive my confusion, but that's what I did, didn't I? I create the package at installation time in maintainer script if it is missing and never again. I don't touch or modify the init script at all. Aside I agree with you. I understand it as a state file as well, which must be persistent across reboots, but not be modified at start time or anytime again. So we may discuss whether we need some contents to initialize it for the first time the package is installed. Note, our own man pages previously suggested to do this: before starting the server for the first time, create an empty /var/db/nfs-stablerestart file. The command install -o root -g wheel -m 600 /dev/null /var/db/nfs-stablerestart executed as ``su'' should suffice. This can only be done when the server is not running and there are no nfsv4 file system mounts against the server. If this file is lost during a crash, recovery from backups is recommended. [1] The 9.0 version of nfsv4.4 lacks this part, however. I haven't tried it yet though (or NFS, at all, on a kFreeBSD system). It works for me, YMMV. [1] http://www.freebsd.org/cgi/man.cgi?query=nfsv4apropos=0sektion=4manpath=FreeBSD+8.2-RELEASEarch=defaultformat=html -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D signature.asc Description: OpenPGP digital signature
Bug#686013: freebsd-nfs-server: NFSD does not start
On 16.09.2012 01:44, Steven Chamberlain wrote: [...] should be created at install time from postinst as you have done. On 16/09/12 01:00, Arno Töll wrote: Please forgive my confusion, but that's what I did, didn't I? I create the package at installation time in maintainer script if it is missing and never again. I don't touch or modify the init script at all. Yes! I was agreeing with you. I only mentioned the initscript as an example of what would be the /wrong/ way to do this, So we may discuss whether we need some contents to initialize it for the first time the package is installed. Note, our own man pages previously suggested to do this: [...] The upstream nfsv4(4) man page seems to be out-of-date actually: If either file is missing, they will be created by the nfsd(8). Of course that's not true any more, and the reason for this bug. An empty file seems to be correct way to initialise it. As you have already done. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/505519b5.40...@pyro.eu.org
Re: Bug#686013: freebsd-nfs-server: NFSD does not start
On 16.09.2012 01:44, Steven Chamberlain wrote: FWIW I think your fix is correct. Gah, sorry Steve, it's late in my time zone. I misread that as incorrect. :) That said, I wonder now: Should that file be removed on a package purge? From reading the man page, I would say no. However, our policy is pretty clear not to leave back anything back on a package purge. -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D signature.asc Description: OpenPGP digital signature
