From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15643] ERROR: No hash found for linux-6.3.8.tar.xz
Date: Sun, 18 Jun 2023 19:29:25 +0000 [thread overview]
Message-ID: <bug-15643-163-Q9bPEImzp8@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15643-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15643
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
CC| |yann.morin.1998@free.fr
Status|NEW |RESOLVED
--- Comment #1 from Yann E. MORIN <yann.morin.1998@free.fr> ---
stsp, All,
Thanks for the report. We believe the issue has just been fixed with:
https://gitlab.com/buildroot.org/buildroot/-/commit/d4a96ee46e3656b95151ab8e27d3fd3407e4633a
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-06-18 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 19:18 [Buildroot] [Bug 15643] New: ERROR: No hash found for linux-6.3.8.tar.xz bugzilla
2023-06-18 19:29 ` 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-15643-163-Q9bPEImzp8@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 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.