[Touch-packages] [Bug 1397361] Re: Failed to try-restart systemd-resolved.service:
** Changed in: systemd (Debian) 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/1397361 Title: Failed to try-restart systemd-resolved.service: Status in systemd package in Ubuntu: Fix Released Status in systemd package in Debian: Fix Released Bug description: This bug is filed against the latest systemd (217-1) in the debian sid/experimental branch. When upgrading to this version (from sid version), this is the warning message I get: Failed to try-restart systemd-resolved.service: Unit systemd-resolved.service failed to load: No such file or directory. However, the systemd (217) works itself fine with no issues, it is only this installation message the bug is about. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1397361/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1397361] Re: Failed to try-restart systemd-resolved.service:
** Changed in: systemd (Ubuntu) Status: In Progress = Fix Committed -- 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/1397361 Title: Failed to try-restart systemd-resolved.service: Status in systemd package in Ubuntu: Fix Committed Status in systemd package in Debian: New Bug description: This bug is filed against the latest systemd (217-1) in the debian sid/experimental branch. When upgrading to this version (from sid version), this is the warning message I get: Failed to try-restart systemd-resolved.service: Unit systemd-resolved.service failed to load: No such file or directory. However, the systemd (217) works itself fine with no issues, it is only this installation message the bug is about. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1397361/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1397361] Re: Failed to try-restart systemd-resolved.service:
** Changed in: systemd (Debian) Status: New = Fix Committed -- 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/1397361 Title: Failed to try-restart systemd-resolved.service: Status in systemd package in Ubuntu: Fix Committed Status in systemd package in Debian: Fix Committed Bug description: This bug is filed against the latest systemd (217-1) in the debian sid/experimental branch. When upgrading to this version (from sid version), this is the warning message I get: Failed to try-restart systemd-resolved.service: Unit systemd-resolved.service failed to load: No such file or directory. However, the systemd (217) works itself fine with no issues, it is only this installation message the bug is about. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1397361/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1397361] Re: Failed to try-restart systemd-resolved.service:
This bug was fixed in the package systemd - 217-2ubuntu1
---
systemd (217-2ubuntu1) vivid; urgency=medium
* Merge with Debian unstable. See 217-1ubuntu1 for remaining Ubuntu changes.
* Put session scopes into all cgroup controllers instead of their parent
user slices. This works better with killing sessions and is consistent
with the systemd controller.
* Do not realize and migrate cgroups multiple times, in particular
-.slice. This fixes PIDs in non-systemd cgroup controllers to be
randomly migrated back to /. (LP: #1346734)
* boot-and-services autopkgtest: Give test apparmor job some time to
actually finish.
systemd (217-2) experimental; urgency=medium
* Re-enable journal forwarding to syslog, until Debian's sysloggers
can/do all read from the journal directly.
* Fix hostnamectl exit code on success.
* Fix diff failed with error code 1 spew with systemd-delta.
(Closes: #771397)
* Re-enable systemd-resolved. This wasn't meant to break the entire
networkd, just disable the new NSS module. Remove that one manually
instead. (Closes: #771423, LP: #1397361)
* Import v217-stable patches (up to commit bfb4c47 from 2014-11-07).
* Disable AppArmor again. This first requires moving libapparmor to /lib
(see #771667). (Closes: #771652)
* systemd.bug-script: Capture stderr of systemd-{delta,analyze}.
(Closes: #771498)
-- Martin Pitt martin.p...@ubuntu.com Mon, 01 Dec 2014 17:17:30 +0100
** 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/1397361
Title:
Failed to try-restart systemd-resolved.service:
Status in systemd package in Ubuntu:
Fix Released
Status in systemd package in Debian:
Fix Committed
Bug description:
This bug is filed against the latest systemd (217-1) in the debian
sid/experimental branch.
When upgrading to this version (from sid version), this is the warning
message I get:
Failed to try-restart systemd-resolved.service: Unit systemd-resolved.service
failed to load: No such file or directory.
However, the systemd (217) works itself fine with no issues, it is
only this installation message the bug is about.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1397361/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1397361] Re: Failed to try-restart systemd-resolved.service:
** Bug watch added: Debian Bug tracker #771423 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771423 ** Also affects: systemd (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771423 Importance: Unknown Status: Unknown ** Changed in: systemd (Ubuntu) Status: New = In Progress ** Changed in: systemd (Ubuntu) Assignee: (unassigned) = Martin Pitt (pitti) -- 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/1397361 Title: Failed to try-restart systemd-resolved.service: Status in systemd package in Ubuntu: In Progress Status in systemd package in Debian: Unknown Bug description: This bug is filed against the latest systemd (217-1ubuntu1) in the Vivid branch. When upgrading to this version, this is the warning message I get: Failed to try-restart systemd-resolved.service: Unit systemd-resolved.service failed to load: No such file or directory. However, the systemd (217) works itself fine with no issues, it is only this installation message the bug is about. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1397361/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1397361] Re: Failed to try-restart systemd-resolved.service:
** Changed in: systemd (Ubuntu) Importance: Undecided = High -- 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/1397361 Title: Failed to try-restart systemd-resolved.service: Status in systemd package in Ubuntu: In Progress Status in systemd package in Debian: Unknown Bug description: This bug is filed against the latest systemd (217-1ubuntu1) in the Vivid branch. When upgrading to this version, this is the warning message I get: Failed to try-restart systemd-resolved.service: Unit systemd-resolved.service failed to load: No such file or directory. However, the systemd (217) works itself fine with no issues, it is only this installation message the bug is about. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1397361/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1397361] Re: Failed to try-restart systemd-resolved.service:
** Changed in: systemd (Debian) Status: Unknown = New -- 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/1397361 Title: Failed to try-restart systemd-resolved.service: Status in systemd package in Ubuntu: In Progress Status in systemd package in Debian: New Bug description: This bug is filed against the latest systemd (217-1ubuntu1) in the Vivid branch. When upgrading to this version, this is the warning message I get: Failed to try-restart systemd-resolved.service: Unit systemd-resolved.service failed to load: No such file or directory. However, the systemd (217) works itself fine with no issues, it is only this installation message the bug is about. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1397361/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1397361] Re: Failed to try-restart systemd-resolved.service:
** Description changed: - This bug is filed against the latest systemd (217-1ubuntu1) in the Vivid - branch. + This bug is filed against the latest systemd (217-1) in the debian + sid/experimental branch. - When upgrading to this version, this is the warning message I get: + When upgrading to this version (from sid version), this is the warning message I get: Failed to try-restart systemd-resolved.service: Unit systemd-resolved.service failed to load: No such file or directory. However, the systemd (217) works itself fine with no issues, it is only this installation message the bug is about. -- 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/1397361 Title: Failed to try-restart systemd-resolved.service: Status in systemd package in Ubuntu: In Progress Status in systemd package in Debian: New Bug description: This bug is filed against the latest systemd (217-1) in the debian sid/experimental branch. When upgrading to this version (from sid version), this is the warning message I get: Failed to try-restart systemd-resolved.service: Unit systemd-resolved.service failed to load: No such file or directory. However, the systemd (217) works itself fine with no issues, it is only this installation message the bug is about. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1397361/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1397361] Re: Failed to try-restart systemd-resolved.service:
More info on my setup: I only use systemd booting with init=/lib/systemd/systemd kernel booting line. I have upstart, cgmanager and systemd-shim purged. -- 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/1397361 Title: Failed to try-restart systemd-resolved.service: Status in systemd package in Ubuntu: New Bug description: This bug is filed against the latest systemd (217-1ubuntu1) in the Vivid branch. When upgrading to this version, this is the warning message I get: Failed to try-restart systemd-resolved.service: Unit systemd-resolved.service failed to load: No such file or directory. However, the systemd (217) works itself fine with no issues, it is only this installation message the bug is about. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1397361/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
