Learn more about these different git repos.
Other Git URLs
We should drop support for legacy versions of NSUPDATE that don't support 'realm' option.
The option 'realm' was added in BIND 9.8.0a1, which is available in RHEL 6.x.
Unless there are any reservations about very old distributions, I think we can remove the non-realm support in 1.14 (master as of now).
Supported downstream releases have the realm option -> no clone
rhbz: => 0
Fields changed
milestone: NEEDS_TRIAGE => SSSD Deferred
keywords: => easyfix
Metadata Update from @preichl: - Issue assigned to preichl - Issue set to the milestone: SSSD Patches welcome
Metadata Update from @jhrozek: - Assignee reset - Custom field design_review reset (from 0) - Custom field mark reset (from 0) - Custom field patch reset (from 0) - Custom field review reset (from 0) - Custom field sensitive reset (from 0) - Custom field testsupdated reset (from 0) - Issue close_status updated to: None - Issue tagged with: easyfix
Metadata Update from @thalman: - Issue assigned to thalman
Metadata Update from @jhrozek: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false) - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @jhrozek: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false) - Issue set to the milestone: SSSD 2.1 (was: SSSD Patches welcome)
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/3858
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.