Problems installing Thunderbird 3.0.10 on Fedora 12-64 bits

[donfisico]

Dear members of the forum,

I am here because I face the following problem: recently the update notifier get me the news that I have to uptdate my Mozilla Thunderbird mail client (now version 3.06) to the newest version 3.0.10. Well, no problem I say to myself and I click in "Install updates" as I usually do. Well, the problem appeared: for this v. of Thunderbird I need the package nss-3.12-8 the update manager somehow does not retireve it and I have the last (not testing version ) of nss-3.12.7-6. Well, I thought then to install manually and downloading nss-3.12.8-2 from RPMfind and also its dependencies nss-softtkn-3.12.8-1 , nss-softkon-freebl-3.12.8-1
and nss-util-3.12.8-1 (all the versions for my version of fedora 12, and my architecture x86-64). All went well installing the dependencies of nss, but when I tried to install nss-3.12.8-2 I get the following message

Errorrs in the proof of transaction: package nss-softokn-3.12.8-1.fc12.x86_64 (which is newer than nss-softokn-3.12.7-6.fc12.i686) is already installed
package nss-util-3.12.8-1.fc12.x86_64 (which is newer than nss-util-3.12.7-2.fc12.i686) is already installed

Well, in this way I could not get install nss and therefor also can not install the last version of Thunderbird!
Any help?

[PabloTwo]

Hello, I just ran into this same problem yesterday. It's easy enough to resolve. The problem is that the updated nss*-3.12.8 version files required by the thunderbird update have not yet been pushed to the standard "updates" repo.

I fixed this for myself by browsing to a F12 "updates-testing" mirror site (for i386) and then used the wget command to download the suite of nss files. I then used "yum localupdate nss*.rpm", followed by "yum update thunderbird".

You can probably achieve the same results by doing:

su
yum --exclude=thunderbird update
yum --enablerepo=updates-testing update thunderbird

The nss related files on my system that needed updating were:

Nov 02 22:22:08 Updated: nss-util-3.12.8-1.fc12.i686
Nov 02 22:22:09 Updated: nss-softokn-freebl-3.12.8-1.fc12.i686
Nov 02 22:22:10 Updated: nss-softokn-3.12.8-1.fc12.i686
Nov 02 22:22:11 Updated: nss-3.12.8-2.fc12.i686
Nov 02 22:22:12 Updated: nss-sysinit-3.12.8-2.fc12.i686

---------- Post added at 02:14 PM GMT ---------- Previous post was at 02:03 PM GMT ----------

You got that yum error because you were trying to install one package at a time (I think). You would need to use the "yum localinstall nss*" command, installing all of them at once, making sure you have all the updated nns-* package files downloaded, and let yum resolve the dependency order. If you missed any, then the transaction would fail. Either of the methods I outlined should work.

[CubicleDweller]

Thanks to both previous posters in this thread for their useful contributions.

I have a similar problem. On FC12, I run an update more-or-less once a day. As an "old-school" user, I do it from the command line with yum. For the last couple of days, I've been getting this:

[root@kentucky ~]# yum update
Loaded plugins: changelog, presto, refresh-packagekit
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package thunderbird.i686 0:3.0.10-1.fc12 set to be updated
--> Processing Dependency: nss >= 3.12.8 for package: thunderbird-3.0.10-1.fc12.i686
--> Finished Dependency Resolution
Error: Package: thunderbird-3.0.10-1.fc12.i686 (updates)
           Requires: nss >= 3.12.8
           Installed: nss-3.12.7-6.fc12.i686 (@updates)
               nss = 3.12.7-6.fc12
           Available: nss-3.12.4-14.fc12.i686 (fedora)
               nss = 3.12.4-14.fc12
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
[root@kentucky ~]#

But here's the question that puzzles me: why was this new version of thunderbird pushed to the "updates" repository, when the version of nss that it requires is not yet in that repository? Is there not some sort of automated version-checking system in place to prevent that sort of thing?

This is not the first time I've seen this happening. I know, Fedora is free, and I've no right to complain; I'm just genuinely puzzled as to how this sort of thing can happen; surely the very capable people who work on Fedora can figure out a way of blocking the release of RPMs to one of the stable repositories that depend on version of other RPMs that are not yet in any of the stable repositories? To be fair, I suspect that such a system is in place, and that there was something unusual about this thunderbird release that allowed it to slip through.

Just my 2 cents. FWIW, I'll just wait this one out. Thanks again.