Problem with 'popt' when updating 'RPM'.

[gizmo777]

Windows user of many years trying linux to get away from Microsoft.
Hence really a Linux newbie and feeling very ignorant!

Have a Toshiba Equium laptop with 1.73 dual core and 2GB RAM.

On my Fedora 16 system, 'Add/Remove software' and 'Software Update' stopped working, with a serious error whenever I tried to start it. Tried solutions from web with no success.

System started as Fedora 13 and was eventually updated to Fedora 16. All worked well until the error with Add/Remove software. Even had Spotify working OK. Could not fix and decided in desperation to try update to Fedora 17 alpha, as last resort. (I know it was drastic, if not plain stupid).

Have had to remove some packages, but now have only 1 error left that I can not solve.

After initial upgrade to FC17 had 1474 updates to apply. Failed mostly due to dependencies and gpg keys ("The problem was not due to yum. The problem was that PackageKit has a bug importing the gpg keys the first time you access a new software repository."), but have been able to overcome/solve all issues except this one:

One software update available:

popt-1.14-1.el5.test (32-bit)

THIS FAILS with message:

rpm-4.9.1.2-12.fc17.i686 requires popt(x86-32) >= 1.10.2.1 : Success - empty transaction

Tried running 'Add/Remove Software' which says I have popt-1.13-10fc17 (32-bit) installed. It shows popt-1.14-1.el5.test (32-bit) as available, but when I try to install that, it says "running" and then "resolving dependencies" then flashes and has stopped. 'Apply' button does nothing. 'Clear' works and clears the check box back to the older version.

Am worried about uninstalling the current version of 'popt' as that was the straw that broke the camel's back with the FC16 setup.

Have tried 'yum update popt*' (as SU) and get the following output:


[root@Equium jules]# yum update popt*
Loaded plugins: presto, priorities, refresh-packagekit
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package popt.i686 0:1.13-10.fc17 will be updated
--> Processing Dependency: popt(x86-32) >= 1.10.2.1 for package: rpm-4.9.1.2-12.fc17.i686
---> Package popt.i386 0:1.14-1.el5.test will be an update
--> Finished Dependency Resolution
Error: Package: rpm-4.9.1.2-12.fc17.i686 (@anaconda-0)
Requires: popt(x86-32) >= 1.10.2.1
Removing: popt-1.13-10.fc17.i686 (@anaconda-0)
popt(x86-32) = 1.13-10.fc17
Updated By: popt-1.14-1.el5.test.i386 (rpmforge-testing)
Not found
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
[root@Equium jules]#

TRIED rpm -Va --nofiles --nodigest

[root@Equium jules]# rpm -Va --nofiles --nodigest

NOTHING

TRIED:
[root@Equium jules]# yum update popt* --skip-broken
Loaded plugins: presto, priorities, refresh-packagekit
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package popt.i686 0:1.13-10.fc17 will be updated
--> Processing Dependency: popt(x86-32) >= 1.10.2.1 for package: rpm-4.9.1.2-12.fc17.i686
---> Package popt.i386 0:1.14-1.el5.test will be an update

Packages skipped because of dependency problems:
popt-1.14-1.el5.test.i386 from rpmforge-testing
[root@Equium jules]#

TRIED:

[root@Equium jules]# yum update
Loaded plugins: presto, priorities, refresh-packagekit
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package popt.i686 0:1.13-10.fc17 will be updated
--> Processing Dependency: popt(x86-32) >= 1.10.2.1 for package: rpm-4.9.1.2-12.fc17.i686
---> Package popt.i386 0:1.14-1.el5.test will be an update
--> Finished Dependency Resolution
Error: Package: rpm-4.9.1.2-12.fc17.i686 (@anaconda-0)
Requires: popt(x86-32) >= 1.10.2.1
Removing: popt-1.13-10.fc17.i686 (@anaconda-0)
popt(x86-32) = 1.13-10.fc17
Updated By: popt-1.14-1.el5.test.i386 (rpmforge-testing)
Not found
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
[root@Equium jules]#



Am not sufficiently knowledgeable to do any more. Please help, any suggestions will be gratefully received.

[glennzo]

For starters, disable the rpmforge repositories. You can do it permanently by changing enabled=1 to enabled=0 in all the rpmforge .repo files. You can do it from the command line on a one-time-only basis with something like this:

PHP Code:

yum --disablerepo=rpmforge* install foo 


Hope this proves to be some sort of help.

And what does the command rpm -qa | grep popt show?

[gizmo777]

Thank you for the swift response.

Have entered the 2 commands as follows:

[root@Equium jules]# yum --disablerepo=rpmforge* install foo
Loaded plugins: presto, priorities, refresh-packagekit
Setting up Install Process
No package foo available.
Error: Nothing to do
[root@Equium jules]#

[root@Equium jules]# rpm -qa | grep popt
popt-1.13-10.fc17.i686
[root@Equium jules]#

This confirms the version of 'popt' that Add/Remove Software reported.

