Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: buildroot@buildroot.org,
	Maxime Chevallier <maxime.chevallier@bootlin.com>
Subject: Re: [Buildroot] [PATCH v2] package/libtracefs: fix build failure due to missing NPTL
Date: Fri, 15 Aug 2025 20:32:47 +0200	[thread overview]
Message-ID: <20250815203247.14ecd5f5@windsurf> (raw)
In-Reply-To: <154C2C5A-1097-4AD1-A36A-2921CF6264FA@benettiengineering.com>

Hello,

On Fri, 15 Aug 2025 18:41:02 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:

> I see. So what about the Fixes: tag pointing the the commit that introduced the issue the same way Linux does?

We already sometimes do that, see for example commit
ab470fbc8eb1053548c3d33e807db84fd5af1445, which has:

    Fixes: 51b27bad915c95499877c8bf9a16a221c904bf82

> The only remaining problem is then how do I point to Autobuilder failure URL?

Two Fixes: tags won't be a problem.

Or the commit introducing the problem can simply be mentioned in the
commit log, like d28ae8b00b7aa5018ec24809ecc393e7420bc292, which goes
like this:

    package/ustream-ssl: fix build w/ mbedtls v3.6
    
    Since the mbedtls bump to v3.6 [1] the ustream-ssl package is failling
    on the autobuilder with the following error:

    [...]

    [1] 3481a9643f package/mbedtls: bump to version 3.6.3.1

    Fixes: https://autobuild.buildroot.org/results/c20/c20dac7cbe5def2c6036d2e1d06de0bfea68b57c

What is important is that the information is available, to facilitate
the effort of the LTS maintainers.

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-08-15 18:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-14 21:07 [Buildroot] [PATCH] package/libtracefs: fix build failure due to missing NPTL Giulio Benetti
2025-08-15 10:24 ` Thomas Petazzoni via buildroot
2025-08-15 11:09   ` [Buildroot] [PATCH v2] " Giulio Benetti
2025-08-15 15:19     ` Thomas Petazzoni via buildroot
2025-08-15 16:41       ` Giulio Benetti
2025-08-15 18:32         ` Thomas Petazzoni via buildroot [this message]
2025-08-15 20:35           ` [Buildroot] [PATCH v3] " Giulio Benetti
2025-08-16 20:05             ` Thomas Petazzoni via buildroot
2025-08-21 19:21 ` [Buildroot] [PATCH] " Thomas Perale 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=20250815203247.14ecd5f5@windsurf \
    --to=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=maxime.chevallier@bootlin.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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