----- Original Message -----
From: "Thorsten Leemhuis" <fedora(a)leemhuis.info>
> +Requires: kernel%{?1:-%{1}}-%{_target_cpu} =
> %{version}-%{release}%{?1:.%{1}}\
Just FYI: Kmod2 packages in some popular add on repo depend on the
kernel they were build for with this:
kernel-uname-r = 3.1.1-2.fc16.x86_64
That seems to work well afaics. I think there was a reason back years
ago why we settled for this strategy and did not use the requires you
chose -- but I can't recall it and maybe it's not relevant any more
these days anyway (and maybe my mind comes up with the reason seconds
after sending this mail...).
Today's broken deps report highlights why kmod2 uses kernel-uname-r
instead. Seems the kernel variant packages (e.g. PAE) don't have a
Provides that includes the variant name. I've switched to putting
the Requires on kernel-uname-r instead, which does include the
variant.
I should have listened to you to begin with :).
josh