Created attachment 868233 [details] build.log I have a binhost which does not have wireless but builds binary packages for a machine that does. With the newest wireless-regdb it can no longer build on the binhost: ``` * With CONFIG_CFG80211 unset, the driver(s) won't be able to load the regulatory.db from * /lib/firmware, resulting in broken regulatory domain support. Please set CONFIG_CFG80211=m. * Starting from kernel version 4.15 net-wireless/crda is no longer needed. * The crda USE flag will be removed on or after Feb 01, 2024 * Checking for suitable kernel configuration options ... * CONFIG_EXPERT: is not set when it should be. [ !! ] * Please check to make sure these options are set correctly. * Failure to do so may cause unexpected problems. * Once you have satisfied these options, please try merging * this package again. * ERROR: net-wireless/wireless-regdb-20230503-r1::gentoo failed (pretend phase): * Incorrect kernel configuration options ``` Should these checks yield warnings instead of errors?
Created attachment 868234 [details] emerge --info
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b0deafa90af353e022cf48c5d6353ddd1468ba82 commit b0deafa90af353e022cf48c5d6353ddd1468ba82 Author: Rick Farina <zerochaos@gentoo.org> AuthorDate: 2023-08-19 20:55:52 +0000 Commit: Rick Farina <zerochaos@gentoo.org> CommitDate: 2023-08-19 20:58:13 +0000 net-wireless/wireless-regdb: fix check bug Thanks to help from negril as these check logics hurt my head. Closes: https://bugs.gentoo.org/912647 Signed-off-by: Rick Farina <zerochaos@gentoo.org> net-wireless/wireless-regdb/wireless-regdb-20230503-r1.ebuild | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
There will be additional logic needed to properly handle binhosts builds. And asserting that the host this is installed is properly configured. But given that this is purely firmware, there is also no reason to build this on a binhost.
It was an accidental oversight that the checks were fatal, and also a little wrong. The ebuild has been updated. I don't think it will cause any issues on a binhost now.
