lp:ubuntu/trusty-proposed/sblim-sfcb

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

12. By Daniel T Chen on 2014-01-24

* Use dh-autoreconf for newer arches, resolving FTBFS.
  - Work around automake syntax;
  - Add missing lib to link.

11. By Kent Baxley on 2013-12-17

Fix one more build dep. LP: #1262338

10. By Colin Watson on 2011-05-25

Rebuild for OpenSSL 1.0.0.

9. By Guillaume BOTTEX <email address hidden> on 2010-06-07

* New upstream release
* Packaging format changed from 1.0 to 3.0 (quilt)
* Add missing man pages for getSchema and genSslCert
* Add missing binary sfcbinst2mof
* flex and unzip added as dependencies, because needed at build time by
  configure

8. By Thierry Carrez on 2009-08-20

* debian/rules, debian/control: Enable SLP agent support
* debian/sfcb.install: Install all libs rather than relying on sfcb.links
  to create the links

7. By Thierry Carrez on 2009-07-16

* New upstream release (LP: #394235)
* debian/control: Add a version to the debhelper build dependency

6. By Thierry Carrez on 2009-06-08

* New upstream release.
* debian/rules: Removed rpath hacks, SFCB default build handles that now.
* Removed 1934753-remove-assignment.diff, now upstream.
* Refreshed patch cim-schema-location.diff

5. By Thierry Carrez on 2009-03-23

debian/sfcb.init: Use retry schedule in start-stop-daemon --stop to kill
sfcbd if it doesn't stop when nicely asked (LP: #344697)

4. By Thierry Carrez on 2009-03-02

debian/sfcb.init: Export /etc/default/sfcb variables so that they are
not ignored by sfcb (LP: #334812)

3. By Thierry Carrez on 2008-09-24

* debian/sfcb.install: Do not install incorrect PAM configuration anymore,
  let SFCB fallback on /etc/pam.d/other (LP: #262455)
* debian/sfcb.init: Fix status action so that it doesn't always report SFCB
  as started (LP: #262635)
* debian/control: added dep on lsb-base to be able to use status_of_proc