From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15976] New: .hash file requires newline to process correctly
Date: Fri, 08 Mar 2024 16:01:06 +0000 [thread overview]
Message-ID: <bug-15976-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15976
Bug ID: 15976
Summary: .hash file requires newline to process correctly
Product: buildroot
Version: 2023.02.9
Hardware: All
OS: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: masonwardle@gmail.com
CC: buildroot@uclibc.org
Target Milestone: ---
I have a <package-name>.hash file with
# Calculated by hand
sha256 <64 hex character hash> <downloaded package name>
I failed to put a newline at the end of the file. This caused
support/download/check-hash to fail with a "No hash found" error. A quick look
at the code suggests this error occurs in my case because the "read" command
exits abnormally if it reaches the end of the file before encountering a
newline.
I initially thought this could be addressed in the documentation but perhaps
there is a simple fix.
I'm running buildroot 2023.02.9 on Ubuntu 22.04. check-hash hasn't changed
since that release.
Thanks!
--
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
next reply other threads:[~2024-03-08 16:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 16:01 bugzilla [this message]
2024-03-09 18:12 ` [Buildroot] [Bug 15976] .hash file requires newline to process correctly bugzilla
2024-03-09 18:58 ` bugzilla
2024-06-15 15:24 ` bugzilla
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-15976-163@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