From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/sslh: fixup the 'v' prefix in the version
Date: Sun, 15 Sep 2019 10:14:47 +0200 [thread overview]
Message-ID: <87d0g23rig.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190915095832.467729c3@windsurf.home> (Thomas Petazzoni's message of "Sun, 15 Sep 2019 09:58:32 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
> On Sun, 15 Sep 2019 09:17:57 +0200
> Peter Korsgaard <peter@korsgaard.com> wrote:
>> >>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
>>
>> > In order for the sslh version to match what is given by
>> > release-monitoring.org, the 'v' prefix should be encoded in
>> > SSLH_SOURCE and not SSLH_VERSION.
>>
>> > Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
>> > ---
>> > package/sslh/sslh.mk | 3 ++-
>>
>> You don't seem to change sslh.hash?
> The tarball name doesn't change:
> -SSLH_VERSION = v1.20
> +SSLH_VERSION = 1.20
> +SSLH_SOURCE = sslh-v$(SSLH_VERSION).tar.gz
> This package is not fetched from Github, so it's not us who control the
> tarball name. Here the tarball name is the one from upstream, and it
> doesn't change, so the .hash file doesn't change.
> After applying this patch:
> sslh-v1.20.tar.gz: OK (sha256: a7f49b0a1cfcb7bb9d97f5ffa932bff11c5f65d9a9bd8fe1812481dee5855116)
>>>> sslh 1.20 Extracting
> gzip -d -c /home/thomas/dl/sslh/sslh-v1.20.tar.gz | tar --strip-components=1 -C /home/thomas/projets/buildroot/output/build/sslh-1.20 -xf -
Ahh yes, indeed - Sorry for the noise.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-09-15 8:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 17:46 [Buildroot] [PATCH 1/1] package/sslh: fixup the 'v' prefix in the version Fabrice Fontaine
2019-09-15 7:17 ` Peter Korsgaard
2019-09-15 7:58 ` Thomas Petazzoni
2019-09-15 8:14 ` Peter Korsgaard [this message]
2019-09-15 7:58 ` Thomas Petazzoni
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=87d0g23rig.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.