[TriLUG] up2date issues

[Wade Bowlin]

I just had the same problem yesterday on my MythTV box.

Try to delete the rpm first.
rpm -e kdesdk-kbabel

Then install it from the mirror.
rpm -ivh ftp://ftp.redhat.com/blah/blah...

Now do the updates as before.


On Mon, 2003-06-02 at 10:50, dsandif wrote:
> I am trying to run up2date and I
> get this error. I don't know why
> this has come up all of a sudden,
> any ideas folks?
> 
> 
> 
> 
> [apple at lolly R_ruff]# up2date -uv --nox
> 
> Fetching package list for channel: redhat-linux-i386-8.0...
> ########################################
> 
> Fetching Obsoletes list for channel: redhat-linux-i386-8.0...
> ########################################
> 
> Fetching rpm headers...
> #######################################
> Testing package set / solving RPM inter-dependencies...
> ########################################
> RPM package conflict error.  The message was:
> Test install failed because of package conflicts:
> file /usr/include/kde/kbabel/catalog.h from install of
> kdesdk-kbabel-3.0.5a-3 conflicts with file from package
> kdesdk-devel-2.2.2-1
> 
> [apple at lolly R_ruff]# up2date -p
> Updating package profile...
> [lees at love R_stuff]# up2date -uv --nox
> 
> Fetching package list for channel: redhat-linux-i386-8.0...
> ########################################
> 
> Fetching Obsoletes list for channel: redhat-linux-i386-8.0...
> ########################################
> 
> Fetching rpm headers...
> #######################################
> Testing package set / solving RPM inter-dependencies...
> ########################################
> RPM package conflict error.  The message was:
> Test install failed because of package conflicts:
> file /usr/include/kde/kbabel/catalog.h from install of
> kdesdk-kbabel-3.0.5a-3 conflicts with file from package
> kdesdk-devel-2.2.2-1
> 
> 
> 
> 
> 
> _______________________________________________
> TriLUG mailing list
>     http://www.trilug.org/mailman/listinfo/trilug
> TriLUG Organizational FAQ:
>     http://www.trilug.org/faq/TriLUG-faq.html