Bug#917261: linux-image-4.19.0-1-amd64: /dev/mapper symlink for dm-crypt volume containing / not created on system startup

2018-12-27 Thread Ben Hutchings
On Wed, 2018-12-26 at 21:57 -0500, Celejar wrote: > On Wed, 26 Dec 2018 15:39:19 + > Ben Hutchings wrote: > > > On Tue, Dec 25, 2018 at 09:58:33PM -0500, Celejar wrote: > > > On Tue, 25 Dec 2018 20:52:46 + > > > Ben Hutchings wrote: > > > > > > > Control: reassign -1 udev 240-1 > > > >

Bug#917185: udev 240-1 + sysvinit-core 2.93-1 break input devices + other problems

2018-12-27 Thread Ricardo Peliquero
Thank you Michael, I've just updated from 239-15 to 240-2; but, unfortunately, none of the problems were solved. Also, followed your instructions, but: root@local:~# udevadm trigger root@local:~# update-initramfs -u update-initramfs: Generating /boot/initrd.img-4.19.0-1-686-pae Fatal:

Bug#917247: udev: Many modules are no longer automatically loaded at boot

2018-12-27 Thread Michael Biebl
On Mon, 24 Dec 2018 12:18:09 -0500 =?utf-8?b?RnLDqWTDqXJpYyBCcmnDqHJl?= wrote: > Package: udev > Version: 240-1 > Severity: important > > After upgrading to 240-1 and rebooting, many modules (about ⅓ of them) > were no longer automatically loaded at boot, causing many problems as > you can

Bug#917124: lvm2 logical volumes are not properly initialized

2018-12-27 Thread Michael Biebl
Am 27.12.18 um 23:09 schrieb Ben Caradoc-Davies: > And I am also please to report that the two-minute wait on shutdown seen > here after upgrade to 240-1 and also after upgrade to 240-2 occurs only > on the first shutdown after upgrade: >

Bug#917124: lvm2 logical volumes are not properly initialized

2018-12-27 Thread Ben Caradoc-Davies
And I am also please to report that the two-minute wait on shutdown seen here after upgrade to 240-1 and also after upgrade to 240-2 occurs only on the first shutdown after upgrade: https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=917124;filename=img_20181223_130610.jpg;msg=27

Bug#917185: udev 240-1 + sysvinit-core 2.93-1 break input devices + other problems

2018-12-27 Thread Michael Biebl
Am 27.12.18 um 23:08 schrieb Michael Biebl: > The explicit "udevadm trigger" should ensure that all symlinks in /dev > are created resulting ...resulting in a working initrd -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?

Bug#917185: udev 240-1 + sysvinit-core 2.93-1 break input devices + other problems

2018-12-27 Thread Ricardo Peliquero
Dear Frédéric: I believe these bugs may be related to #917124. Now expecting 240-2 release to report any results. Anyway, have a look at these two items, just for the record: * diff lsmod_udev_239-15_sort.txt lsmod_udev_240-1_sort.txt 2d1 < ac97_bus 16384 1 snd_ac97_codec 7d5 <

Processed: [bts-link] source package systemd

2018-12-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package systemd > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

[bts-link] source package systemd

2018-12-27 Thread debian-bts-link
# # bts-link upstream status pull for source package systemd # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #917122 (http://bugs.debian.org/917122)

Bug#917423: systemd-sysv: centrally document which "legacy" packages/replaced are replaced by systemd

2018-12-27 Thread Christoph Anton Mitterer
Package: systemd-sysv Version: 240-1 Severity: wishlist Hey. Maybe I couldn't just find it, but it seems there is no central place which describes which "legacy" packages can be removed when running systemd... respectively which services could be (optionally) replaced by which systemd

Processed: merge

2018-12-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 917167 917357 Bug #917167 {Done: Michael Biebl } [systemd] systemd: 240 breaks kde (rakes ages to launch) Bug #917168 {Done: Michael Biebl } [systemd] systemd: fail to start kde after 240-1 upgrade Bug #917173 {Done: Michael Biebl }

Bug#917357: systemd: nfs mount not possible with systemd 240-1

2018-12-27 Thread Michael Biebl
Control: notfound -1 239-15 Control: found -1 240-1 Control: forcemerge 91716 -1 Am 27.12.18 um 14:43 schrieb Holger Schröder: > Am 27.12.18 um 14:13 schrieb Michael Biebl: >> Can you try the following >> # ulimit -n 4096 >> # mount -t nfs -o vers=3 hsp1:/home/holgi/backup >> > Can I put that

Processed (with 1 error): Re: systemd: nfs mount not possible with systemd 240-1

2018-12-27 Thread Debian Bug Tracking System
Processing control commands: > notfound -1 239-15 Bug #917357 [systemd] systemd: nfs mount not possible with systemd 240-1 No longer marked as found in versions systemd/239-15. > found -1 240-1 Bug #917357 [systemd] systemd: nfs mount not possible with systemd 240-1 Marked as found in versions

