Re: Adding systemd unit files in OpenStack packages

Hi, I'm mostly a systemd user myself, but have read through a reasonable part of the documentation. So hopefully I can answer some of your questions. On 07/06/2014 15:33, Thomas Goirand wrote: Let's take an example with keystone. Currently, there's the following init.d sysv-rc script LSB

Comments regarding libsystemd-dummy_208-1_kfreebsd-amd64.changes

Hi, src/sd-shutdown.h is licensed under LGPL-2.1+. Please include that information in d/copyright. I think it would also be good if there was an explicit license for the Debian packaging. Ansgar ___ Pkg-systemd-maintainers mailing list

Bug#755968: libpam-systemd: should depend on dbus

Package: libpam-systemd Version: 208-6 Severity: normal libpam-systemd has a dependency on systemd-sysv (or systemd-shim) to ensure logind is available, but it has no dependency on dbus. However if dbus is not installed, it cannot talk to logind... systemd itself should probably also recommend

Bug#758111: [Pkg-utopia-maintainers] installation-reports: Please consider dbus for the core files

On 08/20/2014 10:12, Simon McVittie wrote: On Thu, 14 Aug 2014 at 13:24:34 +0200, Michael Biebl wrote: Two possible outcomes then 1/ Make systemd recommend/depend on dbus (recommend would probably be sufficient) According to the initial bug report, the base system is installed without

Bug#759293: override: dbus:admin/important or :admin/standard

Package: ftp.debian.org X-Debbugs-Cc: syst...@packages.debian.org, d...@packages.debian.org Please increase the priority of dbus to important or standard (not sure which): it is needed by systemd-logind. If dbus is not available, systems running systemd will not spawn gettys on tty2-6 by default.

Bug#759689: systemd: ProtectSystem= should cover /bin, /sbin, /lib on Debian

. Otherwise ProtectSystem=full is broken (and treated as ProtectSystem=false). Ansgar From: Ansgar Burchardt ans...@debian.org Date: Thu, 24 Jul 2014 19:38:07 +0200 Subject: Include additional directories in ProtectSystem --- a/src/core/namespace.c +++ b/src/core/namespace.c @@ -371,7 +371,7

Re: Bug#761389: breaks shutdown when switching from systemd-sysv to sysvinit-core

Michael Biebl bi...@debian.org writes: Am 13.09.2014 um 15:53 schrieb Michael Biebl: Looking at v215, it seems as if starting cgmanager as part of the installation messes up the running systemd state. When triggering reboot, (i.e. poking /dev/initctl), I get the following: Actually this

Bug#762041: systemd: upgrading systemd results in /run/user/uid being emptied

Michael Biebl bi...@debian.org writes: Am 18.09.2014 um 21:22 schrieb Sven Joachim: This is exactly what I observe: before the upgrade /run/user was mounted on a tmpfs, after the upgrade another tmpfs appeared mounted on /run/user/1000, shadowing the files on /run/user. Unmounting that new

Bug#764628: systemd isn't selected for upgrade

Hi, Sebastian Oswald sebast...@rostwald.de writes: When trying to upgrade systemd-packages from 208-8 systemd isn't selected for upgrade, resulting in KDE and X11 to be removed: Did you pin any packages? Please check /etc/apt/preferences and /etc/apt/preferences.d/*. Ansgar

Bug#764697: systemd: enable ipv6 by default at least for lo

Hi, On 10/10/2014 12:58, Gert Wollny wrote: currently in /etc/sysctl.d/99-sysctl.conf provided by the systemd package ipv6 seems to be disabled by default i.e. That is just a symlink to ../sysctl.conf; /etc/sysctl.conf is provided by procps. net.ipv6.conf.all.disable_ipv6 = 1

Bug#765175: systemd init script integration: status action should use --lines=0

Package: systemd Version: 215-5+b1 Priority: wishlist Hi, as discussed with Michael Biebl on IRC this morning, please consider changing the init script integration: the status action should pass --lines=0 to systemctl, i.e. /etc/init.d/${x} status should call systemctl --lines=0 status ${x}.

Bug#765181: sysvinit: (invoke-rc.d|service) status should pass --lines=0 to systemctl

