sssd.spec for SLES

[Sergei V. Kovylov]

Here you may find a patch for sssd.spec file which provide correct
build sssd for SLES (testes on SLES10SP1).
In brief:
There are 3 essences:
redhat
fedora
sles
which are detected by  /etc/<vendor release file> existence (ex.
/etc/SuSE-release) in spec and all necessary actions are doing along
the OS detection.
Additionally for SLES there is "--without-selinux" flag while
configuring, as SLES doesn't support SELinux.

[Sumit Bose]

On Wed, Dec 09, 2009 at 02:21:05PM +0300, Sergei V. Kovylov wrote:
> Here you may find a patch for sssd.spec file which provide correct
> build sssd for SLES (testes on SLES10SP1).
> In brief:
> There are 3 essences:
> redhat
> fedora
> sles
> which are detected by  /etc/<vendor release file> existence (ex.
> /etc/SuSE-release) in spec and all necessary actions are doing along
> the OS detection.
> Additionally for SLES there is "--without-selinux" flag while
> configuring, as SLES doesn't support SELinux.

Thank you for the patch. Can you please provide the spec file for the
SLES build as a separate file in sssd/contrib/suse/sssd.spec.in ? See
https://fedorahosted.org/pipermail/sssd-devel/2009-December/001786.html
for the reasoning.