Bug#917261: marked as done (linux-image-4.19.0-1-amd64: /dev/mapper symlink for dm-crypt volume containing / not created on system startup)

2018-12-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Dec 2018 13:55:36 + with message-id and subject line Bug#917124: fixed in systemd 240-2 has caused the Debian Bug report #917124, regarding linux-image-4.19.0-1-amd64: /dev/mapper symlink for dm-crypt volume containing / not created on system startup to be marked

Bug#917215: marked as done (systemd: FTBFS on armel and armhf (failing test))

2018-12-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Dec 2018 13:55:36 + with message-id and subject line Bug#917215: fixed in systemd 240-2 has caused the Debian Bug report #917215, regarding systemd: FTBFS on armel and armhf (failing test) to be marked as done. This means that you claim that the problem has been

Bug#917166: marked as done (Errors on and after upgrade to 2.03.01-2, swap on lvm not mounted)

2018-12-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Dec 2018 13:55:36 + with message-id and subject line Bug#917124: fixed in systemd 240-2 has caused the Debian Bug report #917124, regarding Errors on and after upgrade to 2.03.01-2, swap on lvm not mounted to be marked as done. This means that you claim that the

Bug#917195: marked as done (FTBFS on mips(el): expected ‘dev_t *’ {aka ‘long long unsigned int *’} but argument is of type ‘long unsigned int *’)

2018-12-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Dec 2018 13:55:36 + with message-id and subject line Bug#917195: fixed in systemd 240-2 has caused the Debian Bug report #917195, regarding FTBFS on mips(el): expected ‘dev_t *’ {aka ‘long long unsigned int *’} but argument is of type ‘long unsigned int *’ to be

Bug#917168: marked as done (systemd: fail to start kde after 240-1 upgrade)

2018-12-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Dec 2018 13:55:36 + with message-id and subject line Bug#917167: fixed in systemd 240-2 has caused the Debian Bug report #917167, regarding systemd: fail to start kde after 240-1 upgrade to be marked as done. This means that you claim that the problem has been

systemd_240-2_source.changes ACCEPTED into unstable

2018-12-27 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 27 Dec 2018 14:03:57 +0100 Source: systemd Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump systemd-tests libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve

Processing of systemd_240-2_source.changes

2018-12-27 Thread Debian FTP Masters
systemd_240-2_source.changes uploaded successfully to localhost along with the files: systemd_240-2.dsc systemd_240-2.debian.tar.xz systemd_240-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) ___

Bug#917357: systemd: nfs mount not possible with systemd 240-1

2018-12-27 Thread Holger Schröder
Am 27.12.18 um 14:13 schrieb Michael Biebl: On Wed, 26 Dec 2018 17:03:31 +0100 =?utf-8?q?Holger_Schr=C3=B6der?= wrote: Package: systemd Version: 239-15 Severity: normal Dear Maintainer, With systemd 240-1 it is not possible to mount an nfs-share. Downgrade to 239-15 solves the problem.

Processed: Bug #917195 in systemd marked as pending

2018-12-27 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #917195 [src:systemd] FTBFS on mips(el): expected ‘dev_t *’ {aka ‘long long unsigned int *’} but argument is of type ‘long unsigned int *’ Added tag(s) pending. -- 917195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917195 Debian Bug

Processed: Bug #917167 in systemd marked as pending

2018-12-27 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #917167 [systemd] systemd: 240 breaks kde (rakes ages to launch) Bug #917168 [systemd] systemd: fail to start kde after 240-1 upgrade Bug #917173 [systemd] systemd 240-1 breaks Plasma Added tag(s) pending. Added tag(s) pending. Added tag(s)

Processed: Bug #917215 in systemd marked as pending

2018-12-27 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #917215 [src:systemd] systemd: FTBFS on armel and armhf (failing test) Added tag(s) pending. -- 917215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Bug #917124 in systemd marked as pending

2018-12-27 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #917124 [udev] lvm2 logical volumes are not properly initialized Bug #917136 [udev] udev: LVM volumes fail to initialize properly with udev 240-1 Bug #917166 [udev] Errors on and after upgrade to 2.03.01-2, swap on lvm not mounted Bug #917261

Bug#917357: systemd: nfs mount not possible with systemd 240-1

2018-12-27 Thread Michael Biebl
On Wed, 26 Dec 2018 17:03:31 +0100 =?utf-8?q?Holger_Schr=C3=B6der?= wrote: > Package: systemd > Version: 239-15 > Severity: normal > > Dear Maintainer, > > With systemd 240-1 it is not possible to mount an nfs-share. Downgrade to > 239-15 solves the problem. > > root@sidbox/home/holgi $ mount