From: Barry Scott <barry@barrys-emacs.org>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: wireguard broke with recent update on fedora 31
Date: Sun, 5 Jan 2020 21:38:41 +0000 [thread overview]
Message-ID: <15BB190B-4C85-4329-A44D-7011D89BAD84@barrys-emacs.org> (raw)
In-Reply-To: <a4e5e78d-afa0-c7d5-30dc-56fa139c3a85@solidadmin.com>
> On 3 Jan 2020, at 17:53, Joe Doss <joe@solidadmin.com> wrote:
>
> Hey Barry,
>
> Some older versions are building now:
>
> https://copr.fedorainfracloud.org/coprs/jdoss/wireguard/builds/
>
> I have not tested them as I had to make some changes so the old repo
> sources to build the src RPMs. Let me know if you run into any issues.
dnf downgrade put me in this state:
$ rpm -qa | grep wireguard
wireguard-dkms-0.0.20191219-1.fc31.noarch
wireguard-tools-1.0.20200102-1.fc31.x86_64
$ uname -r
5.3.12-300.fc31.x86_64
But wireguard is not working.
Looking at the dnf history I think this is the point at which it went from working to not working.
$ dnf history info 97 | grep -e kernel -e wireguard -e Begin
Begin time : Tue 10 Dec 2019 12:49:28 GMT
Begin rpmdb : 527:133702206fb808b6a14cfbbd59ce0971e85d1f6c
Install kernel-5.3.15-300.fc31.x86_64 @updates
Install kernel-core-5.3.15-300.fc31.x86_64 @updates
Install kernel-devel-5.3.15-300.fc31.x86_64 @updates
Install kernel-modules-5.3.15-300.fc31.x86_64 @updates
Upgrade wireguard-dkms-1:0.0.20191206-1.fc31.noarch @jdoss-wireguard
Upgraded wireguard-dkms-1:0.0.20191127-1.fc31.noarch @@System
Upgrade wireguard-tools-1:0.0.20191206-1.fc31.x86_64 @jdoss-wireguard
Upgraded wireguard-tools-1:0.0.20191127-1.fc31.x86_64 @@System
Removed kernel-5.3.8-300.fc31.x86_64 @@System
Removed kernel-core-5.3.8-300.fc31.x86_64 @@System
Removed kernel-devel-5.3.8-300.fc31.x86_64 @@System
Removed kernel-modules-5.3.8-300.fc31.x86_64 @@System
If that is the change that introduced the break then I need the 2019 11 27 version
for the next bisect test.
Barry
>
> Joe
>
>
>
> --
> Joe Doss
> joe@solidadmin.com
> <pEpkey.asc>_______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2020-01-09 6:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-31 12:03 wireguard broke with recent update on fedora 31 Barry Scott
2020-01-02 20:11 ` Jason A. Donenfeld
2020-01-02 22:58 ` Barry
2020-01-03 17:24 ` Joe Doss
2020-01-03 17:53 ` Joe Doss
2020-01-05 21:38 ` Barry Scott [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15BB190B-4C85-4329-A44D-7011D89BAD84@barrys-emacs.org \
--to=barry@barrys-emacs.org \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).