From: "Laszlo Boszormenyi (GCS)" <gcs@debian.hu>
To: Sage Weil <sage@inktank.com>
Cc: James Page <james.page@ubuntu.com>,
Ben Collins <bcollins@ubuntu.com>,
clint@fewbar.com, Ceph Development <ceph-devel@vger.kernel.org>,
openstack-devel@lists.alioth.debian.org
Subject: Re: sync Ceph packaging efforts for Debian/Ubuntu
Date: Thu, 28 Jun 2012 05:39:15 +0000 [thread overview]
Message-ID: <1340861955.16563.33.camel@julia> (raw)
In-Reply-To: <Pine.LNX.4.64.1206180926100.9362@cobra.newdream.net>
Hi all,
On Mon, 2012-06-18 at 09:44 -0700, Sage Weil wrote:
> On Mon, 18 Jun 2012, James Page wrote:
> > Laszlo - thanks for sending the original email - I'd like to get
> > everything as closely in-sync as possible between the three packaging
> > sources as well.
It seems I could sync with Ubuntu a bit, but you need to get libs3 and
sync that with me if appreciated.
> > On 16/06/12 22:50, Sage Weil wrote:
> > > - Has the leveldb patch been sent upstream? Once it is committed to
> > > the upstream git, we can update ceph to use it; that's nicer than carrying
> > > the patch. However, I thought you needed to link against the existing
> > > libleveldb1 package... which means we shouldn't do anything on our
> > > side,
> > > right?
Yes, the leveldb maintainer tries to port it to all architectures. It
would be better to join efforts on this topic.
Especially that Ceph is unbuildable on mips, powerpc, s390, s390x and
sparc architectures (where previously it was built) due to leveldb is
unbuildable on them. This means Ceph looses a lot of and big users. :(
> > > - That same patch also switched all the Architecture: lines back to
> > > linux-any. Was that intentional? I just changed them from that last
> > > week.
Well, mostly. My step that Ceph and later leveldb should be limited to
the archs where it's buildable is not accepted. Porting is going on for
leveldb, but I still don't see that it will support all archs for
Wheezy. Sorry for the extra work it caused.
> Okay, keep us posted!
To ones whom it may concerns, Ceph 0.47.2 is passed the new queue and
accepted for Wheezy. This means that adding it to OpenStack can start.
> I pushed a new 'debian' branch with those changes; please take a look and
> let me know if it loks okay.
Will do. Now I've to run.
Regards,
Laszlo/GCS
prev parent reply other threads:[~2012-06-28 5:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-16 0:10 sync Ceph packaging efforts for Debian/Ubuntu Laszlo Boszormenyi (GCS)
2012-06-16 16:00 ` Sage Weil
2012-06-16 21:50 ` Sage Weil
2012-06-18 10:27 ` James Page
2012-06-18 16:44 ` Sage Weil
2012-06-28 5:39 ` Laszlo Boszormenyi (GCS) [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=1340861955.16563.33.camel@julia \
--to=gcs@debian.hu \
--cc=bcollins@ubuntu.com \
--cc=ceph-devel@vger.kernel.org \
--cc=clint@fewbar.com \
--cc=james.page@ubuntu.com \
--cc=openstack-devel@lists.alioth.debian.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.