add BUILD_EXCLUSIVE_CONFIG#269
Conversation
|
With the few things it's be perfect. Please double-check with other Debian/Ubuntu patches and send them all upstream. Thanks in advance o/ |
2b5d819 to
4bc767f
Compare
| module_status_built_extra() ( | ||
| set_module_suffix "$3" | ||
| read_conf "$3" "$4" "$dkms_tree/$1/$2/source/dkms.conf" | ||
| read_conf "$3" "$4" "$dkms_tree/$1/$2/source/dkms.conf" 2>/dev/null |
There was a problem hiding this comment.
Why are we masking only this one and not the other dozen+ instances of read_conf/read_conf_or_die?
308abc7 to
10209c7
Compare
|
@anbe42 the Ubuntu tests are failing - it seems like the "update-secureboot-policy" change is causing some additional changes/output. Can you fix those up? With that we should be good to land. |
|
If we enroll the created key on Ubuntu, why we not do the same on other distributions? |
bd51788 to
a205e55
Compare
a205e55 to
d67671c
Compare
|
rebased onto additional fixes arising from discussion on the recently merged PRs, now all green ;-) |
|
with that merged, all my open bugs and PRs should be addressed and most Debian issues should be resolved and upstreamed ;-) |
d67671c to
8cd309f
Compare
there is no point in special casing a mismatching return code of 0
the bash idiom <(foo) relies on the /dev/fd -> /proc/self/fd symlink if /proc is not mounted, dkms status (and other actions) may fail with /usr/sbin/dkms: line ####: /dev/fd/##: No such file or directory https://bugs.debian.org/810665
…derr" This reverts commit 288f580.
skip building the module if kernelver does not satisfy BUILD_EXCLUSIVE_KERNEL_MIN <= kernelver <= BUILD_EXCLUSIVE_KERNEL_MAX Closes dkms-project#300
support build exclusion depending on kernel features being present/absent, e.g. BUILD_EXCLUSIVE_CONFIG="CONFIG_FOO !CONFIG_BAR" Closes dkms-project#219
this is a purely cosmetic change to get a "natural" processing order in case multiple kernels versions are installed, e.g. 4.1 < 4.2 < 4.10 < 5.0 instead of alphanumeric order, e.g. 4.1 < 4.10 < 4.2 < 5.0
8cd309f to
40e0d85
Compare
|
Fixing shellcheck warnings/issues gets a huge 💯 👍 from me. Although let's keep those a separate follow-up PR. It's very easy to follow the suggestions and break thing in unexpected ways - it has happened (both to me and friends) a number of times. With the shellcheck commit dropped, this is ready to merge. |
40e0d85 to
4f4d7d9
Compare
|
I've split the fixes for obvious errors from the shellcheck commit into separate verbose commits and left the quoting style changes for later. |
SC2070 (error): -n doesn't work with unquoted arguments. Quote or use [[ ]].
SC2157 (error): Argument to implicit -n is always true due to literal strings.
SC2071 (error): > is for string comparisons. Use -gt instead.
4f4d7d9 to
a2f3983
Compare
this is used in multiple case "$running_distribution" in ... statements that are independent of $addon_modules_dir
| # These can come from the environment or the config file | ||
| [[ ! ${ADDON_MODULES_DIR} && -e /etc/sysconfig/module-init-tools ]] && . /etc/sysconfig/module-init-tools | ||
| addon_modules_dir="${ADDON_MODULES_DIR}" | ||
| [[ ! ${addon_modules_dir} ]] && running_distribution="$(distro_version)" |
There was a problem hiding this comment.
This looks right, but has a high risk of causing regressions. Let's merge it here and it can be reverted independently if needed.
|
With all my patches merged, what do are your plans for making a new release? |
|
No objections on my end although I have no idea what to do 😅 @scaronni can you share some pointers - be that here or throw them in a RELEASE.md file within git? Thanks o/ |
|
Well, there is no rule, I got the repository as is 😄 I'll make a release now, but in general just bump the release in the |
Since version 3.0.11 <dkms-project/dkms#269>, dkms supports the [`BUILD_EXCLUSIVE_CONFIG`] option in dkms.conf to specify kernel configuration options which must be enabled in the targeted kernel. Add this option with `CONFIG_HID`, `CONFIG_INPUT_FF_MEMLESS`, and `CONFIG_POWER_SUPPLY`, since xpadneo will fail to modpost if any of these are disabled. If a user installs a kernel where these options are disabled, the module will not be built and a warning similar to the following is printed: Warning: The /var/lib/dkms/hid-xpadneo/v0.9-144-g9b3b696-dirty/6.8.0-rc2/x86_64/dkms.conf for module hid-xpadneo includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config. This indicates that it should not be built. dkms autoinstall on 6.8.0-rc2/x86_64 was skipped for hid-xpadneo Without this option, the module build would fail and the kernel package would fail to install, leaving the user with a partially installed kernel package (on Debian, at least). [`BUILD_EXCLUSIVE_CONFIG`]: https://manpages.debian.org/unstable/dkms/dkms.8.en.html#BUILD_EXCLUSIVE_CONFIG= Signed-off-by: Kevin Locke <kevin@kevinlocke.name>
Since version 3.0.11 <dkms-project/dkms#269>, dkms supports the [`BUILD_EXCLUSIVE_CONFIG`] option in dkms.conf to specify kernel configuration options which must be enabled in the targeted kernel. Add this option with `CONFIG_HID`, `CONFIG_INPUT_FF_MEMLESS`, and `CONFIG_POWER_SUPPLY`, since xpadneo will fail to modpost if any of these are disabled. If a user installs a kernel where these options are disabled, the module will not be built and a warning similar to the following is printed: Warning: The /var/lib/dkms/hid-xpadneo/v0.9-144-g9b3b696-dirty/6.8.0-rc2/x86_64/dkms.conf for module hid-xpadneo includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config. This indicates that it should not be built. dkms autoinstall on 6.8.0-rc2/x86_64 was skipped for hid-xpadneo Without this option, the module build would fail and the kernel package would fail to install, leaving the user with a partially installed kernel package (on Debian, at least). [`BUILD_EXCLUSIVE_CONFIG`]: https://github.com/dell/dkms/blob/782bd07641b957012f9b8d621bf9b51f82bfc728/dkms.8.in#L688-L696 Signed-off-by: Kevin Locke <kevin@kevinlocke.name>
Since version 3.0.11 <dkms-project/dkms#269>, dkms supports the [`BUILD_EXCLUSIVE_CONFIG`] option in dkms.conf to specify kernel configuration options which must be enabled in the targeted kernel. Add this option with `CONFIG_HID`, `CONFIG_INPUT_FF_MEMLESS`, and `CONFIG_POWER_SUPPLY`, since xpadneo will fail to modpost if any of these are disabled. If a user installs a kernel where these options are disabled, the module will not be built and a warning similar to the following is printed: Warning: The /var/lib/dkms/hid-xpadneo/v0.9-144-g9b3b696-dirty/6.8.0-rc2/x86_64/dkms.conf for module hid-xpadneo includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config. This indicates that it should not be built. dkms autoinstall on 6.8.0-rc2/x86_64 was skipped for hid-xpadneo Without this option, the module build would fail and the kernel package would fail to install, leaving the user with a partially installed kernel package (on Debian, at least). [`BUILD_EXCLUSIVE_CONFIG`]: https://github.com/dell/dkms/blob/782bd07641b957012f9b8d621bf9b51f82bfc728/dkms.8.in#L688-L696 Signed-off-by: Kevin Locke <kevin@kevinlocke.name>
Since version 3.0.11 <dkms-project/dkms#269>, dkms supports the [`BUILD_EXCLUSIVE_CONFIG`] option in dkms.conf to specify kernel configuration options which must be enabled in the targeted kernel. Add this option with `CONFIG_HID`, `CONFIG_INPUT_FF_MEMLESS`, and `CONFIG_POWER_SUPPLY`, since xpadneo will fail to modpost if any of these are disabled. If a user installs a kernel where these options are disabled, the module will not be built and a warning similar to the following is printed: Warning: The /var/lib/dkms/hid-xpadneo/v0.9-144-g9b3b696-dirty/6.8.0-rc2/x86_64/dkms.conf for module hid-xpadneo includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config. This indicates that it should not be built. dkms autoinstall on 6.8.0-rc2/x86_64 was skipped for hid-xpadneo Without this option, the module build would fail and the kernel package would fail to install, leaving the user with a partially installed kernel package (on Debian, at least). [`BUILD_EXCLUSIVE_CONFIG`]: https://github.com/dell/dkms/blob/782bd07641b957012f9b8d621bf9b51f82bfc728/dkms.8.in#L688-L696 Signed-off-by: Kevin Locke <kevin@kevinlocke.name>
Since version 3.0.11 <dkms-project/dkms#269>, dkms supports the [`BUILD_EXCLUSIVE_CONFIG`] option in dkms.conf to specify kernel configuration options which must be enabled in the targeted kernel. Add this option with `CONFIG_HID`, `CONFIG_INPUT_FF_MEMLESS`, and `CONFIG_POWER_SUPPLY`, since xpadneo will fail to modpost if any of these are disabled. If a user installs a kernel where these options are disabled, the module will not be built and a warning similar to the following is printed: Warning: The /var/lib/dkms/hid-xpadneo/v0.9-144-g9b3b696-dirty/6.8.0-rc2/x86_64/dkms.conf for module hid-xpadneo includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config. This indicates that it should not be built. dkms autoinstall on 6.8.0-rc2/x86_64 was skipped for hid-xpadneo Without this option, the module build would fail and the kernel package would fail to install, leaving the user with a partially installed kernel package (on Debian, at least). [`BUILD_EXCLUSIVE_CONFIG`]: https://github.com/dell/dkms/blob/782bd07641b957012f9b8d621bf9b51f82bfc728/dkms.8.in#L688-L696 Signed-off-by: Kevin Locke <kevin@kevinlocke.name>
support build exclusion depending on kernel features being present/absent, e.g. BUILD_EXCLUSIVE_CONFIG="CONFIG_FOO !CONFIG_BAR"