1. 26 Apr, 2014 1 commit
  2. 27 Feb, 2014 1 commit
  3. 15 Feb, 2014 1 commit
  4. 21 Dec, 2013 1 commit
  5. 28 Nov, 2013 1 commit
  6. 27 Nov, 2013 2 commits
  7. 24 Jul, 2013 1 commit
    • Michael Biebl's avatar
      Restart systemd-logind.service on upgrades · e14b697b
      Michael Biebl authored
      The CreateSession D-Bus API of systemd-logind changed between v44 and
      v204 [1]. As result, newer versions of libpam-systemd fail to register a
      new session if they talk to the old systemd-logind process.
      Restarting systemd-logind.service when upgrading from v44 means we will
      lose existing sessions, but as wheezy still has ConsoleKit as default,
      this shouldn't matter that much.  Closes: #717403
      
      [1] https://bugs.freedesktop.org/show_bug.cgi?id=67131
      e14b697b
  8. 21 Jul, 2013 1 commit
    • Daniel Schaal's avatar
      Add handling of Message Catalog files. · 6853903f
      Daniel Schaal authored
      This compiles the files from /usr/lib/systemd/catalog into a
      binary database, which is used by journalctl to provide
      additional information for log entries. journalctl only uses
      the binary database in /var/lib/systemd/catalog/database.
      
      Call journalctl --update-catalog in systemd.postinst and when
      triggered by dpkg to update the Message Catalog database.
      Also add systemd.postrm to remove the database on purge.
      
      See http://www.freedesktop.org/wiki/Software/systemd/catalog/
      6853903f
  9. 18 Jul, 2013 2 commits
  10. 19 Jun, 2013 1 commit
  11. 09 Feb, 2013 1 commit
    • Michael Biebl's avatar
      Use a file trigger to automatically enable service and socket units · d7e57817
      Michael Biebl authored
      A lot of packages simply install systemd units but do not enable them.
      Running "systemctl enable" in the maintainer scripts is not really an
      option since it is not guaranteed that systemd is installed. We
      therefore implement a workaround for wheezy which is supposed to go away
      in jessie once we have the necessary tools support in debhelper etc.
      
      What the proposed workaround does is:
      - Install a dpkg file trigger for /lib/systemd/system which triggers a
        script named /lib/systemd/debian-enable-units every time a package
        installs a systemd unit.
      - Run this script also upon initial installation of systemd and once on
        upgrades from earlier releases.
      
      The script in particular does the following:
      - Run "systemctl enable" for each service or socket it finds in
        /lib/systemd/system but does that only once, so the administrator can
        disable them if wanted.
      - Record the state and installed symlinks. When a package shipping
        systemd units is uninstalled, we remove those symlinks again.
      - Use a blacklist for internal services.
      - If systemd is not the active init, it will only create a tag file
        and next time we boot with systemd, the script will be run early
        during boot. For that we install a service named
        debian-enable-units.service which is run in basic.target.
      
      http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692150
      d7e57817
  12. 01 Jul, 2012 1 commit
  13. 30 Jun, 2012 1 commit
  14. 03 Apr, 2012 1 commit
  15. 09 Mar, 2012 1 commit
  16. 06 Mar, 2012 3 commits
  17. 28 Feb, 2012 1 commit
  18. 27 Feb, 2012 2 commits
  19. 12 Oct, 2011 1 commit
  20. 14 Sep, 2011 7 commits
  21. 29 Jun, 2011 1 commit
  22. 21 Apr, 2011 1 commit
  23. 11 Mar, 2011 1 commit
  24. 04 Nov, 2010 1 commit
  25. 02 Nov, 2010 2 commits