Please sync xapian-bindings 1.0.5-1 (universe) from Debian unstable (main).

[Scott Kitterman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

 affects ubuntu/xapian-bindings
 status new
 importance wishlist
 subscribe ubuntu-universe-sponsors

FFe request to sync xapian-bindings 1.0.5-1 (universe) from Debian unstable (main).

Current package would FTBFS because xapian-core is to new. Need to bump to the
new version so the package can be built. The Debian maintainer explicitly packaged
this version to work with the infrastructure in Hardy.

Changelog since current hardy version 1.0.4-1:

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

  * debian/rules: Look for "CODENAME" and "debian/codename" rather than
    "COMPONENT" and "debian/component".
  * debian/rules: Strip out unused support for Ubuntu breezy since it reached
    end-of-life and we stopped building packages for it a while ago.
  * debian/control.in: Standards-Version: 3.7.3 (no changes required).
  * debian/patch: Remove patch for building tcl8 on latest sid as it is
    already in the upstream sources.
  * debian/patch: Add patch to fix installation of Ruby RDocs.
  * debian/patch: Add patch to fix "make check" for PHP4 (needed for some of
    the backports).
  * debian/libxapian-ruby1.8.install: Package the installed RDocs.
  * debian/control.in,debian/control-php.in: The "Homepage:" header is now
    official, so convert "Homepage:" pseudo-headers.
  * debian/rules: For Debian lenny and later, and Ubuntu hardy and later,
    make use of the new tcl and tcl-dev packages as the Debian Tcl/Tk policy
    describes.

 -- Olly Betts <email address hidden> Sun, 23 Dec 2007 01:30:45 +0000

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (GNU/Linux)

iD8DBQFH5IFGHajaM93NaGoRAqbbAJ9EWj+M3AoMx3GGzEqVC8o/fDPVtwCfbZZK
Le6x1t8GHm+xtYvUjp+He6g=
=s1hX
-----END PGP SIGNATURE-----

[StefanPotyra (sistpoty)]

ACK #1.

[Scott Kitterman (kitterman)]

[00:04] <ScottK2> sistpoty: Would you please ack Bug 204959
[00:04] <ubotu> Launchpad bug 204959 in xapian-bindings "Please sync xapian-bindings 1.0.5-1 (universe) from Debian unstable (main)." [Wishlist,New] https://launchpad.net/bugs/204959
[00:05] <ScottK2> It builds which is better we have now.
[00:05] <persia> Isn't that version also required to match the current libxapian?
[00:06] <ScottK2> Yes
[00:07] <ScottK2> But it's a new upstream, so I want an ack.
[00:09] <sistpoty> ScottK2: there are two rdepends... did the API change?
[00:10] <sistpoty> (in an incompatible way)
[00:10] <-- xtknight has left this server (Remote closed the connection).
[00:10] * ScottK2 looks.
[00:10] --> LucidFox has joined this channel (n=sikon@wikia/Sikon).
[00:11] <-- santiago-ve has left this server ("<?php if(HAS_NOTHING_TO_DO){die();} ?>").
[00:13] --> gordon_ has joined this channel (<email address hidden>).
[00:13] <-- gordon_ has left this server (Client Quit).
[00:14] <ScottK2> sistpoty: From reading Changelog and NEWS, no. Currently we have xapien-bindings and xapiend-core on different versions. I think having them the same and having the bindings buildable is way better than whatever risk there is of bumping.
[00:16] <sistpoty> ScottK2: hm.. I don't see a xapiend-core?
[00:17] <ScottK2> It would help if I could spell
[00:17] <ScottK2> https://launchpad.net/ubuntu/+source/xapian-core
[00:18] <sistpoty> heh
[00:18] <-- gordon has left this server (Remote closed the connection).
[00:19] <sistpoty> yes, that makes sense to me, ACK'd
[00:19] <ScottK2> Thanks

[Olly Betts (ojwb)]

> <sistpoty> ScottK2: there are two rdepends... did the API change?
> <sistpoty> (in an incompatible way)

Just to clarify (as debian packager and an upstream Xapian developer), xapian-core 1.0.4 and 1.0.5 are both API and ABI compatible (in general, Xapian 1.X.Y and 1.X.Z should be both ABI and API compatible, although we messed up with 1.0.0 and regrettably had to break the ABI for 1.0.1).

The reason that xapian-bindings needs a versioned build-dep on libxapian-dev is that it uses the C++ API more exhaustively than other dependent packages, and minor releases of xapian-core often extend the API/ABI.

It's worth noting that using matching xapian-core and xapian-bindings versions gets a lot more testing too.

Overall I'd say this is a pretty low risk sync.

[Steve Langasek (vorlon)]

Package(s) synced.