uniconv now called uniconvertor

Bug #226383 reported by Tavmjong Bah
20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Fix Released
Medium
jazzynico

Bug Description

A Fedora packaging problem:

/usr/bin/uniconv was moved to /usr/bin/uniconvertor in Fedora to avoid a naming conflict. This breaks .cdr and .wmf import (cdr2svg.sh, cdr_input.inx, wmf_input.inx).

Related branches

Revision history for this message
Luca Bruno (lucab) wrote :

IIRC debian will do the same thing, as uniconv is already taken as binary name.
Maybe we should check if /usr/bin/uniconverter is present at runtime, otherwise fallback to plain uniconv.
If somebody is in contact with upstream, are they already aware of the name clash?

Changed in inkscape:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
sas (sas-sas) wrote :

They are aware of the name clash: http://www.sk1project.org/forum/topic.php?forum=2&topic=33

I don't think .inx files currently support an either/or dependency, so some work would be required to specify "either uniconvertor or uniconv". There's also the problem that UniConvertor is called via a script (formerly cdr2svg.sh, now uniconv-ext.py), and the script needs to know which to use (although it could probably use the uniconvertor Python module directly, which would avoid the name issue).

It would be best if everything could be switched to the longer name for 0.47.

Revision history for this message
Rygle (rygle) wrote :

It is probably as simple as renaming uniconv.cmd to uniconvertor.cmd on the Win32 platform. We can do that ourselves, although that would require a special package hosted somewhere.

Does anyone know about other platforms and linux distros? Mac, Ubuntu, BSD, Suse...?

Revision history for this message
theAdib (theadib) wrote :

Folks please recheck. There is now a new uniconvertor script called uniconv-ext.py that should handle this case.
PLease report! Adib.

theAdib (theadib)
description: updated
tags: added: export importing
tags: added: import-export
removed: export importing
tags: added: uniconvertor
su_v (suv-lp)
tags: added: extensions-plugins
jazzynico (jazzynico)
summary: - uniconv called uniconvertor in Fedora
+ uniconv now called uniconvertor
Revision history for this message
jazzynico (jazzynico) wrote :

Also affects OpenSUSE, Ubuntu 9.10 (if /usr/bin is before /usr/local/bin) and probably some other platforms.

Changed in inkscape:
milestone: none → 0.48
assignee: nobody → JazzyNico (jazzynico)
jazzynico (jazzynico)
Changed in inkscape:
status: Confirmed → In Progress
Revision history for this message
jazzynico (jazzynico) wrote :

Fix committed in bzr, revision 9246.
The new file can be downloaded here: http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/annotate/head%3A/share/extensions/uniconv-ext.py.

Changed in inkscape:
status: In Progress → Fix Committed
jazzynico (jazzynico)
Changed in inkscape:
status: Fix Committed → Fix Released
Revision history for this message
inkscape bug (jetsongeorge72) wrote :

 p = Popen('uniconvertor', shell=True, stdout=PIPE, stderr=PIPE).wait()

is used to test if uniconverter is available. Most of us know that one can often just give a programme name to run it, but some programmes require input.

Just running unicoverter causes an error (no input file, so the extension sees the error and doesn't realize that the programme exists).

'uniconverter --help' does NOT throw an error.

(Fedora core11)

Change the test to check for 'uniconverter --help' OR ... if you know what programme name you have on your system, just rip out the test section and specify the function as:
cmd = 'uniconvertor'

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.