[PlanetCCRMA] Re: apt broken after installing ATrpms?

Mon Oct 25 12:00:02 2004

On Mon, 2004-10-25 at 10:05, Nathaniel Virgo wrote:
> Fernando Pablo Lopez-Lezcano wrote:
> >On Sun, 2004-10-24 at 08:35, Nathaniel Virgo wrote:
> >>Axel Thimm wrote:
> >>>Yes, I'd move the *.rpmsave back to the normal names to get the old
> >>>and known working configuration back. Then I'd install
> >>>medley-package-config from http://atrpms.net/name/medley-package-config/
> >>>(which will install under *.rpmnew) and merge/takeover con fig files
> >>>according to your personal preferences. Or you could start with the
> >>>medley-package-config files and modify them from there.
> >>>      
> >>Okay, I got around to doing that, and decided to just keep the config 
> >>files that medley-package-config gave me, but now when I run apt-get 
> >>update I get the errors shown below and nothing gets installed (though 
> >>an awful lot gets downloaded of course).  What can I do to resolve this?
> >
> >Did you try an "apt-get dist-upgrade"?
> >That will be more agressive in what it tries to do. 
> >
> Sorry, I meant to write "apt-get dist-upgrade" in that email, not 
> "apt-get update" - update and upgrade work fine, it's dist-upgrade that 
> gives those errors.
> >
> >>Committing changes...
> >>Preparing...                ########################################### 
> >>[100%]
> >>        file /usr/bin/fftw-wisdom conflicts between attempted installs 
> >>of fftw3-3.0.1-2.fr and fftw-3.0.1-6.rhfc1.at
> >>        file /usr/lib/libfftw3.so.3.0.1 conflicts between attempted 
> >>	installs of fftw3-3.0.1-2.fr and fftw-3.0.1-6.rhfc1.at
> >>        file /usr/lib/libfftw3_threads.so.3.0.1 conflicts between 
> >
> >Axel (atrpms) has a different naming convention that the other
> >repositories for fftw, the same package has different names (fftw3 vs
> >fftw). Some package somewhere must have an explicit dependency on the
> >name of the fftw package (fftw3 or fftw), so that the library
> >requirements are not enough, and both try to get installed at the same
> >time. 
>
> Any idea how I can prevent this from happening?

Argh....
fftw3-3.0.1-2.fr is part of freshrpms...
fftw-3.0.1-6.rhfc1.at is part of atrpms...

What is it you have installed? ("rpm -q fftw", "rpm -q fft3")

It is hard to know what is the root cause of the problem. That's because
the dependency that is causing the problem is probably in a package that
is not currently installed in your machine. What is the complete output
of the dist-upgrade? I mean, including the list of packages that are
going to be upgraded, erased, etc?

One way to go, I think, is work from that list and try a:
  apt-get install xxx
where xxx is each of the packages that is going to be upgraded, to see
if you can isolate which one is causing the conflict. 

> >>        file /usr/share/doc/HTML/en_GB/common/1.png conflicts between 
> >>attempted installs of kde-i18n-British-3.3.1-0.0.kde and 
> >>kdelibs-3.3.1-0.2.1.kde
> >
> >Hmmm, where do those come from? Which repository? Looks like a conflict
> >inside a different repository (kde?). 
> >
> I don't know - the medey-package-config package added quite a few 
> different repositories to my sources.list and I don't know how to find 
> out which files are coming from where.  I don't use kde, though, so I'm 
> not particularly fussed about these doc files, I just want to be able to 
> run dist-upgrade.

It looks like this is a known upgrade problem with kde and it is
documented (just read about it on another list). I'm including a
forwarded email at the end of this one.

-- Fernando

====

From: Rex Dieter <rdieter@math.unl.edu>
To: kde-redhat-announce@lists.sourceforge.net
Subject: [kde-redhat-announce] kde-3.3.1 -> testing (10/19/04)
Date: 18 Oct 2004 13:33:15 -0500

kde-3.3.1 packages will be arriving in the kde-redhat/testing repo on 
Tue Oct 19.

NOTE: These packages have been built *without* themer support. What this 
means is, folks upgrading from stock-redhat packages will hopefully have 
an easier upgrade experience.

Unfortunately, if you're upgrading from previous 
kde-redhat/themer-supported kde rpms, you'll need to do one extra step 
before upgrading. As root, run
  /usr/sbin/themer --purge
  --purge is an option in themer version 1.81 and newer. If you have a 
previous version (running '/usr/sbin/themer --version' will tell), 
you'll need to upgrade the themer tool first.

FYI, the kde-3.3.1 install/upgrade should follow the usual procedure as 
documented on
  http://kde-redhat.sf.net/
(ie, apt-get/yum install kde qt redhat-artwork .....)

More comments about themer --purge/removal:
1. If you do not run the 'themer --purge' command prior to upgrading 
from existing kde-redhat kde rpms, you *will* get rpm file conflicts on 
upgrade. Yes, this extra step *really* is necessary, and we've found no 
(easy) way to automate this (see the kde-redhat-users mailing list 
archives for the discussion).

2. After running the purge, and before you upgrade, your system will be 
in a quasi unstable state (not completely broken, but all "default" 
qt/gtk/kde styles/themes may not be readily accessible).

3. Once kde is upgraded, you can freely
rpm -e themer

-- 
Rex Dieter
KDE-RedHat Project Admin