Package is obsolete and should be removed

Bug #1660216 reported by Olly Betts
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
apt-xapian-index (Ubuntu)
Fix Released
Undecided
Barry Warsaw
xapian1.3-bindings (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

This package is obsolete now that xapian-bindings 1.4 has been synced from Debian, and should be
removed. It's a development snapshot of upstream code so won't get any sort of upstream support.

Revision history for this message
Steve Langasek (vorlon) wrote :

This package is still in use by apt-xapian-index. How should this be handled? Is python3-xapian a drop-in replacement for python3-xapian1.3?

Changed in xapian1.3-bindings (Ubuntu):
status: New → Incomplete
Revision history for this message
Olly Betts (ojwb) wrote :

I've not looked at how it was packaged, but the upstream code looks to be compatible.

Revision history for this message
Olly Betts (ojwb) wrote :

Incidentally, please note that although launchpad lists me as "maintainer" of this package, I had nothing to do with creating it - I guess I'm listed there as it was forked from a package I maintain in Debian, and someone was too slack to update the metadata properly.

Revision history for this message
Steve Langasek (vorlon) wrote :

ok, opened a task on apt-xapian-index so that this can be dealt with first before removal.

> Incidentally, please note that although launchpad lists me as "maintainer"
> of this package, I had nothing to do with creating it - I guess I'm listed
> there as it was forked from a package I maintain in Debian, and
> someone was too slack to update the metadata properly.

Apologies; there is a policy for maintainer fields in Ubuntu, https://wiki.ubuntu.com/DebianMaintainerField, which was definitely not followed here. It looks like the correct solution in this case is to just remove the package.

Changed in apt-xapian-index (Ubuntu):
status: New → Triaged
Steve Langasek (vorlon)
Changed in apt-xapian-index (Ubuntu):
assignee: nobody → Barry Warsaw (barry)
Revision history for this message
Barry Warsaw (barry) wrote :

IIRC, the a-x-i dependency on xapian1.3-bindings was because at the time only 1.3 support Python 3. I'll do some simple testing to see if we can just use python3-xapian. I suspect that will work just fine.

Changed in apt-xapian-index (Ubuntu):
status: Triaged → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package apt-xapian-index - 0.47ubuntu12

---------------
apt-xapian-index (0.47ubuntu12) zesty; urgency=medium

  * d/control: Drop the explicit Depends/Build-Depends on
    python3-xapian1.3 since that was a development snapshot we only used
    in our port to Python 3. Straight up python3-xapian (1.4) has
    everything we need. (LP: #1660216)

 -- Barry Warsaw <email address hidden> Mon, 03 Apr 2017 13:29:18 -0400

Changed in apt-xapian-index (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Steve Langasek (vorlon) wrote :

Removing packages from zesty:
 xapian1.3-bindings 1.3.4-0ubuntu1 in zesty
  python-xapian1.3 1.3.4-0ubuntu1 in zesty amd64
  python-xapian1.3 1.3.4-0ubuntu1 in zesty arm64
  python-xapian1.3 1.3.4-0ubuntu1 in zesty armhf
  python-xapian1.3 1.3.4-0ubuntu1 in zesty i386
  python-xapian1.3 1.3.4-0ubuntu1 in zesty powerpc
  python-xapian1.3 1.3.4-0ubuntu1 in zesty ppc64el
  python-xapian1.3 1.3.4-0ubuntu1 in zesty s390x
  python3-xapian1.3 1.3.4-0ubuntu1 in zesty amd64
  python3-xapian1.3 1.3.4-0ubuntu1 in zesty arm64
  python3-xapian1.3 1.3.4-0ubuntu1 in zesty armhf
  python3-xapian1.3 1.3.4-0ubuntu1 in zesty i386
  python3-xapian1.3 1.3.4-0ubuntu1 in zesty powerpc
  python3-xapian1.3 1.3.4-0ubuntu1 in zesty ppc64el
  python3-xapian1.3 1.3.4-0ubuntu1 in zesty s390x
Comment: Unused, obsoleted by current xapian-bindings; LP: #1660216
1 package successfully removed.

Changed in xapian1.3-bindings (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.