build dependencies not satisfied in hardy

[Olly Betts]

Binary package hint: xapian-omega

(I'm debian maintainer for xapian-core and xapian-omega, and an upstream developer...)

Sorry for not spotting this earlier, but hardy has xapian-omega 1.0.4-1 which has:

Build-Depends: debhelper (>= 4.1.22), libxapian-dev (>= 1.0.4), libxapian-dev (<= 1.0.4-9999), autotools-dev

But hardy has libxapian-dev 1.0.5-1 so xapian-omega would now FTBFS if rebuilt on hardy.

The build-dependency is overly conservative in this case, so there are two obvious ways to resolve this:

(a) Change to: "Build-Depends: debhelper (>= 4.1.22), libxapian-dev (>= 1.0.4), autotools-dev".

(b) Sync xapian-omega 1.0.5-1 from Debian unstable - changelog is:

xapian-omega (1.0.5-1) unstable; urgency=low

  * New upstream release.
    + Fixes compilation with latest GCC 4.3 snapshot. Closes: #455149
    + omindex now accepts '-f' as documented. Closes: #455526.
  * debian/control.in: Standards-Version: 3.7.3 (no changes required).
  * debian/control.in: Remove "perl" from "Suggests:" as perl is
    "Priority: essential". Policy section 3.5 says that such dependencies
    should be avoided.
  * debian/xapian-omega.prerm,debian/xapian-omega.postrm: prerm doesn't get
    the "purge" action, so replace the prerm with a postrm so templates get
    removed on purge. Closes: #455103
  * debian/control.in: The "Homepage:" header is now official, so convert
    "Homepage:" pseudo-header.

 -- Olly Betts <email address hidden> Sat, 22 Dec 2007 21:38:44 +0000

My recommendation would be (b), as this version has been out upstream and in Debian for over 3 months without problems being reported, and does fix a few bugs. Also, while xapian-core 1.0.5 and xapian-omega 1.0.4 should work correctly together without problems, it is a much less tested combination as most users will be using matching versions.

But I'd certainly understand if you'd prefer to go with (a) this close to the release date!

(Longer term, my feeling is that the upper bound should simply be "< 1.1.0" for 1.0 releases, since as of 1.0.0, the upstream policy is that releases should be source and binary compatible within a release series, except in extraordinary circumstances, and such a build-dependency would capture that policy pretty well).

If you need more information, please just ask.

[Luca Falavigna (dktrkranz)]

This is fixed in Intrepid, thanks.