On 11/09/2019 17:30, Daniel Kahn Gillmor wrote: > > It sounds to me like you and David are saying this report is specific to > an interaction with 4.19.0-5 and wireguard 0.0.20190905-1, not that the > problem has to do with a generic upgrade path. > > But hm, maybe the 4.19.0-5 ABI wasn't actually stable? do either of you > (Matthew or David) know what version of 4.19.0-5 was actually running on > your system, vs. what version of linux-headers-4.19.0-5 you had > installed when it was built? That would be a useful datapoint.
I have these. IMHO they haven't changed since: root@mazer:~# apt-cache policy linux-headers-4.19.0-5-amd64 linux-headers-4.19.0-5-amd64: Installed: 4.19.37-5+deb10u2 Candidate: 4.19.37-5+deb10u2 Version table: *** 4.19.37-5+deb10u2 990 990 http://security.debian.org buster/updates/main amd64 Packages 100 /var/lib/dpkg/status
