[needs-packaging] Upgrade package to 2.0.10

Bug #709089 reported by eteq
This bug affects 2 people
Affects Status Importance Assigned to Milestone
pyzmq (Ubuntu)
Fix Released
Bhavani Shankar

Bug Description

This is a request to update the pyzmq package to version 2.0.10 or There's already a debian package of version 2.0.10 (http://packages.qa.debian.org/p/pyzmq.html - on the experimental branch), but there is a newer bugfix release, available from the project as of January 2011: https://github.com/zeromq/pyzmq/downloads

A more recent version of this package is crucial for supporting the in-development versions of ipython, easing the process of installing. Further, it's problematic to have zmq itself be version 2.0.10, but the python bindings are for a much earlier (non-release) version. So applications that come out before the next version of Ubuntu would probably be forced to manually install a more up-to-date version to use pyzmq at all, unless it is upgraded.

description: updated
description: updated
description: updated
tags: added: needs-packaging
Revision history for this message
Brian Murray (brian-murray) wrote :

*** This is an automated message ***

This bug is tagged needs-packaging which identifies it as a request for a new package in Ubuntu. As a part of the managing needs-packaging bug reports specification, https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-packaging bug reports have Wishlist importance. Subsequently, I'm setting this bug's status to Wishlist.

summary: - Upgrade package to 2.0.10
+ [needs-packaging] Upgrade package to 2.0.10
Changed in pyzmq (Ubuntu):
importance: Undecided → Wishlist
Revision history for this message
eteq (erik-tollerud) wrote :

Actually, I'm not sure if the needs packaging (and therefore wishlist) categorization is correct - http://packages.qa.debian.org/p/pyzmq.html has been updated to 2.0.10-1, so there may not be need to do anything other than grab the debian package. Does that mean "need packaging" no longer applies, or does "need packaging" still apply to adapt the Debian package to whatever Ubuntu wants?

Revision history for this message
Bhavani Shankar (bhavi) wrote :

I intend to look into this once I reach home


Changed in pyzmq (Ubuntu):
status: New → In Progress
assignee: nobody → Bhavani Shankar (bhavi)
Revision history for this message
Thomas Kluyver (takluyver) wrote :

I knew this was going to cause confusion. Debian's 2.0.10-1 is upstream's 2.0.10 (the -1 indicates it's the first debian revision). Upstream has now changed their version numbering scheme so it doesn't conflict, and the bugfix release is If you look at the news box on the Debian page, it says that 2.0.10-1 was accepted in November, i.e. before the extra bugfix release from upstream.

So, ideally it's a "needs packaging", but if that's not feasible, syncing debian's experimental version is the next best thing.

Revision history for this message
Bhavani Shankar (bhavi) wrote :

New version from experimental synced and uploaded into natty repos


Changed in pyzmq (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions