From: Michael Nosthoff via buildroot <buildroot@buildroot.org>
To: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Cc: Michael Nosthoff via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH] package/boost: update download url
Date: Tue, 29 Oct 2024 23:14:44 +0100 [thread overview]
Message-ID: <5a798-67215e80-1-8be02c0@119911138> (raw)
In-Reply-To: <20241029223109.414a2a54@windsurf>
Hi Thomas,
On Tuesday, October 29, 2024 22:31 CET, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> Hello Michael,
>
> On Tue, 29 Oct 2024 21:45:25 +0100
> Michael Nosthoff via buildroot <buildroot@buildroot.org> wrote:
>
> > boost moved it's package hosting from jfrog to their own url
> > sponsored by the C+++Alliance.
> >
> > Signed-off-by: Michael Nosthoff <buildroot@heine.tech>
> > ---
> > package/boost/boost.mk | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Thanks for the patch. Is this fixing a build issue (apparently not)? If
> not, do you have a link/reference about this change of official
> location?
Besides changing all download links there isn't any information about this change on boost.org or boost.io
What I found was this announcement on the Mailinglist: https://lists.boost.org/Archives/boost/2024/05/256914.php
So the important information there is: "JFrog links will continue to function until December 2024."
Maybe I should've included this in the commit message...
Regards,
Michael
>
> Thanks!
>
> Thomas
> --
> Thomas Petazzoni, CTO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-10-29 22:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 20:45 [Buildroot] [PATCH] package/boost: update download url Michael Nosthoff via buildroot
2024-10-29 21:31 ` Thomas Petazzoni via buildroot
2024-10-29 22:14 ` Michael Nosthoff via buildroot [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=5a798-67215e80-1-8be02c0@119911138 \
--to=buildroot@buildroot.org \
--cc=buildroot@heine.tech \
--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 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.