Processed: Re: Bug#805910: FTBFS on x32: wrong assumption about sizeof(long)

Processing control commands: > forwarded -1 https://github.com/systemd/systemd/pull/2013 Bug #805910 [src:systemd] FTBFS on x32: wrong assumption about sizeof(long) Changed Bug forwarded-to-address to 'https://github.com/systemd/systemd/pull/2013' from 'http://lists.freedesktop.org/archives/syst

Bug#805910: FTBFS on x32: wrong assumption about sizeof(long)

Control: forwarded -1 https://github.com/systemd/systemd/pull/2013 Hello Helmut, Helmut Grohne [2015-11-23 22:25 +0100]: > The reason is a wrong assumption on the sizeof(long). I forwarded the > fix upstream already (see above). Can you cherry pick from > git://git.subdivi.de/~helmut/systemd.git

Bug#805927: timesyncd does not automatically start after removing all NTP daemons

Package: systemd Version: 228-2 Severity: wishlist /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf disables systemd-timesyncd if /usr/sbin/ntpd (or another NTP daemon) exists. However, nothing causes systemd-timesyncd to automatically start running after removing the

Processed: tagging 787758, tagging 802897, tagging 759319, tagging 793477, tagging 797894

Processing commands for cont...@bugs.debian.org: > tags 787758 + pending Bug #787758 [systemd] 'Failed at step NAMESPACE spawning' when using ReadOnlyDirectories in multi-instance service file Added tag(s) pending. > tags 802897 + pending Bug #802897 [systemd] systemd: Opening an encrypted device

Bug#805910: FTBFS on x32: wrong assumption about sizeof(long)

Source: systemd Version: 228-1 Tags: patch upstream User: helm...@debian.org Usertags: rebootstrap Forwarded: http://lists.freedesktop.org/archives/systemd-devel/2015-November/035105.html Hi systemd maintainers, Since 228, systemd FTBFS on x32. See https://buildd.debian.org/status/fetch.php?pkg=

Bug#805821: systemd does not see existing dmraid volumes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 > Could you send us a "udevadm info" dump for those devices. root@nyws:~# udevadm info /dev/mapper/jmicron_Main P: /devices/virtual/block/dm-0 N: dm-0 S: disk/by-id/dm-name-jmicron_Main S: disk/by-id/dm-uuid-DMRAID-jmicron_Main E: DEVLINKS=/dev/disk

Processed: Re: Bug#805785: systemd-container: machinectl start #containername# fails when /var/lib/machines/#containername# is symlink to other folder

Processing control commands: > forwarded -1 https://github.com/systemd/systemd/issues/2001 Bug #805785 [systemd-container] systemd-container: machinectl start #containername# fails when /var/lib/machines/#containername# is symlink to other folder Set Bug forwarded-to-address to 'https://github.

Bug#805785: systemd-container: machinectl start #containername# fails when /var/lib/machines/#containername# is symlink to other folder

Control: forwarded -1 https://github.com/systemd/systemd/issues/2001 Control: severity -1 normal Am 22.11.2015 um 14:20 schrieb Denys: > Package: systemd-container > Version: 228-2 > Severity: important > > Dear Maintainer, > > machinectl start #containername# fails when /var/lib/machines/#conta

Bug#805821: systemd does not see existing dmraid volumes

Am 22.11.2015 um 21:13 schrieb Nikita Youshchenko: > System uses fakeraid (configured in BIOS) - two disks in a mirror. > In linux it is enabled via dmraid. > Partitions are visible as /dev/mapper/jmicron_Main[1-4]. > > /dev/mapper/jmicron_Main2 is used for swap > /dev/mapper/jmicron_Main3 is use

Bug#805878: dh-systemd: dh_systemd_start --no-start --restart-after-upgrade causes the service to be started on install

Package: dh-systemd Version: 1.24 Severity: normal Current autoscript has: if [ -d /run/systemd/system ]; then systemctl --system daemon-reload >/dev/null || true if [ -n "$2" : ]; then _dh_action=try-restart else _dh_action=start fi