Just entered "yum reprolist" and got:
[root@Equium jules]# yum repolist
Loaded plugins: presto, priorities, refresh-packagekit
adobe-linux-i386 | 951 B 00:00
fedora/metalink | 31 kB 00:00
livna | 3.6 kB 00:00
rpmforge | 1.1 kB 00:00
rpmforge-extras | 1.1 kB 00:00
rpmforge-testing | 1.1 kB 00:00
rpmfusion-free | 1.2 kB 00:00
rpmfusion-free-updates | 1.2 kB 00:00
rpmfusion-free-updates-testing | 2.7 kB 00:00
rpmfusion-nonfree | 1.2 kB 00:00
rpmfusion-nonfree-updates | 1.2 kB 00:00
rpmfusion-nonfree-updates-testing | 2.7 kB 00:00
updates/metalink | 50 kB 00:00
updates-testing/metalink | 33 kB 00:01
repo id repo name status
adobe-linux-i386 Adobe Systems Incorporated 17
fedora Fedora 17 - i386 20,984
livna rpm.livna.org for 17 - i386 5
rpmforge RHEL 17 - RPMforge.net - dag 11,253
rpmforge-extras RHEL 17 - RPMforge.net - extras 213
rpmforge-testing RHEL 17 - RPMforge.net - testing 319
rpmfusion-free RPM Fusion for Fedora 17 - Free 343
rpmfusion-free-updates RPM Fusion for Fedora 17 - Free - Updates 0
rpmfusion-free-updates-testing RPM Fusion for Fedora 17 - Free - Test Updates 121
rpmfusion-nonfree RPM Fusion for Fedora 17 - Nonfree 159
rpmfusion-nonfree-updates RPM Fusion for Fedora 17 - Nonfree - Updates 0
rpmfusion-nonfree-updates-testing RPM Fusion for Fedora 17 - Nonfree - Test Updates 13
updates Fedora 17 - i386 - Updates 0
updates-testing Fedora 17 - i386 - Test Updates 2,982
repolist: 36,409
[root@Equium jules]#

Do I need to modify the repro files under etc/yum ?

Thanks again.

---------- Post added at 09:46 PM ---------- Previous post was at 09:21 PM ----------

Hi,

Checked the .repo files and have disabled the rpmforge repositories.

[root@Equium jules]# yum repolist
Loaded plugins: presto, priorities, refresh-packagekit
repo id repo name status
adobe-linux-i386 Adobe Systems Incorporated 17
fedora Fedora 17 - i386 20,984
livna rpm.livna.org for 17 - i386 5
rpmfusion-free RPM Fusion for Fedora 17 - Free 343
rpmfusion-free-updates RPM Fusion for Fedora 17 - Free - Updates 0
rpmfusion-free-updates-testing RPM Fusion for Fedora 17 - Free - Test Updates 121
rpmfusion-nonfree RPM Fusion for Fedora 17 - Nonfree 159
rpmfusion-nonfree-updates RPM Fusion for Fedora 17 - Nonfree - Updates 0
rpmfusion-nonfree-updates-testing RPM Fusion for Fedora 17 - Nonfree - Test Updates 13
updates Fedora 17 - i386 - Updates 0
updates-testing Fedora 17 - i386 - Test Updates 2,982
repolist: 24,624
[root@Equium jules]#

Software update now reports 'All software up to date'.

Many thanks for your help.

Can I ask, what is the problem with the rpmforge repositories?

Cheers.

[glennzo]

There's nothing "wrong" with the rpmforge repos but they're not necessary for Fedora unless you need some package that the usual Fedora repos don't provide. The general wisdom is to keep repos such as rpmforge disabled by default and enable them on a one-time-only basis, the reverse of what I showed above.
yum --enablerepo=rpmforge install foo

By the way, there is no package "foo".


You don't need the livna repo either.

[gizmo777]

Thanks again.

I have disabled the livna repo, as you suggest.

One of the many packages I had to uninstall to get things updating was 'brasero'. Have reinstalled it and a subsequent update check gave this reason for failure to process request:

brasero-3.3.91-3.fc17.i686 requires libtracker-sparql-0.12.so.0 : Success - empty transaction

The update is for "Desktop-neutral search tool and indexer.

This package, libtracker-sparql-0.12.so.0 is apparently available on the Rawhide repository. Tried enabling the Rawhide repositories, but no change.

I am obviously breaking some rules as I don't have enough knowledge of Linux.

Thanking you in anticipation.

Cheers.

[glennzo]

Fedora 17 is stil in Alpha stage so there are bound to be some packages that are problematic. Things will be broken. You'll encounter a lot of yum errors, maybe even in the week or two after it is released as final. That's the way it is.

At this point, with your limited knowledge of Linux, you would be far better off installing Fedora 16.

[gizmo777]

I kind of figured that was the situation. Having updated to 17 to cure problems, is there any way to roll back with the need for a complete new install?

Thanks for the help.

---------- Post added at 09:06 AM ---------- Previous post was at 09:04 AM ----------

Should have said WITHOUT need for fresh install.

It took a long time to get everything working (including Spotify)!

Cheers.

[glennzo]

At this point you should probably just run with what you have if you don't want to completely reinstall Fedora 16. Trying to downgrade will be more of a disaster than leaving things as it. Sticking with Fedora 17 will be a bumpy road for a few months (final release in May), but eventually most all issues will be ironed out and it should be smooth sailing, just like it is with previous releases. Just keep updating the system and learn how to work around the errors that yum will throw at you. It's not too difficult but it takes a little patience and some times it takes more time than you want to spend but in the end all will be well. There are a zillion threads here dealing with yum errors and what to do about them. There are also a plenty of members here who can, and are usually willing to, help.

Don't take this as a personal attack but when you play with Alpha releases and you have little to no experience with Linux you are going to get burned real fast. Alpha releases are "not ready for prime time". Even with my experience I don't usually bother with an Alpha release. Too much trouble. It takes a lot of work to keep it running smoothly so I usually wait for the Beta.