[Bug 1152187] Re: [MIR] systemd

[Michael Terry]

And now for the packaging/maintainability review.  I looked only at
version 198 in raring-proposed.

* Packaging is understandably complex.  Not only are there lots of vaguely-related components in this one source, but they are system-level core bits.
* Builds cleanly.
* Has bug subscribers.
* Both desktop and foundation teams are looking after the package.
* Existing bugs seem tolerable (most of them deal with the init pieces anyway).  Should keep a watch on Debian bug 701364, which says it ftbfs with gcc-4.8.
* Uses symbols files.
* Uses python2, but does so with dh_python2 and the python-systemd package is not likely to be pulled onto the Desktop CD, so that's fine.

Seems almost OK.  This will definitely not be a hands-off package, but
it's important enough for us to accept the burden.

The one big beef I have is that we don't run any of the unit tests,
because some of them fail (pitti says they make assumptions that aren't
true on Ubuntu).  I'd like to see those fixed or the rest of the unit
tests enabled, so we have at least some coverage.

** Changed in: systemd (Ubuntu)
       Status: New => Incomplete

** Changed in: systemd (Ubuntu)
     Assignee: Michael Terry (mterry) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1152187

Title:
  [MIR] systemd

Status in “systemd” package in Ubuntu:
  Incomplete

Bug description:
  * The package is in universe and built on all archs:
  https://launchpad.net/ubuntu/+source/systemd/44-10ubuntu1

  * Rationale:

  - in a first step we want systemd-services promoted to replace ubuntu-
  system-services

  -  We will also want to move from consolekit to logind soon
  (https://blueprints.launchpad.net/ubuntu/+spec/foundations-1303
  -consolekit-logind-migration)

  - udev has been merged in the systemd source upstream so we will want
  to build it from there at some point as well

  we don't plan to use the systemd init system at this point

  * Security:

  there has been some security issues in the past
  http://secunia.com/advisories/search/?search=systemd
  http://secunia.com/advisories/48220/
  http://secunia.com/advisories/48208/
  http://secunia.com/advisories/48331/

  Those are mostly logind issue and have been fixed upstream.

  Our current package is outdated but we do plan to update it before
  starting using logind. There should be no issue with the services

  * Quality:
  - there is no RC bug in debian: http://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=systemd
  - there is no bug open in launchpad: https://launchpad.net/ubuntu/+source/systemd/+bugs
  - upstream is active and responsive to issues

  The desktop bugs team is subscribed to the package in launchpad,
  foundations/desktop will maintain the package and look to the bug
  reports regularly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1152187/+subscriptions