Package: sysv-rc Version: 2.88dsf-53.3 Priority: wishlist X-Debbugs-Cc: pkg-systemd-maintainers@lists.alioth.debian.org Hi, as discussed with Michael Biebl on IRC this morning, please consider changing how invoke-rc.d forwards commands to systemctl: the status action should pass --lines=0, i.e.

Bug#769794: override: dbus:admin/important

Package: ftp.debian.org Severity: normal Please raise the priority of dbus a bit further, from standard to important. It turns out that there are several issues with not having dbus around, stemming from systemd-logind not being available. Among these are: - No TTYs on VT 2-6. - No handling of

Bug#776912: debootstrap circular depends/pre-depends between sytemd-sysv and systemd

Control: retitle -1 systemd: missing /dev/urandom makes postinst fail Hi, On 02/03/2015 11:59 AM, Ansgar Burchardt wrote: On 02/03/2015 11:22 AM, Martin Wuertele wrote: Setting up systemd (215-10) ... Failed to open /dev/urandom: Function not implemented dpkg: error processing package

Bug#776912: debootstrap circular depends/pre-depends between sytemd-sysv and systemd

Hi Marin, please remember to also send replies to the bug report (I've not forwarded your message). The debootstrap log looks a bit more scary than I think it should, but I'll take a look at only the systemd error: On 02/03/2015 11:22 AM, Martin Wuertele wrote: Setting up systemd (215-10) ...

Bug#776912: debootstrap circular depends/pre-depends between sytemd-sysv and systemd

Hi, On 02/03/2015 10:39 AM, Martin Wuertele wrote: When trying to debootstrap jessie on an RHEL7 / CENTOS7 (system is running systemd 208 Release 11.el7_0.6) system for usage with lxc or docker debootstrap fails due to systemd and systemd-sys: dpkh: systemd-sysv: dependency problems, but

Bug#759001: [systemd-devel] sysv-generator: doesn't handle /etc/insserv/overrides or /etc/chkconfig.d

Hi, Christian Seiler christ...@iwakd.de writes: I've implemented both of these and attached a modified version of the patch. Do you have any objections? If not, I'll ask for pre- approval by the release team. The load_sysv function also has a heuristic to guess whether the init script support

Bug#778620: systemd: Add less to suggests or recommends

Hi, On 02/18/2015 11:03 AM, Floris wrote: I have installed the Debian Base system and add gnome-session, gdm, xserver-xorg-video-nvidia and probably some other packages to get a working gnome environment. Maybe coincidental, but none of these packages recommends less. Only man-db and gzip

Re: Bug#742802: Bug#771523: systemd: Add build dependency for libmicrohttpd-dev

Hi, On 03/30/2015 12:29 PM, Martin Pitt wrote: Hence the idea of systemd-extras -- everything which brings in large dependencies and isn't needed for booting every system can go there. systemd would Recommends: systemd-extras, but admins of embedded machines etc. could remove/not install it.

Re: Bug#152955: force-reload should not start the daemon if it is not running

Control: block 782993 by 152955 Hi, the meaning of the force-reload action comes up again with systemd: - systemctl implements force-reload as documented by LSB, that is a service not running does *not* get started, - the init script integration maps /etc/init.d/X force-reload to

Bug#796389: systemd should depend on a newer version of mount

Package: systemd Version: 224-1 Severity: minor systemd seems to need a newer version of mount that it currently depends on: Aug 14 10:39:24 xyz swapon[457]: /sbin/swapon: invalid option -- 'o' The fstab entry in question is /dev/mapper/xyz-swap none swap sw 0 0 Ansgar -- System

Re: Preparing a stable release for the upcoming 8.2

Michael Biebl bi...@debian.org writes: we currently have one commit in our jessie branch [1] and the jessie point release 8.2 is about one month away. Or in two weeks based on the current responses[2] which would mean a p-u freeze next weekend. Ansgar [1]

Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards

Axel Beckert a...@debian.org writes: Michael Biebl wrote: Am 30.06.2015 um 17:52 schrieb Klaus Ethgen: # CONFIG_FHANDLE is not set E.g. that one is missing. If you compile your own kernel, you should make sure all requirements listed at [1] are met. I didn't check all other options, but

Bug#790560: udev fails to start on sparc boot, breaking boot

Michael Biebl bi...@debian.org writes: If 215-8 was working successfully, finding the faulty commit would indeed be very helpful. If you know how to use git bisect, you could use that to determine the commit. This will be a lengthy process though and probably not something you want to do on a

Bug#793374: [PATCH] Copy *.link files from /etc/systemd/network to initramfs

Julian Wollrath jwollr...@web.de writes: Am Sat, 25 Jul 2015 12:24:02 +0200 schrieb martin f krafft madd...@debian.org: You could also just use find /etc/systemd/network --name \*.link --exec cp -pt $DESTDIR/lib/systemd/network/ {} + But that would assume, that findutils is installed.

Re: nbd-client and systemd

On 07/15/2015 09:34 AM, Wouter Verhelst wrote: However, recently I found out about the systemd-no-service-for-init-rcS-script lintian error, which triggers for nbd-client. I'm afraid that if I create such a unit generator, this would still trigger. Is that correct? If so, is there another

Bug#805344: systemd: ListenStream=6566 in saned.socket only causes systemd to listen on [::]:6566

Jens Georg writes: > I was trying to run sane network scanning through socket activation, but > with the provided saned.socket file systemd only listens on a v6 socket. > I have to explicitly change ListenStream to 0.0.0.0:6656 to make it > listen on v4. Did you check if

Comments regarding kdbus-dkms_0.20150824t110616.0c05fbd-1_amd64.changes

Hi, you mention Copyright (c) 2006, 2008 Junio C Hamano in d/copyright, but he doesn't seem to be mentioned anywhere? Anyway, this is a minor thing and the package is fine otherwise. Ansgar ___ Pkg-systemd-maintainers mailing list

Bug#799549: systemd: Provide system-log-daemon

Josh Triplett writes: > I'd actually suggest *two* tiny packages: a systemd-journal-persistent > package that ships /var/log/journal and provides/conflicts > system-log-daemon, and a systemd-journal-transient package that > pointedly doesn't ship /var/log/journal (or in the

Bug#806787: systemd-container: machines.target not enabled by default

Michael Biebl <bi...@debian.org> writes: > On Tue, 01 Dec 2015 12:32:06 +0100 Ansgar Burchardt <ans...@debian.org> > wrote: >> machines.target is not enabled by default. This means machines >> configured to start at boot with "machinectl enable " will >&

Bug#806787: systemd-container: machines.target not enabled by default

Package: systemd-container Version: 228-2 Severity: normal Hi, machines.target is not enabled by default. This means machines configured to start at boot with "machinectl enable " will actually not start unless one also enables machines.target manually. Ansgar -- System Information: Debian

Re: iptables split

On Thu, 2016-06-09 at 13:08 +0200, Michael Biebl wrote: > Am 09.06.2016 um 12:40 schrieb Ansgar Burchardt: > > I wonder if it would make sense to keep the three libraries in one > > package then?  All of them would be usually installed anyway should > > systemd depend on them

Re: iptables split

On Thu, 2016-06-09 at 03:17 +0200, Michael Biebl wrote: > One more comment: > > $ du -hs debian/libip*tc0/usr/* > 36K debian/libip4tc0/usr/lib > 88K debian/libip4tc0/usr/share > 40K debian/libip6tc0/usr/lib > 88K debian/libip6tc0/usr/share > 16K debian/libiptc0/usr/lib > 88K

Bug#812970: init-system-helpers and file-rc: error when trying to install together

Control: reassign -1 file-rc/0.8.17,sysv-rc/2.88dsf-59.3 Control: retitle -1 sysv-rc and file-rc: error when trying to install together Ralf Treinen writes: > Package: file-rc,init-system-helpers This is actually a conflict between file-rc and sysv-rc. The one between file-rc

Bug#813372: systemd: does not boot

On Mon, 2016-02-01 at 14:06 +0100, Martin Pitt wrote: > This is the culprit: > > Feb 01 13:18:41 chromebook systemd[1]: dev-mmcblk1p5.mount: Mount > process exited, code=exited status=32 > Feb 01 13:18:41 chromebook systemd[1]: Failed to mount > /dev/mmcblk1p5. > > Your fstab has > >   /

Bug#814758: Case power button is ignored unless dbus is installed.

Josh Triplett writes: > If systemd-logind just needs dbus to check for possible inhibitors, > could systemd-logind simply ignore inhibitors without dbus? systemd-logind failed to start if dbus isn't available (#772700). That's why

Bug#756023: init: Move "Essential: yes" from init to init-system-helpers

On Thu, 2016-05-19 at 18:27 +0200, Michael Biebl wrote: > Could we add the Important: yes field to "init"? Having that makes a > lot of sense to me. To init or to its dependencies (systemd-sysv, sysvinit-core)?  The latter would not only warn when uninstalling all init systems, but also when

Bug#824991: override: init:metapackages/important

Package: ftp.debian.org Severity: normal As discussed in [1] I would like to make it possible for minimal systems (mostly buildd chroots and application containers like Docker) to not have to install an init system. For this the "Essential: yes" field is moved from "init" to

Bug#756023: init: Move "Essential: yes" from init to init-system-helpers

Control: retitle -1 init: Move "Essential: yes" from init to init-system-helpers Control: tag -1 - patch Control: forcemerge -1 823501 I would like "init" to be optional in Debian 9 for chroot environments and some uses of containers. A first step seems to be making "init" no longer essential;

Bug#823501: init: move "Essential: yes" from init to init-system-helpers

Package: init Version: ___ 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#756023: init: Move "Essential: yes" from init to init-system-helpers

Felipe Sateler writes: > On 5 May 2016 at 10:05, Ansgar Burchardt <ans...@debian.org> wrote: >> As maintainer scripts call `invoke-rc.d` and `update-rc.d` >> unconditionally, the package providing these scripts should be made >> essential (i.e. add "Essent

Bug#830575: nspawn lacks a dependency on dbus

On Mon, 2016-07-11 at 14:18 +0200, Michael Biebl wrote: > Am 09.07.2016 um 18:33 schrieb Jan Engelhardt: > > Package: systemd-container > > Version: 230-5 > > > > nspawn fails to start the selected program. It appears to need > > dbus, and Debian > > is missing a Requires:. System has version

Bug#843809: check that executables don't link to libraries in /usr is broken wrt libsystemd-shared

Michael Biebl writes: > But now we have a different issue, ldd thinks, that liblz4 is in /lib.: [...] > This is because of merged-usr. This more or less renders the whole check > useless once we build in a chroot which has been created with > debootstrap --merged-usr > > Dunno, maybe we should

Bug#851400: systemd: Going into suspend yust after waking up

Michael Fritscher writes: > The problem is that if the system is on battery both on going to > suspend and waking up, in 90% of the cases the system goes into > suspend immediately again (few seconds). On the second try it works. > I didn't set the system to go into suspend after some time... Do

Re: piuparts.debian.org: jessie2bpo has >400 packages in dependency-failed-testing status

On Tue, 2017-03-21 at 16:45 +, Holger Levsen wrote: > On Sun, Mar 19, 2017 at 05:31:16PM +0100, Michael Biebl wrote: > > both systemd and udev need to be upgraded in lockstep: > > > > a/ udev has Breaks/Replaces systemd (<< 224-2) > > b/ systemd has a Breaks/Replaces udev (<< 228-5) > > > >

Re: resolv.conf missing?

Hi, Paul Zeiger writes: > I am currently setting up a web server and I want the network to be > managed by systemd's networkd and name resolution to be performed by > resolved. However the file > > /usr/lib/systemd/resolv.conf > > is missing and it should be provided by the package according to

Bug#865536: systemd-sysv: Causes kernel panic if /usr isn't mounted due to liblz4.so being in /usr/lib

On Thu, 2017-06-22 at 07:56 -0500, John Goerzen wrote: > After the upgrade to stretch, my kernel paniced on boot.  I > eventually tracked the problem down to /usr not yet being mounted, > and /sbin/init needing liblz4.so which was in /usr. The /usr filesystem must be mounted by the initramfs (if