Currently the package r8125 is marked as broken because "r8125 has been integrated into the kernel as of v5.9.1". The problem I'm facing is that the module integrated into the kernel is causing issues that the separate r8125 package isn't. For example, sometimes during heavy load I'm getting errors like this one [48338.252937] r8169 0000:01:00.0 enp1s0: NETDEV WATCHDOG: CPU: 4: transmit queue 0 timed out 5863 ms.
It's possible to allow building broken packages but I'd prefer if this package wasn't marked as broken at all.
Currently the package r8125 is marked as broken because "r8125 has been integrated into the kernel as of v5.9.1". The problem I'm facing is that the module integrated into the kernel is causing issues that the separate r8125 package isn't. For example, sometimes during heavy load I'm getting errors like this one
[48338.252937] r8169 0000:01:00.0 enp1s0: NETDEV WATCHDOG: CPU: 4: transmit queue 0 timed out 5863 ms
.It's possible to allow building broken packages but I'd prefer if this package wasn't marked as broken at all.
@peelz
Add a :+1: reaction to issues you find important.