Bug#879191: /usr/lib/modprobe.d/systemd.conf ignored, should be in /lib/modprobe.d

2017-10-20 Thread Marc Haber
Package: systemd Version: 235-2 Severity: normal Hi, /usr/lib/modprobe.d/systemd.conf gets ignored, at least on non-usrmerged systems. The file should be in /lib/modprobe.d, where already other files are placed. Moving the file gets it honored. Greeetings Marc -- Package-specific info: -- Sys

Bug#879191: /usr/lib/modprobe.d/systemd.conf ignored, should be in /lib/modprobe.d

2017-10-20 Thread Michael Biebl
Am 20.10.2017 um 10:38 schrieb Marc Haber: > Package: systemd > Version: 235-2 > Severity: normal > > > Hi, > > /usr/lib/modprobe.d/systemd.conf gets ignored, at least on non-usrmerged > systems. The file should be in /lib/modprobe.d, where already other > files are placed. Moving the file gets

Bug#791944: /etc/init.d/sendsigs kills systemd-udevd upon shutdown, causing dmsetup to hang

2017-10-20 Thread Pali Rohár
On Monday 12 June 2017 13:37:13 Pali Rohár wrote: > On Saturday 10 June 2017 22:44:31 Michael Biebl wrote: > > Hi > > > > Am 10.06.2017 um 21:14 schrieb Pali Rohár: > > > > > PING. Do you need to test something more? Or is that patch enough? > > > > The patch seems to contain some left-over comm

Bug#879191: /usr/lib/modprobe.d/systemd.conf ignored, should be in /lib/modprobe.d

2017-10-20 Thread Michael Biebl
Am 20.10.2017 um 12:54 schrieb Michael Biebl: > Am 20.10.2017 um 10:38 schrieb Marc Haber: >> Package: systemd >> Version: 235-2 >> Severity: normal >> >> >> Hi, >> >> /usr/lib/modprobe.d/systemd.conf gets ignored, at least on non-usrmerged >> systems. The file should be in /lib/modprobe.d, where a

Bug#879191: /usr/lib/modprobe.d/systemd.conf ignored, should be in /lib/modprobe.d

2017-10-20 Thread Marc Haber
On Fri, Oct 20, 2017 at 12:54:38PM +0200, Michael Biebl wrote: > That path is read by kmod. Given that kmod supports > /usr/lib/modules-load.d and /lib/modules-load.d/ it would imho make > sense if it also supported /usr/lib/modprobe.d besides /lib/modprobe.d Should it be decided that /usr/lib/mod

Bug#879191: /usr/lib/modprobe.d/systemd.conf ignored, should be in /lib/modprobe.d

2017-10-20 Thread Michael Biebl
Am 20.10.2017 um 13:00 schrieb Marc Haber: > On Fri, Oct 20, 2017 at 12:54:38PM +0200, Michael Biebl wrote: >> That path is read by kmod. Given that kmod supports >> /usr/lib/modules-load.d and /lib/modules-load.d/ it would imho make >> sense if it also supported /usr/lib/modprobe.d besides /lib/mo

Bug#879191: /usr/lib/modprobe.d/systemd.conf ignored, should be in /lib/modprobe.d

2017-10-20 Thread Michael Biebl
Control: forwarded -1 https://github.com/systemd/systemd/pull/7149 Am 20.10.2017 um 10:38 schrieb Marc Haber: > /usr/lib/modprobe.d/systemd.conf gets ignored, at least on non-usrmerged > systems. The file should be in /lib/modprobe.d, where already other > files are placed. Moving the file gets it

Processed: Re: Bug#879191: /usr/lib/modprobe.d/systemd.conf ignored, should be in /lib/modprobe.d

2017-10-20 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/systemd/systemd/pull/7149 Bug #879191 [systemd] /usr/lib/modprobe.d/systemd.conf ignored, should be in /lib/modprobe.d Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/pull/7149'. -- 879191: https://bugs.debian.or

Bug#879216: /lib/systemd/system/systemd-resolved.service:22: Executable path is not absolute: !!/lib/systemd/systemd-resolved

2017-10-20 Thread Daniel Kahn Gillmor
Package: systemd Version: 235-2 Severity: normal Something about the service configuration for systemd-resolved doesn't match what the service manager expects. What does it mean to start an executable path with "!!" ? 0 dkg@alice:~$ systemctl status systemd-resolved ● systemd-resolved.service

Bug#878625: systemd: NIS users login takes longtime.

2017-10-20 Thread Elimar Riesebieter
Control: reassign -1 nis Control: retitle -1 "nscd should be a Depends" * Michael Biebl [2017-10-16 11:27 +0200]: > Control: forwarded -1 https://github.com/systemd/systemd/issues/7074 > > Am 15.10.2017 um 10:55 schrieb Elimar Riesebieter: > > Package: systemd > > Version: 235-2 > > Severity:

Processed: Re: Bug#878625: systemd: NIS users login takes longtime.

2017-10-20 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 nis Bug #878625 [systemd] systemd: NIS users login takes longtime. Bug reassigned from package 'systemd' to 'nis'. No longer marked as found in versions systemd/235-2. Ignoring request to alter fixed versions of bug #878625 to the same values previously

Bug#879216: marked as done (/lib/systemd/system/systemd-resolved.service:22: Executable path is not absolute: !!/lib/systemd/systemd-resolved)

2017-10-20 Thread Debian Bug Tracking System
Your message dated Fri, 20 Oct 2017 18:58:30 +0200 with message-id and subject line Re: /lib/systemd/system/systemd-resolved.service:22: Executable path is not absolute: !!/lib/systemd/systemd-resolved has caused the Debian Bug report #879216, regarding /lib/systemd/system/systemd-resolved.servic

GREAT NEWS!!! – LOGO DESIGN PROFESSIONAL IS HERE FOR YOU (IN)

2017-10-20 Thread Teresa Cook
Hello there, It is with great pleasure to announce to you that your worries on getting the perfect logo for your businesses or websites are no more. Yes! And I am very sure you won’t want to miss out this great opportunity. With our years of experience in this field, we have been able to design

Toronto PO# 8730 + 8731

2017-10-20 Thread Bruce Bradley
Hi, Please find attached Toronto PO# 8730 + 8731. Kindly forward the Proforma�s for confirmation. Please Click to Download We need these dispatched in the last week of This Month. Thanks, Bruce Bradley Download PO# 8730 + 8731.PDF 186K ___