From: Denys Dmytriyenko <denis@denix.org>
To: linux-bluetooth@vger.kernel.org
Subject: BlueZ old releases have different checksums
Date: Wed, 04 Jan 2012 12:55:23 -0500 [thread overview]
Message-ID: <20120104175522.GC587@denix.org> (raw)
Hi,
Sorry if it was covered previously, but my various searches didn't bring any
relevant results...
On December 22/23 the entire archive of previous BlueZ/obexd/hcidump releases
re-appeared on kernel.org after missing for long time due to the server
compromise. Well, it looks like all the tarballs were re-created and
re-packaged, thus they all have new checksums. Unfortunately, since filenames
were not changed (i.e. FSF had to re-publish all releases of binutils and they
added an 'a' suffix to filenames), this breaks Linux distributions that fetch
and build from sources (like OpenEmbedded and Yocto based distros), since
checksums don't match. The situation is even worse since many mirrors have old
copies of the tarballs...
The question I have is whether this is known and was it done on purpose? What
can be done to fix this situation for users of the old releases, besides
upgrading to the very latest releases of BlueZ/obexd/hcidump? Thank you for
your attention.
--
Denys
next reply other threads:[~2012-01-04 17:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 17:55 Denys Dmytriyenko [this message]
2012-01-04 19:49 ` BlueZ old releases have different checksums Marcel Holtmann
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=20120104175522.GC587@denix.org \
--to=denis@denix.org \
--cc=linux-bluetooth@vger.kernel.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