Ubuntu
libmusicbrainz-2.0 package

Missing Python bindings

Bug #35280 reported by Jason Gerard DeRose
22
Affects Status Importance Assigned to Milestone
libmusicbrainz-2.0 (Ubuntu)
Invalid
Medium
Unassigned
libmusicbrainz-2.1 (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

I'd really like to see the Python bindings for libmusicbrainz in Dapper, and I'm more than willing to help if you can point me in the right direction.

From looking at changelog.Debian, I can't quite tell why the Python bindings are no longer packaged. Disagreements about how they were packaged in Debian, it seems? How can this be fixed? Or was it a problem with the quality or completeness of bindings upstream?

Given my bias as the developer of a music player/ripper/burner written in Python that uses MusicBrainz, it seems impossibly rude to remove them. ;) (Yes, I'm just teasing, but I'd really like my player to run on Dapper.)

So again, I'll gladly help if you explain to me roughly what the problem is.

Revision history for this message
Matt Zimmerman (mdz) wrote :

Rejecting task for old library; bug remains open

Changed in libmusicbrainz-2.0:
status: Unconfirmed → Rejected
Revision history for this message
Jason Gerard DeRose (jderose) wrote : Re: [Bug 35280] Re: Please include Python bindings in Dapper

It was by mistake that I filed it for libmusicbrainz-2.0, which I
realize is irrelevant for Dapper. So sorry about that.

Still, why isn't the Python package being built? Is it because of an
upstream problem with the library, or because of a packaging problem?

Thanks,
Jason

Matt Zimmerman wrote:
> Rejecting task for old library; bug remains open
>
> ** Changed in: libmusicbrainz-2.1 (Ubuntu)
> Severity: Normal => Wishlist
>
> ** Changed in: libmusicbrainz-2.0 (Ubuntu)
> Status: Unconfirmed => Rejected

Revision history for this message
Lukáš Lalinský (luks) wrote : Re: Please include Python bindings in Dapper

After talking to Daniel Holbach (he changed the package), the python bindings were removed because of Build-Depends on python-ctypes which is only in universe, while libmusicbrainz-2.1 source package is in main -- it isn't possible to build python*-musicbrainz packages and upload them to universe.

So, I've updated 2.1.2-2ubuntu3 package by adding a patch to remove build dependency on ctypes and readded the Python bindings. Result is here:

http://users.musicbrainz.org/~luks/ubuntu/dists/dapper/main/source/libmusicbrainz-2.1_2.1.2-2ubuntu3+luks.diff.gz
http://users.musicbrainz.org/~luks/ubuntu/dists/dapper/main/source/libmusicbrainz-2.1_2.1.2-2ubuntu3+luks.dsc
http://users.musicbrainz.org/~luks/ubuntu/dists/dapper/main/source/libmusicbrainz-2.1_2.1.2.orig.tar.gz

Here are changed I've made to the package:

http://users.musicbrainz.org/~luks/libmb21_noctypes.diff

Ilmari Vacklin (wolverian)
Changed in libmusicbrainz-2.1:
status: Unconfirmed → Confirmed
Revision history for this message
Lukáš Lalinský (luks) wrote :

Syncing with Debian will fix this. The new version, 2.1.3, doesn't need python-ctypes as a build dependency, so the python bindings can be included again and uploaded to universe.

Revision history for this message
bramvandijk (bram-van-dijk) wrote :

Right now we are at version 2.1.4 already, but still the python bindings are removed from the Ubuntu package. Even though Lukas indicates that there is no reason for it anymore. He gave a solution here: https://bugs.launchpad.net/ubuntu/+source/libmusicbrainz-2.1/+bug/74300 .

So, is this just a forgotten issue, or is there a new reason for not including python-musicbrainz?

Revision history for this message
Kjell Braden (afflux) wrote :

python-musicbrainz is included in gutsy.

Changed in libmusicbrainz-2.1:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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