Thibaut Paumard wrote: > Indeed, the problem is that per the instructions, I've modified my > update-yorickdoc utility to call dpkg-trigger when invoked from a > package's postinst. dpkg already triggers yorick-doc once after > unpacking the newly installed packages, which is sufficient. Later, dpkg > configures the various packages in several passes, because of the order > of dependencies. Each pass triggers yorick-doc again, and I've gained > close to nothing (depending on the dependencies, the situation can be > slightly better, identical, or worse than before, if each package need to > be configured in its own run). This can be fixed in apt, by passing the --no-triggers option to each dpkg run, followed by running dpkg --configure --pending once at the end to run all the triggers. See bug #473461. > 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. -- see shy jo
Attachment:
signature.asc
Description: Digital signature