From: "Laszlo Boszormenyi (GCS)" <gcs@debian.hu>
To: Sage Weil <sage@inktank.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Ceph status for Wheezy
Date: Wed, 11 Jul 2012 15:35:52 +0000 [thread overview]
Message-ID: <1342020952.12180.28.camel@julia> (raw)
In-Reply-To: <Pine.LNX.4.64.1207082132170.13271@cobra.newdream.net>
On Sun, 2012-07-08 at 21:39 -0700, Sage Weil wrote:
> On Sun, 8 Jul 2012, Laszlo Boszormenyi (GCS) wrote:
> > It was released since then. But there are several files that I don't
> > know where to install. First are some headers under /usr/include/crush :
> > crush.h , hash.h , mapper.h and types.h .
> I don't think these need to be installed anywhere; they're not currently
> packaged. Why do you mention them?
They are installed to /usr/include on 'make install'. Didn't know the
reason, but will ignore them then.
> > What about ceph-disk-activate , ceph-disk-prepare exists , boto_tool and
> > ceph-coverage ? They are python scripts except the latter being a shell
> > script.
> ceph-disk-* are already in ceph. The other two shouldn't be packaged.
OK, added them to my packaging as well. Adds a python dependency to the
base package.
> Is there anything missing on this end?
Just checked, the python scripts are installed in your git tree.
Adjusted my packaging to match that. What do I miss? Manpages for
ceph-disk-activate , ceph-disk-prepare , rest-bench and maybe
librados-config .
Regards,
Laszlo/GCS
next prev parent reply other threads:[~2012-07-11 15:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-01 5:56 Ceph status for Wheezy Laszlo Boszormenyi (GCS)
2012-07-01 6:12 ` 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) [this message]
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=1342020952.12180.28.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.