Bug#1057911: jquery-tablesorter pending version
Control: forwarded -1 https://salsa.debian.org/js-team/jquery-tablesorter/-/commit/07a8ceecbae453221560f1114551289292acfede @elbrus could this package have a version published with Closes: #1057911 ?
Bug#964654: Updates
Control: forwarded -1 https://github.com/SimonKagstrom/kcov/commit/a7ab2971d377e6df84af52b748d46fa40d18f6c8 Control: tags -1 forwarded pending Control: owner ! MR: https://salsa.debian.org/debian/kcov/-/merge_requests/1
Bug#1036630: procps: unowned /usr/bin/ps on filesystem after upgrade to bookworm
Hmm, was there a cleanup or migration script which failed to run? On 6/8/24 09:30, Paul Slootman wrote: On Tue, 23 May 2023 09:06:31 -0500 C Seys wrote: After upgrading to bookworm there is an unowned /usr/bin/ps on the filesystem: # dpkg -S /usr/bin/ps dpkg-query: no path found matching pattern /usr/bin/ps There is also /bin/ps owned by procps: # dpkg -S /bin/ps procps: /bin/ps I suspect that /bin is now a symlink to /usr/bin . So the /usr/bin/ps you see was installed as /bin/ps Regards, Paul
Bug#1065221:
Did you receive my previous message??
Bug#1069726: gophernicus: Default documentroot in man page does not match default config file
Package: gophernicus Version: 3.1.1-3 Severity: normal X-Debbugs-Cc: w...@unux.org Dear Maintainer, When installing Gophernicus, the man page states that the -r option specifies the documentroot of the server, and the default is /var/gopher The file /etc/default/gophernicus contains one line: OPTIONS=-r /srv/gopher setting the document root to /srv/gopher instead I expected the default directory listed in the manual page to be the default location for the server's document root -- System Information: Debian Release: 11.9 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-28-amd64 (SMP w/1 CPU thread) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gophernicus depends on: ii adduser 3.118+deb11u1 ii libc6 2.31-13+deb11u9 ii libwrap0 7.6.q-31 gophernicus recommends no packages. gophernicus suggests no packages. -- Configuration Files: /etc/default/gophernicus changed [not included] /etc/xinetd.d/gophernicus changed [not included] -- no debconf information
Bug#1068802: conserver-server: systemctl reload does not work
Package: conserver-server Version: 8.2.7-2+b1 Severity: normal Tags: patch Dear Maintainer, I'd like to report a simple bug that prevents us from reloading conservers' configuration on the fly by sending it a SIGHUP. the systemd service file does not have a ExecReload to send it. I attach a patch for the service file that adds the corresponding line. * What led up to the situation? -> tried to reload the configuration without restarting the service * What exactly did you do (or not do) that was effective (or ineffective)? -> 'systemctl reload conserver-server' * What was the outcome of this action? -> lead to 'Failed to reload conserver-server.service: Job type reload is not applicable for unit conserver-server.service.' * What outcome did you expect instead? -> conserver recieving a SIGHUP and reloading its config on the fly. -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages conserver-server depends on: ii adduser3.134 ii debconf [debconf-2.0] 1.5.82 ii init-system-helpers1.65.2 ii libc6 2.36-9+deb12u4 ii libcrypt1 1:4.4.33-2 ii libgssapi-krb5-2 1.20.1-2+deb12u1 ii libpam0g 1.5.2-6+deb12u1 ii libssl33.0.11-1~deb12u2 ii libwrap0 7.6.q-32 ii sysvinit-utils [lsb-base] 3.06-4 conserver-server recommends no packages. conserver-server suggests no packages. -- Configuration Files: /etc/conserver/conserver.cf changed [not included] -- debconf information excluded --- conserver-server.service.orig 2024-04-11 14:04:22.609005135 +0200 +++ conserver-server.service2024-04-11 14:03:59.768941435 +0200 @@ -10,6 +10,7 @@ EnvironmentFile=-/etc/conserver/server.conf EnvironmentFile=-/etc/conserver/server.local ExecStart=/usr/sbin/conserver -d $OPTS +ExecReload=kill -SIGHUP $MAINPID [Install] WantedBy=multi-user.target
Bug#976196: clickhouse LTS 2024
Control: retitle -1 clickhouse: Please package ClickHouse v24.3.1.2672-lts 4 years later, the LTS version currently is (reading the releases page: v..): https://github.com/ClickHouse/ClickHouse/releases/tag/v24.3.1.2672-lts I am not sure why the ClickHouse package has not got new versions in Debian. It got very small updates that did not change the currently packaged version.
Bug#1064781: ACK + fix uploaded
Control: tags -1 + pending Control: fixed -1 php-dompdf-svg-lib/0.5.2-1 Thank you for the bug report !
Bug#1057267: Upload done for phpldapadmin/1.2.6.3-0.3+deb12u1
Thank you ! Upload of phpldapadmin/1.2.6.3-0.3+deb12u1 done. -- William Desportes
Bug#1054585: phpmyadmin: no cleanup of tmp dir
Hello Florian ! But as we hardened our server, we setup an own php-fpm pool for phpmyadmin and changed the save_path to /var/lib/phpmyadmin/tmp. It seems like that it is our own created problem and we do need scripting on our end to clean these files ;) As I was re-reading this, be sure to not use the same directory as the tmp directory of phpMyAdmin. - It could get wiped out at any time - Some phpMyAdmin code can access it and leak sessions This will get better with phpMyAdmin 6.0, see: https://bugs.debian.org/bug=583588 Most probably I will try to process this bug report while packaging phpMyAdmin 6.0. But be sure the directory is not in open_basedir for security reasons that will be better. At least this part of the bug report is actually valid ;) Indeed -- William signature.asc Description: OpenPGP digital signature
Bug#1059021: Patch forwarded for loongarch64
Control: forwarded -1 https://salsa.debian.org/php-team/pear/php-bacon-baconqrcode/-/commit/3866eafd8afc57e88729480222e52d5f6723e2f3 Control: tags -1 + patch confirmed pending Thank you for this patch ! I pushed it into Git and it will go with the next release.
Bug#1063439: (no subject)
Thank you for translating into Chinese ! I pushed your work on git, it will be deployed when more changes get into the packaging.
Bug#1062702: libomp-dev: Program which has run for ten years crashed after distribution upgrade
Package: libomp-dev
Version: 1:14.0-55.7~deb12u1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: piob...@mindspring.com
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: 12.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-13-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libomp-dev depends on:
ii libomp-14-dev 1:14.0.6-12
libomp-dev recommends no packages.
libomp-dev suggests no packages.
-- no debconf information
Program containing omp pragma failed after dist upgrade
[CODE]
// oomptest.c
// compile as gcc oomptest.c -o oomp -lm -fopenmp
#include
#include
#include
int omp_get_max_threads(void);
int omp_get_thread_num(void);
void subroutine(float *subject, float *object, int index){
object[index] -= subject[0];
}
int main(int argc, char* argv[]){
int i, id;
float v0[2] = {13579, 24680}, v1[5]={1, 3, 5, 7, 9};
#pragma omp parallel num_threads(5) private (id)
{
id = omp_get_thread_num(); printf("line 22 id=%d\n", id);
subroutine([1], [id], id);
}
for(i=0; i<5; i++)printf("v1[%d] = %f\n", i, v1[i]);
}[/CODE]
output from test program
"
line 22 id=0
line 22 id=3
line 22 id=1
line 22 id=2
line 22 id=4
v1[0] = -24679.00
v1[1] = 3.00
v1[2] = -24675.00
v1[3] = 7.00
v1[4] = -24671.00
"
expected output from test program
>
line 22 id=0
line 22 id=3
line 22 id=1
line 22 id=2
line 22 id=4
v1[0] = -24679.00
v1[1] = -24677.00
v1[2] = -24675.00
v1[3] = -24673.00
v1[4] = -24671.00
"
Bug#1026019: php 7.4
I wish you would ship PHP 7 as an option in Bookworm as well. This will not happen, but the easiest way is to install this repository: https://github.com/oerdnj/deb.sury.org/wiki/Frequently-Asked-Questions#how-to-enable-the-debsuryorg-repository It works out of the box and can provide all php versions you would need. They all can be installed on the same server. As a fact: I use them on my Debian bookworm workstation (7.1,2,3,4 & 8.1,2). I hope my quick (non maintainer) reply will help you solve this php version issue ;) Reminder: upgrades need to be done some day. See: https://endoflife.date/php -- William Desportes
Bug#1031010: icingaweb2: uses an inline version of php-font-lib/php-dompdf-svg-lib/php-dompdf in the binary
My understanding of the dompdf and dejavu licensing is reflected in the copyright file: https://salsa.debian.org/nagios-team/icinga-php-thirdparty/-/blob/debian/0.12.1+ds-1/debian/copyright?ref_type=tags#L65-L81 Thank you for this link, indeed ! What makes you think that the Bitstream license is incompatible with the DFSG? Sorry about that, It was a mistake in the diagnosis on my side. You helped me understand I was wrong on how I understood this license. -- William
Bug#1056974: php-dompdf: providing .ufm files
Control: tags -1 - wontfix Hi, I was wrong while doing my research about the licensing, sorry about that. I think that solution provided by Robin Gustafsson should fix my issue. Definitely ! I approved the PR and should proceed into sending it to unstable shortly. Thank you all for participating on this bug -- William
Bug#1057205: The fedora 39 builds using the works on ppc64le
Hi, I have noticed a similar problem on riscv64 openSUSE Tumbleweed (gcc13-13.2.1+git7813-6.2.riscv64), but everything builds fine on all the fedora 39 and rawhide architectures. These builds include ppc64le. fedora 39: https://koji.fedoraproject.org/koji/buildinfo?buildID=2321551 fedora rawhide: https://koji.fedoraproject.org/koji/buildinfo?buildID=2321548 I don't know what the difference are between the ppc64le Debian and Fedora environments, but that would be a starting point to to figure out why systemtap isn't compiling on Debian. -Will Cohen
Bug#1031010: icingaweb2: uses an inline version of php-font-lib/php-dompdf-svg-lib/php-dompdf in the binary
Hello, I did re-open this bug because I think you should remove the non Debian licence compatible files you embed: https://sources.debian.org/src/php-dompdf/2.0.3%2Bdfsg-3/debian/copyright/#L7 See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056974#10 You can find the files when searching: https://packages.debian.org/search?searchon=contents=ufm==bookworm=any -- William
Bug#1056974: php-dompdf: providing .ufm files
Control: tags -1 wontfix Hello, Only "DejaVu*" fonts have ufm files. But I had to exclude the DejaVu fonts for licensing reasons: https://sources.debian.org/src/php-dompdf/2.0.3%2Bdfsg-3/debian/copyright/#L7 You should ask upstream to provide fonts with a LICENSE and one that can be used in Debian: https://www.debian.org/legal/licenses/ See: https://github.com/dompdf/dompdf/issues If I am correct this license is not Debian compatible: https://github.com/dejavu-fonts/dejavu-fonts/blob/master/LICENSE You can find for now ufm files in the icingaweb2 package. But I think I will raise a bug for this. https://packages.debian.org/search?searchon=contents=ufm==bookworm=any Let me know your thoughts -- William
Bug#1057267: bookworm-pu: package phpldapadmin/1.2.6.3-0.3+deb12u1
Subject: bookworm-pu: package phpldapadmin/1.2.6.3-0.3+deb12u1
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: bookworm
Severity: normal
[ Reason ]
Some users have older PHP versions than the one from bookworm, phpldapadmin is
compatible with most of the recent ones.
But the patch that was distributed at the time of packaging was limited to PHP
8.1+ and got outdated by a newer one that is compatible with more PHP versions.
[ Impact ]
The users will no be able to login to phpldapadmin on older PHP versions.
[ Tests ]
The fix was distributed by upstream on newer versions.
This fix/patch was successfully tested in production by myself.
[ Risks ]
None. The patch is trivial.
[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in (old)stable
[x] the issue is verified as fixed in unstable
[ Changes ]
I changed the type check to what upstream did provide after I had patched the
file myself for PHP 8.1+ only.
[ Other info ]
Reported as https://github.com/leenooks/phpLDAPadmin/issues/231 and
https://github.com/leenooks/phpLDAPadmin/issues/230
Salsa CI did build this successfully:
https://salsa.debian.org/php-team/pear/phpldapadmin/-/pipelines/574472
diff -Nru phpldapadmin-1.2.6.3/debian/changelog phpldapadmin-1.2.6.3/debian/changelog
--- phpldapadmin-1.2.6.3/debian/changelog 2023-03-19 00:10:35.0 +0100
+++ phpldapadmin-1.2.6.3/debian/changelog 2023-09-04 12:14:31.0 +0200
@@ -1,3 +1,9 @@
+phpldapadmin (1.2.6.3-0.3+deb12u1) bookworm; urgency=medium
+
+ * Update the patch for PHP 7.4 LDAP login to work like PHP 8.1
+
+ -- William Desportes Mon, 04 Sep 2023 12:14:31 +0200
+
phpldapadmin (1.2.6.3-0.3) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru phpldapadmin-1.2.6.3/debian/patches/Fix-ldap-connect-PHP-8.1-is-now-a-class.patch phpldapadmin-1.2.6.3/debian/patches/Fix-ldap-connect-PHP-8.1-is-now-a-class.patch
--- phpldapadmin-1.2.6.3/debian/patches/Fix-ldap-connect-PHP-8.1-is-now-a-class.patch 2023-03-19 00:10:35.0 +0100
+++ phpldapadmin-1.2.6.3/debian/patches/Fix-ldap-connect-PHP-8.1-is-now-a-class.patch 2023-09-04 12:13:31.0 +0200
@@ -5,12 +5,15 @@
Ref: https://www.php.net/manual/en/function.ldap-connect.php#refsect1-function.ldap-connect-changelog
In 8.1.0 -> Returns an LDAP\Connection instance now; previously, a resource was returned.
+
+Origin: upstream
+Forwarded: https://github.com/leenooks/phpLDAPadmin/commit/b035e8a0f4f49633c2492a07f0182eefb311848d
---
lib/ds_ldap.php | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/ds_ldap.php b/lib/ds_ldap.php
-index 9537ff2..f465207 100644
+index 9537ff2..2f82eda 100644
--- a/lib/ds_ldap.php
+++ b/lib/ds_ldap.php
@@ -216,7 +216,7 @@ class ldap extends DS {
@@ -18,7 +21,7 @@
$resource,$this->getValue('server','host'),$this->getValue('server','port'));
- if (! is_resource($resource))
-+ if (! $resource instanceof \LDAP\Connection)
++ if (!$resource)
debug_dump_backtrace('UNHANDLED, $resource is not a resource',1);
# Go with LDAP version 3 if possible (needed for renaming and Novell schema fetching)
@@ -27,7 +30,7 @@
# If we didnt log in...
- if (! is_resource($connect) || $this->noconnect || ! $this->userIsAllowedLogin($userDN)) {
-+ if (! $connect instanceof \LDAP\Connection || $this->noconnect || ! $this->userIsAllowedLogin($userDN)) {
++ if (!$connect || $this->noconnect || ! $this->userIsAllowedLogin($userDN)) {
$this->logout($method);
return false;
OpenPGP_signature.asc
Description: OpenPGP digital signature
Bug#1033802: dropbear-initramfs: sleep and cat not found
As written in msg#42 dropbear-initramfs doesn't configure the network
by
itself; all it does is calling initramfs-tools' configure_networking().
And that function currently doesn't support VLAN tags, which is what
the aforementioned wishlist bug is about.
ack. I will try to use an other interface name that does not exist.
What makes you say that? What's the output of `lsinitramfs /initrd.img
| grep -e/{sleep,cat}`?
usr/lib/modules/6.1.0-13-amd64/kernel/drivers/net/usb/catc.ko
usr/bin/sleep
usr/bin/cat
You still haven't replied whether setting DROPBEAR_SHUTDOWN_TIMEOUT=300
fixes this or not, and I still have reasons to believe it's the
(non-)issue described earlier in this bug.
ack, will try this.
I will try to boot a VM and do very minimal steps to get to the final
bug.
signature.asc
Description: OpenPGP digital signature
Bug#1033802: dropbear-initramfs: sleep and cat not found
> Just to confirm, you unlock (at initramfs stage) using keyboard + screen right, not remotely using dropbear SSH right? Because at that point the initramfs hasn't got network access right? Yes Sorry for my lack of follow up, I had gave up on the system. Update December 2023, Using "debian-12.2.0-amd64-netinst.iso": The system was installed by un checking all boxes and only checking "ssh server". Sleep and cat are found on the booted system. I created a new VM for a client on Proxmox and managed to fall into this sleep cat not found bug. I had put an interface name: ens9.123 thinking it would take the VLAN tag. But it triggered the crash. Removing the ".123" fixes it. That said, sleep and cat are still not into the initramfs image.
Bug#1057034: (no subject)
Thank you for opening this bug, this change is already done but not yet released. I marked this as forwarded and will try to send a version soon -- William
Bug#1054585: phpmyadmin: no cleanup of tmp dir
Hi, Are you really sure this files are php sessions? This request raises doubts for me, I will need to check too. They are twig cache files for sure, but yes they could be cleaned up before each upgrade. -- William Le 26 octobre 2023 13:29:43 GMT+02:00, Beowulf a écrit : >Package: phpmyadmin >Version: 4:5.0.4+dfsg2-2+deb11u1 >Severity: important >Tags: patch >X-Debbugs-Cc: beow...@netzguerilla.net > >Dear Maintainer, > >/var/lib/phpmyadmin/tmp/ is created by the installer, php session files are >created in there and never cleaned up. > >It would be best to have a cronjob cleaning up old session files, like it is >done in roundcubemail: >https://salsa.debian.org/roundcube-team/roundcube/-/blob/debian/bullseye/debian/roundcube-core.cron.daily > >Best regards >Florian Müller
Bug#1054181: libjs-bootstrap5: please provide scss files independently
Source: node-bootstrap Severity: wishlist Currently there is no way to have the scss sources (node-bootstrap) with phpunit that requires the old bootstrap 3. Explained: - phpunit pulls php-codecoverage that pulls libjs-bootstrap4 - https://packages.debian.org/sid/all/libjs-bootstrap4/filelist installs files in /usr/share/sass/bootstrap/ - https://packages.debian.org/sid/all/node-bootstrap/filelist installs files in /usr/share/sass/bootstrap/ - They exclude itself some installing, so far so good. I currently can have libjs-bootstrap5 for the the js and css files, but I need the scss files too. But given this impossible configuration I have to keep the contents of your node-bootstrap /usr/share/sass/bootstrap/ in my debian/missing-sources/ In order to have the phpunit that I need to run tests on my package and have the sources I need to build the package. The package is: phpmyadmin I am not sure how this can be improved, but I would like to have the scss files without breaking everything :) -- William
Bug#1053957: (no subject)
Control: reopen -1
Control: tags -1 + confirmed patch
Thank you for opening this bug.
Until now I was waiting on chromium but I have to realize my bug may be due to
their stuff but I need to more on.
For now I managed right now to reproduce the bug on i386 using:
- docker run --rm --privileged multiarch/qemu-user-static --reset -p yes
- docker run -v $PWD:/app --workdir /app --rm i386/debian:bookworm /bin/bash
And installing all the tooling and stuff.
Then I get "selenium.common.exceptions.WebDriverException: Message: unknown error:
session deleted because of page crash"
It seems like the crash goes away if I send the keys line by line and not all
the text at once.
Maybe a memory issue of some type.
Works:
for line in Simpsons.split('\n'):
import_area.send_keys(line + "\n")
Crashes:
import_area.send_keys(Simpsons)
To be continued :)
Bug#1053767: (no subject)
Thank you both for your very quick replies ! I will think a bit about it to see what could be done. Because for now chromium is the only web-driver available in Debian.
Bug#1053767: chromium: please to add support for s390x or armel
Source: chromium Version: 117.0.5938.149-1 Severity: wishlist User: debian-s...@lists.debian.org Usertags: s390x User: debian-...@lists.debian.org Usertags: armel X-Debbugs-Cc: debian-s...@lists.debian.org X-Debbugs-Cc: debian-...@lists.debian.org Dear Maintainer, Chromium could be built on Debian s390x or armel, but it would probably require some upstream work. For now when trying to build on my Linux One s390x VM I got this: ERROR at //base/allocator/partition_allocator/partition_alloc.gni:25:3: Assertion failed. assert(false, "Unknown CPU: $current_cpu") Unknown CPU: s390x Let me know what direction to go if it's worth trying to add support for s390x or not. I would definitely like to have armel supported, maybe it's a more suitable target. (https://wiki.debian.org/RaspberryPi) Once both architectures are built DEP-8 tests will be able to use chromium-driver on them. Related to the riscv64 request: #1051998 -- William
Bug#1008564: Assumes /usr/games/polygen is in $PATH; not true for root
O Mon, Oct 02, 2023 at 03:19:12AM -0700, Breno Leitao wrote:
> On Mon, Sep 18, 2023 at 06:07:54PM +0100, William de Abreu Pinho wrote:
> > I am completely new to maintenance and this is my first attempt to submit a
> > patch.
> >
> > Please find attached the proposed changes, I hope these will suffice.
>
> Thanks for the fix. As we had discussed in person, please attach the
> .debdiff and I will ship a new package with this fix.
>
> Thanks for your contribution to Debian.
Sure, here is the debdiff for the new version.
Thanks,
William
diff -u cappuccino-0.5.1/debian/changelog cappuccino-0.5.1/debian/changelog
--- cappuccino-0.5.1/debian/changelog
+++ cappuccino-0.5.1/debian/changelog
@@ -1,3 +1,9 @@
+cappuccino (0.5.1-11) unstable; urgency=medium
+
+ * Fix polygen not found when running cappuccino as root. Closes: #1008564
+
+ -- William de Abreu Pinho Mon, 18 Sep 2023 13:43:33 +0100
+
cappuccino (0.5.1-10.1) unstable; urgency=medium
* Non-maintainer upload.
only in patch2:
unchanged:
--- cappuccino-0.5.1.orig/debian/patches/polygen_not_found.patch
+++ cappuccino-0.5.1/debian/patches/polygen_not_found.patch
@@ -0,0 +1,31 @@
+Fix polygen not found when running cappuccino as root.
+--- a/cappuccino
b/cappuccino
+@@ -20,14 +20,16 @@
+ except OSError:
+ PLUGIN_DIR = "/usr/share/cappuccino/"
+
++POLYGEN_PATHNAME = "/usr/games/polygen"
++
+ # text to see if polygen is available
+-if not os.access("/usr/games/polygen",os.X_OK):
++if not os.access(POLYGEN_PATHNAME,os.X_OK):
+ print ("Error: polygen must be installed")
+ print ("See http://www.polygen.org;)
+ sys.exit(1)
+
+ # to be discussed
+-pipe_command = 'polygen %s' % os.path.join(PLUGIN_DIR, 'cappuccino.grm')
++pipe_command = '%s %s' % (POLYGEN_PATHNAME, os.path.join(PLUGIN_DIR, 'cappuccino.grm'))
+
+ class CappuccinoSplash(Gtk.Window):
+ def __init__(self):
+@@ -94,7 +96,7 @@
+ GObject.source_remove(self.timeouter)
+
+ def get_log_data(self):
+- p = os.popen("polygen -X 50 %s" % os.path.join(PLUGIN_DIR,"compileline.grm"))
++ p = os.popen("%s -X 50 %s" % (POLYGEN_PATHNAME, os.path.join(PLUGIN_DIR,"compileline.grm")))
+ self.log = p.readlines()
+ p.close()
+
Bug#1051355: Arch armhf does not build
Can someone have a look to the armhf build ? https://buildd.debian.org/status/logs.php?suite=sid=armhf=chromium=117.0.5938.62-1 It does not build, and blocks the package migration: https://tracker.debian.org/pkg/chromium
Bug#1052400: php-zumba-json-serializer: correction to short description
Hi Ben, What do you think about <https://salsa.debian.org/php-team/pear/php-zumba-json-serializer/-/commit/17b94a1835e8e7791a6077ab1a8b1a3a95ddd0fb>? -- William
Bug#1008564: Assumes /usr/games/polygen is in $PATH; not true for root
I am completely new to maintenance and this is my first attempt to submit a
patch.
Please find attached the proposed changes, I hope these will suffice.
Format: 1.8
Date: Mon, 18 Sep 2023 13:43:33 +0100
Source: cappuccino
Binary: cappuccino
Architecture: source all
Version: 0.5.1-10.2
Distribution: unstable
Urgency: medium
Maintainer: Breno Leitao
Changed-By: William de Abreu Pinho
Description:
cappuccino - utility to let your boss think that you're working hard
Closes: 1008564
Changes:
cappuccino (0.5.1-10.2) unstable; urgency=medium
.
* Non-maintainer upload.
* Fix polygen not found when running cappuccino as root. Closes: #1008564
Checksums-Sha1:
c42f3eaab680e3815a5cd293096e8094ce851d5f 887 cappuccino_0.5.1-10.2.dsc
f74d99f8289e55b494514e78efc8f96815b9a203 5146 cappuccino_0.5.1-10.2.diff.gz
a8b667b8f7decf798dc5dc0bf91c541bd1857246 90792 cappuccino_0.5.1-10.2_all.deb
364ea9841bc505eaf00df515ba43105451405540 5600
cappuccino_0.5.1-10.2_amd64.buildinfo
Checksums-Sha256:
0c30f7f7d1100d6a6f11fa9198c1316076302c487d75986fdc39a2a06031040f 887
cappuccino_0.5.1-10.2.dsc
dae2322d37f4a8320e5835535bcd70d072cdbcf5e6d99bfac44dda16d3e07235 5146
cappuccino_0.5.1-10.2.diff.gz
1665ae2225114264cc9c74cf174ba4f88b0ccf9efd6378c09189ac084fe264da 90792
cappuccino_0.5.1-10.2_all.deb
6f7b2122d95c5d1b882ed872c65bb55bbf1184ace76590e77216d08fb44c5758 5600
cappuccino_0.5.1-10.2_amd64.buildinfo
Files:
01420ac22f34501066cc99fb5004655f 887 games optional cappuccino_0.5.1-10.2.dsc
600553c08e23006ae9ca4944068a16b1 5146 games optional
cappuccino_0.5.1-10.2.diff.gz
e8e73c19297a2c10fe061562b188a1ab 90792 games optional
cappuccino_0.5.1-10.2_all.deb
38337ff95f4db1edceb8f0031496384a 5600 games optional
cappuccino_0.5.1-10.2_amd64.buildinfo
Fix polygen not found when running cappuccino as root.
--- a/cappuccino
+++ b/cappuccino
@@ -20,14 +20,16 @@
except OSError:
PLUGIN_DIR = "/usr/share/cappuccino/"
+POLYGEN_PATHNAME = "/usr/games/polygen"
+
# text to see if polygen is available
-if not os.access("/usr/games/polygen",os.X_OK):
+if not os.access(POLYGEN_PATHNAME,os.X_OK):
print ("Error: polygen must be installed")
print ("See http://www.polygen.org;)
sys.exit(1)
# to be discussed
-pipe_command = 'polygen %s' % os.path.join(PLUGIN_DIR, 'cappuccino.grm')
+pipe_command = '%s %s' % (POLYGEN_PATHNAME, os.path.join(PLUGIN_DIR, 'cappuccino.grm'))
class CappuccinoSplash(Gtk.Window):
def __init__(self):
@@ -94,7 +96,7 @@
GObject.source_remove(self.timeouter)
def get_log_data(self):
- p = os.popen("polygen -X 50 %s" % os.path.join(PLUGIN_DIR,"compileline.grm"))
+ p = os.popen("%s -X 50 %s" % (POLYGEN_PATHNAME, os.path.join(PLUGIN_DIR,"compileline.grm")))
self.log = p.readlines()
p.close()
Bug#1051355: No more crash, this is fixed
Thank you for the upload, I can confirm this is fixed. The CIs PASS now: - <https://salsa.debian.org/php-team/pear/phpsysinfo/-/jobs/4704881#L878> - <https://salsa.debian.org/php-team/pear/phpldapadmin/-/jobs/4704895#L524> -- William Desportes
Bug#1051869: ITP: php-di -- A dependency injection container meant to be practical, powerful, and framework-agnostic
Package: wnpp Owner: William Desportes Severity: wishlist * Package name : php-di * Version : 7.0.5 * Upstream Author : Matthieu Napoli * URL : https://github.com/PHP-DI/PHP-DI * License : MIT * Programming Lang: PHP * Description : PHP-DI is a dependency injection container meant to be practical, powerful, and framework-agnostic VCS-Git: https://salsa.debian.org/php-team/pear/php-di
Bug#1051789: RM: sphinxcontrib-youtube -- RoQA; abandoned packaging, MIA
Package: ftp.debian.org Severity: normal Usertags: rm-request User: ftp.debian@packages.debian.org Usertags: remove Hi, Due to #943690 and the current packaging status, please proceed with deleting the package sphinxcontrib-youtube. The package is not maintained, no new version since 2014. Only one version was uploaded. -- William Desportes
Bug#989455: (no subject)
Is there anything that can be done to help this subject ? Only having chrome-driver does not cover all CPU architectures and is problematic for autopkgtests.
Bug#1049980: (no subject)
Control: forwarded -1 https://salsa.debian.org/php-team/pear/phpsysinfo/-/commit/e52aacf0d211c36cea35c39b51c72e14bd5c2845 Thank you for translating into Swedish !
Bug#1051473: ITP: php-di-invoker -- PHP library that allows to invoke callables with named parameters in a generic, and extensible way
Package: wnpp Owner: William Desportes Severity: wishlist * Package name : php-di-invoker * Version : 2.3.4 * Upstream Author : Matthieu Napoli * URL : https://github.com/PHP-DI/Invoker * License : MIT * Programming Lang: PHP * Description : php-di-invoker is a PHP library that allows to invoke callables with named parameters in a generic, and extensible way. VCS-Git: https://salsa.debian.org/php-team/pear/php-di-invoker
Bug#1051355: Also affects jquery-timepicker and phpsysinfo
This is probably what crashes the test suite of jquery-timepicker and
phpsysinfo:
https://ci.debian.net/data/autopkgtest/testing/amd64/j/jquery-timepicker/37547785/log.gz
phpsysinfo does not show up for now since I just realized failures where not
detected in a proper way. The fix is uploaded.
One crash can be seen in:
https://ci.debian.net/data/autopkgtest/unstable/amd64/p/phpsysinfo/37551390/log.gz
With the fix the same one as jquery-timepicker shows up.
Here are some crash logs of the chrome webdriver using sid and phpsysinfo
autopkgtest:
ERROR: test_dynamic_page (__main__.TestPhpSysinfoWeb.test_dynamic_page)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest.Rf2SdY/build.r15/src/./debian/tests/test_phpsysinfo_web.py",
line 48, in test_dynamic_page
WebDriverWait(self.driver, 60).until(lambda x: x.find_element(By.ID,
"s_processes").text != "")
File "/usr/lib/python3/dist-packages/selenium/webdriver/support/wait.py",
line 86, in until
value = method(self._driver)
File "/tmp/autopkgtest.Rf2SdY/build.r15/src/./debian/tests/test_phpsysinfo_web.py",
line 48, in
WebDriverWait(self.driver, 60).until(lambda x: x.find_element(By.ID,
"s_processes").text != "")
File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/webdriver.py",
line 738, in find_element
return self.execute(Command.FIND_ELEMENT, {"using": by, "value":
value})["value"]
^
File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/webdriver.py",
line 344, in execute
self.error_handler.check_response(response)
File
"/usr/lib/python3/dist-packages/selenium/webdriver/remote/errorhandler.py",
line 229, in check_response
raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.WebDriverException: Message: unknown error: session
deleted because of page crash
from unknown error: cannot determine loading status
from tab crashed
(Session info: headless chrome=116.0.5845.180)
Stacktrace:
#0 0x55876cf735aa
#1 0x55876cc95b89
#2 0x55876cc8265c
#3 0x55876cc81be9
#4 0x55876cc80d3e
#5 0x55876cc80bda
#6 0x55876cc7faa9
#7 0x55876cc800a5
#8 0x55876cc8e218
#9 0x55876cc8f059
#10 0x55876cc9fd63
#11 0x55876cca3e98
#12 0x55876cc805a1
#13 0x55876cc9fa0f
#14 0x55876cd0acc2
#15 0x55876ccf364a
#16 0x55876ccc735b
#17 0x55876ccc8936
#18 0x55876cf40fbc
#19 0x55876cf44113
#20 0x55876cf43baa
#21 0x55876cf445fc
#22 0x55876cf4acda
#23 0x55876cf44987
#24 0x55876cf1cdf1
#25 0x55876cf5dd99
#26 0x55876cf5df93
#27 0x55876cf6c243
#28 0x7ff4384a63ec
==
ERROR: test_dynamic_page (__main__.TestPhpSysinfoWeb.test_dynamic_page)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest.Rf2SdY/build.r15/src/./debian/tests/test_phpsysinfo_web.py",
line 23, in tearDown
self.driver.close()
File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/webdriver.py",
line 455, in close
self.execute(Command.CLOSE)
File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/webdriver.py",
line 344, in execute
self.error_handler.check_response(response)
File
"/usr/lib/python3/dist-packages/selenium/webdriver/remote/errorhandler.py",
line 229, in check_response
raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.InvalidSessionIdException: Message: invalid session
id
Stacktrace:
#0 0x55876cf735aa
#1 0x55876cc95b89
#2 0x55876ccc6ed8
#3 0x55876ccc8936
#4 0x55876cf40fbc
#5 0x55876cf44113
#6 0x55876cf43baa
#7 0x55876cf445fc
#8 0x55876cf4acda
#9 0x55876cf44987
#10 0x55876cf1cdf1
#11 0x55876cf5dd99
#12 0x55876cf5df93
#13 0x55876cf6c243
#14 0x7ff4384a63ec
==
ERROR: test_static_page (__main__.TestPhpSysinfoWeb.test_static_page)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest.Rf2SdY/build.r15/src/./debian/tests/test_phpsysinfo_web.py",
line 29, in test_static_page
vitals = WebDriverWait(self.driver, 60).until(lambda x: x.find_element(By.ID,
"vitals"))
^^^
File "/usr/lib/python3/dist-packages/selenium/webdriver/support/wait.py",
line 86, in until
value = method(self._driver)
File "/tmp/autopkgtest.Rf2SdY/build.r15/src/./debian/tests/test_phpsysinfo_web.py",
line 29, in
vitals = WebDriverWait(self.driver, 60).until(lambda x: x.find_element(By.ID,
"vitals"))
^^^
File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/webdriver.py",
line 738, in find_element
Bug#976435: EIDAS retitle?
I think this is a very good idea. However you used ITP: Do you intend to package it some time soon, it's been 3 years. I think it would be better to rename this bug to RFP: It's also worth checking if some Debian packages already embed the certificates. -- William Desportes
Bug#1050300: mkbootimg package missing gki module
Package: mkbootimg Version: 1:34.0.4-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: william.g...@linaro.org Dear Maintainer, When attempting to run /usr/bin/mkbootimg, the following is observed: root@linaro-developer:~# /usr/bin/mkbootimg --help Traceback (most recent call last): File "/usr/bin/mkbootimg", line 31, in from gki.generate_gki_certificate import generate_gki_certificate ModuleNotFoundError: No module named 'gki' This appears to be the result of the gki module missing from the mkbootimg package: https://packages.debian.org/sid/all/mkbootimg/filelist This bug can be resolved by installing the necessary python files (such as generate_fki_certificate.py) located at system/tools/mkbootimg/gki: https://sources.debian.org/src/android-platform-tools/34.0.4-1/system/tools/mkbootimg/gki/ I think the generate_gki_certificate dependency was introduced for the version 33.0.3 release of android-tools, so other Debian versions may be affected as well. Thank you, William Breathitt Gray -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: arm64 (aarch64) Kernel: Linux 6.5.0-rc6-qcomlt-arm64-00060-g797651a03cd8 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages mkbootimg depends on: ii python3 3.11.4-5+b1 mkbootimg recommends no packages. mkbootimg suggests no packages. -- no debconf information
Bug#1049865: php-pear: Creation of dynamic property PEAR_Error::$callback is deprecated
Package: php-pear Version: 1:1.10.13+submodules+notgz+2022032202-2 Severity: normal Tags: patch X-Debbugs-Cc: utka...@debian.org When running the test suite of https://github.com/pear/Console_Getopt Creation of dynamic property PEAR_Error::$callback is deprecated in /usr/share/php/PEAR.php on line 912 Fixed by https://github.com/pear/pear-core/commit/4217e3ea503ba6c0651ea2d182fb9cb88f21ce0b (https://github.com/pear/pear-core/pull/124)
Bug#1049342: RM: smtpprox-loopprevent -- RoQA; abandoned upstream
Package: ftp.debian.org Severity: normal Usertags: rm-request User: ftp.debian@packages.debian.org Usertags: remove Hi, Please proceed with deleting the package smtpprox-loopprevent. it's not maintained, no new version since 10+ years. -- William Desportes
Bug#1049341: RM: smtpprox -- ROM; abandoned upstream
Package: ftp.debian.org Severity: normal Usertags: rm-request User: ftp.debian@packages.debian.org Usertags: remove Hi, Please proceed with deleting the package smtpprox. it's not maintained, no new version since 11 years. -- William Desportes
Bug#723786: (no subject)
Control: retitle -1 RFP: php-v8js -- V8 Javascript Engine for PHP Has now PHP 7 & 8 compatibility (soon to be published I assume). * URL: https://github.com/phpv8/v8js
Bug#1043508: Thank you
Thank you both for your quick patch and upload ! No more work to do then, yay ^^
Bug#1041333: syncthing: systemd user service fails to start due to bad configuration file version
Package: syncthing Version: 1.19.2~ds1-1+b4 Severity: grave Justification: renders package unusable X-Debbugs-Cc: goodsp...@tilde.fsfans.club Dear Maintainer, The syncthing package installed on trixie/sid won't star from systemd. $ systemctl --user start syncthing Tracking down the journal, it shows: [start] INFO: syncthing v1.19.2-ds1 "Fermium Flea" (go1.19.8 linux-amd64) debian@debian 2023-04-09 10:47:16 UTC [start] WARNING: Failed to initialize config: config file version (37) is newer than supported version (36). If this is expected, use --allow-newer-config to override. systemd [1301]: syncthing.service: Main process exited, code=exited, status=1/FAILURE -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (700, 'testing'), (650, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.3.0-1-amd64 (SMP w/20 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages syncthing depends on: ii init-system-helpers 1.65.2 ii libc62.37-5 syncthing recommends no packages. syncthing suggests no packages. -- no debconf information
Bug#1040896: raspi-firmware: Unable to uninstall raspi-firmware on amd64 systems
Package: raspi-firmware Version: 1.20220830+ds-1 Severity: important X-Debbugs-Cc: wiiliamchung...@gmail.com Dear Maintainer, Users are not able to uninstall raspi-firmware on amd64 systems, as the initramfs hook will exit with the following error: > raspi-firmware: missing /boot/firmware, did you forget to mount it? > run-parts: /etc/initramfs/post-update.d//z50-raspi-firmware exited with > return code 1 > run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 > dpkg: error processing package linux-image-6.1.0-10-amd64 (--configure): >installed linux-image-6.1.0-10-amd64 package post-installation script >subprocess returned error exit status 1 > dpkg: dependency problems prevent configuration of linux-image-amd64: >linux-image-amd64 depends on linux-image-6.1.0-10-amd64 (= 6.1.37-1); >however: > Package linux-image-6.1.0-10-amd64 is not configured yet. > > dpkg: error processing package linux-image-amd64 (--configure): >dependency problems - leaving unconfigured > Errors were encountered while processing: >linux-image-6.1.0-10-amd64 >linux-image-amd64 > E: Sub-process /usr/bin/dpkg returned an error code (1) To purge raspi-firmware, users will need to prevent /etc/kernel/postinst.d/z50-raspi-firmware from triggering. A current workaround is to add `exit 0` at the first line of /etc/kernel/postinst.d/z50-raspi-firmware I don't know where raspi-firmware was pulled in from, but the package was found in both systems where I installed debian bookworm (12) using the amd64 KDE live image. I assume that raspi-firmware is included by default. -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages raspi-firmware depends on: ii dosfstools 4.2-1 ii dpkg1.21.22 raspi-firmware recommends no packages. Versions of packages raspi-firmware suggests: ii bluez-firmware 1.2-9 ii firmware-brcm80211 20230210-5 ii firmware-misc-nonfree 20230210-5
Bug#1039773: False positive FTBFS
Control: retitle -1 php-dompdf: FTBFS because of fonts-liberation (#1038940) Control: tags -1 + pending Control: user pkg-php-p...@lists.alioth.debian.org Control: usertag -1 - phpunit Control: usertag 1039835 - phpunit This is a false positive for phpunit, and the real reason is #1038940
Bug#1039835: False positive FTBFS
Control: tags -1 + wontfix Hi Athos, This is a false positive. Can you check your other reports for similar false positives? -- William Desportes
Bug#1028659: angband-audio: should this package be removed?
Control: forwarded -1 https://salsa.debian.org/games-team/angband Hi, That's cool ! You may want to setup a GitLab Salsa CI to check your package is in good shape: Go to "Settings > CI/CD > General pipelines > CI/CD configuration file" And set "recipes/debian.yml@salsa-ci-team/pipeline" And push a new commit See: https://salsa.debian.org/salsa-ci-team/pipeline#debian-pipeline-for-developers And maybe get in touch with games Debian DDs to get it uploaded. IRC OFTC is quite active and you may find DDs to help you. -- William Desportes
Bug#1037547: rpmdb
The fapolicyd.conf file contains trust = rpmdb,file Since debian doesn't, by default, have an rpm database. Even when you install rpm on debian the database doesn't include most OS executables.
Bug#1033388: Thank you !
Control: forwarded -1 https://salsa.debian.org/php-team/pear/phpsysinfo/-/commit/9671a58f5eae1a2720e7fb57c0ee62fdfeefacd1 Control: tags -1 + pending Thank you for translating !, and sorry about the response time :/
Bug#1036313: php-slim-psr7: Useless (and harmful) dependency on (recent) php-symfony-polyfill-php80
Control: forwarded -1 https://salsa.debian.org/php-team/pear/php-slim-psr7/-/commit/d2e579fa2202265888baf9649cadce7f924fd93b Control: found -1 php-slim-psr7/1.6.1-1~bpo11+1 Hi David, This is a complicated subject that I already brought to you, but there is no easy solution. First, for the backports version: thank you for reporting this bug ! There is no change impacting the library in the diff: https://github.com/symfony/polyfill-php80/compare/v1.22.0...v1.26.0 Lowering the version was already done for phpMyAdmin's PPA for Ubuntu jammy. So I lowered the required version to symfony/polyfill-php80 1.22 available in Bullseye to fix this bug. Secondly, the subject that needs to be addressed: Users do what they want and use php libraries on different versions that Debian was shipped with. This is something some people want to avoid thinking about, but it's a reality. - First point: Technically from a packaging stand point, there is no way to block a library or app's usage with another version than the one shipped by Debian. It's only a deb file. - Second point: if we could do that, the user could still run a library or app on a different PHP version. The only way is that the code must protect itself from being run on another version of PHP. So if "pkg-php-tools" autoloader tool would add some code in the autoloader to ensure PHP classes are not run on a different PHP version then yes we can drop the polyfill libraries. The code would be protecting itself and we would avoid problems like: https://bugs.launchpad.net/ubuntu/+source/phpmyadmin/+bug/2016016 The top stack solution we had to do on Ubuntu since one library did screw up it's packaging was to force phpMyAdmin to require PHP 8. Since the code did not protect itself, and this all resulted in a crash. Ref: https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/phpmyadmin/+git/phpmyadmin/+merge/442711 I am awaiting the proper changes in Debian's packaging tools to be able to move out of polyfills. PHP multi version support is complicated. Users do what they want. And as a maintainer of the tools, I have the angry users to handle when the proper safeties and polyfills are not in place when they decide to use another PHP version to run the tool/library packaged. https://github.com/phpmyadmin/phpmyadmin/issues/17523 and https://github.com/phpmyadmin/phpmyadmin/issues/17503 reflect that. I will not be dropping the dependency on the polyfill because upstream is requiring it, and because users will run the code on other versions. And you can not even argue with the users, that will not understand. Upstream says it supports PHP 7.4 so it does: https://github.com/slimphp/Slim-Psr7/blob/1.6.x/composer.json#L31 And makes the polyfill required. The users do not even know how things are packaged and will blame you for it anyway. Conclusion: I am not considering going blind about what users do with their Debian and Ubuntu releases. They install tools from other sources. Ref: deb sury for other PHP versions. I hope you understand, maybe something can be done to ensure the code protects itself for example adding a bit of code to abort execution when it's used on another version that for example: - The php constraint on composer.json (https://github.com/slimphp/Slim-Psr7/blob/1.6.x/composer.json#L31) - Or the Debian shipped version of PHP Let me know your thoughts. -- William
Bug#1035929: RM: sbt -- RoQA; no rdeps, outdated, no upload since 2017
Package: ftp.debian.org Severity: normal Usertags: rm-request User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-CC: fre...@linux.vnet.ibm.com Hi, Please proceed to deleting the package: sbt Last upload: 2017-08-12, 6 years ago. I emailed the package maintainer "Frédéric Bonnard" about an FTP RM possibility and quote of the reply: "I'm not working on sbt since long nor following closely Debian Java development. Though I see the package didn't get updated much to say the least. Also at that time it was a pain to bootstrap and upstream never really wanted to support other ways of distributing it. All in all, I don't see any real future for sbt in Debian..." -- William Desportes
Bug#1034832: www.debian.org: Distribution Archives: ftp.riken.jp no longer hosts debian-archives mirror
Package: www.debian.org Severity: normal X-Debbugs-Cc: william.poe...@gmail.com Dear Maintainer, The archive mirror ftp.riken.jp no longer hosts the debian-archives mirror. This has been verified on 2023-04-25. Affected page: https://www.debian.org/distrib/archive
Bug#1034831: www.debian.org: Distribution Archives: wrong URL/link for hanzubon.jp
Package: www.debian.org Severity: normal X-Debbugs-Cc: william.poe...@gmail.com Dear Maintainer, On the Distribution Archives page (https://www.debian.org/distrib/archive), the HTTP link for hanzubon.jp is wrong. The correct URL is: http://hanzubon.jp/debian-archive/ The URL is currently inaccessible, but I'm not sure if the service is dead, or if there is a glitch on the server.
Bug#1034622: docker.io: Installing docker broke my server: iptables
Package: docker.io Version: 20.10.5+dfsg1-1+deb11u2 Severity: important Dear Maintainer, Installing docker.io rendered my server inoperable. Solely as a result of "apt-get install docker.io", it installed iptables rules which corrupted the network configuration rendering the network unusable. Stopping docker with "systemctl docker stop" did not restore the network state to operability. Uninstalling docker with "dpkg --purge docker.io" did not restore the network state to operability. Manually removing the iptables rules docker installed did not restore the network state to operability. It was a server running lots of vms, so it was a pain to reboot -- the solution which finally restored the network function. The problem was successfully worked around by adding a line to /etc/default/docker: DOCKER_OPTS=--iptables=false Merely installing a software package SHOULD NOT render the network unusable. Suggested correction: Either add iptables=false as default, or do not immediately start docker upon installation so that merely installing docker does not change the network configuration on the machine. -- System Information: Debian Release: 11.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.261-deb11 (SMP w/40 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages docker.io depends on: ii adduser 3.118 ii containerd 1.4.13~ds1-1~deb11u3 ii init-system-helpers 1.60 ii iptables 1.8.7-1 ii libc62.31-13+deb11u5 ii libdevmapper1.02.1 2:1.02.175-2.1 ii libsystemd0 247.3-7+deb11u1 ii lsb-base 11.1.0 ii runc 1.0.0~rc93+ds1-5+deb11u2 ii tini 0.19.0-1 Versions of packages docker.io recommends: ii apparmor 2.13.6-10 ii ca-certificates 20210119 ii cgroupfs-mount 1.4 ii git 1:2.30.2-1+deb11u2 ii needrestart 3.5-4+deb11u2 ii xz-utils 5.2.5-2.1~deb11u1 Versions of packages docker.io suggests: pn aufs-tools ii btrfs-progs5.10.1-2 ii debootstrap1.0.123+deb11u1 pn docker-doc ii e2fsprogs 1.46.2-2 pn rinse pn rootlesskit ii xfsprogs 5.10.0-4 pn zfs-fuse | zfsutils-linux -- Configuration Files: /etc/default/docker changed: DOCKER_OPTS=--iptables=false -- no debconf information
Bug#1033802: dropbear-initramfs: sleep and cat not found
Hm? Installing cryptsetup-initramfs, and letting it unlock devices (incl. those holding the root FS) at early boot stage, definitely doesn't prevent rescue mode or getting an initramfs shell. I mean that the Debian installer after some rounds of getter a rescue chroot to debug this bug did start not finding "sda_crypt" and then the boot was falling into a shell and the system not booting. At this point I re-installed the full system. Because clearly there was an open and mounted /dev/mapper/sda_crypt Anyway, it's off topic I think ^^ What are you trying to do by the way? Are you installing dropbear-initramfs on that machine not because you *need* to get a remote initramfs shell in order to boot, but to have a way to remotely access access the machine should something break at early boot stage? On this machine, I was planning to do the same config that works perfectly on my RaspberryPi to remote SSH unlock the disk. But on this machine (it has two ethernet ports) It does not work and I have only bugs. For now I have a screen so I can unlock the disk with a keyboard. Nope. The /usr/bin/ipconfig binary from the initramfs image comes from /usr/lib/klibc/bin/ipconfig which dropbear-initramfs indirectly has a hard Depends: on… Well maybe, but clearly this is not the hole truth I bet. Right after boot and (user login?) it prints the missing ipconfig missing message. So the script is also called out of initramfs. Anyway, the ‘/run/net-*.conf’ glob and the ipconfig call both come initramfs-tools' configure_networking(). As I wrote before if these fail it's most likely because there is nothing blocking at initramfs stage, so execution is handed over to init(1) before configure_networking() has a chance to terminate (it runs in the background). This, again, smells like #1015810. I have to dig on this aspect. Different that for the RaspberryPi setup, this machine has nothing hooked to it's ethernet ports. For the record, this is my RaspberryPi setup: /etc/dropbear/initramfs/dropbear.conf DROPBEAR_OPTIONS="-I 180 -j -k -p -s" /etc/initramfs-tools/initramfs.conf IP=192.168.4.45::192.168.4.1:255.255.255.0:rpi:eth0:off
Bug#1033802: dropbear-initramfs: sleep and cat not found
> Doesn't look like a dropbear-initramfs bug, possibly a missing module if the device isn't exposed at initramfs stage. I re-installed the machine, at this point I no longer have the sleep and cat missing bug. Not sure If I want to try having it back, with cryptsetup it does not like rescue mode initramfs updates. That said I have a new one (I did not install the basic system utilities): It now says: init-premount/dropbear: line 366: ipconfig: not found And right after the message about net-*.conf The system does not have ipconfig installed, I would say this is a bug that should be fixed in the dropbear script. Or added a as a package dependency/requirement ? -- William Desportes
Bug#1033802: dropbear-initramfs: sleep and cat not found
My Debug did some small progress the other day, and can confirm I walked into https://bugs.debian.org/1015810 > /scripts/init-premount/dropbear: line 300: can't open '/run/net-*.conf': No such file or directory That said, It also says > g: eth0: SI0CGIFINDEX: No such device > g: no devices to configure So there is maybe more to my bug. > I'll be happy to try to improve /usr/share/doc/dropbear-initramfs/README.initramfs if needed, or even create an HTML page under .pages.debian.net if online material is desired I would be glad to help ! :) > but I think the wiki shouldn't be used as a brain dump that way without coordination with the maintainer (duplication of existing documentation shipped in the source package tend to rot and diverge over time). I agree, I was quite deprecated and past out. Can you please revert your change to the wiki, it's not user friendly and will help nobody since it does not link to a proper page. Many internet sources do still link to the wiki page. The page could be emptied and have a link to a .pages.debian.net But the wiki page should redirect to somewhere. Maybe the README.initramfs on Debian sources or Salsa ? > See the NEWS entry for 2015.68-1, /etc/ssh and the initramfs image have different access control so blindly suggesting to convert key materiel from one to the other is a bad idea. The page also had misleading/ confusing information between dropbear and dropbear-initramfs. I did not apply the key part as I saw it generated keys by itself and dropbear-initramfs worked perfectly without key instructions on my RaspberryPi 4B -- William Desportes
Bug#1033802: dropbear-initramfs: sleep and cat not found
Thanks for the quick reply, that's very appreciated >Please file bugs using the reportbug(1) template and provide a debug >output, there is nothing actionable here. The affected version isn't >even specified let alone loose dependencies… Well, it's complicated to use reportbug on machine that does not boot at time of reporting this. It's pure Debian 12. Will report more about the dependencies. With the DI alpha2 I managed to recovery boot into a shell and remove the package dropbear-initramfs It of course makes me able to boot afterwards, but when I install it back the error is back. >FWIW sleep and cat are provided by busybox which dropbear-initramfs >Depends on. Also we have an autopkgtest for dropbear-initramfs (and >encrypted root FS), and the issue is not reproducible there. I agree but in reality they seem not to exist, I am not sure how it's even possible. >If there is nothing blocking between the init-premount and init-bottom >scripts this might be the same as https://bugs.debian.org/1015810 . I will have a look to this bug >FYI this page is not maintained by the src:dropbear maintainer. I'll >even delete it since it contains misleading and even potentially >dangerous information. Can you be more specific?, I updated some of it yesterday. The updating keys seems to be useful. I will most updates as soon as I manage to pin point this. It's very very weird, my first thought is that dropbear maybe does not start Le 1 avril 2023 23:50:48 GMT+02:00, Guilhem Moulin a écrit : >Control: tag -1 unreproducible moreinfo > >On Sat, 01 Apr 2023 at 18:36:47 +0200, William Desportes wrote: >> I am trying to sort out this bug, but the machine is blocked in an endless >> loop >> >> It does /scripts/init-bottom >> >> And then the monitor displays in an endless loop: >> /scripts/init-premount/dropbear: line 339: sleep: not found >> /scripts/init-premount/dropbear: line 149: cat: not found > >Please file bugs using the reportbug(1) template and provide a debug >output, there is nothing actionable here. The affected version isn't >even specified let alone loose dependencies… > >FWIW sleep and cat are provided by busybox which dropbear-initramfs >Depends on. Also we have an autopkgtest for dropbear-initramfs (and >encrypted root FS), and the issue is not reproducible there. > >If there is nothing blocking between the init-premount and init-bottom >scripts this might be the same as https://bugs.debian.org/1015810 . > >> I used https://wiki.debian.org/DropBear as an example and did set: >> DROPBEAR_OPTIONS="-p -s" > >FYI this page is not maintained by the src:dropbear maintainer. I'll >even delete it since it contains misleading and even potentially >dangerous information. > >Authoritative information can be found in >/usr/share/doc/dropbear-initramfs/README.initramfs and the config file. >
Bug#1033802: dropbear-initramfs: sleep and cat not found
Package: dropbear-initramfs Severity: important I am trying to sort out this bug, but the machine is blocked in an endless loop It does /scripts/init-bottom And then the monitor displays in an endless loop: /scripts/init-premount/dropbear: line 339: sleep: not found /scripts/init-premount/dropbear: line 149: cat: not found I think the source code is at: https://salsa.debian.org/debian/dropbear/-/blob/debian/2022.83-1/debian/initramfs/scripts/init-bottom/dropbear#L48 So it's maybe waiting for a non starting dropbear. I used https://wiki.debian.org/DropBear as an example and did set: DROPBEAR_OPTIONS="-p -s"
Bug#1033200: Reply to email -- notes on Debian -- Exposition re Xubuntu
e connection to us.archive.ubuntu.com:443 (2001:67c:1562::15). - connect (101: Network is unreachable) Could not connect to us.archive.ubuntu.com:443 (91.189.91.38). - connect (111: Connection refused) Cannot initiate the connection to us.archive.ubuntu.com:443 (2001:67c:1562::18). - connect (101: Network is unreachable) W: Failed to fetch https://us.archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease Cannot initiate the connection to us.archive.ubuntu.com:443 (2001:67c:1562::15). - connect (101: Network is unreachable) Cannot initiate the connection to us.archive.ubuntu.com:443 (2001:67c:1562::18). - connect (101: Network is unreachable) W: Failed to fetch https://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead == The same procedure was tried on a plain Ubuntu machine. It produced very similar results. The "Some index files failed to download. They have been ignored, or old ones used instead" is not a real attention grabber as an error message and Is pretty much all that might be easily visible with more common update methods. == Tim, This resolution is MYSTERIOUS to me. If you have ideas as to why it might have worked I would appreciate your input. While a similar approach fails with Ubuntu and Xubuntu is not so mystifying ... It would appear that their distribution is just not able to deal with "https://; unlike Debian. I will now try a clean install of Debian ... I expect some problems and should have added infornation for you by early next week. Much thanks, WILLIAM O RICHMOND wor...@windstream.net
Bug#1033481: postfwd not stopped on systemd stop
Package: postfwd Version: 1.35-6 Issue: When stopping the postfwd systemd unit (using `systemctl stop postfwd`), postfwd processes are not stopped. Logs: ``` Mar 25 21:01:18 pmg-test.prorelay.nl systemd[1]: postfwd.service: Unit process 601020 (/usr/sbin/postf) remains running after unit stopped. Mar 25 21:01:18 pmg-test.prorelay.nl systemd[1]: postfwd.service: Unit process 601021 ( postfwd2::cach) remains running after unit stopped. Mar 25 21:01:18 pmg-test.prorelay.nl systemd[1]: postfwd.service: Unit process 601022 ( postfwd2::poli) remains running after unit stopped. Mar 25 21:01:18 pmg-test.prorelay.nl systemd[1]: postfwd.service: Unit process 601023 ( postfwd2::poli) remains running after unit stopped. Mar 25 21:01:18 pmg-test.prorelay.nl systemd[1]: postfwd.service: Unit process 601024 ( postfwd2::poli) remains running after unit stopped. Mar 25 21:01:18 pmg-test.prorelay.nl systemd[1]: postfwd.service: Unit process 601025 ( postfwd2::poli) remains running after unit stopped. Mar 25 21:01:18 pmg-test.prorelay.nl systemd[1]: postfwd.service: Unit process 601026 ( postfwd2::poli) remains running after unit stopped. Mar 25 21:01:18 pmg-test.prorelay.nl systemd[1]: postfwd.service: Unit process 601027 ( postfwd2::poli) remains running after unit stopped. Mar 25 21:01:18 pmg-test.prorelay.nl systemd[1]: postfwd.service: Unit process 601028 ( postfwd2::poli) remains running after unit stopped. Mar 25 21:01:18 pmg-test.prorelay.nl systemd[1]: postfwd.service: Unit process 601029 ( postfwd2::poli) remains running after unit stopped. Mar 25 21:01:18 pmg-test.prorelay.nl systemd[1]: postfwd.service: Unit process 601030 ( postfwd2::poli) remains running after unit stopped. Mar 25 21:01:18 pmg-test.prorelay.nl systemd[1]: postfwd.service: Unit process 601031 ( postfwd2::poli) remains running after unit stopped. Mar 25 21:01:18 pmg-test.prorelay.nl systemd[1]: postfwd.service: Unit process 601032 ( postfwd2::poli) remains running after unit stopped. Mar 25 21:01:18 pmg-test.prorelay.nl systemd[1]: Failed to start LSB: start and stop the postfw daemon. ``` The following processes are still running: ``` /usr/sbin/postfwd --summary=600 --cache=600 --cache-rdomain-only --cache-no-size --daemon --file=/etc/postfix/postfwd.cf --interface=127.0.0.1 --port=10040 --user=postfw --group=postfw --pidfile=/var/run/postfwd.pid postfwd2::cache postfwd2::policy postfwd2::policy::child ``` Reproduce: - Install postfwd (`apt install postfwd`) - Set `STARTUP=1` in /etc/default/postfwd - Stop postfwd using systemd (`systemctl stop postfwd`) With kind regards, William Edwards
Bug#1033209: This info seems to have inadvertently been omitted from the Debian Bug report logs
Package: apt-get Version: 2.2.4 From: William O Richmond wor...@windstream.net When, for example, I do: orville@flinta:~$ sudo apt-get install lynx [sudo] password for orville: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: lynx-common The following NEW packages will be installed: lynx lynx-common 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 1,844 kB of archives. After this operation, 5,768 kB of additional disk space will be used. Do you want to continue? [Y/n] y Ign:1 http://deb.debian.org/debian bullseye/main amd64 lynx-common all 2.9.0dev.6-3~deb11u1 Ign:2 http://deb.debian.org/debian bullseye/main amd64 lynx amd64 2.9.0dev.6-3~deb11u1 Err:1 http://deb.debian.org/debian bullseye/main amd64 lynx-common all 2.9.0dev.6-3~deb11u1 Connection failed [IP: 199.232.34.132 80] Err:2 http://deb.debian.org/debian bullseye/main amd64 lynx amd64 2.9.0dev.6-3~deb11u1 Connection failed [IP: 199.232.34.132 80] E: Failed to fetch http://security.debian.org/debian-security/pool/updates/main/l/lynx/lynx-common_2.9.0dev.6-3%7edeb11u1_all.deb Connection failed [IP: 199.232.34.132 80] E: Failed to fetch http://security.debian.org/debian-security/pool/updates/main/l/lynx/lynx_2.9.0dev.6-3%7edeb11u1_amd64.deb Connection failed [IP: 199.232.34.132 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? orville@flinta:~$ orville@flinta:~$ orville@flinta:~$ lynx -bash: lynx: command not found orville@flinta:~$ I have been mystified by this sort of behavior for a number of months. I have made no headway. I have effectively lost the use of debian linux due to problems resulting from the failure of the update and installation mechanisms. For me this has also become a major security problem. Clamav has ceased to function after months of freshclam failures. Firefox is getting older and older. I have a number of machines running various flavors of ubuntu. The problems which I have with debian are very much the same as ubuntu. I have a Fedora machine as well. I normally have not much liked Fedora because I find it constricting, however it is up to date. I had a spell where its updates were very slow, but it seems to have gotten past that time. I have installed Fedora on a second machine, and if I can resolve the problems with it I will begin the VERY laborious process of porting applications and data to Fedora. I have been considering that maybe some part of the update process, (curl ??), has been being intercepted ... perhaps by my ISP?? ... but I don't know. I have been studying VPN implementation. I really require a VPN with its own IP address to test this. I would have to do this using Fedora or some other system as I cannot download VPN components successfully on Debian or Ubuntu machines. I have successfully connected to both the Debian and Ubuntu sites using ncftp and also to a limited extent using lynx. I was able to download files with ncftp and to a lesser extent with lynx. Apt-get etc however seem to have no luck. I can make no sense of any of this. Needless to say, I have not been able to download and install "reportbug" and am probably obviously not using it. It has seemed to be to be unlikely that I am the only person with these problems, however I do apologize for waiting so long, I would appreciate at least a note that somebody has received this missive and am actually hoping for some resolution. I am most easily reached by email at wor...@windstream.net. Thanking everyone in advance for their help. William O Richmond orville@flinta:~$ uname -a Linux flinta 5.10.0-14-amd64 #1 SMP Debian 5.10.113-1 (2022-04-29) x86_64 orville@flinta:~$ ls -l /lib/*/libc.so.6 lrwxrwxrwx 1 root root 12 Mar 17 2022 /lib/x86_64-linux-gnu/libc.so.6 -> libc-2.31.so orville@flinta:~$ apt show libc6 | grep ^Version Version: 2.31-13+deb11u3
Bug#1033200: apt, apt-get, aptitude and others have been failing for an extended period.
Package: apt-get Version: 2.2.4 From: William O Richmond wor...@windstream.net When, for example, I do: orville@flinta:~$ sudo apt-get install lynx [sudo] password for orville: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: lynx-common The following NEW packages will be installed: lynx lynx-common 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 1,844 kB of archives. After this operation, 5,768 kB of additional disk space will be used. Do you want to continue? [Y/n] y Ign:1 http://deb.debian.org/debian bullseye/main amd64 lynx-common all 2.9.0dev.6-3~deb11u1 Ign:2 http://deb.debian.org/debian bullseye/main amd64 lynx amd64 2.9.0dev.6-3~deb11u1 Err:1 http://deb.debian.org/debian bullseye/main amd64 lynx-common all 2.9.0dev.6-3~deb11u1 Connection failed [IP: 199.232.34.132 80] Err:2 http://deb.debian.org/debian bullseye/main amd64 lynx amd64 2.9.0dev.6-3~deb11u1 Connection failed [IP: 199.232.34.132 80] E: Failed to fetch http://security.debian.org/debian-security/pool/updates/main/l/lynx/lynx-common_2.9.0dev.6-3%7edeb11u1_all.deb Connection failed [IP: 199.232.34.132 80] E: Failed to fetch http://security.debian.org/debian-security/pool/updates/main/l/lynx/lynx_2.9.0dev.6-3%7edeb11u1_amd64.deb Connection failed [IP: 199.232.34.132 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? orville@flinta:~$ orville@flinta:~$ orville@flinta:~$ lynx -bash: lynx: command not found orville@flinta:~$ I have been mystified by this sort of behavior for a number of months. I have made no headway. I have effectively lost the use of debian linux due to problems resulting from the failure of the update and installation mechanisms. For me this has also become a major security problem. Clamav has ceased to function after months of freshclam failures. Firefox is getting older and older. I have a number of machines running various flavors of ubuntu. The problems which I have with debian are very much the same as ubuntu. I have a Fedora machine as well. I normally have not much liked Fedora because I find it constricting, however it is up to date. I had a spell where its updates were very slow, but it seems to have gotten past that time. I have installed Fedora on a second machine, and if I can resolve the problems with it I will begin the VERY laborious process of porting applications and data to Fedora. I have been considering that maybe some part of the update process, (curl ??), has been being intercepted ... perhaps by my ISP?? ... but I don't know. I have been studying VPN implementation. I really require a VPN with its own IP address to test this. I would have to do this using Fedora or some other system as I cannot download VPN components successfully on Debian or Ubuntu machines. I have successfully connected to both the Debian and Ubuntu sites using ncftp and also to a limited extent using lynx. I was able to download files with ncftp and to a lesser extent with lynx. Apt-get etc however seem to have no luck. I can make no sense of any of this. Needless to say, I have not been able to download and install "reportbug" and am probably obviously not using it. It has seemed to be to be unlikely that I am the only person with these problems, however I do apologize for waiting so long, I would appreciate at least a note that somebody has received this missive and am actually hoping for some resolution. I am most easily reached by email at wor...@windstream.net. Thanking everyone in advance for their help. William O Richmond orville@flinta:~$ uname -a Linux flinta 5.10.0-14-amd64 #1 SMP Debian 5.10.113-1 (2022-04-29) x86_64 orville@flinta:~$ ls -l /lib/*/libc.so.6 lrwxrwxrwx 1 root root 12 Mar 17 2022 /lib/x86_64-linux-gnu/libc.so.6 -> libc-2.31.so orville@flinta:~$ apt show libc6 | grep ^Version Version: 2.31-13+deb11u3
Bug#1033163: phpldapadmin: unable to login
Package: phpldapadmin
Version: 1.2.6.3-0.2
Severity: important
Control: -1 patch
Control: forwarded 1009117
https://github.com/leenooks/phpLDAPadmin/commit/34d4f2022214780f93e17a5c8dba15cabc8b82b0
Control: fixed 1009117 phpldapadmin/1.2.6.3-0.1
On phpldapadmin, you can not login.
Here is attached all the patches you need to apply.
The final one "Fix-ldap-connect-PHP-8.1-is-now-a-class.patch" makes this bug
report more true than ever.
Please remove the 149.patch, it's a bundle of patches.
And import all my attachements, I sorted this out and applied DEP-3 headers.
--
William DesportesFrom: Patrick Monnerat
Date: Sat, 18 Mar 2023 16:28:44 +0100
Subject: Fix class name Attribute to PLAAttribute because of PHP8 class name
clash
It has been introduced when class Attribute has been renamed
to PLAAttribute to avoid a name clash with the built-in
class of PHP 8.
Origin: upstream
Forwarded: https://github.com/leenooks/phpLDAPadmin/commit/c90dc06af20b4ec549e43b2b90c018ba0f030cad
Ref: https://www.php.net/manual/en/class.attribute.php
---
lib/Attribute.php| 917 ---
lib/AttributeFactory.php | 2 +-
lib/BinaryAttribute.php | 2 +-
lib/DateAttribute.php| 2 +-
lib/DnAttribute.php | 2 +-
lib/GidAttribute.php | 2 +-
lib/MultiLineAttribute.php | 2 +-
lib/ObjectClassAttribute.php | 2 +-
lib/PLAAttribute.php | 917 +++
lib/PasswordAttribute.php| 2 +-
lib/SelectionAttribute.php | 2 +-
lib/ShadowAttribute.php | 2 +-
lib/Visitor.php | 24 +-
13 files changed, 941 insertions(+), 937 deletions(-)
delete mode 100644 lib/Attribute.php
create mode 100644 lib/PLAAttribute.php
diff --git a/lib/Attribute.php b/lib/Attribute.php
deleted file mode 100644
index 3d040db..000
--- a/lib/Attribute.php
+++ /dev/null
@@ -1,917 +0,0 @@
-getServer($server_id);
-
- $sattr = $server->getSchemaAttribute($name);
- if ($sattr) {
- $this->name = $sattr->getName(false);
- $this->setLDAPdetails($sattr);
-
- } else
- $this->name = $name;
-
- $this->source = $source;
-
- # XML attributes are shown by default
- switch ($source) {
- case 'XML': $this->show();
-$this->setXML($values);
-
-break;
-
- default:
-if (! isset($values['values']))
- debug_dump_backtrace('no index "values"',1);
-
-$this->initValue($values['values']);
- }
-
- # Should this attribute be hidden
- if ($server->isAttrHidden($this->name))
- $this->forcehide = true;
-
- # Should this attribute value be read only
- if ($server->isAttrReadOnly($this->name))
- $this->readonly = true;
-
- # Should this attribute value be unique
- if ($server->isAttrUnique($this->name))
- $this->unique = true;
- }
-
- /**
- * Return the name of the attribute.
- *
- * @param boolean $lower - Return the attribute in normal or lower case (default lower)
- * @param boolean $real - Return the real attribute name (with ;binary, or just the name)
- * @return string Attribute name
- */
- public function getName($lower=true,$real=false) {
- if (DEBUG_ENABLED && (($fargs=func_get_args())||$fargs='NOARGS'))
- debug_log('Entered (%%)',5,0,__FILE__,__LINE__,__METHOD__,$fargs,$this->name);
-
- if ($real)
- return $lower ? strtolower($this->name) : $this->name;
- else
- return $lower ? strtolower($this->real_attr_name()) : $this->real_attr_name();
- }
-
- public function getValues() {
- if (DEBUG_ENABLED && (($fargs=func_get_args())||$fargs='NOARGS'))
- debug_log('Entered (%%)',5,1,__FILE__,__LINE__,__METHOD__,$fargs,$this->values);
-
- return $this->values;
- }
-
- public function getOldValues() {
- if (DEBUG_ENABLED && (($fargs=func_get_args())||$fargs='NOARGS'))
- debug_log('Entered (%%)',5,1,__FILE__,__LINE__,__METHOD__,$fargs,$this->oldvalues);
-
- return $this->oldvalues;
- }
-
- public function getValueCount() {
- if (DEBUG_ENABLED && (($fargs=func_get_args())||$fargs='NOARGS'))
- debug_log('Entered (%%)',5,0,__FILE__,__LINE__,__METHOD__,$fargs,$this->values);
-
- return count($this->values);
- }
-
- public function getSource() {
- if (DEBUG_ENABLED && (($fargs=func_get_args())||$fargs='NOARGS'))
- debug_log('Entered (%%)',5,1,__FILE__,__LINE__,__METHOD__,$fargs,$this->source);
-
- return $this->source;
- }
-
- /**
- * Autovalue is called after the attribute is initialised, and thus the values from the ldap server will be set.
- */
- public function autoValue($new_val) {
- if (DEBUG_ENABLED && (($fargs=func_get_args())||$fargs='NOARGS'))
- debug_log('Entered (%%)',5,0,__FILE__,__LINE__,__METHOD__,$fargs);
-
- if ($this->values)
- return;
-
- $this->values = $new_val;
- }
-
- public function initValue($new_val) {
- if (DEBUG_ENABLED && (($fargs=func_ge
Bug#1033117: fsarchiver tests fail with e2fsprogs >= 1.47
Package: fsarchiver
Version: 0.8.6-2
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lunar ubuntu-patch
Dear Maintainer,
Tests for fsarchiver are failing with the new version of e2fsprogs
(1.47), which is causing it to be unable to migrate in Ubuntu. There is
an upstream commit to fix compatibility with newer e2fsprogs, so this
patch will be able to be dropped when that upstream fix is eventually
released.
In Ubuntu, the attached patch was applied to achieve the following:
* Fix compatibility with new e2fsprogs
Thanks for considering the patch.
-- System Information:
Debian Release: bookworm/sid
APT prefers lunar
APT policy: (500, 'lunar')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-16-generic (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru
fsarchiver-0.8.6/debian/patches/0001-fix-e2fsprogs-compatibility.patch
fsarchiver-0.8.6/debian/patches/0001-fix-e2fsprogs-compatibility.patch
--- fsarchiver-0.8.6/debian/patches/0001-fix-e2fsprogs-compatibility.patch
1969-12-31 19:00:00.0 -0500
+++ fsarchiver-0.8.6/debian/patches/0001-fix-e2fsprogs-compatibility.patch
2023-03-16 13:41:03.0 -0400
@@ -0,0 +1,70 @@
+Description: Add EXT4 orphan_file feature
+ Since kernel 5.15 and e2fsprogs 1.47.0 there is a new feature in
+ EXT4 for orphan_file. fasrchiver needed an update to pass compatibility
+ checks for this feature
+Origin: upstream,
https://github.com/fdupoux/fsarchiver/commit/478fa089521b76064d006dd7241dd0b1dc28d0d8
+Applied-Upstream:
https://github.com/fdupoux/fsarchiver/commit/478fa089521b76064d006dd7241dd0b1dc28d0d8
+Last-Update: 2023-03-17
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+Index: fsarchiver-0.8.6/src/fs_ext2.c
+===
+--- fsarchiver-0.8.6.orig/src/fs_ext2.c
fsarchiver-0.8.6/src/fs_ext2.c
+@@ -59,7 +59,7 @@
+ // us and therefore is not preserved (i.e. present in
FSA_FEATURE_INCOMPAT_SUPP but not listed
+ // below). Users can easily enable it with tune2fs if desired.
+ //
+-struct s_features mkfeatures[] = // cf e2fsprogs-1.46.0/lib/e2p/feature.c
++struct s_features mkfeatures[] = // cf e2fsprogs-1.47.0/lib/e2p/feature.c
+ {
+ {"has_journal", FSA_EXT3_FEATURE_COMPAT_HAS_JOURNAL,
E2P_FEATURE_COMPAT, EXTFSTYPE_EXT3, PROGVER(1,39,0)},
+ {"ext_attr", FSA_EXT2_FEATURE_COMPAT_EXT_ATTR,
E2P_FEATURE_COMPAT, EXTFSTYPE_EXT2, PROGVER(1,40,5)},
+@@ -67,6 +67,7 @@
+ {"dir_index", FSA_EXT2_FEATURE_COMPAT_DIR_INDEX,
E2P_FEATURE_COMPAT, EXTFSTYPE_EXT2, PROGVER(1,33,0)},
+ {"sparse_super2", FSA_EXT4_FEATURE_COMPAT_SPARSE_SUPER2,
E2P_FEATURE_COMPAT, EXTFSTYPE_EXT4, PROGVER(1,42,10)},
+ {"fast_commit", FSA_EXT4_FEATURE_COMPAT_FAST_COMMIT,
E2P_FEATURE_COMPAT, EXTFSTYPE_EXT4, PROGVER(1,46,0)},
++{"orphan_file", FSA_EXT4_FEATURE_COMPAT_ORPHAN_FILE,
E2P_FEATURE_COMPAT, EXTFSTYPE_EXT4, PROGVER(1,47,0)},
+ {"filetype", FSA_EXT2_FEATURE_INCOMPAT_FILETYPE,
E2P_FEATURE_INCOMPAT,EXTFSTYPE_EXT2, PROGVER(1,16,0)},
+ {"extent",FSA_EXT4_FEATURE_INCOMPAT_EXTENTS,
E2P_FEATURE_INCOMPAT,EXTFSTYPE_EXT4, PROGVER(1,41,0)},
+ {"journal_dev", FSA_EXT3_FEATURE_INCOMPAT_JOURNAL_DEV,
E2P_FEATURE_INCOMPAT,EXTFSTYPE_EXT3, PROGVER(1,39,0)},
+Index: fsarchiver-0.8.6/src/fs_ext2.h
+===
+--- fsarchiver-0.8.6.orig/src/fs_ext2.h
fsarchiver-0.8.6/src/fs_ext2.h
+@@ -49,6 +49,7 @@
+ #define FSA_EXT4_FEATURE_COMPAT_SPARSE_SUPER2 0x0200
+ #define FSA_EXT4_FEATURE_COMPAT_FAST_COMMIT0x0400
+ #define FSA_EXT4_FEATURE_COMPAT_STABLE_INODES 0x0800
++#define FSA_EXT4_FEATURE_COMPAT_ORPHAN_FILE0x1000
+
+ /* for s_feature_ro_compat */
+ #define FSA_EXT2_FEATURE_RO_COMPAT_SPARSE_SUPER0x0001
+@@ -63,6 +64,7 @@
+ #define FSA_EXT4_FEATURE_RO_COMPAT_METADATA_CSUM 0x0400
+ #define FSA_EXT4_FEATURE_RO_COMPAT_READONLY0x1000
+ #define FSA_EXT4_FEATURE_RO_COMPAT_PROJECT 0x2000
++#define FSA_EXT4_FEATURE_RO_COMPAT_ORPHAN_PRESENT 0x1
+
+ /* for s_feature_incompat */
+ #define FSA_EXT2_FEATURE_INCOMPAT_FILETYPE 0x0002
+@@ -109,7 +111,8 @@
+
FSA_EXT2_FEATURE_COMPAT_DIR_INDEX|\
+
FSA_EXT2_FEATURE_COMPAT_LAZY_BG|\
+
FSA_EXT4_FEATURE_COMPAT_SPARSE_SUPER2|\
+-
Bug#1032936: bliss: New website for bliss and new releases
Package: bliss Version: 0.73-5 Severity: normal X-Debbugs-Cc: will...@ewpettersson.se Dear Maintainer, Bliss has a new website, and a few new releases. The new website is https://users.aalto.fi/~tjunttil/bliss/ which includes links to version 0.77 of bliss, released 2021-02-18. I realise stable won't accept a new version, but it would be nice to have this in either testing or unstable. For what its worth, version 0.77 compiles just fine on my system (details below) and appears to run fine, so this should be a smooth upgrade. William -- System Information: Debian Release: bookworm/sid APT prefers testing-security APT policy: (1000, 'testing-security'), (900, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages bliss depends on: ii libbliss2 0.73-5 ii libc6 2.36-8 ii libgcc-s1 12.2.0-14 ii libgmp102:6.2.1+dfsg1-1.1 ii libstdc++6 12.2.0-14 bliss recommends no packages. bliss suggests no packages. -- no debconf information
Bug#1032920: shaarli: QR code button does not work
Package: shaarli Severity: important Version: 0.12.1+dfsg-8 The QR code button does not work. 404 not found for the JS script, see dev console. Because in "element.src = basePath + "/plugins/qrcode/qr-1.1.3.min.js";" in shaarli-qrcode.js does not exist. But /usr/share/shaarli/plugins/qrcode/qr-1.1.3.js does. So maybe patch the source file to use the non .min.js file. Else build the .min.js file.
Bug#1029948: (no subject)
I tried to replicate it and could not reproduce the bug, I can add link and delete it. Same for tags
Bug#1032919: shaarli: default install does not enable required apache2 mod rewrite
Package: shaarli Severity: important I installed a fresh shaarli and did browse the /shaarli URL and got an error 500. [Tue Mar 14 03:09:22.981534 2023] [core:alert] [pid 21889] [client xx.xx.xx.xx:42960] /usr/share/shaarli/.htaccess: Invalid command 'RewriteEngine', perhaps misspelled or defined by a module not included in the server configuration I had to run: sudo a2enmod rewrite and restart apache2 to get a normal HTML web page.
Bug#884648: mate-panel occasionally crashes with segfault
Package: mate-panel Version: 1.27.0-1 Followup-For: Bug #884648 Dear Maintainer, Mate-Panel Randomly crashes while changing mate themes and some time it crashes and does not reappear at all until leaving the desktop environment unusable and sometimes alt-F2 key shortcut also does not work after mate-panel crashes -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (1000, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-5-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mate-panel depends on: ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4 ii libatk1.0-0 2.46.0-5 ii libc6 2.36-8 ii libcairo2 1.16.0-7 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libglib2.0-0 2.74.5-1 ii libgtk-3-0 3.24.36-4 ii libgtk-layer-shell0 0.8.0-1 ii libice6 2:1.0.10-1 ii libmate-desktop-2-17 1.26.0-1 ii libmate-menu2 1.26.0-3 ii libmate-panel-applet-4-1 1.27.0-1 ii libmateweather1 1.26.0-1.1 ii libpango-1.0-0 1.50.12+ds-1 ii librda0 0.0.5-1.1 ii libsm6 2:1.2.3-1 ii libwayland-client0 1.21.0-1 ii libwnck-3-0 43.0-3 ii libx11-6 2:1.8.3-3 ii libxrandr2 2:1.5.2-2+b1 ii mate-desktop 1.26.0-1 ii mate-menus 1.26.0-3 ii mate-panel-common 1.27.0-1 ii mate-polkit 1.26.1-1 mate-panel recommends no packages. mate-panel suggests no packages. -- no debconf information
Bug#1009670: installation working on rockpro64
Installation completed on the RockPro64 and all is well. I installed both with sd card and eMMC (with usb adapter for flashing). I used the Debian 12 Bookworm link and followed the instructions for Linux at https://wiki.pine64.org/wiki/ROCKPro64_Software_Releases#Debian . William
Bug#1031114: fwd
Hi, > I'm not sure if I should backport the patch to debian's 110 or not. It depends on if the version will stay for a long time (a Debian version for example) or not. I released the fix so either way it should be okay. for some reason the user dir option was not needed on CIs. maybe it was on my workstation at this time. You could provide backports for this package too, is there a reason you do not provide backports?
Bug#1031114: fwd
Control: tags -1 + pending Control: forwarded -1 https://salsa.debian.org/js-team/jquery-timepicker/-/commit/21f37b5345ccd800507ca3293d12de70ccee5437 It seems like this selenium issue was right: https://github.com/SeleniumHQ/selenium/issues/11634 I removed the user-data-dir option. On GitLab Salsa I had re-run a job and reproduced the failure: https://salsa.debian.org/js-team/jquery-timepicker/-/jobs/3937872#L495 Now it's fixed: https://salsa.debian.org/js-team/jquery-timepicker/-/jobs/3937932#L451
Bug#1031114: jquery-timepicker: autopkgtest failures
I think this has nothing to do with my package :)
selenium.common.exceptions.WebDriverException: Message: unknown error:
unable to discover open pages
And this should be enough to reproduce it (deps: python3-selenium,
chromium-driver):
from selenium import webdriver
from selenium.webdriver.support.wait import WebDriverWait
from selenium.webdriver.common.by import By
import os
data_dir = os.getenv('AUTOPKGTEST_TMP', default='/tmp') +
'/google-chrome'
options = webdriver.ChromeOptions()
options.add_argument('--headless')
options.add_argument('--no-sandbox')
options.add_argument('--headless')
options.add_argument('--disable-gpu')
options.add_argument('--disable-dev-shm-usage')
options.add_argument('--profile-directory=Default')
options.add_argument('--user-data-dir=' + data_dir)
driver = webdriver.Chrome(options=options)
print("Running tests")
driver.get("http://localhost:/SpecRunner.html?random=false;)
Let me know if you can reproduce this WebDriverException
Bug#1031067: RM: mrtg-rrd -- RoQA; no upload since 2015, up upstream update since 2003
Package: ftp.debian.org Severity: normal Usertags: rm-request User: ftp.debian@packages.debian.org Usertags: remove Hi, Please proceed to deleting the package: mrtg-rrd It's only in unstable. And #799097 discussion seems to say it was not unusable and go removed from stretch. Last upstream release was Aug 18, 2003. Nobody seems to care about this package/tool, I found a fork last updated in 2015: https://github.com/makkintosshu/mrtg-rrd Informations: - Last upload: 2015-08-01, 8 years ago. - Last activity of the maintainer on Debian: 2013-08-17 -- William Desportes
Bug#1031065: RM: php-cache-lite -- RoQA; Abandoned upstream
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: Debian PHP PEAR Maintainers Same request as #1014698 but please remove php-cache-lite from experimental too. -- William Desportes
Bug#1031010: icingaweb2: uses an inline version of php-dompdf in the binary
Package: icingaweb2 Version: 2.3.4-1 Severity: wishlist X-Debbugs-CC: sebas...@debian.org X-Debbugs-CC: taf...@debian.org Hi, I updated php-dompdf (php-dompdf/2.0.3+dfsg-1) and you now can depend on it and provide a link + maintscript (dir_to_symlink). https://salsa.debian.org/nagios-team/icingaweb2/-/tree/debian/2.11.4-2/library/vendor/dompdf/vendor/dompdf/dompdf It's present since the early days: https://salsa.debian.org/nagios-team/icingaweb2/-/tree/debian/2.3.4-1/library/vendor/dompdf -- William Desportes
Bug#1031009: icingaweb2: uses an inline version of php-dompdf-svg-lib in the binary
Package: icingaweb2 Version: 2.5.3-1 Severity: wishlist X-Debbugs-CC: sebas...@debian.org X-Debbugs-CC: taf...@debian.org Hi, I created a new package: php-dompdf-svg-lib (php-dompdf-svg-lib/0.5.0-3) and you now can depend on it and provide a link + maintscript (dir_to_symlink). https://salsa.debian.org/nagios-team/icingaweb2/-/tree/debian/2.11.4-2/library/vendor/dompdf/vendor/phenx/php-svg-lib It's present since a while: https://salsa.debian.org/nagios-team/icingaweb2/-/tree/debian/2.5.3-1/library/vendor/dompdf/lib/php-svg-lib/src -- William Desportes
Bug#1029578: New security
using git bisect and icmake unit tests I found out that https://github.com/kward/shunit2/commit/f08632b331612f554e97c598508e4aac3dfa39a2#diff-a453761d888ea6645a651da189e89605523e4eab9500ee9e5988e55bca4f437bR892-R896 is the first bad commit. it's a new security that was added, so the affected packages must adapt. ref: https://github.com/kward/shunit2/issues/84 now shunit2 does not like that any command exits -gt 0 in a test. so the fix is: - assertTrue commandExits1 + assertTrue "$(commandExit1; echo $?)"
Bug#1030918: RM: googleearth-package -- RoM; uninstallable, no upload since 2014
Package: ftp.debian.org Severity: normal Usertags: rm-request User: ftp.debian@packages.debian.org Usertags: remove Hi, Please proceed to deleting the package: googleearth-package This one is RoM because I emailed the author and the reply is: > [...] Yes, please feel free to remove googleearth-package and feel free to remove me from lxcfs. > As I don't have time to maintain these packages anymore and consider myself "ex-maintainer" for some time now. Informations: - Last activity of the maintainer on Debian: 2016-04-03 - Last upload: 2014-10-04, 9 years ago. -- William Desportes
Bug#1030880: RM: sa-learn-cyrus -- RoQA; outdated, uninstallable, no upload since 2013
Package: ftp.debian.org Severity: normal Usertags: rm-request User: ftp.debian@packages.debian.org Usertags: remove Hi, Please proceed to deleting the package: sa-learn-cyrus It's only in unstable now and is uninstallable. Last upload: 2013-03-06, 10 years ago. Informations: - Last activity of the maintainer on Debian: 2013-05-26 Package bugs: - #[730335][1] (ipurge command path has changed in the latest cyrus-common package) - #[730729][2] (fail for mailboxes with spaces) - #[830596][3] (depends on cyrus-imapd-2.4 which is gone) [edos-uninstallable,piuparts] Found on my QA dashboard. [1]: https://bugs.debian.org/730335 [2]: https://bugs.debian.org/730729 [3]: https://bugs.debian.org/830596 -- William Desportes
Bug#1030878: RM: gcap -- RoQA; outdated, broken, no upload since 2018, no upstream updates
Package: ftp.debian.org Severity: normal Usertags: rm-request User: ftp.debian@packages.debian.org Usertags: remove Hi, Please proceed to deleting the package: gcap I tested it and reported in #1030877 that the package is not usable. Informations: - Last upload: 2018-10-04, 5 years ago. - Maintainer is the QA group. Found on my QA dashboard. -- William Desportes
Bug#1030877: gcap: perl error, package unusable
Package: gcap Version: 0.1.1-2 Severity: grave This package does not work (with an existing or non existing YT video), using manpage examples: On my workstation: $ gcap 0QRO3gKj3qw Checking ...Couldn't parsefile [http://video.google.com/timedtext?hl=en=list=0QRO3gKj3qw] with LWP: no element found at line 1, column 0, byte -1 at /usr/lib/x86_64-linux-gnu/perl5/5.34/XML/Parser.pm line 187. On Debian sid: $ gcap 0QRO3gKj3qw Checking ...Couldn't parsefile [http://video.google.com/timedtext?hl=en=list=0QRO3gKj3qw] with LWP: no element found at line 1, column 0, byte -1 at /usr/lib/x86_64-linux-gnu/perl5/5.36/XML/Parser.pm line 187. $ gcap "http://www.youtube.com/watch?v=0QRO3gKj3qw; Checking ...Couldn't parsefile [http://video.google.com/timedtext?hl=en=list=0QRO3gKj3qw] with LWP: no element found at line 1, column 0, byte -1 at /usr/lib/x86_64-linux-gnu/perl5/5.36/XML/Parser.pm line 187. $ gcap -ti 0QRO3gKj3qw WARNING Umph::Prompt not found, ignoring --interactive option Checking ...Couldn't parsefile [http://video.google.com/timedtext?hl=en=list=0QRO3gKj3qw] with LWP: no element found at line 1, column 0, byte -1 at /usr/lib/x86_64-linux-gnu/perl5/5.36/XML/Parser.pm line 187. $ gcap https://www.youtube.com/watch?v=kkui_qBYvmY Checking ...Couldn't parsefile [http://video.google.com/timedtext?hl=en=list=kkui_qBYvmY] with LWP: no element found at line 1, column 0, byte -1 at /usr/lib/x86_64-linux-gnu/perl5/5.36/XML/Parser.pm line 187. $ gcap kkui_qBYvmY Checking ...Couldn't parsefile [http://video.google.com/timedtext?hl=en=list=kkui_qBYvmY] with LWP: no element found at line 1, column 0, byte -1 at /usr/lib/x86_64-linux-gnu/perl5/5.36/XML/Parser.pm line 187.
Bug#1030230: icingaweb2: uses an inline version of php-font-lib in the binary
Package: icingaweb2 Version: 2.3.4-1 Severity: wishlist X-Debbugs-CC: sebas...@debian.org X-Debbugs-CC: taf...@debian.org Hi, I updated php-font-lib (php-font-lib/0.5.4+dfsg-1) and you now can depend on it and provide a link + maintscript (dir_to_symlink). php-dompdf should be next, but probably not before the freeze. This one can be done before the freeze. https://salsa.debian.org/nagios-team/icingaweb2/-/tree/debian/2.11.4-2/library/vendor/dompdf/vendor/phenx/php-font-lib It's present since the early days: https://salsa.debian.org/nagios-team/icingaweb2/-/tree/debian/2.3.4-1/library/vendor/dompdf/lib/php-font-lib/classes -- William Desportes
Bug#1029578: Forwarded upstream without any reply
Control: forwarded -1 https://salsa.debian.org/debian/shunit2/-/commit/513db89d3e5ad321a050fd40130f4c4674adc172 This is what I had sent as my last reply on this subject: " Hi Paul and Kate, I worked a bit more onto this and found out more details, see: https://github.com/kward/shunit2/issues/164 I also added more tests for autopkgtests [1] to cover this bug. So let's see how upstream reacts (Kate as a CC here). The output is like in failing packages: https://salsa.debian.org/debian/shunit2/-/jobs/3688066#L672 So assertTrue and assertFalse seem to be broken [1] https://salsa.debian.org/debian/shunit2/-/blob/debian/latest/debian/tests/simple-script-tests William " Kate is the upstream author. For now I need some help, I had no reply Here is the new autopkgtest for this bug: https://salsa.debian.org/debian/shunit2/-/commit/513db89d3e5ad321a050fd40130f4c4674adc172 -- William Desportes
Bug#978994: Taking responsibility
Control: owner -1 ! I am taking the responsability of this one, I already refreshed php-font-lib (https://salsa.debian.org/php-team/pear/php-font-lib) and it got uploaded today. The salsa repository is at: https://salsa.debian.org/php-team/pear/php-dompdf
Bug#1028227: Should we FTP RM libi8x?
Hi, I would say that at first doko was not reachable, now doko has probably a lot to do. I had mailed the MIA team to see what could be done. Now it's up to doko -- William Desportes
Bug#1029797: phpsysinfo: [INTL:pt] Portuguese translation - debconf messages
Control: forwarded -1 https://salsa.debian.org/php-team/pear/phpsysinfo/-/commit/db9f91e1accf36a130aae2bc9c03fc6946579873 Control: tags -1 + pending Hi, Thank you for translating into European Portuguese ! I pushed your work as https://salsa.debian.org/php-team/pear/phpsysinfo/-/commit/db9f91e1accf36a130aae2bc9c03fc6946579873 -- William Desportes
Bug#1029766: software-properties-common: AttributeError: 'NoneType' object has no attribute 'people' on "add-apt-repository ppa:mozillateam/ppa"
Package: software-properties-common Version: 0.99.30-4 Severity: important Using a fresh Debian 12 installer. I tried to run: sudo add-apt-repository ppa:mozillateam/ppa And got: Traceback (most recent call last): File "/usr/bin/add-apt-repository", line 362, in sys.exit(0 if addaptrepo.main() else 1) File "/usr/bin/add-apt-repository", line 345, in main shortcut = handler(source, **shortcut_params) File "/usr/lib/python3/dist-packages/softwareproperties/shortcuts.py", line 40, in shortcut_handler return handler(shortcut, **kwargs) File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 86, in __init__ if self.lpppa.publish_debug_symbols: File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 126, in lpppa self._lpppa = self.lpteam.getPPAByName(name=self.ppaname) File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 113, in lpteam self._lpteam = self.lp.people(self.teamname) AttributeError: 'NoneType' object has no attribute 'people' As said on Internet: https://www.linuxquestions.org/questions/debian-26/debian-bullseye-sid-add-apt-repository-not-working-python-problem-4175720821/#post6403993 Installing python3-launchpadlib solves this bug and you can re-run the command. -- William Desportes
Bug#1027867: (no subject)
Control: notfound 1027867 mesa/22.2.4-1 As said on https://gitlab.freedesktop.org/mesa/mesa/-/issues/8007#note_1727512 Just tried 22.3.3-1 with the same backtrace & error logs. I rolled back to 22.2.4-1 I also rolled back to 22.2.4-1 (just the package libgl1-mesa-dri) and it works. diff: -libgl1-mesa-dri/testing,now 22.3.3-1 amd64 [installed,automatic] +libgl1-mesa-dri/now 22.2.4-1 amd64 [installed,upgradable to: 22.3.3-1]
Bug#1027867: segfault
Control: severity -1 important Hi, I have the same segfault with a fresh install of Debian 12 installer. Only checked XFCE and desktop env. No non-free drivers installed. It segfaults Xorg. I attached the Xorg log and the installed packages list. On a Lenovo Thinkpad P73. Here is the backtrace: [ 23.616] (EE) Backtrace: [ 23.616] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55d2d611fcc9] [ 23.617] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x40) [0x7f620145af90] [ 23.617] (EE) 2: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x4406c) [0x7f61ff75999c] [ 23.617] (EE) 3: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x1e4c9) [0x7f61ff733df9] [ 23.617] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x266) [0x7f61ff715b96] [ 23.617] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 23.617] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7f61feeaaf56] [ 23.617] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_d3d12+0x60b284) [0x7f61ff4b67a4] [ 23.618] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_d3d12+0x1a93) [0x7f61feeacfb3] [ 23.618] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_d3d12+0xa175) [0x7f61feeb5695] [ 23.618] (EE) 9: /lib/x86_64-linux-gnu/libgbm.so.1 (gbm_format_get_name+0xf2e) [0x7f6200ac7eae] [ 23.618] (EE) 10: /lib/x86_64-linux-gnu/libgbm.so.1 (gbm_format_get_name+0x16f8) [0x7f6200ac8678] [ 23.618] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 23.618] (EE) 11: /lib/x86_64-linux-gnu/libgbm.so.1 (?+0x0) [0x7f6200ac674c] [ 23.619] (EE) 12: /lib/x86_64-linux-gnu/libgbm.so.1 (gbm_create_device+0x44) [0x7f6200ac6884] [ 23.619] (EE) 13: /usr/lib/xorg/modules/libglamoregl.so (glamor_egl_init+0x61) [0x7f6200aec3c1] [ 23.619] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 23.619] (EE) 14: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f6200b2c733] [ 23.619] (EE) 15: /usr/lib/xorg/Xorg (InitOutput+0xa2a) [0x55d2d5fef57a] [ 23.619] (EE) 16: /usr/lib/xorg/Xorg (InitFonts+0x1ce) [0x55d2d5fb04de] [ 23.620] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x8a) [0x7f620144618a] [ 23.620] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x85) [0x7f6201446245] [ 23.620] (EE) 19: /usr/lib/xorg/Xorg (_start+0x21) [0x55d2d5f99b71] -- William Desportes [23.458] X.Org X Server 1.21.1.6 X Protocol Version 11, Revision 0 [23.458] Current Operating System: Linux williamdes 6.1.0-1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.4-1 (2023-01-07) x86_64 [23.458] Kernel command line: BOOT_IMAGE=/vmlinuz-6.1.0-1-amd64 root=UUID=6bb89b1d-4b43-4a90-b4ce-797c56ee68ad ro quiet [23.458] xorg-server 2:21.1.6-1 (https://www.debian.org/support) [23.458] Current version of pixman: 0.42.2 [23.458] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [23.458] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [23.458] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Jan 26 17:49:37 2023 [23.459] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [23.459] (==) No Layout section. Using the first Screen section. [23.459] (==) No screen section available. Using defaults. [23.459] (**) |-->Screen "Default Screen Section" (0) [23.459] (**) | |-->Monitor "" [23.459] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [23.459] (==) Automatically adding devices [23.459] (==) Automatically enabling devices [23.459] (==) Automatically adding GPU devices [23.459] (==) Automatically binding GPU devices [23.459] (==) Max clients allowed: 256, resource mask: 0x1f [23.459] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [23.459] Entry deleted from font path. [23.459] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [23.459] (==) ModulePath set to "/usr/lib/xorg/modules" [23.459] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [23.459] (II) Loader magic: 0x55d2d61abf00 [23.459] (II) Module ABI versions: [23.459] X.Org ANSI C Emulation: 0.4 [23.459] X.Org Video Driver: 25.2 [23.459] X.Org XInput driver : 24.4 [23.459] X.Org Server Extension : 10.0 [23.459]
Bug#1029712: phpsysinfo: [INTL:nl] Dutch translation of debconf messages
Control: forwarded 1029712 https://salsa.debian.org/php-team/pear/phpsysinfo/-/commit/8c9e335c201a880c8ec2d18fd606e0e23d2c06bc Control: tags 1029712 + pending Hi, Thank you for translating into Dutch ! I pushed your work as https://salsa.debian.org/php-team/pear/phpsysinfo/-/commit/8c9e335c201a880c8ec2d18fd606e0e23d2c06bc -- William Desportes
Bug#1029666: [INTL:es] Spanish translation of the debconf template
Control: forwarded 1029666 https://salsa.debian.org/php-team/pear/phpsysinfo/-/commit/bea5192cd4f6564ca5af5100b828a6507a5a42bf Control: tags 1029666 + pending Hi, Thank you for translating into Spanish ! I pushed your work as https://salsa.debian.org/php-team/pear/phpsysinfo/-/commit/bea5192cd4f6564ca5af5100b828a6507a5a42bf -- William Desportes
Bug#1029630: qemu-system-common: libvirt migration fails from QEMU 1:7.1+dfsg-2~bpo11+3 instance to current on virtio-rng
Package: qemu-system-common Version: 1:7.2+dfsg-1~bpo11+2 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Upgrade to current QEMU package from previous bpo on bullseye-backports. Live migrate virtuals from old to another identical system running same version of bullseye-backports qemu software. Upgrade the packages to on current system to 7.2. Attempt to live migrate the previous virtuals back. Starts to copy, but fails at the end and aborts transfer. * What exactly did you do (or not do) that was effective (or ineffective)? Migrating virtuals between two instances of the new 7.2 version works ok. Just fails going from old to new. * What was the outcome of this action? Unable to easily upgrade without shutting down virtuals and restarting. [2023-01-25 15:54:46.445997 +] I [io-stats.c:3706:ios_sample_buf_size_configure] 0-vm: Configure ios_sample_buf size is 1024 because ios_sample_interval is 0 2023-01-25T15:54:55.600614Z qemu-system-x86_64: get_pci_config_device: Bad config data: i=0x34 read: c8 device: dc cmask: ff wmask: 0 w1cmask:0 2023-01-25T15:54:55.600687Z qemu-system-x86_64: Failed to load PCIDevice:config 2023-01-25T15:54:55.600694Z qemu-system-x86_64: Failed to load virtio-rng:virtio 2023-01-25T15:54:55.600700Z qemu-system-x86_64: error while loading state for instance 0x0 of device ':00:03.0:00.0/virtio-rng' 2023-01-25T15:54:55.607062Z qemu-system-x86_64: load of migration failed: Invalid argument 2023-01-25 15:54:56.011+: shutting down, reason=crashed * What outcome did you expect instead? Seamless update. *** End of the template - remove these template lines *** -- System Information: Debian Release: 11.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-0.deb11.6-amd64 (SMP w/24 CPU threads; PREEMPT) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages qemu-system-common depends on: ii libaio1 0.3.112-9 ii libasound2 1.2.4-1.1 ii libbrlapi0.86.3+dfsg-1+deb11u1 ii libc6 2.31-13+deb11u5 ii libcacard0 1:2.8.0-3 ii libcap-ng0 0.7.9-2.2+b1 ii libepoxy0 1.5.5-1 ii libfuse3-3 3.10.3-2 ii libgbm1 20.3.5-1 ii libglib2.0-02.66.8-1 ii libgmp102:6.2.1+dfsg-1+deb11u1 ii libgnutls30 3.7.1-5+deb11u2 ii libhogweed6 3.7.3-1 ii libncursesw66.2+20201114-2 ii libnettle8 3.7.3-1 ii libnuma12.0.12-1+b1 ii libpixman-1-0 0.40.0-1.1~deb11u1 ii libseccomp2 2.5.1-1+deb11u1 ii libspice-server10.14.3-2.1 ii libtinfo6 6.2+20201114-2 ii liburing1 0.7-3 ii libusb-1.0-02:1.0.24-3 ii libusbredirparser1 0.8.0-1+b1 ii libzstd11.4.8+dfsg-2.1 ii zlib1g 1:1.2.11.dfsg-2+deb11u2 qemu-system-common recommends no packages. qemu-system-common suggests no packages. -- no debconf information
Bug#1029551: phpsysinfo: [INTL:pt_BR] Brazilian Portuguese debconf templates translation
Hi, Thank you for translating into Brazilian Portuguese ! I committed the change as https://salsa.debian.org/php-team/pear/phpsysinfo/-/commit/d777cc566f3498fccebcb3ce993c4532168d413d -- William Desportes Le 2023/01/24 15:12, Adriano Rafael Gomes a écrit : Package: phpsysinfo Tags: l10n patch Severity: wishlist Hello, Could you please update the Brazilian Portuguese translation? Attached you will find the file pt_BR.po. It is UTF-8 encoded and tested with msgfmt and podebconf-display-po. Kind regards.
Bug#1029597: related
Control: severity 252521 serious This one describes the same error than using the login page. https://bugs.debian.org/252521
