Arch Linux User Repository

I get a compile-time error, while running package() :

Traceback (most recent call last):
  File "setup.py", line 2, in <module>
    from DistUtilsExtra.command import *
ModuleNotFoundError: No module named 'DistUtilsExtra'

even though package python-distutils-extra (version 2.39-3) is properly installed.

Sorry for the lack of updates here, should work again as intended.

erikzenker: About the error: ValueError: Namespace Unity not available I just commented the line 28 of the file /usr/lib/python3.6/site-packages/usbcreator/frontends/gtk/unitysupport.py. And work just fine.

So I installed this and got, like the others, the " ValueError: Namespace Unity not available" error. I looked a bit in the code and found the problem.

FIX:

change the line 28 in ..site-packages/usbcreator/frontends/gtk/unitysupport.py

from

except ImportError as e:

to

except (ImportError, ValueError) as e:

EXPLANATION:

In ..site-packages/usbcreator/frontends/gtk/unitysupport.py it checks if the Unity environment (the former Ubuntu desktop environment) is running and therefore calls require_versions('Unity', '7.0') in a try block that has an except block for exceptions of type "ImportError". BUT require_versions (..site-packages/gi/init.py:92) throws an exception of type ValueError.

THIS PACKAGE SHOULD BE UPDATED

I also looked up the current version of usbcreator from upstream (https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/usb-creator/trusty/view/head:/usbcreator/frontends/gtk/unitysupport.py) and there the require_versions check was completely deleted. Maybe it would help to just update this package to the current version of the code instead of wildly patching in it :-)

I also get the error of the previous comment:

...
ValueError: Namespace Unity not available

Missing some unity stuff as dependency?

$ usb-creator-gtk
Traceback (most recent call last):
File "/usr/bin/usb-creator-gtk", line 28, in <module>
from usbcreator.frontends.gtk import GtkFrontend
File "/usr/lib/python3.6/site-packages/usbcreator/frontends/gtk/__init__.py", line 1, in <module>
from usbcreator.frontends.gtk.frontend import GtkFrontend
File "/usr/lib/python3.6/site-packages/usbcreator/frontends/gtk/frontend.py", line 31, in <module>
from usbcreator.frontends.gtk.unitysupport import UnitySupport
File "/usr/lib/python3.6/site-packages/usbcreator/frontends/gtk/unitysupport.py", line 28, in <module>
gi.require_version('Unity', '7.0')
File "/usr/lib/python3.6/site-packages/gi/__init__.py", line 118, in require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Unity not available

┌─[benzi] @ [benzi-pc]
└─[(~)] > packer -S usb-creator
warning: usb-creator is flagged out of date

AUR (1): usb-creator

Proceed with installation? [Y/n] y
Installing AUR package: usb-creator
Edit usb-creator PKGBUILD? [y/N] n
Edit usb-creator.install? [y/N] n
==> Creazione del pacchetto: usb-creator 0.2.67-2 (ven 22 gen 2016, 12.32.17, CET)
==> Controllo delle dipendenze durante l'avvio in corso...
==> Dipendenze mancanti:
-> python-debian
==> Controllo delle dipendenze durante la compilazione in corso...
==> Dipendenze mancanti:
-> python-distutils-extra
==> ERRORE: Impossibile risolvere tutte le dipendenze.
The build failed.

Strange, I had to manually install python-debian although it is correctly listed as a dependency.

I have a issue in compilation:

/usr/local/bin/python -O /tmp/tmp0at6pfbw.py
unable to execute '/usr/local/bin/python': Permission denied
error: command '/usr/local/bin/python' failed with exit status 1
==> ERROR: Se produjo un fallo en package_python-debian().

Updated to 0.2.67 - http://git.io/vTjWd
The KDE/QT frontend has been updated to use QT5.
I have used a less aggressive patch to pass the included Ubuntu version check now.
This should allow us to write images prior to 10.10 now, however, I have not tested it.
Btw. they have added the functionality to use the bundled syslinux of the iso image to write the bootloader on the usb drive.
While this might work most of the times, i can think of issues when you try to use it with different architectures
(for example writing an amd64 image under i686). Because this takes precedence, a locally installed version is not used.