Debconf questions and purge
Hi, I need to merge the wwsympa package into sympa. Both packages use debconf. I wonder how I should merge wwsympa debconf templates into sympa's. In sympa, debconf variables start with sympa/ and wwsympa ones start with wwsympa/ If I keep the same variable name, I feel like I'm going to have problem if the user decide to purge wwsympa, because of db_purge. So do I really have to care for the purge and to rename variables? A same kind of problem is likely to happen for the conffiles and other non-conffiles configuration files that I move from wwsympa to sympa and that are been removed in wwsympa postrm. What is the bast way to handle this? Thanks in advance. Cheers, -- Jérôme Marant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Why debhelper doesn't add /usr/doc/package links creation/removal ?
On Wed, Jul 31, 2002 at 04:50:39PM -0400, Ari Pollak wrote: > They are not being silently removed, but since none of the debhelper > scripts for your package need to do anything, and since dh_installdocs > no longer creates and removes symlinks, the debhelper section just stays > empty. > > debhelper (4.1.0) unstable; urgency=low > > * Remove /usr/doc manglement code from postinst and prerm. > Do not use this verion of debhelper for woody backports! > Well, it seems we have to wait for new version of lintian in unstable. R. -- "First they ignore you. Then they laugh at you. Then they fight you. Then you win." - Mohandas Gandhi. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: request for package review - serel
[Resent because I accidentally sent this to Colin per Email, sorry.] Colin Watson <[EMAIL PROTECTED]> wrote: > On Thu, Aug 01, 2002 at 06:24:09PM +1000, Leni Mayo wrote: >> I am new to Debian and have packaged some software which lets the >> boot scripts (/etc/rc[12345].d) run in parallel. It also supports >> visualisation of services, dependencies and timings. [...] >> One known bug is that the -ldb library is currently statically >> linked into the daemon, and it ought to be dynamically >> linked. I haven't yet figured how to bind the linker to a specific >> version of db that's known to be widely deployed. > Use whatever version you think is appropriate (say, db3) and let > dependencies do the rest of the work for you. IANDD but db3 is placed in /usr/lib and probably cannot be used for for a system-bootup software, /usr/ might not be mounted yet. Actually I am confused because there is /lib/libdb.so.3 in package libdb2. cu andreas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: request for package review - serel
On Fri, Aug 02, 2002 at 04:51:32PM +0200, Andreas Metzler wrote: > In article <[EMAIL PROTECTED]> Leni Mayo <[EMAIL PROTECTED]> wrote: > > As this is the first release on debian, I'd be grateful if someone > > with more packaging experience than myself could take a look at it, > > especially since the installation process patches /etc/init.d/rc. > > The .deb is at: http://www.fastboot.org/download/binaries/debian/ > > Hello! > * lintian serel_0.3.4-1.dsc > W: serel source: out-of-date-standards-version 3.0.1 > E: serel source: package-uses-debhelper-but-lacks-build-depends Also: $ lintian serel_0.3.4-1_i386.deb E: serel: file-in-etc-not-marked-as-conffile etc/default/serel E: serel: file-in-etc-not-marked-as-conffile etc/init.d/rc.serel.include E: serel: file-in-etc-not-marked-as-conffile etc/serel/serel.conf E: serel: file-in-etc-not-marked-as-conffile etc/serel/default.rdf E: serel: unregistered-script-in-etc-init.d /etc/init.d/rc.serel.include E: serel: non-standard-file-permissions-for-etc-init.d-script etc/init.d/rc.serel.include 0644 != 0755 W: serel: package-contains-upstream-install-documentation usr/share/doc/serel/INSTALL W: serel: extra-license-file usr/share/doc/serel/COPYING.gz (You can run lintian over the .changes file to check both at once.) At least the first four are serious - they mean that configuration file changes won't be preserved on upgrades. The fifth and sixth may also be a problem depending on how you're interacting with other init script subsystems - I haven't looked at the details. -- Colin Watson [[EMAIL PROTECTED]] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Why debhelper doesn't add /usr/doc/package links creation/re
> > > Well, it seems we have to wait for new version of lintian in unstable. > there is a bug on lintian, the solution is known. I am finishing up a project right now and then intend to devote several weeks to getting lintian up to speed. lintian is a sanity checker but you are free to questions ITS sanity. No where in Debian is lintian used to enforce any rules. It is solely a tool to help you the developer make better packages and reduce the time you spend doing so. This does not mean that you should ignore lintian all of the time. But sometimes it gets policy wrong or policy changes. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debconf questions and purge
Jérôme Marant wrote: > I need to merge the wwsympa package into sympa. Both packages > use debconf. > I wonder how I should merge wwsympa debconf templates into sympa's. > In sympa, debconf variables start with sympa/ and wwsympa ones > start with wwsympa/ > If I keep the same variable name, I feel like I'm going to have > problem if the user decide to purge wwsympa, because of db_purge. > So do I really have to care for the purge and to rename variables? Well, you basically have two options: 1. Don't change the name. Put identically named wsympa/* templates into sympa and watch debconf do the right thing. (That is, when the new sympa is installed, it will mark the templates as shared between the two packages that contain them; then when wsympa is purged it will remove it from the owners list of the questions but keep them around since one other package still owns them. Reference counting.) 2. Change the names and in sympa's config script, use the GET and SET and FSET and FGET commands to copy the old values and seen flags of the old wsympa questions over. > A same kind of problem is likely to happen for the conffiles and other > non-conffiles configuration files that I move from wwsympa to sympa > and that are been removed in wwsympa postrm. I'm afraid you're on your own there; dpkg does not deal with shared conffiles well when the older package is removed I think it removes the conffile. -- see shy jo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
How to upgrade a conflicting package
Hi, I have a package 'liba52-0.7.4-dev' that provides/conflicts/replaces 'liba52-dev'. There is also a 'liba52-0.7.3' with the same provide etc. The problem is I cannot install the newer package: zodiac:/home/micce# LANG=C dpkg -i liba52-0.7.4-dev_0.7.4-1_i386.deb dpkg: regarding liba52-0.7.4-dev_0.7.4-1_i386.deb containing liba52-0.7.4-dev: liba52-0.7.4-dev conflicts with a52dec liba52-0.7.3-dev provides a52dec and is installed. dpkg: error processing debian/UPLOAD/a52dec/liba52-0.7.4-dev_0.7.4-1_i386.deb (--install): conflicting packages - not installing liba52-0.7.4-dev Errors were encountered while processing: debian/UPLOAD/a52dec/liba52-0.7.4-dev_0.7.4-1_i386.deb zodiac:/home/micce# How should this be handled? Is is unavoidable that liba52-0.7.3-dev is first removed? TIA, Micce -- Mikael Hedin, MSc +46 (0)8 344979 (home) +46 (0)70 5891533 (mobile) [gpg key fingerprint = 387F A8DB DC2A 50E3 FE26 30C4 5793 29D3 C01B 2A22] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: request for package review - serel
In article <[EMAIL PROTECTED]> Leni Mayo <[EMAIL PROTECTED]> wrote: [...] > As this is the first release on debian, I'd be grateful if someone > with more packaging experience than myself could take a look at it, > especially since the installation process patches /etc/init.d/rc. > The .deb is at: http://www.fastboot.org/download/binaries/debian/ [...] Hello! * lintian serel_0.3.4-1.dsc W: serel source: out-of-date-standards-version 3.0.1 E: serel source: package-uses-debhelper-but-lacks-build-depends * Is this really a debian-native package, i.e. is serel debian-only? If not (and I think so), use the real upstream source and keep the debian-part in the diff.gz. wget http://www.fastboot.org/download/sources/serel-0.3.4.tar.gz mv serel-0.3.4.tar.gz serel_0.3.4.orig.tar.gz cd serel-0.3.4 dpkg-buildpackage -sd -rfakeroot -S -uc -us * dh_suidregister is depreceated. just my 2 cents. cu andreas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: request for package review - serel
Ick, I didn't notice this thread earlier... On Fri, 02 Aug 2002, Andreas Metzler wrote: > In article <[EMAIL PROTECTED]> Leni Mayo <[EMAIL PROTECTED]> wrote: > [...] > > As this is the first release on debian, I'd be grateful if someone > > with more packaging experience than myself could take a look at it, > > especially since the installation process patches /etc/init.d/rc. > > The .deb is at: http://www.fastboot.org/download/binaries/debian/ Make sure you read http://people.debian.org/~hmh/debconf2/debconf2-initscripts-bkg.ps.gz And you should also get the sysvinit and file-rc package sources, and understand them properly, how they work, how they connect themselves to the init script subsystem, etc. This way, you will know how init-script related utilities are implemented in Debian. serel must properly integrate itself with the lot of them. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debconf questions and purge
Jerome> A same kind of problem is likely to happen for the conffiles Jerome> and other non-conffiles configuration files that I move from Jerome> wwsympa to sympa and that are been removed in wwsympa postrm. Joey> I'm afraid you're on your own there; dpkg does not deal with Joey> shared conffiles well when the older package is removed I think Joey> it removes the conffile. Surely you mean "when the older package is _purged_"? I have done "dpkg --remove oldname ; apt-get install newname" many times on my system, and I think it works. Of course, one has to know in advance a name change is afoot .. -- Ian Zimmerman, Oakland, California, U.S.A. GPG: 433BA087 9C0F 194F 203A 63F7 B1B8 6E5A 8CA3 27DB 433B A087 EngSoc adopts market economy: cheap is wasteful, efficient is expensive. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debconf questions and purge
Ian Zimmerman <[EMAIL PROTECTED]> writes: > Jerome> A same kind of problem is likely to happen for the conffiles > Jerome> and other non-conffiles configuration files that I move from > Jerome> wwsympa to sympa and that are been removed in wwsympa postrm. > > Joey> I'm afraid you're on your own there; dpkg does not deal with > Joey> shared conffiles well when the older package is removed I think > Joey> it removes the conffile. > > Surely you mean "when the older package is _purged_"? Yes, purged. > I have done "dpkg --remove oldname ; apt-get install newname" many > times on my system, and I think it works. It is ok with remove. -- Jérôme Marant http://marant.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debconf questions and purge
Joey Hess <[EMAIL PROTECTED]> writes: > Jérôme Marant wrote: >> I need to merge the wwsympa package into sympa. Both packages >> use debconf. >> I wonder how I should merge wwsympa debconf templates into sympa's. >> In sympa, debconf variables start with sympa/ and wwsympa ones >> start with wwsympa/ >> If I keep the same variable name, I feel like I'm going to have >> problem if the user decide to purge wwsympa, because of db_purge. >> So do I really have to care for the purge and to rename variables? > > Well, you basically have two options: > > 1. Don't change the name. Put identically named wsympa/* templates into >sympa and watch debconf do the right thing. (That is, when the new >sympa is installed, it will mark the templates as shared between the >two packages that contain them; then when wsympa is purged it will >remove it from the owners list of the questions but keep them around >since one other package still owns them. Reference counting.) Smart ;-) I love this. You've made my day! >> A same kind of problem is likely to happen for the conffiles and other >> non-conffiles configuration files that I move from wwsympa to sympa >> and that are been removed in wwsympa postrm. > > I'm afraid you're on your own there; dpkg does not deal with shared > conffiles well when the older package is removed I think it removes the > conffile. I see no real solution to this. One disgusting way for non-conffiles would be to delete the removing part: if [ -e /var/lib/dpkg/info/wwsympa.postrm ]; then sed fi I think you won't like this, will you? ;-) -- Jérôme Marant http://marant.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Debconf questions and purge
Hi, I need to merge the wwsympa package into sympa. Both packages use debconf. I wonder how I should merge wwsympa debconf templates into sympa's. In sympa, debconf variables start with sympa/ and wwsympa ones start with wwsympa/ If I keep the same variable name, I feel like I'm going to have problem if the user decide to purge wwsympa, because of db_purge. So do I really have to care for the purge and to rename variables? A same kind of problem is likely to happen for the conffiles and other non-conffiles configuration files that I move from wwsympa to sympa and that are been removed in wwsympa postrm. What is the bast way to handle this? Thanks in advance. Cheers, -- Jérôme Marant
Re: Why debhelper doesn't add /usr/doc/package links creation/removal ?
On Wed, Jul 31, 2002 at 04:50:39PM -0400, Ari Pollak wrote: > They are not being silently removed, but since none of the debhelper > scripts for your package need to do anything, and since dh_installdocs > no longer creates and removes symlinks, the debhelper section just stays > empty. > > debhelper (4.1.0) unstable; urgency=low > > * Remove /usr/doc manglement code from postinst and prerm. > Do not use this verion of debhelper for woody backports! > Well, it seems we have to wait for new version of lintian in unstable. R. -- "First they ignore you. Then they laugh at you. Then they fight you. Then you win." - Mohandas Gandhi.
Re: request for package review - serel
[Resent because I accidentally sent this to Colin per Email, sorry.] Colin Watson <[EMAIL PROTECTED]> wrote: > On Thu, Aug 01, 2002 at 06:24:09PM +1000, Leni Mayo wrote: >> I am new to Debian and have packaged some software which lets the >> boot scripts (/etc/rc[12345].d) run in parallel. It also supports >> visualisation of services, dependencies and timings. [...] >> One known bug is that the -ldb library is currently statically >> linked into the daemon, and it ought to be dynamically >> linked. I haven't yet figured how to bind the linker to a specific >> version of db that's known to be widely deployed. > Use whatever version you think is appropriate (say, db3) and let > dependencies do the rest of the work for you. IANDD but db3 is placed in /usr/lib and probably cannot be used for for a system-bootup software, /usr/ might not be mounted yet. Actually I am confused because there is /lib/libdb.so.3 in package libdb2. cu andreas
Re: request for package review - serel
In article <[EMAIL PROTECTED]> Leni Mayo <[EMAIL PROTECTED]> wrote: [...] > As this is the first release on debian, I'd be grateful if someone > with more packaging experience than myself could take a look at it, > especially since the installation process patches /etc/init.d/rc. > The .deb is at: http://www.fastboot.org/download/binaries/debian/ [...] Hello! * lintian serel_0.3.4-1.dsc W: serel source: out-of-date-standards-version 3.0.1 E: serel source: package-uses-debhelper-but-lacks-build-depends * Is this really a debian-native package, i.e. is serel debian-only? If not (and I think so), use the real upstream source and keep the debian-part in the diff.gz. wget http://www.fastboot.org/download/sources/serel-0.3.4.tar.gz mv serel-0.3.4.tar.gz serel_0.3.4.orig.tar.gz cd serel-0.3.4 dpkg-buildpackage -sd -rfakeroot -S -uc -us * dh_suidregister is depreceated. just my 2 cents. cu andreas
Re: request for package review - serel
On Fri, Aug 02, 2002 at 04:51:32PM +0200, Andreas Metzler wrote: > In article <[EMAIL PROTECTED]> Leni Mayo <[EMAIL PROTECTED]> wrote: > > As this is the first release on debian, I'd be grateful if someone > > with more packaging experience than myself could take a look at it, > > especially since the installation process patches /etc/init.d/rc. > > The .deb is at: http://www.fastboot.org/download/binaries/debian/ > > Hello! > * lintian serel_0.3.4-1.dsc > W: serel source: out-of-date-standards-version 3.0.1 > E: serel source: package-uses-debhelper-but-lacks-build-depends Also: $ lintian serel_0.3.4-1_i386.deb E: serel: file-in-etc-not-marked-as-conffile etc/default/serel E: serel: file-in-etc-not-marked-as-conffile etc/init.d/rc.serel.include E: serel: file-in-etc-not-marked-as-conffile etc/serel/serel.conf E: serel: file-in-etc-not-marked-as-conffile etc/serel/default.rdf E: serel: unregistered-script-in-etc-init.d /etc/init.d/rc.serel.include E: serel: non-standard-file-permissions-for-etc-init.d-script etc/init.d/rc.serel.include 0644 != 0755 W: serel: package-contains-upstream-install-documentation usr/share/doc/serel/INSTALL W: serel: extra-license-file usr/share/doc/serel/COPYING.gz (You can run lintian over the .changes file to check both at once.) At least the first four are serious - they mean that configuration file changes won't be preserved on upgrades. The fifth and sixth may also be a problem depending on how you're interacting with other init script subsystems - I haven't looked at the details. -- Colin Watson [EMAIL PROTECTED]
Re: request for package review - serel
Ick, I didn't notice this thread earlier... On Fri, 02 Aug 2002, Andreas Metzler wrote: > In article <[EMAIL PROTECTED]> Leni Mayo <[EMAIL PROTECTED]> wrote: > [...] > > As this is the first release on debian, I'd be grateful if someone > > with more packaging experience than myself could take a look at it, > > especially since the installation process patches /etc/init.d/rc. > > The .deb is at: http://www.fastboot.org/download/binaries/debian/ Make sure you read http://people.debian.org/~hmh/debconf2/debconf2-initscripts-bkg.ps.gz And you should also get the sysvinit and file-rc package sources, and understand them properly, how they work, how they connect themselves to the init script subsystem, etc. This way, you will know how init-script related utilities are implemented in Debian. serel must properly integrate itself with the lot of them. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
Re: Why debhelper doesn't add /usr/doc/package links creation/re
> > > Well, it seems we have to wait for new version of lintian in unstable. > there is a bug on lintian, the solution is known. I am finishing up a project right now and then intend to devote several weeks to getting lintian up to speed. lintian is a sanity checker but you are free to questions ITS sanity. No where in Debian is lintian used to enforce any rules. It is solely a tool to help you the developer make better packages and reduce the time you spend doing so. This does not mean that you should ignore lintian all of the time. But sometimes it gets policy wrong or policy changes.
Re: Debconf questions and purge
Jérôme Marant wrote: > I need to merge the wwsympa package into sympa. Both packages > use debconf. > I wonder how I should merge wwsympa debconf templates into sympa's. > In sympa, debconf variables start with sympa/ and wwsympa ones > start with wwsympa/ > If I keep the same variable name, I feel like I'm going to have > problem if the user decide to purge wwsympa, because of db_purge. > So do I really have to care for the purge and to rename variables? Well, you basically have two options: 1. Don't change the name. Put identically named wsympa/* templates into sympa and watch debconf do the right thing. (That is, when the new sympa is installed, it will mark the templates as shared between the two packages that contain them; then when wsympa is purged it will remove it from the owners list of the questions but keep them around since one other package still owns them. Reference counting.) 2. Change the names and in sympa's config script, use the GET and SET and FSET and FGET commands to copy the old values and seen flags of the old wsympa questions over. > A same kind of problem is likely to happen for the conffiles and other > non-conffiles configuration files that I move from wwsympa to sympa > and that are been removed in wwsympa postrm. I'm afraid you're on your own there; dpkg does not deal with shared conffiles well when the older package is removed I think it removes the conffile. -- see shy jo
How to upgrade a conflicting package
Hi, I have a package 'liba52-0.7.4-dev' that provides/conflicts/replaces 'liba52-dev'. There is also a 'liba52-0.7.3' with the same provide etc. The problem is I cannot install the newer package: zodiac:/home/micce# LANG=C dpkg -i liba52-0.7.4-dev_0.7.4-1_i386.deb dpkg: regarding liba52-0.7.4-dev_0.7.4-1_i386.deb containing liba52-0.7.4-dev: liba52-0.7.4-dev conflicts with a52dec liba52-0.7.3-dev provides a52dec and is installed. dpkg: error processing debian/UPLOAD/a52dec/liba52-0.7.4-dev_0.7.4-1_i386.deb (--install): conflicting packages - not installing liba52-0.7.4-dev Errors were encountered while processing: debian/UPLOAD/a52dec/liba52-0.7.4-dev_0.7.4-1_i386.deb zodiac:/home/micce# How should this be handled? Is is unavoidable that liba52-0.7.3-dev is first removed? TIA, Micce -- Mikael Hedin, MSc +46 (0)8 344979 (home) +46 (0)70 5891533 (mobile) [gpg key fingerprint = 387F A8DB DC2A 50E3 FE26 30C4 5793 29D3 C01B 2A22]
Re: Debconf questions and purge
Jerome> A same kind of problem is likely to happen for the conffiles Jerome> and other non-conffiles configuration files that I move from Jerome> wwsympa to sympa and that are been removed in wwsympa postrm. Joey> I'm afraid you're on your own there; dpkg does not deal with Joey> shared conffiles well when the older package is removed I think Joey> it removes the conffile. Surely you mean "when the older package is _purged_"? I have done "dpkg --remove oldname ; apt-get install newname" many times on my system, and I think it works. Of course, one has to know in advance a name change is afoot .. -- Ian Zimmerman, Oakland, California, U.S.A. GPG: 433BA087 9C0F 194F 203A 63F7 B1B8 6E5A 8CA3 27DB 433B A087 EngSoc adopts market economy: cheap is wasteful, efficient is expensive.
Re: Debconf questions and purge
Ian Zimmerman <[EMAIL PROTECTED]> writes: > Jerome> A same kind of problem is likely to happen for the conffiles > Jerome> and other non-conffiles configuration files that I move from > Jerome> wwsympa to sympa and that are been removed in wwsympa postrm. > > Joey> I'm afraid you're on your own there; dpkg does not deal with > Joey> shared conffiles well when the older package is removed I think > Joey> it removes the conffile. > > Surely you mean "when the older package is _purged_"? Yes, purged. > I have done "dpkg --remove oldname ; apt-get install newname" many > times on my system, and I think it works. It is ok with remove. -- Jérôme Marant http://marant.org
Re: Debconf questions and purge
Joey Hess <[EMAIL PROTECTED]> writes: > Jérôme Marant wrote: >> I need to merge the wwsympa package into sympa. Both packages >> use debconf. >> I wonder how I should merge wwsympa debconf templates into sympa's. >> In sympa, debconf variables start with sympa/ and wwsympa ones >> start with wwsympa/ >> If I keep the same variable name, I feel like I'm going to have >> problem if the user decide to purge wwsympa, because of db_purge. >> So do I really have to care for the purge and to rename variables? > > Well, you basically have two options: > > 1. Don't change the name. Put identically named wsympa/* templates into >sympa and watch debconf do the right thing. (That is, when the new >sympa is installed, it will mark the templates as shared between the >two packages that contain them; then when wsympa is purged it will >remove it from the owners list of the questions but keep them around >since one other package still owns them. Reference counting.) Smart ;-) I love this. You've made my day! >> A same kind of problem is likely to happen for the conffiles and other >> non-conffiles configuration files that I move from wwsympa to sympa >> and that are been removed in wwsympa postrm. > > I'm afraid you're on your own there; dpkg does not deal with shared > conffiles well when the older package is removed I think it removes the > conffile. I see no real solution to this. One disgusting way for non-conffiles would be to delete the removing part: if [ -e /var/lib/dpkg/info/wwsympa.postrm ]; then sed fi I think you won't like this, will you? ;-) -- Jérôme Marant http://marant.org
