On 21.3.2019 16.23, Timo Aaltonen wrote:
> On 21.3.2019 16.02, Jan Luca Naumann wrote:
>> Another way could be to check in the postinst files if there is already
>> an existing sssd.conf file and, if yes, do not enable the systemd units.
>>
>> This should prevent breaking existing installations
On 21.3.2019 16.02, Jan Luca Naumann wrote:
> Another way could be to check in the postinst files if there is already
> an existing sssd.conf file and, if yes, do not enable the systemd units.
>
> This should prevent breaking existing installations but would allow to
> use the services after
Another way could be to check in the postinst files if there is already
an existing sssd.conf file and, if yes, do not enable the systemd units.
This should prevent breaking existing installations but would allow to
use the services after adjusting sssd.conf and new users would use the
sockets
On 6.3.2019 19.22, Jan Luca Naumann wrote:
> Package: sssd-tools
> Version: 1.16.3-3
> Severity: normal
>
> Since Debian deactivates the installation of the sssd-ifp.service (c.f.
> changelog for
> Debian release 1.16.0-4) the subcommands using infopipe (e.g. list-domain and
> domain-status)
>
Package: sssd-tools
Version: 1.16.3-3
Severity: normal
Since Debian deactivates the installation of the sssd-ifp.service (c.f.
changelog for
Debian release 1.16.0-4) the subcommands using infopipe (e.g. list-domain and
domain-status)
of the tool sssctl are broken:
$ sssctl domain-list
Unable
5 matches
Mail list logo
