Package: debian-policy
Version: 3.9.8
Severity: normal

Hi!

Starting with dpkg 1.18.5, several maintainer script actions involving
a new package version, get that version as an argument after the old
version, because they could not get it in any other easy way. The new
version was only available in the new package somewhere in the
filesystem.

One previous way to workaround this limitation was to inject the new
version at build time into those maintainer scripts, which is rather
cumbersome, when dpkg already knows at run-time which new version it
is handling.

This was proposed and discussed some time ago in the debian-dpkg
 mailing list.

The list of the actions and their new arguments, from the dpkg
changelog entry are:

  - <new-postrm> failed-upgrade <old-version> <new-version>
  - <new-postrm> abort-install <old-version> <new-version>
  - <new-postrm> abort-upgrade <old-version> <new-version>
  - <new-preinst> install <old-version> <new-version>
  - <new-preinst> upgrade <old-version> <new-version>
  - <new-prerm> failed-upgrade <old-version> <new-version>

Please, update the relevant section to mention those new arguments.

Thanks,
Guillem

Reply via email to