From: Eddie <stunnel@attglobal.net>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Procedure for Updating Snapshot
Date: Sun, 13 May 2018 13:21:32 -0700 [thread overview]
Message-ID: <22f3ea2f-b76e-e106-3e62-4584241e8d1a@attglobal.net> (raw)
What is the correct procedure for updating WG with a new snapshot.
I'm currently running CentOS 7.4 and previously had installed the
20180420 snapshot. Today, I tried to update with the new 20180513 one,
and it appears to be failing. The command I used was: yum update
--disablerepo=* --enablerepo=jdoss-wireguard wireguard*
This resulted in the following messages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Updating :
1:wireguard-dkms-0.0.20180513-1.el7.centos.noarch 1/4
warning: %post(wireguard-dkms-1:0.0.20180513-1.el7.centos.noarch)
scriptlet failed, exit status 10
Non-fatal POSTIN scriptlet failure in rpm package
1:wireguard-dkms-0.0.20180513-1.el7.centos.noarch
Updating :
1:wireguard-tools-0.0.20180513-1.el7.centos.x86_64 2/4
Cleanup :
1:wireguard-tools-0.0.20180420-1.el7.centos.x86_64 3/4
Cleanup :
1:wireguard-dkms-0.0.20180420-1.el7.centos.noarch 4/4
Verifying :
1:wireguard-dkms-0.0.20180513-1.el7.centos.noarch 1/4
Verifying :
1:wireguard-tools-0.0.20180513-1.el7.centos.x86_64 2/4
Verifying :
1:wireguard-tools-0.0.20180420-1.el7.centos.x86_64 3/4
Verifying :
1:wireguard-dkms-0.0.20180420-1.el7.centos.noarch 4/4
Updated:
wireguard-dkms.noarch 1:0.0.20180513-1.el7.centos
wireguard-tools.x86_64 1:0.0.20180513-1.el7.centos
Complete!
However, the extra/wireguard.ko module was not built.
I then realised that I had not stopped the running instance, and so ran:
systemctl stop wg-quick@wg0
yum reinstall --disablerepo=* --enablerepo=jdoss-wireguard wireguard*
This resulted in exactly the same errors and again the
extra/wireguard.ko module was not built.
What am I doing wrong here.
Cheers.
next reply other threads:[~2018-05-13 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-13 20:21 Eddie [this message]
2018-05-13 21:29 ` Jason A. Donenfeld
2018-05-14 5:05 ` Eddie
2018-05-14 14:50 ` Joe Doss
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=22f3ea2f-b76e-e106-3e62-4584241e8d1a@attglobal.net \
--to=stunnel@attglobal.net \
--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).