All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Dieter <jdieter@lesbg.com>
To: ceph-devel@vger.kernel.org
Subject: Re: Compilation issues on Fedora 13 and Fedora 15
Date: Sun, 25 Mar 2012 18:23:25 +0300	[thread overview]
Message-ID: <1332689005.2102.3.camel@jdlaptop.lesbg.loc> (raw)
In-Reply-To: <1332665829.7312.8.camel@indica.cc.iitb.ac.in>

[-- Attachment #1: Type: text/plain, Size: 641 bytes --]

On Sun, 2012-03-25 at 14:27 +0530, Ajit K Jena wrote:
> Hello All,
> 
> I have lost touch with the growth of ceph after version 0.30.
> I am trying to compile version 0.43 and 0.44 on FC13 and FC15.

FWIW, we've pushed 0.43 in Fedora 17. We don't have anything later than
0.41 in versions lower than 17 because of Fedora's updates policies.  

However, you could take the source rpm from F17 and rebuild it for older
versions of Fedora.

It's available at
http://kojipkgs.fedoraproject.org/packages/ceph/0.43/1.fc17/src/ceph-0.43-1.fc17.src.rpm

I'll probably push 0.44 to F17 once I manage to get the RPM built.

Jonathan

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2012-03-25 15:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-25  8:57 Compilation issues on Fedora 13 and Fedora 15 Ajit K Jena
2012-03-25 10:14 ` Wido den Hollander
2012-03-25 10:47   ` Ajit K Jena
2012-03-25 15:23 ` Jonathan Dieter [this message]
2012-03-25 15:40   ` Sage Weil
2012-03-25 17:45     ` Jonathan Dieter
2012-04-13 17:24   ` Ajit K Jena
2012-04-14  0:30     ` Udo Seidel
2012-04-14 11:16       ` Jonathan Dieter
2012-04-19 11:00         ` Ajit K Jena
  -- strict thread matches above, loose matches on Subject: below --
2012-03-25 14:05 Nick Couchman

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=1332689005.2102.3.camel@jdlaptop.lesbg.loc \
    --to=jdieter@lesbg.com \
    --cc=ceph-devel@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 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.