From: Peter Korsgaard <peter@korsgaard.com>
To: yann.morin@orange.com
Cc: Thomas Perale <thomas.perale@mind.be>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
<buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH] package/docker-credential-gcr: needs NPTL
Date: Fri, 21 Aug 2026 17:25:38 +0200 [thread overview]
Message-ID: <87bjav7ax9.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <an6ZiFqeluAkBNbH@yd-6wlzhs3> (yann morin's message of "Fri, 14 Aug 2026 06:28:56 +0200")
>>>>> "yann" == yann morin <yann.morin@orange.com> writes:
Hi Yann,
> This should also be backported to 2026.02, to fix the following build
> failure:
> https://autobuild.buildroot.org/results/aa5754a547f6dea3165e598f8e22b6cbe3b38f5b/
> Similarly, the following commits, related to the other docker credential
> helpers, should also be backported :
> 882c35f7388a package/docker-credential-acr-env: needs NPTL
> 7a7b0522b34c package/amazon-ecr-credential-helper: needs NPTL
> Either that, or the 2026.02 branch should no longer be built in the
> autobuilder is it is no longer maintained...
Indeed, 2026.02.x is now EOL. I fixed the autobuilder config earlier
this week:
commit e1d90c57b65a2b37db8f4aaa0ce3068f1db957b7 (HEAD -> master, origin/master, origin/HEAD)
Author: Peter Korsgaard <peter@korsgaard.com>
Date: Tue Aug 18 23:37:45 2026 +0200
web/branches: test next instead of 2026.02.x
Now that 2026.02.x is EOL.
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-08-21 15:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 5:42 [Buildroot] [PATCH] package/docker-credential-gcr: needs NPTL yann.morin
2026-07-20 19:43 ` Julien Olivain via buildroot
2026-07-31 12:21 ` Thomas Perale via buildroot
2026-08-14 4:28 ` yann.morin
2026-08-21 15:25 ` Peter Korsgaard [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=87bjav7ax9.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=thomas.perale@mind.be \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin@orange.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