#1437 upstream spec should use systemd where available
Closed: Fixed None Opened 7 years ago by simo.

currently we unconditionally use init scripts and /sbin/service even though we have perfectly valid systemd unit files.

The .spec file should be fixed asap with conditionals, the Fedora spec is a good template for using systemd


Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.9.0
priority: major => minor

Fields changed

rhbz: => 0

Fields changed

milestone: SSSD 1.9.0 => SSSD 1.9.1

Fields changed

milestone: SSSD 1.9.1 => SSSD 1.9.2

This upstream-only task didn't make 1.9.2 unfortunately. We'll look at it during the 1.9.3 cycle. Sorry for the constant rescheduling.

milestone: SSSD 1.9.2 => SSSD 1.9.3

Fields changed

owner: somebody => pbrezina
status: new => assigned

Fields changed

patch: 0 => 1

Fields changed

design: =>
design_review: => 0
fedora_test_page: =>
owner: pbrezina => jcholast
status: assigned => new

master:
- 4eafef4
- 287e764
sssd-1-9:
- 0d1c4aa
- 144031b

resolution: => fixed
status: new => closed

Metadata Update from @simo:
- Issue assigned to jcholast
- Issue set to the milestone: SSSD 1.9.3

3 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/2479

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata