Le 16 mai 08 à 13:47, Thibaut Paumard a écrit :
Le 15 mai 08 à 21:54, Joey Hess a écrit :
If I remove the dpkg-trigger call from my update- script, everything
goes fine. I still need to check what happens for upgrades rather
than
installs (but I will require some seep before I do).
So I'm currently thinking that I should, indeed, remove the dpkg-
trigger
call from the script. Any thought?
You generally only need a file trigger, or an update- script that
manually triggers, and not both.
I understand that. Currently, the add-ons call the update- script,
so the script should remain as long as the add-on packages have not
been fixed. The transition plan suggested in triggers.txt.gz says
that update-<package> should be modified to call dpkg-trigger, but
I'm under the impression that in my case, it should just become a
no-op. Note that I'm the only maintainer for Yorick add-on packages
so far, so I have a good understanding of the situation and I can
usually reach a consensus with myself easily :-) But, still, I
prefer to think twice before I upload...
By the way, the postinst/postrm lines which call update-yorickdoc
in add-on packages are added by dh_installyorick. I plan on
modifying it right away to not generate these lines anymore. After
that, a simple rebuild of the add-on packages would be sufficient
to fix them.
If anyone fancies having a say on the color of the bike-shed, my
updated package is available for review on my personal repo:
dget http://lesia.obspm.fr/~paumard/debian/pool/main/y/yorick/
yorick_2.1.05+dfsg-5~rc1.dsc
I'll welcome any comment (on anything by the way, not only triggers
support, a review is always good). I plan on uploading to unstable
next week.
Best regards, Thibaut.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
