Hello Steve,

thanks for your report. Maybe, you can help me with this bug or should I
ask on d-mentors/d-devel?

Steve Langasek schrieb am Fri 18. May, 20:19 (-0700):
> reopen 424976
> thanks
> 
> Hi Jörg,
> 
> xindy is still failing to build with the same error as before.

?-) I don't understand this.

http://buildd.debian.org/fetch.cgi?pkg=xindy;ver=2.2%7Ebeta2-2;arch=alpha;stamp=1179510778

** Using build dependencies supplied by package:
Build-Depends: debhelper (>= 5), dpatch, autotools-dev, flex, clisp-dev
Build-Depends-Indep: texlive-latex-base, texlive-lang-cyrillic, 
texlive-latex-recommended, cm-super
Checking for already installed source dependencies...
debhelper: already installed (5.0.49 >= 5 is satisfied)
dpatch: missing
autotools-dev: missing
flex: missing
clisp-dev: missing
Checking for source dependency conflicts...

So, it installs only the packages from Build-Depends, but later it calls 

 debian/rules build

The Debian policy says in section 7.6.

 The dependencies and conflicts they define must be satisfied (as
 defined earlier for binary packages) in order to invoke the targets in
 `debian/rules', as follows:[1]

 `Build-Depends-Indep', `Build-Conflicts-Indep'
      The `Build-Depends-Indep' and `Build-Conflicts-Indep' fields must
      be satisfied when any of the following targets is invoked:
      `build', `build-indep', `binary' and `binary-indep'.
       ^^^^^

So, why the build target is called even though the dependencies from
Build-Depends-Indep aren't satisfied?

I found this[1] posting from Andreas Metzler where he says: “And my
personal opinion in this respect is that a FBTFS bug in a package caused
by autobuilders no following policy strictly would be a serious bug. -
Policy simply is wrong […]” That's the newest statement I found about
build vs. Build-Depends-Indep.

Bye, Jörg.

[1] http://lists.debian.org/debian-devel/2003/12/msg01804.html
-- 
Da würde ich auch lieber den Panzerführerschein machen als den MCSE.
Bringt mehr, dürfte das gleiche kosten und macht sicher mehr Spaß.
                                   Jens Dittmar in de.comp.security

Attachment: pgppKuBj31n2S.pgp
Description: PGP signature

Reply via email to