Hi Davide, I believe I got it. Apparently there was some confusion how the trigger values are passed to the maintainer script and the following code in the postinst script might have changed over time:
for trigger in ${2}; do
case "${trigger}" in
('')
break
;;
(auctex-install-*)
FLAVORS="${FLAVORS}${FLAVORS:+ }${trigger#auctex-
install-}"
shift
;;
(/*)
FLAVORS="${FLAVORS}${FLAVORS:+ }<all>"
shift
;;
(*)
echo >&2 "${PROGNAME}:" \
"Unsupported trigger: ${trigger}"
exit 43
;;
If you'd be so kind to make your Git repo public (e.g. on alioth) then I could
confirm this.
Anyways. There's no reason for the "shift" statements in the above code since
you're looping over the quoted values in the second argument. The postinst
script is called like
postinst triggered 'auctex-install-emacs24 auctex-install-emacs23 auctex-
install-emacs-snapshot'
The shifts don't trouble as long as you have only 2 emacs versions installed
but the third call to shift will return error code 1 since there's no more
argument left to shift.
Just remove the shifts please.
I wonder, whether update-auctex-elisp gets called twice during the
installation of auctex? Once during the configure phase and second during the
trigger phase?
Regards,
Thomas Koch, http://www.koch.ro
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
