Bug#925772: lua-cqueues: ftbfs with GCC-9
Upstream has fixed the issue, please see new releases: https://github.com/wahern/cqueues/releases On Thu, 28 Mar 2019 at 12:49, Daurnimator wrote: > > This issue is known upstream: https://github.com/wahern/cqueues/issues/212 > > It comes down to GCC extensions no longer being compatible with GCC's > new scope for compound literals. > > https://gcc.gnu.org/ml/gcc/2019-02/msg00042.html > https://gcc.gnu.org/gcc-9/porting_to.html
Bug#863286: completely broken in non-US locales
On 28 May 2017 at 12:53, Daurnimator <q...@daurnimator.com> wrote: > However I'm hoping to make a 0.2 release today that includes the fix > (as well as others that weren't reported to debian directly): please > consider packaging that instead. See http://daurnimator.com/post/161154248644/lua-http-v02-released and https://github.com/daurnimator/lua-http/releases/tag/v0.2
Bug#863286: completely broken in non-US locales
On 28 May 2017 at 01:38, Santiago Ruano Rincónwrote: > In case you want to test it, I've uploaded a patched version to my > personal repo: > https://people.debian.org/~santiago/debian/santiago-unstable/ If patching the upstream, please update the version in http/version.lua to something like version="0.1.debian-1" However I'm hoping to make a 0.2 release today that includes the fix (as well as others that weren't reported to debian directly): please consider packaging that instead.
Bug#863286: completely broken in non-US locales
On 25 May 2017 at 08:03, Steinar H. Gunderson <sgunder...@bigfoot.com> wrote: > lua-http cannot construct legal requests if a non-US locale (or more > precisely, > anything using comma as decimal separator) is in use. Fixed upstream in https://github.com/daurnimator/lua-http/commit/f822bbef48f8ee6b42ce4cca843d4cc10cd0f775
Bug#764298: Still an issue
On 3 March 2015 at 20:45, Michael Biebl bi...@debian.org wrote: Am 2015-03-04 01:13, schrieb Michael Biebl: Am 04.03.2015 um 01:34 schrieb Michael Biebl: Am 04.03.2015 um 01:07 schrieb Daurnimator: Did you dist-upgrade the VM and those failures are from before the upgrade? Can you attach your /var/log/dpkg.log The reason why I'm asking is, that the fixed version 215-12 migrated to testing on 2015-02-28. The latest AMI according to [1] is from 20150213, so it can't have 215-12 yet. So this looks like the VM was upgraded and the error messages are from before the upgrade when systemd 215-12 was installed. [1] https://wiki.debian.org/Cloud/AmazonEC2Image/Jessie Just double checked: The latest AMI provided by Debian ships 215-11. So, if you have 215-12 installed, this means the VM was upgraded after the VM was instantiated and booted and the error messages you see are most likely from 215-11, which does not ship the fix yet. Ah ha! It appears something along the way upgraded systemd without me knowing. I just rebooted the system and everything seems to be fine now :) dpkg.log contains: 2015-03-03 20:57:32 upgrade libsystemd0:amd64 215-11 215-12 2015-03-03 20:57:32 status half-configured libsystemd0:amd64 215-11 2015-03-03 20:57:32 status unpacked libsystemd0:amd64 215-11 2015-03-03 20:57:32 status half-installed libsystemd0:amd64 215-11 2015-03-03 20:57:32 status half-installed libsystemd0:amd64 215-11 2015-03-03 20:57:32 status unpacked libsystemd0:amd64 215-12 2015-03-03 20:57:32 status unpacked libsystemd0:amd64 215-12 2015-03-03 20:57:32 configure libsystemd0:amd64 215-12 none 2015-03-03 20:57:32 status unpacked libsystemd0:amd64 215-12 2015-03-03 20:57:32 status half-configured libsystemd0:amd64 215-12 2015-03-03 20:57:32 status installed libsystemd0:amd64 215-12 2015-03-03 20:57:32 upgrade systemd:amd64 215-11 215-12 2015-03-03 20:57:32 status half-configured systemd:amd64 215-11 2015-03-03 20:57:32 status unpacked systemd:amd64 215-11 2015-03-03 20:57:32 status half-installed systemd:amd64 215-11 2015-03-03 20:57:33 status half-installed systemd:amd64 215-11 2015-03-03 20:57:33 status unpacked systemd:amd64 215-12 2015-03-03 20:57:33 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 configure systemd:amd64 215-12 none 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status half-configured systemd:amd64 215-12 2015-03-03 20:57:34 status installed systemd:amd64 215-12 2015-03-03 20:57:34 upgrade systemd-sysv:amd64 215-11 215-12 2015-03-03 20:57:34 status half-configured systemd-sysv:amd64 215-11 2015-03-03 20:57:34 status unpacked systemd-sysv:amd64 215-11 2015-03-03 20:57:34 status half-installed systemd-sysv:amd64 215-11 2015-03-03 20:57:34 status half-installed systemd-sysv:amd64 215-11 2015-03-03 20:57:34 status unpacked systemd-sysv:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd-sysv:amd64 215-12 2015-03-03 20:57:35 configure systemd-sysv:amd64 215-12 none 2015-03-03 20:57:35 status unpacked systemd-sysv:amd64 215-12 2015-03-03 20:57:35 status half-configured systemd-sysv:amd64 215-12 2015-03-03 20:57:35 status installed systemd-sysv:amd64 215-12 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764298: Still an issue
On 3 March 2015 at 18:35, Michael Biebl bi...@debian.org wrote: What's the output of systemctl status dbus.service dbus.socket? I do not have dbus installed. $ sudo systemctl status dbus.service ● dbus.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) $ sudo systemctl status dbus.socket ● dbus.socket Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Cannot add dependency job for unit dbus.socket, ignoring: Unit dbus.socket failed to load: No such file or directory. Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Cannot add dependency job for unit dbus.socket, ignoring: Unit dbus.socket failed to load: No such file or directory. Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Cannot add dependency job for unit dbus.socket, ignoring: Unit dbus.socket failed to load: No such file or directory. Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Cannot add dependency job for unit dbus.socket, ignoring: Unit dbus.socket failed to load: No such file or directory. Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Cannot add dependency job for unit dbus.socket, ignoring: Unit dbus.socket failed to load: No such file or directory. Mar 03 21:08:09 ip-10-80-175-145 systemd[1]: Cannot add dependency job for unit dbus.socket, ignoring: Unit dbus.socket failed to load: No such file or directory. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764298: Still an issue
I just installed a fresh systemd (via amazon AMI: https://wiki.debian.org/Cloud/AmazonEC2Image/Jessie) that includes systemd 215-12 I still got the log message: Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Starting Login Service... Mar 03 20:02:56 ip-10-80-175-145 systemd-logind[323]: Failed to connect to system bus: No such file or directory Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Failed to start Login Service. Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Unit systemd-logind.service entered failed state. Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service has no holdoff time, scheduling restart. Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Stopping Login Service... (and then again a few times)
Bug#764298: Still an issue
On 3 March 2015 at 18:42, Michael Biebl bi...@debian.org wrote: What's the output of systemctl cat systemd-logind.service systemctl status systemd-logind.service $ sudo systemctl cat systemd-logind.service # /lib/systemd/system/systemd-logind.service # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. [Unit] Description=Login Service Documentation=man:systemd-logind.service(8) man:logind.conf(5) Documentation=http://www.freedesktop.org/wiki/Software/systemd/logind Documentation=http://www.freedesktop.org/wiki/Software/systemd/multiseat Wants=user.slice After=nss-user-lookup.target user.slice ConditionPathExists=/lib/systemd/system/dbus.service # Ask for the dbus socket. If running over kdbus, the socket will # not be actually used. Wants=dbus.socket After=dbus.socket [Service] ExecStart=/lib/systemd/systemd-logind Restart=always RestartSec=0 BusName=org.freedesktop.login1 CapabilityBoundingSet=CAP_SYS_ADMIN CAP_AUDIT_CONTROL CAP_CHOWN CAP_KILL CAP_DAC_READ_SEARCH CAP_DAC_OVERRIDE CAP_FOWNER CAP_SYS_TTY_CONFIG WatchdogSec=1min # Increase the default a bit in order to allow many simultaneous # logins since we keep one fd open per session. LimitNOFILE=16384 $ sudo systemctl status systemd-logind.service ● systemd-logind.service - Login Service Loaded: loaded (/lib/systemd/system/systemd-logind.service; static) Active: failed (Result: start-limit) since Tue 2015-03-03 20:02:56 UTC; 4h 3min ago start condition failed at Tue 2015-03-03 21:08:09 UTC; 2h 57min ago Docs: man:systemd-logind.service(8) man:logind.conf(5) http://www.freedesktop.org/wiki/Software/systemd/logind http://www.freedesktop.org/wiki/Software/systemd/multiseat Main PID: 341 (code=exited, status=1/FAILURE) Status: Shutting down... Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service has no holdoff time, scheduling restart. Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Stopping Login Service... Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Starting Login Service... Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service start request repeated too quickly, refusing to start. Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Failed to start Login Service. Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Unit systemd-logind.service entered failed state. Mar 03 21:08:09 ip-10-80-175-145 systemd[1]: Started Login Service. Mar 03 23:11:46 ip-10-80-175-145 systemd[1]: Stopped systemd-logind.service. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org