Bug#624586: marked as done (are packages allowed to per default not purge on purge?)
Your message dated Mon, 31 Oct 2011 10:48:19 -0700 with message-id 87ehxt3vdo@windlord.stanford.edu and subject line Re: Bug#624586: sasl2-bin: unowned files after purge (policy 6.8, 10.8) has caused the Debian Bug report #624586, regarding are packages allowed to per default not purge on purge? 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 ow...@bugs.debian.org immediately.) -- 624586: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sasl2-bin Version: 2.1.23.dfsg1-8 Severity: important User: debian...@lists.debian.org Usertags: piuparts piuparts.d.o 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...): 0m20.7s ERROR: FAIL: Package purging left files on system: /etc/sasldb2 not owned cheers, Holger Start: 2011-03-17 09:30:41 UTC Package: sasl2-bin Priority: optional Section: utils Installed-Size: 508 Maintainer: Debian Cyrus SASL Team pkg-cyrus-sasl2-debian-de...@lists.alioth.debian.org Architecture: amd64 Source: cyrus-sasl2 Version: 2.1.23.dfsg1-8 Depends: libsasl2-2 (= 2.1.23.dfsg1-8), libc6 (= 2.4), libcomerr2 (= 1.01), libdb4.8, libgssapi-krb5-2 (= 1.6.dfsg.2), libk5crypto3 (= 1.6.dfsg.2), libkrb5-3 (= 1.7dfsg), libldap-2.4-2 (= 2.4.7), libpam0g (= 0.99.7.1), libssl0.9.8 (= 0.9.8m-1), debconf (= 0.5) | debconf-2.0, lsb-base (= 3.0-6), db4.8-util, debconf (= 1.4.69) | cdebconf (= 0.39) Filename: pool/main/c/cyrus-sasl2/sasl2-bin_2.1.23.dfsg1-8_amd64.deb Size: 179922 MD5sum: c45fb950ae4fb646dd12f36bde14e541 SHA1: 961391da4f409e44e6e941cb13130cd26c3bb6d8 SHA256: 3df4be5dc4f89e9077b1bb39e937a5b620ffe1743466c32104bddffcb0a1a63c Description: Cyrus SASL - administration programs for SASL users database This is the Cyrus SASL API implementation, version 2.1. See package libsasl2-2 and RFC for more information. . This package contains administration programs for the SASL users database and common binary files for plugin modules. Homepage: http://cyrusimap.web.cmu.edu/ Tag: admin::user-management, interface::commandline, role::program, scope::utility, security::authentication Executing: sudo /org/piuparts.debian.org/sbin/piuparts --warn-symlinks --warn-on-others --skip-logrotatefiles-test --scriptsdir /etc/piuparts/scripts/ --tmpdir /org/piuparts.debian.org/tmp -ad sid -b sid.tar.gz --mirror http://piatti.debian.org/debian/ sasl2-bin Guessed: debian 0m0.0s INFO: -- 0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of this logfile. 0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ 0m0.0s INFO: -- 0m0.0s INFO: piuparts version 0.40~201102250909 starting up. 0m0.0s INFO: Command line arguments: /org/piuparts.debian.org/sbin/piuparts --warn-symlinks --warn-on-others --skip-logrotatefiles-test --scriptsdir /etc/piuparts/scripts/ --tmpdir /org/piuparts.debian.org/tmp -ad sid -b sid.tar.gz --mirror http://piatti.debian.org/debian/ sasl2-bin 0m0.0s INFO: Running on: Linux piatti 2.6.32-5-amd64 #1 SMP Wed Jan 12 03:40:32 UTC 2011 x86_64 0m0.0s DEBUG: Created temporary directory /org/piuparts.debian.org/tmp/tmpCXgHo2 0m0.0s DEBUG: Unpacking sid.tar.gz into /org/piuparts.debian.org/tmp/tmpCXgHo2 0m0.0s DEBUG: Starting command: ['tar', '-C', '/org/piuparts.debian.org/tmp/tmpCXgHo2', '-zxf', 'sid.tar.gz'] 0m2.0s DEBUG: Command ok: ['tar', '-C', '/org/piuparts.debian.org/tmp/tmpCXgHo2', '-zxf', 'sid.tar.gz'] 0m2.0s DEBUG: Created policy-rc.d and chmodded it. 0m2.0s DEBUG: Starting command: ['chroot', '/org/piuparts.debian.org/tmp/tmpCXgHo2', 'apt-get', 'update'] 0m10.5s DUMP: Get:1 http://piatti.debian.org sid InRelease [147 kB] Ign http://piatti.debian.org sid/main amd64 Packages/DiffIndex Ign http://piatti.debian.org sid/contrib amd64 Packages/DiffIndex Ign http://piatti.debian.org sid/non-free amd64 Packages/DiffIndex Ign http://piatti.debian.org sid/contrib TranslationIndex Ign http://piatti.debian.org sid/main TranslationIndex Ign http://piatti.debian.org sid/non-free TranslationIndex Get:2 http://piatti.debian.org sid/main amd64 Packages [9195 kB] Get:3 http://piatti.debian.org sid/contrib amd64 Packages [72.7 kB
are packages allowed to per default not purge on purge?
reopen 618885 reassign 618885 tech-ctte thanks Hi, please read #618885 which is about whether sasl2-bin can kept files on the system after purging it. Policy 6.8 says that files must be removed on purge, Roberto says sasl2-bin is an exception. I disagree. There are some packages in the archive which (are made to) disagree and keep some files, possible providing a mechanism via debconf to delete them, but if so defaulting to false. For example piuparts currently ignores (among others) these patterns: /var/lib/ldap(/.*)? and /var/lib/maxdb(/.*)? and technically I could easily make it ignore /etc/sasldb2.*. But I actually think these exceptions are wrong, but I'm not the instance to decide how to interpret policy. I merely maintain piuparts which test policy compliance as officially interpreted. So dear technical committee, that's why I assigned this bug to you. Thanks for dealing with it, cheers, Holger -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201104291443.08836.hol...@layer-acht.org
Processed: Re: Processed: are packages allowed to per default not purge on purge?
Processing commands for cont...@bugs.debian.org: retitle 618885 are packages allowed to per default not purge on purge? Bug #618885 [debian-policy] sasl2-bin: unowned files after purge (policy 6.8, 10.8) Changed Bug title to 'are packages allowed to per default not purge on purge?' from 'sasl2-bin: unowned files after purge (policy 6.8, 10.8)' thanks Stopping processing here. Please contact me if you need assistance. -- 618885: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13040922035336.transcr...@bugs.debian.org
Bug#618885: are packages allowed to per default not purge on purge?
Holger Levsen hol...@layer-acht.org writes: please read #618885 which is about whether sasl2-bin can kept files on the system after purging it. Policy 6.8 says that files must be removed on purge, Roberto says sasl2-bin is an exception. I disagree. I concur with Roberto in general. I don't think removing a user-generated authentication database on purge without some sort of prompt is acceptable given the risk of user data loss. To me, this is equivalent to removing the OpenLDAP database or the Kerberos KDC database, which have similar prompts and default to not removing the database on purge. However, in the specific case exercised by puiparts, this file would contain only automatically generated data from the sasl2-bin postinst. Could its postrm examine the file on purge and see whether it contains only the automatically-generated content created by the postinst, and if so, delete it without a prompt? This seems entirely safe to me provided that the logic works, and would resolve the puiparts issue without removing user data without prompting. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87pqo5nggi@windlord.stanford.edu
Bug#618885: are packages allowed to per default not purge on purge?
On Fri, Apr 29, 2011 at 09:57:17AM -0700, Russ Allbery wrote: Holger Levsen hol...@layer-acht.org writes: please read #618885 which is about whether sasl2-bin can kept files on the system after purging it. Policy 6.8 says that files must be removed on purge, Roberto says sasl2-bin is an exception. I disagree. I concur with Roberto in general. I don't think removing a user-generated authentication database on purge without some sort of prompt is acceptable given the risk of user data loss. To me, this is equivalent to removing the OpenLDAP database or the Kerberos KDC database, which have similar prompts and default to not removing the database on purge. However, in the specific case exercised by puiparts, this file would contain only automatically generated data from the sasl2-bin postinst. Could its postrm examine the file on purge and see whether it contains only the automatically-generated content created by the postinst, and if so, delete it without a prompt? This seems entirely safe to me provided that the logic works, and would resolve the puiparts issue without removing user data without prompting. I would like to thank you for writing that. The distinction should be done between user-generated data and package-generated data, and how to deal with amiguous cases. This issue is similar with handling of config files changes. Packages should not bother the users when the users did no modify the files. In the same way, if the user did not actually generate any data, then the useless file should be cleaned up. Cheers, -- Bill. ballo...@debian.org Imagine a large red swirl here. -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110429191841.GC2835@yellowpig
Bug#618885: are packages allowed to per default not purge on purge?
reassign 618885 sasl2-bin found 618885 2.1.23.dfsg1-8 retitle 618885 sasl2-bin: Remove /etc/sasldb2 on purge if unmodified since installation thanks On Fri, Apr 29, 2011 at 09:18:41PM +0200, Bill Allombert wrote: I would like to thank you for writing that. The distinction should be done between user-generated data and package-generated data, and how to deal with amiguous cases. This issue is similar with handling of config files changes. Packages should not bother the users when the users did no modify the files. In the same way, if the user did not actually generate any data, then the useless file should be cleaned up. Russ and Bill, Thanks very much for your input on this. Holger, I have reassigned the bug back to sasl2-bin and will look into a solution that accounts for /etc/sasldb2 having been unmodified since its creation. Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature
Processed: Re: Bug#618885: are packages allowed to per default not purge on purge?
Processing commands for cont...@bugs.debian.org: reassign 618885 sasl2-bin Bug #618885 [debian-policy] are packages allowed to per default not purge on purge? Bug reassigned from package 'debian-policy' to 'sasl2-bin'. found 618885 2.1.23.dfsg1-8 Bug #618885 [sasl2-bin] are packages allowed to per default not purge on purge? Bug Marked as found in versions cyrus-sasl2/2.1.23.dfsg1-8. retitle 618885 sasl2-bin: Remove /etc/sasldb2 on purge if unmodified since installation Bug #618885 [sasl2-bin] are packages allowed to per default not purge on purge? Changed Bug title to 'sasl2-bin: Remove /etc/sasldb2 on purge if unmodified since installation' from 'are packages allowed to per default not purge on purge?' thanks Stopping processing here. Please contact me if you need assistance. -- 618885: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.130411061829501.transcr...@bugs.debian.org
Processed: Re: Processed: Re: Bug#618885: are packages allowed to per default not purge on purge?
Processing commands for cont...@bugs.debian.org: clone 618885 -1 Bug#618885: sasl2-bin: Remove /etc/sasldb2 on purge if unmodified since installation Bug 618885 cloned as bug 624586. reassign -1 debian-policy Bug #624586 [sasl2-bin] sasl2-bin: Remove /etc/sasldb2 on purge if unmodified since installation Bug reassigned from package 'sasl2-bin' to 'debian-policy'. Bug No longer marked as found in versions cyrus-sasl2/2.1.23.dfsg1-8. thanks Stopping processing here. Please contact me if you need assistance. -- 624586: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624586 618885: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618885 -1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-1 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13044530726.transcr...@bugs.debian.org
Re: Processed: Re: Bug#618885: are packages allowed to per default not purge on purge?
clone 618885 -1 reassign -1 debian-policy thanks Oy! I didn't see that it had already been assigned to policy. Sorry. Regards, -Roberto On Fri, Apr 29, 2011 at 09:00:09PM +, Debian Bug Tracking System wrote: Processing commands for cont...@bugs.debian.org: reassign 618885 sasl2-bin Bug #618885 [debian-policy] are packages allowed to per default not purge on purge? Bug reassigned from package 'debian-policy' to 'sasl2-bin'. found 618885 2.1.23.dfsg1-8 Bug #618885 [sasl2-bin] are packages allowed to per default not purge on purge? Bug Marked as found in versions cyrus-sasl2/2.1.23.dfsg1-8. retitle 618885 sasl2-bin: Remove /etc/sasldb2 on purge if unmodified since installation Bug #618885 [sasl2-bin] are packages allowed to per default not purge on purge? Changed Bug title to 'sasl2-bin: Remove /etc/sasldb2 on purge if unmodified since installation' from 'are packages allowed to per default not purge on purge?' thanks Stopping processing here. Please contact me if you need assistance. -- 618885: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature
Processed: retitle 624586 to are packages allowed to per default not purge on purge?
Processing commands for cont...@bugs.debian.org: retitle 624586 are packages allowed to per default not purge on purge? Bug #624586 [debian-policy] sasl2-bin: Remove /etc/sasldb2 on purge if unmodified since installation Changed Bug title to 'are packages allowed to per default not purge on purge?' from 'sasl2-bin: Remove /etc/sasldb2 on purge if unmodified since installation' thanks Stopping processing here. Please contact me if you need assistance. -- 624586: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13041137155606.transcr...@bugs.debian.org
