On 2006-12-03 José Luis Tallón <[EMAIL PROTECTED]> wrote:
> Andreas Metzler wrote:
[...]
> > # reopening as neither an explanation was given nor a change was made
[...]
> > Why is it necessary? The only reason you would need it is if you used
> > debconf in preinst.
> Having debconf as a Pre-Depends (as recommended by the Policy and
> debconf's manual, AFAICR)
Hello,
I think your memory on that is off. I have just doublechecked both
policy and debconf to be sure, it does not suggest it.
The main interesting parts is this one:
You should not specify a `Pre-Depends' entry for a package before this
has been discussed on the `debian-devel' mailing list and a consensus
about doing that has been reached.
> is indeed more convenient than absolutely
> necessary. The reason why it is needed: automated testing tools such as
> piuparts fail horribly without a Pre-Depends (debconf is removed before
> imapproxy) -- go figure.
I am not 100% sure but afaict from reading policy both pre- and normal
depends should have the exactly same effect when removing or purging.
As a matter of fact I think I have found the source of the breakage,
there is a bug in imapproxy's postrm script - it unconditionally sources
/usr/share/debconf/confmodule. This is going to break for this
scenario:
1. piuparts is installed
2. apt-get remove piuparts (Not purged!)
3. apt-get remove debconf (No problem wth piuparts dependencies,
because they are not considered fr uninstalled packages.)
4. apt-get --purge remove piuparts
The fix is simple, the unconditiional sourcing of
/usr/share/debconf/confmodule is not necessary because
dh_installdebconf already does the correct thing:
---------------
# Automatically added by dh_installdebconf
if [ "$1" = purge ] && [ -e /usr/share/debconf/confmodule ]; then
. /usr/share/debconf/confmodule
db_purge
fi
# End automatically added section
---------------
and therefore this code can simply be deleted:
---------------
--- up-imapproxy-1.2.4/debian/imapproxy.postrm.orig 2006-12-07
12:21:02.000000000 -0700
+++ up-imapproxy-1.2.4/debian/imapproxy.postrm 2006-12-07 12:21:29.000000000
-0700
@@ -1,9 +1,6 @@
#! /bin/sh
# postrm script for imapproxy
-. /usr/share/debconf/confmodule
-db_version 2.0
-
set -e
# summary of how this script can be called:
@@ -25,7 +22,6 @@
;;
purge)
rm -f /etc/imapproxy.conf
- db_purge
;;
*)
---------------
> Of course, piuparts might be buggy as hell, but it is used widely enough
> to not be considered *that* buggy.
> Moreover, I can't test uninstalling everything down to "essential" to
> check whether this would become a real problem, so I'll have to trust
> our tools.
> I still cannot understand why is this Pre-Depends so important (for
> you?).
Because policy is probably the best thing about Debian at all and I
hate if it is ignored for no good reason at all.
> There are far worse dependency problems out there.
I did not stumble about them. If I take the time to find and report a
bug I do not like it all if it is simply closed without fix or an
explanation. I do realize this happened by accident not on purpose.
> Of course, I know darn well that we are just about to enter a deep
> freeze stage.
Yes, neither this bug nor the one found above (purging without debconf
fails) is release critical.
thanks for the consideration, cu andreas
--
The 'Galactic Cleaning' policy undertaken by Emperor Zhark is a personal
vision of the emperor's, and its inclusion in this work does not constitute
tacit approval by the author or the publisher for any such projects,
howsoever undertaken. (c) Jasper Ffforde
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
