Le mardi 28 avril 2009 à 11:45 +0200, Rene Engelhard a écrit : > > Préparation du remplacement de openoffice.org-emailmerge 1:3.0.1-11 (en utilisant .../openoffice.org-emailmerge_1%3a3.0.1-11_all.deb) ... > > Removing extension org.openoffice.legacy.mailmerge.py... > > ERROR: python-loader:<type 'exceptions.ImportError'>: No module named pythonloader, traceback follows > > no traceback available > > > > unopkg failed. > > done. > > Dépaquetage de la mise à jour de openoffice.org-emailmerge ... > > > > Either you pre-depend on python-uno or you ensure that python-uno is > > functional when simply unpacked (and not configured). Or you stop removing No, this doesn’t work. There is absolutely no guarantee that dependencies will be unpacked at the time the preinst is run. > Tell that our beloved new python policy guys with pycentral/pysupport, please. > Where the stuff is only there after the packages' postinst ran. Since this won’t work, you shouldn’t bother with that. There is absolutely nothing specific to Python here. > > the extension in the preinst and do everything in the postinst. > > No, it has to be removed in the preinst, because the postinst registers the > *new* one, and the old one should be gone before the new one gets installed. > Otherwise you might get interesting effects.. > > Looks like I need a Pre-Depends: on python-uno. sigh. You need a Pre-Depends on whatever is used in the preinst. This is why it is strongly discouraged to do anything funky in the preinst. If you have stuff to deconfigure during upgrades, you need to do it, if possible, in the prerm of the old package. -- .''`. Josselin Mouette : :' : `. `' “I recommend you to learn English in hope that you in `- future understand things” -- Jörg Schilling
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=