[Pkg-puppet-devel] How to handle left-over files

[Micah Anderson]

One of the release goals for Lenny is that the archive is
piuparts-clean. It seems like puppet is failing that test, and I'm not
sure how to solve this, so I am looking for other's thoughts on the
subject. There are two scenarios that need to be addressed that I
outline below. The first one I have some suggestions for how to handle
this, the second I'm looking for help on.

The bug was reported here: #454681 <http://bugs.debian.org/454681>.

1. If you install puppetmaster, then purge it, there are things left
over, steps to reproduce:
   a. apt-get install puppetmaster=0.24.4-6 puppet=0.24.4-6
   b. apt-get --purge remove puppetmaster puppet
   c. # ls -l /var/log/puppet
      total 8
      -rw-rw---- 1 113 120 4962 2008-05-03 18:01 masterhttp.log
      # ls -l /etc/puppet/
      drwxr-xr-x 2 root root 1024 2008-05-03 18:00 manifests

The /etc/puppet/manifests directory seems to be there because of the
following two entries:
rules:52:       install -d -m0755 $(pkgconfdir)/manifests
puppetmaster.files:5:	etc/puppet/

Suggestions: 
1. remove line 52 from debian/rules
2. remove line 5 from puppetmater.files
3. do a mkdir -p /etc/puppet in debian/rules
4. add an rm -f /var/log/puppet/* in the prerm?

2. If you had puppet installed from etch (0.20), and then upgrade to the
lenny version, you are left with a few files, steps to reproduce:
      a. add a etch source to your apt/sources.list, update
      b. apt-get install puppet=0.20.1-1 puppetmaster=0.20.1-1
      c. apt-get install puppet=0.24.4-6 puppetmaster=0.24.4-6 (or -5 which is in lenny now)
      d. apt-get --purge remove puppet
      e. pond:/var/log# ls /etc/puppet/
      manifests  puppetd.conf  puppetmasterd.conf  ssl
      drwxrwx--x 6 root root 1024 2008-05-03 18:17 ssl
      f. # ls -l /var/log/puppet
      total 8
      -rw-rw---- 1 113 120 4962 2008-05-03 18:01 masterhttp.log

The manifests and masterhttp.log are the same as the previous issue.

The /etc/puppet/puppetd.conf and puppetmasterd.conf is there because the
old version of puppet used this config file, but the newer version uses
puppet.conf. The newer version of puppet also is putting the ssl
certificates in /var/lib/puppet/ssl. The NEWS.Debian for 0.23.2-3
details the problem: how do we transition people from the old-style
config files to the new consolidated one? 

Suggestsions: ? I do not have any good ideas.