Bug#757891: init-system-helpers: Please do not depend on perl
On Tue, Aug 12, 2014 at 10:41:50PM +0200, Michael Biebl wrote: Am 12.08.2014 21:15, schrieb Niko Tyni: The perl-base package is Essential:yes, so inclusion there is pretty close to a promise of supporting that interface forever inside the Essential set. So care must be taken when adding functionality there. IMO Perl reimplementations of /usr/bin/find, /usr/bin/basename, /bin/mkdir -p, and /bin/rm -r don't seem very good candidates. Why not? Can you elaborate? The Debian Policy defines Essential:yes as the minimal set of functionality that must be available and usable on the system at all times. Adding other implementations of the functionality already present in those separate binaries, just in a different language, goes counter to the minimal part IMO. I am somewhat concerned that the needs of a package that seems to have become part of the base system more or less by accident would drive additions in the Essential set. I'm also concerned that the more functionality we add in perl-base, the easier it becomes to drop dependencies on the full perl package from normal packages. This will make it more probable that end users encounter systems without the full perl package, which goes counter to Perl upstream's wishes. But yeah, I may be making too big a fuss about just a few modules at 150kB. -- Niko Tyni nt...@debian.org ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
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
Bug#756202:
Hi, I saw the same after converting to systemd as init: Delay until some systemd script times out. In the hope this helps someone seeing the same issue, this are my observations: In my case the reason was that somehow the UUID of the swap device changed, so that systemd was simply waiting for the wrong device. The UUID changed when I migrated to systemd, however the very first reboot was still fast. (though I did not boot to X this time has I had to recompile the nvidia stuff) After I changed to the new UUID, the system boots as expected. Maybe this helps someone with the same isssue.. I don't know why the UUID changed in the first place. The upgrade also included a kernel update. (linux-image-amd64:amd64 3.14+57 - 3.14+59) (timeline to back that up with information) Last reboot with sysv: Aug 14 09:55:20 mordor kernel: [0.00] Initializing cgroup subsys cpuset (..) Aug 14 09:55:20 mordor kernel: [ 25.798452] Adding 16775164k swap on /dev/mapper/cryptswap. Priority:-1 extents:1 across:16775164k First reboot with systemd as init: Aug 14 11:37:36 mordor kernel: [0.00] Initializing cgroup subsys cpuset (..) Aug 14 11:37:36 mordor kernel: [ 26.772168] Adding 16775164k swap on /dev/mapper/cryptswap. Priority:-1 extents:1 across:16775164k (proof that this is systemd:) Aug 14 11:37:37 mordor systemd[1]: Starting Authenticate and Authorize Users to Run Privileged Tasks... Second reboot: Aug 14 11:51:42 mordor kernel: [0.00] Initializing cgroup subsys cpuset (..) Aug 14 11:51:44 mordor systemd[1]: Expecting device dev-disk-by\x2duuid-918c7c50\x2d17ed\x2d4e21\x2d9026\x2d6aedacaec283.device... Aug 14 11:53:14 mordor systemd[1]: Job dev-disk-by\x2duuid-918c7c50\x2d17ed\x2d4e21\x2d9026\x2d6aedacaec283.device/start timed out. Aug 14 11:53:14 mordor systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-918c7c50\x2d17ed\x2d4e21\x2d9026\x2d6aedacaec283.device. Aug 14 11:53:14 mordor systemd[1]: Dependency failed for /dev/disk/by-uuid/918c7c50-17ed-4e21-9026-6aedacaec283. My setup: - LUKS crytped root sda4_crypt UUID=x-xxx---x9d2 none luks - LUKS crypted swap with derived key from root device cryptswap UUID=x-xxx---xdc3 sda4_crypt luks,keyscript=/lib/cryptsetup/scripts/decrypt_derived,swap the relevant fstab line: UUID=x-xxx---x283 noneswapdefaults 0 0 (resume kernel-param -- however resume not yet tested after migration:) resume=/dev/mapper/cryptswap ls -la /dev/disk/by-uuid/ lrwxrwxrwx 1 root root 10 Aug 14 13:11 x-xxx---x1b2 - ../../dm-1 lrwxrwxrwx 1 root root 10 Aug 14 13:11 x-xxx---x9d2 - ../../sda4 lrwxrwxrwx 1 root root 10 Aug 14 13:11 x-xxx---x5c0 - ../../dm-0 lrwxrwxrwx 1 root root 10 Aug 14 13:11 x-xxx---xdc3 - ../../sda3 ___ 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#758119: dnsmasq: fails to start under systemd when dbus is not installed
Package: dnsmasq Version: 2.71-1 Severity: important User: syst...@packages.debian.org Usertags: systemd-units dependencies X-Debbugs-CC: syst...@packages.debian.org When installing dnsmasq on a newly installed Debian jessie system from the daily debian-installer netinst ISO, I get the error below and dnsmasq is not running afterwards but no error on sysvinit systems. This seems to be caused by the systemd service being Type=dbus and not having any dependency on dbus. I'm marking this bug report as important because systemd is now the default. Please add a Depends that reflects this (like [1]). I'm CCing the systemd maintainers in case they think this should be solved in a more systematic way. Setting up dnsmasq-base (2.71-1) ... Setting up dnsmasq (2.71-1) ... Failed to issue method call: Unit dbus.socket failed to load: No such file or directory. invoke-rc.d: initscript dnsmasq, action start failed. 1. dbus | sysvinit-core | upstart -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/1 CPU core) 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 dnsmasq depends on: ii dnsmasq-base 2.71-1 ii init-system-helpers 1.20 ii netbase 5.2 dnsmasq recommends no packages. Versions of packages dnsmasq suggests: pn resolvconf none -- no debconf information -- bye, pabs http://wiki.debian.org/PaulWise -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Re: Bug#758119: dnsmasq: fails to start under systemd when dbus is not installed
Am 14.08.2014 13:54, schrieb Paul Wise: Package: dnsmasq Version: 2.71-1 Severity: important User: syst...@packages.debian.org fwiw, we are using User: pkg-systemd-maintainers@lists.alioth.debian.org since a while now. Usertags: systemd-units dependencies X-Debbugs-CC: syst...@packages.debian.org When installing dnsmasq on a newly installed Debian jessie system from the daily debian-installer netinst ISO, I get the error below and dnsmasq is not running afterwards but no error on sysvinit systems. This seems to be caused by the systemd service being Type=dbus and not having any dependency on dbus. I'm marking this bug report as important because systemd is now the default. Please add a Depends that reflects this (like [1]). I'm CCing the systemd maintainers in case they think this should be solved in a more systematic way. Setting up dnsmasq-base (2.71-1) ... Setting up dnsmasq (2.71-1) ... Failed to issue method call: Unit dbus.socket failed to load: No such file or directory. invoke-rc.d: initscript dnsmasq, action start failed. 1. dbus | sysvinit-core | upstart Hm, it seems dnsmasq requires dbus in any case, even when running under sysvinit or upstart. So I don't understand the alternative dependency you suggest. Afaics, dnsmasq should simply add a Depends on dbus? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Re: Bug#758119: dnsmasq: fails to start under systemd when dbus is not installed
On Thu, 2014-08-14 at 14:15 +0200, Michael Biebl wrote: fwiw, we are using User: pkg-systemd-maintainers@lists.alioth.debian.org since a while now. Ah, there are still some bugs with the old user, sorry. BTW archived bugs can now have their usertags altered so that could be fixed. Hm, it seems dnsmasq requires dbus in any case, even when running under sysvinit or upstart. So I don't understand the alternative dependency you suggest. Afaics, dnsmasq should simply add a Depends on dbus? As far as I can tell, dnsmasq doesn't need dbus under sysvinit, not sure about upstart though. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Re: Bug#758119: dnsmasq: fails to start under systemd when dbus is not installed
Am 14.08.2014 14:30, schrieb Paul Wise: On Thu, 2014-08-14 at 14:15 +0200, Michael Biebl wrote: fwiw, we are using User: pkg-systemd-maintainers@lists.alioth.debian.org since a while now. Ah, there are still some bugs with the old user, sorry. BTW archived bugs can now have their usertags altered so that could be fixed. Hm, it seems dnsmasq requires dbus in any case, even when running under sysvinit or upstart. So I don't understand the alternative dependency you suggest. Afaics, dnsmasq should simply add a Depends on dbus? As far as I can tell, dnsmasq doesn't need dbus under sysvinit, not sure about upstart though. Hm, right. It seems so use --enable-dbus when being run under systemd. You've proposed: Depends: dbus | sysvinit-core | upstart But even with sysvinit-core installed, one can boot using the init=/bin/systemd command line. So maybe a simple: Recommend: dbus is better? I'm also inclined to just make systemd depend or at least recommend dbus, seeing [1] Michael [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758111 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Re: Bug#758119: dnsmasq: fails to start under systemd when dbus is not installed
Am 14.08.2014 14:57, schrieb Michael Biebl: Am 14.08.2014 14:30, schrieb Paul Wise: On Thu, 2014-08-14 at 14:15 +0200, Michael Biebl wrote: fwiw, we are using User: pkg-systemd-maintainers@lists.alioth.debian.org since a while now. Ah, there are still some bugs with the old user, sorry. BTW archived bugs can now have their usertags altered so that could be fixed. Hm, it seems dnsmasq requires dbus in any case, even when running under sysvinit or upstart. So I don't understand the alternative dependency you suggest. Afaics, dnsmasq should simply add a Depends on dbus? As far as I can tell, dnsmasq doesn't need dbus under sysvinit, not sure about upstart though. Hm, right. It seems so use --enable-dbus when being run under systemd. You've proposed: Depends: dbus | sysvinit-core | upstart But even with sysvinit-core installed, one can boot using the init=/bin/systemd command line. So maybe a simple: Recommend: dbus is better? I'm also inclined to just make systemd depend or at least recommend dbus, seeing [1] Michael [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758111 After some more discussion on #debian-systemd, we decided to make systemd recommend dbus. After all, when unprivileged users use systemctl, a dbus system bus is required and apparently we also need it for [1] -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Re: Bug#758119: dnsmasq: fails to start under systemd when dbus is not installed
On Thu, 2014-08-14 at 14:57 +0200, Michael Biebl wrote: Hm, right. It seems so use --enable-dbus when being run under systemd. You've proposed: Depends: dbus | sysvinit-core | upstart But even with sysvinit-core installed, one can boot using the init=/bin/systemd command line. So maybe a simple: Recommend: dbus is better? I'm not really sure, I'll leave it up to the maintainer. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758111 Hmm, that is surprising to me, I didn't think the getty service used dbus at all. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part ___ 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
Bug#757903: [Syslog-ng-maintainers] Bug#757903: Bug#757903: syslog-ng-core: invoke-rc.d: initscript syslog-ng, action stop failed.
Hi On 2014-08-13 13:29:47, Gergely Nagy wrote: 3.5.6-2 will likely hit unstable by tonight, I would be very interested in hearing whether the problem persists with that version. Upgrades to 3.5.6-2 on both machines went fine. Also repeatedly running dpkg-reconfigure with the new version installed didn't trigger the issue. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
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
[bts-link] source package systemd
# # 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 # 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 usertags 757302 + 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 thanks ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#754078: crypt devices not brought online (backed by iscsi)
On Sun, 20.07.14 15:58, Michael Biebl (bi...@debian.org) wrote: Currently, with systemd, it gets to where it'd like to bring up the crypt devices. As network and open-iscsi aren't up yet, it wastes a lot of time waiting for block devices that will never appear (at least not without further action later in the boot process). Hm, k. So I guess we'd need something like a cryptsetup-pre.target, where certain units can hook into (via Wants/Before), network.target being one of them. And devices flagged noearly would get a dependency on this target and be ordered after it. Lennart, do you have a different/better idea how we could handle such setups which have more complex requirements, like cryptsetup devices being backed by iscsi which in turn requires network access? Not following here. In contrast to classic sysv the jobs actually stay queued until the devices show up. If you have iscsi devices that shall be mounted during boot, then you really need to make sure that iscsi can work in early boot. Then, if iscsi needs the network, then your network system needs to be able to run in early-boot too. I have the suspcicion this works on Fedora already. But generally, the old Debian scheme of running cryptsetup twice doesn't really apply to systemd, since we never scan for devices, we just subscribe to them. Anyway, still not grokking the actual problem here I must say... Lennart -- Lennart Poettering, Red Hat ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Re: Bug#754314: systemd support for kdm
On Tue, Aug 12, 2014 at 10:43:11AM +0200, Michael Biebl wrote: Hi, On Thu, Jul 17, 2014 at 05:17:23PM +0200, Moritz Muehlenhoff wrote: On Mon, Jul 14, 2014 at 06:34:40PM +0200, Moritz Mühlenhoff wrote: On Wed, Jul 09, 2014 at 10:16:07PM +0200, Moritz Muehlenhoff wrote: Source: kde-workspace Severity: wishlist Tags: patch activation of the service - After installation of the updated package the service isn't enabled by default. You'll need to run systemctl enable kdm.service for that. I'm not sure how the default display manager is handled if several systemd units are installed, so it's probably for the best right now. Michael Stapelberg explained to me that the unit file needs an additional WantedBy=multi-user.target which would resolve this. This doesn't seem to be sufficient, I still need to enable the service manually ATM. This issue was discussed during the systemd/GNOME sprint this spring. I.e. how the display-manager.service symlink is supposed to be managed when multiple display managers are installed. lightdm and gdm3 are already updated to support this scheme, so I'm bringing their maintainers into the loop here. Please coordinate with them when adding systemd support to kdm. We should really wrap this into some common code, which is included from the respective display managers! I've looked into lightdm amd gdm3 and they already diverge (lightdm misses the removal code present for gdm3). After all, this affects wdm and xdm as well. Cheers, Moritz ___ 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#758157: systemd make shutdown hang at “Stopped Getty on tty1”
Am 14.08.2014 23:30, schrieb M G Berberich: Package: systemd Version: 208-6 Severity: normal Dear Maintainer, since systemd has been installed instead of sysvinit, shutdown does no longer work. it stops at “Stopped Getty on tty1” and the system does not power down. What exact command did you use to shutdown the system? Did you wait at least 90 secs? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
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
