nss in updates-testing - more problems

Michael Schwendt mschwendt at gmail.com
Thu Sep 16 12:58:02 UTC 2010


On Thu, 16 Sep 2010 08:40:20 -0400, Genes wrote:

> 
>   I have both 64 and 32 bit libs installed.

Then let Yum handle it instead of asking explicitly for i686 or x86_64.

> 
>              ....
> 
>           Error: Package: nss-tools-3.12.6-12.fc13.i686
>                           (@/nss-tools-3.12.6-12.fc13.i686)
>            Requires: nss = 3.12.6-12.fc13
>            Removing: nss-3.12.6-12.fc13.i686 (@updates)
>                nss = 3.12.6-12.fc13
>            Updated By: nss-3.12.7-6.fc13.i686 (updates-testing)
>                nss = 3.12.7-6.fc13
>            Available: nss-3.12.6-4.fc13.i686 (fedora)
>                nss = 3.12.6-4.fc13

https://admin.fedoraproject.org/updates/nspr-4.8.6-1.fc13,nss-util-3.12.7-2.fc13,nss-softokn-3.12.7-6.fc13,nss-3.12.7-6.fc13

According to that ticket, no testers have noticed broken deps. The broken
deps check doesn't find anything either.

>     All above problems seem to be in 32 bit libs so :
> 
>            yum --enablerepo=updates-testing update nss.x86_64
> nspr.x86_64 nss-tools.x86_64
> 
> 
>           This succeeds -  but why did this drag in some 32 bit libs ?

Because some dependencies aren't arch-specific and the other arch
provides packages with the required EVR.

> ** Found 3 pre-existing rpmdb problem(s), 'yum check' output follows:
> nspr-4.8.6-1.fc13.x86_64 is a duplicate with nspr-4.8.4-2.fc13.i686
> nss-3.12.7-6.fc13.x86_64 is a duplicate with nss-3.12.6-12.fc13.i686
> nss-tools-3.12.7-6.fc13.x86_64 is a duplicate with
> nss-tools-3.12.6-12.fc13.i686
> 
>    -----------------------------
> 
>   The check seems totally false .. what is broken here ? rpm, yum or the
> packages ?
 
What's strange here is that the EVRs of your i686 and x86_64 packages
don't match. They are built from the same src.rpm and published at once,
so why your i686 packages are newer, no idea. I've never encountered that
before on a multi-arch x86_64 installation, so I can't comment on
it. Perhaps you've somehow managed to arrive at that state by asking Yum
explicitly for i686 updates when actually you needed both, i686 and
x86_64.


More information about the test mailing list