From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12611] New: ntp hash is not matching with upstream 4.2.8p13
Date: Thu, 05 Mar 2020 22:30:29 +0000 [thread overview]
Message-ID: <bug-12611-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=12611
Bug ID: 12611
Summary: ntp hash is not matching with upstream 4.2.8p13
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: mjhammel at graphics-muse.org
CC: buildroot at uclibc.org
Target Milestone: ---
I was building 2019.05.1 and found ntp 4.2.8p13 hash didn't match with
upstream. I checked 2020.02rc3 and it has the same hash as 2019.05.1. Then
checking upstream ntp I found this.
[ ] ntp-4.2.8p13.tar.gz 2020-03-03 19:54 6.7M
[ ] ntp-4.2.8p13.tar.gz.md5 2020-03-03 19:54 61
[ ] ntp-4.2.8p13.tar.gz.sha1 2019-03-07 06:18 62
[ ] ntp-4.2.8p13.tar.gz.sha256 2020-03-03 19:54 96
[ ] ntp-4.2.8p13.tar.gz.sha512 2019-03-07 06:18 150
[ ] ntp-4.2.8p14.tar.gz 2020-03-03 20:45 6.7M
[ ] ntp-4.2.8p14.tar.gz.md5 2020-03-03 20:45 61
[ ] ntp-4.2.8p14.tar.gz.sha256 2020-03-03 20:45 96
It looks like both 4.2.8p13 and 4.2.8p14 were updated the same day, except for
the former's sha1. I can also verify that the 4.2.8p13 tar.gz is larger than
my local archive.
Not sure what to do with this. Might be someone upstream just updated the
archives and messed it up. But I wasn't sure how to report that to the
upstream.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-03-05 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 22:30 bugzilla at busybox.net [this message]
2020-03-05 22:35 ` [Buildroot] [Bug 12611] ntp hash is not matching with upstream 4.2.8p13 bugzilla at busybox.net
2020-05-18 7:06 ` bugzilla at busybox.net
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-12611-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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