All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Laszlo Boszormenyi (GCS)" <gcs@debian.hu>
To: Sage Weil <sage@inktank.com>
Cc: Dan Mick <dan.mick@inktank.com>,
	Mark Nelson <mark.nelson@inktank.com>,
	ceph-devel@vger.kernel.org, james.page@ubuntu.com
Subject: Re: deb/rpm package purge
Date: Tue, 19 Mar 2013 22:27:29 +0000	[thread overview]
Message-ID: <1363732049.12547.22.camel@julia> (raw)
In-Reply-To: <alpine.DEB.2.00.1303191349360.4850@cobra.newdream.net>

On Tue, 2013-03-19 at 13:51 -0700, Sage Weil wrote:
> On Tue, 19 Mar 2013, Dan Mick wrote:
> > Is there a way out if you remove the keyrings?
> 
> Yeah; you can use the keyring in the mon data dir to refetch any keyrings 
> you deleted from /etc/ceph/.
 But if packages are purged on mon as well...

> I don't disagree with any of this discussion, BTW; I ask the question 
> because I want to understand what the packaging best-practices are before 
> we put our foot down for what is "right".
 Actually there are two methods to uninstall a package from the system.
One is '-r' or '--remove' options of dpkg . As it's name and the
manpage confirms: "Remove  an  installed  package. -r or --remove remove
everything _except conffiles_. This may avoid having to reconfigure the
package if it is reinstalled later.". The second is '-P' or '--purge',
which stands for '[...] removes  everything,  including conffiles.".
Debian policy chapter 10 [1] writes about files and their handling. Its
subchapter 10.7 [2] talks about configuration files. Their handling is
expressed in subchapter 6.8 [3].

 In short, if user asks to purge the package, then the keys have to be
removed as well. If someone thinks about a reinstallation, s/he should
use remove instead. To be safe, I see one option. On purge, a debconf
message can be displayed notifying the user about the keys are going to
be removed as well. Abort of purge or backup of keys can be offered,
based on the choice.

Hope this helps,
Laszlo/GCS
[1] http://www.debian.org/doc/debian-policy/ch-files.html
[2] http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files
[3] http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails


  reply	other threads:[~2013-03-19 22:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-19 19:48 deb/rpm package purge Sage Weil
2013-03-19 19:59 ` Greg Farnum
2013-03-19 20:05 ` Mark Nelson
2013-03-19 20:46   ` Dan Mick
2013-03-19 20:51     ` Sage Weil
2013-03-19 22:27       ` Laszlo Boszormenyi (GCS) [this message]
2013-03-19 22:29         ` Sage Weil
2013-03-19 22:51           ` Laszlo Boszormenyi (GCS)
2013-03-19 22:59             ` Sage Weil
2013-03-20  6:29               ` Laszlo Boszormenyi (GCS)
2013-03-20 12:48                 ` Sage Weil
2013-03-20 14:48                   ` Mark Nelson
2013-03-20 17:27                     ` James Page
2013-03-20 23:23                   ` Laszlo Boszormenyi (GCS)
2013-03-21  1:08                     ` Dan Mick
2013-03-19 23:01             ` Mark Nelson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1363732049.12547.22.camel@julia \
    --to=gcs@debian.hu \
    --cc=ceph-devel@vger.kernel.org \
    --cc=dan.mick@inktank.com \
    --cc=james.page@ubuntu.com \
    --cc=mark.nelson@inktank.com \
    --cc=sage@inktank.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.