The package installer crash in the instalation.

Bug #622376 reported by davidjhi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
wxBanker
Incomplete
Medium
Unassigned

Bug Description

In debian testing, the package installer crash and close during the install.

Revision history for this message
Michael Rooney (mrooney) wrote :

Thanks for the report, could you please include the error output, such as from running dpkg -i from a terminal?

Changed in wxbanker:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
davidjhi (davidjhi) wrote :

Sorry, i forget that:

Desempaquetando wxbanker (de wx.deb) ...
dpkg: problemas de dependencias impiden la configuración de wxbanker:
 wxbanker depende de python-wxgtk2.8; sin embargo:
  El paquete `python-wxgtk2.8' no está instalado.
 wxbanker depende de python-dateutil; sin embargo:
  El paquete `python-dateutil' no está instalado.
dpkg: error al procesar wxbanker (--install):
 problemas de dependencias - se deja sin configurar
Procesando disparadores para hicolor-icon-theme ...
Procesando disparadores para gnome-menus ...
Procesando disparadores para desktop-file-utils ...
Procesando disparadores para man-db ...
Se encontraron errores al procesar:
 wxbanker

Revision history for this message
Michael Rooney (mrooney) wrote :

First, I notice it looks like you aren't using the latest version (0.8.1) but instead perhaps 0.7, so I'd recommend downloading 0.8.1.

But I don't think this is a bug; I believe this is the expected behavior of dpkg, in that it doesn't install dependencies. You can use apt-get to install those dependencies, or use gdebi instead of dpkg to install the .deb. Let me know how that goes! I'd like to eventually get wxbanker in debian properly, so debian users can also just apt-get, but haven't find the time just yet to go through the whole process. Perhaps I should!

Revision history for this message
Michael Rooney (mrooney) wrote :

After another thought I'm wondering if you weren't installing using dpkg to begin with, and this is just a different error unrelated to the one you saw. If so, can you provide full steps to reproduce the problem, such as where you got the deb and then exactly what commands/clicks and such you performed? Thanks!

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.