Your message dated Tue, 16 Jun 2015 15:11:29 +0200
with message-id <[email protected]>
and subject line Re: Bug#761951: systemd: Did not start network in default
has caused the Debian Bug report #761951,
regarding systemd: networking service not started due to dependency cycle
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
761951: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761951
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 215-4
Severity: normal
Dear Maintainer,
When update to version 215 from version 208, not starting network at default.
Networks are defined by /etc/network/interfaces, not NetworkManagedr.
Workaround is re-defining network(s) to /etc/systemd/network/foo , and
enable systemd-network.service by hand.
Regards,
K.Ohta.
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- Package-specific info:
-- System Information:
Debian Release: jessie/sid
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'unstable'), (500, 'stable'),
(500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to ja_JP.UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages systemd depends on:
ii acl 2.2.52-2
ii adduser 3.113+nmu3
ii initscripts 2.88dsf-53.4
ii libacl1 2.2.52-2
ii libaudit1 1:2.4-1
ii libblkid1 2.20.1-5.8
ii libc6 2.19-11
ii libcap2 1:2.24-4
ii libcap2-bin 1:2.24-4
ii libcryptsetup4 2:1.6.6-1
ii libgcrypt11 1.5.4-3
ii libkmod2 18-1
ii liblzma5 5.1.1alpha+20120614-2
ii libpam0g 1.1.8-3.1
ii libselinux1 2.3-2
ii libsystemd0 215-4
ii sysv-rc 2.88dsf-53.4
ii udev 215-4
ii util-linux 2.20.1-5.8
Versions of packages systemd recommends:
ii dbus 1.8.6-2
ii libpam-systemd 215-4
Versions of packages systemd suggests:
ii systemd-ui 3-2
-- Configuration Files:
/etc/systemd/logind.conf changed [not included]
/etc/systemd/system.conf changed [not included]
-- no debconf information
--- End Message ---
--- Begin Message ---
Control: reassign -1 setserial
Control: forcemerge 786976 -1
Martin Pitt [2015-01-26 12:28 +0100]:
> As Michael pointed out in his previous comment, Simon's debug output
> very much looked like https://bugs.debian.org/771118 which is fixed in
> unstable and testing now. Do you still have this problem with the
> current versions?
It might have been that bug. But presumably it is due to
https://bugs.debian.org/786976 (the above report showed that setserial
caused the cycle), so duplicating to that.
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
