libjvm.so not found

Bug #1085226 reported by Steve Fox
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pylucene (Ubuntu)
Fix Released
Undecided
Unassigned
Precise
Fix Released
Undecided
Unassigned

Bug Description

Impact: pylucene is not importable and thus unusable
this is due to a wrong rpath of libjvm.so

Fix: a no change rebuild fixes the issue, this requires jcc 2.11-3ubuntu0.1 from -updats

TESTCASE:
python -c "import lucene"

should succeed and not give this error:

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python2.7/dist-packages/lucene/__init__.py", line 2, in <module>
    import os, _lucene
ImportError: libjvm.so: cannot open shared object file: No such file or directory

Regression potential:
low, no change rebuild current version unusable

Revision history for this message
Steve Fox (drfickle2) wrote :

Turns out this is actually not a bug in the pylucene package, but rather a result of upgrading from Lucid to Precise. The default-jre-headless package creates the /usr/lib/jvm/java-6-openjdk symlink upon a fresh install, but not during the distro upgrade.

Running aptitude reinstall default-jre-headless recreated the symlink and pylucene functions properly now.

Changed in pylucene (Ubuntu):
status: New → Invalid
Revision history for this message
Julian Taylor (jtaylor) wrote :

an upgrade issue is a bug too
I can also reproduce it in a clean chroot.
unfortunately a rebuild in precise is complicated by bug 935380

Changed in pylucene (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
Julian Taylor (jtaylor) wrote :

the fix for bug 935380 requires a jcc update but its quite simple
a rebuild of pylucene fixes the issue then

Revision history for this message
Julian Taylor (jtaylor) wrote :

see bug 1085256 for the jcc update

Revision history for this message
Steve Fox (drfickle2) wrote :

Julian, thanks for looking into the issue. I hope an updated package will eventually come out. I'll use the work-around for now.

Julian Taylor (jtaylor)
description: updated
Changed in pylucene (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Julian Taylor (jtaylor) wrote :

I have submitted a rebuild, please test it when it is accepted. The release team will post instructions on how to do that in this bug.

Revision history for this message
Colin Watson (cjwatson) wrote : Please test proposed package

Hello Steve, or anyone else affected,

Accepted pylucene into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/pylucene/2.3.1-1.1ubuntu2.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in pylucene (Ubuntu Precise):
status: New → Fix Committed
tags: added: verification-needed
Revision history for this message
Steve Fox (drfickle2) wrote :

pylucene 2.3.1-1.1ubuntu2.1 from precise-proposed fixes the issue. I can import the lucene module in a python console. Thanks for fixing!

tags: added: verification-done
removed: verification-needed
Revision history for this message
Chris Halse Rogers (raof) wrote : Update Released

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package pylucene - 2.3.1-1.1ubuntu2.1

---------------
pylucene (2.3.1-1.1ubuntu2.1) precise-proposed; urgency=low

  * no change rebuild build depending on jcc 2.11-3ubuntu0.1 from updates
    fixes wrong libjvm rpath resulting in import failure (LP: #1085226)
 -- Julian Taylor <email address hidden> Sun, 13 Jan 2013 21:19:08 +0100

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

Other bug subscribers

Remote bug watches

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