Kaixo!
On Sat, Feb 19, 2000 at 04:53:29AM -0800, Brian J. Murrell wrote:
> I was trying to bring my system up to date with cooker today and found
> the following dependancy breakage:
>
> kernel >= 2.2.5 is needed by nfs-utils-0.1.6-1mdk
>
> Yet I have several packages providing kernel >= 2.2.5
>
> $ rpm -q --whatprovides kernel=2.2.14
> kernel-fb-2.2.14-15mdk
The problem is that the versions don't work with provides given by
Provides: line (that is they only work for package names).
So you have "kernel-fb" = 2.2.14 and "kernel=2.2.14" which means nothing.
"kernel-fb" can provide "kernel" but without version, so a request for
"kernel" of a given version will allways fail.
You know however the it is a correct version; so you can use --nodeps;
you have no choice indeed.
> $ rpm -q --whatprovides kernel=2.2.15
"kernel=2.2.15" is different of "kernel" of version 2.2.15
> kernel-fb-2.2.15-0.7mdk
Try 'rpm -q --whatprovides kernel-fb=2.2.15' and you will see.
> $ rpm -q --provides kernel-fb-2.2.14-17bjm
> kernel=2.2.14
> module-info
The *.spec file of kernel building is wrong; all "Provide: kernel=%{version}"
must be changed to "Provide: kernel", no versioning can be used on
the Provide: line
To chmou: I think the right way to handle that will be to have those packages
just provide "kernel" (as they should) then patch rpm so for any "provides"
it takes the version number of the package, when checking version numbers.
> Why does rpm fail to recognize all of those packages providing kernel >=
> 2.2.5?
Because they don't provide kernel >= 2.2.5, they provide a strange thing
called "kernel=2.2.14"
> This problem exists for more packages than just nfs-utils.
As you have no package that provides "kernel" then any package requiring
it will fail.
> --
> Brian J. Murrell InterLinx Support Services, Inc.
> North Vancouver, B.C. 604 983 UNIX
> Platform and Brand Independent UNIX Support - R3.2 - R4 - BSD
--
Ki �a vos v�ye b�n,
Pablo Saratxaga
http://www.ping.be/~pin19314/ PGP Key available, key ID: 0x8F0E4975
