All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Nelson <mnelson@redhat.com>
To: Sage Weil <sage@newdream.net>,
	Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Brad Hubbard <bhubbard@redhat.com>,
	Mustafa Muhammad <mustafaa.alhamdaani@gmail.com>,
	ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Fedora 21 packages
Date: Mon, 30 Mar 2015 10:54:56 -0500	[thread overview]
Message-ID: <551971D0.4070300@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1503300832280.23387@cobra.newdream.net>

On 03/30/2015 10:34 AM, Sage Weil wrote:
> On Mon, 30 Mar 2015, Jan Kratochvil wrote:
>> On Mon, 30 Mar 2015 01:45:55 +0200, Sage Weil wrote:
>>> These packages are from downstream Fedora.  What's missing are more up
>>> to date packages built and published at ceph.com.  The distro only ships
>>> one version of Ceph (the most recent LTS), while ceph.com gets everything
>>> and ceph-deploy let's you choose which stable series or development branch
>>> to install.  We're also not doing any testing on f21.
>>
>> That's not the Fedora way.  LTS-like packages are not for Fedora, those are
>> for CentOS/RHEL (but where Ceph LTS is already present).  Latest development
>> packages are for Fedora Rawhide.  And for other cases there is also
>> https://fedorahosted.org/copr .
>
> In that case, I think the latest stable release (e.g., giant) should go in
> Fedora.  Maybe we could put the latest development release in Rawhide, but
> I'm nto sure.  They're really not intended for end users.
>
> sage
>

FWIW, I've got some of our performance gear on fedora 20 right now and 
happily use the gitbuilder packages (though there are some annoying 
dependency issues that require different excludes during the yum 
installation).  It's incredibly convenient to be able to simply change 
the repo and grab the newest build from different versions the same way 
we do in Ubuntu.  Hopefully regardless of whatever other decisions are 
made, we can retain this kind of workflow with the gitbuilder releases.

Mark

>>
>> I have filed for Fedora-shipped ceph-deploy:
>> 	https://bugzilla.redhat.com/show_bug.cgi?id=1207275
>>
>>
>> Jan
>>
>>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

      reply	other threads:[~2015-03-30 15:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-28 13:22 Fedora 21 packages Mustafa Muhammad
2015-03-28 17:36 ` Sage Weil
2015-03-29 21:55   ` Brad Hubbard
2015-03-29 23:45     ` Sage Weil
2015-03-30  0:30       ` Brad Hubbard
2015-03-30 15:17       ` Jan Kratochvil
2015-03-30 15:34         ` Sage Weil
2015-03-30 15:54           ` Mark Nelson [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=551971D0.4070300@redhat.com \
    --to=mnelson@redhat.com \
    --cc=bhubbard@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=mustafaa.alhamdaani@gmail.com \
    --cc=sage@newdream.net \
    /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.