All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@uclibc.org
Subject: Re: [Buildroot] [PATCH] package/fmt: bump to version 12.2.0
Date: Sun, 05 Jul 2026 18:48:01 +0200	[thread overview]
Message-ID: <b5dd30852bde29c27b79e9d92f3a1c29@free.fr> (raw)
In-Reply-To: <pan$1e5ac$b7fc699a$3e8fac53$bef4b4c9@ID-313208.user.individual.net>

Hi Bernd,

On 29/06/2026 15:02, Bernd Kuhls wrote:
> Am Mon, 29 Jun 2026 09:14:18 +0200 schrieb Michael Nosthoff via 
> buildroot:
> 
>> changelog:
>> https://github.com/fmtlib/fmt/releases/tag/12.2.0
> 
> Hi Michael,
> 
> this bump will break the build of gerbera unless these patches are
> included into buildroot:
> 
> https://github.com/gerbera/gerbera/commit/
> 7caa9ae9ebf5c4cded5a292701528ff1d5c4946e
> 
> https://github.com/gerbera/gerbera/commit/
> 9507706136fde8c324d95d5c84c78bae1703bafc

For some reason, your message was not displayed in patchwork:
https://patchwork.ozlabs.org/project/buildroot/patch/20260629071429.4131207-2-buildroot@heine.tech/

So I missed it and applied the fmt bump. I guess we'll need the patches 
for
fixing the gerbera package.

> Regards, Bernd

Best regards,

Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-07-05 16:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260629071429.4131207-2-buildroot__14354.4681415491$1782717305$gmane$org@heine.tech>
2026-06-29 13:02 ` [Buildroot] [PATCH] package/fmt: bump to version 12.2.0 Bernd Kuhls
2026-07-05 16:48   ` Julien Olivain via buildroot [this message]
2026-07-05 17:33     ` Bernd Kuhls
2026-06-29  7:14 Michael Nosthoff via buildroot
2026-07-05 16:46 ` Julien Olivain via buildroot

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=b5dd30852bde29c27b79e9d92f3a1c29@free.fr \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=buildroot@uclibc.org \
    --cc=ju.o@free.fr \
    /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.