Screenkey

Installation failed in Hardy

Bug #597212 reported by Grek-336
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Screenkey
Confirmed
Low
Unassigned

Bug Description

screenkey_0.2_all.deb

I have installed the new Version (0.2) in my real Hardy and Lucid Version of Ubuntu and the installation (and deinstallation) failed.

In a new installed Lucid installation in a VM the installation (of screenkey) works in a new installed Hardy installation it works not.

In my real Hardy installation a reinstallation make this output:

michael@michael-desktop:/media/disk/Debian-Pakete$ LANGUAGE=C sudo dpkg -i screenkey_0.2_all.deb
[sudo] password for michael:
Selecting previously deselected package screenkey.
(Reading database ... 278822 files and directories currently installed.)
Preparing to replace screenkey 0.2 (using screenkey_0.2_all.deb) ...
Usage: update-python-modules [-v] [-c] package_directory [...]
       update-python-modules [-v] [-c] package.dirs [...]
       update-python-modules [-v] [-a|-f]

update-python-modules: error: /usr/share/python-support/screenkey.public is not a directory
dpkg: warning - old pre-removal script returned error exit status 2
dpkg - trying script from the new package instead ...
Usage: update-python-modules [-v] [-c] package_directory [...]
       update-python-modules [-v] [-c] package.dirs [...]
       update-python-modules [-v] [-a|-f]

update-python-modules: error: /usr/share/python-support/screenkey.public is not a directory
dpkg: error processing screenkey_0.2_all.deb (--install):
 subprocess new pre-removal script returned error exit status 2
Usage: update-python-modules [-v] [-c] package_directory [...]
       update-python-modules [-v] [-c] package.dirs [...]
       update-python-modules [-v] [-a|-f]

update-python-modules: error: /usr/share/python-support/screenkey.public is not a directory
dpkg: error while cleaning up:
 subprocess post-installation script returned error exit status 2
Errors were encountered while processing:
 screenkey_0.2_all.deb
michael@michael-desktop:/media/disk/Debian-Pakete$

I will try the same in my real Lucid installation in a few Minutes and then post the output here.

Revision history for this message
Grek-336 (kult01) wrote :

Sorry but I can not reproduce the failure in Lucid.
When I startet my Lucid real installation again, Synaptic says screenkey is broken. After remove screenkey the installation of screenkey_0.2_all.deb works without problems.

I will try a new test in a new Hardy installation in a VM

Revision history for this message
Grek-336 (kult01) wrote :

I have found that the update-python-modules not works with .public files.
In the man pages is karmic the first version of update-python-modules that can work with .public files. See
Karmic: http://manpages.ubuntu.com/manpages/karmic/en/man8/update-python-modules.8.html
Jaunty: http://manpages.ubuntu.com/manpages/jaunty/en/man8/update-python-modules.8.html

Revision history for this message
Pablo SEMINARIO (pabluk) wrote :

Thanks,
Now I can see the difference between update-python-modules in Karmic and Jaunty.

I've tried install/reinstall in Lucid and Karmic without problems.
Installing with:
  sudo dpkg -i screenkey_0.2_all.deb
and uninstalling with:
  sudo apt-get remove screenkey

summary: - Installation failed in Hardy and (Lucid)
+ Installation failed in Hardy
Changed in screenkey:
status: New → Confirmed
importance: Undecided → Low
Revision history for this message
Grek-336 (kult01) wrote :

I have test the package screenkey_0.2_all.deb in a VirtualBox VM with a Live-DVD from Kubuntu 9.04 (Jaunty Jackalope) that use Python 2.6 but update-python-modules don't support .pulic files.

The installation fails with the folling output (sorry the language is german):

Wähle vormals abgewähltes Paket python-cairo.
(Lese Datenbank ... 188660 Dateien und Verzeichnisse sind derzeit installiert.)
Entpacke python-cairo (aus .../python-cairo_1.4.12-1.2ubuntu1_i386.deb) ...
Wähle vormals abgewähltes Paket python-gtk2.
Entpacke python-gtk2 (aus .../python-gtk2_2.14.1-1ubuntu1_i386.deb) ...
Wähle vormals abgewähltes Paket python-xlib.
Entpacke python-xlib (aus .../python-xlib_0.14-2_all.deb) ...
Richte python-cairo ein (1.4.12-1.2ubuntu1) ...

Richte python-gtk2 ein (2.14.1-1ubuntu1) ...

Richte python-xlib ein (0.14-2) ...

Verarbeite Trigger für python-support ...
Wähle vormals abgewähltes Paket screenkey.
(Lese Datenbank ... 188821 Dateien und Verzeichnisse sind derzeit installiert.)
Entpacke screenkey (aus .../screenkey_0.2_all.deb) ...
Richte screenkey ein (0.2) ...
Usage: update-python-modules [-v] [-c] package_directory [...]
       update-python-modules [-v] [-c] package.dirs [...]
       update-python-modules [-v] [-a|-f|-p]

update-python-modules: error: /usr/share/python-support/screenkey.public is not a directory
dpkg: Fehler beim Bearbeiten von screenkey (--install):
 Unterprozess post-installation script gab den Fehlerwert 2 zurück
Fehler traten auf beim Bearbeiten von:
 screenkey

The installation problem is not a problem of python 2.5 vs. python 2.6, it is a problem of update-python-moduls in package python-support 0.8.7 vs. 1.0.3

Revision history for this message
Pablo SEMINARIO (pabluk) wrote :

Yes, apparently the problem is in dh_pysupport that invoke update-python-modules when the debian package is created.
Thanks

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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