[MIR] xapian1.3-bindings

[Barry Warsaw]

[Availability]
xapian1.3-bindings is already in universe.

[Rationale]
python3-xapian1.3 needs to be included in main since the upload of apt-xapian-index 0.47ubuntu3 because this version switches to Python 3 as part of the "get Python 2 off the default images" initiative for Xenial. Source package xapian1.3-bindings is based off of the Xapian 1.3 development release (what will be Xapian 1.4 when that is released). xapian-bindings (the source for python-xapian) is already in main.

[Security]
Should have the same security constraints as xapian-bindings since its developed by the same upstream and will have the same security considerations once Xapian 1.4 is released. The source package is well maintained by members of Ubuntu Foundations.

[Quality assurance]
See Security - similar consideration.

[Dependencies]
Similar, although this package also B-D on libxapian-1.3-dev so xapian1.3-core will also need to be MIR'd.

[Barry Warsaw (barry)]

See LP: #1519890

[Michael Terry (mterry)]

- Needs a team bug subscriber (~foundations-bugs would make sense)
- So I buy that this is just a continuation of xapian-bindings. Is Debian also going to split the packages like this, or was this just to get the code into Ubuntu faster without forcing an actual update to xapian 1.3 yet on everyone else?

[Barry Warsaw (barry)]

Oops, I actually did add a bug subscriber but accidentally did a personal one instead of the team. I've fixed that for xapian1.3-bindings and xapian1.3-core now.

I don't think Debian will follow us here. The timing should allow Debian to adopt Xapian 1.4 sometime farther along the Stretch release cycle (hopefully), but we need to get rid of the Python 2 dependency sooner.

I should also note that the plan is still to drop Software Center from Xenial. When that happens, the entire stack of apt-xapian-index and xapian1.3-* should drop out of main. So this might be a temporary MIR anyway (it's currently needed because the Python 3 port of apt-xapian-index 0.47ubuntu3 is in depwait).

[Michael Terry (mterry)]

Gotcha. Why not just update the existing xapian packages to 1.3? Does 1.3 break compatibility?

[Barry Warsaw (barry)]

On Nov 27, 2015, at 01:38 PM, Michael Terry wrote:

>Gotcha. Why not just update the existing xapian packages to 1.3? Does
>1.3 break compatibility?

I think Doko packaged these up separately just to be cautious and allow a
staged migration path.

[Michael Terry (mterry)]

I guess my point was that if we don't have enough confidence in 1.3 to actually upgrade the package, that doesn't speak to its readiness for main.

But I get that this is hopefully a temporary solution and they'll fall back to universe. And we won't have messed with the 1.2 package, thus staying closer to Debian.

So since this is just a version update of software already in main, maintained by the foundations team, and is temporary anyway... approved.

[Barry Warsaw (barry)]

@mterry: This was marked Fix Committed, but xapian1.3-bindings is still in universe, and it's still blocking apt-xapian-index. What more needs to be done to transition this to main?

[Michael Terry (mterry)]

Upload something that build-depends or depends on xapian1.3-bindings. Then an archive admin will notice (or you can poke them) that there is a component mismatch, and then see that it has an approved MIR and promote it for us. I'm not an archive admin, so I can't do that myself.

[Adam Conrad (adconrad)]

Promoted.