From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org,
openembedded-core@lists.openembedded.org
Subject: BlueZ old releases have new checksums
Date: Wed, 04 Jan 2012 13:14:00 -0500 [thread overview]
Message-ID: <20120104181400.GD587@denix.org> (raw)
All,
The main archive of BlueZ/obexd/hcidump releases on kernel.org[1] finally
re-appeared after missing for long time since kernel.org compromise.
Unfortunately, all previous tarballs have new checksums, breaking builds for
anyone w/o previous copy cached. Old copies were also extensively mirrored,
so you never know which one you fetch next time...
I pinged the upstream, but I doubt it will be changed or fixed in any way.
So the proper solution for us would be to upgrade recipes to the latest
released versions - bluez-4.97, obexd-0.43 and bluez-hcidump-2.2.
Are there any other suggestions?
[1] http://www.kernel.org/pub/linux/bluetooth/
--
Denys
next reply other threads:[~2012-01-04 19:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 18:14 Denys Dmytriyenko [this message]
2012-01-04 20:14 ` BlueZ old releases have new checksums Chris Larson
2012-01-04 20:53 ` Khem Raj
2012-01-04 22:02 ` [oe] " Denys Dmytriyenko
2012-01-05 0:16 ` Chris Larson
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=20120104181400.GD587@denix.org \
--to=denis@denix.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.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