touch-packages team mailing list archive

[Launchpad Bug Tracker <1480310@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package systemd - 224-2ubuntu2

---------------
systemd (224-2ubuntu2) wily; urgency=medium

  * Cherry-pick FTBFS (with pkg-create-dbgsym) fix from Debian master
branch.

systemd (224-2ubuntu1) wily; urgency=medium

  * Merge with Debian unstable. Remaining Ubuntu changes:
    - Hack to support system-image read-only /etc, and modify files in
      /etc/writable/ instead.
    - Keep our much simpler udev maintainer scripts (all platforms must
      support udev, no debconf).
    - initramfs init-bottom: If LVM is installed, settle udev,
      otherwise we get missing LV symlinks. Workaround for LP #1185394.
    - Add debian/udev.lvm2.init: Dummy SysV init script to satisfy insserv
      dependencies to "lvm2" which is handled with udev rules in Ubuntu.
    - Add debian/udev.lvm2.service to avoid running the dummy lvm2 init
      script.
    - Provide shutdown fallback for upstart. (LP: #1370329)
    - debian/extra/ifup@.service: Additionally run for "auto" class. We don't
      really support "allow-hotplug" in Ubuntu at the moment, so we need to
      deal with "auto" devices appearing after "/etc/init.d/networking start"
      already ran. (LP: #1374521)
    - ifup@.service: Drop dependency on networking.service (i. e.
      /etc/init.d/networking), and merely ensure that /run/network exists.
      This avoids unnecessary dependencies/waiting during boot and dependency
      cycles if hooks wait for other interfaces to come up (like ifenslave
      with bonding interfaces). (LP: #1414544)
    - Add Get-RTC-is-in-local-time-setting-from-etc-default-rc.patch: In
      Ubuntu we currently keep the setting whether the RTC is in local or UTC
      time in /etc/default/rcS "UTC=yes|no", instead of /etc/adjtime.
      (LP: #1377258)
    - Put session scopes into all cgroup controllers. This makes unprivileged
      user LXC containers work under systemd. (LP: #1346734)
    - systemctl: Don't forward telinit u to upstart. This works around
      upstart's Restart() always reexec'ing /sbin/init on Restart(), even if
      that changes to point to systemd during the upgrade. This avoids running
      systemd during a dist-upgrade. (LP: #1430479)
    - Drop hwdb-update dependency from udev-trigger.service, which got
      introduced in v219-stable. This causes udev and plymouth to start too
      late and isn't really needed in Ubuntu yet as we don't support stateless
      systems yet and handle hwdb.bin updates through dpkg triggers. This can
      be dropped again with initramfs-tools 0.117.
    - Lower Breaks: to plymouth version which has the udev inotify fix in
      Ubuntu.
    - Lower apparmor Breaks: to the Ubuntu version that dropped $remote_fs.
    - Change systemd-sysv's conflicts to upstart-sysv. (LP: #1422681)

    Upgrade fixes, keep until 16.04 LTS release:
    - systemd Conflicts/Replaces/Provides systemd-services.
    - Remove obsolete systemd-logind upstart job.
    - Clean up obsolete /etc/udev/rules.d/README.
    - systemd.postinst: Migrate mountall specific fstab options to standard
      util-linux "nofail" option.

  * Don't build new systemd-journal-remote package and drop libmicrohttpd-dev.
    This is blocked by the MIR (LP #1488341) and feature freeze.

systemd (224-3) UNRELEASED; urgency=medium

  * Add better fix for "systemctl link/enable" breakage with full paths.
    (LP: #1480310)
  * debian/rules: Add missing $(dh_options) in overridden debhelper targets.

systemd (224-2) unstable; urgency=medium

  [ Martin Pitt ]
  * Skip systemd-fsckd autopkgtest if /run/initramfs/fsck-root exists, i. e.
    the initramfs already ran fsck.
  * Fix broken ACL in tmpfiles.d/systemd.conf. (Closes: #794645, LP: #1480552)
  * Add debian/tests/unit-config: Test "systemctl link"; reproduces LP#1480310.
  * Add a hack to unbreak "systemctl link". (LP: #1480310)
  * debian/extra/rules-ubuntu/40-hyperv-hotadd.rules: Also apply to Xen, and
    rename to 40-vm-hotadd.rules.
  * Fix networkd crash. (Closes: #796358)
  * debian/rules: Remove all files/empty dirs in systemd which are already
    shipped by systemd-* or udev, instead of an explicit list.
  * Bump "mount" dependency to >= 2.26, to ensure "swapon -o" availability.
    (Closes: #796389)
  * Install /lib/systemd/network/* into udev instead of systemd, as it's
    really udev which is evaluating these.
  * Split out "systemd-container" package with machined and nspawn and enable
    importd. Add new libbz2-dev, zlib1g-dev, and libcurl-dev build deps.
    (LP: #1448900)
  * Move transitional libgcrypt11-dev build dep to libgcrypt20-dev.
  * debian/rules: Limit check for libraries in /usr to systemd and udev
    packages, as other packages like systemd-containers can (and do) link to
    /usr.
  * Build-depend on dpkg-dev (>= 1.17.14) and bump debhelper version for build
    profiles support.
  * Drop "display-managers" autopkgtest, obsolete with dropped
    default-display-manager-generator.
  * boot-and-services autopkgtest: Add systemd-container test dependency for
    the nspawn tests.
  * Don't enable audit support when building with "stage1" profile, to avoid
    circular build dep.

  [ Helmut Grohne ]
  * Improve support for cross-building and bootstrapping.

  [ Michael Biebl ]
  * Drop default-display-manager-generator. All major desktops now use a
    display manager which support the new scheme and setup the
    /etc/systemd/system/display-manager.service symlink correctly.
  * Add new binary package "systemd-journal-remote" with tools for
    sending/receiving remote journal logs:
    systemd-journal-{remote,upload,gatewayd}. (Closes: #742802, LP: #1480952)

 -- Martin Pitt <martin.pitt@xxxxxxxxxx>  Thu, 27 Aug 2015 14:23:04
+0200

** Changed in: systemd (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1480310

Title:
  systemctl link request failed for service FOO: Unit name FOO is not
  valid.

Status in juju-core:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  As seen in
      http://reports.vapour.ws/releases/2936/job/local-deploy-wily-amd64/attempt/136
  Juju cannot bootstrap on wily because 
     ERROR juju.service.systemd service.go:149 dbus link request failed for service
      "juju-db-jenkins-local-deploy-wily-amd64": Unit name
      /var/lib/juju/init/juju-db-jenkins-local-deploy-wily-amd64/juju-db-jenkins-local-deploy-wily-amd64.service
      is not valid.

  This error first occurred after the wily-slave got package updates.
  The released jujus get the same errors as the jujus under test. This
  issue is probably an Ubuntu packaging break.

  I am making the test non-voting since we can see table 1.24.3 no
  longer works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1480310/+subscriptions