Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13581] jpegsrc.v9d.tar.gz has changed hash
Date: Fri, 05 Mar 2021 22:03:53 +0000	[thread overview]
Message-ID: <bug-13581-163-jKTHucd12X@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-13581-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=13581

Peter Korsgaard <jacmet@uclibc.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #1 from Peter Korsgaard <jacmet@uclibc.org> ---
Sorry, we cannot do that. All Buildroot releases since January 2020 uses this
version and expects the old checksum. If we were to change the checksum, then
we would also have to change the copy on sources.buildroot.org, and that would
break all Buildoot releases expecting the old checksum.

Buildroot should automatically fallback to the copy on sources.buildroot.org
when it notices the wrong checksum from upstream, doesn't that work for you?

Please instead contact upstream and ask them to revert the checksum change
and/or release a v9e version that we could move to instead.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2021-03-05 22:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05 11:15 [Buildroot] [Bug 13581] New: jpegsrc.v9d.tar.gz has changed hash bugzilla at busybox.net
2021-03-05 22:03 ` bugzilla at busybox.net [this message]
2021-03-06 10:14 ` [Buildroot] [Bug 13581] " 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-13581-163-jKTHucd12X@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