Bug#1065702: krb5-kdc: uninstallable due to hard-coded dependency on libverto-libev1 | libverto-libevent1,
Package: krb5-kdc Version: 1.20.1-5.1 Severity: serious User: debian-...@lists.debian.org Usertag: time-t Hi Sam, I've run into a problem with openldap not being bootstrappable for the time_t transition because it build-depends on krb5-kdc, and krb5-kdc is uninstallable on arm* because of a hard-coded dependency on libverto-libev1 | libverto-libevent1. Both of these library packages have changed names so are now libverto-libev1t64 and libverto-libevent1t64. I don't know why these need to be hard-coded, but if they do they need to be updated, because they conflict with the shlibdeps-generated dependency on libverto1t64. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Bug#1065634: marked as done (wv: /usr/share/doc wv is a dangling symlink)
Your message dated Sat, 09 Mar 2024 07:04:43 + with message-id and subject line Bug#1065634: fixed in wv 1.2.9-7 has caused the Debian Bug report #1065634, regarding wv: /usr/share/doc wv is a dangling symlink to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1065634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wv Version: 1.2.9-6.1 Severity: serious X-Debbugs-Cc: Sven Joachim , Steve Langasek After renaming the libwv-1.2-4 library package to libwv-1.2-4t64, the /usr/share/doc/wv symlink has become dangling. , | $ file /usr/share/doc/wv | /usr/share/doc/wv: broken symbolic link to libwv-1.2-4 ` It should point to libwv-1.2-4t64 instead, obviously. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.81-nouveau (SMP w/2 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 wv depends on: ii libc62.37-15.1 ii libglib2.0-0t64 2.78.4-3 ii libgsf-1-114 1.14.51-2 ii libwv-1.2-4t64 1.2.9-6.1 wv recommends no packages. Versions of packages wv suggests: ii elinks 0.16.1.1-4.1+b2 ii ghostscript [postscript-viewer] 10.02.1~dfsg-3 ii imagemagick 8:6.9.12.98+dfsg1-5.1+b1 ii imagemagick-6.q16 [imagemagick] 8:6.9.12.98+dfsg1-5.1+b1 ii lynx 2.9.0rel.0-2 ii okular [postscript-viewer] 4:23.08.1-2 ii texlive 2023.20240207-1 -- no debconf information --- End Message --- --- Begin Message --- Source: wv Source-Version: 1.2.9-7 Done: Steve Langasek We believe that the bug you reported is fixed in the latest version of wv, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve Langasek (supplier of updated wv package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 09 Mar 2024 06:50:23 + Source: wv Architecture: source Version: 1.2.9-7 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Steve Langasek Closes: 1065634 Changes: wv (1.2.9-7) unstable; urgency=medium . [ Sven Joachim ] * QA upload. * Fix dangling /usr/share/doc symlinks (Closes: #1065634). Checksums-Sha1: f607fea806da9ec3b7b388a8a7531034be870d2a 1987 wv_1.2.9-7.dsc 99d393a1facc57021e3f1b3bac689601c9cbe3d3 13508 wv_1.2.9-7.debian.tar.xz 36a0068ed8ee5d9bacb46144a3c0ed413fc2b936 5932 wv_1.2.9-7_source.buildinfo Checksums-Sha256: ffbfd72adc2105dd3f0871d85a656a51458e49bbfd2bfabd8ea2458ea30343b0 1987 wv_1.2.9-7.dsc a314942da026298af9e33709fffaecd6b92c205de9a6ae824db243087dca650c 13508 wv_1.2.9-7.debian.tar.xz 865b17487ebb969a7003179448659d33933dba8ac68c7e62919a7e08c8f54881 5932 wv_1.2.9-7_source.buildinfo Files: 2fc6b08a886af292768fc5bb1881db68 1987 text optional wv_1.2.9-7.dsc 9f5c130bdcbee4207eedfb5d12e88c3e 13508 text optional wv_1.2.9-7.debian.tar.xz 1dbcab72af3b5406b17835a3c6e8fb41 5932 text optional wv_1.2.9-7_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEErEg/aN5yj0PyIC/KVo0w8yGyEz0FAmXsBsASHHZvcmxvbkBk ZWJpYW4ub3JnAAoJEFaNMPMhshM9JmsP/1Gg3FgTA06NoPvv0KvHVtGMMMY22rT1 o+iSbZmB2L/OedMZXzHSm6+cLREGGDEyDB8ZXE16ZS858aKtfnBQxIxlJ2cgQlkL bhU/vfhe3+iqTGkyycLfCTshLrWJAOYdkd2AztbVWqEwYegInXxbhmXkJQvW5cZP 4MsvUoyCzYKsWBjlxVwkNAN9HdLQZCp92j7XLA5Aq/GwDVlIYc1DeBC2dzMhw778 fnh3pu2Yssxv88O2dCFp4WwfSLNK/l5ZTOvJZKCP61o5LOv75hg2Cvabw9y+3851 Dbd4YSeruBmf9OJUxCWP0lBD1pahnoG6Llhna6bFmUM3Z2wP2ddqcTw6JJ4FRBsD 5wNBtuDeE+cU6ad0MgotsRAzPPyj5OuHOIf5vsMpUE8Rnj/OCwjiuS7MDufDqClG 2j9xGC8UdDMKXYLEbfYeNNOyulvLybnLFrZa/VDuYnuaj2DzVM7o8WA210kfRq0T So0O6MIc5FxA93WrdcxH8aWx2ur9nfIVjscgBxb/vbdc5+fpoTo1bpY3rEV7kiDf UTFdQgIfv0/jphGgzH7Nxrfi0pzmTpSEO40RLlw9mw+GM/xnqUFwUcamavkt9X12 jiNtFk4C1zrVpdeV8GV9n7NQoM9W1OxqPG46DLi9xJJLoLrShrMH3hzWMF0sgiS/
Bug#1065634: wv: /usr/share/doc wv is a dangling symlink
On Thu, Mar 07, 2024 at 08:00:34PM +0100, Sven Joachim wrote: > On 2024-03-07 18:49 +0100, Sven Joachim wrote: > > > Package: wv > > Version: 1.2.9-6.1 > > Severity: serious > > X-Debbugs-Cc: Sven Joachim , Steve Langasek > > > > > > After renaming the libwv-1.2-4 library package to libwv-1.2-4t64, the > > /usr/share/doc/wv symlink has become dangling. > > > > , > > | $ file /usr/share/doc/wv > > | /usr/share/doc/wv: broken symbolic link to libwv-1.2-4 > > ` > > > > It should point to libwv-1.2-4t64 instead, obviously. > > There is a similar broken symlink in the libwv-dev package (which > I do not have installed). The attached patch takes care of them. > Steve, would you like to upload that? Note that the package is > orphaned, therefore I have created a debian/changelog entry for a QA > upload rather than for another NMU. Thanks, uploaded. > diff -Nru wv-1.2.9/debian/changelog wv-1.2.9/debian/changelog > --- wv-1.2.9/debian/changelog 2024-02-29 06:47:50.0 +0100 > +++ wv-1.2.9/debian/changelog 2024-03-07 19:42:29.0 +0100 > @@ -1,3 +1,10 @@ > +wv (1.2.9-7) unstable; urgency=medium > + > + * QA upload. > + * Fix dangling /usr/share/doc symlinks (Closes: #1065634). > + > + -- Sven Joachim Thu, 07 Mar 2024 19:42:29 +0100 > + > wv (1.2.9-6.1) unstable; urgency=medium > >* Non-maintainer upload. > diff -Nru wv-1.2.9/debian/libwv-dev.links wv-1.2.9/debian/libwv-dev.links > --- wv-1.2.9/debian/libwv-dev.links 2023-09-17 23:45:41.0 +0200 > +++ wv-1.2.9/debian/libwv-dev.links 2024-03-07 19:41:38.0 +0100 > @@ -1 +1 @@ > -usr/share/doc/libwv-1.2-4 usr/share/doc/libwv-dev > +usr/share/doc/libwv-1.2-4t64 usr/share/doc/libwv-dev > diff -Nru wv-1.2.9/debian/wv.links wv-1.2.9/debian/wv.links > --- wv-1.2.9/debian/wv.links 2023-09-17 23:45:41.0 +0200 > +++ wv-1.2.9/debian/wv.links 2024-03-07 19:01:19.0 +0100 > @@ -1 +1 @@ > -usr/share/doc/libwv-1.2-4 usr/share/doc/wv > +usr/share/doc/libwv-1.2-4t64 usr/share/doc/wv -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Bug#1065633: marked as done (openldap: FTBFS on hppa - implicit declaration of function ‘kadm5_s_init_with_password_ctx’)
Your message dated Sat, 09 Mar 2024 06:49:25 + with message-id and subject line Bug#1065633: fixed in openldap 2.5.16+dfsg-1 has caused the Debian Bug report #1065633, regarding openldap: FTBFS on hppa - implicit declaration of function ‘kadm5_s_init_with_password_ctx’ to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1065633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openldap Version: 2.5.13+dfsg-5+b4 Severity: normal Tags: ftbfs Dear Maintainer, See: https://buildd.debian.org/status/fetch.php?pkg=openldap=hppa=2.5.13%2Bdfsg-5%2Bb4=1709830559=0 smbk5pwd.c: In function ‘smbk5pwd_modules_init’: smbk5pwd.c:917:23: error: implicit declaration of function ‘kadm5_s_init_with_password_ctx’; did you mean ‘kadm5_init_with_password_ctx’? [-Werror=implicit-function-declaration] 917 | ret = kadm5_s_init_with_password_ctx( context, | ^~ | kadm5_init_with_password_ctx smbk5pwd.c:924:25: warning: ‘krb5_get_error_string’ is deprecated [-Wdeprecated-declarations] 924 | err_str = krb5_get_error_string( context ); | ^~~ In file included from /usr/include/heimdal/krb5.h:967, from smbk5pwd.c:45: /usr/include/heimdal/krb5-protos.h:4188:1: note: declared here 4188 | krb5_get_error_string (krb5_context /*context*/) | ^ smbk5pwd.c:926:33: warning: ‘krb5_get_err_text’ is deprecated [-Wdeprecated-declarations] 926 | err_msg = (char *)krb5_get_err_text( context, ret ); | ^~~ /usr/include/heimdal/krb5-protos.h:4152:1: note: declared here 4152 | krb5_get_err_text ( | ^ smbk5pwd.c:931:33: warning: ‘krb5_free_error_string’ is deprecated [-Wdeprecated-declarations] 931 | krb5_free_error_string( context, err_str ); | ^~ /usr/include/heimdal/krb5-protos.h:3721:1: note: declared here 3721 | krb5_free_error_string ( | ^~ cc1: some warnings being treated as errors make[2]: *** [Makefile:54: smbk5pwd.lo] Error 1 Regards, Dave Anglin -- System Information: Debian Release: trixie/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable') Architecture: hppa (parisc64) Kernel: Linux 6.1.80+ (SMP w/4 CPU threads) 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) --- End Message --- --- Begin Message --- Source: openldap Source-Version: 2.5.16+dfsg-1 Done: Ryan Tandy We believe that the bug you reported is fixed in the latest version of openldap, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ryan Tandy (supplier of updated openldap package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 08 Mar 2024 21:46:26 -0800 Source: openldap Architecture: source Version: 2.5.16+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian OpenLDAP Maintainers Changed-By: Ryan Tandy Closes: 1020319 1029758 1032742 1033177 1036995 1039740 1065633 Changes: openldap (2.5.16+dfsg-1) unstable; urgency=medium . [ Ryan Tandy ] * New upstream release. - fixed possible null pointer dereferences if strdup fails (ITS#9904) (Closes: #1036995, CVE-2023-2953) - fixed unaligned accesses in LMDB on sparc64 (ITS#9916) (Closes: #1020319) * Update Turkish debconf translation. (Closes: #1029758) Thanks to Atila KOÇ. * Add Romanian debconf translation. (Closes: #1033177) Thanks to Remus-Gabriel Chelu. * Create an autopkgtest covering basic TLS functionality. Thanks to John Scott. * Drop transitional package slapd-smbk5pwd. (Closes: #1032742) * Drop dbgsym migration for slapd-dbg. * Build and install the ppm
Processed: Re: Fwd: E: unsupported command: poweroff.no-molly-guard
Processing control commands: > forcemerge 1059691 -1 Bug #1059691 [molly-guard] molly-guard: impossible reboot Bug #1059861 [molly-guard] molly-guard: Poweroff doesnt' work anymore Bug #1065696 [molly-guard] E: unsupported command: poweroff.no-molly-guard Severity set to 'important' from 'grave' Added tag(s) patch. Bug #1059861 [molly-guard] molly-guard: Poweroff doesnt' work anymore Merged 1059691 1059861 1065696 -- 1059691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059691 1059861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059861 1065696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1065696: Fwd: E: unsupported command: poweroff.no-molly-guard
Control: forcemerge 1059691 -1 On Fri, Mar 08, 2024 at 09:37:05PM -0800, Francois Marier wrote: > Hi Helmut, > > This looks like an unexpected edge case from the recent usr-merge changes: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065696 > > It sounds like a system using sysvinit, instead of systemd, which was > recently upgraded using usrmerge. Yes, I think this is a duplicate of #1059691. Could you give feedback on the contained patch? Helmut
Bug#1065700: mysql-8.0: ftbfs with 64-bit time_t on 32-bit archs
Package: mysql-8.0
Version: 8.0.36-2
Severity: serious
Tags: patch
Justification: ftbfs
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Dear maintainers,
With the switch to 64-bit time_t on 32-bit archs, mysql-8.0 now fails to
build from source because of a test that *checks* that only 32-bit time is
supported:
[...]
[ 57%] main.func_unixtime_32bitsw4 [ fail ]
Test ended at 2024-03-09 05:01:27
CURRENT_TEST: main.func_unixtime_32bits
--- /<>/mysql-test/r/func_unixtime_32bits.result 2023-12-12
21:09:36.0 +0300
+++ /<>/builddir/mysql-test/var/4/log/func_unixtime_32bits.reject
2024-03-09 08:01:27.450443865 +0300
@@ -12,7 +12,7 @@
2038-01-19 06:14:07
select from_unixtime(2147483648);
from_unixtime(2147483648)
-NULL
+2038-01-19 06:14:08
select from_unixtime(0);
from_unixtime(0)
1970-01-01 03:00:00
@@ -32,26 +32,26 @@
2147483647
select unix_timestamp(from_unixtime(2147483648));
unix_timestamp(from_unixtime(2147483648))
-NULL
+2147483648
[...]
- the logfile can be found in
'/<>/builddir/mysql-test/var/log/main.func_unixtime_32bits/func_unixtime_32bits.log'
Test main.func_unixtime_32bits has failed 2 times, no more retries.
[...]
(https://launchpad.net/ubuntu/+source/mysql-8.0/8.0.36-2/+build/27892969)
Please find attached a patch for this issue which I have uploaded to Ubuntu.
Thanks,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru mysql-8.0-8.0.36/debian/patches/64bit_time_everywhere.patch
mysql-8.0-8.0.36/debian/patches/64bit_time_everywhere.patch
--- mysql-8.0-8.0.36/debian/patches/64bit_time_everywhere.patch 1969-12-31
16:00:00.0 -0800
+++ mysql-8.0-8.0.36/debian/patches/64bit_time_everywhere.patch 2024-03-08
21:59:20.0 -0800
@@ -0,0 +1,22 @@
+Description: fix test for 64-bit time_t
+ i386 is the only architecture where we don't have 64-bit time_t now.
+ Update the tests accordingly.
+Author: Steve Langasek
+Forwarded: no
+Last-Update: 2024-03-08
+
+Index: mysql-8.0-8.0.36/mysql-test/include/have_32bits_time.inc
+===
+--- mysql-8.0-8.0.36.orig/mysql-test/include/have_32bits_time.inc
mysql-8.0-8.0.36/mysql-test/include/have_32bits_time.inc
+@@ -1,8 +1,7 @@
+ # see also have_64bits_time.inc
+
+-let $have_64bit = `SELECT @@version_compile_machine IN
+- ('x86_64', 'amd64', 'sparc', 'sparc64', 'arm64',
'aarch64',
+- 'ppc64', 'ppc64le', 's390x')`;
++let $have_64bit = `SELECT @@version_compile_machine != 'i686'`;
++
+ if ($have_64bit) {
+ --skip Doesn't support 32 bits UNIX time, only 64 bits
+ }
diff -Nru mysql-8.0-8.0.36/debian/patches/series
mysql-8.0-8.0.36/debian/patches/series
--- mysql-8.0-8.0.36/debian/patches/series 2024-03-05 06:26:25.0
-0800
+++ mysql-8.0-8.0.36/debian/patches/series 2024-03-08 21:55:11.0
-0800
@@ -9,3 +9,4 @@
disable_timestamping_test.patch
mysql_secure_installation-remove-root-pw-creation.patch
suppress_armhf_test_warning.patch
+64bit_time_everywhere.patch
Bug#1065696: Fwd: E: unsupported command: poweroff.no-molly-guard
Hi Helmut, This looks like an unexpected edge case from the recent usr-merge changes: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065696 It sounds like a system using sysvinit, instead of systemd, which was recently upgraded using usrmerge. Francois -- https://fmarier.org/
Bug#1065633: openldap: FTBFS on hppa - implicit declaration of function 'kadm5_s_init_with_password_ctx'
On Fri, Mar 08, 2024 at 08:04:59PM -0800, Ryan Tandy wrote: > > This does fix the build failure. I was about to push such a change to the > > repo and do a maintainer upload, since I've never been removed from the > > uploaders field after all these years ;) Do you want me to do this, or > > would you be able to do it tonight? Getting openldap to build is a priority > > wrt rebootstrapping 32-bit archs for time_t. > I wasn't sure where openldap was on the priority list for arm* since it's > still BD-Uninstallable on the buildds. Yes, it's BD-Uninstallable there because it needs manually built to address build loops (ldap->cyrus-sasl2->krb5). > Yes, I can upload it tonight, in a couple of hours from now. Is that OK? Works for me! > > WARNING! > > Running as root! > > There's a fair chance slapd will fail to start. > > Check file permissions! > > > > Starting slapd on TCP/IP port 9011... > > Testing slapd searching... > > Creating a dynamic entry... > > ldapadd failed (255)! > > ../../../tests/scripts/test046-dds: 93: kill: No such process > > > > > > > > > test046-dds failed for mdb after 2 seconds > > (exit 255) > > make[4]: *** [Makefile:303: mdb-mod] Error 255 > I have not seen this failure. Ran it again just now and it passed. But I > only run amd64... I wouldn't be able to dig into that tonight, even if I > could reproduce it. Do you think I should disable the test proactively? Rather than disabling the test in the package, I can do a DEB_BUILD_OPTIONS=nocheck build to help get things bootstrapped in the archive. I'm interested to know if it also shows up on hppa, since that would definitely point to it being time_t related. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Bug#1065633: openldap: FTBFS on hppa - implicit declaration of function 'kadm5_s_init_with_password_ctx'
On Fri, Mar 08, 2024 at 07:33:59PM -0800, Steve Langasek wrote: This bug is also reproducible on the armel and armhf release archs as a result of the time_t transition, so bumping this to serious. ACK. This does fix the build failure. I was about to push such a change to the repo and do a maintainer upload, since I've never been removed from the uploaders field after all these years ;) Do you want me to do this, or would you be able to do it tonight? Getting openldap to build is a priority wrt rebootstrapping 32-bit archs for time_t. I wasn't sure where openldap was on the priority list for arm* since it's still BD-Uninstallable on the buildds. Yes, I can upload it tonight, in a couple of hours from now. Is that OK? BTW there's also a reproducible test failure that I'm seeing on armhf in both Debian and Ubuntu which is new; I'm not sure if it's related to time_t, or if it affects other archs? Starting test046-dds for mdb... running defines.sh Running slapadd to build slapd database... Running slapindex to index slapd database... WARNING! Running as root! There's a fair chance slapd will fail to start. Check file permissions! Starting slapd on TCP/IP port 9011... Testing slapd searching... Creating a dynamic entry... ldapadd failed (255)! ../../../tests/scripts/test046-dds: 93: kill: No such process test046-dds failed for mdb after 2 seconds (exit 255) make[4]: *** [Makefile:303: mdb-mod] Error 255 I have not seen this failure. Ran it again just now and it passed. But I only run amd64... I wouldn't be able to dig into that tonight, even if I could reproduce it. Do you think I should disable the test proactively? thanks, Ryan
Bug#1065696: E: unsupported command: poweroff.no-molly-guard
Package: molly-guard Version: 0.8.3 Severity: grave Justification: renders package unusable Severity chosen both because this makes the package unusable (I will have to remove it now) and because it breaks the whole system (boot). root@aranym:/var/cache/apt/archives # poweroff W: molly-guard: SSH session detected! Please type in hostname of the machine to poweroff: aranym E: unsupported command: poweroff.no-molly-guard 1|root@aranym:/var/cache/apt/archives # which poweroff.no-molly-guard /usr/sbin/poweroff.no-molly-guard root@aranym:/var/cache/apt/archives # dpkg -S /usr/sbin/poweroff.no-molly-guard diversion by molly-guard from: /usr/sbin/poweroff diversion by molly-guard to: /usr/sbin/poweroff.no-molly-guard root@aranym:/var/cache/apt/archives # dpkg -S /usr/sbin/poweroff diversion by molly-guard from: /usr/sbin/poweroff diversion by molly-guard to: /usr/sbin/poweroff.no-molly-guard molly-guard, sysvinit-core: /usr/sbin/poweroff At this point, I thought this was somehow a bug in sysvinit-core, but… root@aranym:/var/cache/apt/archives # ll /usr/sbin/poweroff* lrwxrwxrwx 1 root root 30 Dec 22 22:23 /usr/sbin/poweroff -> ../lib/molly-guard/molly-guard* lrwxrwxrwx 1 root root 4 Feb 29 11:22 /usr/sbin/poweroff.no-molly-guard -> halt* root@aranym:/var/cache/apt/archives # less /usr/sbin/poweroff.no-molly-guard #!/bin/sh # # shutdown -- wrapper script to guard against accidental shutdowns […] ME=molly-guard […] … this shows pretty clearly who’s at fault here. The system was just converted to UsrMove in order to be able to install a newer kernel for upgrading. -- System Information: Debian Release: buster/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: m68k Kernel: Linux 4.19.0-4-m68k Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/lksh Init: sysvinit (via /sbin/init) Versions of packages molly-guard depends on: ii procps 2:3.3.15-2 molly-guard recommends no packages. molly-guard suggests no packages. -- no debconf information
Processed: Re: Bug#1065633: openldap: FTBFS on hppa - implicit declaration of function 'kadm5_s_init_with_password_ctx'
Processing control commands: > severity -1 serious Bug #1065633 [src:openldap] openldap: FTBFS on hppa - implicit declaration of function ‘kadm5_s_init_with_password_ctx’ Severity set to 'serious' from 'important' -- 1065633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1064764 is forwarded to https://github.com/jpvanhal/flask-basicauth/issues/32
Processing commands for cont...@bugs.debian.org: > forwarded 1064764 https://github.com/jpvanhal/flask-basicauth/issues/32 Bug #1064764 [src:flask-basicauth] flask-basicauth: FTBFS: AssertionError: b'' != b'This view always requires authentication.' Set Bug forwarded-to-address to 'https://github.com/jpvanhal/flask-basicauth/issues/32'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1064764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1065373: marked as done (fix heimdal build with abi=time64)
Your message dated Sat, 09 Mar 2024 01:04:42 +
with message-id
and subject line Bug#1065373: fixed in heimdal 7.8.git20221117.28daf24+dfsg-5
has caused the Debian Bug report #1065373,
regarding fix heimdal build with abi=time64
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1065373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065373
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:heimdal
Version: 7.8.git20221117.28daf24+dfsg-4
Severity: serious
Tags: sid trixie ftbfs patch
fix heimdal build with abi=time64. This is just a work-around for a
configure test not setting LIB_crypt.
diff -Nru heimdal-7.8.git20221117.28daf24+dfsg/debian/changelog heimdal-7.8.git20221117.28daf24+dfsg/debian/changelog
--- heimdal-7.8.git20221117.28daf24+dfsg/debian/changelog 2024-02-29 17:20:07.0 +0100
+++ heimdal-7.8.git20221117.28daf24+dfsg/debian/changelog 2024-03-03 15:31:17.0 +0100
@@ -1,3 +1,10 @@
+heimdal (7.8.git20221117.28daf24+dfsg-4.1ubuntu2) noble; urgency=medium
+
+ * Filter-out -Werror=implicit-function-declaration, unconditionally set
+by abi=time64.
+
+ -- Matthias Klose Sun, 03 Mar 2024 15:31:17 +0100
+
heimdal (7.8.git20221117.28daf24+dfsg-4.1ubuntu1) noble; urgency=low
* Merge from Debian unstable. Remaining changes:
diff -Nru heimdal-7.8.git20221117.28daf24+dfsg/debian/rules heimdal-7.8.git20221117.28daf24+dfsg/debian/rules
--- heimdal-7.8.git20221117.28daf24+dfsg/debian/rules 2024-02-28 16:57:12.0 +0100
+++ heimdal-7.8.git20221117.28daf24+dfsg/debian/rules 2024-03-03 15:31:17.0 +0100
@@ -37,7 +37,7 @@
dh_auto_test -- -j1
override_dh_auto_configure:
- ./configure $(shell dpkg-buildflags --export=configure) \
+ ./configure $(shell dpkg-buildflags --export=configure | sed 's/-Werror=implicit-function-declaration//') \
--disable-silent-rules \
--libexecdir="\$${prefix}/sbin" \
--enable-shared \
--- End Message ---
--- Begin Message ---
Source: heimdal
Source-Version: 7.8.git20221117.28daf24+dfsg-5
Done: Brian May
We believe that the bug you reported is fixed in the latest version of
heimdal, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Brian May (supplier of updated heimdal package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 09 Mar 2024 11:01:27 +1100
Source: heimdal
Architecture: source
Version: 7.8.git20221117.28daf24+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Brian May
Changed-By: Brian May
Closes: 1065373
Changes:
heimdal (7.8.git20221117.28daf24+dfsg-5) unstable; urgency=medium
.
* Apply NMU patches. Closes: #1065373.
Checksums-Sha1:
9c499f72b63488b8fe8994bf1a97fa8eb7fa03e6 3743
heimdal_7.8.git20221117.28daf24+dfsg-5.dsc
0a8023057a49ac94ac196b949bd50841cdbaca4a 7744956
heimdal_7.8.git20221117.28daf24+dfsg.orig.tar.xz
d196adbb94da3ee5d05f752ef40dbaaf34bd96a9 130012
heimdal_7.8.git20221117.28daf24+dfsg-5.debian.tar.xz
dd7103296ba2af696e6bd1d85f8e6942ae88ef93 7581
heimdal_7.8.git20221117.28daf24+dfsg-5_source.buildinfo
Checksums-Sha256:
059ec587e91fcc356eb5fcdb3ba531079651cf3dcc4594dc3bcab613a3df2837 3743
heimdal_7.8.git20221117.28daf24+dfsg-5.dsc
ae703f84856b98609985f8c63ed2d414c69fe8d55147137b3a71136621ffd454 7744956
heimdal_7.8.git20221117.28daf24+dfsg.orig.tar.xz
dbdd58a9f444f20c3f15985884e7bd9e67068567ef6135c5e674fe273eb60c83 130012
heimdal_7.8.git20221117.28daf24+dfsg-5.debian.tar.xz
09ae0b3d9f1cc764fa26b3c4e5c1576f32149510ddfca2f21ce12ac287d3e555 7581
heimdal_7.8.git20221117.28daf24+dfsg-5_source.buildinfo
Files:
470c6189a0146de238608b9266ee1235 3743 net optional
heimdal_7.8.git20221117.28daf24+dfsg-5.dsc
2bfd3177cc2f35aa3d5917c67d2eb845 7744956 net optional
heimdal_7.8.git20221117.28daf24+dfsg.orig.tar.xz
41de3ba7f2b8e64fc87a8f72d6d83fbd 130012 net optional
heimdal_7.8.git20221117.28daf24+dfsg-5.debian.tar.xz
14e39f4916d8678a615d524b34aa4dd2 7581 net optional
heimdal_7.8.git20221117.28daf24+dfsg-5_source.buildinfo
-BEGIN PGP SIGNATURE-
Bug#1055852: marked as done (frr: CVE-2023-38407 CVE-2023-41361 CVE-2023-46752 CVE-2023-46753 CVE-2023-47234 CVE-2023-47235)
Your message dated Sat, 09 Mar 2024 00:04:55 + with message-id and subject line Bug#1055852: fixed in frr 9.1-0.1 has caused the Debian Bug report #1055852, regarding frr: CVE-2023-38407 CVE-2023-41361 CVE-2023-46752 CVE-2023-46753 CVE-2023-47234 CVE-2023-47235 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1055852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055852 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: frr X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for frr. CVE-2023-38407[0]: | bgpd/bgp_label.c in FRRouting (FRR) before 8.5 attempts to read | beyond the end of the stream during labeled unicast parsing. https://github.com/FRRouting/frr/pull/12951 https://github.com/FRRouting/frr/commit/7404a914b0cafe046703c8381903a80d3def8f8b (base_9.0) https://github.com/FRRouting/frr/pull/12956 https://github.com/FRRouting/frr/commit/ab362eae68edec12c175d9bc488bcc3f8b73d36f (frr-8.5) CVE-2023-41361[1]: | An issue was discovered in FRRouting FRR 9.0. bgpd/bgp_open.c does | not check for an overly large length of the rcv software version. https://github.com/FRRouting/frr/pull/14241 Fixed by: https://github.com/FRRouting/frr/commit/b4d09af9194d20a7f9f16995a062f5d8e3d32840 Backport for 9.0 branch: https://github.com/FRRouting/frr/pull/14250 Fixed by: https://github.com/FRRouting/frr/commit/73ad93a83f18564bb7bff4659872f7ec1a64b05e CVE-2023-46752[2]: | An issue was discovered in FRRouting FRR through 9.0.1. It | mishandles malformed MP_REACH_NLRI data, leading to a crash. Fixed by: https://github.com/FRRouting/frr/commit/b08afc81c60607a4f736f418f2e3eb06087f1a35 (master) Fixed by: https://github.com/FRRouting/frr/commit/30b5c2a434d25981e16792f6f50162beb517ae4d (stable/8.5 branch) CVE-2023-46753[3]: | An issue was discovered in FRRouting FRR through 9.0.1. A crash can | occur for a crafted BGP UPDATE message without mandatory attributes, | e.g., one with only an unknown transit attribute. Fixed by: https://github.com/FRRouting/frr/commit/d8482bf011cb2b173e85b65b4bf3d5061250cdb9 (master) Fixed by: https://github.com/FRRouting/frr/commit/21418d64af11553c402f932b0311c812d98ac3e4 (stable/8.5 branch) CVE-2023-47234[4]: | An issue was discovered in FRRouting FRR through 9.0.1. A crash can | occur when processing a crafted BGP UPDATE message with a | MP_UNREACH_NLRI attribute and additional NLRI data (that lacks | mandatory path attributes). https://github.com/FRRouting/frr/commit/c37119df45bbf4ef713bc10475af2ee06e12f3bf CVE-2023-47235[5]: | An issue was discovered in FRRouting FRR through 9.0.1. A crash can | occur when a malformed BGP UPDATE message with an EOR is processed, | because the presence of EOR does not lead to a treat-as-withdraw | outcome. https://github.com/FRRouting/frr/commit/6814f2e0138a6ea5e1f83bdd9085d9a7700b If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-38407 https://www.cve.org/CVERecord?id=CVE-2023-38407 [1] https://security-tracker.debian.org/tracker/CVE-2023-41361 https://www.cve.org/CVERecord?id=CVE-2023-41361 [2] https://security-tracker.debian.org/tracker/CVE-2023-46752 https://www.cve.org/CVERecord?id=CVE-2023-46752 [3] https://security-tracker.debian.org/tracker/CVE-2023-46753 https://www.cve.org/CVERecord?id=CVE-2023-46753 [4] https://security-tracker.debian.org/tracker/CVE-2023-47234 https://www.cve.org/CVERecord?id=CVE-2023-47234 [5] https://security-tracker.debian.org/tracker/CVE-2023-47235 https://www.cve.org/CVERecord?id=CVE-2023-47235 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: frr Source-Version: 9.1-0.1 Done: Daniel Baumann We believe that the bug you reported is fixed in the latest version of frr, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Baumann (supplier of updated frr package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by
Bug#1058132: marked as done (python-mitogen: FTBFS: ModuleNotFoundError: No module named 'imp')
Your message dated Fri, 08 Mar 2024 22:40:30 +
with message-id
and subject line Bug#1058132: fixed in python-mitogen 0.3.4-3
has caused the Debian Bug report #1058132,
regarding python-mitogen: FTBFS: ModuleNotFoundError: No module named 'imp'
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1058132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-mitogen
Version: 0.3.4-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- --system custom --test-args="{interpreter} \
> -m unittest discover -v \
> --start-directory {dir}/tests \
> --pattern '*_test.py'"
> I: pybuild base:310: python3.12 -m unittest discover -v
> --start-directory /<>/tests--pattern
> '*_test.py'
> broker_test (unittest.loader._FailedTest.broker_test) ... ERROR
> buildah_test (unittest.loader._FailedTest.buildah_test) ... ERROR
> call_error_test (unittest.loader._FailedTest.call_error_test) ... ERROR
> call_function_test (unittest.loader._FailedTest.call_function_test) ... ERROR
> channel_test (unittest.loader._FailedTest.channel_test) ... ERROR
> connection_test (unittest.loader._FailedTest.connection_test) ... ERROR
> context_test (unittest.loader._FailedTest.context_test) ... ERROR
> create_child_test (unittest.loader._FailedTest.create_child_test) ... ERROR
> doas_test (unittest.loader._FailedTest.doas_test) ... ERROR
> docker_test (unittest.loader._FailedTest.docker_test) ... ERROR
> error_test (unittest.loader._FailedTest.error_test) ... ERROR
> fakessh_test (unittest.loader._FailedTest.fakessh_test) ... ERROR
> file_service_test (unittest.loader._FailedTest.file_service_test) ... ERROR
> first_stage_test (unittest.loader._FailedTest.first_stage_test) ... ERROR
> fork_test (unittest.loader._FailedTest.fork_test) ... ERROR
> id_allocation_test (unittest.loader._FailedTest.id_allocation_test) ... ERROR
> importer_test (unittest.loader._FailedTest.importer_test) ... ERROR
> io_op_test (unittest.loader._FailedTest.io_op_test) ... ERROR
> iter_split_test (unittest.loader._FailedTest.iter_split_test) ... ERROR
> jail_test (unittest.loader._FailedTest.jail_test) ... ERROR
> kubectl_test (unittest.loader._FailedTest.kubectl_test) ... ERROR
> latch_test (unittest.loader._FailedTest.latch_test) ... ERROR
> local_test (unittest.loader._FailedTest.local_test) ... ERROR
> log_handler_test (unittest.loader._FailedTest.log_handler_test) ... ERROR
> lxc_test (unittest.loader._FailedTest.lxc_test) ... ERROR
> lxd_test (unittest.loader._FailedTest.lxd_test) ... ERROR
> master_test (unittest.loader._FailedTest.master_test) ... ERROR
> message_test (unittest.loader._FailedTest.message_test) ... ERROR
> minify_test (unittest.loader._FailedTest.minify_test) ... ERROR
> mitogen_protocol_test (unittest.loader._FailedTest.mitogen_protocol_test) ...
> ERROR
> module_finder_test (unittest.loader._FailedTest.module_finder_test) ... ERROR
> nested_test (unittest.loader._FailedTest.nested_test) ... ERROR
> os_fork_test (unittest.loader._FailedTest.os_fork_test) ... ERROR
> parent_test (unittest.loader._FailedTest.parent_test) ... ERROR
> podman_test (unittest.loader._FailedTest.podman_test) ... ERROR
> policy_function_test (unittest.loader._FailedTest.policy_function_test) ...
> ERROR
> poller_test (unittest.loader._FailedTest.poller_test) ... ERROR
> polyfill_functions_test (unittest.loader._FailedTest.polyfill_functions_test)
> ... ERROR
> push_file_service_test (unittest.loader._FailedTest.push_file_service_test)
> ... ERROR
> reaper_test (unittest.loader._FailedTest.reaper_test) ... ERROR
> receiver_test (unittest.loader._FailedTest.receiver_test) ... ERROR
> responder_test (unittest.loader._FailedTest.responder_test) ... ERROR
> router_test (unittest.loader._FailedTest.router_test) ... ERROR
> select_test (unittest.loader._FailedTest.select_test) ... ERROR
> service_test (unittest.loader._FailedTest.service_test) ... ERROR
> setns_test (unittest.loader._FailedTest.setns_test) ... ERROR
> signals_test (unittest.loader._FailedTest.signals_test) ... ERROR
> ssh_test (unittest.loader._FailedTest.ssh_test) ... ERROR
> su_test (unittest.loader._FailedTest.su_test) ... ERROR
> sudo_test (unittest.loader._FailedTest.sudo_test) ... ERROR
>
Bug#1061755: marked as done (python-mitogen ftbfs with Python 3.12 as default)
Your message dated Fri, 08 Mar 2024 22:40:30 + with message-id and subject line Bug#1061755: fixed in python-mitogen 0.3.4-3 has caused the Debian Bug report #1061755, regarding python-mitogen ftbfs with Python 3.12 as default to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1061755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061755 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-mitogen Version: 0.3.4-2 Severity: serious Tags: sid trixie ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 With python3-defaults from experimental, the package fails to build: [...] == ERROR: utils_test (unittest.loader._FailedTest.utils_test) -- ImportError: Failed to import test module: utils_test Traceback (most recent call last): File "/usr/lib/python3.12/unittest/loader.py", line 394, in _find_test_path module = self._get_module_from_name(name) File "/usr/lib/python3.12/unittest/loader.py", line 337, in _get_module_from_name __import__(name) File "/<>/tests/utils_test.py", line 1, in import mitogen.core File "/<>/mitogen/core.py", line 63, in import imp ModuleNotFoundError: No module named 'imp' -- Ran 55 tests in 0.003s FAILED (errors=55) --- End Message --- --- Begin Message --- Source: python-mitogen Source-Version: 0.3.4-3 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of python-mitogen, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated python-mitogen package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 08 Mar 2024 18:21:07 -0400 Source: python-mitogen Architecture: source Version: 0.3.4-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Stefano Rivera Closes: 1058132 1059935 1061755 Changes: python-mitogen (0.3.4-3) unstable; urgency=medium . * Patch: Support setting interpreter_python in config, again. * Patch: Support Ansible 2.16. (Closes: #1059935) * Patch: Python 3.11 support. * Patch: Python 3.12 support. (Closes: #1058132, 1061755) * Patch test module paths in testlib.py in the ansible-tests autopkgtest. Checksums-Sha1: 27a235cf3b4050c1fda7157ce9140fef34a7a329 1794 python-mitogen_0.3.4-3.dsc 8a8ea5e14081060ad756b119aa5d7228a70f58af 33276 python-mitogen_0.3.4-3.debian.tar.xz 5730389738b6b3b03086d8a7ba4f06b65d9470ad 6644 python-mitogen_0.3.4-3_source.buildinfo Checksums-Sha256: d3fe35647dbf80bcbb2818d2b9ce00849b80f9a8ac7ff2d4781378c452c31dc6 1794 python-mitogen_0.3.4-3.dsc 0b7669f33f2f51f94cb30182db207311a4966c768691612019773293fe935733 33276 python-mitogen_0.3.4-3.debian.tar.xz 5929b15ea5934e7ebed05f645b46d9f1a0b7618bb428e7239efecae3ef5733b7 6644 python-mitogen_0.3.4-3_source.buildinfo Files: 967824f7e2947be91a17a133be33ab25 1794 python optional python-mitogen_0.3.4-3.dsc 1fb2427ec140afc733f0ef79ee10 33276 python optional python-mitogen_0.3.4-3.debian.tar.xz 3b5e1d6f6aebcef9f1647ed2ce682ae0 6644 python optional python-mitogen_0.3.4-3_source.buildinfo -BEGIN PGP SIGNATURE- iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCZeuPaRQcc3RlZmFub3JA ZGViaWFuLm9yZwAKCRBHew2wJjpU2K6UAQCn3tqa+peVhJEk4FzKMUgr7eWjIZ/z Vm78rgOnZmahuAD/QM7CFhUOe1Hc6NMjEMRaxjAb5Fwm+aQ8jDQQRtv6nwk= =JnDt -END PGP SIGNATURE- pgplRm4VyWICx.pgp Description: PGP signature --- End Message ---
Bug#1065654: mesa ftbfs with time_t64
Il Ven 8 Mar 2024, 11:21 Matthias Klose ha scritto: > On 08.03.24 11:00, Fabio Pedretti wrote: > > Already fixed upstream, the patch will be included since 24.0.3 (will > > be released in 5 days): > > > https://cgit.freedesktop.org/mesa/mesa/commit/?h=staging/24.0=8ea039019761ecc25d49f075aef50de6e81db854 > > no, that commit is only fixing one occurrence. > The other file is not built in Debian, a fix will anyway also be included in 24.0.3. >
Processed: Bug#1058132 marked as pending in python-mitogen
Processing control commands: > tag -1 pending Bug #1058132 [src:python-mitogen] python-mitogen: FTBFS: ModuleNotFoundError: No module named 'imp' Added tag(s) pending. -- 1058132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058132 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058132: marked as pending in python-mitogen
Control: tag -1 pending Hello, Bug #1058132 in python-mitogen reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-mitogen/-/commit/d017ecfea882adde47ddc3a7b3a58355babb6a28 Patch: Python 3.12 support. (Closes: #1058132, 1061755) (this message was generated automatically) -- Greetings https://bugs.debian.org/1058132
Bug#1062491: marked as done (knot: NMU diff for 64-bit time_t transition)
Your message dated Fri, 08 Mar 2024 22:20:32 +
with message-id
and subject line Bug#1062491: fixed in knot 3.3.5-1.1
has caused the Debian Bug report #1062491,
regarding knot: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1062491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062491
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: knot
Version: 3.3.4-1
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
knot as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.
Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time. Therefore I have prepared a 0-day NMU for knot
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.
Please find the patch for this NMU attached.
If you have any concerns about this patch, please reach out ASAP. Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-15-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru knot-3.3.4/debian/changelog knot-3.3.4/debian/changelog
--- knot-3.3.4/debian/changelog 2024-01-24 13:12:36.0 +
+++ knot-3.3.4/debian/changelog 2024-02-01 17:07:28.0 +
@@ -1,3 +1,10 @@
+knot (3.3.4-1.1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Graham Inggs Thu, 01 Feb 2024 17:07:28 +
+
knot (3.3.4-1) unstable; urgency=medium
* New upstream version 3.3.4
diff -Nru knot-3.3.4/debian/control knot-3.3.4/debian/control
--- knot-3.3.4/debian/control 2024-01-08 12:32:19.0 +
+++ knot-3.3.4/debian/control 2024-02-01 17:07:28.0 +
@@ -49,9 +49,9 @@
Architecture: any
Depends:
adduser,
- libdnssec9 (= ${binary:Version}),
- libknot14 (= ${binary:Version}),
- libzscanner4 (= ${binary:Version}),
+ libdnssec9t64 (= ${binary:Version}),
+ libknot14t64 (= ${binary:Version}),
+ libzscanner4t64 (= ${binary:Version}),
${misc:Depends},
${shlibs:Depends},
Pre-Depends:
@@ -68,7 +68,10 @@
registry and hence is well suited to run anything from the root
zone, the top-level domain, to many smaller standard domain names.
-Package: libknot14
+Package: libknot14t64
+Provides: ${t64:Provides}
+Replaces: libknot14
+Breaks: libknot14 (<< ${source:Version})
Architecture: any
Depends:
${misc:Depends},
@@ -85,7 +88,10 @@
This package provides libknot shared library used by Knot DNS and
Knot Resolver.
-Package: libzscanner4
+Package: libzscanner4t64
+Provides: ${t64:Provides}
+Replaces: libzscanner4
+Breaks: libzscanner4 (<< ${source:Version})
Architecture: any
Depends:
${misc:Depends},
@@ -102,7 +108,10 @@
This package provides a fast zone parser shared library used by Knot
DNS and Knot Resolver.
-Package: libdnssec9
+Package: libdnssec9t64
+Provides: ${t64:Provides}
+Replaces: libdnssec9
+Breaks: libdnssec9 (<< ${source:Version})
Architecture: any
Depends:
${misc:Depends},
@@ -122,10 +131,10 @@
Package: libknot-dev
Architecture: any
Depends:
- libdnssec9 (= ${binary:Version}),
+ libdnssec9t64 (= ${binary:Version}),
libgnutls28-dev,
- libknot14 (= ${binary:Version}),
- libzscanner4 (=
Bug#1065489: marked as done (mongo-c-driver: FTBFS on armhf: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘__suseconds64_t’ {aka ‘long long int’})
Your message dated Fri, 08 Mar 2024 19:50:47 +
with message-id
and subject line Bug#1065489: fixed in mongo-c-driver 1.26.1-1
has caused the Debian Bug report #1065489,
regarding mongo-c-driver: FTBFS on armhf: format ‘%ld’ expects argument of type
‘long int’, but argument 4 has type ‘__suseconds64_t’ {aka ‘long long int’}
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1065489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065489
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mongo-c-driver
Version: 1.26.0-1.1
Severity: serious
Tags: ftbfs
User: debian-...@lists.debian.org
Usertags: time-t
Dear Maintainer,
mongo-c-driver fails to build from source on armhf. The failure may be
explained with the build flags introduced for the time64 migration,
which are on by default on armhf:
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64
-Werror=implicit-function-declaration
[ 37%] Building C object
src/libmongoc/CMakeFiles/mongoc_static.dir/src/mongoc/mongoc-error.c.o
cd /<>/obj-arm-linux-gnueabihf/src/libmongoc && /usr/bin/cc
-DBSON_STATIC -DHAVE_STDARG_H -DHAVE_UNISTD_H -DKMS_MESSAGE_ENABLE_CRYPTO
-DKMS_MESSAGE_ENABLE_CRYPTO_LIBCRYPTO -DKMS_MESSAGE_LITTLE_ENDIAN
-DKMS_MSG_STATIC -DMCOMMON_NAME_PREFIX=_mongoc_mcommon -DMONGOC_COMPILATION
-DMONGOC_STATIC -D_BSD_SOURCE -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=700
-I/<>/src/libmongoc/../kms-message/src
-I/<>/obj-arm-linux-gnueabihf/src/libmongoc/src
-I/<>/obj-arm-linux-gnueabihf/src/libmongoc/src/mongoc
-I/<>/src/libmongoc/src
-I/<>/src/libmongoc/src/mongoc
-I/<>/src/libmongoc/../../src/common
-I/<>/obj-arm-linux-gnueabihf/src/libmongoc/../../src
-I/<>/obj-arm-linux-gnueabihf/src/libmongoc/../../src/common
-I/<>/src/libbson/src
-I/<>/obj-arm-linux-gnueabihf/src/libbson/src
-I/<>/src/common
-I/<>/obj-arm-linux-gnueabihf/src/common -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -std=c99 -Werror=implicit
-Werror=return-type -Werror=incompatible-pointer-types -Werror=int-conversion
-Werror=discarded-qualifiers -Werror=uninitialized -Werror -pedantic -Wall
-Wempty-body -Wexpansion-to-defined -Wformat -Wformat-nonliteral
-Wformat-security -Winit-self -Wmissing-include-dirs -Wredundant-decls -Wshadow
-Wstrict-prototypes -Wswitch-default -Wswitch-enum -Wundef -Wuninitialized
-Wno-strict-aliasing -fPIC -DUTF8PROC_EXPORTS -MD -MT
src/libmongoc/CMakeFiles/mongoc_static.dir/src/mongoc/mongoc-error.c.o -MF
CMakeFiles/mongoc_static.dir/src/mongoc/mongoc-error.c.o.d -o
CMakeFiles/mongoc_static.dir/src/mongoc/mongoc-error.c.o -c
/<>/src/libmongoc/src/mongoc/mongoc-error.c
/<>/src/libmongoc/src/mongoc/mongoc-log.c: In function
‘mongoc_log_default_handler’:
/<>/src/libmongoc/src/mongoc/mongoc-log.c:215:21: error: format
‘%ld’ expects argument of type ‘long int’, but argument 4 has type
‘__suseconds64_t’ {aka ‘long long int’} [-Werror=format=]
215 | "%s.%04ld: [%5d]: %8s: %12s: %s\n",
| ^
| |
| long int
| %04lld
216 | nowstr,
217 | tv.tv_usec / 1000L,
| ~~
||
|__suseconds64_t {aka long long int}
cc1: all warnings being treated as errors
make[3]: *** [src/libmongoc/CMakeFiles/mongoc_shared.dir/build.make:765:
src/libmongoc/CMakeFiles/mongoc_shared.dir/src/mongoc/mongoc-log.c.o] Error 1
--- End Message ---
--- Begin Message ---
Source: mongo-c-driver
Source-Version: 1.26.1-1
Done: Kyle Kloberdanz
We believe that the bug you reported is fixed in the latest version of
mongo-c-driver, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Kyle Kloberdanz (supplier of updated
mongo-c-driver package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date:
Bug#1063752: [Debichem-devel] Bug#1063752: custodian: Inappriate maintainer address
Hi, On Tue, Feb 13, 2024 at 11:24:15AM +0100, Drew Parsons wrote: > Source: custodian > Followup-For: Bug #1063752 > X-Debbugs-Cc: Debichem Team > Control: reassign 1063752 lists.debian.org > Control: affects 1063752 src:custodian > > Scott Kitterman reported that lists.alioth.debian.org is bouncing > emails from debian official addresses (ftpmas...@ftp-master.debian.org > in this case, processing packages for the Debichem team with Maintainer > address debichem-de...@lists.alioth.debian.org) > > Scott filed the bug against src:custodian, but the bug must be in the > mailing list daemon, so I'm reassigning the bug to lists.debian.org I don't think the Debian listmasters are responsible for lists.alioth.debian.org - also, I don't think there is a pseudo package for it :-/ I got another complaint from ftp-master for a NEW processing mail some time ago, so maybe it is related to that. After checking the admin interface, it looks like lists.alioth.debian.org was updated last month and the configuration reset - suspected spam mails were auto-rejected again while they were sent to me previously. I reverted that now and maybe that fixes it already. Michael
Bug#1064736: marked as done (urlwatch: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Fri, 08 Mar 2024 18:06:11 +
with message-id
and subject line Bug#1064736: fixed in urlwatch 2.28-2
has caused the Debian Bug report #1064736,
regarding urlwatch: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p "3.12 3.11" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1064736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064736
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: urlwatch
Version: 2.28-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3,sphinxdoc --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:305: python3.12 setup.py config
> running config
> I: pybuild base:305: python3.11 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:305: /usr/bin/python3.12 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12_urlwatch/build/urlwatch
> copying lib/urlwatch/__init__.py ->
> /<>/.pybuild/cpython3_3.12_urlwatch/build/urlwatch
> copying lib/urlwatch/mailer.py ->
> /<>/.pybuild/cpython3_3.12_urlwatch/build/urlwatch
> copying lib/urlwatch/main.py ->
> /<>/.pybuild/cpython3_3.12_urlwatch/build/urlwatch
> copying lib/urlwatch/filters.py ->
> /<>/.pybuild/cpython3_3.12_urlwatch/build/urlwatch
> copying lib/urlwatch/storage.py ->
> /<>/.pybuild/cpython3_3.12_urlwatch/build/urlwatch
> copying lib/urlwatch/reporters.py ->
> /<>/.pybuild/cpython3_3.12_urlwatch/build/urlwatch
> copying lib/urlwatch/html2txt.py ->
> /<>/.pybuild/cpython3_3.12_urlwatch/build/urlwatch
> copying lib/urlwatch/command.py ->
> /<>/.pybuild/cpython3_3.12_urlwatch/build/urlwatch
> copying lib/urlwatch/migration.py ->
> /<>/.pybuild/cpython3_3.12_urlwatch/build/urlwatch
> copying lib/urlwatch/cli.py ->
> /<>/.pybuild/cpython3_3.12_urlwatch/build/urlwatch
> copying lib/urlwatch/worker.py ->
> /<>/.pybuild/cpython3_3.12_urlwatch/build/urlwatch
> copying lib/urlwatch/jobs.py ->
> /<>/.pybuild/cpython3_3.12_urlwatch/build/urlwatch
> copying lib/urlwatch/config.py ->
> /<>/.pybuild/cpython3_3.12_urlwatch/build/urlwatch
> copying lib/urlwatch/util.py ->
> /<>/.pybuild/cpython3_3.12_urlwatch/build/urlwatch
> copying lib/urlwatch/handler.py ->
> /<>/.pybuild/cpython3_3.12_urlwatch/build/urlwatch
> copying lib/urlwatch/xmpp.py ->
> /<>/.pybuild/cpython3_3.12_urlwatch/build/urlwatch
> copying lib/urlwatch/ical2txt.py ->
> /<>/.pybuild/cpython3_3.12_urlwatch/build/urlwatch
> I: pybuild base:305: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_urlwatch/build/urlwatch
> copying lib/urlwatch/__init__.py ->
> /<>/.pybuild/cpython3_3.11_urlwatch/build/urlwatch
> copying lib/urlwatch/mailer.py ->
> /<>/.pybuild/cpython3_3.11_urlwatch/build/urlwatch
> copying lib/urlwatch/main.py ->
> /<>/.pybuild/cpython3_3.11_urlwatch/build/urlwatch
> copying lib/urlwatch/filters.py ->
> /<>/.pybuild/cpython3_3.11_urlwatch/build/urlwatch
> copying lib/urlwatch/storage.py ->
> /<>/.pybuild/cpython3_3.11_urlwatch/build/urlwatch
> copying lib/urlwatch/reporters.py ->
> /<>/.pybuild/cpython3_3.11_urlwatch/build/urlwatch
> copying lib/urlwatch/html2txt.py ->
> /<>/.pybuild/cpython3_3.11_urlwatch/build/urlwatch
> copying lib/urlwatch/command.py ->
> /<>/.pybuild/cpython3_3.11_urlwatch/build/urlwatch
> copying lib/urlwatch/migration.py ->
> /<>/.pybuild/cpython3_3.11_urlwatch/build/urlwatch
> copying lib/urlwatch/cli.py ->
> /<>/.pybuild/cpython3_3.11_urlwatch/build/urlwatch
> copying lib/urlwatch/worker.py ->
> /<>/.pybuild/cpython3_3.11_urlwatch/build/urlwatch
> copying lib/urlwatch/jobs.py ->
> /<>/.pybuild/cpython3_3.11_urlwatch/build/urlwatch
> copying lib/urlwatch/config.py ->
> /<>/.pybuild/cpython3_3.11_urlwatch/build/urlwatch
> copying lib/urlwatch/util.py ->
> /<>/.pybuild/cpython3_3.11_urlwatch/build/urlwatch
> copying lib/urlwatch/handler.py ->
> /<>/.pybuild/cpython3_3.11_urlwatch/build/urlwatch
> copying lib/urlwatch/xmpp.py ->
> /<>/.pybuild/cpython3_3.11_urlwatch/build/urlwatch
> copying lib/urlwatch/ical2txt.py ->
> /<>/.pybuild/cpython3_3.11_urlwatch/build/urlwatch
>dh_auto_test -O--buildsystem=pybuild
> I:
Bug#1065548: marked as done (octave-statistics: binary-any FTBFS)
Your message dated Fri, 08 Mar 2024 18:05:25 + with message-id and subject line Bug#1065548: fixed in octave-statistics 1.6.4-3 has caused the Debian Bug report #1065548, regarding octave-statistics: binary-any FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1065548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065548 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: octave-statistics Version: 1.6.4-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=octave-statistics=1.6.4-1 ... debian/rules execute_after_dh_installdeb make[1]: Entering directory '/<>' # Use local JavaScript and CSS files debian/local-url sed: can't read debian/octave-statistics-common/usr/share/doc/octave-statistics-common/docs/*.html: No such file or directory # Remove empty directory rmdir debian/octave-statistics-common/usr/share/octave/packages/statistics-*/doc/ rmdir: failed to remove 'debian/octave-statistics-common/usr/share/octave/packages/statistics-*/doc/': No such file or directory make[1]: *** [debian/rules:15: execute_after_dh_installdeb] Error 1 --- End Message --- --- Begin Message --- Source: octave-statistics Source-Version: 1.6.4-3 Done: Rafael Laboissière We believe that the bug you reported is fixed in the latest version of octave-statistics, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rafael Laboissière (supplier of updated octave-statistics package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 08 Mar 2024 08:14:53 -0300 Source: octave-statistics Architecture: source Version: 1.6.4-3 Distribution: unstable Urgency: medium Maintainer: Debian Octave Group Changed-By: Rafael Laboissière Closes: 1065548 Changes: octave-statistics (1.6.4-3) unstable; urgency=medium . * d/rules: Instead of the execute_after_dh_installdeb target, use the -indep variant. The commands in this rule are intended to be run on the files installed by the octave-statistics-common package and fail in arch:any builds. (Really, closes: #1065548) Checksums-Sha1: 00e892d0db1358f82686cfe26b08a6c1cf7cb675 2442 octave-statistics_1.6.4-3.dsc d80521d24671b6b35206bd21286a42d2c4c0355b 8912 octave-statistics_1.6.4-3.debian.tar.xz Checksums-Sha256: 695526651f7674bd18b1e86d5750b101ec3798b0e02b4434764e8e5d10f0cc98 2442 octave-statistics_1.6.4-3.dsc 4f131ba0c13e47e79ed8c56388be9171eb2a8e0b53b4c6dc5002185725c7909b 8912 octave-statistics_1.6.4-3.debian.tar.xz Files: 0f09d09225cdaaa0d829d2faed53a775 2442 math optional octave-statistics_1.6.4-3.dsc 36df5c73b1422f6589db2d8464179cf3 8912 math optional octave-statistics_1.6.4-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEEP0ZDkUmP6HS9tdmPISSqGYN4XJAFAmXrTsQSHHJhZmFlbEBk ZWJpYW4ub3JnAAoJECEkqhmDeFyQEhoP/1i/bCZM1iIwRnwwQU5Yj1+xoa/N4X+F NrvPavKpxvSWePCfSqVE3Nn7eNNUF+2STJtZrJtF/xXnJpyGYS8DtsCcZxx2NTpX 8I1zq0pC1GrB9GDQ+Or2LNfvvmiez7966z4Q3TwNnL6m/OGsQAM0s62TUQDHxX2X v42Z5BiN3MldkfllbjeCPDVUFObYlg31yoZpCJyiHIxMGvqXHHNiWt81gQOV48Hi K8LZS8CiwQs5LDRAc53Gw1LnPDlpDhAkYoix1fSQx/UzahrFQHx2zoLMwAab0+xK QHgmq1VFMTGtKcUPmV5bJRt4qoutLkCJ6E69uuR8wrDwQnWumgAnV21L558QsmFe fk2c5LRs6lqqP33JQXeNKwZydz3Pu2ZEOlcrAUi5l3GydrJZdfjzSPxh+r3RgYWA 9s2pleOuetzrFIFinc0Yb5NH246axDScEWFPvygsRlX938qVWWUEF7FALsIlyRu/ 3K+rTxcz1BXiWUom9bMIhSVFrUom0V6ZP2w+zA2zjCvw8PWuvAjGwD6S+Xh8emMc zid0sObZ7kSttQc5wsYMlsRI6yOt5xq4LBAhDApLkji4mwjXL2SiJEJQpuHNLs/W uQfxjBnd01JKIg3eV4q7ooaDykzNs0eXha/NP3YmlT5S/ZbH9FqZ7fAJM6zXgEvP DzEly3cGsT23 =nb7Z -END PGP SIGNATURE- pgpdulWr3mh4I.pgp Description: PGP signature --- End Message ---
Processed: Bug#1065548 marked as pending in octave-statistics
Processing control commands: > tag -1 pending Bug #1065548 [src:octave-statistics] octave-statistics: binary-any FTBFS Added tag(s) pending. -- 1065548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065548 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1065548: marked as pending in octave-statistics
Control: tag -1 pending Hello, Bug #1065548 in octave-statistics reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/pkg-octave-team/octave-statistics/-/commit/88b9f5a665bd538b86385ab957c58179bfffcee6 d/rules: Instead of the execute_after_dh_installdeb target, use the -indep variant The commands in this rule are intended to be run on the files installed by the octave-statistics-common package and fail in arch:any builds. Closes: #1065548 Gbp-Dch: Full (this message was generated automatically) -- Greetings https://bugs.debian.org/1065548
Bug#1065585: linux-headers-6.7.7-amd64: Depends: linux-compiler-gcc-13-x86 -> linux-image-6.7.7-amd64, gcc-13 => uninstallable on x32
Control: severity -1 minor > Because this is an x32 host. x32 is multi-arch kernel only architecture. Debian still don't have proper support for multi-arch for compilers. Just use amd64. Bastian -- Bones: "The man's DEAD, Jim!"
Processed: Re: Bug#1065585: linux-headers-6.7.7-amd64: Depends: linux-compiler-gcc-13-x86 -> linux-image-6.7.7-amd64, gcc-13 => uninstallable on x32
Processing control commands: > severity -1 minor Bug #1065585 [src:linux] linux-headers-6.7.7-amd64: Depends: linux-compiler-gcc-13-x86 -> linux-image-6.7.7-amd64, gcc-13 => uninstallable on x32 Severity set to 'minor' from 'grave' -- 1065585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065585 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1065477: marked as done (owncloud-client: Uploads to unstable must have a higher version than present in unstable.)
Your message dated Fri, 08 Mar 2024 18:21:20 +0100 with message-id <87bk7o63k2@daath.cgg.com> and subject line Re: [Pkg-owncloud-maintainers] Bug#1065477: owncloud-client: Uploads to unstable must have a higher version than present in unstable. has caused the Debian Bug report #1065477, regarding owncloud-client: Uploads to unstable must have a higher version than present in unstable. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1065477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065477 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: owncloud-client Version: 4.2.0.11670+dfsg-1.1 Severity: serious Tags: ftbfs X-Debbugs-Cc: sramac...@debian.org Version check failed: Your upload included the binary package dolphin-owncloud, version 4.2.0.11670+dfsg-1.1, for amd64, however unstable already has version 5.0.0-1+b1. Uploads to unstable must have a higher version than present in unstable. Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Sebastian Ramacher wrote on 05/03/2024 at 21:52:44+0100: > On 2024-03-05 16:01:10 +0100, Sebastian Ramacher wrote: >> Hi >> >> On 2024-03-05 15:42:49 +0100, Pierre-Elliott Bécue wrote: >> > Hello, >> > >> > Sebastian Ramacher wrote on 05/03/2024 at >> > 09:38:13+0100: >> > >> > > Source: owncloud-client >> > > Version: 4.2.0.11670+dfsg-1.1 >> > > Severity: serious >> > > Tags: ftbfs >> > > X-Debbugs-Cc: sramac...@debian.org >> > > >> > > Version check failed: >> > > Your upload included the binary package dolphin-owncloud, version >> > > 4.2.0.11670+dfsg-1.1, for amd64, >> > > however unstable already has version 5.0.0-1+b1. >> > > Uploads to unstable must have a higher version than present in unstable. >> > > >> > > Cheers >> > >> > owncloud-client has been uploaded far before in the past, and was >> > shipping dolphin-owncloud, nautilus-owncloud, et al. >> > >> > In client v5, upstream removed these packages from the owncloud-client >> > source, and therefore they're now packaged through dedicated source >> > packages. >> > >> > These ones are the latest uploads. >> > >> > I'll upload the v5 version of owncloud-client source package which won't >> > ship dolphin-owncloud et al anymore. >> > >> > It's what's been suggested to me, and therefore I can't see a bug here. >> > >> > Could you give me a bit more intel aobut why this would be a serious >> > bug? >> >> The uploads by the buidds fail to be included in the archive since the >> constraints are not satisfied. You can check the reject files for the >> changes files from owncloud-client on coccia.d.o. >> >> You can also see on >> https://buildd.debian.org/status/package.php?p=owncloud-client=sid >> that the package is stuck in Uploaded state due to this issue. > > FWIW, the dolphin-owncloud binary package is provided with a higher > version number by owncloud-client-desktop-shell-integration-dolphin. I > suppose the dolphin-owncloud package can just be dropped from > owncloud-client. > > Cheers Yes, actually the root cause is the upload of T64 libs due to the t64 transition. So a reupload of owncloud-client has been made inappropriately, conflicting with my changes in experimental. I've made my experimental-to-unstable upload for owncloud-client. I'll see whether I can redo an upload for t64 variants. Thanks, -- PEB signature.asc Description: PGP signature --- End Message ---
Bug#1060318: This is a regression: it used to pass with PoCL3.1
Platform Name Portable Computing Language Platform Vendor The pocl project Platform VersionOpenCL 3.0 PoCL 3.1+debian Linux, None+Asserts, RELOC, SPIR, LLVM 15.0.6, SLEEF, DISTRO, POCL_DEBUG Platform ProfileFULL_PROFILE
Processed: severity of 1061102 is important
Processing commands for cont...@bugs.debian.org: > severity 1061102 important Bug #1061102 [librust-tikv-jemalloc-sys-dev] librust-tikv-jemalloc-sys-dev: fails to compile without xsltproc Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 1061102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061102 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1065666: Compiz 0.8.18 appears to be broken in testing
Not sure if this helps, but I keep package lists of each build. Here is a diff of 2/24 build (works) vs 3/24 (broken). https://spins.tuxfamily.org/package-list-diff.txt I dont know if any changes would break compiz, but at least its more info. Jim On 3/6/24 11:25, Steve Langasek wrote: On Wed, Mar 06, 2024 at 06:19:48PM +0100, Colomban Wendling wrote: Le 06/03/2024 à 17:31, Steve Langasek a écrit : On Wed, Mar 06, 2024 at 03:46:41PM +0100, Colomban Wendling wrote: Anyway, I'm CCing Steve (who did the unstable NMU) and Samuel in case they have extra clues. The only change in the NMU was to rename the libdecoration0 package to libdecoration0t64 for the 64-bit time_t transition. Unless this managed to break the *contents* of that package (i.e. the library has gone missing), this should not have had any effect on the behavior of compiz. So the package has not been rebuilt with different flags or anything? Not *deliberately* as part of this upload. The only change to flags should be on 32-bit architectures, excluding i386. I have assumed you are not trying to run compiz on one of these archs! But the toolchain also evolves over time, so this could certainly be a misbuild due to underlying changes. Anyway, I hardly expect this to be an issue, I just wanted to eliminate the only Compiz-side change that happened in the last months.
Bug#1065666: Compiz 0.8.18 appears to be broken in testing
Hi This address is listed as a maintainer on the Compiz package search page. 0.8.18 black screens on boot after a recent update when building a iso with livebuild. I have been building the xfce-Compiz iso for about 4 months without issue. The xfce (testing amd64) iso is built without errors, but it is unusable with the black screen. Rebuilding the source package does not fix it. I cant seem to get any more info with the black screen, ctrl+alt+F(any number) stays a black screen and booting into safe mode also results in a black screen. Xfce images without compiz build and work fine. Thanks Jim
Bug#1065666: Compiz 0.8.18 appears to be broken in testing
Hello James, Unfortunately I can't test this for the moment, but: Le 06/03/2024 à 15:03, James Bielefeldt a écrit : This address is listed as a maintainer on the Compiz package search page. 0.8.18 black screens on boot after a recent update when building a iso with livebuild. I have been building the xfce-Compiz iso for about 4 months without issue. The xfce (testing amd64) iso is built without errors, but it is unusable with the black screen. Rebuilding the source package does not fix it. Are you sure you're not using unstable? FWIW, there's no recent changes to the Compiz packages in testing, last ones were from about a year ago. However, there's a large transition currently happening in unstable, which affects Compiz as well. Maybe it could have an unknown side effect you're seeing? I cant seem to get any more info with the black screen, ctrl+alt+F(any number) stays a black screen and booting into safe mode also results in a black screen. Xfce images without compiz build and work fine. Maybe you could try SSHing to the machine to gather more data? Or possibly access the logs any other way? It could possibly be fairly unrelated to Compiz itself, but rather something else in the graphic stack (OpenGL? so maybe mesa, the kernel or something?) that affects Compiz more than others? Anyway, I'm CCing Steve (who did the unstable NMU) and Samuel in case they have extra clues. Note that you probably should report a bug, although it's understandably harder with scarce data to reference. Regards, Colomban
Bug#1065666: Compiz 0.8.18 appears to be broken in testing
Le 06/03/2024 à 16:59, James Bielefeldt a écrit : I am using testing. I create Debian spins that are rolling release based on testing. it's the same package in standard testing and unstable to my knowledge. Unstable recently got 2:0.8.18-5.1 -- yet as Steve said, it should not affect anything. they all have the same version number. The package is also seriously outdated. Compiz is at 9.14 but the package is 8 point something. Well, yes and no. Compiz is a complicated beast, and version 0.9 is a C++ rewrite by Ubuntu, that is now basically unmaintained. Compiz 0.8, also known as "compiz reloaded", is the pre-Ubuntu rewrite and has been continued separately. Effectively nowadays it's 2 different (yet similar) software, and 0.9 is mostly discontinued, and 0.8 is maintained albeit not seeing muhc activity lately. I tried to build it from the Ubuntu sources, but they errored out and are beyond me. My main thing is themeing and polishing the desktop. I do have a live build script if you want it. Just not sure how I'd get it to you. I don't think I'd have the time to dive this deep, and it would help immensely if you could try and gather some more information as to why Compiz is having issues. Logs from the kernel, X and the Xfce sessions are likely the most interesting bits where you might find more information to pinpoint the issue. Failing that, one interesting thing you could possibly attempt is to see whether an image with the exact same set of packages work fine if you don't *run* Compiz. Basically build the Compiz image, and simply adjust the configuration not to run it (but use e.g. xfwm4). You could also try and play with the Compiz plugins and configuration to see if one in particular is at fault, or if it's the core itself. Regards, Colomban
Bug#1065666: Compiz 0.8.18 appears to be broken in testing
Le 06/03/2024 à 17:31, Steve Langasek a écrit : On Wed, Mar 06, 2024 at 03:46:41PM +0100, Colomban Wendling wrote: Anyway, I'm CCing Steve (who did the unstable NMU) and Samuel in case they have extra clues. The only change in the NMU was to rename the libdecoration0 package to libdecoration0t64 for the 64-bit time_t transition. Unless this managed to break the *contents* of that package (i.e. the library has gone missing), this should not have had any effect on the behavior of compiz. So the package has not been rebuilt with different flags or anything? Anyway, I hardly expect this to be an issue, I just wanted to eliminate the only Compiz-side change that happened in the last months. Colomban
Bug#1065666: Compiz 0.8.18 appears to be broken in testing
On Wed, Mar 06, 2024 at 06:19:48PM +0100, Colomban Wendling wrote: > Le 06/03/2024 à 17:31, Steve Langasek a écrit : > > On Wed, Mar 06, 2024 at 03:46:41PM +0100, Colomban Wendling wrote: > > > Anyway, I'm CCing Steve (who did the unstable NMU) and Samuel in case they > > > have extra clues. > > The only change in the NMU was to rename the libdecoration0 package to > > libdecoration0t64 for the 64-bit time_t transition. Unless this managed to > > break the *contents* of that package (i.e. the library has gone missing), > > this should not have had any effect on the behavior of compiz. > So the package has not been rebuilt with different flags or anything? Not *deliberately* as part of this upload. The only change to flags should be on 32-bit architectures, excluding i386. I have assumed you are not trying to run compiz on one of these archs! But the toolchain also evolves over time, so this could certainly be a misbuild due to underlying changes. > Anyway, I hardly expect this to be an issue, I just wanted to eliminate the > only Compiz-side change that happened in the last months. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Bug#1065666: Compiz 0.8.18 appears to be broken in testing
On Wed, Mar 06, 2024 at 03:46:41PM +0100, Colomban Wendling wrote: > Anyway, I'm CCing Steve (who did the unstable NMU) and Samuel in case they > have extra clues. The only change in the NMU was to rename the libdecoration0 package to libdecoration0t64 for the 64-bit time_t transition. Unless this managed to break the *contents* of that package (i.e. the library has gone missing), this should not have had any effect on the behavior of compiz. > Note that you probably should report a bug, although it's understandably > harder with scarce data to reference. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Processed: fix ftbfs bug metadata
Processing commands for cont...@bugs.debian.org: > # reassign from binary to source > reassign 1065214 src:iproute2 Bug #1065214 [iproute2] iproute2: recent libc6-dev change causes the RPC support to be dropped Bug reassigned from package 'iproute2' to 'src:iproute2'. No longer marked as found in versions iproute2/6.7.0-2. Ignoring request to alter fixed versions of bug #1065214 to the same values previously set > # restore found version after reassign > found 1065214 iproute2/6.7.0-2 Bug #1065214 [src:iproute2] iproute2: recent libc6-dev change causes the RPC support to be dropped Marked as found in versions iproute2/6.7.0-2. > # reassign from binary to source > reassign 1065184 src:xwayland Bug #1065184 [xwayland] xwayland: missing build-dep on libtirpc-dev Bug reassigned from package 'xwayland' to 'src:xwayland'. No longer marked as found in versions xwayland/2:23.2.4-1. Ignoring request to alter fixed versions of bug #1065184 to the same values previously set > # restore found version after reassign > found 1065184 xwayland/2:23.2.4-1 Bug #1065184 [src:xwayland] xwayland: missing build-dep on libtirpc-dev Marked as found in versions xwayland/2:23.2.4-1. > # reassign from binary to source > reassign 1064128 src:liquidsoap Bug #1064128 [liquidsoap] liquidsoap: FTBFS: Error: Unbound module Pcre Bug reassigned from package 'liquidsoap' to 'src:liquidsoap'. No longer marked as found in versions liquidsoap/2.2.3-1. Ignoring request to alter fixed versions of bug #1064128 to the same values previously set > # restore found version after reassign > found 1064128 liquidsoap/2.2.3-1 Bug #1064128 [src:liquidsoap] liquidsoap: FTBFS: Error: Unbound module Pcre Marked as found in versions liquidsoap/2.2.3-1. > # reassign from binary to source > reassign 1051985 src:php-laravel-framework Bug #1051985 [php-laravel-framework] php-laravel-framework: Uninstallable with symfony 6: unsatisfiable dependencies Bug reassigned from package 'php-laravel-framework' to 'src:php-laravel-framework'. No longer marked as found in versions php-laravel-framework/8.83.26+dfsg-2. Ignoring request to alter fixed versions of bug #1051985 to the same values previously set > # restore found version after reassign > found 1051985 php-laravel-framework/8.83.26+dfsg-2 Bug #1051985 [src:php-laravel-framework] php-laravel-framework: Uninstallable with symfony 6: unsatisfiable dependencies Marked as found in versions php-laravel-framework/8.83.26+dfsg-2. > # change affects from binary to source > affects 1020160 - paredit-everywhere markdown-toc-el elisp-refs use-package > emacs-webserver ebib emacs-websocket seq-el package-lint-el emacs-web-server > elfeed Bug #1020160 [dh-elpa] emacs-helm-ag: FTBFS: make: *** [debian/rules:4: build] Error 25 Removed indication that 1020160 affects paredit-everywhere, markdown-toc-el, elisp-refs, use-package, emacs-webserver, ebib, emacs-websocket, seq-el, package-lint-el, emacs-web-server, and elfeed > affects 1020160 + src:paredit-everywhere src:markdown-toc-el src:elisp-refs > src:use-package src:emacs-webserver src:ebib src:emacs-websocket src:seq-el > src:package-lint-el src:emacs-web-server src:elfeed Bug #1020160 [dh-elpa] emacs-helm-ag: FTBFS: make: *** [debian/rules:4: build] Error 25 Added indication that 1020160 affects src:paredit-everywhere, src:markdown-toc-el, src:elisp-refs, src:use-package, src:emacs-webserver, src:ebib, src:emacs-websocket, src:seq-el, src:package-lint-el, src:emacs-web-server, and src:elfeed > # change affects from binary to source > affects 1020185 - markdown-toc-el ebib package-lint-el seq-el elisp-refs > emacs-websocket elfeed use-package paredit-everywhere Bug #1020185 [dh-elpa] emacs-web-server: FTBFS: make: *** [debian/rules:4: binary] Error 25 Removed indication that 1020185 affects markdown-toc-el, ebib, package-lint-el, seq-el, elisp-refs, emacs-websocket, elfeed, use-package, and paredit-everywhere > affects 1020185 + src:markdown-toc-el src:ebib src:package-lint-el src:seq-el > src:elisp-refs src:emacs-websocket src:elfeed src:use-package > src:paredit-everywhere Bug #1020185 [dh-elpa] emacs-web-server: FTBFS: make: *** [debian/rules:4: binary] Error 25 Added indication that 1020185 affects src:markdown-toc-el, src:ebib, src:package-lint-el, src:seq-el, src:elisp-refs, src:emacs-websocket, src:elfeed, src:use-package, and src:paredit-everywhere > # reassign from binary to source > reassign 1014512 src:freeipa Bug #1014512 [freeipa] freeipa: FTBFS: AttributeError: module 'collections' has no attribute 'Iterable' Bug reassigned from package 'freeipa' to 'src:freeipa'. No longer marked as found in versions 4.9.8-1+exp1. Ignoring request to alter fixed versions of bug #1014512 to the same values previously set > # restore found version after reassign > found 1014512 freeipa/4.9.8-1+exp1 Bug #1014512 [src:freeipa] freeipa: FTBFS: AttributeError: module 'collections' has no attribute 'Iterable' Marked as found in versions
Bug#1065666: mesa: Upgrading to mesa from testing breaks compiz
Source: mesa Version: 23.3.5-1 Severity: serious Tags: a11y Justification: breaks compiz Hello, When upgrading mesa to the version from testing, compiz does not start any more. I tried both upgrading only mesa (and deps), as well as mesa and the rest of the system, with the same result. compiz gets stuck here: #0 0x7f15fadefa80 in __GI___poll (fds=fds@entry=0x7ffc95974370, nfds=nfds@entry=1, timeout=timeout@entry=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f15facd94d3 in poll (__timeout=-1, __nfds=1, __fds=0x7ffc95974370) at /usr/include/x86_64-linux-gnu/bits/poll2.h:47 #2 read_block (len=8, buf=0x56080e7564e0, fd=4) at ../../src/xcb_in.c:394 #3 _xcb_in_read_block (c=c@entry=0x56080e75ebb0, buf=0x56080e7564e0, len=len@entry=8) at ../../src/xcb_in.c:1087 #4 0x7f15facd6b56 in read_setup (c=0x56080e75ebb0) at ../../src/xcb_conn.c:180 #5 xcb_connect_to_fd (fd=fd@entry=4, auth_info=auth_info@entry=0x7ffc959744b0) at ../../src/xcb_conn.c:384 #6 0x7f15facdb192 in xcb_connect_to_display_with_auth_info (displayname=displayname@entry=0x0, auth=auth@entry=0x0, screenp=screenp@entry=0x7ffc959745ac) at ../../src/xcb_util.c:536 #7 0x7f15facdb30a in xcb_connect (displayname=displayname@entry=0x0, screenp=screenp@entry=0x7ffc959745ac) at ../../src/xcb_util.c:493 #8 0x7f15f83081cd in device_select_find_xcb_pci_default (devices=devices@entry=0x56080e7564c0, device_count=device_count@entry=1) at ../src/vulkan/device-select-layer/device_select_x11.c:72 #9 0x7f15f8307cfb in get_default_device (expose_only_one_dev=, pPhysicalDevices=, physical_device_count=1, selection=, info=) at ../src/vulkan/device-select-layer/device_select_layer.c:498 #10 device_select_EnumeratePhysicalDevices (instance=, pPhysicalDeviceCount=0x7ffc95974740, pPhysicalDevices=0x7ffc95974760) at ../src/vulkan/device-select-layer/device_select_layer.c:594 #11 0x7f15f8350a9c in vkEnumeratePhysicalDevices () from /lib/x86_64-linux-gnu/libvulkan.so.1 #12 0x7f15f64aa37e in choose_pdev (dev_minor=-1, dev_major=-1, screen=0x56080e732cc0) at ../src/gallium/drivers/zink/zink_screen.c:1637 #13 zink_internal_create_screen (config=, dev_major=dev_major@entry=-1, dev_minor=dev_minor@entry=-1) at ../src/gallium/drivers/zink/zink_screen.c:3210 #14 0x7f15f64ab73e in zink_create_screen (winsys=, config=) at ../src/gallium/drivers/zink/zink_screen.c:3557 #15 0x7f15f611a2d5 in pipe_loader_sw_create_screen (dev=, config=, sw_vk=) at ../src/gallium/auxiliary/pipe-loader/pipe_loader_sw.c:426 #16 0x7f15f611a218 in pipe_loader_create_screen_vk (dev=0x56080e72ce20, sw_vk=sw_vk@entry=false) at ../src/gallium/auxiliary/pipe-loader/pipe_loader.c:184 #17 0x7f15f611a24b in pipe_loader_create_screen (dev=) at ../src/gallium/auxiliary/pipe-loader/pipe_loader.c:190 #18 0x7f15f5ab6c2e in kopper_init_screen (screen=0x56080e729360) at ../src/gallium/frontends/dri/kopper.c:134 #19 0x7f15f5abb6dc in driCreateNewScreen2 (scrn=0, fd=-1, loader_extensions=0x7f15fa8e47e0 , driver_extensions=, driver_configs=0x7ffc95975370, data=0x56080e696910) at ../src/gallium/frontends/dri/dri_util.c:139 #20 0x7f15fa8a3523 in driswCreateScreenDriver (screen=0, priv=0x56080e694430, driver=0x7f15fa8cc31b "zink") at ../src/glx/drisw_glx.c:979 #21 0x7f15fa8a8401 in AllocAndFetchScreenConfigs (dpy=dpy@entry=0x56080e3c0270, priv=priv@entry=0x56080e694430, zink=zink@entry=1) at ../src/glx/glxext.c:798 #22 0x7f15fa8a9385 in __glXInitialize (dpy=dpy@entry=0x56080e3c0270) at ../src/glx/glxext.c:928 #23 0x7f15fa8a61d6 in GetGLXPrivScreenConfig (ppsc=, ppriv=, scrn=0, dpy=0x56080e3c0270) at ../src/glx/glxcmds.c:147 #24 glXGetConfig (dpy=0x56080e3c0270, vis=0x56080e676820, attribute=1, value_return=0x7ffc959754ec) at ../src/glx/glxcmds.c:722 #25 0x56080c4764e2 in addScreen (display=display@entry=0x56080e3beef0, screenNum=screenNum@entry=0, wmSnSelectionWindow=wmSnSelectionWindow@entry=6291457, wmSnAtom=wmSnAtom@entry=436, wmSnTimestamp=wmSnTimestamp@entry=244386) at ./src/screen.c:1984 #26 0x56080c471407 in addDisplay (name=name@entry=0x0) at ./src/display.c:2755 #27 0x56080c46b8e2 in main (argc=, argv=0x7ffc95976278) at ./src/main.c:519 (gdb) info thread Id Target Id Frame * 1Thread 0x7f15fac147c0 (LWP 1034) "compiz" 0x7f15fadefa80 in __GI___poll (fds=fds@entry=0x7ffc95974370, nfds=nfds@entry=1, timeout=timeout@entry=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 (I'll bounce to this bts the original report from a compiz user) Samuel -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'unreleased'), (500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500,
Bug#1053195: marked as done (Please remove librados-dev build-depends on all 32 bits arch)
Your message dated Fri, 8 Mar 2024 15:58:36 +0100 with message-id <387c5292-0471-4d8b-9de8-b4fbb8aed...@uni-mainz.de> and subject line Re: Bug#1053195: Please remove librados-dev build-depends on all 32 bits arch has caused the Debian Bug report #1053195, regarding Please remove librados-dev build-depends on all 32 bits arch to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1053195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053195 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nfs-ganesha Version: 4.3-2 Severity: important Hi, I'd like to remove 32 bits support from Ceph, because upstream makes some 64 bits assumptions a bit everywhere, because it's not tested in upstream CI, and because it is increasingly difficult to build Ceph on a smaller addressing footprint (we used to have many tricks to reduce the build footprint that isn't sustainable in the long run). So please remove librados-dev in build-depends of your package for all 32 bits arch, and remove Ceph support in all 32 bits binaries. I'll upload Ceph with Build-Depends: architecture-is-64-bit as soon as this is done for the affected packages: - fio - libvirt - tcmu - qemu - eckit - fdb - nfs-ganesha - uwsgi - xrootd Cheers, Thomas Goirand (zigo) --- End Message --- --- Begin Message --- Version: 4.3-8 The bug was fixes in Version 4.3-8 which was released on Mon, 30 Oct 2023 Christoph OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#1060318: silx: autopkgtest failure with Python 3.12
In order to reproduce the bug, install python3-silx 2.0.0+dfsg-1 python3-pytest-xvfb pocl-opencl-icd then $ pytest --pyargs silx.image.test.test_medianfilter -v === test session starts === platform linux -- Python 3.11.8, pytest-8.0.2, pluggy-1.4.0 -- /usr/bin/python3 cachedir: .pytest_cache rootdir: /home/picca/debian/science-team/pyvkfft plugins: anyio-4.2.0, dials-data-2.4.0, xvfb-3.0.0 collected 2 items ::TestMedianFilterEngines::testCppMedFilt2d PASSED [ 50%] ::TestMedianFilterEngines::testOpenCLMedFilt2d Abandon the OpenCL test fails
Bug#1065183: marked as done (python-fsquota: missing build-dep on libtirpc-dev)
Your message dated Fri, 08 Mar 2024 13:59:15 +
with message-id
and subject line Bug#1065183: fixed in python-fsquota 0.1.0+dfsg1-5
has caused the Debian Bug report #1065183,
regarding python-fsquota: missing build-dep on libtirpc-dev
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1065183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-fsquota
Version: 0.1.0+dfsg1-4
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
User: debian-gl...@lists.debian.org
Usertags: libtirpc-dev
Dear maintainer,
Starting with glibc 2.31, support for NIS (libnsl library) has been
moved to a separate libnsl2 package. In order to allow a smooth
transition, a libnsl-dev, which depends on libtirpc-dev, has been added
to the libc6-dev package.
The libnsl-dev dependency has been temporarily dropped in the 2.37-15.1
NMU, as part of the 64-bit time_t transition. This causes python-fsquota
to FTBFS in sid with:
|dh_auto_configure -O--buildsystem=pybuild
| pybuild --configure -i python{version} -p 3.11
| I: pybuild base:305: python3.11 setup.py config
| Using hints/linux.h for myconfig.h
| WARNING: Header file /usr/include/rpc/rpc.h not present on this system.
| Likely compilation will fail. Recommend to either install package
| "libtirpc-dev", or disable RPC (network file system) support by
| adding the following switch to myconfig.h:
| #define NO_RPC
|
| running config
|dh_auto_build -O--buildsystem=pybuild
| pybuild --build -i python{version} -p 3.11
| I: pybuild base:305: /usr/bin/python3 setup.py build
| Using hints/linux.h for myconfig.h
| WARNING: Header file /usr/include/rpc/rpc.h not present on this system.
| Likely compilation will fail. Recommend to either install package
| "libtirpc-dev", or disable RPC (network file system) support by
| adding the following switch to myconfig.h:
| #define NO_RPC
|
| running build
| running build_ext
| building 'FsQuota' extension
| creating build
| creating build/temp.linux-x86_64-cpython-311
| creating build/temp.linux-x86_64-cpython-311/src
| x86_64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fcf-protection -g -fwrapv -O2 -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
-Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I. -I/usr/include/python3.11 -c
src/FsQuota.c -o build/temp.linux-x86_64-cpython-311/src/FsQuota.o
| In file included from src/FsQuota.c:18:
| ./myconfig.h:18:10: fatal error: rpc/rpc.h: No such file or directory
|18 | #include
| | ^~~
| compilation terminated.
| error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
| E: pybuild pybuild:391: build: plugin distutils failed with: exit code=1:
/usr/bin/python3 setup.py build
| dh_auto_build: error: pybuild --build -i python{version} -p 3.11 returned
exit code 13
| make: *** [debian/rules:9: binary] Error 25
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
2
This could be fixed by adding an explicit Build-Depends on libtirpc-dev.
The glibc change will likely be reverted in the short term, but given
its a change we want to do for Trixie, this will only lower the severity
of the bug.
Regards
Aurelien
--- End Message ---
--- Begin Message ---
Source: python-fsquota
Source-Version: 0.1.0+dfsg1-5
Done: Philipp Huebner
We believe that the bug you reported is fixed in the latest version of
python-fsquota, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Philipp Huebner (supplier of updated python-fsquota
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 08 Mar 2024 14:35:32 +0100
Source: python-fsquota
Architecture: source
Version: 0.1.0+dfsg1-5
Distribution: unstable
Processed: Bug#1065183 marked as pending in python-fsquota
Processing control commands: > tag -1 pending Bug #1065183 [src:python-fsquota] python-fsquota: missing build-dep on libtirpc-dev Added tag(s) pending. -- 1065183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1065183: marked as pending in python-fsquota
Control: tag -1 pending Hello, Bug #1065183 in python-fsquota reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-fsquota/-/commit/3dc5d640ab05fd347eb654cb9fba874a2eb05a9b add libtirpc-dev to Build-Depends (Closes: #1065183) (this message was generated automatically) -- Greetings https://bugs.debian.org/1065183
Bug#1065464: marked as done (tracker: 3.7 failing autopkgtest)
Your message dated Fri, 08 Mar 2024 13:27:58 + with message-id and subject line Bug#1065464: fixed in tracker 3.7~rc-3 has caused the Debian Bug report #1065464, regarding tracker: 3.7 failing autopkgtest to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1065464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065464 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tracker Version: 3.5.3-1 Severity: serious Tags: experimental Control: affects -1 src:tracker-miners I believe I have fixed all the blocking issues to update tracker and tracker-miners in Unstable except for its failing autopkgtest. Its autopkgtest has apparently been failing since at least 3.5.3. I am confused because the autopkgtest appears to be nearly identical to what is run during the build by dh_auto_test which does pass. https://ci.debian.net/packages/t/tracker/unstable/amd64/ https://salsa.debian.org/gnome-team/tracker/-/pipelines Thank you, Jeremy Bícha --- End Message --- --- Begin Message --- Source: tracker Source-Version: 3.7~rc-3 Done: Jeremy Bícha We believe that the bug you reported is fixed in the latest version of tracker, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bícha (supplier of updated tracker package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 08 Mar 2024 08:01:20 -0500 Source: tracker Built-For-Profiles: noudeb Architecture: source Version: 3.7~rc-3 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bícha Closes: 1035903 1061464 1065464 Changes: tracker (3.7~rc-3) unstable; urgency=medium . [ Helmut Grohne ] * Disable build tests when nocheck is set (Closes: #1061464) . [ Jeremy Bícha ] * Release to unstable (Closes: #1065464) . tracker (3.7~rc-2) experimental; urgency=medium . * debian/tests/unit-tests: - the autopkgtest are using the upstream buildtests which aren't installed tests. The tests setup isn't rebuilding the libraries but then LD_LIBRARY_PATH is forced by meson on a local path and not considering the system location, which means it doesn't fail the needed libraries. Workaround the problem by copying the system library to the local path in the unit-tests script. It's not ideal but the alternative of rebuilding the library would mean we wouldn't be testing the right binaries. . tracker (3.7~rc-1) experimental; urgency=medium . * New upstream release * Drop 3 patches applied in new release . tracker (3.7~beta-3) experimental; urgency=medium . * Add debian/salsa-ci.yml * Drop workaround patches for 32-bit build test issues and cherry-pick upstream's new fixes instead . tracker (3.7~beta-2) experimental; urgency=medium . * Revert a commit & 2 fixups that broke build tests on 32-bit (Closes: #1035903) . tracker (3.7~beta-1) experimental; urgency=medium . * New upstream release * debian/libtracker-sparql-3.0-0.symbols: Add new symbols * debian/tracker.install: Install additional binaries * debian/tracker.install: /usr/libexec/tracker-3 is no longer provided * Add/restore patch to use bash because of bashisms in scripts . tracker (3.6.0-1) experimental; urgency=medium . * New upstream release . tracker (3.6~rc-1) experimental; urgency=medium . * New upstream release . tracker (3.6~beta-1) experimental; urgency=medium . * New upstream release * Drop /usr/bin/env patch applied in new release * debian/libtracker-sparql-3.0-0.symbols: Add new symbol . tracker (3.5.3-1) experimental; urgency=medium . * New upstream release - Fix datetime issues for 32-bit architectures (Closes: #1035903) * Add patch to use full /usr/bin/env path instead of /bin/env . tracker (3.5.2-1) experimental; urgency=medium . * New upstream release * debian/control.in: Build-Depend on graphviz for docs build * debian/copyright: Add generated docs to Files-Excluded . tracker (3.5.1-1) experimental; urgency=medium . *
Bug#1061464: marked as done (tracker FTBFS with nocheck profile: ../meson.build:99:26: ERROR: python3 is missing modules: gi)
Your message dated Fri, 08 Mar 2024 13:27:58 + with message-id and subject line Bug#1061464: fixed in tracker 3.7~rc-3 has caused the Debian Bug report #1061464, regarding tracker FTBFS with nocheck profile: ../meson.build:99:26: ERROR: python3 is missing modules: gi to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1061464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061464 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tracker Version: 3.4.2-3 Severity: serious Tags: patch trixie sid tracker fails to build from source when built with the nocheck build profile. This is considered release-critical since the trixie release, but not earlier. The failure is: ../meson.build:99:26: ERROR: python3 is missing modules: gi The build system does not automatically disable building tests and thus fails. I'm attaching a patch for your convenience. Helmut diff --minimal -Nru tracker-3.4.2/debian/changelog tracker-3.4.2/debian/changelog --- tracker-3.4.2/debian/changelog 2023-06-27 18:09:03.0 +0200 +++ tracker-3.4.2/debian/changelog 2024-01-24 22:37:52.0 +0100 @@ -1,3 +1,10 @@ +tracker (3.4.2-3.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix nocheck FTBFS. (Closes: #-1) + + -- Helmut Grohne Wed, 24 Jan 2024 22:37:52 +0100 + tracker (3.4.2-3) unstable; urgency=medium [ Manuel A. Fernandez Montecelo ] diff --minimal -Nru tracker-3.4.2/debian/rules tracker-3.4.2/debian/rules --- tracker-3.4.2/debian/rules 2023-06-27 18:09:03.0 +0200 +++ tracker-3.4.2/debian/rules 2024-01-24 22:37:18.0 +0100 @@ -19,7 +19,8 @@ -Dbash_completion_dir=/usr/share/bash-completion/completions \ -Dsoup=soup3 \ -Dsystemd_user_services=true \ - -Dsystemd_user_services_dir=/usr/lib/systemd/user + -Dsystemd_user_services_dir=/usr/lib/systemd/user \ + -Dtests=$(if $(filter nocheck,$(DEB_BUILD_OPTIONS)),false,true) # Enforce tight shlibs dependencies override_dh_makeshlibs: --- End Message --- --- Begin Message --- Source: tracker Source-Version: 3.7~rc-3 Done: Jeremy Bícha We believe that the bug you reported is fixed in the latest version of tracker, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bícha (supplier of updated tracker package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 08 Mar 2024 08:01:20 -0500 Source: tracker Built-For-Profiles: noudeb Architecture: source Version: 3.7~rc-3 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bícha Closes: 1035903 1061464 1065464 Changes: tracker (3.7~rc-3) unstable; urgency=medium . [ Helmut Grohne ] * Disable build tests when nocheck is set (Closes: #1061464) . [ Jeremy Bícha ] * Release to unstable (Closes: #1065464) . tracker (3.7~rc-2) experimental; urgency=medium . * debian/tests/unit-tests: - the autopkgtest are using the upstream buildtests which aren't installed tests. The tests setup isn't rebuilding the libraries but then LD_LIBRARY_PATH is forced by meson on a local path and not considering the system location, which means it doesn't fail the needed libraries. Workaround the problem by copying the system library to the local path in the unit-tests script. It's not ideal but the alternative of rebuilding the library would mean we wouldn't be testing the right binaries. . tracker (3.7~rc-1) experimental; urgency=medium . * New upstream release * Drop 3 patches applied in new release . tracker (3.7~beta-3) experimental; urgency=medium . * Add debian/salsa-ci.yml * Drop workaround patches for 32-bit build test issues and cherry-pick upstream's new fixes instead . tracker (3.7~beta-2) experimental; urgency=medium . * Revert a commit & 2 fixups that broke build tests on 32-bit (Closes: #1035903) . tracker (3.7~beta-1) experimental; urgency=medium . * New upstream
Bug#1035903: marked as done (tracker: datetime build tests failing on 32-bit)
Your message dated Fri, 08 Mar 2024 13:27:58 + with message-id and subject line Bug#1035903: fixed in tracker 3.7~rc-3 has caused the Debian Bug report #1035903, regarding tracker: datetime build tests failing on 32-bit to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1035903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035903 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tracker Version: 3.5.0-1 Severity: serious Tags: ftbfs Forwarded: https://gitlab.gnome.org/GNOME/tracker/-/issues/398 Tracker build tests are failing on 32-bit architectures. See the upstream issue for more details. Thank you, Jeremy Bícha --- End Message --- --- Begin Message --- Source: tracker Source-Version: 3.7~rc-3 Done: Jeremy Bícha We believe that the bug you reported is fixed in the latest version of tracker, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1035...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bícha (supplier of updated tracker package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 08 Mar 2024 08:01:20 -0500 Source: tracker Built-For-Profiles: noudeb Architecture: source Version: 3.7~rc-3 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bícha Closes: 1035903 1061464 1065464 Changes: tracker (3.7~rc-3) unstable; urgency=medium . [ Helmut Grohne ] * Disable build tests when nocheck is set (Closes: #1061464) . [ Jeremy Bícha ] * Release to unstable (Closes: #1065464) . tracker (3.7~rc-2) experimental; urgency=medium . * debian/tests/unit-tests: - the autopkgtest are using the upstream buildtests which aren't installed tests. The tests setup isn't rebuilding the libraries but then LD_LIBRARY_PATH is forced by meson on a local path and not considering the system location, which means it doesn't fail the needed libraries. Workaround the problem by copying the system library to the local path in the unit-tests script. It's not ideal but the alternative of rebuilding the library would mean we wouldn't be testing the right binaries. . tracker (3.7~rc-1) experimental; urgency=medium . * New upstream release * Drop 3 patches applied in new release . tracker (3.7~beta-3) experimental; urgency=medium . * Add debian/salsa-ci.yml * Drop workaround patches for 32-bit build test issues and cherry-pick upstream's new fixes instead . tracker (3.7~beta-2) experimental; urgency=medium . * Revert a commit & 2 fixups that broke build tests on 32-bit (Closes: #1035903) . tracker (3.7~beta-1) experimental; urgency=medium . * New upstream release * debian/libtracker-sparql-3.0-0.symbols: Add new symbols * debian/tracker.install: Install additional binaries * debian/tracker.install: /usr/libexec/tracker-3 is no longer provided * Add/restore patch to use bash because of bashisms in scripts . tracker (3.6.0-1) experimental; urgency=medium . * New upstream release . tracker (3.6~rc-1) experimental; urgency=medium . * New upstream release . tracker (3.6~beta-1) experimental; urgency=medium . * New upstream release * Drop /usr/bin/env patch applied in new release * debian/libtracker-sparql-3.0-0.symbols: Add new symbol . tracker (3.5.3-1) experimental; urgency=medium . * New upstream release - Fix datetime issues for 32-bit architectures (Closes: #1035903) * Add patch to use full /usr/bin/env path instead of /bin/env . tracker (3.5.2-1) experimental; urgency=medium . * New upstream release * debian/control.in: Build-Depend on graphviz for docs build * debian/copyright: Add generated docs to Files-Excluded . tracker (3.5.1-1) experimental; urgency=medium . * New upstream release * Drop patch applied in new release * Add debian/upstream/metadata * Update renamed lintian tag names in lintian overrides * Update standards version to 4.6.2, no changes needed . tracker (3.5.0-1) experimental; urgency=medium . * New upstream release * Cherry-pick build test
Bug#1065460: uwsgi: the package fails to build from source due to missing 'plugins/rack_ruby32'
Hi, > The package fails to build in sid chroot with the following error: > > -- > *** uWSGI building and linking plugin plugins/rack_ruby32 *** > Error: unable to find directory 'plugins/rack_ruby32' > make: *** [debian/rules:429: debian/stamp-uwsgi-plugin-rack-ruby3.2] Error 1 > dpkg-buildpackage: error: debian/rules binary subprocess returned exit status > 2 > > Build finished at 2024-03-04T23:36:17Z There is something strange because the default ruby version in sid is 3.1 and uwsgi 2.0.24-2 builds just fine on my sid chroot, see below. Thanks, Alex -- UWSGICONFIG_RUBYPATH=/usr/bin/ruby3.1 \ CFLAGS="-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-z,relro" python3 uwsgiconfig.py -v --plugin plugins/rack debian/buildconf/uwsgi-plugin.ini rack_ruby31 using profile: debian/buildconf/uwsgi-plugin.ini detected include path: ['/usr/lib/gcc/x86_64-linux-gnu/13/include', '/usr/local/include', '/usr/include/x86_64-linux-gnu', '/usr/include'] *** uWSGI building and linking plugin plugins/rack *** x86_64-linux-gnu-gcc -fPIC -shared -o ./rack_ruby31_plugin.so -I. -O2 -I. -Wall -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Wformat-signedness -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wextra -Wno-unused-parameter -Wno-missing-field-initializers -DUWSGI_HAS_IFADDRS -DUWSGI_ZLIB -DUWSGI_LOCK_USE_MUTEX -DUWSGI_EVENT_USE_EPOLL -DUWSGI_EVENT_TIMER_USE_TIMERFD -DUWSGI_EVENT_FILEMONITOR_USE_INOTIFY -DUWSGI_PCRE2 -DUWSGI_ROUTING -DUWSGI_CAP -DUWSGI_UUID -DUWSGI_VERSION="\"2.0.24-debian\"" -DUWSGI_VERSION_BASE="2" -DUWSGI_VERSION_MAJOR="0" -DUWSGI_VERSION_MINOR="24" -DUWSGI_VERSION_REVISION="0" -DUWSGI_VERSION_CUSTOM="\"debian\"" -DUWSGI_YAML -DUWSGI_LIBYAML -I/usr/include/yajl -DUWSGI_JSON -DUWSGI_JSON_YAJL -DUWSGI_SSL -I/usr/include/libxml2 -DUWSGI_XML -DUWSGI_XML_LIBXML2 -DUWSGI_PLUGIN_DIR="\".\"" -g -O2 -ffile-prefix-map=BUILDDIR=. -fstack-protector-strong -fstack-clash-protection -fcf-protection -fPIC -DRUBY19 -DRUBY27 -I/usr/include/ruby-3.1.0 -I/usr/lib/x86_64-linux-gnu/ruby/3.1.0 -I/usr/lib/x86_64-linux-gnu/ruby/3.1.0/x86_64-linux-gnu -I/usr/include/ruby-3.1.0/x86_64-linux-gnu -I/usr/include/x86_64-linux-gnu/ruby-3.1.0 -Drack_plugin=rack_ruby31_plugin plugins/rack/rack_plugin.c plugins/rack/rack_api.c -Wl,-z,relro -L. -Wl,-z,now -fstack-protector-strong -rdynamic -Wl,-export-dynamic -Wl,--no-as-needed -L/usr/lib -lm -lruby-3.1 build time: 2 seconds *** rack_ruby31 plugin built and available in ./rack_ruby31_plugin.so *** touch debian/stamp-uwsgi-plugin-rack-ruby3.1
Processed: Bug#1061464 marked as pending in tracker
Processing control commands: > tag -1 pending Bug #1061464 [src:tracker] tracker FTBFS with nocheck profile: ../meson.build:99:26: ERROR: python3 is missing modules: gi Added tag(s) pending. -- 1061464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061464 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061464: marked as pending in tracker
Control: tag -1 pending Hello, Bug #1061464 in tracker reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/tracker/-/commit/4bd923df43496443a603008ba32a1f6a4f9ebf8a Disable build tests when nocheck is set Closes: #1061464 (this message was generated automatically) -- Greetings https://bugs.debian.org/1061464
Bug#1056429: marked as done (mystic's autopkg tests fail with Python 3.12)
Your message dated Fri, 8 Mar 2024 11:57:44 + with message-id and subject line Re: Bug#1056429: mystic's autopkg tests fail with Python 3.12 has caused the Debian Bug report #1056429, regarding mystic's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1056429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056429 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mystic Version: 0.4.1-1 Severity: important Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 [...] 364s Testing with python3.12: 375s ...Traceback (most recent call last): 375s File "/tmp/autopkgtest.glS7px/autopkgtest_tmp/tests/test_symbolic_abs.py", line 32, in 375s res = ms.simplify(eq_, all=True) 375s ^^ 375s File "/usr/lib/python3/dist-packages/mystic/symbolic.py", line 807, in simplify 375s cons = [simple(ci, **kwds) for ci in cons] if type(cons) is tuple else simple(cons, **kwds) 375s ^^ 375s File "/usr/lib/python3/dist-packages/mystic/symbolic.py", line 763, in _simplify 375s res = _simplify1(eqn, variables=variables, target=vars, **kwds) 375s ^ 375s File "/usr/lib/python3/dist-packages/mystic/symbolic.py", line 736, in _simplify1 375s if equals(before,after,next(testvals),**kwds): 375s^^ 375s File "/usr/lib/python3/dist-packages/mystic/symbolic.py", line 720, in _testvals 375s code = compile(code, '', 'exec') 375s^ 375s File "", line 1 375s (x0 - x1) = 0+0.007929281281520508 375s ^^^ 375s SyntaxError: cannot assign to expression here. Maybe you meant '==' instead of '='? 377s F-- 377s Ran 32 tests in 1.362s 377s 377s OK 377s .Traceback (most recent call last): 377s File "/tmp/autopkgtest.glS7px/autopkgtest_tmp/tests/test_symbolic.py", line 153, in 377s test_solve_constraint() 377s File "/tmp/autopkgtest.glS7px/autopkgtest_tmp/tests/test_symbolic.py", line 74, in test_solve_constraint 377s x = constraint([1.0, 2.0, 3.0]) 377s ^^^ 377s File "/usr/lib/python3/dist-packages/mystic/coupler.py", line 75, in func 377s return f(inner(x, *args, **kwds), *argz, **kwdz) 377s ^^^ 377s File "", line 4, in solver_140181050460160 377s File "", line 1 377s (x[1] - x[0]) - 1.0 = mean([x[0],x[1]]) 377s ^^^ 377s SyntaxError: cannot assign to expression here. Maybe you meant '==' instead of '='? 377s F-- --- End Message --- --- Begin Message --- Source: mystic Version: 0.4.2-1 On Wed, Nov 22, 2023 at 01:08:26PM +0100, Matthias Klose wrote: > Package: src:mystic > Version: 0.4.1-1 > Severity: important > Tags: sid trixie > User: debian-pyt...@lists.debian.org > Usertags: python3.12 > > > [...] > 364s Testing with python3.12: > 375s ...Traceback (most recent call last): > 375s File > "/tmp/autopkgtest.glS7px/autopkgtest_tmp/tests/test_symbolic_abs.py", line > 32, in > 375s res = ms.simplify(eq_, all=True) > 375s ^^ > 375s File "/usr/lib/python3/dist-packages/mystic/symbolic.py", line 807, > in simplify > 375s cons = [simple(ci, **kwds) for ci in cons] if type(cons) is tuple > else simple(cons, **kwds) > 375s ^^ > 375s File "/usr/lib/python3/dist-packages/mystic/symbolic.py", line 763, > in _simplify > 375s res = _simplify1(eqn, variables=variables, target=vars, **kwds) > 375s ^ > 375s File "/usr/lib/python3/dist-packages/mystic/symbolic.py", line 736, > in _simplify1 > 375s if equals(before,after,next(testvals),**kwds): > 375s^^ > 375s File "/usr/lib/python3/dist-packages/mystic/symbolic.py", line 720, > in _testvals > 375s code = compile(code, '', 'exec') > 375s^ > 375s File "", line 1 > 375s (x0 - x1) = 0+0.007929281281520508 > 375s ^^^ > 375s SyntaxError: cannot assign to expression here. Maybe you meant '==' > instead of '='? > 377s F-- > 377s Ran 32 tests in 1.362s > 377s > 377s OK > 377s .Traceback (most
Bug#1065662: FTBFS: error: aborting due to unexpected upstream changes
Source: ipywidgets Version: 8.1.1-4 Severity: serious Tags: ftbfs Justification: fails to build from source Rebuilding https://deb.debian.org/debian/pool/main/i/ipywidgets/ipywidgets_8.1.1-4.dsc in a clean sid chroot fails with error: aborting due to unexpected upstream changes -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.6.15-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1064697: flask-babelex: FTBFS: ImportError: cannot import name '_request_ctx_stack' from 'flask' (/usr/lib/python3/dist-packages/flask/__init__.py)
On Sun, Feb 25, 2024 at 08:37:09PM +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. [...] > > == > > ERROR: flask_babelex (unittest.loader._FailedTest.flask_babelex) > > -- > > ImportError: Failed to import test module: flask_babelex > > Traceback (most recent call last): > > File "/usr/lib/python3.12/unittest/loader.py", line 427, in > > _find_test_path > > package = self._get_module_from_name(name) > > > > File "/usr/lib/python3.12/unittest/loader.py", line 337, in > > _get_module_from_name > > __import__(name) > > File > > "/<>/.pybuild/cpython3_3.12_flask-babelex/build/flask_babelex/__init__.py", > > line 20, in > > from flask import _request_ctx_stack > > ImportError: cannot import name '_request_ctx_stack' from 'flask' > > (/usr/lib/python3/dist-packages/flask/__init__.py) https://github.com/mrjoes/flask-babelex is archived and shows a deprecation warning: "All Flask-BabelEx features were merged into Flask-Babel and Flask-BabelEx package should no longer be used in your projects. Please migrate." Apparently this was originally packaged as a dependency of pgadmin4, but pgadmin4 no longer uses it: https://github.com/pgadmin-org/pgadmin4/commit/d644b4f94ec71af78a46434121bce0fcd626a2dc Should we just remove this package from Debian? I'm CCing everyone who's uploaded it in the past just in case, but I suspect this is an easy decision. Thanks, -- Colin Watson (he/him) [cjwat...@debian.org]
Bug#1064773: marked as done (chemicaltagger: FTBFS: [ERROR] Plugin org.antlr:antlr4-maven-plugin:4.7.2 or one of its dependencies could not be resolved: Cannot access central (https://repo.maven.apach
Your message dated Fri, 08 Mar 2024 11:04:11 + with message-id and subject line Bug#1064773: fixed in chemicaltagger 1.6.2-3 has caused the Debian Bug report #1064773, regarding chemicaltagger: FTBFS: [ERROR] Plugin org.antlr:antlr4-maven-plugin:4.7.2 or one of its dependencies could not be resolved: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact org.antlr:antlr4-maven-plugin:jar:4.7.2 has not been downloaded from it before. -> [Help 1] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1064773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064773 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: chemicaltagger Version: 1.6.2-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240224 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > mh_patchpoms -plibchemicaltagger-java --debian-build --keep-pom-version > --maven-repo=/<>/debian/maven-repo >dh_auto_build > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > -Dproperties.file.manual=/<>/debian/maven.properties > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package > -DskipTests -Dnotimestamp=true -Dlocale=en_US > OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were > deprecated in JDK 13 and will likely be removed in a future release. > [INFO] Scanning for projects... > [INFO] > [INFO] --< uk.ac.cam.ch.wwmm:chemicalTagger > >-- > [INFO] Building chemicalTagger 1.6.2 > [INFO] [ jar > ]- > [WARNING] The POM for org.antlr:antlr4-maven-plugin:jar:4.7.2 is missing, no > dependency information available > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 0.105 s > [INFO] Finished at: 2024-02-24T22:51:03Z > [INFO] > > [ERROR] Plugin org.antlr:antlr4-maven-plugin:4.7.2 or one of its dependencies > could not be resolved: Cannot access central > (https://repo.maven.apache.org/maven2) in offline mode and the artifact > org.antlr:antlr4-maven-plugin:jar:4.7.2 has not been downloaded from it > before. -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException > dh_auto_build: error: /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > -Dproperties.file.manual=/<>/debian/maven.properties > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package > -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1 > make: *** [debian/rules:4: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2024/02/24/chemicaltagger_1.6.2-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240224;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240224=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a
Bug#1042679: quark-sphinx-theme: FTBFS with Sphinx 7.1, docutils 0.20: AssertionError: no elements
On Sun, Jul 30, 2023 at 08:29:35PM +0200, Lucas Nussbaum wrote:
> quark-sphinx-theme fails to build with Sphinx 7.1 and docutils 0.20, both of
> which
> are currently available in experimental.
A new upstream version 0.6.0 has been sitting in git since 2022, so I
wondered whether it fixed this. But instead it just has different
errors (see below).
I'm wondering whether we should just remove this package from Debian?
It has no reverse-dependencies, and
https://gitlab.com/fkrull/quark-sphinx-theme shows the project as
unmaintained and suggests that the errors below mean that it isn't
realistically compatible with modern Sphinx any more.
==
ERROR: setUpClass (test.test_html_rewrite.TestHTMLCompatOutput)
--
Traceback (most recent call last):
File
"/<>/.pybuild/cpython3_3.11_quark-sphinx-theme/build/test/util.py",
line 84, in setUpClass
run_sphinx(cls.source_dir, cls.build_dir, cls.builder, cls.config,
File
"/<>/.pybuild/cpython3_3.11_quark-sphinx-theme/build/test/util.py",
line 65, in run_sphinx
raise Exception('%s returned non-zero exit status %s\n'
Exception: ['-b', 'html', '-N', '-t', 'test_html_compat_alias',
'/<>/.pybuild/cpython3_3.11_quark-sphinx-theme/build/test/testdoc-html_rewrite',
'/tmp/tmp-sphinx-build-test-bo9lbres'] returned non-zero exit status 2
--- Output:
Running Sphinx v7.2.6
Configuration error:
HTML 4 is no longer supported by Sphinx. ("html4_writer=True" detected in
configuration options)
==
ERROR: setUpClass (test.test_html_rewrite.TestHTMLRewriteFeatures)
--
Traceback (most recent call last):
File
"/<>/.pybuild/cpython3_3.11_quark-sphinx-theme/build/test/util.py",
line 84, in setUpClass
run_sphinx(cls.source_dir, cls.build_dir, cls.builder, cls.config,
File
"/<>/.pybuild/cpython3_3.11_quark-sphinx-theme/build/test/util.py",
line 65, in run_sphinx
raise Exception('%s returned non-zero exit status %s\n'
Exception: ['-b', 'html', '-N', '-D', 'quark_html_features=',
'/<>/.pybuild/cpython3_3.11_quark-sphinx-theme/build/test/testdoc-html_rewrite',
'/tmp/tmp-sphinx-build-test-kjvqfnoy'] returned non-zero exit status 2
--- Output:
Running Sphinx v7.2.6
Configuration error:
HTML 4 is no longer supported by Sphinx. ("html4_writer=True" detected in
configuration options)
==
ERROR: setUpClass (test.test_html_rewrite.TestHTMLRewriteOutput)
--
Traceback (most recent call last):
File
"/<>/.pybuild/cpython3_3.11_quark-sphinx-theme/build/test/util.py",
line 84, in setUpClass
run_sphinx(cls.source_dir, cls.build_dir, cls.builder, cls.config,
File
"/<>/.pybuild/cpython3_3.11_quark-sphinx-theme/build/test/util.py",
line 65, in run_sphinx
raise Exception('%s returned non-zero exit status %s\n'
Exception: ['-b', 'html', '-N',
'/<>/.pybuild/cpython3_3.11_quark-sphinx-theme/build/test/testdoc-html_rewrite',
'/tmp/tmp-sphinx-build-test-pvyjfedf'] returned non-zero exit status 2
--- Output:
Running Sphinx v7.2.6
Configuration error:
HTML 4 is no longer supported by Sphinx. ("html4_writer=True" detected in
configuration options)
==
ERROR: setUpClass
(test.test_html_rewrite.TestHTMLRewriteOutputWithBuilderBasedOnQtHelpBuilder)
--
Traceback (most recent call last):
File
"/<>/.pybuild/cpython3_3.11_quark-sphinx-theme/build/test/util.py",
line 84, in setUpClass
run_sphinx(cls.source_dir, cls.build_dir, cls.builder, cls.config,
File
"/<>/.pybuild/cpython3_3.11_quark-sphinx-theme/build/test/util.py",
line 65, in run_sphinx
raise Exception('%s returned non-zero exit status %s\n'
Exception: ['-b', 'custom-qthelp', '-N',
'/<>/.pybuild/cpython3_3.11_quark-sphinx-theme/build/test/testdoc-html_rewrite',
'/tmp/tmp-sphinx-build-test-6joh0ezy'] returned non-zero exit status 2
--- Output:
Running Sphinx v7.2.6
Configuration error:
HTML 4 is no longer supported by Sphinx. ("html4_writer=True" detected in
configuration options)
==
ERROR: setUpClass
(test.test_html_rewrite.TestHTMLRewriteOutputWithQtHelpBuilder)
--
Traceback (most recent call last):
File
"/<>/.pybuild/cpython3_3.11_quark-sphinx-theme/build/test/util.py",
line 84, in setUpClass
run_sphinx(cls.source_dir, cls.build_dir, cls.builder, cls.config,
File
"/<>/.pybuild/cpython3_3.11_quark-sphinx-theme/build/test/util.py",
line 65, in run_sphinx
raise Exception('%s returned
Bug#1035516: php-smbclient broke with samba 4.17.5
Dear maintainers, On Thu, 04 May 2023 16:23:10 +0200 Alan Krempler wrote: > Package: php-smbclient > Version: 1.0.6-8 > Severity: grave > Justification: renders package unusable > > php-smbclient does not work with samba versions 4.17.5 and above: > https://github.com/eduardok/libsmbclient-php/issues/98 > https://github.com/nextcloud/server/issues/367please upload 73 > > php-smbclient upstream version 1.1.1 fixes the issue. php-smbclient 1.1.1 has been released almost over a year ago. Could you update the package to this version in order to fix this issue and reintroduce php-smbclient into testing again? Thank you and kind regards, Dan smime.p7s Description: S/MIME cryptographic signature
Bug#1065654: mesa ftbfs with time_t64
On 08.03.24 11:00, Fabio Pedretti wrote: Already fixed upstream, the patch will be included since 24.0.3 (will be released in 5 days): https://cgit.freedesktop.org/mesa/mesa/commit/?h=staging/24.0=8ea039019761ecc25d49f075aef50de6e81db854 no, that commit is only fixing one occurrence. Il giorno ven 8 mar 2024 alle ore 10:27 Matthias Klose ha scritto: Package: src:mesa Version: 24.0.2-1 Severity: serious Tags: sid trixie patch mesa ftbfs with time_t64, patch attached. I didn't check if the _TIMET_BITS are used in the affected files. There's also a bug in the profile support. WINE cannot be built without LLVM, and therefore should be disabled. and that one needs to be fixed in the packaging.
Bug#1065654: mesa ftbfs with time_t64
Already fixed upstream, the patch will be included since 24.0.3 (will be released in 5 days): https://cgit.freedesktop.org/mesa/mesa/commit/?h=staging/24.0=8ea039019761ecc25d49f075aef50de6e81db854 Il giorno ven 8 mar 2024 alle ore 10:27 Matthias Klose ha scritto: > > Package: src:mesa > Version: 24.0.2-1 > Severity: serious > Tags: sid trixie patch > > mesa ftbfs with time_t64, patch attached. I didn't check if the > _TIMET_BITS are used in the affected files. > > There's also a bug in the profile support. WINE cannot be built without > LLVM, and therefore should be disabled.
Bug#1065654: mesa ftbfs with time_t64
Package: src:mesa
Version: 24.0.2-1
Severity: serious
Tags: sid trixie patch
mesa ftbfs with time_t64, patch attached. I didn't check if the
_TIMET_BITS are used in the affected files.
There's also a bug in the profile support. WINE cannot be built without
LLVM, and therefore should be disabled.reverted:
--- mesa-24.0.2/.pc/.quilt_patches
+++ mesa-24.0.2.orig/.pc/.quilt_patches
@@ -1 +0,0 @@
-patches
reverted:
--- mesa-24.0.2/.pc/.quilt_series
+++ mesa-24.0.2.orig/.pc/.quilt_series
@@ -1 +0,0 @@
-series
reverted:
--- mesa-24.0.2/.pc/.version
+++ mesa-24.0.2.orig/.pc/.version
@@ -1 +0,0 @@
-2
reverted:
--- mesa-24.0.2/.pc/applied-patches
+++ mesa-24.0.2.orig/.pc/applied-patches
@@ -1 +0,0 @@
-time64.diff
reverted:
--- mesa-24.0.2/.pc/time64.diff/src/drm-shim/drm_shim.c
+++ mesa-24.0.2.orig/.pc/time64.diff/src/drm-shim/drm_shim.c
@@ -1,836 +0,0 @@
-/*
- * Copyright © 2018 Broadcom
- *
- * Permission is hereby granted, free of charge, to any person obtaining a
- * copy of this software and associated documentation files (the "Software"),
- * to deal in the Software without restriction, including without limitation
- * the rights to use, copy, modify, merge, publish, distribute, sublicense,
- * and/or sell copies of the Software, and to permit persons to whom the
- * Software is furnished to do so, subject to the following conditions:
- *
- * The above copyright notice and this permission notice (including the next
- * paragraph) shall be included in all copies or substantial portions of the
- * Software.
- *
- * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
- * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
- * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
- * THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
- * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
- * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
- * DEALINGS IN THE SOFTWARE.
- */
-
-/**
- * @file
- *
- * Implements wrappers of libc functions to fake having a DRM device that
- * isn't actually present in the kernel.
- */
-
-/* Prevent glibc from defining open64 when we want to alias it. */
-#undef _FILE_OFFSET_BITS
-#define _LARGEFILE64_SOURCE
-
-#include
-#include
-#include
-#include
-#include
-#include
-#include
-#include
-#include
-#include
-#include
-#include
-#include
-#include
-#include
-
-#include "util/anon_file.h"
-#include "util/set.h"
-#include "util/simple_mtx.h"
-#include "util/u_debug.h"
-#include "drm_shim.h"
-
-#define REAL_FUNCTION_POINTER(x) __typeof__(x) *real_##x
-
-static simple_mtx_t shim_lock = SIMPLE_MTX_INITIALIZER;
-struct set *opendir_set;
-bool drm_shim_debug;
-
-/* If /dev/dri doesn't exist, we'll need an arbitrary pointer that wouldn't be
- * returned by any other opendir() call so we can return just our fake node.
- */
-DIR *fake_dev_dri = (void *)_set;
-
-REAL_FUNCTION_POINTER(close);
-REAL_FUNCTION_POINTER(closedir);
-REAL_FUNCTION_POINTER(dup);
-REAL_FUNCTION_POINTER(fcntl);
-REAL_FUNCTION_POINTER(fopen);
-REAL_FUNCTION_POINTER(ioctl);
-REAL_FUNCTION_POINTER(mmap);
-REAL_FUNCTION_POINTER(mmap64);
-REAL_FUNCTION_POINTER(open);
-REAL_FUNCTION_POINTER(opendir);
-REAL_FUNCTION_POINTER(readdir);
-REAL_FUNCTION_POINTER(readdir64);
-REAL_FUNCTION_POINTER(readlink);
-REAL_FUNCTION_POINTER(realpath);
-
-#define HAS_XSTAT __GLIBC__ == 2 && __GLIBC_MINOR__ < 33
-
-#if HAS_XSTAT
-REAL_FUNCTION_POINTER(__xstat);
-REAL_FUNCTION_POINTER(__xstat64);
-REAL_FUNCTION_POINTER(__fxstat);
-REAL_FUNCTION_POINTER(__fxstat64);
-#else
-REAL_FUNCTION_POINTER(stat);
-REAL_FUNCTION_POINTER(stat64);
-REAL_FUNCTION_POINTER(fstat);
-REAL_FUNCTION_POINTER(fstat64);
-#endif
-
-static char render_node_dir[] = "/dev/dri/";
-/* Full path of /dev/dri/renderD* */
-static char *render_node_path;
-/* renderD* */
-static char *render_node_dirent_name;
-/* /sys/dev/char/major: */
-static int drm_device_path_len;
-static char *drm_device_path;
-/* /sys/dev/char/major:minor/device */
-static int device_path_len;
-static char *device_path;
-/* /sys/dev/char/major:minor/device/subsystem */
-static char *subsystem_path;
-int render_node_minor = -1;
-
-struct file_override {
- const char *path;
- char *contents;
-};
-static struct file_override file_overrides[10];
-static int file_overrides_count;
-extern bool drm_shim_driver_prefers_first_render_node;
-
-static int
-nfvasprintf(char **restrict strp, const char *restrict fmt, va_list ap)
-{
- int ret = vasprintf(strp, fmt, ap);
- assert(ret >= 0);
- return ret;
-}
-
-static int
-nfasprintf(char **restrict strp, const char *restrict fmt, ...)
-{
- va_list ap;
- va_start(ap, fmt);
- int ret = nfvasprintf(strp, fmt, ap);
- va_end(ap);
- return ret;
-}
-
-/* Pick the minor and filename for our shimmed render node. This can be
- * either a new one that didn't exist on the system, or if the driver wants,
- * it can replace
Bug#1065501: marked as done (qgis FTBFS: FAILED: src/crssync/CMakeFiles/synccrsdb)
Your message dated Fri, 08 Mar 2024 08:51:12 + with message-id and subject line Bug#1065501: fixed in qgis 3.34.4+dfsg-4 has caused the Debian Bug report #1065501, regarding qgis FTBFS: FAILED: src/crssync/CMakeFiles/synccrsdb to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1065501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065501 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qgis Version: 3.34.4+dfsg-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=qgis=3.34.4%2Bdfsg-3 ... FAILED: src/crssync/CMakeFiles/synccrsdb /<>/debian/build/src/crssync/CMakeFiles/synccrsdb cd /<>/debian/build/src/crssync && /<>/debian/build/output/bin/crssync Could not execute: INSERT INTO tbl_srs(srs_id, description,projection_acronym,ellipsoid_acronym,parameters,srid,auth_name,auth_id,is_geo,deprecated,srs_type) VALUES (63561, 'MSL UK & Ireland VORF08 depth','','','+vunits=m +no_defs',520003561,'EPSG','10150',0,0,'Vertical') [UNIQUE constraint failed: tbl_srs.srs_id/UNIQUE constraint failed: tbl_srs.srs_id] Could not execute: INSERT INTO tbl_srs(srs_id, description,projection_acronym,ellipsoid_acronym,parameters,srid,auth_name,auth_id,is_geo,deprecated,srs_type) VALUES (63562, 'CD UK & Ireland VORF08 depth','','','+vunits=m +no_defs',520003562,'EPSG','10151',0,0,'Vertical') [UNIQUE constraint failed: tbl_srs.srs_id/UNIQUE constraint failed: tbl_srs.srs_id] Could not execute: INSERT INTO tbl_srs(srs_id, description,projection_acronym,ellipsoid_acronym,parameters,srid,auth_name,auth_id,is_geo,deprecated,srs_type) VALUES (63563, 'ETRS89 + MSL UK & Ireland VORF08 depth','longlat','longlat','+proj=longlat +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +vunits=m +no_defs',520003563,'EPSG','10156',0,0,'Compound') [UNIQUE constraint failed: tbl_srs.srs_id/UNIQUE constraint failed: tbl_srs.srs_id] Could not execute: INSERT INTO tbl_srs(srs_id, description,projection_acronym,ellipsoid_acronym,parameters,srid,auth_name,auth_id,is_geo,deprecated,srs_type) VALUES (63564, 'ETRS89 + CD UK & Ireland VORF08 depth','longlat','longlat','+proj=longlat +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +vunits=m +no_defs',520003564,'EPSG','10157',0,0,'Compound') [UNIQUE constraint failed: tbl_srs.srs_id/UNIQUE constraint failed: tbl_srs.srs_id] Could not execute: INSERT INTO tbl_srs(srs_id, description,projection_acronym,ellipsoid_acronym,parameters,srid,auth_name,auth_id,is_geo,deprecated,srs_type) VALUES (63565, 'S34J-IRF','longlat','longlat','+proj=longlat +ellps=intl +no_defs',520003565,'EPSG','10158',1,0,'Geographic2d') [UNIQUE constraint failed: tbl_srs.srs_id/UNIQUE constraint failed: tbl_srs.srs_id] Could not execute: INSERT INTO tbl_srs(srs_id, description,projection_acronym,ellipsoid_acronym,parameters,srid,auth_name,auth_id,is_geo,deprecated,srs_type) VALUES (63566, 'S34J reconstruction east-orientated','tmerc','tmerc','+proj=tmerc +lat_0=0 +lon_0=10.37 +k=1 +x_0=-210327 +y_0=-6034310 +ellps=intl +units=m +no_defs',520003566,'EPSG','10160',0,0,'Projected') [UNIQUE constraint failed: tbl_srs.srs_id/UNIQUE constraint failed: tbl_srs.srs_id] Could not execute: INSERT INTO tbl_srs(srs_id, description,projection_acronym,ellipsoid_acronym,parameters,srid,auth_name,auth_id,is_geo,deprecated,srs_type) VALUES (63567, 'JGD2011 / Japan Plane Rectangular CS I + JGD2011 (vertical) height','tmerc','tmerc','+proj=tmerc +lat_0=33 +lon_0=129.5 +k=0. +x_0=0 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +vunits=m +no_defs',520003567,'EPSG','10162',0,0,'Compound') [UNIQUE constraint failed: tbl_srs.srs_id/UNIQUE constraint failed: tbl_srs.srs_id] Could not execute: INSERT INTO tbl_srs(srs_id, description,projection_acronym,ellipsoid_acronym,parameters,srid,auth_name,auth_id,is_geo,deprecated,srs_type) VALUES (63568, 'JGD2011 / Japan Plane Rectangular CS II + JGD2011 (vertical) height','tmerc','tmerc','+proj=tmerc +lat_0=33 +lon_0=131 +k=0. +x_0=0 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +vunits=m +no_defs',520003568,'EPSG','10163',0,0,'Compound') [UNIQUE constraint failed: tbl_srs.srs_id/UNIQUE constraint failed: tbl_srs.srs_id] Could not execute: INSERT INTO tbl_srs(srs_id, description,projection_acronym,ellipsoid_acronym,parameters,srid,auth_name,auth_id,is_geo,deprecated,srs_type) VALUES (63569, 'JGD2011 / Japan Plane Rectangular CS III + JGD2011 (vertical) height','tmerc','tmerc','+proj=tmerc +lat_0=36 +lon_0=132.1667 +k=0. +x_0=0 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +vunits=m
Bug#1065373: fix heimdal build with abi=time64
Control: tags -1 -experimental Since heimdal failing to build from source has a significant impact on rebootstrapping the archive on 32-bit archs, I am going ahead and uploading a 0-day NMU for this issue with the patch provided by Matthias. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Processed: Re: fix heimdal build with abi=time64
Processing control commands: > tags -1 -experimental Bug #1065373 [src:heimdal] fix heimdal build with abi=time64 Removed tag(s) experimental. -- 1065373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065373 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
