[Bug 1519887] Re: [MIR] xapian1.3-bindings

[Barry Warsaw]

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.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to xapian1.3-bindings in Ubuntu.
https://bugs.launchpad.net/bugs/1519887

Title:
  [MIR] xapian1.3-bindings

Status in xapian1.3-bindings package in Ubuntu:
  New

Bug description:
  [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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xapian1.3-bindings/+bug/1519887/+subscriptions