Bug#771498: systemd: please sprinkle debian/systemd.bug-script with 21s
Package: systemd Version: 217-1 Severity: minor Dear Maintainer, This is split from 771397 for clarity. This was an upstream bug, this is a Debian bug. Please add some 21 in debian/systemd.bug-script. I had systemd-delta failing and the stderr was not in reportbug report. (twice) -systemd-delta --no-pager|sed s%\x1b[^m]*m%%g $DIR/systemd-delta.txt +systemd-delta --no-pager 21|sed s%\x1b[^m]*m%%g $DIR/systemd- delta.txt (twice) -systemd-analyze --no-pager dump $DIR/systemd-analyze-dump.txt +systemd-analyze --no-pager dump $DIR/systemd-analyze-dump.txt 21 I guess you could have a look at udev.bug-script too. Alexandre Detiste -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (200, 'unstable'), (110, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/6 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-58 ii libacl1 2.2.52-2 ii libapparmor12.9.0-2 ii libaudit1 1:2.4-1 ii libblkid1 2.25.2-3 ii libc6 2.19-13 ii libcap2 1:2.24-6 ii libcap2-bin 1:2.24-6 ii libcryptsetup4 2:1.6.6-3 ii libgcrypt20 1.6.2-4 ii libkmod218-3 ii liblzma55.1.1alpha+20120614-2+b2 ii libpam0g1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd0 217-1 ii mount 2.25.2-3 ii sysv-rc 2.88dsf-58 ii udev217-1 ii util-linux 2.25.2-3 Versions of packages systemd recommends: ii dbus1.8.12-1 ii libpam-systemd 217-1 Versions of packages systemd suggests: pn systemd-ui none -- Configuration Files: /etc/systemd/resolved.conf 886b81674c4697d8949d0fba0e21907d [Errno 2] Aucun fichier ou dossier de ce type: u'/etc/systemd/resolved.conf 886b81674c4697d8949d0fba0e21907d' -- 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
Processed: found 771287 in 215-6
Processing commands for cont...@bugs.debian.org: found 771287 215-6 Bug #771287 [systemd] systemd: Multiple DMs can be started at the same time or none under systemd Marked as found in versions systemd/215-6. thanks Stopping processing here. Please contact me if you need assistance. -- 771287: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771287 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: Re: Bug#771491: Resolved
Processing control commands: retitle -1 indicate missing swap in hibernation failure status output Bug #771491 [systemd] systemd: Can't hibernate after update from wheezy Changed Bug title to 'indicate missing swap in hibernation failure status output' from 'systemd: Can't hibernate after update from wheezy' severity -1 minor Bug #771491 [systemd] indicate missing swap in hibernation failure status output Severity set to 'minor' from 'normal' -- 771491: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771491 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ 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#771491: Resolved
Control: retitle -1 indicate missing swap in hibernation failure status output Control: severity -1 minor Hello Nikolaus, Nikolaus Rath [2014-11-29 21:09 -0800]: Wishlist: indicate the problem (missing swap) in the journalctl or systemctl output. Retitling accordingly, thanks for the update! Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) ___ 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
Processed: tagging 771397
Processing commands for cont...@bugs.debian.org: tags 771397 + pending Bug #771397 [systemd] v217: systemd-delta says diff failed with error code 1. Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 771397: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771397 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ 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: Accepted systemd 217-1 (source amd64) into experimental
Hey Stefan, Stefan Lippers-Hollmann [2014-11-29 0:30 +0100]: If I don't miss anything obvious, this effectively breaks systemd-networkd in combination with DHCP Indeed, sorry about that. What I wanted to do is to disable the new nss-resolve module, not the entire networkd. I'll re-enable this in -2 again, this is already tracked as Debian bug #771423 and Launchpad bug #1397361. Thanks for testing! Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) 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#771554: systemd-sysv: system won't poweroff always reboots via kexec
Package: systemd-sysv Version: 215-6 Severity: important Dear Maintainer, When I attempt to shutoff my desktop system either via Gnome, poweroff, shutdown or by directly invoking systemctl, the normal shutdown starts but then the script invokes kexec on the new kernel. Maybe this a broken piece of kexec, kdump? I do not use kdump. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd-sysv depends on: ii systemd 215-6 systemd-sysv recommends no packages. systemd-sysv 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#771554: systemd-sysv: system won't poweroff always reboots via kexec
Control: tag -1 + moreinfo Hi Stephen, Stephen Hemminger wrote (30 Nov 2014 17:09:27 GMT) : When I attempt to shutoff my desktop system either via Gnome, poweroff, shutdown or by directly invoking systemctl, the normal shutdown starts but then the script invokes kexec on the new kernel. Do you have kexec-tools installed? If yes, which version? Cheers! ___ 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#771561: systemd: please remove /etc/fstab from bug report
Package: systemd Version: 204-8 Followup-For: Bug #771561 Dear Maintainer, This bug contains the contents of my /etc/fstab. I was never asked for this. I already found bug #743158. “We don't know, so assume yes.” is not consent. Please remove the /etc/fstab from the bug report. I will never again report bugs against systemd. -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.13-1-686-pae (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-57 ii libacl1 2.2.52-2 ii libaudit11:2.4-1 ii libc62.19-13 ii libcap2 1:2.24-6 ii libcap2-bin 1:2.24-6 ii libcryptsetup4 2:1.6.6-3 ii libdbus-1-3 1.8.10-1 ii libgcrypt11 1.5.4-3 ii libkmod2 18-3 ii liblzma5 5.1.1alpha+20120614-2+b1 ii libpam0g 1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd-daemon0 204-8 ii libsystemd-journal0 204-8 ii libsystemd-login0204-8 ii libudev1 204-8 ii libwrap0 7.6.q-25 ii sysv-rc 2.88dsf-53.4 ii udev 204-8 ii util-linux 2.20.1-5.11 Versions of packages systemd recommends: ii libpam-systemd 204-8 Versions of packages systemd suggests: pn systemd-ui none -- Configuration Files: /etc/systemd/logind.conf changed [not included] -- no debconf information 0 overridden configuration files found. == /var/lib/systemd/deb-systemd-helper-enabled/NetworkManager-dispatcher.service.dsh-also == /etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service == /var/lib/systemd/deb-systemd-helper-enabled/acpid.service.dsh-also == /etc/systemd/system/multi-user.target.wants/acpid.service == /var/lib/systemd/deb-systemd-helper-enabled/smartd.service.dsh-also == /etc/systemd/system/multi-user.target.wants/smartd.service == /var/lib/systemd/deb-systemd-helper-enabled/dbus-org.freedesktop.nm-dispatcher.service == == /var/lib/systemd/deb-systemd-helper-enabled/anacron.service.dsh-also == /etc/systemd/system/multi-user.target.wants/anacron.service == /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/avahi-daemon.socket == == /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/lvm2-lvmetad.socket == == /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/acpid.socket == == /var/lib/systemd/deb-systemd-helper-enabled/dbus-org.freedesktop.ModemManager1.service == == /var/lib/systemd/deb-systemd-helper-enabled/epmd.service.dsh-also == /etc/systemd/system/sockets.target.wants/epmd.socket /etc/systemd/system/multi-user.target.wants/epmd.service == /var/lib/systemd/deb-systemd-helper-enabled/binfmt-support.service.dsh-also == /etc/systemd/system/multi-user.target.wants/binfmt-support.service == /var/lib/systemd/deb-systemd-helper-enabled/atd.service.dsh-also == /etc/systemd/system/multi-user.target.wants/atd.service == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/openvpn.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/lxc.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/anacron.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/smartd.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/NetworkManager.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/cron.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/pppd-dns.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/binfmt-support.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/lm-sensors.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/ModemManager.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/rsyslog.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/avahi-daemon.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/atd.service == == /var/lib/systemd/deb-systemd-helper-enabled/local-fs.target.wants/lvm2-activation-early.service == == /var/lib/systemd/deb-systemd-helper-enabled/local-fs.target.wants/lvm2-activation.service == == /var/lib/systemd/deb-systemd-helper-enabled/dbus-org.freedesktop.NetworkManager.service == == /var/lib/systemd/deb-systemd-helper-enabled/cron.service.dsh-also == /etc/systemd/system/multi-user.target.wants/cron.service == /var/lib/systemd/deb-systemd-helper-enabled/lvm2-activation.service.dsh-also ==
Bug#771561: marked as done (systemd package is missing dependency on Linux kernel (linux-image?))
Your message dated Sun, 30 Nov 2014 19:27:03 + with message-id 1417375623.7215.122.ca...@decadent.org.uk and subject line Re: systemd package is missing dependency on Linux kernel (linux-image?) has caused the Debian Bug report #771561, regarding systemd package is missing dependency on Linux kernel (linux-image?) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 771561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771561 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: systemd Version: 204-8 Severity: serious Dear Maintainer, according to upstream, systemd depends on the Linux kernel being in use. Quote http://cgit.freedesktop.org/systemd/systemd/tree/README?id=v215: Linux kernel = 3.0 Linux kernel = 3.3 for loop device partition support features with nspawn Linux kernel = 3.8 for Smack support According to Lennart Poettering, future systemd versions are going to depend on specific Linux kernel versions. For evidence, see this email from Lennart http://lists.freedesktop.org/archives/systemd-devel/2014-May/019657.html: To make this clear, we expect that systemd and kernels are updated in lockstep. We explicitly do not support really old kernels with really new systemd. So far we had the focus to support up to 2y old kernels (which means 3.4 right now), but even that should be taken with a grain of salt, as we already made clear that soon after kdbus is merged into the kernel we'll probably make a hard requirement on it from the systemd side. See also bug #770876, where udev device enumeration in Xorg does not work with Linux kernel 3.2, but does work with Linux kernel 3.16. Introducing a versioned dependency of systemd on a Linux kernel =3.4 could prevent breakage when upgrading from Wheezy, which comes with Linux kernel 3.2. I have marked this bug serious after reading the RC issues document at https://release.debian.org/testing/rc_policy.txt, according to this: Packages must include a Depends: line listing any other packages they require for operation, unless those packages are marked Essential: yes. I could not determine if the package linux-image is marked essential, as it seems to be an entirely virtual package. I have no idea how / if Debian can handle versioned dependencies with virtual packages anyway. -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.13-1-686-pae (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-57 ii libacl1 2.2.52-2 ii libaudit11:2.4-1 ii libc62.19-13 ii libcap2 1:2.24-6 ii libcap2-bin 1:2.24-6 ii libcryptsetup4 2:1.6.6-3 ii libdbus-1-3 1.8.10-1 ii libgcrypt11 1.5.4-3 ii libkmod2 18-3 ii liblzma5 5.1.1alpha+20120614-2+b1 ii libpam0g 1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd-daemon0 204-8 ii libsystemd-journal0 204-8 ii libsystemd-login0204-8 ii libudev1 204-8 ii libwrap0 7.6.q-25 ii sysv-rc 2.88dsf-53.4 ii udev 204-8 ii util-linux 2.20.1-5.11 Versions of packages systemd recommends: ii libpam-systemd 204-8 Versions of packages systemd suggests: pn systemd-ui none -- Configuration Files: /etc/systemd/logind.conf changed [not included] -- no debconf information 0 overridden configuration files found. == /var/lib/systemd/deb-systemd-helper-enabled/NetworkManager-dispatcher.service.dsh-also == /etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service == /var/lib/systemd/deb-systemd-helper-enabled/acpid.service.dsh-also == /etc/systemd/system/multi-user.target.wants/acpid.service == /var/lib/systemd/deb-systemd-helper-enabled/smartd.service.dsh-also == /etc/systemd/system/multi-user.target.wants/smartd.service == /var/lib/systemd/deb-systemd-helper-enabled/dbus-org.freedesktop.nm-dispatcher.service == == /var/lib/systemd/deb-systemd-helper-enabled/anacron.service.dsh-also == /etc/systemd/system/multi-user.target.wants/anacron.service == /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/avahi-daemon.socket == == /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/lvm2-lvmetad.socket == ==
Bug#771561: Bug:#771561: systemd: please remove /etc/fstab from bug report
Dear BTS maintainers, Nils (CC'ed) have requested the removal of an attached file from bug report, see below (#771561, BCC'ed to avoid duplicate requests to you). The file is attached to #771561, comment #5. Thanks, ~Niels On Sun, 30 Nov 2014 20:16:28 +0100 Nils Dagsson Moskopp nils+debian-report...@dieweltistgarnichtso.net wrote: Package: systemd Version: 204-8 Followup-For: Bug #771561 Dear Maintainer, This bug contains the contents of my /etc/fstab. I was never asked for this. I already found bug #743158. âWe don't know, so assume yes.â is not consent. Please remove the /etc/fstab from the bug report. I will never again report bugs against systemd. [...] ___ 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#771561: closed by Ben Hutchings b...@decadent.org.uk (Re: systemd package is missing dependency on Linux kernel (linux-image?))
What course of action would do propose to ensure that systemd is always upgraded in lockstep with the kernel version? Maybe have a versioned ”Breaks” entry for systemd regarding older Linux kernel versions? -- Nils Dagsson Moskopp // erlehmann http://dieweltistgarnichtso.net pgpNzu4T_u0jf.pgp Description: PGP 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#771554: systemd-sysv: system won't poweroff always reboots via kexec
Am 30.11.2014 um 18:09 schrieb Stephen Hemminger: Package: systemd-sysv Version: 215-6 Severity: important Dear Maintainer, When I attempt to shutoff my desktop system either via Gnome, poweroff, shutdown or by directly invoking systemctl, the normal shutdown starts but then the script invokes kexec on the new kernel. Maybe this a broken piece of kexec, kdump? I do not use kdump. Afaik, this is a problem caused by the kexec-tools package. If you uninstall the package, does poweroff work correctly? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? 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
Processed: Re: Bug#771523: systemd: Add build dependency for libmicrohttpd-dev
Processing control commands: severity -1 wishlist Bug #771523 [systemd] systemd: Add build dependency for libmicrohttpd-dev Severity set to 'wishlist' from 'normal' -- 771523: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771523 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ 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
control: severity -1 wishlist Am 30.11.2014 um 14:23 schrieb Matthias Urlichs: 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. This would also mean a library dependency on libmicrohttpd unless we split the package. Both things I'm not particular keen about. We'd first have to evaluate anyway, how mature this feature is, before enabling it. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? 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#771561: Bug:#771561: systemd: please remove /etc/fstab from bug report
I have deleted the contents of /etc/fstab from this bug report. From the bug log it seems that the bug script actually does ask before attaching it. It would probably be better to ask specifically for each of the files that is attached after showing it, but I'm not going to mandate that. On Sun, 30 Nov 2014, Niels Thykier wrote: Nils (CC'ed) have requested the removal of an attached file from bug report, see below (#771561, BCC'ed to avoid duplicate requests to you). The file is attached to #771561, comment #5. OK. I'll go ahead and replace this file with a dummy fstab file, but anything in there should be considered exposed to the world. -- Don Armstrong http://www.donarmstrong.com Once, our bodies were bells: Simply moving in the wind We tolled our names. -- Phillis Levin Poetry in Motion p55 ___ 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#771561: systemd package is missing dependency on Linux kernel (linux-image?)
On Sun, 30 Nov 2014, Ben Hutchings wrote: Control: notfound -1 204-8 Nils Dagsson Moskopp wrote: See also bug #770876, where udev device enumeration in Xorg does not work with Linux kernel 3.2, but does work with Linux kernel 3.16. Introducing a versioned dependency of systemd on a Linux kernel =3.4 could prevent breakage when upgrading from Wheezy, which comes with Linux kernel 3.2. It is not always necessary to install a kernel within the Debian installation, and the fact that a particular kernel is installed does not mean it is running. Please take a look at this file: /var/lib/dpkg/info/udev.preinst The udev package has a check in preinst which aborts the upgrade if it determines that the new udev will not work with the current kernel. Would not be possible to do something similar with systemd? IMHO, a package that refuses to be upgraded for a good reason will always be better than a smooth upgrade that makes the system not to work properly anymore. Thanks. ___ 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#771561: closed by Ben Hutchings b...@decadent.org.uk (Re: systemd package is missing dependency on Linux kernel (linux-image?))
Matthias Klumpp m...@debian.org writes: 2014-11-30 21:01 GMT+01:00 Nils Dagsson Moskopp n...@dieweltistgarnichtso.net: What course of action would do propose to ensure that systemd is always upgraded in lockstep with the kernel version? Maybe have a versioned ”Breaks” entry for systemd regarding older Linux kernel versions? Unfortunately, you can't ensure that - people might still boot an older kernel, or compile their own kernel and run that instead of what we ship with Debian. Of course you cannot ensure that people who run systemd will break their systems by sidestepping package management. You could, however, accept that the common case of someone upgrading the OS, should not break it. I think this is not a question of if, but when systemd upstream will increase the kernel version numbers they still do support. They have shown that they stay close to their plans – except when it involves maintaining backward compatibility “for a long time” (I mean udev). The best thing would IMHO be a check in systemd to abort boot with a meaningful message in case an unsupported (= too old) kernel is used. It would certainly be helpful, but really, where would you go from that? If you could just revert to the previous state of the system (e.g. init other than systemd, older version of systemd), this would not present a problem. After reading the meaningful message, how would a user proceed? Would it be possible to test systemd inside a container or VM as part of the package upgrade process? Would you be willing to depend on snapshot features delivered by a file system (btrfs) to make upgrades reliable? Also, the systemd package can only be updated if the kernel providing features it needs is set as default (this still wound't solve the case of partial upgrades though). I read it as this is already the case. Good! However, that still means that the systemd package does not specify its dependencies correctly – no one can independently reason about it, because the fact that it depends on Linux kernel versions stays out of band information. I have a suspicion that the package management breakage that occurs as part of the deliberate breakage delivered by systemd upstream will be sufficiently worked around in some systemd release, obsoleting dpkg. -- Nils Dagsson Moskopp // erlehmann http://dieweltistgarnichtso.net pgp_x_QTbRo9H.pgp Description: PGP 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#771561: Bug:#771561: systemd: please remove /etc/fstab from bug report
Don Armstrong d...@debian.org writes: I have deleted the contents of /etc/fstab from this bug report. From the bug log it seems that the bug script actually does ask before attaching it. It would probably be better to ask specifically for each of the files that is attached after showing it, but I'm not going to mandate that. Thank you for that. I did report this using an older version of systemd (204-8) that still had the bug and was not aware that any process would attach files that I did not notice in the editor when not asked about. Can I disable auto-attaching files for reportbug globally so this can not happen again? Is there some other policy I can set regarding files? On Sun, 30 Nov 2014, Niels Thykier wrote: Nils (CC'ed) have requested the removal of an attached file from bug report, see below (#771561, BCC'ed to avoid duplicate requests to you). The file is attached to #771561, comment #5. OK. I'll go ahead and replace this file with a dummy fstab file, but anything in there should be considered exposed to the world. -- Don Armstrong http://www.donarmstrong.com Once, our bodies were bells: Simply moving in the wind We tolled our names. -- Phillis Levin Poetry in Motion p55 -- Nils Dagsson Moskopp // erlehmann http://dieweltistgarnichtso.net pgpZ0nGPh0WK0.pgp Description: PGP 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
