From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
Egbert Verhage <egbert@eggiecode.org>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] Seeking Ubuntu PPA Maintainer
Date: Thu, 17 Nov 2016 07:17:19 +0900 [thread overview]
Message-ID: <87bmxf6pe8.fsf@alice.fifthhorseman.net> (raw)
In-Reply-To: <CAHmME9q7GX2CzYDxQC-W7nmjAeRkht+1hQxFRr22be5E244J+Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 749 bytes --]
On Wed 2016-11-16 23:24:35 +0900, Jason A. Donenfeld wrote:
> Hey Egbert, Daniel,
>
> On Wed, Nov 16, 2016 at 12:10 PM, Egbert Verhage <egbert@eggiecode.org> wrote:
>> Git repo: https://git.launchpad.net/wireguard?h=master
>
> Is there a good machine readable URL that I can check for getting the
> latest package version?
>
> For Debian I currently use this cludge, which is totally wrong and terrible:
> curl -s https://anonscm.debian.org/git/collab-maint/wireguard.git/refs/
> | sed -n 's/.*debian\/\([^ ]*\)-experimental[0-9]\+.*/\1/p' | head -n
> 1
for debian, you could use:
rmadison wireguard
if you don't have rmadison installed, you can inspect the content here:
https://qa.debian.org/madison.php?package=wireguard
--dkg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]
next prev parent reply other threads:[~2016-11-16 22:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 20:44 Jason A. Donenfeld
2016-11-15 23:41 ` Egbert Verhage
[not found] ` <454ad249-3313-9423-c2d4-7602d56849fc@eggiecode.org>
2016-11-16 0:12 ` Jason A. Donenfeld
2016-11-16 0:34 ` Egbert Verhage
2016-11-16 1:31 ` Jason A. Donenfeld
2016-11-16 6:20 ` Dan Luedtke
2016-11-16 11:18 ` Egbert Verhage
2016-11-16 11:34 ` Dan Lüdtke
2016-11-16 14:04 ` Jason A. Donenfeld
2016-11-16 10:03 ` Egbert Verhage
2016-11-16 14:09 ` Jason A. Donenfeld
2016-11-16 14:22 ` Egbert Verhage
2016-11-16 14:25 ` Jason A. Donenfeld
2016-11-16 6:45 ` Daniel Kahn Gillmor
2016-11-16 11:10 ` Egbert Verhage
2016-11-16 14:24 ` Jason A. Donenfeld
2016-11-16 22:17 ` Daniel Kahn Gillmor [this message]
2016-11-16 22:52 ` Jason A. Donenfeld
2016-11-16 14:11 ` Jason A. Donenfeld
2016-11-16 14:37 Anonymous Anonymous
2016-11-16 15:00 ` Jason A. Donenfeld
2016-11-16 15:08 ` Egbert Verhage
2016-11-16 14:47 Anonymous Anonymous
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=87bmxf6pe8.fsf@alice.fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=Jason@zx2c4.com \
--cc=egbert@eggiecode.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).