After doing apt-get update and then apt-get upgrade I get this message: "file /opt/kde3/share/apps/kdm/pics/users/BeachBall.png from install of kdebase3-kdm-3.3.0-15 conflicts with file from package kdeutils3-3.2.1-61 Error while running transaction." I don't get it. How can a little picture file "conflict" with anything? What's to conflict about a picture file? There were two other such "conflicts", Butterfly.png and Flower.png. Could someone explain, in small words please? I could understand missing or corrupted... but a portable network graphics drawing of a beachball conflicts with. . . well, what can a picture conflict with? Kevin
Op zondag 3 oktober 2004 06:42, schreef elefino:
After doing apt-get update and then apt-get upgrade I get this message: "file /opt/kde3/share/apps/kdm/pics/users/BeachBall.png from install of kdebase3-kdm-3.3.0-15 conflicts with file from package kdeutils3-3.2.1-61 Error while running transaction."
I don't get it. How can a little picture file "conflict" with anything? What's to conflict about a picture file? There were two other such "conflicts", Butterfly.png and Flower.png.
Could someone explain, in small words please? I could understand missing or corrupted... but a portable network graphics drawing of a beachball conflicts with. . . well, what can a picture conflict with?
Kevin
http://apt4rpm.sourceforge.net/faq.html#q40 -- Richard Bos Without a home the journey is endless
On Sunday 03 October 2004 11:01, Richard Bos wrote:
Op zondag 3 oktober 2004 06:42, schreef elefino:
After doing apt-get update and then apt-get upgrade I get this message: "file /opt/kde3/share/apps/kdm/pics/users/BeachBall.png from install of kdebase3-kdm-3.3.0-15 conflicts with file from package kdeutils3-3.2.1-61 Error while running transaction."
I don't get it. How can a little picture file "conflict" with anything? What's to conflict about a picture file? There were two other such "conflicts", Butterfly.png and Flower.png.
Could someone explain, in small words please? I could understand missing or corrupted... but a portable network graphics drawing of a beachball conflicts with. . . well, what can a picture conflict with?
Kevin
Please ignore the advise given in that link. People are far to quick to --force the issue Look at the kdeutils3 version. For some reason apt wants to upgrade kdm to version 3.3, but keep kdeutils3 at 3.2.1. In between those two versions, the packager decided to move that picture from kdeutils to kdm. The correct solution is to somehow get apt to upgrade kdetils3 along with kdm. Usually, kde packages need to be upgraded in unison
Anders Johansson wrote:
On Sunday 03 October 2004 11:01, Richard Bos wrote:
Op zondag 3 oktober 2004 06:42, schreef elefino:
After doing apt-get update and then apt-get upgrade I get this message: "file /opt/kde3/share/apps/kdm/pics/users/BeachBall.png from install of kdebase3-kdm-3.3.0-15 conflicts with file from package kdeutils3-3.2.1-61 Error while running transaction."
I don't get it. How can a little picture file "conflict" with anything? What's to conflict about a picture file? There were two other such "conflicts", Butterfly.png and Flower.png.
Could someone explain, in small words please? I could understand missing or corrupted... but a portable network graphics drawing of a beachball conflicts with. . . well, what can a picture conflict with?
Kevin
Please ignore the advise given in that link. People are far to quick to --force the issue
Look at the kdeutils3 version. For some reason apt wants to upgrade kdm to version 3.3, but keep kdeutils3 at 3.2.1. In between those two versions, the packager decided to move that picture from kdeutils to kdm.
The correct solution is to somehow get apt to upgrade kdetils3 along with kdm. Usually, kde packages need to be upgraded in unison
Sometimes you need to use "--replacefiles" when upgrading a package, in order to resolve such a conflict, so it doesn't keep two copies around. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer =====LINUX ONLY USED HERE=====
On Monday 04 October 2004 02:19, Sid Boyce wrote:
Sometimes you need to use "--replacefiles" when upgrading a package, in order to resolve such a conflict, so it doesn't keep two copies around.
Yes it happens, but it's pretty rare that you're forced to do it. In my experience, these conflicts usually arise in exactly this situation, when some package gets upgraded and some companion package isn't. But yes, there are exceptions (eg. ksirc, kvirc, konversation). This case wasn't one of them though, and overwriting files should always be a last resort
Op zondag 3 oktober 2004 19:05, schreef Anders Johansson:
Please ignore the advise given in that link. People are far to quick to --force the issue
Look at the kdeutils3 version. For some reason apt wants to upgrade kdm to version 3.3, but keep kdeutils3 at 3.2.1. In between those two versions, the packager decided to move that picture from kdeutils to kdm.
The correct solution is to somehow get apt to upgrade kdetils3 along with kdm. Usually, kde packages need to be upgraded in unison
Good point. Most likely apt stated that kdeutils3 is being 'kept back'. Is it possible to provide the full apt output of this upgrade? If apt reported htat kdeutils is lept back indeed, than an 'apt dist-upgrade' would help. -- Richard Bos Without a home the journey is endless
participants (4)
-
Anders Johansson
-
elefino
-
Richard Bos
-
Sid Boyce