From: "Laszlo Boszormenyi (GCS)" <gcs@debian.hu>
To: Sage Weil <sage@inktank.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Ceph status for Wheezy
Date: Sun, 01 Jul 2012 05:56:50 +0000 [thread overview]
Message-ID: <1341122210.10000.46.camel@julia> (raw)
Hi Sage,
As previously noted, using leveldb caused some trouble with Ceph could
be included in Wheezy or not.
I've proposed that the supported architectures should be limited in Ceph
and leveldb to the ones the latter supports. I got a release critical
bugreport[1] that it should be reversed. Alessio Treglia, the leveldb
maintainer in Debian wrote the following:
"I'm going to test leveldb on powerpc and then I'll report my results
to upstream.
Hence I cannot promise it will be ready in time for Wheezy, of course
I'll upload a patch as soon as a fix becomes available.".
Upstream was asked[2], noted that it fails on big-endian architectures,
but no answer until now.
Then, as it was previously announced, the freeze of Wheezy started some
hours ago[3].
Soon, after that Julien Cristau, one of our Release Assistant noted
about Ceph doesn't build on all architectures due to leveldb:
"Unless this gets fixed we'll have to remove ceph from wheezy. Which
means qemu and qemu-kvm need to drop their build-deps on ceph packages.
They can always be re-added if/when leveldb/ceph are fixed.".
It seems everything is up to leveldb upstream/maintainer now. It is
fixed in time on big-endian machines or the package will be limited to
little-endian machines as I wanted to do with Ceph.
But please look into the reason why Ceph fails to build on ia64[4].
Also, how 0.48 goes? Will it contain big differences to 0.47.2? As you
can read, even 0.47.2 is in question for Wheezy. But would you propose
0.48 for inclusion when it's released?
Fingers crossed. Regards,
Laszlo/GCS
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677626
[2] http://code.google.com/p/leveldb/issues/detail?id=84
[3] https://lists.debian.org/debian-devel-announce/2012/06/msg00009.html
[4] https://buildd.debian.org/status/fetch.php?pkg=ceph&arch=ia64&ver=0.47.2-1&stamp=1340802492
next reply other threads:[~2012-07-01 5:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-01 5:56 Laszlo Boszormenyi (GCS) [this message]
2012-07-01 6:12 ` Ceph status for Wheezy Sage Weil
2012-07-01 15:15 ` Gregory Farnum
2012-07-08 22:22 ` Laszlo Boszormenyi (GCS)
2012-07-09 4:39 ` Sage Weil
2012-07-11 15:35 ` Laszlo Boszormenyi (GCS)
2012-07-11 16:18 ` Sage Weil
2012-07-02 21:13 ` Yehuda Sadeh
2012-07-02 23:12 ` Yehuda Sadeh
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=1341122210.10000.46.camel@julia \
--to=gcs@debian.hu \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@inktank.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.