Dependancy problems FC5t2

[Carlton]

I'm having dependancy problems with FC5 t2. Is that something I should expect until the final release. See below: It's the output from yum upgrade and yum update
--> Processing Dependency: libtotem-plparser.so.0 for package: rhythmbox
--> Processing Dependency: hotplug >= 3:2004_04_01-10 for package: sane-backends
--> Processing Dependency: hotplug for package: udev
--> Processing Dependency: libtotem-plparser.so.0 for package: rhythmbox
--> Finished Dependency Resolution
Error: Missing Dependency: libtotem-plparser.so.0 is needed by package rhythmbox
Error: Missing Dependency: hotplug >= 3:2004_04_01-10 is needed by package sane-backends
Error: Missing Dependency: hotplug is needed by package udev

Yumex shows several updates available including a newer kernel (I think). After I run the update and reboot, all of the updates are still listed.

I'm probably too new at this to be running a distro's test versions.

[lsatenstein]

I am a newbie. Have you tried doing the updates from PUP?

[Carlton]

Don't know what PUP is??

[drunkahol]

PUP is the preferred GUI frontend for yum I believe.

It's in the menu as:

Applications -> System Tools -> Software Updater

The menu item doesn't have an icon on my machine - nor does the Add/Remove Software (pirut) application on the same menu. Anyone else seen this?

Cheers

Duncan

[NBZ]

I'm having dependancy problems with FC5 t2. Is that something I should expect until the final release. See below: It's the output from yum upgrade and yum update
--> Processing Dependency: libtotem-plparser.so.0 for package: rhythmbox
--> Processing Dependency: hotplug >= 3:2004_04_01-10 for package: sane-backends
--> Processing Dependency: hotplug for package: udev
--> Processing Dependency: libtotem-plparser.so.0 for package: rhythmbox
--> Finished Dependency Resolution
Error: Missing Dependency: libtotem-plparser.so.0 is needed by package rhythmbox
Error: Missing Dependency: hotplug >= 3:2004_04_01-10 is needed by package sane-backends
Error: Missing Dependency: hotplug is needed by package udev

Yumex shows several updates available including a newer kernel (I think). After I run the update and reboot, all of the updates are still listed.

I'm probably too new at this to be running a distro's test versions.

With rawhide, things can and do break.

Just wait a bit, and the updates will work again. That will probably be tomorrow, but it can take longer.

pup is the official yum gui for updates. Its does not handle anything else.

pirut (Package Install Remove Update Tool. Pronounced pirate) will handle installing, removing etc. Pup will be a part of pirut from what I understand.

[Firewing1]

PUP is the Fedora default, but not preferred to many. It needs a lot of development. I'd recommend yumex or smartpm.
Also, you can try
yum makecache, itll run for a while, then try again.
Firewing1

[Carlton]

I'm wondering if I should go back to FC4 or hang tight with FC5 test 2?

If I stay with test2, will yum update or upgrade get me the final FC5 once it's released?

Can I add the FC4 RPMForge repos to FC5 or is that asking for trouble??

[redeemingspirit]

second that dependancy issue - running yum update I get 'hotplug >= 3:2004_04_01-10 is needed by package san-backends'

yum search hotplug shows hotplug.i386 3:2004_09_23-10.1 is installed

[mit]

use yumex to do the updates and dont select totom & initscripts. Then update the rest, The are some broken depencies in Rawhide at the moment.

Rawhide report from 20060122.
..
Broken deps for i386
----------------------------------------------------------
GFS-kernel - 2.6.14.1-20051219.162641.FC5.9.i686 requires kernel = 0:2.6.15-1.1826.2.10_FC5
GFS-kernel - 2.6.14.1-20051219.162641.FC5.9.i686 requires /lib/modules/2.6.15-1.1826.2.10_FC5
GFS-kernel-smp - 2.6.14.1-20051219.162641.FC5.9.i686 requires /lib/modules/2.6.15-1.1826.2.10_FC5smp
GFS-kernel-smp - 2.6.14.1-20051219.162641.FC5.9.i686 requires kernel-smp = 0:2.6.15-1.1826.2.10_FC5
cman-kernel - 2.6.14.1-20051219.162641.FC5.10.i686 requires kernel = 0:2.6.15-1.1826.2.10_FC5
cman-kernel - 2.6.14.1-20051219.162641.FC5.10.i686 requires /lib/modules/2.6.15-1.1826.2.10_FC5
cman-kernel-smp - 2.6.14.1-20051219.162641.FC5.10.i686 requires /lib/modules/2.6.15-1.1826.2.10_FC5smp
cman-kernel-smp - 2.6.14.1-20051219.162641.FC5.10.i686 requires kernel-smp = 0:2.6.15-1.1826.2.10_FC5
dlm-kernel - 2.6.14.1-20051219.162641.FC5.8.i686 requires kernel = 0:2.6.15-1.1826.2.10_FC5
dlm-kernel - 2.6.14.1-20051219.162641.FC5.8.i686 requires /lib/modules/2.6.15-1.1826.2.10_FC5
dlm-kernel-smp - 2.6.14.1-20051219.162641.FC5.8.i686 requires /lib/modules/2.6.15-1.1826.2.10_FC5smp
dlm-kernel-smp - 2.6.14.1-20051219.162641.FC5.8.i686 requires kernel-smp = 0:2.6.15-1.1826.2.10_FC5
gnbd-kernel - 2.6.14.0-20051108.134753.FC5.14.i686 requires kernel = 0:2.6.15-1.1826.2.10_FC5
gnbd-kernel - 2.6.14.0-20051108.134753.FC5.14.i686 requires /lib/modules/2.6.15-1.1826.2.10_FC5
gnbd-kernel-smp - 2.6.14.0-20051108.134753.FC5.14.i686 requires /lib/modules/2.6.15-1.1826.2.10_FC5smp
gnbd-kernel-smp - 2.6.14.0-20051108.134753.FC5.14.i686 requires kernel-smp = 0:2.6.15-1.1826.2.10_FC5
gnome-python2-totem - 2.12.1-9.i386 requires libtotem-plparser.so.0
rhythmbox - 0.9.2-8.i386 requires libtotem-plparser.so.0
sane-backends - 1.0.17-1.i386 requires hotplug >= 3:2004_04_01-10
udev - 078-4.i386 requires hotplug

