Bug#848192: /usr/bin/dh_systemd_start: dh_systemd_start needs to start .socket before .service
Thank you. Will fix. knxd is going to be packaged soon(ish; I missed the new-packages cut-off date by less than a week). -- -- Matthias Urlichs ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#808222: /usr/bin/systemd-nspawn: systemd-nspawn --link-journal=host fails when the directoy exists
Package: systemd-container Version: 227-2 Severity: important File: /usr/bin/systemd-nspawn systemd-nspawn --link-journal=host should accept an existing directory. root@iron:~# systemctl start systemd-nspawn@foo [ everything works ] root@iron:~# systemctl stop systemd-nspawn@foo root@iron:~# systemctl status -l systemd-nspawn@foo ● systemd-nspawn@foo.service - Container foo Loaded: loaded (/lib/systemd/system/systemd-nspawn@.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/systemd-nspawn@.service.d └─smurf.conf Active: failed (Result: exit-code) since Do 2015-12-17 13:00:33 CET; 7s ago Docs: man:systemd-nspawn(1) Process: 12750 ExecStart=/usr/bin/systemd-nspawn --quiet --network-bridge=br0 --network-veth-extra=vb-%i:host443 --keep-unit --boot --link-journal=host --directory=/d/vm/%i --bind=/var/cache (code=exited, status=1/FAILURE) Main PID: 12750 (code=exited, status=1/FAILURE) Status: "Terminating..." Dez 17 13:00:33 iron systemd[1]: Starting Container foo... Dez 17 13:00:33 iron systemd-nspawn[12750]: mount(/d/vm/foo/sys/fs/selinux) failed, ignoring: No such file or directory Dez 17 13:00:33 iron systemd-nspawn[12750]: mount(/d/vm/foo/sys/fs/selinux) failed, ignoring: Invalid argument Dez 17 13:00:33 iron systemd-nspawn[12750]: /etc/localtime is not a symlink, not updating container timezone. Dez 17 13:00:33 iron systemd-nspawn[12750]: Failed to create /var/log/journal/15bfd317d6044649beb2e509acfd0cac: File exists Dez 17 13:00:33 iron systemd[1]: systemd-nspawn@foo.service: Main process exited, code=exited, status=1/FAILURE Dez 17 13:00:33 iron systemd[1]: Failed to start Container foo. Dez 17 13:00:33 iron systemd[1]: systemd-nspawn@foo.service: Unit entered failed state. Dez 17 13:00:33 iron systemd[1]: systemd-nspawn@foo.service: Failed with result 'exit-code'. root@iron:~# ls -l /var/log/journal/15bfd317d6044649beb2e509acfd0cac total 8192 -rw-r-+ 1 root netdev 8388608 Jan 18 2015 system.journal root@iron:~# rm -r /var/log/journal/15bfd317d6044649beb2e509acfd0cac root@iron:~# systemctl start systemd-nspawn@foo [ everything works ] root@iron:~# -- System Information: Debian Release: 8.2 APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (550, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd-container depends on: ii libblkid12.25.2-6 ii libbz2-1.0 1.0.6-7+b3 ii libc62.19-18+deb8u1 ii libcap2 1:2.24-8 ii libcurl3-gnutls 7.45.0-1+b1 ii libgcrypt20 1.6.3-2 ii liblzma5 5.1.1alpha+20120614-2+b3 ii libseccomp2 2.1.1-1 ii libselinux1 2.3-2 ii systemd 227-2 ii zlib1g 1:1.2.8.dfsg-2+b1 systemd-container recommends no packages. systemd-container suggests no packages. -- no debconf information ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#808222: /usr/bin/systemd-nspawn: systemd-nspawn --link-journal=host fails when the directoy exists
On 17.12.2015 14:59, Michael Biebl wrote: > Control: severity -1 normal > Control: tags -1 upstream > > Hi > > Am 17.12.2015 um 13:06 schrieb Matthias Urlichs: >> Package: systemd-container >> Version: 227-2 >> Severity: important >> File: /usr/bin/systemd-nspawn >> >> systemd-nspawn --link-journal=host should accept an existing directory. >> > Please test with the latest version 228-2 Actually this is from 228-2, I simply forgot to update the header. > and if the problem still > persists, file the bug upstream at > https://github.com/systemd/systemd/issues > > OK, will do. -- -- Matthias Urlichs ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#808222: Upstream bug
https://github.com/systemd/systemd/issues/2186 -- -- Matthias Urlichs ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#799549: systemd: Provide system-log-daemon
Package: systemd Version: 224-1 Severity: normal Some packages depend on or recommend e.g. "rsyslogd | system-log-daemon". systemd provides a log daemon (the journal) and already intercepts all syslog requests, so IMHO adding a "Provides: system-log-daemon" makes sense. -- System Information: Debian Release: 8.1 APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (550, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii adduser 3.113+nmu3 ii libacl1 2.2.52-2 ii libapparmor12.9.2-3 ii libaudit1 1:2.4-1+b1 ii libblkid1 2.25.2-6 ii libc6 2.19-18 ii libcap2 1:2.24-8 ii libcap2-bin 1:2.24-8 ii libcryptsetup4 2:1.6.6-5 ii libgcrypt20 1.6.3-2 ii libkmod218-3 ii liblzma55.1.1alpha+20120614-2+b3 ii libmount1 2.25.2-6 ii libpam0g1.1.8-3.1 ii libseccomp2 2.1.1-1 ii libselinux1 2.3-2 ii libsystemd0 224-1 ii mount 2.25.2-6 ii sysv-rc 2.88dsf-59 ii udev224-1 ii util-linux 2.26.2-9 Versions of packages systemd recommends: ii dbus1.8.18-0+deb8u1 ii libpam-systemd 224-1 Versions of packages systemd suggests: pn systemd-ui -- no debconf information ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#799549: systemd: Provide system-log-daemon
On 20.09.2015 17:23, Martin Pitt wrote: > But this also interacts with systemd-journal-remote, as > installing this will currently (unintentionally) auto-enable > persistent journal, doesn't it? Why should installing systemd-journal-remote enable persistent logging? It doesn't touch journald.conf and doesn't create that directory. -- -- Matthias Urlichs signature.asc Description: OpenPGP digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#799549: systemd: Provide system-log-daemon
On 20.09.2015 17:09, Michael Biebl wrote: > I'm actually not sure if we should do that just yet. > Keep in mind that we don't enable persistent logging in journald. > One idea, that's coming from openSUSE, is a basically empty package > which ships /var/log/journal, thus enabled persistent logging and this > package would provide system-log-daemon. I like this solution in general, but it'd still annoy me. IMHO it should be the system admin's decision whether to enable persistent logging, either by creating that directory or by installing some syslog daemon or by starting a journal forwarder. My problem case is nullmailer, which Recommends: rsyslogd|system-log-daemon. It certainly makes sense to log emailer errors, but this was a bunch of Raspberry Pi computers with verbose logging-to-memory turned on – installing nullmailer turned this into a bunch of small computers logging copiously to µSD cards. I lost two of them before I realized what's going on. :-/ Installing an emailer should not result in something like that. -- -- Matthias Urlichs signature.asc Description: OpenPGP digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Re: Proposal: enable stateless persistant network interface names
Hi, Karsten Merker: while this probably works resonably well for (semi-)fixed devices like onboard-NICs and PCI/PCIe cards, it results in a completely unsuitable behaviour with pluggable devices such as USB network adapters. Why? I can envision two likely scenarios for using a USB adapter. (a) you need to test something, so you plug in a handy USB adapter and configure it statically. So you're root and mucking about in /etc anyway, so also adding a one-liner to /etc/udev/rules.d/70-persistent-net.rules which names the adapter statically should not be a problem. (b) you're a client (e.g. you configure a new router), likely to use NetworkManager to just run a dhcp client on the adapter or configure a one-off RFC1918 address. So what if the adapter gets a different name next time? Most likely you need to configure a different device in a different '1918 subnet anyway. Or, if you use DHCP, there's no difference either way. In all other situations, quickly configuring a static address is no problem IMHO. Despite the problems of the MAC-based system that we use currently, the ifnames method appears way worse to me than what we have now. On a server, a missed rename due to interfaces showing up in exactly the wrong order makes the system unreachable. Frankly, I cannot imagine anything way worse than that. Not in this context. -- -- Matthias Urlichs signature.asc Description: Digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#742802: Bug#771523: systemd: Add build dependency for libmicrohttpd-dev
On 29.03.2015 05:13, Marco d'Itri wrote: It would surely be beneficial if the users arguing for support of this feature could document its popularity. Data point: I use this feature (via my own systemd packages) for all my Raspberry Pi and similar computers. They don't have enough RAM to store meaningful logs, and logging to SD cards is not a good long-term strategy for controllers built into walls and utility closets. -- -- Matthias Urlichs signature.asc Description: OpenPGP digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#771523: systemd: Add build dependency for libmicrohttpd-dev
Package: systemd Version: 215-7 Severity: normal Forwarding journal entries to another system is an important feature; doing that via rsyslog loses information. Unfortunately, the current Debian package does not build the program to receive journal log entries. Therefore, please add a build dependency on libmicrohttpd-dev so that systemd-journal-remote gets built. Thank you. -- -- Matthias Urlichs ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#753589: systemd: Missing dependency on glibc?
Package: systemd Version: 208-5 Severity: normal While updating, systemd was updated before glibc. Needless to say, this does not work at all. # aptitude(wd: ~) Reading changelogs... apt-listchanges: Mailing smurf-chan...@smurf.noris.de: apt-listchanges: news for eltern Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 59720 files and directories currently installed.) Removing homevent ... Stopping homevent: Removing python-twisted-conch ... Removing python-twisted-core ... Removing python-zope.interface ... Removing python-pkg-resources ... Removing debconf-i18n ... Removing fuse-utils ... Processing triggers for man-db ... (Reading database ... 57308 files and directories currently installed.) Preparing to replace systemd-sysv 44-11+deb7u4 (using .../systemd-sysv_208-5_i386.deb) ... Unpacking replacement systemd-sysv ... Preparing to replace libtirpc1:i386 0.2.2-5 (using .../libtirpc1_0.2.3-1_i386.deb) ... Unpacking replacement libtirpc1:i386 ... Preparing to replace libgcrypt11:i386 1.5.0-5+deb7u1 (using .../libgcrypt11_1.5.3-4_i386.deb) ... Unpacking replacement libgcrypt11:i386 ... Preparing to replace libsystemd-daemon0:i386 204-8 (using .../libsystemd-daemon0_208-5_i386.deb) ... Unpacking replacement libsystemd-daemon0:i386 ... Preparing to replace libsystemd-journal0:i386 44-11+deb7u4 (using .../libsystemd-journal0_208-5_i386.deb) ... Unpacking replacement libsystemd-journal0:i386 ... Selecting previously unselected package libudev1:i386. Unpacking libudev1:i386 (from .../libudev1_204-8_i386.deb) ... Preparing to replace libsystemd-login0:i386 44-11+deb7u4 (using .../libsystemd-login0_208-5_i386.deb) ... Unpacking replacement libsystemd-login0:i386 ... Selecting previously unselected package acl. Unpacking acl (from .../archives/acl_2.2.52-1_i386.deb) ... Preparing to replace libpam-systemd:i386 44-11+deb7u4 (using .../libpam-systemd_208-5_i386.deb) ... Unpacking replacement libpam-systemd:i386 ... Preparing to replace systemd 44-11+deb7u4 (using .../systemd_208-5_i386.deb) ... Moving obsolete conffile /etc/bash_completion.d/systemd-bash-completion.sh out of the way... Unpacking replacement systemd ... Processing triggers for man-db ... (Reading database ... 57471 files and directories currently installed.) Removing libaudit0 ... Selecting previously unselected package libaudit-common. (Reading database ... 57465 files and directories currently installed.) Unpacking libaudit-common (from .../libaudit-common_1%3a2.3.7-1_all.deb) ... Selecting previously unselected package libaudit1:i386. Unpacking libaudit1:i386 (from .../libaudit1_1%3a2.3.7-1_i386.deb) ... Preparing to replace nscd 2.13-38+deb7u1 (using .../archives/nscd_2.19-4_i386.deb) ... /sbin/runlevel: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.17' not found (required by /sbin/runlevel) /sbin/runlevel: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.14' not found (required by /sbin/runlevel) /sbin/runlevel: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.15' not found (required by /lib/i386-linux-gnu/libgcrypt.so.11) -- System Information: Debian Release: 7.5 APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (550, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.6-trunk-486 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-1 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-41+deb7u1 ii libacl1 2.2.52-1 ii libaudit11:2.3.7-1 ii libblkid12.20.1-5.3 ii libc62.19-4 ii libcap2 1:2.22-1.2 ii libcap2-bin 1:2.22-1.2 ii libcryptsetup4 2:1.4.3-4 ii libdbus-1-3 1.6.8-1+deb7u1 iu libgcrypt11 1.5.3-4 ii libkmod2 9-3 ii liblzma5 5.1.1alpha+20120614-2 ii libpam0g 1.1.3-9 ii libselinux1 2.1.9-5 ii libsystemd-daemon0 208-5 iu libsystemd-journal0 208-5 ii libsystemd-login0208-5 iu libudev1 204-8 ii libwrap0 7.6.q-24 ii sysv-rc 2.88dsf-41+deb7u1 ii udev 175-7.2 ii util-linux 2.20.1-5.3 Versions of packages systemd recommends: iu libpam-systemd 208-5 Versions of packages systemd suggests: pn systemd-ui none -- Configuration Files: /etc/dbus-1/system.d/org.freedesktop.machine1.conf [Errno 2] No such file or directory: u'/etc/dbus-1/system.d/org.freedesktop.machine1.conf' /etc/pam.d/systemd-user [Errno 2] No such file or directory: u'/etc/pam.d/systemd-user' /etc/systemd/bootchart.conf [Errno 2] No such file or directory: u'/etc/systemd/bootchart.conf' /etc/systemd/journald.conf [Errno 2] No such file or directory: u'/etc/systemd/journald.conf' /etc/systemd/logind.conf [Errno 2] No such file or directory: u'/etc/systemd/logind.conf'
