Can't import avg from libavg in Jaunty

Bug #363436 reported by Alex Harrington
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libavg (Ubuntu)
Fix Released
High
Siegfried Gevatter
Jaunty
Fix Released
High
Siegfried Gevatter

Bug Description

Hi

I've been using python-libavg on intrepid without problems, but since I upgraded to Jaunty, I don't seem to be able to import avg anymore:

alex@alex-laptop:~/libavg/eingangsmonitore/monitor1$ python -c "import avg"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ImportError: No module named avg
alex@alex-laptop:~/libavg/eingangsmonitore/monitor1$ python -c "import libavg"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ImportError: No module named libavg

The eingangsmonitore code from libavg doens't work anymore either.

I tried apt-get remove python-libavg / apt-get install python-libavg and problem persists...

TEST CASE:

sudo apt-get install python-libavg
enter a Python shell (type python)
then type import libavg
see the error as above (no module named libavg).
exit the Python shell with ctrl d

Install the updated package from jaunty-proposed
enter a Python (2.6 - the Jaunty default) shell (type python)
then type import libavg
see no error.
exit the Python shell with ctrl d

Install the updated package from jaunty-proposed
enter a Python 2.5 shell (type python2.5)
then type import libavg
see no error.
exit the Python 2.5 shell with ctrl d

If it successfully import in both supported python versions, it passes verification. It will fail in Python 2.4. This is expected. Python 2.4 is not a supported Python version for Jaunty.

Related branches

Revision history for this message
Alex Harrington (alexharrington) wrote :

FYI I tried this on a new install Jaunty updated to today and have the same issue.

Revision history for this message
Scott Kitterman (kitterman) wrote :

Confirmed:

$ python
Python 2.6.2 (release26-maint, Apr 19 2009, 01:56:41)
[GCC 4.3.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import libavg
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: No module named libavg
>>>
$ python2.5
Python 2.5.4 (r254:67916, Apr 4 2009, 17:55:16)
[GCC 4.3.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import libavg
>>>

Changed in libavg (Ubuntu):
importance: Undecided → High
status: New → Triaged
Changed in libavg (Ubuntu):
assignee: nobody → Siegfried Gevatter (RainCT) (rainct)
Changed in libavg (Ubuntu):
status: Triaged → In Progress
Revision history for this message
Siegfried Gevatter (rainct) wrote :

The attached changes fix this. ScottK, does look OK to you?

Revision history for this message
Scott Kitterman (kitterman) wrote :

Yes.

Changed in libavg (Ubuntu Jaunty):
assignee: nobody → rainct
importance: Undecided → High
milestone: none → jaunty-updates
status: New → In Progress
Revision history for this message
Cody A.W. Somerville (cody-somerville) wrote :

ACK.

description: updated
Revision history for this message
Scott Kitterman (kitterman) wrote :

Accepted libavg into jaunty-proposed-proposed; please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Revision history for this message
Alex Harrington (alexharrington) wrote :

Hi Scott / Siegfried

I can confirm that fixes it for me:
alex@alex-laptop:~$ python
Python 2.6.2 (release26-maint, Apr 19 2009, 01:56:41)
[GCC 4.3.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import libavg
>>> libavg
<module 'libavg' from '/usr/lib/python2.6/dist-packages/libavg/__init__.pyc'>
>>> quit()
alex@alex-laptop:~$ python2.5
Python 2.5.4 (r254:67916, Apr 4 2009, 17:55:16)
[GCC 4.3.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import libavg
>>> libavg
<module 'libavg' from '/usr/lib/python2.5/site-packages/libavg/__init__.pyc'>
>>> quit()

Thanks for your help with this.

Cheers

Alex

tags: added: verification-done
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libavg - 0.8.0-2ubuntu2.1

---------------
libavg (0.8.0-2ubuntu2.1) jaunty-proposed; urgency=low

  * Stable Release Update (LP: #363436).
  * debian/control:
     - Change "XS-Python-Version" from "2.5" to ">= 2.5", so that it
       gets build for Python 2.6.
  * debian/rules:
     - Move Python 2.6 stuff from site-packages to dist-packages.

 -- Siegfried-Angel Gevatter Pujals <email address hidden> Thu, 23 Apr 2009 23:15:08 +0200

Changed in libavg (Ubuntu Jaunty):
status: In Progress → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote :

copied to karmic

Changed in libavg (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

Remote bug watches

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