sssd api conf files in wrong place

Bug #859611 reported by Myllynen on 2011-09-26
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sssd (Ubuntu)
Undecided
Timo Aaltonen

Bug Description

Currently sssd api conf files are under /usr/share/doc/sssd and this prevents using the API from Python scripts since SSSDConfig.py has hardcoded references to /etc/sssd/sssd.api.conf and /etc/sssd/sssd.api.d.

Please move the sssd api conf files from /usr/share/doc/sssd to /etc/sssd.

Timo Aaltonen (tjaalton) wrote :

Right, as discussed on irc, we'll move them to /usr/share/sssd, and see that the place is referenced on SSSDConfig.py.

Changed in sssd (Ubuntu):
assignee: nobody → Timo Aaltonen (tjaalton)
status: New → In Progress
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package sssd - 1.5.13-0ubuntu1

---------------
sssd (1.5.13-0ubuntu1) oneiric; urgency=low

  * FFE: New upstream release. (LP: #860297)
    - control: Add libunistring-dev to build-depends.
    - sssd.install: Include libipa_hbac.so*.
  * Rebuild against current libldb1, and use the multiarch path
    for libldb modules. (LP: #746981)
  * sssd.default:
    - Move the option to run as daemon here.
    - Add option that makes the daemon to use logfiles. (LP: #859602)
  * sssd.upstart:
    - Don't start before net-device-up. (LP: #812943)
    - Source /etc/default/sssd. (LP: #812943)
  * rules: Install the Python API files to /usr/share/sssd, as discussed
    with upstream. (LP: #859611)
  * fix-python-api-path.dpatch: Use the new location for the API files.
    (LP: #859611)
  * libpam-sss.pam-auth-update:
    - Add 'forward_pass' to auth stack to fix ecryptfs mounts. (LP: #826643)
    - Add pam_localuser.so to account stack to allow local users to log in.
      (LP: #860488)
  * control: sssd now Recommends libpam-sss and libnss-sss, since sssd is
    mostly useless without them. (LP: #767337)
 -- Timo Aaltonen <email address hidden> Tue, 27 Sep 2011 06:03:41 +0300

Changed in sssd (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers