Arch Linux

I had the same question, I just have the latest lts kernel but the new dependencies of broadcom-wl-dkms-6.30.223.271-34 is forcing me to install linux-6.0.1.arch2-1 linux-headers-6.0.1.arch2-1 . If I remember correctly broadcom-wl-dkms as the name implies was dependant on dkms to install on older kernels like linux-lts and the package broadcom-wl was the binary version for the latest kernel (now linux-6.0.1.arch2-1), another thing I've noticed is that the package broadcom-wl-dkms as expected conflicts with broadcom-wl (according to the package's info and page) , but at the same time broadcom-wl depends on broadcom-wl-dkms! How is it possible for package A to depend on package B while package B conflicts with package A, hence they can not coexist at the same time on a machine? I will IgnorePkg the broadcom-wl-dkms for the time being.

Same here with `linux-zen`; maybe the issue is on the not-linux packages which are not recognized as linux kernel packages, that is `linux-zen` should have the "provides=(linux)" array, as well for the headers package: `linux-zen-headers` with "provides=(linux-headers)" array...

I would raise the severity of this issue since it blocks us to upgrade to version 6, since new broadcom-wl-dkms package contains linux 6 patch.

Same problem over here: https://bugs.archlinux.org/task/76211
WiFi not detected after upgrade.

Good thing, the bug is already raised. May be the maintainer of broadcom-wl-dkms has refered broadcom-wl dependencies: https://archlinux.org/packages/community/x86_64/broadcom-wl/ , which needed linux and linux-headers.

@mattia if the provides were added, then i think multiple different kernels cannot be added since they provide the same package linux and linux-headers which in turn makes conflict.

@nTia89 we didn't have this problem with the previous version (6.30.223.271-33) and it did not depend on linux and linux-headers, the only dependency was dkms as it should, and none of the kernel packages provides linux or linux-lts or linux-zen (it is just implied by the package name), The problem is broadcom-wl-dkms should not be dependant on linux and linux-headers packages, since being dependant on dkms implies needing "a" kernel and its headers.

i agree with @behnam

I do not think so; we would have that problem with the "conflict=()" array... in fact, both `linux` and `linux-zen` provide some common MODULEs (let's compare their PKGBUILDs).

Anyway, the point is another: the ratio behind this change and the only one who can answer is the package maintainer itself, Alexander Rødseth.

One hypothesis could be: DKMS works (can build modules) together with kernel headers; that is, without it, it's useless; but if he added them (linux+headers) for this reason, I have one (+one) issues the expose: first, `broadcom-wl-dkms` depends on `dkms` in turns it optionally depends on kernel-headers; second, the `broadcom-wl-dkms` can switch those dependencies from hard to optional.

How i can install a previously 33 version?

@wowblvck It should be available on your system, just try this :

sudo pacman -U /var/cache/pacman/pkg/broadcom-wl-dkms-6.30.223.271-33-x86_64.pkg.tar.zst

I added linux and linux headers to make testing easier for myself as without the additions DKMS has no kernel in a clean chroot to build the module against.
I forgot to remove the additions before posting [1], I then noticed the issue and the diff referenced in [2] did not change the depends.

[1] https://bbs.archlinux.org/viewtopic.php?pid=2061961#p2061961
[2] https://bbs.archlinux.org/viewtopic.php?pid=2061964#p2061964

Thanks for reporting. The updated package without the linux and linux-header dependencies will appear in [community] shortly. Please test and re-open this issue if there should be further issues with this. Thanks.