[64studio-devel] error message

[Gustin Johnson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jaromír Mikeš wrote:
| Hi Dave, Hi Gustin
|
| First I was trying Gustin's suggestion:
|
| sudo aptitude purge debian-archive-keyring && sudo aptitude install
| debian-archive-keyring
|
| But message in terminal warned me that I am doing something very
| dangerous.. Uninstalling some very essential packages. I aborted this
| process.

What is the exact message?

| Than I tried Dave's method, but I did it differently... First I was
| upgrading just cupsys packges from lenny repository... it went well.
| Than I've upgraded rest. Also was going well.
|
| I just get this message:
|
| E: /var/cache/apt/archives/qsynth_0.2.5-2.2_i386.deb: trying to
| overwrite `/usr/share/applications/qsynth.desktop', which is also in
| package 64studio-theme

What I am about to suggest is usually a very bad idea.  In this case the
conflicting file is a desktop shortcut, so I am reasonably sure it won't
do harm.  It should also be on one line.

sudo dpkg -i --force-all /var/cache/apt/archives/qsynth_0.2.5-2.2_i386.deb

| probably broken qsynth in Lenny.

In this case just a duplicate file in two packages.  It is fairly common
when using 3rd party repositories.  It happens regularly to me while
testing KDE4 stuff on Ubuntu.  Most of the time it is icons or
shortcuts.  If it is something else (a library perhaps), then be very
careful.

| Than I've enabled lenny-backports repository... mark all for
| upgrading....apply...(using synaptic)..and get this message:
|
| : docbook-xml: subprocess post-installation script returned error
| exit status 1 E: scrollkeeper: dependency problems - leaving
| unconfigured E: bug-buddy: dependency problems - leaving unconfigured
|  E: capplets-data: dependency problems - leaving unconfigured E:
| gedit: dependency problems - leaving unconfigured E:
| gnome-applets-data: dependency problems - leaving unconfigured E:
| gnome-control-center: dependency problems - leaving unconfigured E:
| gnome-panel-data: dependency problems - leaving unconfigured E:
| gnome-panel: dependency problems - leaving unconfigured E:
| gnome-applets: dependency problems - leaving unconfigured E:
| gnome-session: dependency problems - leaving unconfigured E:
| gnome-terminal: dependency problems - leaving unconfigured E:
| nautilus-data: dependency problems - leaving unconfigured E:
| nautilus: dependency problems - leaving unconfigured E: yelp:
| dependency problems - leaving unconfigured E: gnome-core: dependency
| problems - leaving unconfigured E: gnome-user-guide: dependency
| problems - leaving unconfigured E: gnome-utils: dependency problems -
| leaving unconfigured E: gthumb: dependency problems - leaving
| unconfigured E: nautilus-cd-burner: dependency problems - leaving
| unconfigured E: synaptic: dependency problems - leaving unconfigured
| E: terminatorx: dependency problems - leaving unconfigured E:
| 64studio-themes: dependency problems - leaving unconfigured E:
| 64studio: dependency problems - leaving unconfigured
|
| Than I've tried from terminal # apt-get upgrade

Try aptitude from the command prompt.  It sometimes makes some
intelligent guesses when sorting out apt issues.  Of course when things
get really messy I go straight back to apt-get, dpkg, and
http://packages.debian.org.  You may wish to download the
debian-archive-keyring from http://packages.debian.org and then install
it with dpkg -i

| Got this:
|
| : docbook-xml: subprocess post-installation script returned error
| exit status 1 E: scrollkeeper: dependency problems - leaving
| unconfigured E: bug-buddy: dependency problems - leaving unconfigured
|  E: capplets-data: dependency problems - leaving unconfigured E:
| gedit: dependency problems - leaving unconfigured E:
| gnome-applets-data: dependency problems - leaving unconfigured E:
| gnome-control-center: dependency problems - leaving unconfigured E:
| gnome-panel-data: dependency problems - leaving unconfigured E:
| gnome-panel: dependency problems - leaving unconfigured E:
| gnome-applets: dependency problems - leaving unconfigured E:
| gnome-session: dependency problems - leaving unconfigured E:
| gnome-terminal: dependency problems - leaving unconfigured E:
| nautilus-data: dependency problems - leaving unconfigured E:
| nautilus: dependency problems - leaving unconfigured E: yelp:
| dependency problems - leaving unconfigured E: gnome-core: dependency
| problems - leaving unconfigured E: gnome-user-guide: dependency
| problems - leaving unconfigured E: gnome-utils: dependency problems -
| leaving unconfigured E: gthumb: dependency problems - leaving
| unconfigured E: nautilus-cd-burner: dependency problems - leaving
| unconfigured E: synaptic: dependency problems - leaving unconfigured
| E: terminatorx: dependency problems - leaving unconfigured E:
| 64studio-themes: dependency problems - leaving unconfigured E:
| 64studio: dependency problems - leaving unconfigured
|
~From what I can see, the issues appear solvable.  The real question is
how much time do you want to spend on it.  Personally I believe it is
worth the time to figure out how to correct these kinds of issues,
figuring how things are put together has paid handsome dividends.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIV+LVwRXgH3rKGfMRAuQpAKCaP0f8WtFan4WdgDwguwO35AjGkwCfQNDF
PicoUeuFdmcmEF/DcZbYgbY=
=j/dp
-----END PGP SIGNATURE-----