[lsatenstein]

PUP is the preferred GUI frontend for yum I believe.

It's in the menu as:

Applications -> System Tools -> Software Updater

The menu item doesn't have an icon on my machine - nor does the Add/Remove Software (pirut) application on the same menu. Anyone else seen this?

Cheers

Duncan
With a fresh install of Gnome, the icon was there, If you have installed the Gnome patches, in that process, Gnome has died. At least that is the situaition on my pc.

Pup works like yumex. In fact, I compared both and have the same results.

There are some missing dependencies. Either the rpm creator typed a 2 for a 1, and the dependency tree is broken, or there are missing installs.

So, I cannot use Gnome for now, and that is disappointing. Gnome is more intuitive for my grandchildren. KDE is much more explorer style.

[redeemingspirit]

Hi mit,

In my particular situation, I'm trying to update the system to fix some other issues on my T42p around video drivers, so using a graphical interface isn't a good idea. I'll hunt up some documentation around yum and see if I can't figure out how to exclude the packages you're suggesting.

[lsatenstein]

I lived with and enjoyed working with OS2.

What I liked with my OS2 experience was the update process. It was similar to PUP, but an archive concept (a kind of zip tar file). The archive contained the files being replaced, based on the date the PUP equivalent was being executed on the local system. My archive version and contents could be different from that created by my co-worker on his system.

The archive was time stamped and a system update was able to be backed out to that archive date. In the OS2 specifications, we set parameters for numbers of generations of archives (3 to 4 was recommended).

Say you wanted to roll back to the date of an older archive Archive(-3). (That is the way to specify 3 generations back). The process was implemented so that the rollback of the later archives archive(-1), archive(-2), where done first, and then archive(-3) was done. It was automatic and in reverse creation sequence. The current upgrade was always downloaded and stored as archive(0).

You also had the option to re-apply archives, so that I could backout to undo the contents of archive(-3), and then apply archives again, omitting the one I did not want.

Why do I bring this up?. I just installed a PUP update for Fedora Core5 test2. As a result, Gnome is broken. If I log in using Gnome, I am unable to execute most programs, including the shell. I am not able to start most programs that rely on Gnome, and I am not able to log out the normal way.

(I did manage to log out by rebooting.) To reboot, I use the control-alt-f1 key to log into root and then, to issue the reboot command.


This problem prompted my writing this note. I would like to see this type of archive design discussed for opportunities down the road. I see an easy implementation of this concept, using a date stamped directory containing the modules that were replaced. Perhaps a little less sophisticated, but then OS2 system maintainers thought about the skill sets of Mr. Average user.

Lets face it, disk space is now available in gigabytes. So why not use some of it for a roll back processes.

[mit]

Hi mit,

In my particular situation, I'm trying to update the system to fix some other issues on my T42p around video drivers, so using a graphical interface isn't a good idea. I'll hunt up some documentation around yum and see if I can't figure out how to exclude the packages you're suggesting.

This sould do it in textmode.

yum --exclude=initscripts --exclude=totem update

[mit]

I lived with and enjoyed working with OS2.

What I liked with my OS2 experience was the update process. It was similar to PUP, but an archive concept (a kind of zip tar file). The archive contained the files being replaced, based on the date the PUP equivalent was being executed on the local system. My archive version and contents could be different from that created by my co-worker on his system.



I have used OS/2, and liked it to, but it is hard to compare the OS/2 fixpack system with a linux system.
A linux system i build by a lot of packages, and can each one can be updated, where OS/2 is a traditional OS, maintained by one firm, and easier to patch. pup is working on single packages, not the whole system like a fixpack in OS/2.

[lsatenstein]

PUP does not provide a non-gui interface, does it?
And I found that I could uncheck the files I did not want and achieve the same results.

[mit]

PUP does not provide a non-gui interface, does it?
And I found that I could uncheck the files I did not want and achieve the same results.
pup is a gui for doing a 'yum update', in textmode you have to use yum with the '--exclude' flag to exclude packages.

[smfinley]

I suggest you read this (http://fedoraproject.org/wiki/JefSpaleta/TestingManifesto) and then use one of the scripts at the bottom of this page (http://fedoraproject.org/wiki/Tools/yum).