From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Michael Riesch <michael.riesch@wolfvision.net>
Subject: Re: [ptxdist] [APPLIED] libcamera: version bump 0.0.1 -> 0.0.4
Date: Fri, 10 Feb 2023 15:17:16 +0100 [thread overview]
Message-ID: <20230210141716.3533780-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20230206084335.1968875-1-michael.riesch@wolfvision.net>
Thanks, applied as 5a52678fc8875b09670e2564370c63d05b8af37b.
Michael
[sent from post-receive hook]
On Fri, 10 Feb 2023 15:17:16 +0100, Michael Riesch <michael.riesch@wolfvision.net> wrote:
> Bump libcamera version to the recently released v0.0.4.
>
> Note: pipewire v0.3.62 or newer is now required to build the pipewire
> plugin for libcamera. This is caused by an API breakage introduced
> in libcamera v0.0.3.
>
> Signed-off-by: Michael Riesch <michael.riesch@wolfvision.net>
> Message-Id: <20230206084335.1968875-1-michael.riesch@wolfvision.net>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/libcamera.make b/rules/libcamera.make
> index 12969cafa57d..d51533a73e2e 100644
> --- a/rules/libcamera.make
> +++ b/rules/libcamera.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_LIBCAMERA) += libcamera
> #
> # Paths and names
> #
> -LIBCAMERA_VERSION := 0.0.1
> -LIBCAMERA_MD5 := d428d7e7455e9cca763d313323043e7b
> +LIBCAMERA_VERSION := 0.0.4
> +LIBCAMERA_MD5 := c671af5f54528c2dcc73f1c1fa733e50
> LIBCAMERA := libcamera-$(LIBCAMERA_VERSION)
> LIBCAMERA_SUFFIX := tar.gz
> LIBCAMERA_URL := https://git.libcamera.org/libcamera/libcamera.git;tag=v$(LIBCAMERA_VERSION)
prev parent reply other threads:[~2023-02-10 14:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 8:43 [ptxdist] [PATCH] " Michael Riesch
2023-02-10 14:17 ` 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=20230210141716.3533780-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=michael.riesch@wolfvision.net \
--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