Re: Bug#18033: samba: No error chk in postinst
Hi.
Eloy Paris wrote:
> [gpp10] wrote:
> >Due to a "dpkg-deb subprocess paste" thing samba fails to install.
> >At this point the postinst is called with the following arguments:
> >
> > abort-upgrade 1.9.18p2-1
> >
> >which it fails to honour. Please check the Policy Manual, section 2.3.8.
> I checked the Policy Manual but could not understand a word on how to make
> my package honour the abort-upgrade. How should I do this?
The gory details are in the packaging manual /usr/doc/dpkg/packaging.html
> In any case, the error you were getting was caused because samba-1.9.18p2-1
> included man pages that were part of other packages. I think this is the
> real bug and that is fixed in 1.9.18p2-2 that is waiting in master's Incoming.
I agree.
> I am not closing this bug report until I get an understanding on how I
> should support abort-upgrade in my scripts.
OK. Here are the possible calls of your postinst... This is only my
opinion as to the stated aims of these commands, based on the contents
of the packaging manual. A dpkg guru might differ.
1. postinst configure most-recently-configured-version
This is the standard one: "Please configure version X of this pkg"
2. old-postinst abort-upgrade new-version
This is also fairly common: "An error occured unpacking a new version
of this package, please try and un-do whatever prerm upgrade did (and
do it silently)."
3. conflictor's-postinst abort-remove in-favour package new-version
"We tried to remove you (prerm remove) in favour of another,
conflicting package, but something went wrong, please try and un-do
whatever the prerm did (and do it silently)."
4. deconfigured's-postinst abort-deconfigure in-favour \
failed-install-package version removing conflicting-package version
"We tried to deconfigure you (prerm deconfigure) as we wanted to
install a conflicting pkg, but something went wrong, please try and
un-do whatever the prerm did (and do it silently)."
Summary:
postinst abort-upgrade undoes prerm upgrade
postinst abort-remove undoes prerm remove
postinst abort-deconfigure undoes prerm deconfigure
In most cases the prerms do the same thing: stop daemons. So, I
imagine you should just restart them (and do NOT ask the admin user
any silly questions as they were already answered last time).
IMHO,
Giuliano.
--
mail: gpp10@cam.ac.uk / myxie@debian.org
PGP key ID: 93898735 / key available from public key servers
home: +44 1223 561237 / 547 Newmarket Road, Cambridge CB5 8PA, UK
work: +44 1223 332127 / Magdalene College, Cambridge CB3 0AG, UK
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: