[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: (fwd) Draft spec for new dpkg "triggers" feature

Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de> wrote:

> Frank Küster <frank@debian.org> writes:
>>   However, in this case an additional feature which I didn't find would
>>   be great: In case the triggered action fails and the package that was
>>   triggered is put into failed-config state, it would be very good to
>>   somehow be able to know: "Which package(s) activated the trigger?".
>>   [...]
> Say I install buggy-updmap-package first and then udpmap1-package and
> udpmap2-package.
> The second time around the updmap would still fail and claim that
> udpmap1-package and udpmap2-package triggered it. But both are not to
> blame.

There is no second time:  If you install the three packages in one dpkg
run, the trigger will be only run once.  All three packages would then
be listed as "has activated the failed trigger":  That's better than
none, since I only need to check these three packages and not all N
installed packages that might activate the trigger.

If you first install the buggy package in one run, you can't install the
others, since they will depend on the package that contains updmap and
provides the trigger, which will be failed-config.

> I think you have to make the triger itself report a reasonably
> helpfull error message to pinpoint the broken file causing the
> failure. Anything else will just add useless information to
> bugreports.

Currently, when updmap is run by a TeX package that follows the TeX Task
Force's recommendations, it will fail with a message that tells the user
to include /tmp/updmap.XF23012 in the bug report.  Many users do not do
that - however most post the apt-get/dpkg error.  Therefore I think it
would help us if dpkg said something like:

dpkg: failed running trigger '/etc/texmf/updmap.d' which was triggered by
tex-fonts-foo texlive-fonts-extra thaifonts-extra

> I think triggers as specified work without depends. You just trigger
> them and if tex-common happens to be installed it gets the
> trigger. Otherwise nothing happens.

Yep, missed that.

Regards, Frank
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)

Reply to: