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:51:13 +0000	[thread overview]
Message-ID: <1363733473.12547.33.camel@julia> (raw)
In-Reply-To: <alpine.DEB.2.00.1303191528510.4850@cobra.newdream.net>

On Tue, 2013-03-19 at 15:29 -0700, Sage Weil wrote:
> On Tue, 19 Mar 2013, Laszlo Boszormenyi (GCS) wrote:
> >  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.
> The keys aren't a problem; they are still in the mon database 
> (/var/lib/ceph/mon/...).
> 
> The real question is whether purge should remove /var/lib/ceph and 
> /var/log/ceph...
 Sorry if I was not clear and/or generic enough. Use of 'dpkg --remove'
is to remove binaries of the package, but leave other things, runtime
data (configuration, logs, database settings/users and so on) to be left
untouched.
On the other hand, 'dpkg --purge' is to remove everything the package
has installed and/or generated. This includes debconf answers as well.
With other words, purge is used to make the system totally clean of the
package. As such, if the sysadmin install the package again, all debconf
questions will be asked again and all generated files will be generated
again from scratch.

Laszlo/GCS


  reply	other threads:[~2013-03-19 22:51 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)
2013-03-19 22:29         ` Sage Weil
2013-03-19 22:51           ` Laszlo Boszormenyi (GCS) [this message]
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=1363733473.12547.33.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.