Could you close this bug or downgrade its severity, or do whatever it
takes so that this *isn't* removed from bullseye? Removing this
package from the bullseye release would cause large problems.
Many people run Debian on different kernels. Therefore the dkms remains
useful and should not be removed.
On Fri, 1 May 2020 15:30:40 + Luca Filipozzi wrote:
> The changes made do not address the bug, I'm afraid. wireguard-dkms
> fails to install because kernel-image 4.19.0-9 includes a backported
> change that is not caught by the pragmas in compat.h. This backport
> might be a Debian-ism that pe
https://git.zx2c4.com/wireguard-linux-compat/commit/?id=4602590adee92557847e61c8cd14445d35fbfa2e
To further summarize ongoing conversations:
It appears that there many be another alternative, midway between the
two extremes of stabilization on one hand and keeping this bug report
open on the other. The idea is to ship WireGuard in stable-backports
and in unstable, but not let this migrate to
dkg and I had a discussion about this recently and he asked me to
summarize my understanding of it.
- WireGuard still prefers to operate on a rolling basis, with new
snapshots totally replacing old ones, with no stability, security, or
other long term guarantees.
- WireGuard probably won't be oper
Debian and all sane distros should revert this commit at once.
Changing the aesthetic of ls output is ugly, confusing, and completely
absurd. The developer who made the commit should think twice next time
before introducing such an unwanted setting and making it the default.
This is a change apprec
7 matches
Mail list logo
