Ubuntu
pyinotify package

pyinotify's libc version check fails on Karmic

Bug #408600 reported by Facundo Batista
224
This bug affects 36 people
Affects Status Importance Assigned to Milestone
Ubuntu One Client
Invalid
Undecided
Unassigned
pyinotify (Fedora)
Fix Released
Medium
pyinotify (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: python-pyinotify

pyinotify, in the file /usr/lib/pymodules/python2.6/pyinotify.py, it's doing the following test:

if LIBC_VERSION < '2.4':
    raise UnsupportedLibcVersionError(LIBC_VERSION)

Today libc6 was upgraded to 2.10... and this check started to fail, as it comparse *strings*, not numbers.

Note that this is critical, because it prevents completely the module from start

Tags: packaging

Related branches

lp:ubuntu/karmic/pyinotify
Revision history for this message
In , Ben (ben-redhat-bugs) wrote :

Description of problem:
python-inotify does not check for the glibc version correctly. I got the following trace today:

Traceback (most recent call last):
  File "/usr/bin/git-cola", line 59, in <module>
    main()
  File "/usr/lib/python2.6/site-packages/cola/main.py", line 138, in main
    ctl = Controller(model, view)
  File "/usr/lib/python2.6/site-packages/cola/controllers/main.py", line 197, in __init__
    self.start_inotify_thread()
  File "/usr/lib/python2.6/site-packages/cola/controllers/main.py", line 1085, in start_inotify_thread
    from cola.inotify import GitNotifier
  File "/usr/lib/python2.6/site-packages/cola/inotify.py", line 14, in<module>
    import pyinotify
  File "/usr/lib/python2.6/site-packages/pyinotify.py", line 103, in <module>
    raise UnsupportedLibcVersionError(LIBC_VERSION)
pyinotify.UnsupportedLibcVersionError: Libc 2.10.1 is unsupported, requires at least Libc 2.4

Version-Release number of selected component (if applicable):
% rpm -q glibc python-inotify
glibc-2.10.1-1.x86_64
python-inotify-0.8.1-2.git20090208.fc11.noarch
Additional info:

Revision history for this message
In , Terje (terje-redhat-bugs) wrote :

I have sent a patch upstream fixing this. Will rebase source and release
updated package soon.

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

python-inotify-0.8.6-1.git20090518.fc10 has been submitted as an update for Fedora 10.
http://admin.fedoraproject.org/updates/python-inotify-0.8.6-1.git20090518.fc10

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

python-inotify-0.8.6-1.git20090518.fc9 has been submitted as an update for Fedora 9.
http://admin.fedoraproject.org/updates/python-inotify-0.8.6-1.git20090518.fc9

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

python-inotify-0.8.6-1.git20090518.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/python-inotify-0.8.6-1.git20090518.fc11

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

python-inotify-0.8.6-1.git20090518.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

python-inotify-0.8.6-1.git20090518.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

python-inotify-0.8.6-1.git20090518.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.

Revision history for this message
John O'Brien (jdobrien) wrote :

This seems to have been corrected upstream.

Revision history for this message
James Henstridge (jamesh) wrote :

There was a report of this bug on the #ubuntuone IRC channel today. As a work around, I directed the user to remove the two offending lines from pyinotify.py.

The upstream fix for this problem is:

http://git.dbzteam.org/?p=pyinotify.git;a=blobdiff;f=pyinotify.py;h=9fb0031055e42d4bbda56ef5386c4f6c7391c311;hp=0bfc379a919234a7bb6caa18d47315a8da9cc472;hb=affbbb02dec05dc0d5d75508ff1258587b54d7d1;hpb=d8e42159304f73440f1b05c01f5e4bec00ee506a

It doesn't look like any new releases have been made since the fix went in.

James Henstridge (jamesh)
summary: - Bad libc version control
+ pyinotify's libc version check fails on Karmic
Krzysztof Klimonda (kklimonda)
Changed in pyinotify (Ubuntu):
assignee: nobody → Krzysztof Klimonda (kklimonda)
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Krzysztof Klimonda (kklimonda) wrote :

A patch cherry picked from upstream (couldn't find a commit nor ticket though).

Changed in pyinotify (Ubuntu):
assignee: Krzysztof Klimonda (kklimonda) → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package pyinotify - 0.8.6-2ubuntu2

---------------
pyinotify (0.8.6-2ubuntu2) karmic; urgency=low

  * debian/patches/libc_check.patch:
    - Cherry picked patch from upstream to fix libc check (LP: #408600)
  * debian/rules:
    - enable quilt support
  * debian/control:
    - add quilt to Build-Deps

 -- Krzysztof Klimonda <email address hidden> Tue, 04 Aug 2009 10:58:42 +0200

Changed in pyinotify (Ubuntu):
status: Triaged → Fix Released
Krzysztof Klimonda (kklimonda)
tags: added: packaging
Paul Sladen (sladen)
Changed in ubuntuone-client:
status: New → Invalid
Bug Watch Updater (bug-watch-updater)
Changed in pyinotify (Fedora):
status: Unknown → Fix Released
Bongcaivang (bongcaivang)
Changed in ubuntuone-client:
status: Invalid → Fix Committed
assignee: nobody → Bongcaivang (bongcaivang)
Changed in pyinotify (Ubuntu):
assignee: nobody → Bongcaivang (bongcaivang)
status: Fix Released → Fix Committed
Roman Yepishev (rye)
Changed in ubuntuone-client:
status: Fix Committed → Invalid
assignee: Bongcaivang (bongcaivang) → nobody
Changed in pyinotify (Ubuntu):
status: Fix Committed → Fix Released
assignee: Bongcaivang (bongcaivang) → nobody
Bug Watch Updater (bug-watch-updater)
Changed in pyinotify (Fedora):
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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