Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update name of ceph development package in spec file. #406

Closed
wants to merge 1 commit into from

Conversation

bmcann
Copy link
Contributor

@bmcann bmcann commented Aug 19, 2016

Since the 'hammer' release of ceph, the package "ceph-devel" no longer exists, having been replaced by the meta package "ceph-devel-compat". This change updates the spec file accordingly.

'ceph-devel-compat'.

Since the 'hammer' release of ceph, this has been the name of the
development package.
@simonmichal
Copy link
Contributor

From what I've seen the ceph-devel-compat has been there at least since Firefly release ;-) It does obsolete the ceph-devel package in the spec file so IMHO everything is OK.

@bmcann
Copy link
Contributor Author

bmcann commented Aug 23, 2016

Hi Simon,

I can't see "ceph-devel-compat" in our local mirrors here at RAL for firefly or giant or "ceph-devel" for hammer, infernalis or jewel. We are mirroring from download.ceph.com. I think this change will be OK, XrootD and Ceph have only been usable together since the more recent releases of both.

Best wishes,
Bruno

@simonmichal
Copy link
Contributor

Hi Bruno,

Hmm that's interesting, I actually checked what's in epel7 (http://koji.fedoraproject.org/koji/buildinfo?buildID=738434) and there's ceph-0.80.7-0.8.el7 (so firefly) and it contains ceph-devel-compat ;-)

In download.ceph.com the ceph-devel-compat indeed appears only in hammer.

Changing the build requires to ceph-devel-compat would mean that we wont be able to build xrootd-ceph with giant any more, right? (giant does have radosstriper and ceph-devel)

On the other hand, all the releases that have devel-compat, have a respective obsolete entry in the spec file for the devel package, which means that the dependencies will be handled correctly.

Just considering the pros and cons ;-)

Cheers,
Michal

@bmcann
Copy link
Contributor Author

bmcann commented Jan 16, 2017

Hi Michal,

I meant to get in touch about this. I notice you've put a more elegant solution into the spec file than the one I proposed here. I tested it in December when I build XRootD 4.5 with ceph it it works just fine, so closing this PR is a good thing. Should I delete the branch?

Best wishes,
Bruno

@simonmichal
Copy link
Contributor

Hi Bruno,

Yes, please go ahead and delete the branch. Sorry I forgot to notify you ;-)

Thanks,
Michal

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants