2017-07-24 16:28 GMT+02:00 Thorsten Leemhuis <fedora(a)leemhuis.info>:
On 24.07.2017 15:53, Josh Boyer wrote:
> On Mon, Jul 24, 2017 at 9:40 AM, Nicolas Chauvet <kwizart(a)gmail.com> wrote:
>> 2017-07-24 15:28 GMT+02:00 Josh Boyer <jwboyer(a)fedoraproject.org>:
>>> On Mon, Jul 24, 2017 at 9:20 AM, Nicolas Chauvet <kwizart(a)gmail.com>
> And I still don't know what problem you're trying to solve. Still NAK.
I guess the bugzilla number in the subject is meant as an explanation:
FWIW, I welcome that finally someone is working towards getting this
fixed, as it seems users have a hard time understanding and handling
I didn't look to much into this recently, but I think there might be an
easier and better solution: Don't provide variant specific kernel-devel
package at all (like kernel-PAE-devel), just ship one kernel-devel
package that provides the files for all the kernel variants on the
architecture in question (IOW: on x86-32 simply ship the files that
currently are in kernel-PAE-devel in kernel-devel instead & get rid of
kernel-PAE-devel). Sure, kernel-devel gets bigger. But my gut says it's
the better solution (but I didn't check and someone should how much it
grows if we want to go down that route).
First, I apologize to have send a patch that rely on boolean
dependencies whereas this is not yet allowed as our packaging
I thought it was the case, and I will resubmit with an appropriate
notice for a preliminary review (until boolean deps are allowed,
hopefully in the f27 timeline).
So trying to sum-up. On fedora, kernel-devel installation can be wrong
in two ways:
- It's not the appropriate variant (PAE,lpae,rt,debug,up,etc)
- Both versions mismatch. (one has kernel from
fedora-kernel-rawhide-nodebug but kernel-devel from f26-updates (so
4.11.10-300.fc26.x86_64 =/ 4.13.0-0.rc1.git4.1.fc27 mismatch).
This patch and bugreport is only meant to address the latter issue, so
that when a user issue the following command, the right kernel-devel
dnf update kernel --enablerepo=updates-testing
(this fails to grab the kernel-devel from updates-testing, at least
without the patch)
Like you might have noticed, users could have used the following instead:
dnf update kernel\* --enablerepo=updates-testing
(there it works and even without using kernel\* at all)
But , that's not something one can expect from ours users, (and even
from me when distracted). So there is a need to state the appropriate
requires (which the patch implements), otherwise the failure is
The former issue can be fixed in tools using kernel-devel
(akmods,dkms,systemtap,other ?) by using the boolean dependencies such
as Suggests: kernel-lpae-devel if kernel-lpae, etc
The same restriction might apply to boolean dependencies here. So the
plan is to ask for clarification from releng, and implement in the f27
timeline if allowed.
Thx for the review.