FTBFS of other packages due to dpkg-trigger bug in texlive-base

On Di, 05 Mai 2009, Moshroum wrote:
> Setting up texlive-base (2007.dfsg.2-4) ...
> Running mktexlsr. This may take some time... done.
> Building format(s) --all.
> This may take some time... done.
> dpkg-trigger: dpkg-trigger must be called from a maintainer script (or with a --by-package option)
> dpkg: error processing texlive-base (--configure):

Well, I have no idea what is the breakage on Ubuntu here, but on Debian
it does work.

And, the warning is just rubbish, we *are* running from a maintainer
script. No idea what has been changed in the enviromental variables but
I guess that is a bug in dpkg-trigger that does not recognize that it is
running from a maintainer script.

Best wishes

Norbert

-------------------------------------------------------------------------------
Dr. Norbert Preining <email address hidden> Vienna University of Technology
Debian Developer <email address hidden> Debian TeX Group
gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
SMEARISARY (n.)
The correct name for a junior apprentice greengrocer whose main duty
is to arrange the fruit so that the bad side is underneath. From the
name of a character not in Dickens.
   --- Douglas Adams, The Meaning of Liff

This bug was fixed in the package s3d - 0.2.1-14

---------------
s3d (0.2.1-14) unstable; urgency=low

  * Add function and structure manpages for libs3d2 and libs3dw
  * debian/patches:
    - Add 111-xmlto-documentation.patch, workaround for LP: #372243 by
      using xmlto instead of docbook-utils for documentation generation
  * debian/control:
    - Depend on xmlto as new tool to generate the html documentation
    - Update Depend on >=docbook-xml-4.5 for DocBook 4.5 DTDs

 -- Ubuntu Archive Auto-Sync <email address hidden> Thu, 14 May 2009 17:48:38 +0100

The same thing just happened to sane-backends on PPC:
https://launchpad.net/ubuntu/+source/sane-backends/1.0.20-3ubuntu1/+build/1030293

Hm, maybe it is only a buildserver problem. I tried to install a ubuntu karmic inside a qemu-system-ppc and afterwards docbook-utils. The install went fine and didn't cause the dpkg-trigger bug.

This bug also shows that some packages aren't well written. An example is the pdns package which also has the dependencies for arch independent packages inside the normal Build-Depends instead of Build-Depends-Indep. This doesn't fix that bug, but such packages wouldn't have been affected by this bug.

don't open ton of tasks this way you will spam all the subscriber to any of the tasks for every comment on other component

could somebody close all the tasks there and open different bugs for each software?

Also happens in libraw1394:
http://launchpadlibrarian.net/27565560/buildlog_ubuntu-karmic-powerpc.libraw1394_2.0.2-2ubuntu1_FAILEDTOBUILD.txt.gz

Will not open new bugs as they would have to release an update just to workaround a broken build server.