I would also recommend not to use the /etc/*-release files to check for
the distribution, but rely on the variables defined by rpm. I have made
the experience that, e.g. the openSUSE build system does not always
install /etc/SuSE-release for SUSE builds. But there is a nice overview
of the variables defined by various distributions in
http://en.opensuse.org/Build_Service/cross_distribution_package_how_to

bye,
Sumit

[Sergei V. Kovylov]

Ok, i'll do this.

2009/12/9 Sumit Bose :
> On Wed, Dec 09, 2009 at 02:21:05PM +0300, Sergei V. Kovylov wrote:
> > Here you may find a patch for sssd.spec file which provide correct
> > build sssd for SLES (testes on SLES10SP1).
> > In brief:
> > There are 3 essences:
> > redhat
> > fedora
> > sles
> > which are detected by  /etc/<vendor release file> existence (ex.
> > /etc/SuSE-release) in spec and all necessary actions are doing along
> > the OS detection.
> > Additionally for SLES there is "--without-selinux" flag while
> > configuring, as SLES doesn't support SELinux.
>
> Thank you for the patch. Can you please provide the spec file for the
> SLES build as a separate file in sssd/contrib/suse/sssd.spec.in ? See
> https://fedorahosted.org/pipermail/sssd-devel/2009-December/001786.html
> for the reasoning.
>
> I would also recommend not to use the /etc/*-release files to check for
> the distribution, but rely on the variables defined by rpm. I have made
> the experience that, e.g. the openSUSE build system does not always
> install /etc/SuSE-release for SUSE builds. But there is a nice overview
> of the variables defined by various distributions in
> http://en.opensuse.org/Build_Service/cross_distribution_package_how_to
>
> bye,
> Sumit
> _______________________________________________
> sssd-devel mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/sssd-devel

[Sergei V. Kovylov]

Hi all.
Here is a patch to create sssd/contrib/suse/sssd.spec.in for SLES build.
It's been tested under SLES10SP1 and SLES10SP2.
The only problem is to make main ./configure process use --with-os for
correct detection of spec .

2009/12/9 Sergei V. Kovylov :
> Ok, i'll do this.
>
> 2009/12/9 Sumit Bose :
> > On Wed, Dec 09, 2009 at 02:21:05PM +0300, Sergei V. Kovylov wrote:
> > > Here you may find a patch for sssd.spec file which provide correct
> > > build sssd for SLES (testes on SLES10SP1).
> > > In brief:
> > > There are 3 essences:
> > > redhat
> > > fedora
> > > sles
> > > which are detected by  /etc/<vendor release file> existence (ex.
> > > /etc/SuSE-release) in spec and all necessary actions are doing along
> > > the OS detection.
> > > Additionally for SLES there is "--without-selinux" flag while
> > > configuring, as SLES doesn't support SELinux.
> >
> > Thank you for the patch. Can you please provide the spec file for the
> > SLES build as a separate file in sssd/contrib/suse/sssd.spec.in ? See
> > https://fedorahosted.org/pipermail/sssd-devel/2009-December/001786.html
> > for the reasoning.
> >
> > I would also recommend not to use the /etc/*-release files to check for
> > the distribution, but rely on the variables defined by rpm. I have made
> > the experience that, e.g. the openSUSE build system does not always
> > install /etc/SuSE-release for SUSE builds. But there is a nice overview
> > of the variables defined by various distributions in
> > http://en.opensuse.org/Build_Service/cross_distribution_package_how_to
> >
> > bye,
> > Sumit
> > _______________________________________________
> > sssd-devel mailing list
> > [e-mail]
> > https://fedorahosted.org/mailman/listinfo/sssd-devel

[Sumit Bose]

On Thu, Dec 10, 2009 at 01:26:11PM +0300, Sergei V. Kovylov wrote:
> Hi all.
> Here is a patch to create sssd/contrib/suse/sssd.spec.in for SLES build.
> It's been tested under SLES10SP1 and SLES10SP2.
> The only problem is to make main ./configure process use --with-os for
> correct detection of spec .

Thanks, I just have one minor request, can you change the BuildRequires
c-ares-devel to libcares-devel. c-ares is not available on SLES10 so I
assume you have build it yourself and called it the same as on Fedora.
But newer SUSE versions provide c-ares as libcares2 and libcares-devel.
(Btw. if you are interested in SUSE builds of sssd you might want to
have a look at
http://download.opensuse.org/repositories/home:/sbose:/sssd/)

It would be convenient for us, if you can provide your patch as a git
patch, but if it's easier for you to send standard patches I will create
the git patch and add you as the author.

bye,
Sumit

[Sergei V. Kovylov]

Hi Sumit.
Thanks for this repo, i'll change all BuildRequires within names of
libraries from the repo.
Yes, I've made special builds from Fedora srpms (as I work under it)
because it was the fastest way for me.

2009/12/10 Sumit Bose :
> On Thu, Dec 10, 2009 at 01:26:11PM +0300, Sergei V. Kovylov wrote:
> > Hi all.
> > Here is a patch to create sssd/contrib/suse/sssd.spec.in for SLES build.
> > It's been tested under SLES10SP1 and SLES10SP2.
> > The only problem is to make main ./configure process use --with-os for
> > correct detection of spec .
>
> Thanks, I just have one minor request, can you change the BuildRequires
> c-ares-devel to libcares-devel. c-ares is not available on SLES10 so I
> assume you have build it yourself and called it the same as on Fedora.
> But newer SUSE versions provide c-ares as libcares2 and libcares-devel.
> (Btw. if you are interested in SUSE builds of sssd you might want to
> have a look at
> http://download.opensuse.org/repositories/home:/sbose:/sssd/)
>
> It would be convenient for us, if you can provide your patch as a git
> patch, but if it's easier for you to send standard patches I will create
> the git patch and add you as the author.
>
> bye,
> Sumit
> _______________________________________________
> sssd-devel mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/sssd-devel

[Sumit Bose]

On Thu, Dec 10, 2009 at 11:04:17PM +0300, Sergei V. Kovylov wrote:
> Hi Sumit.
> Thanks for this repo, i'll change all BuildRequires within names of
> libraries from the repo.

sorry, the patch is missing
> Yes, I've made special builds from Fedora srpms (as I work under it)
> because it was the fastest way for me.
>
> 2009/12/10 Sumit Bose :
> > On Thu, Dec 10, 2009 at 01:26:11PM +0300, Sergei V. Kovylov wrote:
> > > Hi all.
> > > Here is a patch to create sssd/contrib/suse/sssd.spec.in for SLES build.
> > > It's been tested under SLES10SP1 and SLES10SP2.
> > > The only problem is to make main ./configure process use --with-os for
> > > correct detection of spec .
> >
> > Thanks, I just have one minor request, can you change the BuildRequires
> > c-ares-devel to libcares-devel. c-ares is not available on SLES10 so I
> > assume you have build it yourself and called it the same as on Fedora.
> > But newer SUSE versions provide c-ares as libcares2 and libcares-devel.
> > (Btw. if you are interested in SUSE builds of sssd you might want to
> > have a look at
> > http://download.opensuse.org/repositories/home:/sbose:/sssd/)
> >
> > It would be convenient for us, if you can provide your patch as a git
> > patch, but if it's easier for you to send standard patches I will create
> > the git patch and add you as the author.
> >
> > bye,
> > Sumit
> > _______________________________________________
> > sssd-devel mailing list
> > [e-mail]
> > https://fedorahosted.org/mailman/listinfo/sssd-devel
>
> sssd-devel mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/sssd-devel

[Sergei V. Kovylov]

Oh sorry - my mistake.
Unfourtunately, I'm not able to do a patch in git format , as I've
never work with git.

Also maybe a good idea is to create page in wiki "How to contribute
patches" and describe some basic steps.

2009/12/10 Sumit Bose :
> On Thu, Dec 10, 2009 at 11:04:17PM +0300, Sergei V. Kovylov wrote:
> > Hi Sumit.
> > Thanks for this repo, i'll change all BuildRequires within names of
> > libraries from the repo.
>
> sorry, the patch is missing
> > Yes, I've made special builds from Fedora srpms (as I work under it)
> > because it was the fastest way for me.
> >
> > 2009/12/10 Sumit Bose :
> > > On Thu, Dec 10, 2009 at 01:26:11PM +0300, Sergei V. Kovylov wrote:
> > > > Hi all.
> > > > Here is a patch to create sssd/contrib/suse/sssd.spec.in for SLES build.
> > > > It's been tested under SLES10SP1 and SLES10SP2.
> > > > The only problem is to make main ./configure process use --with-os for
> > > > correct detection of spec .
> > >
> > > Thanks, I just have one minor request, can you change the BuildRequires
> > > c-ares-devel to libcares-devel. c-ares is not available on SLES10 so I
> > > assume you have build it yourself and called it the same as on Fedora.
> > > But newer SUSE versions provide c-ares as libcares2 and libcares-devel.
> > > (Btw. if you are interested in SUSE builds of sssd you might want to
> > > have a look at
> > > http://download.opensuse.org/repositories/home:/sbose:/sssd/)
> > >
> > > It would be convenient for us, if you can provide your patch as a git
> > > patch, but if it's easier for you to send standard patches I will create
> > > the git patch and add you as the author.
> > >
> > > bye,
> > > Sumit
> > > _______________________________________________
> > > sssd-devel mailing list
> > > [e-mail]
> > > https://fedorahosted.org/mailman/listinfo/sssd-devel
> >
> > sssd-devel mailing list
> > [e-mail]
> > https://fedorahosted.org/mailman/listinfo/sssd-devel
>
> sssd-devel mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/sssd-devel

[Stephen Gallagher]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

That's a great idea. I'll put such a page together this afternoon.

Here's the short version:

git clone git://git.fedorahosted.org/sssd.git
cd sssd
<Make your changes>
git add <files you have changed>
git commit
<Add a commit comment>
git format-patch -1

This will output in the current directory a patch name starting with
0001-<commit comment>.patch

On 12/11/2009 06:58 AM, Sergei V. Kovylov wrote:
> Oh sorry - my mistake.
> Unfourtunately, I'm not able to do a patch in git format , as I've
> never work with git.
>
> Also maybe a good idea is to create page in wiki "How to contribute
> patches" and describe some basic steps.

- -- 
Stephen Gallagher
RHCE 804006346421761

Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAksieKwACgkQeiVVYja6o6OZLgCfd2Ov4XrCiXRmYatKUsQSjbmh
> oL0AoIh0Pk5lE8TpWkw9bvkHwfi8BQaK
> =5i+0
> -----END PGP SIGNATURE-----

[Stephen Gallagher]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/11/2009 06:58 AM, Sergei V. Kovylov wrote:
> Oh sorry - my mistake.
> Unfourtunately, I'm not able to do a patch in git format , as I've
> never work with git.
>
> Also maybe a good idea is to create page in wiki "How to contribute
> patches" and describe some basic steps.

I have updated the Contribute page on the Wiki.

Please see
https://fedorahosted.org/sssd/wiki/Contribute
for general details, including cloning the repository, as well as
https://fedorahosted.org/sssd/wiki/BugLifecycle
for a brief guideline on how to create patches.

A much better guide to Git than I can write is also available here:
http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html

- -- 
Stephen Gallagher
RHCE 804006346421761

Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAksmifMACgkQeiVVYja6o6Og0QCfQlhxgWbaL0I8ALv/EcSZ7SQ6
> jxkAn17K8W0oAaausifbJNf/yIj4PJ+L
> =6s4p
> -----END PGP SIGNATURE-----

[Sergei V. Kovylov]

Great... Thanks :-)

2009/12/14 Stephen Gallagher :
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 12/11/2009 06:58 AM, Sergei V. Kovylov wrote:
> > Oh sorry - my mistake.
> > Unfourtunately, I'm not able to do a patch in git format , as I've
> > never work with git.
> >
> > Also maybe a good idea is to create page in wiki "How to contribute
> > patches" and describe some basic steps.
>
> I have updated the Contribute page on the Wiki.
>
> Please see
> https://fedorahosted.org/sssd/wiki/Contribute
> for general details, including cloning the repository, as well as
> https://fedorahosted.org/sssd/wiki/BugLifecycle
> for a brief guideline on how to create patches.
>
> A much better guide to Git than I can write is also available here:
> http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html
>
> Stephen Gallagher
> RHCE 804006346421761
>
> Delivering value year after year.
> Red Hat ranks #1 in value among software vendors.
> http://www.redhat.com/promo/vendor/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAksmifMACgkQeiVVYja6o6Og0QCfQlhxgWbaL0I8ALv/EcSZ7SQ6
> jxkAn17K8W0oAaausifbJNf/yIj4PJ+L
> =6s4p
> -----END PGP SIGNATURE-----
> _______________________________________________
> sssd-devel mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/sssd-devel

[Sumit Bose]

On Fri, Dec 11, 2009 at 02:58:36PM +0300, Sergei V. Kovylov wrote:
> Oh sorry - my mistake.
> Unfourtunately, I'm not able to do a patch in git format , as I've
> never work with git.

ok, I have 'converted' it to git patch and I was able to build SLES10
rpms with this patch, so ACK.
> Also maybe a good idea is to create page in wiki "How to contribute
> patches" and describe some basic steps.
>
> 2009/12/10 Sumit Bose :
> > On Thu, Dec 10, 2009 at 11:04:17PM +0300, Sergei V. Kovylov wrote:
> > > Hi Sumit.
> > > Thanks for this repo, i'll change all BuildRequires within names of
> > > libraries from the repo.
> >
> > sorry, the patch is missing
> > > Yes, I've made special builds from Fedora srpms (as I work under it)
> > > because it was the fastest way for me.
> > >
> > > 2009/12/10 Sumit Bose :
> > > > On Thu, Dec 10, 2009 at 01:26:11PM +0300, Sergei V. Kovylov wrote:
> > > > > Hi all.
> > > > > Here is a patch to create sssd/contrib/suse/sssd.spec.in for SLES build.
> > > > > It's been tested under SLES10SP1 and SLES10SP2.
> > > > > The only problem is to make main ./configure process use --with-os for
> > > > > correct detection of spec .

Yes, I'll try to find out how to tell the autotools to do this.

bye,
Sumit
> > > > Thanks, I just have one minor request, can you change the BuildRequires
> > > > c-ares-devel to libcares-devel. c-ares is not available on SLES10 so I
> > > > assume you have build it yourself and called it the same as on Fedora.
> > > > But newer SUSE versions provide c-ares as libcares2 and libcares-devel.
> > > > (Btw. if you are interested in SUSE builds of sssd you might want to
> > > > have a look at
> > > > http://download.opensuse.org/repositories/home:/sbose:/sssd/)
> > > >
> > > > It would be convenient for us, if you can provide your patch as a git
> > > > patch, but if it's easier for you to send standard patches I will create
> > > > the git patch and add you as the author.
> > > >
> > > > bye,
> > > > Sumit
> > > > _______________________________________________
> > > > sssd-devel mailing list
> > > > [e-mail]
> > > > https://fedorahosted.org/mailman/listinfo/sssd-devel
> > >
> > > sssd-devel mailing list
> > > [e-mail]
> > > https://fedorahosted.org/mailman/listinfo/sssd-devel
> >
> > sssd-devel mailing list
> > [e-mail]
> > https://fedorahosted.org/mailman/listinfo/sssd-devel
> diff -uNr sssd/contrib/suse/sssd.spec.in sssd.b/contrib/suse/sssd.spec.in
> --- sssd/contrib/suse/sssd.spec.in      1970-01-01 00:00:00.000000000 +0000
> +++ sssd.b/contrib/suse/sssd.spec.in    2009-12-11 11:26:30.207320763 +0000
> @@ -0,0 +1,238 @@
> +%{!?python_sitearch: %global python_sitearch %(%{__python} -c "from distutils.sysconfig import *; import sys; sys.stdout.write(get_python_lib(1))")}
> +%{!?python_sitelib: %global python_sitelib %(%{__python} -c "from distutils.sysconfig import *; import sys; sys.stdout.write(get_python_lib())")}
>
> +Name: @PACKAGE_NAME@
> +Version: @PACKAGE_VERSION@
> +Release: 0@PRERELEASE_VERSION@%{?dist}
> +Group: Applications/System
> +Summary: System Security Services Daemon
> +# The entire source code is GPLv3+ except replace/ which is LGPLv3+
> +License: GPLv3+ and LGPLv3+
> +URL: http://www.freeipa.org/
> +Source0: %{name}-%{version}.tar.gz
> +BuildRoot: %(mktemp -ud %{_tmppath}/%{name}-%{version}-%{release}-XXXXXX)
>
> +### Patches ###
>
> +### Dependencies ###
>
> +Requires: libldb0 >= 0.9.3
> +Requires: libtdb1 >= 1.1.3
> +Requires: sssd-client = %{version}-%{release}
> +Requires: cyrus-sasl-gssapi
> +Requires(post): python
> +Requires(preun): aaa_base procps filesystem
> +Requires(postun): /sbin/service
>
> +%define servicename sssd
> +%define sssdstatedir %{_localstatedir}/lib/sss
> +%define dbpath %{sssdstatedir}/db
> +%define pipepath %{sssdstatedir}/pipes
> +%define pubconfpath %{sssdstatedir}/pubconf
>
> +### Build Dependencies ###
>
> +BuildRequires: autoconf
> +BuildRequires: automake
> +BuildRequires: libtool
> +BuildRequires: m4
> +BuildRequires: popt-devel
> +BuildRequires: libtalloc-devel
> +BuildRequires: libtevent0-devel
> +BuildRequires: libtdb1-devel
> +BuildRequires: libldb0-devel
> +BuildRequires: libcares-devel
> +BuildRequires: dbus-1-devel
> +BuildRequires: dbus-1
> +BuildRequires: openldap2-devel
> +BuildRequires: pam-devel
> +BuildRequires: mozilla-nss-devel
> +BuildRequires: mozilla-nspr-devel
> +BuildRequires: pcre-devel
> +BuildRequires: libxslt
> +BuildRequires: libxml2
> +BuildRequires: docbook-xsl-stylesheets
> +BuildRequires: krb5-devel
> +BuildRequires: python-devel
>
> +%description
> +Provides a set of daemons to manage access to remote directories and
> +authentication mechanisms. It provides an NSS and PAM interface toward
> +the system and a pluggable backend system to connect to multiple different
> +account sources. It is also the basis to provide client auditing and policy
> +services for projects like FreeIPA.
>
> +%package client
> +Summary: SSSD Client libraries for NSS and PAM
> +Group: Applications/System
>
> +%description client
> +Provides the libraries needed by the PAM and NSS stacks to connect to the SSSD
> +service.
>
> +%prep
> +%setup -q
>
> +%build
> +NSS_LIBS=-lnss3 \
> +KRB5_LIBS=-lkrb5 \
> +%configure \
> --without-tests \
> --with-db-path=%{dbpath} \
> --with-pipe-path=%{pipepath} \
> --with-pubconf-path=%{pubconfpath} \
> --with-init-dir=%{_initrddir} \
> --without-selinux \
> --with-os=suse \
> --enable-nsslibdir=/%{_lib}
>
> +make %{?_smp_mflags}
>
> +%install
> +rm -rf $RPM_BUILD_ROOT
>
> +make install DESTDIR=$RPM_BUILD_ROOT
>
> +# Prepare language files
> +/usr/lib/rpm/find-lang.sh $RPM_BUILD_ROOT sss_daemon
> +/usr/lib/rpm/find-lang.sh $RPM_BUILD_ROOT sss_client
>
> +# Copy default sssd.conf file
> +mkdir -p $RPM_BUILD_ROOT/%{_sysconfdir}/sssd
> +install -m600 server/examples/sssd.conf $RPM_BUILD_ROOT%{_sysconfdir}/sssd/sssd.conf
> +install -m400 server/config/etc/sssd.api.conf $RPM_BUILD_ROOT%{_sysconfdir}/sssd/sssd.api.conf
> +install -m400 server/config/etc/sssd.api.d/* $RPM_BUILD_ROOT%{_sysconfdir}/sssd/sssd.api.d/
>
> +# Remove .la files created by libtool
> +rm -f \
> $RPM_BUILD_ROOT/%{_lib}/libnss_sss.la \
> $RPM_BUILD_ROOT/%{_lib}/security/pam_sss.la \
> $RPM_BUILD_ROOT/%{_libdir}/ldb/memberof.la \
> $RPM_BUILD_ROOT/%{_libdir}/sssd/libsss_ldap.la \
> $RPM_BUILD_ROOT/%{_libdir}/sssd/libsss_proxy.la \
> $RPM_BUILD_ROOT/%{_libdir}/sssd/libsss_krb5.la \
> $RPM_BUILD_ROOT/%{_libdir}/sssd/libsss_ipa.la \
> $RPM_BUILD_ROOT/%{_libdir}/krb5/plugins/libkrb5/sssd_krb5_locator_plugin.la \
> $RPM_BUILD_ROOT/%{python_sitearch}/pysss.la
>
> +if test -e $RPM_BUILD_ROOT/%{_libdir}/krb5/plugins/libkrb5/sssd_krb5_locator_plugin.so
> +then
> # Apppend this file to the sss_daemon.lang
> # Older versions of rpmbuild can only handle one -f option
> echo %{_libdir}/krb5/plugins/libkrb5/sssd_krb5_locator_plugin.so >> sss_daemon.lang
>
> +fi
> +%clean
> +rm -rf $RPM_BUILD_ROOT
>
> +%files -f sss_daemon.lang
> +%defattr(-,root,root,-)
> +%doc COPYING
> +%{_initrddir}/%{name}
> +%{_sbindir}/sssd
> +%{_sbindir}/sss_useradd
> +%{_sbindir}/sss_userdel
> +%{_sbindir}/sss_usermod
> +%{_sbindir}/sss_groupadd
> +%{_sbindir}/sss_groupdel
> +%{_sbindir}/sss_groupmod
> +%{_libexecdir}/%{servicename}/
> +%{_libdir}/%{name}/
> +%{_libdir}/ldb/memberof.so
> +%dir %{sssdstatedir}
> +%attr(700,root,root) %dir %{dbpath}
> +%attr(755,root,root) %dir %{pipepath}
> +%attr(755,root,root) %dir %{pubconfpath}
> +%attr(700,root,root) %dir %{pipepath}/private
> +%attr(750,root,root) %dir %{_var}/log/%{name}
> +%attr(700,root,root) %dir %{_sysconfdir}/sssd
> +%config(noreplace) %{_sysconfdir}/sssd/sssd.conf
> +%config %{_sysconfdir}/sssd/sssd.api.conf
> +%attr(700,root,root) %dir %{_sysconfdir}/sssd/sssd.api.d
> +%config %{_sysconfdir}/sssd/sssd.api.d/
> +%{_mandir}/man5/sssd.conf.5*
> +%{_mandir}/man5/sssd-ipa.5*
> +%{_mandir}/man5/sssd-krb5.5*
> +%{_mandir}/man5/sssd-ldap.5*
> +%{_mandir}/man8/sssd.8*
> +%{_mandir}/man8/sss_groupadd.8*
> +%{_mandir}/man8/sss_groupdel.8*
> +%{_mandir}/man8/sss_groupmod.8*
> +%{_mandir}/man8/sss_useradd.8*
> +%{_mandir}/man8/sss_userdel.8*
> +%{_mandir}/man8/sss_usermod.8*
> +%{_mandir}/man8/sssd_krb5_locator_plugin.8*
> +%{python_sitearch}/pysss.so
> +%{python_sitelib}/*.py*
>
> +%files client -f sss_client.lang
> +%defattr(-,root,root,-)
> +/%{_lib}/libnss_sss.so.2
> +/%{_lib}/security/pam_sss.so
> +%{_mandir}/man8/pam_sss.8*
>
> +%post
> +/sbin/ldconfig
> +/sbin/chkconfig --add %{servicename}
> +if [ $1 -ge 2 ] ; then
> +# a one-time upgrade from confdb v1 to v2, only if upgrading
> python %{_libexecdir}/%{servicename}/upgrade_config.py
>
> +fi
>
> +%preun
> +if [ $1 = 0 ]; then
> /sbin/service %{servicename} stop 2>&1 > /dev/null
> /sbin/chkconfig --del %{servicename}
>
> +fi
>
> +%postun
> +/sbin/ldconfig
> +if [ $1 -ge 1 ] ; then
> /sbin/service %{servicename} condrestart 2>&1 > /dev/null
>
> +fi
>
> +%post client -p /sbin/ldconfig
>
> +%postun client -p /sbin/ldconfig
>
> +%changelog
> +* Mon Sep 28 2009 Sumit Bose  - 0.6.0-0
> +- New upstream release 0.6.0
>
> +* Fri Sep 25 2009 Simo Sorce  - 0.5.0-1
> +- Split package into server and clients components
> +- Convert to new config file format
>
> +* Wed Sep 02 2009 Stephen Gallagher  - 0.5.0-0
> +- New upstream release 0.5.0
>
> +* Mon May 18 2009 Stephen Gallagher  - 0.4.0-1
> +- Convert build system to automake
>
> +* Mon Apr 20 2009 Jakub Hrozek  - 0.3.2-1
> +- bugfix release 0.3.2
>
> +* Mon Apr 13 2009 Simo Sorce  - 0.3.1-1
> +- bugfix release
>
> +* Sun Apr 12 2009 Stephen Gallagher  - 0.3.0-2
> +- Remove InfoPipe from RPM build
>
> +* Sun Apr 12 2009 Stephen Gallagher  - 0.3.0-1
> +- Convert to using /etc/sssd/sssd.conf for configuration
>
> +* Tue Mar 10 2009 Simo Sorce  - 0.2.1-1
> +- Bump up to version 0.2.1
>
> +* Fri Mar 06 2009 Jakub Hrozek  - 0.1.0-4
> +- fixed items found during review
> +- added initscript
>
> +* Thu Mar 05 2009 Sumit Bose  - 0.1.0-3
> +- added sss_client
>
> +* Mon Feb 23 2009 Jakub Hrozek  - 0.1.0-2
> +- Small cleanup and fixes in the spec file
>
> +* Thu Feb 12 2009 Stephen Gallagher  - 0.1.0-1
> +- Initial release (based on version 0.1.0 upstream code)
> sssd-devel mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/sssd-devel

[Stephen Gallagher]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/15/2009 06:53 AM, Sumit Bose wrote:
> On Fri, Dec 11, 2009 at 02:58:36PM +0300, Sergei V. Kovylov wrote:
> > Oh sorry - my mistake.
> > Unfourtunately, I'm not able to do a patch in git format , as I've
> > never work with git.
>
> ok, I have 'converted' it to git patch and I was able to build SLES10
> rpms with this patch, so ACK.

Pushed to master and 1-0-0

- -- 
Stephen Gallagher
RHCE 804006346421761

Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAksnkSIACgkQeiVVYja6o6O1QACgmapqtWhtThTyZBENO3u16Qrj
> p7gAnAo9OPdChVPiDZUkdHiGl94K2Jlz
> =3LYe
> -----END PGP SIGNATURE-----

[Sergei V. Kovylov]

Hi all.
Here is update of suse/sssd.spec.in file to meet current changes
(splitting sssd and dhash, etc).

2009/12/15 Stephen Gallagher :
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 12/15/2009 06:53 AM, Sumit Bose wrote:
> > On Fri, Dec 11, 2009 at 02:58:36PM +0300, Sergei V. Kovylov wrote:
> > > Oh sorry - my mistake.
> > > Unfourtunately, I'm not able to do a patch in git format , as I've
> > > never work with git.
> >
> > ok, I have 'converted' it to git patch and I was able to build SLES10
> > rpms with this patch, so ACK.
>
> Pushed to master and 1-0-0
>
> Stephen Gallagher
> RHCE 804006346421761
>
> Delivering value year after year.
> Red Hat ranks #1 in value among software vendors.
> http://www.redhat.com/promo/vendor/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAksnkSIACgkQeiVVYja6o6O1QACgmapqtWhtThTyZBENO3u16Qrj
> p7gAnAo9OPdChVPiDZUkdHiGl94K2Jlz
> =3LYe
> -----END PGP SIGNATURE-----
> _______________________________________________
> sssd-devel mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/sssd-devel

[Stephen Gallagher]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sergei, I appreciate the patch, but I'm going to recommend holding off
on it for a couple days, as I'm currently working to split out several
of our other libraries as well (path_utils, collection, ini and
refarray), so it might be better to solve this all at once.

On 02/01/2010 08:40 AM, Sergei V. Kovylov wrote:
> Hi all.
> Here is update of suse/sssd.spec.in file to meet current changes
> (splitting sssd and dhash, etc).

- -- 
Stephen Gallagher
RHCE 804006346421761

Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAktm3P4ACgkQeiVVYja6o6M7jACfSdWp9GyPxnMLP6g/kHLy4nlC
> t7YAn3eNDYNc1nggcYnpBQ/pXtOHD8Pu
> =mNvt
> -----END PGP SIGNATURE-----

[Sumit Bose]

Hi,

this patch works for me. I think it's ok to integrate the changes as
they are available.

ACK

bye,
Sumit

On Mon, Feb 01, 2010 at 08:54:06AM -0500, Stephen Gallagher wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Sergei, I appreciate the patch, but I'm going to recommend holding off
> on it for a couple days, as I'm currently working to split out several
> of our other libraries as well (path_utils, collection, ini and
> refarray), so it might be better to solve this all at once.
>
> On 02/01/2010 08:40 AM, Sergei V. Kovylov wrote:
> > Hi all.
> > Here is update of suse/sssd.spec.in file to meet current changes
> > (splitting sssd and dhash, etc).
>
> Stephen Gallagher
> RHCE 804006346421761
>
> Delivering value year after year.
> Red Hat ranks #1 in value among software vendors.
> http://www.redhat.com/promo/vendor/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAktm3P4ACgkQeiVVYja6o6M7jACfSdWp9GyPxnMLP6g/kHLy4nlC
> t7YAn3eNDYNc1nggcYnpBQ/pXtOHD8Pu
> =mNvt
> -----END PGP SIGNATURE-----
> _______________________________________________
> sssd-devel mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/sssd-devel

[Stephen Gallagher]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/01/2010 03:26 PM, Sumit Bose wrote:
> Hi,
>
> this patch works for me. I think it's ok to integrate the changes as
> they are available.
>
> ACK

Pushed to master.

- -- 
Stephen Gallagher
RHCE 804006346421761

Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAktogKAACgkQeiVVYja6o6OD4ACfbue4KWSmaH8GBy71mHt23AvP
> 9U0AnjwbE6rVNc5skuzqIJhkrO9PVPqq
> =UIvN
> -----END PGP SIGNATURE-----