Le mardi 01 décembre 2009, Norbert Preining a écrit : > On Di, 01 Dez 2009, Tanguy Ortolo wrote: > > But, when compiling againts libpoppler-dev 0.8.7-2, for instance: > > libpoppler 0.8 is in stable. > > testing contains libpoppler 0.10 > > why should there be any versioned dependency? Well, I thought it should be possible to build a package on a system with build dependencies installed. From the Debian Policy Manual: > If build-time dependencies are specified, it must be possible to build > the package and produce working binaries on a system with only > essential and build-essential packages installed and also those > required to satisfy the build-time relationships (including any > implied relationships). In particular, this means that version clauses > should be used rigorously in build-time relationships so that one > cannot produce bad or inconsistently configured packages when the > relationships are properly satisfied. If I understand that correctly, it means that, with the Build-Depends met, it should build. But it does not, because, contrary to what these Build-Depends say, libpoppler-dev 0.8 is not enough to satisfy the configure script, that looks for libpoppler-dev >= 0.10. Anyway, the debian/control lists libpoppler-dev (>= 0.8), that gives the impression that any libpoppler-dev >= 0.8 is enough to build luatex, which is wrong, as at least 0.10 is needed. If you do not care about the version dependency because the testing version is enough, assuming that compiles with the Policy Manual, I think you should only list libpoppler-dev, without version indication. -- Tanguy Ortolo
Attachment:
signature.asc
Description: Digital signature