jcc not importable in some situations

Bug #1085256 reported by Julian Taylor
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jcc (Ubuntu)
Fix Released
Undecided
Unassigned
Precise
Fix Released
Undecided
Unassigned

Bug Description

[Impact]
jcc/__init__.py uses _jcc without directly importing importing it
this can cause import errors
this breaks e.g. the pylucene build in precise, see bug 935380 which again blocks bug 1085226

[Fix]
add to the __init__.py
from jcc import _jcc
as is done in quantal

[TEST CASE]
I have not managed to find a simple testcase, so for now the pylucene build is the testcase
apt-get --compile pylucene

you should _not_ get this type of error:
  File "/usr/lib/python2.7/dist-packages/jcc/__init__.py", line 37, in <module>
     _jcc.CLASSPATH = CLASSPATH
 NameError: name '_jcc' is not defined

[Regression potential]
low just a simple add of an import, it is already applied in quantal

Julian Taylor (jtaylor)
Changed in jcc (Ubuntu):
status: New → Fix Released
description: updated
Revision history for this message
Clint Byrum (clint-fewbar) wrote : Please test proposed package

Hello Julian, or anyone else affected,

Accepted jcc into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/jcc/2.11-3ubuntu0.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 jcc (Ubuntu Precise):
status: New → Fix Committed
tags: added: verification-needed
Revision history for this message
Julian Taylor (jtaylor) wrote :

pylucene now builds successful so we can fix it now in precise

tags: added: verification-done
removed: verification-needed
Revision history for this message
Colin Watson (cjwatson) 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 jcc - 2.11-3ubuntu0.1

---------------
jcc (2.11-3ubuntu0.1) precise-proposed; urgency=low

  * import-_jcc.patch: import used _jcc in __init__.py (LP: #1085256)
    fixes pylucene build failure
 -- Julian Taylor <email address hidden> Sat, 01 Dec 2012 00:10:45 +0100

Changed in jcc (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.