Bug#1092095: php-gettext: debci failure with PHPUnit 11

2025-04-05 Thread Pete Batard
Hi, I'm trying to understand the context of this bug, as my current take on this is that php-gettext is at risk of being removed from Trixie purely on account that: - There exists a *downstream* package (tt-rss, i.e. not an actual dependency of php-gettext) that is posing a problem. - The PH

Bug#1092095: [pkg-php-pear] Bug#1092095: php-gettext: debci failure with PHPUnit 11

2025-03-23 Thread Pete Batard
Hi David, Thanks for clarifying the evolution of the php-gettext package. I have indeed been using it more more than 10 years, so I wasn't aware that, in that time, gettext had been formally integrated into PHP without requiring a separate dependencies, and that the package also had gone thro

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

2016-09-12 Thread Pete Batard
Yes! At long last 231-6 seems to have cleared the systemd issue I was observing on Raspberry Pi: -- root@pi ~ # systemctl status ● pi State: running Jobs: 0 queued Failed: 0 units

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

2016-08-30 Thread Pete Batard
Okay. I have logged issue #651 (https://github.com/raspberrypi/firmware/issues/651) with the rpi team so that they try to sort their SECCOMP configuration in future kernels. Regards, /Pete

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

2016-08-30 Thread Pete Batard
On 2016.08.30 17:30, Felipe Sateler wrote: I managed to get the config from a jessie rpi by loading the 'configs' module (sudo modprobe configs). After that the config is found on /proc/config.gz Yeah, I just discovered the same after I replied. This is also documented on the official rpi githu

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

2016-08-30 Thread Pete Batard
Thanks Felipe. I guess with the new detection process, the resurgence of the issue is starting to make sense now. For the record, I am using one of the latest official Raspberry Pi kernels from https://github.com/raspberrypi/firmware (which I get indirectly through the https://github.com/Hex

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

2016-08-29 Thread Pete Batard
Please find my boot log. Note that I've tried commenting out 'MemoryDenyWriteExecute=yes' in the various .service config files, but it didn't help. If you need anything else, please let me know. Regards, /Pete [0.00] Booting Linux on physical CPU 0xf00 [0.00] Initializing cgro

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

2016-08-28 Thread Pete Batard
On 2016.08.28 15:37, Felipe Sateler wrote: Could you try 231-5 from unstable? Oops, I mean 231-5 broke it. I'm seeing the issue back in 231-5 and not 231-4 as I mentioned earlier. 231-4 seemed to be okay, and it's only when I upgraded to 231-5 that the problem reappeared. Regards, /Pete

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

2016-08-27 Thread Pete Batard
...and 231-4 broke the whole thing down again. :( Same error: root@pi ~ # systemctl status systemd-journald.service ● systemd-journald.service - Journal Service Loaded: loaded (/lib/systemd/system/systemd-journald.service; s

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

2016-08-14 Thread Pete Batard
Didn't fix it for me... :( I went to an 'apt-get --reinstall install' of every single package that is listed under 'Description' above (expect -udeb and -dev), and got the 231-2 version alright, but the issue remains exactly the same, even after a full reboot. I should point out that I did g

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

2016-08-12 Thread Pete Batard
Okay. I have now gone through a dpkg -i install of all the (non dbgsym) .deb I see on your server, and also issued a reboot for good measure, but I still see the same problem with journald being failed, along with dependent services -

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

2016-08-12 Thread Pete Batard
Thanks Felipe. I installed libsystemd0_231-2_armhf.deb but shouldn't there be a systemd_231-2_armhf.deb as well? Strangely there's a systemd-dbgsym_231-2_armhf.deb but no non-dbgsym version, as opposed to other .debs. The .dsc does mention a 'systemd' binary, and earlier, the idea was to in

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

2016-08-08 Thread Pete Batard
Thanks Felipe. I'm afraid it's still not completing successfully though: ../src/test/test-execute.c: In function ‘test_exec_systemcallfilter’: ../src/test/test-execute.c:120:14: error: implicit declaration of function ‘is_seccomp_e

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

2016-08-06 Thread Pete Batard
Since Rick hasn't replied, and I've been encountering the same issue on a Raspberry Pi 2 model B running sid, I've been trying the steps mentioned above. However the post-build tests failed with the following: - test-