From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15266] curl-7.87.0 is missing from http://sources.buildroot.net/libcurl
Date: Sat, 21 Jan 2023 13:59:56 +0000 [thread overview]
Message-ID: <bug-15266-163-PHu1rckAWP@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15266-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15266
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
CC| |yann.morin.1998@free.fr
--- Comment #1 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Andrew, All,
The sources.buildroot.org is a best-effort mirror, which is automatically
populated with a cronjob, and there is no guarantee it is cpmlete. If an
upstream becomes unreachable before we can cache it, then there is nothing
we can do about it.
In this specific instance, the upstream site is working again, with a
certificate that is up-to-date, so we should soon see the archive on s.b.o
once the cronjob kick in (at least, I could download it manually here).
Regards,
Yann E. MORIN.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-01-21 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 23:13 [Buildroot] [Bug 15266] New: curl-7.87.0 is missing from http://sources.buildroot.net/libcurl bugzilla
2023-01-21 13:59 ` bugzilla [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=bug-15266-163-PHu1rckAWP@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/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