Processed: Re: Bug#748311: systemd: unknown operation 'dump' in reportbug script
Processing control commands: tags -1 + pending Bug #748311 [systemd] systemd: unknown operation 'dump' in reportbug script Added tag(s) pending. -- 748311: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748311 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: Missing /run/shm also breaks mk-sbuild (ubuntu-dev-tools)
Processing control commands: affects -1 + ubuntu-dev-tools Bug #674755 [systemd] systemd: tmpfs inconsistencies (/run/lock, /run/shm, /tmp) Added indication that 674755 affects ubuntu-dev-tools -- 674755: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674755 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#742668: /etc/sysctl.conf
Processing control commands:
clone -1 -2
Bug #742668 {Done: Didier Raboud o...@debian.org} [cups] cups: Fails to
install because can't listen to sockets
Bug 742668 cloned as bug 749841
reassign -2 systemd 204-8
Bug #749841 {Done: Didier Raboud o...@debian.org} [cups] cups: Fails to
install because can't listen to sockets
Bug reassigned from package 'cups' to 'systemd'.
No longer marked as found in versions cups/1.7.2-3 and cups/1.7.1-10.
No longer marked as fixed in versions cups/1.7.1-13.
Bug #749841 {Done: Didier Raboud o...@debian.org} [systemd] cups: Fails to
install because can't listen to sockets
Marked as found in versions systemd/204-8.
retitle -2 systemd: IPv6 addresses in ListenStream should not hinder socket
file starting
Bug #749841 {Done: Didier Raboud o...@debian.org} [systemd] cups: Fails to
install because can't listen to sockets
Changed Bug title to 'systemd: IPv6 addresses in ListenStream should not hinder
socket file starting' from 'cups: Fails to install because can't listen to
sockets'
--
742668: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742668
749841: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749841
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#750360: marked as done (systemd-sysv: /sbin/init should be a relative symlink)
Your message dated Mon, 02 Jun 2014 23:58:02 +0200 with message-id 538cf36a.4020...@debian.org and subject line Re: Bug#750360: systemd-sysv: /sbin/init should be a relative symlink has caused the Debian Bug report #750360, regarding systemd-sysv: /sbin/init should be a relative symlink 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.) -- 750360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750360 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: systemd-sysv Version: 204-10 Severity: important /sbin/init is installed as a symbolic link to the absolute path //lib/systemd/systemd. This breaks in environments where the root filesystem is not mounted at /, for example, when inspecting a chroot from outside or, which is worse, when being first mounted from initramfs. I just spent quite some time figuring out why the initramfs on a PXE boot client behaved oddly, and it turned out that the nfs root mount script in initramfs has a logic that repeatedly checks for the existence of /root/sbin/init, with the soon-to-be rootfs being mounted at /root. With the absolute symlink of systemd-sysv in place, /sbin/init points outside the /root directory holding the rootfs, and thus renders the link target non-existent. Just updating the /sbin/init symlink to point to a relative path fixes the issue without side effects: /sbin/init - ../lib/systemd/systemd Please fix this in the script so systemd can work in all environments where sysv-init worked! -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/6 CPU cores) 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-sysv depends on: ii systemd 204-10 systemd-sysv recommends no packages. systemd-sysv suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Am 02.06.2014 22:29, schrieb Dominik George: Package: systemd-sysv Version: 204-10 Severity: important /sbin/init is installed as a symbolic link to the absolute path //lib/systemd/systemd. This symlink is created via debian/systemd-sysv.links by dh_link. I don't know the reasons why dh_links creates relative symlinks, but you'll need to talk to the debhelper maintainers if you want to see this behaviour changed. I assume there are reasons for that, but you'll need to talk to the debhelper maintainers. This is nothing which can be fixed in the systemd package, thus closing the bug report. Please feel free to report this issue against the debhelper package, which ships dh_link. Regards, 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 ---End Message--- ___ 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#750360: systemd-sysv: breaks NFS root systems
Processing control commands: reassign -1 initramfs-tools 0.115 Bug #750360 [systemd-sysv] systemd-sysv: breaks NFS root systems Bug reassigned from package 'systemd-sysv' to 'initramfs-tools'. No longer marked as found in versions systemd/204-10. Ignoring request to alter fixed versions of bug #750360 to the same values previously set Bug #750360 [initramfs-tools] systemd-sysv: breaks NFS root systems Marked as found in versions initramfs-tools/0.115. retitle -1 initramfs-tools: nfs mount script check for /sbin/init incomplete Bug #750360 [initramfs-tools] systemd-sysv: breaks NFS root systems Changed Bug title to 'initramfs-tools: nfs mount script check for /sbin/init incomplete' from 'systemd-sysv: breaks NFS root systems' -- 750360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750360 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#750992: marked as done (position in build process not clear)
Your message dated Sat, 14 Jun 2014 11:34:05 + with message-id e1wvmdl-0007bp...@franck.debian.org and subject line Bug#750992: fixed in init-system-helpers 1.19 has caused the Debian Bug report #750992, regarding position in build process not clear 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.) -- 750992: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750992 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: dh-systemd Version: 1.18 Severity: normal According to its manpage dh_systemd_enable should be run before dh_installinit. However, when building quota I get an error message when doing so: dh_systemd_enable: Could not find quotarpc.service in the ... And sure enough this error message make sense as the file is only created by dh_installinit --name=quotarpc after the dh_systemd_enable call. Moving the dh_systemd_enable call down, makes the package build without an error. I'm not sure, though, if it still does what it should. Michael -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) 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 dh-systemd depends on: ii debhelper 9.20140228 ii perl 5.18.2-4 dh-systemd recommends no packages. dh-systemd suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: init-system-helpers Source-Version: 1.19 We believe that the bug you reported is fixed in the latest version of init-system-helpers, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 750...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Stapelberg stapelb...@debian.org (supplier of updated init-system-helpers package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 14 Jun 2014 13:17:57 +0200 Source: init-system-helpers Binary: init-system-helpers dh-systemd Architecture: source all Version: 1.19 Distribution: unstable Urgency: medium Maintainer: pkg-systemd-maintainers pkg-systemd-maintainers@lists.alioth.debian.org Changed-By: Michael Stapelberg stapelb...@debian.org Description: dh-systemd - debhelper add-on to handle systemd unit files init-system-helpers - helper tools for all init systems Closes: 750404 750986 750992 Changes: init-system-helpers (1.19) unstable; urgency=medium . * Use try-restart only on upgrades, start after initial installation (Closes: #750404) * improve error message wording (Closes: #750986) * dh_systemd_enable: document the --name option (Closes: #750992) Checksums-Sha1: 63b2db4c9be51bb8f35b32a08418878649c405ca 1829 init-system-helpers_1.19.dsc 3d37fa5ed6cf96fd7dec3be83f28d259811fc12f 16336 init-system-helpers_1.19.tar.xz da27bdab30fed3fd0af3a5458325ee4bcbfb59e1 13360 init-system-helpers_1.19_all.deb e5b436dc891b7de453fc8d81841ad19675b72458 14018 dh-systemd_1.19_all.deb Checksums-Sha256: 0c52c3e8222661762625501e7ab7ab7e06cbd352e988e93bd047aa4dfef20998 1829 init-system-helpers_1.19.dsc 07f5a0cb86f3b265d4000cc537ff5d98032621e412a207c694dfd97a0f7d25f3 16336 init-system-helpers_1.19.tar.xz 56020318db3e26f8263e74e3e0b91508aec4d665e2ff5c4bf0f83437c1acef3d 13360 init-system-helpers_1.19_all.deb 4c7f47891cff0ce3aa4574602e1a9aa6bba82c6756aa67a862de4b5c7084767d 14018 dh-systemd_1.19_all.deb Files: 145cce0ba99b6604ce9c5465189fe55e 13360 admin extra init-system-helpers_1.19_all.deb 0706bd51e14d710e4955fe72f2abbcca 14018 admin extra dh-systemd_1.19_all.deb 72ad905f964ba1d5b365fb56fa574f29 1829 admin extra init-system-helpers_1.19.dsc 4f1667671ce1c9d51b0fa5c5b49f47d1 16336 admin extra init-system-helpers_1.19.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJTnC/nAAoJEE5xYO1KyO4dYwMP/2Ze9NWjvKanwR4ChO7eCxEE 7OCjFOJaBQ2tPF3SgHe3CwmK4zQo/qNXAOtKObwLHpzmfptGq+PNIFXVmlMVQfaD xUhL0t1eSRXjzr3BGJqbsuZI5FGEcJteDtYlqNRJ72bXjhrv5htyan3yisnLupKN HyvR3/AA
Processed: severity of 751585 is important, tagging 751585
Processing commands for cont...@bugs.debian.org: severity 751585 important Bug #751585 [systemd] systemd: opens emergency shell after prompting for unnecessary dm-crypt passwords Severity set to 'important' from 'critical' tags 751585 + moreinfo Bug #751585 [systemd] systemd: opens emergency shell after prompting for unnecessary dm-crypt passwords Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 751585: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751585 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: reassign 751589 to sysvinit-core,systemd-sysv, found 751589 in sysvinit/2.88dsf-53 ...
Processing commands for cont...@bugs.debian.org: reassign 751589 sysvinit-core,systemd-sysv Bug #751589 [sysvinit-core] sysvinit-core: /sbin/init missing after switching from systemd to sysvinit Bug reassigned from package 'sysvinit-core' to 'sysvinit-core,systemd-sysv'. No longer marked as found in versions sysvinit/2.88dsf-53, systemd-sysv, and systemd/204-6. Ignoring request to alter fixed versions of bug #751589 to the same values previously set found 751589 sysvinit/2.88dsf-53 Bug #751589 [sysvinit-core,systemd-sysv] sysvinit-core: /sbin/init missing after switching from systemd to sysvinit Marked as found in versions sysvinit/2.88dsf-53. found 751589 systemd/204-6 Bug #751589 [sysvinit-core,systemd-sysv] sysvinit-core: /sbin/init missing after switching from systemd to sysvinit Marked as found in versions systemd/204-6. thanks Stopping processing here. Please contact me if you need assistance. -- 751589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751589 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#751585: systemd: opens emergency shell after prompting for unnecessary dm-crypt passwords
Processing commands for cont...@bugs.debian.org: severity 751585 normal Bug #751585 [systemd] systemd: opens emergency shell after prompting for unnecessary dm-crypt passwords Severity set to 'normal' from 'important' clone 751585 -1 -2 -3 Bug #751585 [systemd] systemd: opens emergency shell after prompting for unnecessary dm-crypt passwords Bug 751585 cloned as bugs 751622-751624 retitle -1 systemd: shows unnecessary password prompts for encrypted disks Bug #751622 [systemd] systemd: opens emergency shell after prompting for unnecessary dm-crypt passwords Changed Bug title to 'systemd: shows unnecessary password prompts for encrypted disks' from 'systemd: opens emergency shell after prompting for unnecessary dm-crypt passwords' severity -1 normal Bug #751622 [systemd] systemd: shows unnecessary password prompts for encrypted disks Ignoring request to change severity of Bug 751622 to the same value. retitle -2 systemd: should print reason for starting emergency shell Bug #751623 [systemd] systemd: opens emergency shell after prompting for unnecessary dm-crypt passwords Changed Bug title to 'systemd: should print reason for starting emergency shell' from 'systemd: opens emergency shell after prompting for unnecessary dm-crypt passwords' severity -2 wishlist Bug #751623 [systemd] systemd: should print reason for starting emergency shell Severity set to 'wishlist' from 'normal' retitle -3 systemd: emergency shell takes several minutes to start Bug #751624 [systemd] systemd: opens emergency shell after prompting for unnecessary dm-crypt passwords Changed Bug title to 'systemd: emergency shell takes several minutes to start' from 'systemd: opens emergency shell after prompting for unnecessary dm-crypt passwords' severity -3 normal Bug #751624 [systemd] systemd: emergency shell takes several minutes to start Ignoring request to change severity of Bug 751624 to the same value. thanks Stopping processing here. Please contact me if you need assistance. -- 751585: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751585 751622: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751622 751623: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751623 751624: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751624 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: under systemd: Warning: Stopping foo.service, but it can still be activated by: foo.socket
Processing control commands: reassign -1 dh-systemd Bug #751744 [monopd] monopd: under systemd: Warning: Stopping monopd.service, but it can still be activated by: monopd.socket Bug reassigned from package 'monopd' to 'dh-systemd'. No longer marked as found in versions monopd/0.9.7-1. Ignoring request to alter fixed versions of bug #751744 to the same values previously set forcemerge 751741 751744 Bug #751741 [dh-systemd] gpsd: under systemd: Warning: Stopping gpsd.service, but it can still be activated by: gpsd.socket Bug #751744 [dh-systemd] monopd: under systemd: Warning: Stopping monopd.service, but it can still be activated by: monopd.socket Merged 751741 751744 retitle 751741 dh-systemd: postinst snippets should stop foo.socket during upgrades too Bug #751741 [dh-systemd] gpsd: under systemd: Warning: Stopping gpsd.service, but it can still be activated by: gpsd.socket Bug #751744 [dh-systemd] monopd: under systemd: Warning: Stopping monopd.service, but it can still be activated by: monopd.socket Changed Bug title to 'dh-systemd: postinst snippets should stop foo.socket during upgrades too' from 'gpsd: under systemd: Warning: Stopping gpsd.service, but it can still be activated by: gpsd.socket' Changed Bug title to 'dh-systemd: postinst snippets should stop foo.socket during upgrades too' from 'monopd: under systemd: Warning: Stopping monopd.service, but it can still be activated by: monopd.socket' affects 751741 gpsd monopd cups-daemon Bug #751741 [dh-systemd] dh-systemd: postinst snippets should stop foo.socket during upgrades too Bug #751744 [dh-systemd] dh-systemd: postinst snippets should stop foo.socket during upgrades too Added indication that 751741 affects gpsd, monopd, and cups-daemon Added indication that 751744 affects gpsd, monopd, and cups-daemon -- 751741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751741 751744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751744 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 (with 3 errors): Re: under systemd: Warning: Stopping foo.service, but it can still be activated by: foo.socket
/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/751741 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/751741 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/751741 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/751741 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/751741 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/751741 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
at /usr/local/lib/site_perl/Debbugs/Common.pm line 587
Debbugs::Common::filelock('/org/bugs.debian.org/spool/lock/751741')
called at /usr/local/lib/site_perl/Debbugs/Status.pm line 213
Debbugs::Status::read_bug('bug', 751741, 'lock', 1) called at
/usr/local/lib/site_perl/Debbugs/Status.pm line 465
Debbugs::Status::lock_read_all_merged_bugs('bug', 751741) called at
/usr/local/lib/site_perl/Debbugs/Control.pm line 3671
Debbugs::Control::__begin_control('remove', 0, 'add', 1,
'request_replyto', 'Paul Wise p...@debian.org', 'transcript',
'GLOB(0x3489648)', 'bug', ...) called at
/usr/local/lib/site_perl/Debbugs/Control.pm line 2556
Debbugs::Control::affects('transcript', 'GLOB(0x3489648)', 'requester',
'Paul Wise p...@debian.org', 'request_addr', '751741-sub...@bugs.debian.org',
'request_msgid', '1402913655.477.12.camel@chianamo', 'request_subject', ...)
called at /usr/local/lib/site_perl/Debbugs/Control/Service.pm line 637
eval {...} called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 636
Debbugs::Control::Service::control_line('line', 'affects 751741 gpsd
monopd cups-daemon', 'clonebugs', 'HASH(0x34a12c0)', 'limit',
'HASH(0x34a14e8)', 'common_control_options', 'ARRAY(0x34a15c0)', 'errors', ...)
called at /usr/lib/debbugs/process line 1040
--
751741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751741
751744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751744
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: reassign 751741 to dh-systemd, reassign 751744 to dh-systemd, forcibly merging 751741 751744 ...
Processing commands for cont...@bugs.debian.org: reassign 751741 dh-systemd Bug #751741 [dh-systemd] dh-systemd: postinst snippets should stop foo.socket during upgrades too Bug #751744 [dh-systemd] dh-systemd: postinst snippets should stop foo.socket during upgrades too Ignoring request to reassign bug #751741 to the same package Ignoring request to reassign bug #751744 to the same package reassign 751744 dh-systemd Bug #751744 [dh-systemd] dh-systemd: postinst snippets should stop foo.socket during upgrades too Bug #751741 [dh-systemd] dh-systemd: postinst snippets should stop foo.socket during upgrades too Ignoring request to reassign bug #751744 to the same package Ignoring request to reassign bug #751741 to the same package forcemerge 751741 751744 Bug #751741 [dh-systemd] dh-systemd: postinst snippets should stop foo.socket during upgrades too Bug #751744 [dh-systemd] dh-systemd: postinst snippets should stop foo.socket during upgrades too Bug #751744 [dh-systemd] dh-systemd: postinst snippets should stop foo.socket during upgrades too Merged 751741 751744 retitle 751741 dh-systemd: postinst snippets should stop foo.socket during upgrades too Bug #751741 [dh-systemd] dh-systemd: postinst snippets should stop foo.socket during upgrades too Bug #751744 [dh-systemd] dh-systemd: postinst snippets should stop foo.socket during upgrades too Ignoring request to change the title of bug#751741 to the same title Ignoring request to change the title of bug#751744 to the same title affects 751741 gpsd monopd cups-daemon Bug #751741 [dh-systemd] dh-systemd: postinst snippets should stop foo.socket during upgrades too Bug #751744 [dh-systemd] dh-systemd: postinst snippets should stop foo.socket during upgrades too Ignoring request to set affects of bug 751741 to the same value previously set Ignoring request to set affects of bug 751744 to the same value previously set thanks Stopping processing here. Please contact me if you need assistance. -- 751741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751741 751744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751744 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#752266: systemd: laptop powers down on resume when suspended via power/suspend button
Processing commands for cont...@bugs.debian.org: tags 752266 + moreinfo Bug #752266 [systemd] systemd: laptop powers down on resume when suspended via power/suspend button Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 752266: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752266 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#752104: systemd: tries to run fsck on a mounted filesystem
Processing commands for cont...@bugs.debian.org: forcemerge 751845 752104 Bug #751845 [systemd] seems to run fsck twice Bug #751845 [systemd] seems to run fsck twice Marked as found in versions systemd/204-8. Bug #752104 [systemd] systemd: tries to run fsck on a mounted filesystem Marked as found in versions systemd/204-10. Merged 751845 752104 thanks Stopping processing here. Please contact me if you need assistance. -- 751845: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751845 752104: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752104 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: tagging 746351
Processing commands for cont...@bugs.debian.org: tags 746351 + pending Bug #746351 [systemd] systemd: multi-line syslog messages are truncated Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 746351: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746351 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#748311: marked as done (systemd: unknown operation 'dump' in reportbug script)
Your message dated Tue, 24 Jun 2014 16:04:49 + with message-id e1wztdf-00059r...@franck.debian.org and subject line Bug#748311: fixed in systemd 208-2 has caused the Debian Bug report #748311, regarding systemd: unknown operation 'dump' in reportbug script 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.) -- 748311: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748311 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: systemd Version: 208-1 Severity: normal Hi, The reportbug script for systemd prints Unknown operation 'dump' The script calls systemctl dump but the dump operation has been moved to systemd-analyze in v208. James -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-1 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-53 ii libacl1 2.2.52-1 ii libaudit11:2.3.6-1 ii libblkid12.20.1-5.7 ii libc62.18-6 ii libcap2 1:2.22-1.2 ii libcap2-bin 1:2.22-1.2 ii libcryptsetup4 2:1.6.4-4 ii libdbus-1-3 1.8.2-1 ii libgcrypt11 1.5.3-4 ii libkmod2 17-2 ii liblzma5 5.1.1alpha+20120614-2 ii libpam0g 1.1.8-3 ii libselinux1 2.3-1 ii libsystemd-daemon0 208-1 ii libsystemd-journal0 208-1 ii libsystemd-login0208-1 ii libudev1 208-1 ii libwrap0 7.6.q-25 ii sysv-rc 2.88dsf-53 ii udev 208-1 ii util-linux 2.20.1-5.7 Versions of packages systemd recommends: ii libpam-systemd 208-1 Versions of packages systemd suggests: pn systemd-ui none -- no debconf information ---End Message--- ---BeginMessage--- Source: systemd Source-Version: 208-2 We believe that the bug you reported is fixed in the latest version of systemd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 748...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl bi...@debian.org (supplier of updated systemd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 24 Jun 2014 17:45:26 +0200 Source: systemd Binary: systemd systemd-sysv libpam-systemd libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev libsystemd-journal0 libsystemd-journal-dev libsystemd-id128-0 libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev python-systemd systemd-dbg Architecture: source amd64 Version: 208-2 Distribution: experimental Urgency: medium Maintainer: Debian systemd Maintainers pkg-systemd-maintainers@lists.alioth.debian.org Changed-By: Michael Biebl bi...@debian.org Description: gir1.2-gudev-1.0 - libgudev-1.0 introspection data libgudev-1.0-0 - GObject-based wrapper library for libudev libgudev-1.0-dev - libgudev-1.0 development files libpam-systemd - system and service manager - PAM module libsystemd-daemon-dev - systemd utility library - development files libsystemd-daemon0 - systemd utility library libsystemd-id128-0 - systemd 128 bit ID utility library libsystemd-id128-dev - systemd 128 bit ID utility library - development files libsystemd-journal-dev - systemd journal utility library - development files libsystemd-journal0 - systemd journal utility library libsystemd-login-dev - systemd login utility library - development files libsystemd-login0 - systemd login utility library libudev-dev - libudev development files libudev1 - libudev shared library libudev1-udeb - libudev shared library (udeb) python-systemd - python bindings for systemd systemd- system and service manager systemd-dbg - system and service manager (debug symbols) systemd-sysv - system and service manager - SysV links udev
Bug#751472: marked as done (/lib/lsb/init-functions.d/40-systemd: init script integration: set +e; set +u changes behavior of init scripts)
Your message dated Tue, 24 Jun 2014 15:44:35 +
with message-id e1wzstf-0001qs...@franck.debian.org
and subject line Bug#751472: fixed in systemd 204-11
has caused the Debian Bug report #751472,
regarding /lib/lsb/init-functions.d/40-systemd: init script integration: set
+e; set +u changes behavior of init scripts
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.)
--
751472: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751472
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: systemd
Version: 208-1
Severity: normal
File: /lib/lsb/init-functions.d/40-systemd
/lib/lsb/init-functions.d/40-systemd unconditionally uses set +e; set
+u. This can change the behavior of init scripts that use set -e
and/or set -u.
The systemd integration should not rely on set +e or set +u, but
instead work correctly in all cases:
Instead of set +u, access variables in a way that doesn't trigger an
exception when the variable is not set: ${foo:-} will result in an
empty string when foo is not set.
Instead of set +e, explicitly catch commands that might fail, for example
something-that-might-fail || :
It is still okay to use set +e; set +u in the redirection code when
control is not returned to the init script.
I've attached an *untested* patch implementing what I described
above. Not sure if I missed anything.
Ansgar
diff --git a/debian/init-functions.d/40-systemd b/debian/init-functions.d/40-systemd
index a213afc..809ec7a 100644
--- a/debian/init-functions.d/40-systemd
+++ b/debian/init-functions.d/40-systemd
@@ -1,21 +1,18 @@
# -*-Shell-script-*-
# /lib/lsb/init-functions
+_use_systemctl=0
if [ -d /run/systemd/system ]; then
-# Some init scripts use set -e and set -u, we don't want that
-# here
-set +e
-set +u
-if [ -n $DPKG_MAINTSCRIPT_PACKAGE ]; then
+if [ -n ${DPKG_MAINTSCRIPT_PACKAGE:-} ]; then
# If we are called by a maintainer script, chances are good that a
# new or updated sysv init script was installed. Reload daemon to
# pick up any changes.
-systemctl daemon-reload
+systemctl daemon-reload || :
fi
# Redirect SysV init scripts when executed by the user
-if [ $PPID -ne 1 ] [ -z $init ] [ -z $_SYSTEMCTL_SKIP_REDIRECT ]; then
+if [ $PPID -ne 1 ] [ -z ${init:-} ] [ -z ${_SYSTEMCTL_SKIP_REDIRECT:-} ]; then
case $(readlink -f $0) in
/etc/init.d/*)
_use_systemctl=1
@@ -23,7 +20,7 @@ if [ -d /run/systemd/system ]; then
# but can through the init script.
prog=${0##*/}
service=${prog%.sh}.service
-if [ $(systemctl -p CanReload show $service 2/dev/null) = CanReload=no ] [ $1 = reload ]; then
+if [ $(systemctl -p CanReload show $service 2/dev/null) = CanReload=no ] [ ${1:-} = reload ]; then
_use_systemctl=0
fi
;;
@@ -31,8 +28,6 @@ if [ -d /run/systemd/system ]; then
else
export _SYSTEMCTL_SKIP_REDIRECT=true
fi
-else
-_use_systemctl=0
fi
systemctl_redirect () {
@@ -73,6 +68,11 @@ systemctl_redirect () {
}
if [ $_use_systemctl = 1 ]; then
+# Some init scripts use set -e and set -u, we don't want that
+# here
+set +e
+set +u
+
if [ x$1 = xstart -o \
x$1 = xstop -o \
x$1 = xrestart -o \
---End Message---
---BeginMessage---
Source: systemd
Source-Version: 204-11
We believe that the bug you reported is fixed in the latest version of
systemd, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 751...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Biebl bi...@debian.org (supplier of updated systemd package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 24 Jun 2014 17:03:43 +0200
Source: systemd
Binary: systemd systemd-sysv libpam-systemd libsystemd-login0
libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev
libsystemd-journal0 libsystemd-journal-dev libsystemd-id128-0
libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb
libgudev-1.0-0 gir1.2
Bug#747741: marked as done (systemd-sysv, systemd: please clairfy /sbin/init choice in package description)
Your message dated Tue, 24 Jun 2014 15:44:35 + with message-id e1wzstf-0001qg...@franck.debian.org and subject line Bug#747741: fixed in systemd 204-11 has caused the Debian Bug report #747741, regarding systemd-sysv, systemd: please clairfy /sbin/init choice in package description 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.) -- 747741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747741 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: systemd Version: 204-8 Severity: normal Hi, I just spent way too much time cursing the polkit - libpam-systemd - systemd dependence that seemed to want to switch a computer I admin to boot systemd, and debugging and trying to find ways around that. I only understood what was happening when I found https://lists.debian.org/debian-user/2014/05/msg00576.html , which proves I was not the only one confused this way. Please make the package descriptions of systemd and systemd-sysv mention that the latter switches /sbin/init to systemd, not the former. Right now systemd's description says nothing specific, and systemd-sysv's says manual page and links for replacing sysvinit, which was not at all clear to me. Of course, systemd's README.Debian explains the situtation, but I can't read that without installing systemd, which I'm certainly not going to do while I think it replaces the init system on a machine I don't have hands on. So it really needs to be in the package description. I suggest adding something like the following to systemd's description: This package does/contains foo* , but will not actually boot your computer using systemd.[ Install the systemd-sysv package for that.] And change systemd-sysv's to something like This package provides the manual pages and links needed for systemd to replace sysvinit, including /sbin/init, and thus causes your computer to boot using systemd. Thanks, Jan *) I obviously still don't understand what the purpose of the package systemd is. If it doesn't cause systemd services to be run, why is it a dependency of libpam-systemd, and if it does, then why is systemd-shim needed? But I don't really care either, as long as it doesn't mess with init then I'll pretend it's just a weird library dependency of hplip. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (800, 'testing'), (550, 'unstable'), (10, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: systemd Source-Version: 204-11 We believe that the bug you reported is fixed in the latest version of systemd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 747...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl bi...@debian.org (supplier of updated systemd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 24 Jun 2014 17:03:43 +0200 Source: systemd Binary: systemd systemd-sysv libpam-systemd libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev libsystemd-journal0 libsystemd-journal-dev libsystemd-id128-0 libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev python-systemd systemd-dbg Architecture: source amd64 Version: 204-11 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers pkg-systemd-maintainers@lists.alioth.debian.org Changed-By: Michael Biebl bi...@debian.org Description: gir1.2-gudev-1.0 - libgudev-1.0 introspection data libgudev-1.0-0 - GObject-based wrapper library for libudev libgudev-1.0-dev - libgudev-1.0 development files libpam-systemd - system and service manager - PAM module libsystemd-daemon-dev - systemd utility library - development files libsystemd-daemon0 - systemd utility library libsystemd-id128-0 - systemd 128 bit ID utility library libsystemd-id128-dev - systemd 128 bit ID utility library - development files libsystemd-journal
Bug#748355: marked as done (Upgrading from sysvinit/wheezy to systemd-sysv/sid impossible due to loop)
Your message dated Tue, 24 Jun 2014 15:44:35 + with message-id e1wzstf-0001qm...@franck.debian.org and subject line Bug#748355: fixed in systemd 204-11 has caused the Debian Bug report #748355, regarding Upgrading from sysvinit/wheezy to systemd-sysv/sid impossible due to loop 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.) -- 748355: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748355 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: systemd-sysv Version: 204-10 Severity: serious Justification: triggers a debian-policy defined dpkg error (§7.4) X-Debbugs-CC: pkg-sysvinit-de...@lists.alioth.debian.org Hi *, I got a report (now…) that apt segfaults in a wheezy → sid upgrade. Debugging this leads to the following universe (hugely simplified): Package: sysvinit Version: 1 Essential: yes Package: sysvinit Version: 2 Pre-Depends: sysvinit-core | systemd-sysv Essential: yes Package: sysvinit-core Version: 2 Package: systemd-sysv Version: 2 Conflicts: sysvinit ( 2) Breaks: sysvinit-core If we have sysvinit v1 installed and want to install systemd-sysv now we not only run into the previously mentioned segfault, but, if the segfault would not appear and dpkg actually executed we get: | Selecting previously unselected package systemd-sysv. | dpkg: considering deconfiguration of sysvinit, which would be broken by installation of systemd-sysv ... | dpkg: no, sysvinit is essential, will not deconfigure | it in order to enable installation of systemd-sysv | dpkg: error processing archive /tmp/tmp.W9nkJhRQvg/aptarchive/pool/systemd-sysv_2_amd64.deb (--unpack): | installing systemd-sysv would break existing software | Errors were encountered while processing: | /tmp/tmp.W9nkJhRQvg/aptarchive/pool/systemd-sysv_2_amd64.deb | E: Sub-process fakeroot returned an error code (1) The reason is simple: Unpacking systemd-sysv is not possible before we have gotten right of sysvinit 1. The normal solution is to just upgrade it to version 2, but this requires us to first unpack systemd-sysv - loop. The other solution is to temporary remove sysvinit 1 and reinstall it later on. Such a practice isn't allowed for essential packages. Debian policy §7.4 even explicitly defines that dpkg should error out if it is attempt, which is what you get at the moment (minus a segfault). Note that Breaks will not work either (same message). I see two probably good-enough solutions: 1. Downgrade Pre-Depends in sysvinit to a Depends Technical it isn't entirely correct as it would be allowed to have an unpacked sysvinit then, but not a working init system. In theory I assume this window of opportunity to be very small as APT treats Depends of a (pseudo-)essential package if at all possible as Pre-Depends and also tries to configure them as soon as possible. In practice it should mean that they are unpacked in the same dpkg call, so if you can write your maintainerscripts without requiring runlevel, shutdown and co this should work out. 2. Remove Conflicts: sysvinit ( 2) from systemd-sysv It is only for the file replacement, right? (In which case Breaks would have equally (not) worked). dpkg is happy as long as it has Replaces, so we talk mostly about partial upgrades and downgrades here and while I tried to come up with a good scenario in which something would break, I failed to find one given that both seem to work with the binaries of the other at least somehow. (This 2nd solution is btw deployed in sysvinit-core, so just in case someone requests adding a Conflicts/Breaks here: be careful) I guess 'solution' 2 is preferable, so I report against systemd, but have CC'ed sysvinit maintainers. Feel free to disagree and reassign and/or invent another (better) solution. Best regards David Kalnischkies P.S.: Full-disclosure bla bla: At the moment a third solution would be for apt to temporary install sysvinit-core, to be able to install the new version of sysvinit, so that it in turn can remove sysvinit-core again and replace it with systemd-sysv. Yes, that would be insane and is not even close to be supportable as a scenario by apt … signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: systemd Source-Version: 204-11 We believe that the bug you reported is fixed in the latest version of systemd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 748...@bugs.debian.org
Bug#751589: marked as done (sysvinit-core: /sbin/init missing after switching from systemd to sysvinit)
Your message dated Tue, 24 Jun 2014 15:44:35 + with message-id e1wzstf-0001qy...@franck.debian.org and subject line Bug#751589: fixed in systemd 204-11 has caused the Debian Bug report #751589, regarding sysvinit-core: /sbin/init missing after switching from systemd to sysvinit 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.) -- 751589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751589 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sysvinit-core Version: 2.88dsf-53.2 Severity: critical After a failed switch to systemd today (Debian bug #751585), I tried to switch back to sysvinit but found /sbin/init missing after a reboot, which of course prevented the system from booting. /sbin was available in the emergency shell and contained some files, but 'init' wasn't there. 'dpkg -L sysvinit-core' ended at the line '/sbin' (i.e., it was missing /sbin/shutdown, /sbin/init, etc.). I eventually figured out to run 'dpkg -i' on that .deb; this restored /sbin/init, and then I was able to boot the system normally. I've attached dpkg and apt logfiles, starting with the systemd installation. Note that systemd printed systemd is the active init system, please switch to another before removing systemd when I tried to remove it; but it gave no guidance on how to do this. Did this mean to install sysvinit and reboot (which is what I did)? Was I supposed to do something with update-alternatives or similar, or was I actually supposed to be running sysvinit somehow before rebooting? It's possible this is actually a bug in dpkg, apt, or systemd. - Michael -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sysvinit-core depends on: ii debconf [debconf-2.0] 1.5.53 ii debianutils4.4 ii initscripts2.88dsf-53 ii libc6 2.19-1 ii libselinux12.3-1 ii libsepol1 2.3-1 ii sysv-rc2.88dsf-53 ii sysvinit-utils 2.88dsf-53 sysvinit-core recommends no packages. sysvinit-core suggests no packages. -- debconf information: sysvinit/hurd-fix-inittab: 2014-06-14 08:58:14 startup archives unpack 2014-06-14 08:58:15 install systemd:amd64 none 204-10 2014-06-14 08:58:15 status half-installed systemd:amd64 204-10 2014-06-14 08:58:15 status triggers-pending dbus:amd64 1.8.2-1 2014-06-14 08:58:15 status half-installed systemd:amd64 204-10 2014-06-14 08:58:15 status triggers-pending man-db:amd64 2.6.7.1-1 2014-06-14 08:58:16 status triggers-pending dbus:amd64 1.8.2-1 2014-06-14 08:58:16 status unpacked systemd:amd64 204-10 2014-06-14 08:58:16 status unpacked systemd:amd64 204-10 2014-06-14 08:58:16 trigproc dbus:amd64 1.8.2-1 1.8.2-1 2014-06-14 08:58:16 status half-configured dbus:amd64 1.8.2-1 2014-06-14 08:58:17 status installed dbus:amd64 1.8.2-1 2014-06-14 08:58:17 trigproc man-db:amd64 2.6.7.1-1 2.6.7.1-1 2014-06-14 08:58:17 status half-configured man-db:amd64 2.6.7.1-1 2014-06-14 08:58:20 status installed man-db:amd64 2.6.7.1-1 2014-06-14 08:58:21 startup packages configure 2014-06-14 08:58:21 configure systemd:amd64 204-10 none 2014-06-14 08:58:21 status unpacked systemd:amd64 204-10 2014-06-14 08:58:21 status unpacked systemd:amd64 204-10 2014-06-14 08:58:21 status unpacked systemd:amd64 204-10 2014-06-14 08:58:21 status unpacked systemd:amd64 204-10 2014-06-14 08:58:21 status unpacked systemd:amd64 204-10 2014-06-14 08:58:21 status unpacked systemd:amd64 204-10 2014-06-14 08:58:21 status triggers-pending dbus:amd64 1.8.2-1 2014-06-14 08:58:21 status unpacked systemd:amd64 204-10 2014-06-14 08:58:21 status unpacked systemd:amd64 204-10 2014-06-14 08:58:21 status unpacked systemd:amd64 204-10 2014-06-14 08:58:21 status unpacked systemd:amd64 204-10 2014-06-14 08:58:21 status unpacked systemd:amd64 204-10 2014-06-14 08:58:21 status unpacked systemd:amd64 204-10 2014-06-14 08:58:22 status half-configured systemd:amd64 204-10 2014-06-14 08:58:22 status triggers-awaited systemd:amd64 204-10 2014-06-14 08:58:22 trigproc dbus:amd64 1.8.2-1 none 2014-06-14 08:58:22 status half-configured dbus:amd64 1.8.2-1 2014-06-14 08:58:22 status installed systemd:amd64 204-10 2014-06-14 08:58:22 status installed dbus:amd64 1.8.2-1 2014-06-14 08:58:22 startup packages remove 2014-06-14 08:58:22 status installed sysvinit-core:amd64 2.88dsf-53 2014-06-14 08:58:22 status installed
Bug#739113: marked as done (systemd: Please document Vcs-Git workflow in README.source)
Your message dated Tue, 24 Jun 2014 15:44:35 + with message-id e1wzstf-0001q4...@franck.debian.org and subject line Bug#739113: fixed in systemd 204-11 has caused the Debian Bug report #739113, regarding systemd: Please document Vcs-Git workflow in README.source 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.) -- 739113: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739113 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: systemd Version: 204-7 Severity: wishlist Hi, after checking out the Vcs-Git for this package, it's not immediately clear how to e.g. build it from Git after applying an additional patch. I assume one shall use debian/systemd-hack-up-the-source.hook, and perhaps gitpkg too, but I'm not sure how. How about giving a few hints about this in debian/README.source? If someone gave me enough hints about it, I wouldn't mind testing it and writing the actual README.source. (Actually, I'm interested in the answer both because I'd like to test some systemd patches, and also because I suspect we might want to use the same workflow in the upcoming pkg-otr team.) Thank you for maintaining systemd in Debian. Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc ---End Message--- ---BeginMessage--- Source: systemd Source-Version: 204-11 We believe that the bug you reported is fixed in the latest version of systemd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 739...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl bi...@debian.org (supplier of updated systemd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 24 Jun 2014 17:03:43 +0200 Source: systemd Binary: systemd systemd-sysv libpam-systemd libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev libsystemd-journal0 libsystemd-journal-dev libsystemd-id128-0 libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev python-systemd systemd-dbg Architecture: source amd64 Version: 204-11 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers pkg-systemd-maintainers@lists.alioth.debian.org Changed-By: Michael Biebl bi...@debian.org Description: gir1.2-gudev-1.0 - libgudev-1.0 introspection data libgudev-1.0-0 - GObject-based wrapper library for libudev libgudev-1.0-dev - libgudev-1.0 development files libpam-systemd - system and service manager - PAM module libsystemd-daemon-dev - systemd utility library - development files libsystemd-daemon0 - systemd utility library libsystemd-id128-0 - systemd 128 bit ID utility library libsystemd-id128-dev - systemd 128 bit ID utility library - development files libsystemd-journal-dev - systemd journal utility library - development files libsystemd-journal0 - systemd journal utility library libsystemd-login-dev - systemd login utility library - development files libsystemd-login0 - systemd login utility library libudev-dev - libudev development files libudev1 - libudev shared library libudev1-udeb - libudev shared library (udeb) python-systemd - python bindings for systemd systemd- system and service manager systemd-dbg - system and service manager (debug symbols) systemd-sysv - system and service manager - SysV links udev - /dev/ and hotplug management daemon udev-udeb - /dev/ and hotplug management daemon (udeb) Closes: 739113 746351 747741 748355 751472 751589 Changes: systemd (204-11) unstable; urgency=medium . [ Martin Pitt ] * Explain patch management in debian/README.source. (Closes: #739113) * Replace Always probe cpu support drivers patch with cherry-picked upstream fix which is more general. * Advertise hibernation only if there's enough free swap. Patches backported from current upstream. (LP: #1313522) * Fix typo in sg loading rule to make it actually work. . [ Michael Biebl ] * Make no-patch-numbers the default for gbp-pq. * Cherry-pick upstream fix to properly
Processed: tagging 746578
Processing commands for cont...@bugs.debian.org: tags 746578 + wontfix Bug #746578 [libpam-systemd] libpam-systemd: for upgrade safety, swap or-dependency to systemd-shim|systemd-sysv Added tag(s) wontfix. thanks Stopping processing here. Please contact me if you need assistance. -- 746578: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746578 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: tagging 751622
Processing commands for cont...@bugs.debian.org: tags 751622 - moreinfo Bug #751622 [systemd] systemd: shows unnecessary password prompts for encrypted disks Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 751622: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751622 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#752765: systemd: wrong path in man systemd-suspend.service(8)
Processing commands for cont...@bugs.debian.org: reassign 752765 src:systemd Bug #752765 [systemd] systemd: wrong path in man systemd-suspend.service(8) Bug reassigned from package 'systemd' to 'src:systemd'. No longer marked as found in versions systemd/204-8. Ignoring request to alter fixed versions of bug #752765 to the same values previously set forcemerge 717491 752765 Bug #717491 [src:systemd] documentation: file references all point to /usr/lib Bug #725621 [src:systemd] systemd-suspend.service(8) mentions wrong path for system-sleep directory Bug #745793 [src:systemd] [udev] man page bug - wrong system rules path Bug #752765 [src:systemd] systemd: wrong path in man systemd-suspend.service(8) Marked as found in versions systemd/204-1. Bug #725621 [src:systemd] systemd-suspend.service(8) mentions wrong path for system-sleep directory Bug #745793 [src:systemd] [udev] man page bug - wrong system rules path Merged 717491 725621 745793 752765 thanks Stopping processing here. Please contact me if you need assistance. -- 717491: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717491 725621: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725621 745793: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745793 752765: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752765 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#752744: systemd: consistently blocks suspend/reboot after upgrade
Processing commands for cont...@bugs.debian.org: reassign 752744 xfce4-session Bug #752744 [systemd] systemd: consistently blocks suspend/reboot after upgrade Bug reassigned from package 'systemd' to 'xfce4-session'. No longer marked as found in versions systemd/204-12. Ignoring request to alter fixed versions of bug #752744 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 752744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752744 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: tagging 732981
Processing commands for cont...@bugs.debian.org: tags 732981 + wontfix Bug #732981 [systemd] ExecStart et al should be capable of honouring PATH Added tag(s) wontfix. thanks Stopping processing here. Please contact me if you need assistance. -- 732981: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732981 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 (with 1 errors): forcibly merging 752259 747112
Processing commands for cont...@bugs.debian.org:
forcemerge 752259 747112
Bug #752259 {Done: Michael Biebl bi...@debian.org} [systemd] systemd: User
interaction regarding Ordering cycle found: D-Bus System Message Bus Socket
Unable to merge bugs because:
package of #747112 is 'systemd-sysv' not 'systemd'
Failed to forcibly merge 752259: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x1e3b550)',
'requester', 'Michael Biebl bi...@debian.org', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid',
'1403916098-3550-bts-bi...@debian.org', 'request_subject', ...) called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 552
eval {...} called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 551
Debbugs::Control::Service::control_line('line', undef, 'clonebugs',
'HASH(0x1db30b8)', 'limit', 'HASH(0x1db2aa0)', 'common_control_options',
'ARRAY(0x1db2ae8)', 'errors', ...) called at /usr/lib/debbugs/service line 474
thanks
Stopping processing here.
Please contact me if you need assistance.
--
747112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747112
752259: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752259
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: tagging 735583, severity of 735583 is minor
Processing commands for cont...@bugs.debian.org: tags 735583 + wontfix Bug #735583 [systemd] systemd - Always succesful cryptdisks-early.service and cryptdisks.service Added tag(s) wontfix. severity 735583 minor Bug #735583 [systemd] systemd - Always succesful cryptdisks-early.service and cryptdisks.service Severity set to 'minor' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 735583: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735583 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: severity of 750909 is normal
Processing commands for cont...@bugs.debian.org:
severity 750909 normal
Bug #750909 {Done: Michael Biebl em...@michaelbiebl.de} [src:systemd]
systemd: breaks a big part of my system
Severity set to 'normal' from 'critical'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
750909: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750909
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: fixed 743157 in 208-4
Processing commands for cont...@bugs.debian.org: fixed 743157 208-4 Bug #743157 [systemd] systemd: disables networking permanently during tried suspend Marked as fixed in versions systemd/208-4. thanks Stopping processing here. Please contact me if you need assistance. -- 743157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743157 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#747749: marked as done (systemd: closing lid suddenly suspends the machine)
Your message dated Sat, 28 Jun 2014 03:09:05 +0200 with message-id 53ae15b1.10...@debian.org and subject line systemd: closing lid suddenly suspends the machine has caused the Debian Bug report #747749, regarding systemd: closing lid suddenly suspends the machine 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.) -- 747749: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747749 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: systemd Version: 204-10 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, I switched from sysvinit to systemd and now, if I close the lid, my machine suddenly suspends. For me this means, that the data of my current session is lost, since there are some problems with suspend with my machine. This is unspected behaviour, that at least I would not expect from just changing the init system, since the init system should not have to do anything with events like closing the lid. I was able to restore the old behaviour (doing nothing) by editing the HandleLidSwitch entry in /etc/systemd/logind.conf but I think, that should not be necessary. I also have a keybinding, so that pressing the XF86Sleep key, hibernates the machine to disk, but now it first suspends and after waking up from the suspend, the machine is hibernated (to disk) since systemd also silently takes over control over that key event. This is also not behaviour I would expect from changing the init systemd. Therefore, please consider changing the default to doing nothing when doing this actions, so that others do not get this unexpected behaviour and experience data loss like I did. With best regards, Julian Wollrath - -- Package-specific info: - -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.15.0-rc5 (SMP w/2 CPU cores) 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-1 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-53 ii libacl1 2.2.52-1 ii libaudit11:2.3.6-1 ii libc62.18-5 ii libcap2 1:2.22-1.2 ii libcap2-bin 1:2.22-1.2 ii libcryptsetup4 2:1.6.4-4 ii libdbus-1-3 1.8.2-1 ii libgcrypt11 1.5.3-4 ii libkmod2 17-2 ii liblzma5 5.1.1alpha+20120614-2 ii libpam0g 1.1.8-3 ii libselinux1 2.2.2-2 ii libsystemd-daemon0 204-10 ii libsystemd-journal0 204-10 ii libsystemd-login0204-10 ii libudev1 204-10 ii libwrap0 7.6.q-25 ii sysv-rc 2.88dsf-53 ii udev 204-10 ii util-linux 2.20.1-5.7 Versions of packages systemd recommends: pn libpam-systemd none Versions of packages systemd suggests: pn systemd-ui none - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJTb4ZqAAoJEFl2dmpRMS8zW58H/j3M9KZn7MOcoA9re9M+v1LR ivkmv7ElFGPWtxmKX+S9XyaVHhG/OLz1REqgwAZSaYvNT8vpEMkJ+RHirxbZS+ec gi6d8wXqDdmgBicVjjylEerI2LddsiosiawvTarsyf5m+t1F212Cr/i7mM4l8Bge +Lobh9aDRz1L4a2f6arAXIFqSOlFsJj2C2j8uBngzewaz1Zp4kn1nVuR7xsw+hQ/ NMnyJQmHyDCJndItLdPhVSRhgx/hDwRc3BQNDFesw+Pg8uRs7dPSzhA6aHXXVR/F 2E6++G2X57P0e85rGuLOfMA+bvnXlpDDLMtMvC7nuKIOCdfTWdyNDuXnFuA29J0= =2P4/ -END PGP SIGNATURE- [OVERRIDDEN] /etc/systemd/system/sockets.target.wants → /lib/systemd/system/sockets.target.wants Only in /etc/systemd/system/sockets.target.wants: acpid.socket Only in /etc/systemd/system/sockets.target.wants: cups.socket Only in /lib/systemd/system/sockets.target.wants: dbus.socket Only in /etc/systemd/system/sockets.target.wants: lvm2-lvmetad.socket Only in /lib/systemd/system/sockets.target.wants: systemd-initctl.socket Only in /lib/systemd/system/sockets.target.wants: systemd-journald.socket Only in /lib/systemd/system/sockets.target.wants: systemd-shutdownd.socket Only in /lib/systemd/system/sockets.target.wants: systemd-udevd-control.socket Only in /lib/systemd/system/sockets.target.wants: systemd-udevd-kernel.socket [OVERRIDDEN] /etc/systemd/system/multi-user.target.wants → /lib/systemd/system/multi-user.target.wants Only in /etc/systemd/system/multi-user.target.wants: cups.path Only in /lib/systemd/system/multi-user.target.wants: dbus.service Only in /lib/systemd/system/multi-user.target.wants: getty.target Only in /etc/systemd/system/multi
Bug#600112: marked as done (Units generated from virtual names LSB header have status error)
Your message dated Sat, 28 Jun 2014 14:29:22 +0200 with message-id 53aeb522.8060...@debian.org and subject line Units generated from virtual names LSB header have status error has caused the Debian Bug report #600112, regarding Units generated from virtual names LSB header have status error 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.) -- 600112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: systemd Version: 11-1 Severity: minor -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi again, this does not seem to hurt, but its confusing and probably still something that should be fixed. It seems that for names appearing in the LSB headers of init scripts, if there are no scripts actually named that way, systemd generates failing units: $ systemctl --all --full|grep error auditd.serviceerror inactive dead auditd.service autofs.serviceerror inactive dead autofs.service avahi.service error inactive dead avahi.service clamav-daemon.service error inactive dead clamav-daemon.service devfsd.serviceerror inactive dead devfsd.service display-manager.service error inactive dead display-manager.service evms.service error inactive dead evms.service glibc.service error inactive dead glibc.service greylist.service error inactive dead greylist.service hal.service error inactive dead hal.service kbd.service error inactive dead kbd.service kdm.service error inactive dead kdm.service ldm.service error inactive dead ldm.service lvm.service error inactive dead lvm.service mdadm-raid.serviceerror inactive dead mdadm-raid.service multipath-tools-boot.service error inactive dead multipath-tools-boot.service mysql.service error inactive dead mysql.service network-manager.service error inactive dead network-manager.service nfs-common.serviceerror inactive dead nfs-common.service nodm.service error inactive dead nodm.service nscd.service error inactive dead nscd.service raid2.service error inactive dead raid2.service samba.service error inactive dead samba.service sdm.service error inactive dead sdm.service spamassassin.service error inactive dead spamassassin.service uptimed-init.service error inactive dead uptimed-init.service wdm.service error inactive dead wdm.service xdm.service error inactive dead xdm.service ypbind.serviceerror inactive dead ypbind.service all.targeterror inactive dead all.target Just for reference, here is the show information for one of those: $ systemctl show nodm.service Id=nodm.service Names=nodm.service Before=bootlogs.service After=openvpn.service Description=nodm.service LoadState=error ActiveState=inactive SubState=dead CanStart=yes CanStop=yes CanReload=no CanIsolate=no RecursiveStop=no StopWhenUnneeded=no RefuseManualStart=no RefuseManualStop=no AllowIsolate=no DefaultDependencies=yes NeedDaemonReload=no JobTimeoutUSec=0 Type=simple Restart=no NotifyAccess=none RestartUSec=100ms TimeoutUSec=1min UMask=0002 LimitCPU=18446744073709551615 LimitFSIZE=18446744073709551615 LimitDATA=18446744073709551615 LimitSTACK=18446744073709551615 LimitCORE=18446744073709551615 LimitRSS=18446744073709551615 LimitNOFILE=1024 LimitAS=18446744073709551615 LimitNPROC=46965 LimitMEMLOCK=65536 LimitLOCKS=18446744073709551615 LimitSIGPENDING=46965 LimitMSGQUEUE=819200 LimitNICE=0 LimitRTPRIO=0 LimitRTTIME=18446744073709551615 OOMScoreAdjust=0 Nice=0 IOScheduling=4 CPUSchedulingPolicy=0 CPUSchedulingPriority=0 TimerSlackNSec=5 CPUSchedulingResetOnFork=no NonBlocking=no StandardInput=null StandardOutput=inherit StandardError=inherit SyslogPriority=30 SyslogLevelPrefix=yes SecureBits=0 CapabilityBoundingSetDrop=0 MountFlags=1048576 PrivateTmp=no SameProcessGroup=no KillMode=control-group KillSignal=15 PermissionsStartOnly=no RootDirectoryStartOnly=no RemainAfterExit=no ExecMainPID=0 ExecMainCode=0 ExecMainStatus=0 MainPID=0 ControlPID=0 SysVStartPriority=-1 Greetings, Joachim - -- System Information: Debian Release: squeeze/sid
Processed: affects 724796
Processing commands for cont...@bugs.debian.org: affects 724796 rsyslog Bug #724796 [systemd] systemd loses track of rsyslog state when syslog.service is replaced during upgrade Added indication that 724796 affects rsyslog thanks Stopping processing here. Please contact me if you need assistance. -- 724796: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724796 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: tagging 665396, bug 665396 is forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=80686 ...
Processing commands for cont...@bugs.debian.org: tags 665396 + upstream Bug #665396 [systemd] systemd: There should be a way to load a second font Ignoring request to alter tags of bug #665396 to the same tags previously set forwarded 665396 https://bugs.freedesktop.org/show_bug.cgi?id=80686 Bug #665396 [systemd] systemd: There should be a way to load a second font Set Bug forwarded-to-address to 'https://bugs.freedesktop.org/show_bug.cgi?id=80686'. close 665396 Bug #665396 [systemd] systemd: There should be a way to load a second font Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 665396: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665396 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: tagging 665398, bug 665398 is forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=80687 ...
Processing commands for cont...@bugs.debian.org: tags 665398 + upstream Bug #665398 [systemd] systemd: should configure the widthheight of the console Ignoring request to alter tags of bug #665398 to the same tags previously set forwarded 665398 https://bugs.freedesktop.org/show_bug.cgi?id=80687 Bug #665398 [systemd] systemd: should configure the widthheight of the console Set Bug forwarded-to-address to 'https://bugs.freedesktop.org/show_bug.cgi?id=80687'. tags 665398 + wontfix Bug #665398 [systemd] systemd: should configure the widthheight of the console Added tag(s) wontfix. thanks Stopping processing here. Please contact me if you need assistance. -- 665398: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665398 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#753357: marked as done (Power button broken due to systemd stealthily installed)
Your message dated Tue, 01 Jul 2014 01:13:05 +0200 with message-id 53b1ef01.5070...@debian.org and subject line Re: Bug#753357: Power button broken due to systemd stealthily installed has caused the Debian Bug report #753357, regarding Power button broken due to systemd stealthily installed 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.) -- 753357: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753357 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: systemd Version: 204-8 After a recent upgrade, the power button on my laptop stopped doing anything useful. It turned out that a recent upgrade had installed systemd, but without replacing init with it. The powerbtn-acpi-support.sh script was detecting a running systemd-logind, and therefore doing nothing. Folks, I understand that you're excited about systemd, but this sort of stealthy pulling in of code is something that really pisses people off. If I'd rather not be running 15 lines of code as pid 1, please respect my wishes. -- Juliusz ---End Message--- ---BeginMessage--- Am 30.06.2014 22:04, schrieb Juliusz Chroboczek: Package: systemd Version: 204-8 After a recent upgrade, the power button on my laptop stopped doing anything useful. It turned out that a recent upgrade had installed systemd, but without replacing init with it. The powerbtn-acpi-support.sh script was detecting a running systemd-logind, and therefore doing nothing. Folks, I understand that you're excited about systemd, but this sort of stealthy pulling in of code is something that really pisses people off. If I'd rather not be running 15 lines of code as pid 1, please respect my wishes. If you don't want to run systemd as pid one and you want to use logind, then install systemd-shim. -- 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 ---End Message--- ___ 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#753357: Power button broken due to systemd stealthily installed
Processing commands for cont...@bugs.debian.org:
reopen 753357
Bug #753357 {Done: Michael Biebl bi...@debian.org} [systemd] Power button
broken due to systemd stealthily installed
Bug reopened
Ignoring request to alter fixed versions of bug #753357 to the same values
previously set
thanks
Stopping processing here.
Please contact me if you need assistance.
--
753357: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753357
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#753357: marked as done (Power button broken due to systemd stealthily installed)
Your message dated Tue, 01 Jul 2014 01:29:03 +0200 with message-id 87d2dqm0xs.wl%...@pps.univ-paris-diderot.fr and subject line Re: Bug#753357: Power button broken due to systemd stealthily installed has caused the Debian Bug report #753357, regarding Power button broken due to systemd stealthily installed 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.) -- 753357: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753357 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: systemd Version: 204-8 After a recent upgrade, the power button on my laptop stopped doing anything useful. It turned out that a recent upgrade had installed systemd, but without replacing init with it. The powerbtn-acpi-support.sh script was detecting a running systemd-logind, and therefore doing nothing. Folks, I understand that you're excited about systemd, but this sort of stealthy pulling in of code is something that really pisses people off. If I'd rather not be running 15 lines of code as pid 1, please respect my wishes. -- Juliusz ---End Message--- ---BeginMessage--- reopen 753357 thanks Michael Biebl bi...@debian.org wrote: Folks, I understand that you're excited about systemd, but this sort of stealthy pulling in of code is something that really pisses people off. If you don't want to run systemd as pid one and you want to use logind, then install systemd-shim. Sorry, I'm afraid there was a misunderstanding. I have no wish to run logind. The issue is that apt-get update apt-get dist-upgrade stealthily installed systemd, which broke my system. Fixing the issue was a simple matter of apt-get purge systemd but it took me the best part of an hour (including tracing the acpi scripts) to find what the issue is. Please add some conflicts to the systemd package to make sure it doesn't happen in the future. -- Juliusz---End Message--- ___ 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: fixed 753357 in 204-9
Processing commands for cont...@bugs.debian.org:
fixed 753357 204-9
Bug #753357 {Done: Juliusz Chroboczek j...@pps.univ-paris-diderot.fr}
[systemd] Power button broken due to systemd stealthily installed
Marked as fixed in versions systemd/204-9.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
753357: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753357
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: fix versions for #751589
Processing commands for cont...@bugs.debian.org:
# version tracking doesn't handle multiple packages very well
reassign 751589 systemd 204-6
Bug #751589 {Done: Michael Biebl bi...@debian.org}
[sysvinit-core,systemd-sysv] sysvinit-core: /sbin/init missing after switching
from systemd to sysvinit
Bug reassigned from package 'sysvinit-core,systemd-sysv' to 'systemd'.
No longer marked as found in versions sysvinit/2.88dsf-53 and systemd/204-6.
No longer marked as fixed in versions systemd/204-11.
Bug #751589 {Done: Michael Biebl bi...@debian.org} [systemd] sysvinit-core:
/sbin/init missing after switching from systemd to sysvinit
Marked as found in versions systemd/204-6.
fixed 751589 systemd/204-11
Bug #751589 {Done: Michael Biebl bi...@debian.org} [systemd] sysvinit-core:
/sbin/init missing after switching from systemd to sysvinit
Marked as fixed in versions systemd/204-11.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
751589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751589
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: severity of 753589 is serious
Processing commands for cont...@bugs.debian.org: severity 753589 serious Bug #753589 [systemd] systemd: Missing dependency on glibc? Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 753589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753589 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: notfound 753606 in 204-8
Processing commands for cont...@bugs.debian.org: notfound 753606 204-8 Bug #753606 [libsystemd-journal-dev] libsystemd-journal-dev: unable to install libsystemd-journal-dev=204-8~bpo70+1 Ignoring request to alter found versions of bug #753606 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 753606: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753606 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#753606: libsystemd-journal-dev: unable to install libsystemd-journal-dev=204-8~bpo70+1
Processing commands for cont...@bugs.debian.org: severity 753606 important Bug #753606 [libsystemd-journal-dev] libsystemd-journal-dev: unable to install libsystemd-journal-dev=204-8~bpo70+1 Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 753606: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753606 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: found 753589 in 204-8
Processing commands for cont...@bugs.debian.org: found 753589 204-8 Bug #753589 [systemd] systemd: Missing dependency on glibc? Marked as found in versions systemd/204-8. thanks Stopping processing here. Please contact me if you need assistance. -- 753589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753589 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#753108: marked as done (dh-systemd does not seem to properly handle services when using --name)
Your message dated Sat, 05 Jul 2014 21:02:11 +0200 with message-id x6ha2v4ojw@midna.zekjur.net and subject line Re: Bug#753108: Fwd: Re: Bug#753108: dh-systemd does not seem to properly handle services when using --name has caused the Debian Bug report #753108, regarding dh-systemd does not seem to properly handle services when using --name 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.) -- 753108: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753108 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: dh-systemd Version: 1.19 Am 29.06.2014 11:49, schrieb Michael Biebl: So quotarpc.service is only supposed to run if rpcbind is installed? I think what you want here then is Wants/After + a Condition [1]. i.e. [Unit] Wants=rpcbind.service After=rpcbind.service ConditionFileIsExecutable=/sbin/rpcbind Btw, I noticed that quotarpc is not enabled by default. Instead dh_systemd creates two sections for quota.service # ls debian/*.service debian/quota.quotarpc.service debian/quota.service # debian/rules dh_systemd_enable dh_systemd_enable --name=quotarpc.service The start section for quotarpc is completely missing. This might be a bug in dh_systemd in how --name= is handled. Michael Stapelberg, could you look into this? 3 Michaels now, I feel like talking to myself :-) Cheers, 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 ---End Message--- ---BeginMessage--- Hi Michael, You used “dh_systemd_enable --name=quotarpc.service”, but I think you are confusing two things here: 1) For deciding which service file dh_systemd_enable should install (like dh_installinit), you should specify --name=quotarpc, i.e. without the .service prefix. This is the handling that is common to debhelper and specifies the per-package files. dh_systemd_enable --name=quotarpc install -p -m644 debian/quota.quotarpc.service debian/quota/lib/systemd/system/quotarpc.service 2) For only generating blocks for specific service files, you need to pass them as arguments: “dh_systemd_enable quota.service” and “dh_systemd_enable --name=quotarpc quotarpc.service”. Likewise for dh_systemd_start. When I use these commands in debian/rules, the package is built correctly for me. Hence, I’m closing this bugreport. Feel free to reopen and explain in detail in case you still have doubts. -- Best regards, Michael---End Message--- ___ 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: severity of 627949 is important, tagging 627949
Processing commands for cont...@bugs.debian.org: severity 627949 important Bug #627949 [systemd] systemd-modules-load: modules with options in /etc/modules are not supported Severity set to 'important' from 'normal' tags 627949 + help Bug #627949 [systemd] systemd-modules-load: modules with options in /etc/modules are not supported Added tag(s) help. thanks Stopping processing here. Please contact me if you need assistance. -- 627949: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627949 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#754059: marked as done ([systemd-sysv] Conflicts with sysvinit-core)
Your message dated Mon, 07 Jul 2014 13:09:35 +0200 with message-id 53ba7fef.1010...@debian.org and subject line Re: Bug#754059: [systemd-sysv] Conflicts with sysvinit-core has caused the Debian Bug report #754059, regarding [systemd-sysv] Conflicts with sysvinit-core 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.) -- 754059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754059 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: systemd-sysv Version: 204-14 Severity: serious systemd-sysv conflicts with sysvinit-core, which is required. This is particularly problematic since libpam-systemd alternatively depends on systemd-sysv. On my testing install, APT's solution when asked to upgrade systemd is to remove sysvinit-core: # LANG=C apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... The following packages were automatically installed and are no longer required: libcolamd2.8.0 lp-solve xulrunner-29 Use 'apt-get autoremove' to remove them. Done The following packages will be REMOVED: sysvinit-core The following NEW packages will be installed: systemd-sysv The following packages will be upgraded: libpam-systemd libsystemd-daemon0 libsystemd-id128-0 libsystemd-journal0 libsystemd-login0 systemd 6 upgraded, 1 newly installed, 1 to remove and 0 not upgraded. Removing libpam-systemd isn't too tempting neither: # LANG=C apt-get remove libpam-systemd Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libcolamd2.8.0 libmodemmanagerqt1 libnetworkmanagerqt1 lp-solve xulrunner-29 Use 'apt-get autoremove' to remove them. The following packages will be REMOVED: colord hplip kde-plasma-desktop libpam-systemd network-manager plasma-nm plasma-widget-networkmanagement policykit-1 policykit-1-gnome printer-driver-postscript-hp udisks2 0 upgraded, 0 newly installed, 11 to remove and 5 not upgraded. I managed to solve this safely by installing systemd-shim. I was surprised to see APT propose the removal of a required package. I didn't test how that would go, but if that's not a problem, something must be wrong with its priority field. I'll save my system from such an experimentation and let others decide if this needs to be reassigned. -- Filipus Klutiero http://www.philippecloutier.com ---End Message--- ---BeginMessage--- Am 07.07.2014 08:56, schrieb Filipus Klutiero: Package: systemd-sysv Version: 204-14 Severity: serious systemd-sysv conflicts with sysvinit-core, which is required. Correct, systemd-sysv has a Conflicts/Replaces against sysvinit-core so it is actually possible to switch between different init systems. This is not a bug but intentional and necessary. Thus closing the bug report. 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 ---End Message--- ___ 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#754984: libpam-systemd 208-6 conflicts with sysvinit-core
Processing commands for cont...@bugs.debian.org: severity 754984 normal Bug #754984 [libpam-systemd] libpam-systemd 208-6 conflicts with sysvinit-core Severity set to 'normal' from 'critical' thanks Stopping processing here. Please contact me if you need assistance. -- 754984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754984 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#755062: systemd: Syslog (contents that journalctl shows) stopped working after upgrading from 204-14 to 208-6
Processing control commands: tag -1 - moreinfo Bug #755062 [systemd] systemd: Syslog (contents that journalctl shows) stopped working after upgrading from 204-14 to 208-6 Removed tag(s) moreinfo. -- 755062: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755062 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#755436: libpam-systemd: When using I hit 'B' to upgrade a systemd dependecy, aptitude crashes
Processing commands for cont...@bugs.debian.org: reassign 755436 aptitude Bug #755436 [libpam-systemd] libpam-systemd: When using I hit 'B' to upgrade a systemd dependecy, aptitude crashes Bug reassigned from package 'libpam-systemd' to 'aptitude'. No longer marked as found in versions systemd/204-8. Ignoring request to alter fixed versions of bug #755436 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 755436: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755436 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 (with 1 errors): Re: Bug#755516: systemd-vconsole-setup.service failed to load: No such file or directory.
Processing commands for cont...@bugs.debian.org: reassign 755516 plymouth Bug #755516 [systemd] systemd-vconsole-setup.service failed to load: No such file or directory. Bug reassigned from package 'systemd' to 'plymouth'. No longer marked as found in versions systemd/208-6. Ignoring request to alter fixed versions of bug #755516 to the same values previously set forcmerge 755194 755516 Unknown command or malformed arguments to command. affects 755194 systemd Bug #755194 [plymouth] systemd-vconsole-setup.service not present but referenced in other services Added indication that 755194 affects systemd thanks Stopping processing here. Please contact me if you need assistance. -- 755194: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755194 755516: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755516 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#755512: systemd-sysv: Can not normal /sbin/shutdown (even as root)
Processing commands for cont...@bugs.debian.org: reassign 755512 systemd Bug #755512 [systemd-sysv] systemd-sysv: Can not normal /sbin/shutdown (even as root) Bug reassigned from package 'systemd-sysv' to 'systemd'. No longer marked as found in versions systemd/208-6. Ignoring request to alter fixed versions of bug #755512 to the same values previously set forcemerge 755373 755512 Bug #755373 [systemd] systemd 208-6 conflicts with ulatencyd Bug #755512 [systemd] systemd-sysv: Can not normal /sbin/shutdown (even as root) Marked as found in versions systemd/208-6. Merged 755373 755512 thanks Stopping processing here. Please contact me if you need assistance. -- 755373: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755373 755512: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755512 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#754064: marked as done (systemd-sysctl is not called with service procps)
Your message dated Mon, 21 Jul 2014 23:34:54 +0200 with message-id 53cd877e.4000...@debian.org and subject line Re: Bug#754064: procps: kernel paramaters not set has caused the Debian Bug report #754064, regarding systemd-sysctl is not called with service procps 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.) -- 754064: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: procps Version: 1:3.3.9-6 Severity: important The /etc/init.d/procps script which is part of procps package no longer runs. If you rely on this script to set important system parameters because they are misconfigured in the Debian distribubtion kernels your system breaks. Thanks Michal -- System Information: Debian Release: 7.5 APT prefers testing APT policy: (910, 'testing'), (900, 'stable'), (500, 'testing'), (410, 'unstable'), (400, 'experimental'), (300, 'saucy-updates'), (300, 'saucy-security'), (300, 'saucy-proposed'), (300, 'saucy-backports'), (300, 'saucy') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.15-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages procps depends on: ii initscripts 2.88dsf-53.2 ii libc6 2.19-4 ii libncurses5 5.9-10 ii libncursesw5 5.9-10 ii libprocps31:3.3.9-5 ii libtinfo5 5.9-10 ii lsb-base 4.1+Debian13 Versions of packages procps recommends: ii psmisc 22.19-1+deb7u1 procps suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Am 17.07.2014 00:55, schrieb Michael Biebl: Am 15.07.2014 18:17, schrieb Michal Suchanek: Excerpts from Michael Biebl's message of Tue Jul 15 15:44:24 +0200 2014: Please also mention which version of systemd and systemd-sysv you have installed. ii systemd 204-14 amd64 system and service manager ii systemd-sysv 204-14 amd64 system and service manager - SysV links The only variables I care about are vm.dirty_background_ratio vm.dirty_ratio which default to 40/60 and I set them to 2/5 That looks like they might be reset by pm-utils. See pm-utils (1.4.1-15) unstable; urgency=medium * laptop-mode: If there is no state file (such as at boot), don't overwrite /proc/sys/vm/ values with fixed kernel defaults, simply do nothing. This allows sysctl.conf to set these values. Thanks to Osamu Aoki! (Closes: #659260) * Add 17-fix-wireless-hook.patch: Fix typo in wireless hook to make enabled check actually work. Thanks to Whoopie! (LP: #1299975) -- Martin Pitt mp...@debian.org Thu, 10 Jul 2014 14:58:31 +0200 If you run touch /etc/pm/power.d/laptop-mode and reboot, is the sysfs value correctly set? I'm closing this bug report since I'm pretty sure it simply was pm-utils re-setting the sysctl value. If you still encounter the problem after upgrade pm-utils (or disabling the laptop_mode hook, please let us know. 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 ---End Message--- ___ 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: systemd: Warning on each reboot: Superblock last write time is in the future
Processing control commands: reassign -1 ntpdate Bug #755722 [systemd] systemd: Warning on each reboot: Superblock last write time is in the future Bug reassigned from package 'systemd' to 'ntpdate'. No longer marked as found in versions systemd/208-6. Ignoring request to alter fixed versions of bug #755722 to the same values previously set retitle -1 ntpdate does not set the RTC when syncing the system clock Bug #755722 [ntpdate] systemd: Warning on each reboot: Superblock last write time is in the future Changed Bug title to 'ntpdate does not set the RTC when syncing the system clock' from 'systemd: Warning on each reboot: Superblock last write time is in the future' -- 755722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755722 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#741252: marked as done (dh-systemd: please merge systemd2init to allow autogenerating shell init scripts)
Your message dated Fri, 25 Jul 2014 00:00:06 + with message-id e1xasve-0001bi...@franck.debian.org and subject line Bug#741252: fixed in init-system-helpers 1.20 has caused the Debian Bug report #741252, regarding dh-systemd: please merge systemd2init to allow autogenerating shell init scripts 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.) -- 741252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741252 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: dh-systemd Version: 1.11~bpo70.1 Severity: wishlist Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Lukas Zapletal from RedHat has built upon my inital commit and we think the script is complete for most cases. Could you merge it from: ssh://git.debian.org/git/collab-maint/systemd2init.git This should allow most packages to just specify: debian/package.service and run: systemd2init package to generate templated debian/package.init O. - -- System Information: Debian Release: 7.4 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dh-systemd depends on: ii debhelper 9.20120909 ii perl 5.14.2-21+deb7u1 dh-systemd recommends no packages. dh-systemd suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlMdtLEACgkQ9OZqfMIN8nN//ACdEtpRvN0Q744uF0GsvU6IIPCz D10AnRYAErRFpluqjIyOcCBd1JhjMA7X =lIbw -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Source: init-system-helpers Source-Version: 1.20 We believe that the bug you reported is fixed in the latest version of init-system-helpers, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 741...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl bi...@debian.org (supplier of updated init-system-helpers package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 24 Jul 2014 23:49:57 +0200 Source: init-system-helpers Binary: init-system-helpers dh-systemd init Architecture: source all amd64 Version: 1.20 Distribution: unstable Urgency: medium Maintainer: pkg-systemd-maintainers pkg-systemd-maintainers@lists.alioth.debian.org Changed-By: Michael Biebl bi...@debian.org Description: dh-systemd - debhelper add-on to handle systemd unit files init - System-V-like init utilities - metapackage init-system-helpers - helper tools for all init systems Closes: 741252 Changes: init-system-helpers (1.20) unstable; urgency=medium . [ Michael Stapelberg ] * Add systemd2init tool which can be used to generate SysV init scripts from systemd .service files. The systemd2init tool requires Augeas, so add a Depends on augeas-tools to dh-systemd. (Closes: #741252) Maintained by Ondřej Surý ond...@debian.org * Clarify dh_systemd_enable documentation (Thanks Michael Meskes for the patch). . [ Michael Biebl ] * Add new init metapackage which ensures that an init system is installed at all times. For now the default is still sysvinit-core. Checksums-Sha1: 1dd26554514c769f71250db73f78acdf918effee 1880 init-system-helpers_1.20.dsc 07cdc675fb292bef4d8028776bff89b98eacc73d 30116 init-system-helpers_1.20.tar.xz eaf594d52c06e6b884094dcf3c18732b19294d5e 13818 init-system-helpers_1.20_all.deb 3cdbad36ac85e536621e1acc50f04915b1c6f247 17808 dh-systemd_1.20_all.deb daf6ff78953510bfde1d840c4f434c6b9be82ab2 4488 init_1.20_amd64.deb Checksums-Sha256: cf67746f1306b4623158c53ed6ea75c1995b148841841b1fe2f6d3d46444a58e 1880 init-system-helpers_1.20.dsc 2a7c40389b04d5eb56238220a34a214e78583326ed16c7211d2f684516537745 30116 init-system-helpers_1.20.tar.xz 294aee3080e4ab8c837eb8c12a9b1c16f419a3ea62511a2101f1996ad82cffaa 13818 init-system-helpers_1.20_all.deb 47be33eb3d09a55bdcb00d13acb275c79cce4cded0601f7f3e45ded9fcedfe63 17808 dh-systemd_1.20_all.deb 5b00dc1170398dab2a0d9806446e57d70e5f82b0dd87226fa5c81e30401a89bc 4488 init_1.20_amd64.deb Files
Processed: affects 627949
Processing commands for cont...@bugs.debian.org: affects 627949 kmod Bug #627949 [systemd] systemd-modules-load: modules with options in /etc/modules are not supported Added indication that 627949 affects kmod thanks Stopping processing here. Please contact me if you need assistance. -- 627949: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627949 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#717540 closed by Michael Biebl bi...@debian.org (Bug#717540: fixed in systemd 208-1)
Processing control commands:
reopen -1
Bug #717540 {Done: Michael Biebl bi...@debian.org} [systemd] systemd: Please
install zsh completion
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions systemd/208-1.
found -1 systemd/208-6
Bug #717540 [systemd] systemd: Please install zsh completion
Marked as found in versions systemd/208-6.
retitle -1 systemd: install zsh completion to the correct place
Bug #717540 [systemd] systemd: Please install zsh completion
Changed Bug title to 'systemd: install zsh completion to the correct place'
from 'systemd: Please install zsh completion'
--
717540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717540
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#717540: closed by Michael Biebl bi...@debian.org (Bug#717540: fixed in systemd 208-1)
Processing control commands: tags -1 + pending Bug #717540 [systemd] systemd: install zsh completion to the correct place Added tag(s) pending. -- 717540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717540 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: systemd invoke-rc.d stop unsafe if socket is activated
Processing commands for cont...@bugs.debian.org:
reassign 736258 dh-systemd
Bug #736258 {Done: Michael Meskes mes...@debian.org} [acpid] acpid fails to
upgrade on amd64
Bug reassigned from package 'acpid' to 'dh-systemd'.
No longer marked as found in versions acpid/1:2.0.20-1 and acpid/1:2.0.21-1.
Ignoring request to alter fixed versions of bug #736258 to the same values
previously set
forcemerge 751741 736258
Bug #751741 [dh-systemd] dh-systemd: postinst snippets should stop foo.socket
during upgrades too
Bug #751744 [dh-systemd] dh-systemd: postinst snippets should stop foo.socket
during upgrades too
Bug #736258 {Done: Michael Meskes mes...@debian.org} [dh-systemd] acpid fails
to upgrade on amd64
Bug reopened
Ignoring request to alter fixed versions of bug #736258 to the same values
previously set
Added indication that 736258 affects acpid,monopd,cups-daemon,gpsd
Bug #751744 [dh-systemd] dh-systemd: postinst snippets should stop foo.socket
during upgrades too
Merged 736258 751741 751744
thanks
Stopping processing here.
Please contact me if you need assistance.
--
736258: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736258
751741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751741
751744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751744
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: severity of 744828 is serious
Processing commands for cont...@bugs.debian.org: severity 744828 serious Bug #744828 [systemd-cron] systemd-cron not running cron jobs. Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 744828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744828 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#744828: marked as done (systemd-cron not running cron jobs.)
Your message dated Mon, 28 Jul 2014 15:09:47 +1000 with message-id 20140728050945.GA5699@frey and subject line 744828 does not apply to Debian has caused the Debian Bug report #744828, regarding systemd-cron not running cron jobs. 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.) -- 744828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: systemd-cron Version: 1.1.1-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I had install systemd back in mid-Feb--had not checked logs until last week. I found that cron jobs were not being run. * What exactly did you do (or not do) that was effective (or ineffective)? I manually installed the newer systemd-cron package from upstream (1.21) corrected it to work with my system. This started to make cron jobs work. My logs indicated that /user/bin/run-parts were not found, so jobs were not run. I then created a link from /bin/run-parts to /usr/bin/run-parts which was the final piece of the puzzle. * What was the outcome of this action? Cron jobs are now running normally. * What outcome did you expect instead? Expected version 1.1.1-1 to run cron jobs normally. I can be contacted to show what I did to make the cron.target(s) run - the changes were very minimal. I run a sid system pull from experimental were it looks like it would be helpful. -- System Information: Debian Release: jessie/sid APT prefers experimental APT policy: (900, 'experimental'), (900, 'unstable'), (850, 'testing'), (500, 'testing-updates'), (500, 'testing-proposed-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-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-cron depends on: ii init-system-helpers 1.18 ii systemd 204-8 systemd-cron recommends no packages. systemd-cron suggests no packages. ---End Message--- ---BeginMessage--- Upstream defaults to /usr/bin/run-parts. Debian's packaging correctly passes --runparts=/bin/run-parts to ./configure. The resulting package as at 1.1.1-1 is correct: cron-daily.service:9: ExecStart=/bin/run-parts /etc/cron.daily cron-hourly.service:9: ExecStart=/bin/run-parts /etc/cron.hourly cron-monthly.service:9: ExecStart=/bin/run-parts /etc/cron.monthly cron-weekly.service:9: ExecStart=/bin/run-parts /etc/cron.weekly Dean wrote: I manually installed [systemd-cron 1.21] from upstream. Clearly Dean simply forgot to pass this option. signature.asc Description: Digital signature ---End Message--- ___ 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#726027: Required-Start: $remote_fs for rcS type services (early boot) can lead to dependency loops
Processing commands for cont...@bugs.debian.org: severity 726027 critical Bug #726027 [systemd] Required-Start: $remote_fs for rcS type services (early boot) can lead to dependency loops Severity set to 'critical' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 726027: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726027 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: severity of 726027 is important
Processing commands for cont...@bugs.debian.org: severity 726027 important Bug #726027 [systemd] Required-Start: $remote_fs for rcS type services (early boot) can lead to dependency loops Severity set to 'important' from 'critical' thanks Stopping processing here. Please contact me if you need assistance. -- 726027: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726027 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#756340: marked as done ([systemd] Boot stops with certain (valid) tmpfs entries in /etc/fstab)
Your message dated Tue, 29 Jul 2014 00:05:44 +0200 with message-id 53d6c938.2000...@debian.org and subject line Re: Bug#756340: [systemd] Boot stops with certain (valid) tmpfs entries in /etc/fstab has caused the Debian Bug report #756340, regarding [systemd] Boot stops with certain (valid) tmpfs entries in /etc/fstab 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.) -- 756340: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756340 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: systemd Version: 208-6 Severity: important --- Please enter the report below this line. --- I had the following two lines in my /etc/fstab and these caused systemd to not boot anymore. tmpfs /var/run tmpfs defaults,relatime,mode=1777 0 0 tmpfs /var/lock tmpfs defaults,relatime,mode=1777 0 0 It complained about /run/systemd/private not being available and indeed the system dbus was not started. With an older kernel (3.12) I got it to get kdm started, but I could not enter my password, it simply did not accept any keyboard input. Switching to the console only worked thanks to the menu option in kdm that I could activate with the mouse. I couldn't install or configure certain new packages, because their post- install scripts again failed due to the missing dbus socket. So after trying to install sysvinit-core and rebooting, booting failed even harder, apparently because of missing /bin/init. I could only fix this in grub with init=/bin/bash After searching for similar problems on a second computer, I found those boot- bugs with encrypted and nfts filesystems in /etc/fstab which brought me into commenting out the tmpfs lines. So there's a few problems here: - systemd does not know how to deal with certain entries in fstab (somewhat OK) - systemd does not report or log any error about that (NOT OK) - systemd breaks the entire system instead of just skipping those entries (NOT OK) - systemd did not allow me to manually start dbus (NOT OK) - (this might go to a different report): packages should be installable without dbus being available I fixed the problem by (re-)installing systemd-shim and systemd-sysv Thanks Carsten PS: yes, I noticed that the tmpfs lines are superfluous by now, since they can be managed through /etc/default/tmpfs. That was not possible when I had added them. --- System information. --- Architecture: amd64 Kernel: Linux 3.14-2-amd64 Debian Release: jessie/sid 500 unstablewww.deb-multimedia.org 500 unstableftp.de.debian.org 500 stable security.debian.org 1 experimentalftp.de.debian.org --- Package information. --- Depends(Version) | Installed -+-= libacl1(= 2.2.51-8) | libaudit1 (= 1:2.2.1) | libblkid1(= 2.17.2) | libc6 (= 2.17) | libcap2(= 2.10) | libcryptsetup4 (= 2:1.4.3) | libdbus-1-3 (= 1.1.1) | libgcrypt11 (= 1.5.1) | libkmod2 (= 5~) | liblzma5(= 5.1.1alpha+20120614) | libpam0g (= 0.99.7.1) | libselinux1 (= 2.1.9) | libsystemd-daemon0 (= 208-6) | libsystemd-journal0(= 208-6) | libudev1(= 189) | libwrap0 (= 7.6-4~) | libsystemd-login0 (= 208-6) | util-linux (= 2.19.1-2) | initscripts (= 2.88dsf-17) | sysv-rc | udev | acl | adduser | libcap2-bin | Recommends (Version) | Installed =-+-=== libpam-systemd| 208-6 Suggests(Version) | Installed =-+-=== systemd-ui| ---End Message--- ---BeginMessage--- Am 28.07.2014 23:52, schrieb g...@leonde.de: Package: systemd Version: 208-6 Severity: important --- Please enter the report below this line. --- I had the following two lines in my /etc/fstab and these caused systemd to not boot anymore. tmpfs /var/run tmpfs defaults,relatime,mode
Bug#734400: marked as done (make libsystemd-daemon available on non-linux architectures)
Your message dated Wed, 30 Jul 2014 11:42:58 +0200 with message-id 53d8be22.1030...@debian.org and subject line Re: Bug#734400: make libsystemd-daemon available on non-linux architectures has caused the Debian Bug report #734400, regarding make libsystemd-daemon available on non-linux architectures 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.) -- 734400: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734400 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: systemd Version: 204-6 Severity: wishlist This is mostly a brain dump, because I am not going to pursue this further until #727708 is resolved at least. In http://bugs.debian.org/727708#2160, I realized that libsystemd-daemon is not actually available on non-linux, even though it can be compiled and all its code turns into a noop. The reason for this is the build system in the first place. A number of non-optional dependencies are linux-only (e.g. libcap) and thus a number of changes are necessary to the autotools config files. I am not sure if those changes would be accepted upstream, and certainly there is potential for them to break given that not many people compile the code on non-linux (only Debian AFAIK). One possibility suggested by Tollef is to have a separate Makefile just for src/libsystemd-daemon/, but then we don’t get all the global flags with which the systemd source is compiled. This may or may not be a deal-breaker, given that all the code turns into a nop anyway. The current (204-6) compiler invocation on Linux for libsystemd-daemon is: ./libtool --tag=CC --mode=link gcc -std=gnu99 -pipe -Wall -Wextra -Wno-inline -Wundef -Wformat=2 -Wformat-security -Wformat-nonliteral -Wlogical-op -Wsign-compare -Wmissing-include-dirs -Wold-style-definition -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wmissing-prototypes -Wstrict-prototypes -Wredundant-decls -Wmissing-declarations -Wmissing-noreturn -Wshadow -Wendif-labels -Wcast-align -Wstrict-aliasing=2 -Wwrite-strings -Wno-long-long -Wno-overlength-strings -Wno-unused-parameter -Wno-missing-field-initializers -Wno-unused-result -Werror=overflow -ffast-math -fno-common -fdiagnostics-show-option -fno-strict-aliasing -fvisibility=hidden -ffunction-sections -fdata-sections -fstack-protector --param=ssp-buffer-size=4 -fvisibility=hidden -DSD_EXPORT_SYMBOLS -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wl,--as-needed -Wl,--no-undefined -Wl,--gc-sections -Wl,-z,relro -Wl,-z,now -version-info 0:10:0 -Wl,--version-script=../src/libsystemd-daemon/libsystemd-daemon.sym -Wl,-z,relro -o libsystemd-daemon.la -rpath /usr/lib/x86_64-linux-gnu src/libsystemd-daemon/libsystemd_daemon_la-sd-daemon.lo -ldl -lrt Maybe there is a way to have a standalone Makefile that is used on non-Linux, which contains the compiler invocation that is used on Linux and is updated by the Debian developer who uploads the package. It’s not a very beautiful solution, but it is as close to the Linux compilation as possible. ---End Message--- ---BeginMessage--- Hi, Marco d'Itri uploaded libsystemd-dummy which provides libsystemd-daemon-dev on kfreebsd and Hurd. Ansgar---End Message--- ___ 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#648747: marked as done (systemd: Getty setup broken)
Your message dated Wed, 30 Jul 2014 11:46:27 +0200 with message-id 53d8bef3.3030...@debian.org and subject line Re: Bug#648747: systemd: Getty setup broken has caused the Debian Bug report #648747, regarding systemd: Getty setup broken 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.) -- 648747: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648747 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: systemd Version: 37-1 Severity: normal Dear Maintainer, I upgraded systemd and tried it again. It still does the following (although I cannot give you exact output) after a terminal reset on boot: Getty1 starting foo some message next message It looks like some old printer problems or like a terminal that expects newlines at \r\n but only gets \n. Very strange! OTOH: Why does systemd reset the terminal so that all the other boot messages disappear? HS -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0 (SMP w/2 CPU cores; PREEMPT) 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 initscripts 2.88dsf-13.12 ii libacl1 2.2.51-4 ii libaudit0 1.7.18-1 ii libc6 2.13-21 ii libcap2 1:2.22-1 ii libcryptsetup1 2:1.3.0-3 ii libdbus-1-3 1.4.16-1 ii libpam0g1.1.3-4 ii libselinux1 2.1.0-4 ii libsystemd-daemon0 37-1 ii libsystemd-login0 37-1 ii libudev0172-1 ii libwrap07.6.q-21 ii udev172-1 ii util-linux 2.19.1-5 Versions of packages systemd recommends: ii libpam-systemd 37-1 Versions of packages systemd suggests: pn python 2.7.2-9 pn systemd-gui none -- no debconf information ---End Message--- ---BeginMessage--- Hi, Michael Biebl asked for more information in November 2012 as the bug was not reproducible with systemd 44-5. As no further information has been provided, I'm now closing this bug. Please reopen with additional information if this is still a problem. Ansgar---End Message--- ___ 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: bug 756604 is forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=81959
Processing commands for cont...@bugs.debian.org: forwarded 756604 https://bugs.freedesktop.org/show_bug.cgi?id=81959 Bug #756604 [systemd] Misleading documentation about NoNewPrivileges and UID changes Set Bug forwarded-to-address to 'https://bugs.freedesktop.org/show_bug.cgi?id=81959'. thanks Stopping processing here. Please contact me if you need assistance. -- 756604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756604 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#756760: systemd: stale session prevents hibernation of workstation
Processing commands for cont...@bugs.debian.org: reassign 756760 systemd-shim Bug #756760 [systemd] systemd: stale session prevents hibernation of workstation Bug reassigned from package 'systemd' to 'systemd-shim'. No longer marked as found in versions systemd/208-1. Ignoring request to alter fixed versions of bug #756760 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 756760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756760 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: reassign 756375 to systemd, forcibly merging 755373 756375, reopening 755373
Processing commands for cont...@bugs.debian.org:
reassign 756375 systemd
Bug #756375 [systemd-sysv] systemd-sysv: Can not normal shutdown with ulatencyd
Bug reassigned from package 'systemd-sysv' to 'systemd'.
No longer marked as found in versions systemd/208-6.
Ignoring request to alter fixed versions of bug #756375 to the same values
previously set
forcemerge 755373 756375
Bug #755373 {Done: Jon Severinsson j...@severinsson.net} [systemd] systemd
208-6 conflicts with ulatencyd
Bug #755512 {Done: Jon Severinsson j...@severinsson.net} [systemd]
systemd-sysv: Can not normal /sbin/shutdown (even as root)
Bug #756044 {Done: Jon Severinsson j...@severinsson.net} [systemd] systemd:
On system power,halt,reboot fail to reboot,poweroff my system
Bug #756307 {Done: Jon Severinsson j...@severinsson.net} [systemd] systemd:
Systemd fail to start(mount) stop(umount) Unit boot.mount
Bug #756375 [systemd] systemd-sysv: Can not normal shutdown with ulatencyd
Marked Bug as done
Marked as found in versions systemd/208-6.
Bug #755512 {Done: Jon Severinsson j...@severinsson.net} [systemd]
systemd-sysv: Can not normal /sbin/shutdown (even as root)
Bug #756044 {Done: Jon Severinsson j...@severinsson.net} [systemd] systemd:
On system power,halt,reboot fail to reboot,poweroff my system
Bug #756307 {Done: Jon Severinsson j...@severinsson.net} [systemd] systemd:
Systemd fail to start(mount) stop(umount) Unit boot.mount
Merged 755373 755512 756044 756307 756375
reopen 755373
Bug #755373 {Done: Jon Severinsson j...@severinsson.net} [systemd] systemd
208-6 conflicts with ulatencyd
Bug #755512 {Done: Jon Severinsson j...@severinsson.net} [systemd]
systemd-sysv: Can not normal /sbin/shutdown (even as root)
Bug #756044 {Done: Jon Severinsson j...@severinsson.net} [systemd] systemd:
On system power,halt,reboot fail to reboot,poweroff my system
Bug #756307 {Done: Jon Severinsson j...@severinsson.net} [systemd] systemd:
Systemd fail to start(mount) stop(umount) Unit boot.mount
Bug #756375 {Done: Jon Severinsson j...@severinsson.net} [systemd]
systemd-sysv: Can not normal shutdown with ulatencyd
Bug reopened
Ignoring request to alter fixed versions of bug #755373 to the same values
previously set
Ignoring request to alter fixed versions of bug #755512 to the same values
previously set
Ignoring request to alter fixed versions of bug #756044 to the same values
previously set
Ignoring request to alter fixed versions of bug #756307 to the same values
previously set
Ignoring request to alter fixed versions of bug #756375 to the same values
previously set
thanks
Stopping processing here.
Please contact me if you need assistance.
--
755373: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755373
755512: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755512
756044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756044
756307: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756307
756375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756375
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: reassigning my bugs to t...@debian.org
463318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463318 466116: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466116 466117: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466117 532228: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=532228 564438: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564438 601843: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601843 653858: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653858 656713: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656713 662238: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662238 664229: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664229 664838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664838 665003: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665003 665005: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665005 727692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727692 728459: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728459 728804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728804 733942: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733942 734961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734961 734971: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734971 736315: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736315 736856: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736856 738177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738177 738178: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738178 738179: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738179 738180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738180 738187: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738187 740582: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740582 740584: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740584 741632: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741632 741635: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741635 741637: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741637 742322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742322 742751: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742751 743968: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743968 743969: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743969 743975: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743975 744055: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744055 744273: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744273 744314: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744314 746503: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746503 752696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752696 753013: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753013 754663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754663 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: systemd: creates /var/cache/man with wrong owner/permissions
Processing control commands: affects -1 + man-db Bug #756896 [systemd] systemd: creates /var/cache/man with wrong owner/permissions Added indication that 756896 affects man-db -- 756896: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756896 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: severity of 756903 is important
Processing commands for cont...@bugs.debian.org: severity 756903 important Bug #756903 [systemd] systemd: Boot hangs if filesystems unavailable Severity set to 'important' from 'critical' thanks Stopping processing here. Please contact me if you need assistance. -- 756903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756903 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: tagging 756097
Processing commands for cont...@bugs.debian.org: tags 756097 + pending Bug #756097 [systemd] FTBFS: sys/xattr.h:32:3: error: expected identifier before numeric constant Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 756097: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756097 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#755968: libpam-systemd: should depend on dbus
Processing control commands: tag -1 pending Bug #755968 [libpam-systemd] libpam-systemd: should depend on dbus Added tag(s) pending. -- 755968: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755968 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: retitle 753589 to systemd: needs Pre-Depends for transitively Essential functionality of systemd-sysv
Processing commands for cont...@bugs.debian.org: retitle 753589 systemd: needs Pre-Depends for transitively Essential functionality of systemd-sysv Bug #753589 [systemd] systemd: Missing dependency on glibc? Changed Bug title to 'systemd: needs Pre-Depends for transitively Essential functionality of systemd-sysv' from 'systemd: Missing dependency on glibc?' thanks Stopping processing here. Please contact me if you need assistance. -- 753589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753589 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: forcibly merging 756097 757085
Processing commands for cont...@bugs.debian.org: forcemerge 756097 757085 Bug #756097 [systemd] FTBFS: sys/xattr.h:32:3: error: expected identifier before numeric constant Bug #757085 [systemd] systemd: Systemd fail to build from source Severity set to 'serious' from 'normal' Added tag(s) pending. Merged 756097 757085 thanks Stopping processing here. Please contact me if you need assistance. -- 756097: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756097 757085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757085 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: severity of 757195 is wishlist
Processing commands for cont...@bugs.debian.org: severity 757195 wishlist Bug #757195 [systemd] journalmctl: incomplete doc Severity set to 'wishlist' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 757195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757195 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#743157: marked as done (systemd: disables networking permanently during tried suspend)
Your message dated Thu, 07 Aug 2014 01:14:21 +0200 with message-id 53e2b6cd.6090...@debian.org and subject line Re: [Pkg-utopia-maintainers] Bug#743206: [Pkg-systemd-maintainers] Bug#743157: Bug#743157: systemd: disables networking permanently during tried suspend has caused the Debian Bug report #743157, regarding systemd: disables networking permanently during tried suspend 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.) -- 743157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743157 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: systemd Version: 204-8 Severity: serious Justification: breaks unrelated software Hi, running xfce4, latest sid, recent clean new install. suspend to ram via the xfce shutdown button works without any hunk. connected to power source I closed the lid of the laptop, with the following consequences: * suspend did not succeed * networking was completely broken - shown as disabled in the nm-applet, and could not be reenabled The log messages indicate that this is a systemd bug, here are the messages starting from when the sleep was requested: Mar 31 10:21:03 wienerschnitzel NetworkManager[3382]: info sleep requested (sleeping: no enabled: yes) Mar 31 10:21:03 wienerschnitzel NetworkManager[3382]: info sleeping or disabling... Mar 31 10:21:03 wienerschnitzel NetworkManager[3382]: info (wlan0): device state change: activated - unmanaged (reason 'sleeping') [100 10 37] Mar 31 10:21:03 wienerschnitzel NetworkManager[3382]: info (wlan0): deactivating device (reason 'sleeping') [37] Mar 31 10:21:03 wienerschnitzel NetworkManager[3382]: info (wlan0): canceled DHCP transaction, DHCP client pid 10688 Mar 31 10:21:03 wienerschnitzel kernel: [13525.215202] wlan0: deauthenticating from 00:24:c4:ab:bd:e9 by local choice (reason=3) Mar 31 10:21:03 wienerschnitzel wpa_supplicant[3694]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3 Mar 31 10:21:03 wienerschnitzel avahi-daemon[3208]: Withdrawing address record for 150.65.206.77 on wlan0. Mar 31 10:21:03 wienerschnitzel avahi-daemon[3208]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 150.65.206.77. Mar 31 10:21:03 wienerschnitzel kernel: [13525.218795] cfg80211: Calling CRDA to update world regulatory domain Mar 31 10:21:03 wienerschnitzel avahi-daemon[3208]: Interface wlan0.IPv4 no longer relevant for mDNS. Mar 31 10:21:03 wienerschnitzel NetworkManager[3382]: info (wlan0): cleaning up... Mar 31 10:21:03 wienerschnitzel NetworkManager[3382]: info (wlan0): taking down device. Mar 31 10:21:03 wienerschnitzel NetworkManager[3382]: info NetworkManager state is now ASLEEP Mar 31 10:21:03 wienerschnitzel kernel: [13525.235011] cfg80211: World regulatory domain updated: Mar 31 10:21:03 wienerschnitzel kernel: [13525.235023] cfg80211: DFS Master region: unset Mar 31 10:21:03 wienerschnitzel kernel: [13525.235028] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Mar 31 10:21:03 wienerschnitzel kernel: [13525.235036] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm) Mar 31 10:21:03 wienerschnitzel kernel: [13525.235043] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm) Mar 31 10:21:03 wienerschnitzel kernel: [13525.235048] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm) Mar 31 10:21:03 wienerschnitzel kernel: [13525.235054] cfg80211: (517 KHz - 525 KHz @ 8 KHz), (N/A, 2000 mBm) Mar 31 10:21:03 wienerschnitzel kernel: [13525.235060] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm) Mar 31 10:21:03 wienerschnitzel kernel: [13525.235066] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 mBm) Mar 31 10:21:03 wienerschnitzel avahi-daemon[3208]: Withdrawing address record for 2002:9641:cfb0:b:7e7a:91ff:fe2d:4074 on wlan0. Mar 31 10:21:03 wienerschnitzel avahi-daemon[3208]: Withdrawing address record for 2001:df0:2ed:7201:7e7a:91ff:fe2d:4074 on wlan0. Mar 31 10:21:03 wienerschnitzel avahi-daemon[3208]: Leaving mDNS multicast group on interface wlan0.IPv6 with address 2001:df0:2ed:7201:7e7a:91ff:fe2d:4074. Mar 31 10:21:03 wienerschnitzel avahi-daemon[3208]: Joining mDNS multicast group on interface wlan0.IPv6 with address fec0::b:7e7a:91ff:fe2d:4074. Mar 31 10:21:03 wienerschnitzel avahi-daemon[3208]: Withdrawing address record for fec0::b:7e7a:91ff:fe2d:4074 on wlan0. Mar 31 10:21:03 wienerschnitzel avahi-daemon[3208]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fec0::b:7e7a:91ff:fe2d:4074. Mar 31 10:21
Processed: Re: Bug#755120: mate-power-manager,systemd: suspend happens twice
Processing commands for cont...@bugs.debian.org:
clone #755120 -1
Bug #755120 {Done: Michael Biebl bi...@debian.org}
[mate-power-manager,systemd] mate-power-manager,systemd: suspend happens twice
Bug 755120 cloned as bug 757314
reopen -1
Bug #757314 {Done: Michael Biebl bi...@debian.org}
[mate-power-manager,systemd] mate-power-manager,systemd: suspend happens twice
Bug reopened
Ignoring request to alter fixed versions of bug #757314 to the same values
previously set
retitle -1 Drop dependency on consolekit
Bug #757314 [mate-power-manager,systemd] mate-power-manager,systemd: suspend
happens twice
Changed Bug title to 'Drop dependency on consolekit' from
'mate-power-manager,systemd: suspend happens twice'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
755120: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755120
757314: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757314
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: jessie
Processing commands for cont...@bugs.debian.org: tags 757207 + sid jessie Bug #757207 [systemd] systemd: Installation of systemd makes system unbootable Added tag(s) sid and jessie. thanks Stopping processing here. Please contact me if you need assistance. -- 757207: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757207 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#757207: systemd: Installation of systemd makes system unbootable
Processing commands for cont...@bugs.debian.org: forcemerge 757207 756903 Bug #757207 [systemd] systemd: Installation of systemd makes system unbootable Bug #756903 [systemd] systemd: Boot hangs if filesystems unavailable Severity set to 'critical' from 'important' Added tag(s) sid, moreinfo, and jessie. Bug #757207 [systemd] systemd: Installation of systemd makes system unbootable Marked as found in versions systemd/208-6. Merged 756903 757207 thanks Stopping processing here. Please contact me if you need assistance. -- 756903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756903 757207: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757207 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 (with 4 errors): ulatencyd conflicts with default systemd configuration
Processing commands for cont...@bugs.debian.org:
clone 756375 -1
Bug #756375 [systemd] systemd-sysv: Can not normal shutdown with ulatencyd
Bug #755373 [systemd] systemd 208-6 conflicts with ulatencyd
Bug #755512 [systemd] systemd-sysv: Can not normal /sbin/shutdown (even as root)
Bug #756044 [systemd] systemd: On system power,halt,reboot fail to
reboot,poweroff my system
Bug #756307 [systemd] systemd: Systemd fail to start(mount) stop(umount) Unit
boot.mount
Failed to clone 756375: Bug is marked as being merged with others. Use an
existing clone.
reassign -1 ulatency
Failed to clear fixed versions and reopen on -1: The 'bug' parameter (-1) to
Debbugs::Control::set_package did not pass regex check
Debbugs::Control::set_package('transcript', 'GLOB(0x2777840)',
'requester', 'Michael Biebl bi...@debian.org', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid', '53e3448b.1050...@debian.org',
'request_subject', ...) called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 255
eval {...} called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 254
Debbugs::Control::Service::control_line('line', 'reassign -1 ulatency',
'clonebugs', 'HASH(0x26d2c58)', 'limit', 'HASH(0x26d2640)',
'common_control_options', 'ARRAY(0x26d2688)', 'errors', ...) called at
/usr/lib/debbugs/service line 474
retitle -1 ulatencyd conflicts with default systemd configuration
Failed to set the title of -1: The 'bug' parameter (-1) to
Debbugs::Control::set_title did not pass regex check
Debbugs::Control::set_title('transcript', 'GLOB(0x2777840)',
'requester', 'Michael Biebl bi...@debian.org', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid', '53e3448b.1050...@debian.org',
'request_subject', ...) called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 514
eval {...} called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 513
Debbugs::Control::Service::control_line('line', 'retitle -1 ulatencyd
conflicts with default systemd configura...', 'clonebugs', 'HASH(0x26d2c58)',
'limit', 'HASH(0x26d2640)', 'common_control_options', 'ARRAY(0x26d2688)',
'errors', ...) called at /usr/lib/debbugs/service line 474
found -1 0.5.0-9
Failed to add found on -1: The 'bug' parameter (-1) to
Debbugs::Control::set_found did not pass regex check
Debbugs::Control::set_found('transcript', 'GLOB(0x2777840)',
'requester', 'Michael Biebl bi...@debian.org', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid', '53e3448b.1050...@debian.org',
'request_subject', ...) called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 298
eval {...} called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 297
Debbugs::Control::Service::control_line('line', 'found -1 0.5.0-9',
'clonebugs', 'HASH(0x26d2c58)', 'limit', 'HASH(0x26d2640)',
'common_control_options', 'ARRAY(0x26d2688)', 'errors', ...) called at
/usr/lib/debbugs/service line 474
thanks
Stopping processing here.
Please contact me if you need assistance.
--
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#756375: marked as done (systemd-sysv: Can not normal shutdown with ulatencyd)
Your message dated Thu, 07 Aug 2014 17:47:07 +0800 with message-id 53e34b1b.4010...@gmail.com and subject line Re: Bug#756375: Info received (Bug#756375: After upgrade systemd-* to 208-7, I still have this problem) has caused the Debian Bug report #756375, regarding systemd-sysv: Can not normal shutdown with ulatencyd 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.) -- 756375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756375 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: systemd-sysv Version: 208-6 Severity: normal Dear Maintainer, I want to reopen bug report (the old one number: 755375) When my system installed ulatencyd, my system can not normal shutdown, even as root. I opened the bug report, number: 755375, deveplor said: - I believe this is a configuration issue, not a bug. Please see (1) https://github.com/poelzi/ulatencyd/wiki/Faq#id4 Closing, please reopen if the problem persists after adjusting the systemd configuration as documented in the ulatencyd faq. - I tried remove /etc/ulatencyd, then reinstall ulatencyd with default setup/config (/etc/ulatencyd/*), but still can not normal shutdown. then I tried following the (1)Faq#id4 add 3 line to /etc/ulatencyd/system.conf --- DefaultControllers= JoinControllers= controllers= --- but still can not normal shutdown. then I remove ulatencyd (apt-get remove ulatencyd), my system can normal shutdown. So, I want to reopen this bug report. Thank you. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd-sysv depends on: ii systemd 208-6 systemd-sysv recommends no packages. systemd-sysv suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- On 08/07/2014 05:42 PM, Debian Bug Tracking System wrote: Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Debian systemd Maintainers pkg-systemd-maintainers@lists.alioth.debian.org If you wish to submit further information on this problem, please send it to 756...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. ---End Message--- ___ 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#755512: marked as done (systemd-sysv: Can not normal /sbin/shutdown (even as root))
Your message dated Thu, 07 Aug 2014 17:47:07 +0800 with message-id 53e34b1b.4010...@gmail.com and subject line Re: Bug#756375: Info received (Bug#756375: After upgrade systemd-* to 208-7, I still have this problem) has caused the Debian Bug report #756375, regarding systemd-sysv: Can not normal /sbin/shutdown (even as root) 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.) -- 756375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756375 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: systemd-sysv Version: 208-6 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** Recently(over 2 weeks), I noticed my system can not normal shutdown, even as root (/sbin/shutdown -h now). (but not everytime, sometime can normal shutdown, but usually can not) When I type /sbin/shutdown -h now (as root), my system will exit Xorg/xfce4 to console mode, then hang on it without any response (alt-ctrl-delete, Ctrl-c), until I put the power/reset button. I see some error/warning messages in /var/log/syslog, like this when shuting down: (ulatencyd:1173): WARNING **: pid: 10735 parnet 10731 missing. attaching to pid 1 So I try to remove ulatency/ulatencyd package, after that, my system can normal shutdown everytime. My english is so bad, what I want to say is: 1. When installed ulatencyd, my system can not normal shutdown. (but not everytime) 2. when remove ulatencyd, my system can normal shutdown everytime. Thank you. ulatency/ulatencyd version is: 0.5.0-9 systemd-sysv version is: 208-6 *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd-sysv depends on: ii systemd 208-6 systemd-sysv recommends no packages. systemd-sysv suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- On 08/07/2014 05:42 PM, Debian Bug Tracking System wrote: Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Debian systemd Maintainers pkg-systemd-maintainers@lists.alioth.debian.org If you wish to submit further information on this problem, please send it to 756...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. ---End Message--- ___ 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#757348: systemd: with SysV init, can no longer suspend and shutdown from lightdm
Processing control commands: reassign -1 systemd-shim Bug #757348 [systemd] systemd: with SysV init, can no longer suspend and shutdown from lightdm Bug reassigned from package 'systemd' to 'systemd-shim'. No longer marked as found in versions systemd/208-7. Ignoring request to alter fixed versions of bug #757348 to the same values previously set -- 757348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757348 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: reassign 757314 to mate-power-manager
Processing commands for cont...@bugs.debian.org: reassign 757314 mate-power-manager Bug #757314 [mate-power-manager,systemd] Drop dependency on consolekit Bug reassigned from package 'mate-power-manager,systemd' to 'mate-power-manager'. Ignoring request to alter found versions of bug #757314 to the same values previously set Ignoring request to alter fixed versions of bug #757314 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 757314: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757314 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#747939: marked as done (systemd: prevents hibernation without password with open screen session in other login session)
Your message dated Sun, 10 Aug 2014 22:15:31 +0200 with message-id 53e7d2e3.6000...@debian.org and subject line Re: Bug#747939: systemd: prevents hibernation without password with open screen session in other login session has caused the Debian Bug report #747939, regarding systemd: prevents hibernation without password with open screen session in other login session 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.) -- 747939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747939 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: systemd Version: 208-1 Severity: normal Dear Maintainer, if systemd is running I get a password prompt during hibernation[1][2]. Now if I spawn another KDE session, open a screen in it, quit the session, loginctl still treats it as running session: merkaba:~ loginctl | cat 1 1000 martin seat0 4 2012 ms seat0 Well, the screen is indeed running as that user: ba:~ ps aux | grep ^ms | grep -v grep ms5651 0.0 0.0 37792 1468 ?Ss Mai11 0:00 /lib/systemd/systemd --user ms5654 0.0 0.0 178412 4 ?SMai11 0:00 (sd-pam) ms 14034 0.0 0.0 26296 1288 ?Ss Mai12 0:01 SCREEN ms 14035 0.0 0.0 44620 1004 pts/15 Ss+ Mai12 0:00 /usr/bin/zsh ms 14061 0.0 0.0 40656 796 pts/16 Ss+ Mai12 0:00 /usr/bin/zsh Honestly, while treating this as an still open session from a technical session may be correct, this again shows why the policy of asking a password on hibernation on a *single* seat system creates a lot of changes in default behavior that I find outrightly annoying, unintuitive and from a user point of view of common sense just plain broken. This is *still* a single seat system. I am its boss. So it is supposed to do what *I* want, instead of insisting of knowing better than me. And as I am logged into to an existing session it is supposed to do so without asking me any password anymore. I am authenticated, thanks. The only way this could make sense from a usability point of view IMHO is displaying a dialog with hey, you still got a screen session open, really want to hibernate? before locking the screen with simple yes and no button. Its obviously not there yet as it first locks the screen, then displays the dialog, and then if I unlock the screen and and enter the password immediately hibernates *without* locking the screen, basically hibernating with a unlocked desktop if I am not quick enough to press Ctrl-L to lock it. Thats why I yesterday used, sleep 20 ; pm-hibernate last night, I just wanted to go to sleep and hibernate the system. Again just closing the lid will suspend the system just fine, without asking a password, so its even inconsistent. And again, changing it with merkaba:/etc/polkit-1 cat ./localauthority/50-local.d/org.freedesktop.upower.pkla [Suspend/hibernate permissions] Identity=unix-group:sudo Action=org.freedesktop.upower.hibernate;org.freedesktop.upower.suspend ResultAny=yes ResultInactive=yes ResultActive=yes does not have any effect on this. So please, treat this report seriously at least from a policy point of view, instead of just closing it again as not your business. I am ready to report different bugs for the affected components, in case I get advice on where to report what, but please treat this as a regression over previous behavior in case systemd is running. Previous behavior that IMHO matches common sense much more closely. [1] Debian BTS web gui does not respond within acceptable time, will add later [2] See above. Thanks, Martin -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental')Architecture: amd64 (x86_64) Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.15.0-rc5-tp520 (SMP w/4 CPU cores; PREEMPT) 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-1 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-53 ii libacl1 2.2.52-1 ii libaudit11:2.3.6-1 ii libblkid12.20.1-5.7 ii libc62.18-5 ii libcap2 1:2.22-1.2 ii libcap2-bin 1:2.22-1.2 ii libcryptsetup4 2:1.6.4-4 ii libdbus-1-3 1.8.2-1 ii libgcrypt11 1.5.3-4 ii libkmod2 17-2 ii liblzma5 5.1.1alpha+20120614-2 ii libpam0g
Processed: Re: Bug#757696: [systemd] systemd: writes messages to kmsg
Processing commands for cont...@bugs.debian.org: forcemerge 748648 757696 Bug #748648 [systemd] systemd-logind polluting dmesg Bug #748648 [systemd] systemd-logind polluting dmesg Marked as found in versions systemd/208-7. Bug #757696 [systemd] [systemd] systemd: writes messages to kmsg Marked as found in versions systemd/204-8. Merged 748648 757696 thanks Stopping processing here. Please contact me if you need assistance. -- 748648: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748648 757696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757696 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: bug 757302 is forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=82453
Processing commands for cont...@bugs.debian.org: forwarded 757302 https://bugs.freedesktop.org/show_bug.cgi?id=82453 Bug #757302 [systemd] systemd: should ignore files ending in .dpkg-tmp Set Bug forwarded-to-address to 'https://bugs.freedesktop.org/show_bug.cgi?id=82453'. thanks Stopping processing here. Please contact me if you need assistance. -- 757302: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757302 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#756103: systemd should be more forgiving of fstab errors
Processing control commands:
reopen -1
Bug #756103 {Done: Michael Biebl bi...@debian.org} [systemd] systemd: boot
fails due to fstab entry for /dev/cdrom with 'noauto'
Bug reopened
Ignoring request to alter fixed versions of bug #756103 to the same values
previously set
severity -1 wishlist
Bug #756103 [systemd] systemd: boot fails due to fstab entry for /dev/cdrom
with 'noauto'
Severity set to 'wishlist' from 'important'
retitle -1 systemd should be more forgiving of fstab errors
Bug #756103 [systemd] systemd: boot fails due to fstab entry for /dev/cdrom
with 'noauto'
Changed Bug title to 'systemd should be more forgiving of fstab errors' from
'systemd: boot fails due to fstab entry for /dev/cdrom with 'noauto''
--
756103: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756103
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: reassign 754404 to dbus
Processing commands for cont...@bugs.debian.org: reassign 754404 dbus Bug #754404 [systemd-sysv] /usr/sbin/invoke-rc.d: line 288: /sbin/runlevel: No such file or directory Bug reassigned from package 'systemd-sysv' to 'dbus'. Ignoring request to alter found versions of bug #754404 to the same values previously set Ignoring request to alter fixed versions of bug #754404 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 754404: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754404 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#757891: init-system-helpers: Please do not depend on perl
Processing control commands: clone -1 -2 Bug #757891 [init-system-helpers] init-system-helpers: Please do not depend on perl Bug 757891 cloned as bug 757905 reassign -2 perl-base Bug #757905 [init-system-helpers] init-system-helpers: Please do not depend on perl Bug reassigned from package 'init-system-helpers' to 'perl-base'. No longer marked as found in versions init-system-helpers/1.20. Ignoring request to alter fixed versions of bug #757905 to the same values previously set retitle -2 perl-base: Please include File::Path, File::Basename, File::Find, Text::ParseWords Bug #757905 [perl-base] init-system-helpers: Please do not depend on perl Changed Bug title to 'perl-base: Please include File::Path, File::Basename, File::Find, Text::ParseWords' from 'init-system-helpers: Please do not depend on perl' -- 757891: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757891 757905: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757905 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#757913: systemd: On systemd dbus.target is invoked but not exist.
Processing commands for cont...@bugs.debian.org: reassign 757913 dbus Bug #757913 [systemd] systemd: On systemd dbus.target is invoked but not exist. Bug reassigned from package 'systemd' to 'dbus'. No longer marked as found in versions systemd/208-6. Ignoring request to alter fixed versions of bug #757913 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 757913: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757913 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: affects 751741
Processing commands for cont...@bugs.debian.org: affects 751741 + syslog-ng-core Bug #751741 [dh-systemd] dh-systemd: postinst snippets should stop foo.socket during upgrades too Bug #736258 [dh-systemd] acpid fails to upgrade on amd64 Bug #751744 [dh-systemd] dh-systemd: postinst snippets should stop foo.socket during upgrades too Bug #757903 [dh-systemd] syslog-ng-core: invoke-rc.d: initscript syslog-ng, action stop failed. Added indication that 751741 affects syslog-ng-core Added indication that 736258 affects syslog-ng-core Added indication that 751744 affects syslog-ng-core Added indication that 757903 affects syslog-ng-core thanks Stopping processing here. Please contact me if you need assistance. -- 736258: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736258 751741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751741 751744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751744 757903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757903 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: [Pkg-utopia-maintainers] installation-reports: Please consider dbus for the core files
Processing commands for cont...@bugs.debian.org: reassign 758111 systemd Bug #758111 [installation-reports] installation-reports: Please consider dbus for the core files Bug reassigned from package 'installation-reports' to 'systemd'. Ignoring request to alter found versions of bug #758111 to the same values previously set Ignoring request to alter fixed versions of bug #758111 to the same values previously set found 758111 208-6 Bug #758111 [systemd] installation-reports: Please consider dbus for the core files Marked as found in versions systemd/208-6. thanks Stopping processing here. Please contact me if you need assistance. -- 758111: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758111 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: tagging 758111
Processing commands for cont...@bugs.debian.org: tags 758111 + confirmed Bug #758111 [systemd] installation-reports: Please consider dbus for the core files Added tag(s) confirmed. thanks Stopping processing here. Please contact me if you need assistance. -- 758111: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758111 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: [bts-link] source package systemd
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 # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #757302 (http://bugs.debian.org/757302) # Bug title: systemd: should ignore files ending in .dpkg-tmp # * https://bugs.freedesktop.org/show_bug.cgi?id=82453 # * remote status changed: (?) - RESOLVED # * remote resolution changed: (?) - FIXED # * closed upstream tags 757302 + fixed-upstream Bug #757302 [systemd] systemd: should ignore files ending in .dpkg-tmp Added tag(s) fixed-upstream. usertags 757302 + status-RESOLVED resolution-FIXED There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. # remote status report for #757367 (http://bugs.debian.org/757367) # Bug title: udev: /lib/udev/hwdb.d/60-keyboard.hwdb documentation issues # * https://bugs.freedesktop.org/show_bug.cgi?id=82311 # * remote status changed: (?) - NEW usertags 757367 + status-NEW There were no usertags set. Usertags are now: status-NEW. thanks Stopping processing here. Please contact me if you need assistance. -- 757302: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757302 757367: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757367 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 (with 1 errors): Re: Bug#758145: installation-reports: Missing dbus; logind service fails
Processing commands for cont...@bugs.debian.org:
merge 758111 758145
Bug #758111 [systemd] installation-reports: Please consider dbus for the core
files
Unable to merge bugs because:
severity of #758145 is 'normal' not 'wishlist'
package of #758145 is 'installation-reports' not 'systemd'
Failed to merge 758111: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x3485a80)',
'requester', 'Brian Potkin claremont...@gmail.com', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid',
'14082014225544.f95ba0ef5...@desktop.copernicus.demon.co.uk',
'request_subject', ...) called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 538
eval {...} called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 537
Debbugs::Control::Service::control_line('line', undef, 'clonebugs',
'HASH(0x33c4c58)', 'limit', 'HASH(0x33c4640)', 'common_control_options',
'ARRAY(0x33c4688)', 'errors', ...) called at /usr/lib/debbugs/service line 474
thanks
Stopping processing here.
Please contact me if you need assistance.
--
758111: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758111
758145: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758145
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: forcibly merging 618862 756202
Processing commands for cont...@bugs.debian.org: forcemerge 618862 756202 Bug #618862 [systemd] systemd: ignores keyscript in crypttab Bug #756202 [systemd] systemd: Slow bootup (more than 3 minutes), comment swap line in fstab Severity set to 'important' from 'normal' Marked as found in versions systemd/19-1. Added tag(s) confirmed. Bug #618862 [systemd] systemd: ignores keyscript in crypttab Marked as found in versions systemd/208-6. Merged 618862 756202 thanks Stopping processing here. Please contact me if you need assistance. -- 618862: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618862 756202: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756202 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: reassign 757887 to source:kde-workspace, forcibly merging 754314 757887
Processing commands for cont...@bugs.debian.org: reassign 757887 source:kde-workspace Bug #757887 [systemd] systemd: kdm don't start Bug reassigned from package 'systemd' to 'src:kde-workspace'. No longer marked as found in versions systemd/208-6. Ignoring request to alter fixed versions of bug #757887 to the same values previously set forcemerge 754314 757887 Bug #754314 [src:kde-workspace] systemd support for kdm Bug #757887 [src:kde-workspace] systemd: kdm don't start Severity set to 'wishlist' from 'normal' Added tag(s) patch. Merged 754314 757887 thanks Stopping processing here. Please contact me if you need assistance. -- 754314: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754314 757887: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757887 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
