This bug was fixed in the package systemd - 229-4ubuntu19
---
systemd (229-4ubuntu19) xenial; urgency=medium
* debian/extra/units/systemd-resolved.service.d/resolvconf.conf: partially
revert, by removing ExecStart|StopPost lines, as these are not needed on
xenial and generat
Starting with systemd 229-4ubuntu17.
Observed:
Jul 19 13:26:15 key-giraffe systemd[1]: Reached target Network is Online.
Jul 19 13:26:15 key-giraffe systemd[1]: Starting Network Name Resolution...
Upgraded to systemd 229-4ubuntu19
Observed:
Jul 19 13:32:58 key-giraffe systemd[1]: Started Network
Hello Ryan, or anyone else affected,
Accepted systemd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu19
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki
systemd (229-4ubuntu19) xenial; urgency=medium
* debian/extra/units/systemd-resolved.service.d/resolvconf.conf: partially
revert, by removing ExecStart|StopPost lines, as these are not needed on
xenial and generate warnings in the journal. (LP: #1704677)
systemd (229-4ubuntu18) xenial;
Since resolved is not enabled by default in xenial, I'm doing a slightly
modified testcase of enabling resolved first, reboot, upgrade to new
systemd, reboot again, check the results after every reboot.
Package versions from the upgrade log: Unpacking systemd (229-4ubuntu18)
over (229-4ubuntu17)
Hello Ryan, or anyone else affected,
Accepted systemd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu18
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki
** Changed in: systemd (Ubuntu Xenial)
Milestone: None => ubuntu-16.04.3
--
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/1673860
Title:
systemd-resolved unit should run
This bug was fixed in the package systemd - 231-9ubuntu4
---
systemd (231-9ubuntu4) yakkety; urgency=medium
* debian/extra/units/systemd-resolved.service.d/resolvconf.conf: if
resolved is going to be started, make sure this blocks
network-online.target. LP: #1673860.
* de
Confirmed this fix in yakkety. Behavior with systemd 231-9ubuntu3:
# journalctl -o short-precise -u systemd-resolved -u network-online.target
--no-pager
-- Logs begin at Thu 2017-04-20 23:50:20 UTC, end at Fri 2017-04-21 03:22:45 UTC
Apr 20 23:51:06.897218 ubuntu systemd[1]: Starting Network Nam
** Changed in: systemd (Ubuntu Xenial)
Status: New => Triaged
--
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/1673860
Title:
systemd-resolved unit should run Before=
Hello Ryan, or anyone else affected,
Accepted systemd into yakkety-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/systemd/231-9ubuntu4 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki
This bug was fixed in the package systemd - 232-21ubuntu2
---
systemd (232-21ubuntu2) zesty; urgency=medium
* pkgconfig: Cherrypick upstream fix to libdir locations in .pc files
(LP: #1674201)
-- Dimitri John Ledkov Tue, 28 Mar 2017 16:59:14
+0100
** Changed in: systemd (Ub
I just tested the zesty-proposed version and it works as expected.
% lxc launch ubuntu-daily:zesty z1
Creating z1
Starting z1
# confirm current version of systemd
% lxc exec z1 -- apt-cache policy systemd
systemd:
Installed: 232-19
Candidate: 232-19
Version table:
*** 232-19 500
The zesty systemd upload with this fix is still in zesty-proposed,
please make sure to carry it through. The yakkety systemd SRU that
includes this fix as part of its changes cannot be approved before
232-21ubuntu1 migrates to the release pocket.
--
You received this bug notification because you
** Description changed:
+ === Begin SRU Template ===
+ [Impact]
+
+ For releases using systemd-resolved (yakkety and zesty); the unit
+ configuration does not require that the service be active before
+ allowing systemd to reach 'network-online.target' which is a special
+ target used to allow ot
Working it now, sorry for the delay
On Thu, Mar 23, 2017 at 1:07 PM, Brian Murray wrote:
> Missing SRU information regarding Impact, Test Case, Regression
> Potential.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/16
Missing SRU information regarding Impact, Test Case, Regression
Potential.
--
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/1673860
Title:
systemd-resolved unit should run B
** Changed in: systemd (Ubuntu)
Status: New => Fix Committed
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Steve Langasek (vorlon)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
htt
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Yakkety)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to system
Related history in LP: #1649931
--
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/1673860
Title:
systemd-resolved unit should run Before=network-online.target
Status in syst
20 matches
Mail list logo