Skip to content

ceph.spec.in: include SUSE in _with_systemd#4666

Closed
smithfarm wants to merge 1 commit intoceph:nextfrom
SUSE:wip-11610-next
Closed

ceph.spec.in: include SUSE in _with_systemd#4666
smithfarm wants to merge 1 commit intoceph:nextfrom
SUSE:wip-11610-next

Conversation

@smithfarm
Copy link
Copy Markdown
Contributor

http://tracker.ceph.com/issues/11610

The master specfile newly defines a _with_systemd variable that should be true
for the set of distros that are using systemd. Since this set of distros
includes SUSE/openSUSE (at least for the more recent versions where ceph is
supported), this commit sets _with_systemdto true on SUSE/openSUSE.

@ghost ghost added the build/ops label May 13, 2015
@ghost ghost assigned ktdreyer May 13, 2015
@ghost ghost added this to the next milestone May 13, 2015
@ghost
Copy link
Copy Markdown

ghost commented May 13, 2015

Could you add

http://tracker.ceph.com/issues/11610 Fixes: #11610

before the Signed-off-by: ?

@ghost
Copy link
Copy Markdown

ghost commented May 13, 2015

👍 but Ken is the ultimate authority on these matters.

The master specfile newly defines a _with_systemd variable that should be true
for the set of distros that are using systemd. Since this set of distros
includes SUSE/openSUSE (at least for the more recent versions where ceph is
supported), this commit sets _with_systemdto true on SUSE/openSUSE.

http://tracker.ceph.com/issues/11610 Fixes: ceph#11610

Signed-off-by: Nathan Cutler <ncutler@suse.cz>
@smithfarm
Copy link
Copy Markdown
Contributor Author

@dachary: done

@ktdreyer
Copy link
Copy Markdown
Contributor

Thanks! I was hoping someone would contribute this. Merging...

ktdreyer added a commit that referenced this pull request May 13, 2015
ceph.spec.in: include SUSE in _with_systemd

Reviewed-by: Loic Dachary <ldachary@redhat.com>
Reviewed-by: Ken Dreyer <kdreyer@redhat.com>
@ktdreyer
Copy link
Copy Markdown
Contributor

No idea why github didn't see that this was merged :-( Is it because ncutler@suse.cz isn't associated with your GitHub account?

At any rate, it's in master now, as f9d66a8 . Thanks!

@ktdreyer ktdreyer closed this May 13, 2015
@ktdreyer
Copy link
Copy Markdown
Contributor

Oh shoot, it's because you'd targeted next, not master, and I missed that fact. Sorry!

So I think we have to cherry-pick this down to next, now.

@smithfarm
Copy link
Copy Markdown
Contributor Author

@ktdreyer: I targeted next after re-reading the code submission guidelines, which - as I read them - say basically that master is for new features, and use next for everything else.

@ktdreyer
Copy link
Copy Markdown
Contributor

You were correct to target next. This was my fault. I'll cherry-pick this to next and do a second PR.

@ktdreyer
Copy link
Copy Markdown
Contributor

cherry-pick to next is at #4670

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants