From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH v2] dmidecode: update to 3.2
Date: Mon, 07 Jan 2019 17:45:47 +0000 [thread overview]
Message-ID: <2334131B-C124-4AF5-AE46-CD89E72E9B96@ipfire.org> (raw)
In-Reply-To: <8f8b1957-9534-00ad-20fc-3fcdee52e79a@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]
Thanks.
How did you build this before?
> On 7 Jan 2019, at 17:24, Peter Müller <peter.mueller(a)link38.eu> wrote:
>
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
> dmidecode/dmidecode.nm | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/dmidecode/dmidecode.nm b/dmidecode/dmidecode.nm
> index 828924367..27eee5d14 100644
> --- a/dmidecode/dmidecode.nm
> +++ b/dmidecode/dmidecode.nm
> @@ -4,11 +4,11 @@
> ###############################################################################
>
> name = dmidecode
> -version = 3.0
> +version = 3.2
> release = 1
>
> groups = Applications/System
> -url = http://www.nongnu.org/dmidecode/
> +url = https://www.nongnu.org/dmidecode/
> license = GPLv2+
> summary = Tool to analyse BIOS DMI data.
>
> @@ -21,7 +21,8 @@ description
> manufacturer.
> end
>
> -source_dl = http://download.savannah.gnu.org/releases/dmidecode/
> +source_dl = https://download.savannah.gnu.org/releases/dmidecode/
> +sources = %{thisapp}.tar.xz
>
> build
> make_build_targets += CFLAGS="%{CFLAGS}" LDFLAGS="%{LDFLAGS}"
> --
> 2.16.4
prev parent reply other threads:[~2019-01-07 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-05 10:47 [PATCH] " Peter Müller
2019-01-07 13:03 ` Michael Tremer
2019-01-07 17:24 ` [PATCH v2] " Peter Müller
2019-01-07 17:45 ` Michael Tremer [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=2334131B-C124-4AF5-AE46-CD89E72E9B96@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/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