wsjt does not install the correct dependencies

Bug #159734 reported by Stephen Wheaton
16
Affects Status Importance Assigned to Milestone
wsjt (Ubuntu)
Fix Released
Medium
Emmet Hikory
Gutsy
Won't Fix
Medium
Unassigned
Hardy
Fix Released
Medium
Emmet Hikory

Bug Description

Binary package hint: wsjt

When trying to install WSJT in Gutsy Gibbon I received an error telling me that numpy was missing.

I installed numpy which cleared the original problem, but then WSJT core dumped. I suspect a dependency problem with numpy.

WSJT works fine with my Feisty Fawn partition.

Best regards,

Steve

Emmet Hikory (persia)
Changed in wsjt:
assignee: nobody → persia
importance: Undecided → Medium
status: New → In Progress
Revision history for this message
Emmet Hikory (persia) wrote :

wsjt (5.9.7.r383-1ubuntu2) hardy; urgency=low

  * Add dependency on python-numpy (LP: #159734)
  * Update Maintainer to match standard default

 -- Emmet Hikory <email address hidden> Sat, 03 Nov 2007 23:43:27 +0900

Changed in wsjt:
status: In Progress → Fix Released
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Jonathan Marsden (jmarsden) wrote :

In Intrepid, installing wsjt pulls in numpy just fine... but wsjt then coredumps with an "Illegal instruction".

So I suspect this issue has been only partially fixed?

The backtrace I get from gdb (after ulimit -c 10000000 so it actually creates a core file) is:

Core was generated by `python /usr/share/wsjt/wsjt.py'.
Program terminated with signal 4, Illegal instruction.
[New process 27142]
[New process 27143]
#0 0xb3506f68 in ?? ()
(gdb) bt
#0 0xb3506f68 in ?? ()
#1 0xb3500a30 in ?? ()
#2 0x0805d867 in ?? ()
#3 0x080cc8a7 in ?? ()
#4 0x080d0345 in ?? ()
#5 0x080d0557 in ?? ()
#6 0x080edf8f in ?? ()
#7 0x080ee25a in ?? ()
#8 0x080595e7 in ?? ()
#9 0x08058962 in ?? ()
#10 0xb7e4b685 in ?? ()
#11 0x080588a1 in ?? ()
(gdb)

Incidentally, wsjt appears to lack a man page, too.

Jonathan

Revision history for this message
Jonathan Marsden (jmarsden) wrote :

BTW, should a problem such as "WSJT core dumped" really be considered "bitesize" ? It seems a lot to expect of newcomers to deal appropriately with this kind of issue.

Is there an official rule about "un-bitesizing" a bug -- how would I do that?

Revision history for this message
Sergio Zanchetta (primes2h) wrote :

The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
Gutsy task.

Changed in wsjt (Ubuntu Gutsy):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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