From: Marcel Holtmann <marcel@holtmann.org>
To: Denys Dmytriyenko <denis@denix.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: BlueZ old releases have different checksums
Date: Wed, 04 Jan 2012 11:49:03 -0800 [thread overview]
Message-ID: <1325706543.6454.64.camel@aeonflux> (raw)
In-Reply-To: <20120104175522.GC587@denix.org>
Hi Denys,
> 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.
I have no idea what these kernel.org people did with it, but I uploaded
the original tar.gz release. However just taking the 4.0 release, you
are correct, there is a difference.
@@ -1,4 +1,4 @@
-0000000 8b1f 0008 b6f4 4ef3 0302 3cec 7ff1 b6da
+0000000 8b1f 0008 dbf0 4899 0302 3cec 7ff1 b6da
0000010 fdb3 fe35 342b 96c6 0590 da12 dda4 6592
0000020 135f 0870 04af 00f8 db59 fdad c6ba f018
0000030 6c6a b6be 9b49 fdad dfdf 49dd 65b2 4930
I have no idea why they unpacked and re-packed the tar.gz files, but I
can not really do much about it.
Regards
Marcel
prev parent reply other threads:[~2012-01-04 19:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 17:55 BlueZ old releases have different checksums Denys Dmytriyenko
2012-01-04 19:49 ` Marcel Holtmann [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=1325706543.6454.64.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=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