From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] libpciaccess: Version bump. 0.16 -> 0.17.
Date: Fri, 11 Nov 2022 15:31:15 +0100 [thread overview]
Message-ID: <20221111143115.893378-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20221026190124.789574-1-christian.melki@t2data.com>
Thanks, applied as c9a8f2184cf8c60d7300eadd10f4d24028cfd50b.
Michael
[sent from post-receive hook]
On Fri, 11 Nov 2022 15:31:15 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> Mostly build related. Some bugfixes.
> A new meson build mechanism was added.
>
> * Project moved to xz from bz2 as dist tarballs.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20221026190124.789574-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/libpciaccess.make b/rules/libpciaccess.make
> index 447236d7fa41..fb0b46a8eb4a 100644
> --- a/rules/libpciaccess.make
> +++ b/rules/libpciaccess.make
> @@ -14,10 +14,10 @@ PACKAGES-$(PTXCONF_LIBPCIACCESS) += libpciaccess
> #
> # Paths and names
> #
> -LIBPCIACCESS_VERSION := 0.16
> -LIBPCIACCESS_MD5 := b34e2cbdd6aa8f9cc3fa613fd401a6d6
> +LIBPCIACCESS_VERSION := 0.17
> +LIBPCIACCESS_MD5 := 1466cf950c914ad2db1dbb76c9a724db
> LIBPCIACCESS := libpciaccess-$(LIBPCIACCESS_VERSION)
> -LIBPCIACCESS_SUFFIX := tar.bz2
> +LIBPCIACCESS_SUFFIX := tar.xz
> LIBPCIACCESS_URL := $(call ptx/mirror, XORG, individual/lib/$(LIBPCIACCESS).$(LIBPCIACCESS_SUFFIX))
> LIBPCIACCESS_SOURCE := $(SRCDIR)/$(LIBPCIACCESS).$(LIBPCIACCESS_SUFFIX)
> LIBPCIACCESS_DIR := $(BUILDDIR)/$(LIBPCIACCESS)
prev parent reply other threads:[~2022-11-11 14:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 19:01 [ptxdist] [PATCH] " Christian Melki
2022-11-11 14:31 ` Michael Olbrich [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=20221111143115.893378-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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