Bug#1033780: marked as done (nvidia-graphics-drivers-tesla-470: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, C
Your message dated Sun, 09 Apr 2023 02:35:35 + with message-id and subject line Bug#1033780: fixed in nvidia-graphics-drivers-tesla-470 470.182.03-1 has caused the Debian Bug report #1033780, regarding nvidia-graphics-drivers-tesla-470: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 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.) -- 1033780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033780 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nvidia-graphics-drivers Severity: serious Tags: security upstream X-Debbugs-Cc: Debian Security Team Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6 Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: tag -2 + wontfix Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4 Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: tag -3 + wontfix Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1 Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: tag -4 + wontfix Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1 Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1 Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: tag -6 + wontfix Control: close -6 460.106.00-3 Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1 Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: reassign -8 src:nvidia-graphics-drivers-tesla-510 510.47.03-1 Control: retitle -8 nvidia-graphics-drivers-tesla-510: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0183, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: tag -8 + wontfix Control: close -8 510.85.02-2 Control: reassign -9 src:nvidia-graphics-drivers-tesla 510.85.02-1 Control: retitle -9 nvidia-graphics-drivers-tesla: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0183, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: found -9 515.48.07-1 Control: found -9 525.60.13-1 Control: reassign -10 src:nvidia-open-gpu-kernel-modules 515.43.04-1 Control: retitle -10 nvidia-open-gpu-kernel-modules: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0183, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: found -10 520.56.06-1 Control: found -10 525.85.12-1 Control: found -10 530.30.02-1 Control: found -1 340.24-1 Control: found -1 343.22-1 Control: found -1 396.18-1 Control: found -1 430.14-1 Control: found -1 455.23.04-1 Control: found -1 465.24.02-1 Control: found -1 495.44-1 Control: found -1 515.48.07-1 Control: found -1 520.56.06-1 Control: found -1 525.53-1 Control: found -1 530.30.02-1 Control: fixed -1 530.41.03-1 https://nvidia.custhelp.com/app/answers/detail/a_id/5452 CVE-2023-0189 NVIDIA GPU Display Driver for Linux contains a vulnerability in the kernel mode layer handler, which may lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering. CVE-2023-0184 NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the
Bug#1032104: linux: ppc64el iouring corrupted read
> > On Sat, Mar 18, 2023 at 11:19:29PM -0700, Otto Kekäläinen wrote: > > > Any updates on this one? > > > > > > I am still seeing the main.index_merge_innodb failure in > > > https://buildd.debian.org/status/fetch.php?pkg=mariadb=ppc64el=1%3A10.11.2-2%7Eexp1=1678728871=0 > > > and rebuild > > > https://buildd.debian.org/status/fetch.php?pkg=mariadb=ppc64el=1%3A10.11.2-2%7Eexp1=1679174850=0. > > > > > > Logs show: Kernel: Linux 5.10.0-21-powerpc64le #1 SMP Debian > > > 5.10.162-1 (2023-01-21) ppc64el (ppc64le) > > > > Remember that with the 5.10.162 upstream version the io_uring code was > > rebased to the 5.15-stable one. So it is likely, and it maches the > > verison ranges, that the regression was introduced with this > > particular changes. Ideally someone with access to the given > > architecture, can verify that the issue is gone with the current > > 5.10.175 upstream (where there were several followup fixes, in > > particular e.g. a similar one for s390x), and if not, reports the > > problem to upstream. > > > > Paul Gevers asked if the issues are gone as well with 6.1.12-1 > > (or later 6.1.y series versions, which will land in bookworm). That > > would be valuable information to know as well to exclude we do not > > have the issue as well in bookworm. > > Were you able to verify this? No, not yet. I have not done new uploads to experimental after the one I mentioned and linked above from March 18th. The builds for unstable are passing because I forced the tests to run with regular fsync instead of native I/O in https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/fc1358087b39ac6520420c7bbae2e536bc86748d. I will test this again later but right now I don't want to do any extra uploads as the package is pending unblock and inclusion in Bullseye (Bug#1033811) and I don't want one single minor issue to jeopardize getting fixes for multiple major issues forward.
Processed: Re: Bug#1034090: ibus: FTBFS twice in a row: src/ibusenumtypes.h is regenerated too late
Processing control commands: > tags -1 upstream Bug #1034090 [src:ibus] ibus: FTBFS twice in a row: src/ibusenumtypes.h is regenerated too late Added tag(s) upstream. > forwarded -1 https://github.com/ibus/ibus/issues/2501 Bug #1034090 [src:ibus] ibus: FTBFS twice in a row: src/ibusenumtypes.h is regenerated too late Set Bug forwarded-to-address to 'https://github.com/ibus/ibus/issues/2501'. -- 1034090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034090 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1034090: ibus: FTBFS twice in a row: src/ibusenumtypes.h is regenerated too late
Control: tags -1 upstream Control: forwarded -1 https://github.com/ibus/ibus/issues/2501 Thanks for your report! We use a pre-compiled, kind of, tarball as the upstream source: https://github.com/ibus/ibus/releases/download/1.5.28/ibus-1.5.28.tar.gz ibusenumtypes.h has already been generated in that tarball, which explains why it works the first time. The file is not present in the upstream git source (only the 8 years old src/ibusenumtypes.h.template file is). As an experiment I tried to build with the true source tarball, and then it failed already at the first attempt for the same reason. The behavior has been reported upstream, so let's await the outcome of the upstream issue. Btw, is "serious" an appropriate severity level for this bug? -- Rgds, Gunnar
Processed: missing dependency on python3-requests
Processing commands for cont...@bugs.debian.org: > severity 1002642 grave Bug #1002642 [cups-tea4cups] missing dependency on python3-requests Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1002642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1034059: marked as done (zstd-jni-java: FTBFS during binary-arch build: Plugin org.apache.maven.plugins:maven-resources-plugin:3.1.0 or one of its dependencies could not be resolved)
Your message dated Sat, 08 Apr 2023 21:33:59 + with message-id and subject line Bug#1034059: fixed in zstd-jni-java 1.5.4-2+ds-2 has caused the Debian Bug report #1034059, regarding zstd-jni-java: FTBFS during binary-arch build: Plugin org.apache.maven.plugins:maven-resources-plugin:3.1.0 or one of its dependencies could not be resolved 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.) -- 1034059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034059 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zstd-jni-java Version: 1.5.2-5+ds-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Control: found -1 1.5.4-2+ds-1 Hi, zstd-jni-java FTBFS during a binary-arch build (as it is done on the buildd network), while binary-indep and combined binary-arch and binary-indep builds succeed. Reproducible in bookworm, sid and experimental. ... dh_auto_build -a -O--buildsystem=maven /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=/build/zstd-jni-java-1.5.2-5\+ds -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/build/zstd-jni-java-1.5.2-5\+ds/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/build/zstd-jni-java-1.5.2-5\+ds/debian -Dmaven.repo.local=/build/zstd-jni-java-1.5.2-5\+ds/debian/maven-repo 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] -< com.github.luben:zstd-jni >-- [INFO] Building zstd-jni 1.5.2-5 [INFO] [ jar ]- [WARNING] The POM for org.apache.maven.plugins:maven-resources-plugin:jar:3.1.0 is missing, no dependency information available [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 0.093 s [INFO] Finished at: 2023-04-07T17:09:36Z [INFO] [ERROR] Plugin org.apache.maven.plugins:maven-resources-plugin:3.1.0 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.apache.maven.plugins:maven-resources-plugin:jar:3.1.0 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=/build/zstd-jni-java-1.5.2-5\+ds -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/build/zstd-jni-java-1.5.2-5\+ds/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/build/zstd-jni-java-1.5.2-5\+ds/debian -Dmaven.repo.local=/build/zstd-jni-java-1.5.2-5\+ds/debian/maven-repo package -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1 make: *** [debian/rules:8: binary-arch] Error 25 Note that maven-resources-plugin 3.3.0 was uploaded in December, i.e. after the last zstd-jni-java upload to sid in November. maven-resources-plugin | 3.1.0-1 | stable | source maven-resources-plugin | 3.3.0-1 | testing | source maven-resources-plugin | 3.3.0-1 | unstable | source The last zstd-jni-java upload to experimental in March does FTBFS on all buildds: https://buildd.debian.org/status/package.php?p=zstd-jni-java=experimental Andreas zstd-jni-java.bookworm.build.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: zstd-jni-java Source-Version: 1.5.4-2+ds-2 Done: Markus Koschany We believe that the bug you reported is fixed in the latest version of zstd-jni-java, which is due to be installed in the
Bug#1034059: marked as done (zstd-jni-java: FTBFS during binary-arch build: Plugin org.apache.maven.plugins:maven-resources-plugin:3.1.0 or one of its dependencies could not be resolved)
Your message dated Sat, 08 Apr 2023 21:19:37 + with message-id and subject line Bug#1034059: fixed in zstd-jni-java 1.5.2-5+ds-3 has caused the Debian Bug report #1034059, regarding zstd-jni-java: FTBFS during binary-arch build: Plugin org.apache.maven.plugins:maven-resources-plugin:3.1.0 or one of its dependencies could not be resolved 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.) -- 1034059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034059 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zstd-jni-java Version: 1.5.2-5+ds-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Control: found -1 1.5.4-2+ds-1 Hi, zstd-jni-java FTBFS during a binary-arch build (as it is done on the buildd network), while binary-indep and combined binary-arch and binary-indep builds succeed. Reproducible in bookworm, sid and experimental. ... dh_auto_build -a -O--buildsystem=maven /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=/build/zstd-jni-java-1.5.2-5\+ds -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/build/zstd-jni-java-1.5.2-5\+ds/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/build/zstd-jni-java-1.5.2-5\+ds/debian -Dmaven.repo.local=/build/zstd-jni-java-1.5.2-5\+ds/debian/maven-repo 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] -< com.github.luben:zstd-jni >-- [INFO] Building zstd-jni 1.5.2-5 [INFO] [ jar ]- [WARNING] The POM for org.apache.maven.plugins:maven-resources-plugin:jar:3.1.0 is missing, no dependency information available [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 0.093 s [INFO] Finished at: 2023-04-07T17:09:36Z [INFO] [ERROR] Plugin org.apache.maven.plugins:maven-resources-plugin:3.1.0 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.apache.maven.plugins:maven-resources-plugin:jar:3.1.0 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=/build/zstd-jni-java-1.5.2-5\+ds -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/build/zstd-jni-java-1.5.2-5\+ds/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/build/zstd-jni-java-1.5.2-5\+ds/debian -Dmaven.repo.local=/build/zstd-jni-java-1.5.2-5\+ds/debian/maven-repo package -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1 make: *** [debian/rules:8: binary-arch] Error 25 Note that maven-resources-plugin 3.3.0 was uploaded in December, i.e. after the last zstd-jni-java upload to sid in November. maven-resources-plugin | 3.1.0-1 | stable | source maven-resources-plugin | 3.3.0-1 | testing | source maven-resources-plugin | 3.3.0-1 | unstable | source The last zstd-jni-java upload to experimental in March does FTBFS on all buildds: https://buildd.debian.org/status/package.php?p=zstd-jni-java=experimental Andreas zstd-jni-java.bookworm.build.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: zstd-jni-java Source-Version: 1.5.2-5+ds-3 Done: Markus Koschany We believe that the bug you reported is fixed in the latest version of zstd-jni-java, which is due to be installed in the
Bug#1034059: marked as pending in zstd-jni-java
Control: tag -1 pending Hello, Bug #1034059 in zstd-jni-java 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/java-team/zstd-jni-java/-/commit/67b4cbfab56dc775db01963cae87ca223b969b4a Depend on maven-resources-plugin 3.3.0 instead of version 3.1.0. Fixes FTBFS when building zstd-jni-java for binary-arch only. Thanks: Andreas Beckmann for the report. Closes: #1034059 (this message was generated automatically) -- Greetings https://bugs.debian.org/1034059
Processed: Bug#1034059 marked as pending in zstd-jni-java
Processing control commands: > tag -1 pending Bug #1034059 [src:zstd-jni-java] zstd-jni-java: FTBFS during binary-arch build: Plugin org.apache.maven.plugins:maven-resources-plugin:3.1.0 or one of its dependencies could not be resolved Ignoring request to alter tags of bug #1034059 to the same tags previously set -- 1034059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034059 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1034059 marked as pending in zstd-jni-java
Processing control commands: > tag -1 pending Bug #1034059 [src:zstd-jni-java] zstd-jni-java: FTBFS during binary-arch build: Plugin org.apache.maven.plugins:maven-resources-plugin:3.1.0 or one of its dependencies could not be resolved Added tag(s) pending. -- 1034059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034059 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1034059: marked as pending in zstd-jni-java
Control: tag -1 pending Hello, Bug #1034059 in zstd-jni-java 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/java-team/zstd-jni-java/-/commit/67b4cbfab56dc775db01963cae87ca223b969b4a Depend on maven-resources-plugin 3.3.0 instead of version 3.1.0. Fixes FTBFS when building zstd-jni-java for binary-arch only. Thanks: Andreas Beckmann for the report. Closes: #1034059 (this message was generated automatically) -- Greetings https://bugs.debian.org/1034059
Processed: forcibly merging 999526 1002393
Processing commands for cont...@bugs.debian.org:
> forcemerge 999526 1002393
Bug #999526 [python3-mdp] mdp: FTBFS with numpy 1.21 (in experimental):
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9
returned exit code 13
Bug #1002393 [python3-mdp] mdp: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
Merged 999526 1002393
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1002393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002393
999526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: reassign 1033931 to libc6
Processing commands for cont...@bugs.debian.org: > reassign 1033931 libc6 Bug #1033931 [libc-bin] Bug in glibc causes SIGSEGV in fis-gtm; see upstream bug report Bug reassigned from package 'libc-bin' to 'libc6'. No longer marked as found in versions glibc/2.36-8. Ignoring request to alter fixed versions of bug #1033931 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1033931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032553: magic-wormhole: FTBFS in testing: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit code 13
Hi Martin, [...] This is mentioned in https://github.com/magic-wormhole/magic-wormhole/issues/458 as likely a "timing issue". Not sure if it's fixed upstream. > Could it make sense to also patch the tests to include the delay that is mentioned in the GitHub issue comments? I've tried adding a 2 second delay in the failing test and that yields a package that builds reliably for me. I just rebuild the package with the patch 250 times successfully in a row. Excellent, thanks a lot! I will take a look and upload if needed. The maintainer supports LowNMU so that should not be a problem I guess. Otherwise please speak up now, Antoine :) [...] I'm not a DD, so i can't upload any fixes, but i would really appreciate if we can get this fixed before the auto removal strikes. Even with the 20 days transition delay we have now, this should still be in time for May 07. Thanks again and have nice holidays Sascha OpenPGP_signature Description: OpenPGP digital signature
Bug#1026204: marked as done (tar FTBFS on armel, armhf, i386, hppa, powerpc and sparc64)
Your message dated Sat, 08 Apr 2023 18:18:57 +
with message-id
and subject line Bug#1026204: fixed in tar 1.34+dfsg-1.2
has caused the Debian Bug report #1026204,
regarding tar FTBFS on armel, armhf, i386, hppa, powerpc and sparc64
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.)
--
1026204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026204
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tar
Version: 1.34+dfsg-1.1
Tags: hppa, patch, ftbfs, lfs
I wondered why tar now suddenly fails to build on those platforms.
Testcase # 151 does create files whith access dates which are outside of the
reach for
32-bit plaforms with a default of 32-bit timestamps in glibc.
This does succeed on filesystems which support 64-bit timestamps, but
stat'ing this file from 32-bit tar executable fails like this:
+tar: dir/f2038-01-19T03\:14\:08.9: Cannot stat: Value too large for defined
data type
(this message comes from glibc!)
Full log is here:
https://buildd.debian.org/status/fetch.php?pkg=tar=hppa=1.34%2Bdfsg-1.1=1670958554=0
I've found, that changing the line 12 in debian/rules from
CPPFLAGS = `dpkg-buildflags --get CPPFLAGS`
to:
CPPFLAGS = `dpkg-buildflags --get CPPFLAGS` -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D__USE_TIME_BITS64
does solve the issue.
So, either please add this line, or glibc needs fixing to allow
64-bit timestamps (which it probably did in earlier versions, since
otherwise tar would have failed in the past).
Here is a trivial testcase:
1. run:
touch -d 2106-02-07T06:28:15.001 f2106-02-07T06:28:15.001
2. compile and run this program, with and without __USE_TIME_BITS64 defined:
-
#define _FILE_OFFSET_BITS 64
#define _LARGEFILE_SOURCE
// #define __USE_TIME_BITS64
#include
#include
#include
#include
// run before starting this program: touch -d 2106-02-07T06:28:15.001
f2106-02-07T06:28:15.001
int main(void)
{
struct stat statbuf = { 0 };
int ret;
ret = fstatat(AT_FDCWD, "f2106-02-07T06:28:15.001", ,
AT_SYMLINK_NOFOLLOW);
fprintf(stderr, "return code %d errno %d st_atim.tv_sec %llx\n", ret,
errno, statbuf.st_atim.tv_sec);
return ret;
}
-
--- End Message ---
--- Begin Message ---
Source: tar
Source-Version: 1.34+dfsg-1.2
Done: Paul Gevers
We believe that the bug you reported is fixed in the latest version of
tar, 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 1026...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Paul Gevers (supplier of updated tar 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: Thu, 06 Apr 2023 16:25:47 +0200
Source: tar
Architecture: source
Version: 1.34+dfsg-1.2
Distribution: unstable
Urgency: medium
Maintainer: Janos Lenart
Changed-By: Paul Gevers
Closes: 1026204
Changes:
tar (1.34+dfsg-1.2) unstable; urgency=medium
.
* Non-maintainer upload.
* Build with lfs and -D_TIME_BITS=64 on 32 bits archs (Closes: #1026204)
Thanks to Andreas Henriksson and Helge Deller
Checksums-Sha1:
0d512170aeb72e1a47bdd69a9be8021e60e8e2be 1768 tar_1.34+dfsg-1.2.dsc
129c166c4c9351a97003f2c90895fda5e6c2e193 20336 tar_1.34+dfsg-1.2.debian.tar.xz
Checksums-Sha256:
4e7999f6d8a7fef2d09aa5b915877357a80c68ab0a339ee802b304d0e99e7517 1768
tar_1.34+dfsg-1.2.dsc
6e32291771f375a7e08cc4cabad1a658327d3dd7a4ff1b557a338ffe0675a25c 20336
tar_1.34+dfsg-1.2.debian.tar.xz
Files:
acbc41754da2052768791d014a55545f 1768 utils required tar_1.34+dfsg-1.2.dsc
c8c2f6987a8ed25d0bd075a4151dd754 20336 utils required
tar_1.34+dfsg-1.2.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmQvBWoACgkQnFyZ6wW9
dQrApgf/c5AN80kYBo6fl321CVE46EUiHIqYCdQYW6IKD6ZdFCwpd2KhijA5hVcy
q3jnu2aJtcQ1B6Uv8T6J95bLkCGD6xaMz8mY2fciYMNQ2WklAdgMQ+Jk9UHuwet3
w06acYNydf/+eaKfz8fT4qA5+p7eeyGpgPY4jOXqZelvtS/rz1Dd6p4oOk6fEIdP
HSpgTrqDunYDxy6llIaxKBzNEizYttkRDZpWvJohIgj36PkALRzRA3wBv/qepmZP
Uz6HKExAqRRFZhSkBczARaWV3iFjGPWa+9sYZUEn7QJYVM4sdWLSXiaG096dRToJ
8rq+RmKg1zVeyo8anCLmlUOirQxZwA==
=4hYc
Bug#1028104: libboost-dev: Boost with C++20 uses unavailable std functions
Control: tags -1 bookworm-ignore Hi Anton, On 08-04-2023 10:07, Anton Gladky wrote: I think there is a risk that something needs to be fixed, as there are no RC bugs against libboost-dev. You mean, no *other* RC bugs. It seems like boost1.81 is not affected by this problem. So, if somebody needs a newer library, they can take libboost1.81-dev, which is available for bookworm. I didn't realize we ship multiple boost versions. Which such a simple work around, I'll mark this bug as bookworm-ignore. I would not fix anything in boost shortly before release. Indeed, Paul, if you have some use cases where a small fix is really necessary, we can discuss it. Otherwise, I would leave it as it is. I don't, I'm not the bug submitter. I am wearing the Release Team hat here. By the way, I guess this bug is basically a duplicate of bug 1006309. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: Bug#1028104: libboost-dev: Boost with C++20 uses unavailable std functions
Processing control commands:
> tags -1 bookworm-ignore
Bug #1028104 {Done: Andreas Beckmann } [libboost-dev]
libboost-dev: Boost with C++20 uses unavailable std functions
Added tag(s) bookworm-ignore.
--
1028104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028104
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1034080: marked as done (sdop: fails to clean after successful build: No rule to make target 'distclean'.)
Your message dated Sat, 08 Apr 2023 16:49:16 + with message-id and subject line Bug#1034080: fixed in sdop 0.90-2 has caused the Debian Bug report #1034080, regarding sdop: fails to clean after successful build: No rule to make target 'distclean'. 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.) -- 1034080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034080 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sdop Version: 1.00-1 Severity: serious Tags: ftbfs Justification: fails to build from source twice in a row Hi, sdop/experimental fails to build twice in a row. (I haven't checked whether the package in sid has the same problem.) The first build succeeds, but the subsequent clean fails: debian/rules clean dh clean dh_auto_clean make -j3 distclean make[1]: Entering directory '/build/sdop-1.00' make[1]: *** No rule to make target 'distclean'. Stop. make[1]: Leaving directory '/build/sdop-1.00' dh_auto_clean: error: make -j3 distclean returned exit code 2 make: *** [debian/rules:17: clean] Error 25 Andreas sdop_1.00-1_twice.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: sdop Source-Version: 0.90-2 Done: Andreas Metzler We believe that the bug you reported is fixed in the latest version of sdop, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Metzler (supplier of updated sdop 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, 08 Apr 2023 18:19:00 +0200 Source: sdop Architecture: source Version: 0.90-2 Distribution: unstable Urgency: medium Maintainer: Andreas Metzler Changed-By: Andreas Metzler Closes: 1034080 Changes: sdop (0.90-2) unstable; urgency=medium . * 30_fix-dh_auto_clean.diff: Fix failure to build from source twice in a row. Closes: #1034080 Checksums-Sha1: 659735168adfe5e8cdd0ac0b91a7a9981fc959e7 1660 sdop_0.90-2.dsc d261d777e8e76853bcabccf80cd0e8b6d1bbc733 5220 sdop_0.90-2.debian.tar.xz Checksums-Sha256: 4c0def3751741aa5dd16b2d9578184e1412f214cc6b7abba40c7c36a83bbd6b8 1660 sdop_0.90-2.dsc 20b7a3e8c896a36cde7c46dfa7f6f3c1e445baa4515a91a6b56a5abf3bca5da7 5220 sdop_0.90-2.debian.tar.xz Files: a7345fb5d5f9fdfbca483df662746e7c 1660 text optional sdop_0.90-2.dsc 447cc2a269b1da77030ec5f591481eba 5220 text optional sdop_0.90-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmQxlWcACgkQpU8BhUOC FIS41BAAisKKQuwIf/nGixnlnOWbn1s2XwbWf0zp4qxEYSkOkLg6zy37RoEDnecI 9OKSgqCMnVVI7c6dl23PCTLzbkOJdh535xqTwXS1tVVpDsIUT2Fg7xjmic2pceRq nJSmUnDNFDAEAZLAlEoTmcH9yt4DOez9JPF1e1xSFAStsxYwReBE5S/XyV0CIL8j /ADpFHvPiZVlZhPRyU/jxu9zp08zl9ORQW1B2PKInpzeViQ53xv5As/eDJ4dKGjG 9YSoRKKF/4aulZvuRX+lJBDsIyZT0/nrbdth0PgD8b8cne3ibeA834K1ZneSNMk7 KwzHMFQfp/m/Q4S474zMd0IfGQAmVDbV2qHgOTt01vOucB9L4wYwh/kLFYWdJNDM hsrD0HDbgoqsyigfgNs7yHTIM+U8hgwgg4citkUDnD+3wV/d9eGsPN4H6DJzHNIG 7nbvXAIULfN51dV4Xj4bCWM4K9bxK9YGv/ezSiMCQuUrSPvXZq8D+v5Kj1HZ7zIr /MlDhz/IHw6kA+fsQiLdbtk1tFI/tbel1lAlmfYk7A4fwLXEMywlAOwreTwGFRRs aba0foO+gCy2esdEv3esKdGx/4BTVBk24Kf8ngjVOPbDdvJzJXNQA/adqQPjFtNU uYd2XvChsEod5ei91d25AKe9q6lzYXuGJhEQEE9R+9JD5DwlwYQ= =sZ9I -END PGP SIGNATURE End Message ---
Bug#1033702: marked as done (freefem++: autopkgtest regression: warnings on stderr)
Your message dated Sat, 08 Apr 2023 16:49:06 + with message-id and subject line Bug#1033702: fixed in freefem++ 4.11+dfsg1-3 has caused the Debian Bug report #1033702, regarding freefem++: autopkgtest regression: warnings on stderr 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.) -- 1033702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033702 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: freefem++ Version: 4.11+dfsg1-2 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), Your package has an autopkgtest, great. However, it started to fail in August 2022 on amd64, armhf and i386. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team hat on] Because of the timing (we're in hard freeze) I've marked this bug as bookworm-ignore as the problem is "only" warnings. A targeted fix is still welcome (adding allow-stderr restriction for the test, code fixing needs to wait until the release). More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/f/freefem++/32183287/log.gz build-and-run-libFAIL stderr: In file included from /usr/include/freefem++/AFunction.hpp:93, autopkgtest [16:24:09]: test build-and-run-lib: - - - - - - - - - - stderr - - - - - - - - - - In file included from /usr/include/freefem++/AFunction.hpp:93, from /usr/include/freefem++/ff++.hpp:21, from /tmp/autopkgtest-lxc.okwz3yij/downtmp/build.NQ2/src/plugin/seq/myfunction.cpp:30: /usr/include/freefem++/String.hpp:195:19: warning: ‘template_Arg1, class _Arg2, class _Result> struct std::binary_function’ is deprecated [-Wdeprecated-declarations] 195 | struct pairless : binary_function,const char *, bool> | ^~~ In file included from /usr/include/c++/12/string:48, from /usr/include/c++/12/bits/locale_classes.h:40, from /usr/include/c++/12/bits/ios_base.h:41, from /usr/include/c++/12/ios:42, from /usr/include/c++/12/istream:38, from /usr/include/c++/12/fstream:38, from /usr/include/freefem++/ff++.hpp:12: /usr/include/c++/12/bits/stl_function.h:131:12: note: declared here 131 | struct binary_function |^~~ OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: freefem++ Source-Version: 4.11+dfsg1-3 Done: Francois Mazen We believe that the bug you reported is fixed in the latest version of freefem++, 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 1033...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Francois Mazen (supplier of updated freefem++ 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, 08 Apr 2023 15:19:26 +0200 Source: freefem++ Architecture: source Version: 4.11+dfsg1-3 Distribution: unstable Urgency: high Maintainer: Debian Science Maintainers Changed-By: Francois Mazen Closes: 1033702 Changes: freefem++ (4.11+dfsg1-3) unstable; urgency=high . * Add allow-stderr restriction for build-and-run-lib (Closes: #1033702) Checksums-Sha1: 67c7f43881170b24c99a1ee11c171eece38c8d4a 2961 freefem++_4.11+dfsg1-3.dsc 53190de5e8c4e0419929a12a39cd6f5006f9cf5c 29604 freefem++_4.11+dfsg1-3.debian.tar.xz 6b6f9234d18ffc53d4ac760683a6a477308c065d 19952 freefem++_4.11+dfsg1-3_source.buildinfo Checksums-Sha256: 8efbdab7e91cca9fb1f810641030cebcd6d813234820ed5a2cba225d42f1ec96 2961 freefem++_4.11+dfsg1-3.dsc 5e63a999d193d3c08f5ac0235d07a3ae24423169fc752fa26e941e3dd02865e2 29604 freefem++_4.11+dfsg1-3.debian.tar.xz
Bug#1017180: FTBFS
Hi, I did a rebuild of 5.8-arduino11-2 in a sid sbuild chroot. Buildlog is attached. the watchfile is broken, but it built fine apart from that. Regards, --- Matthias Geiger (werdahias) arduino-ctags_5.8-arduino11-2_amd64.build Description: Binary data -BEGIN PGP PUBLIC KEY BLOCK- mQINBGJGNsQBEADCVylaCtYtBQW4NmDrZOIizSrVlv5ZJ5WJ128MAblWk3fRFPya Cs/klkTT58ehBSr61sXVP+NpkF7MWOBu2CNg66U40a/Eb+v4poxNaIjXKvQtf51S y5yGwmTc7IJg8HuohT7K3/pcsEt0jvYSwvvDFUIz5WdOR5RmB7WkDRGh8Zaior3z tzx6AKhx/aXmAc/i4BDavDxZeFC0d79H3S1+TvFsvhyIZXIFTB0sTzWreZZxSOjk Mz6xxgWGdc27lsbZbKU7N+c+GnWrRlTjimU1AfPLJQgehIejR9pSyZ2Y5BAqB7Qr f8Tvc8jc1kDx473sUUla6ELEuJMIISK1qam/B7buxZ1r/ngWRiQsqAHznm7OYk69 ttXBeHxS1b+HrcJMWfROkzsTuG6G//axMCb6x0MuyOgLXk87aDnDx1fPn62R+tq7 T4JvW51TSnlNNh75zA+8w3UzDHy2By0H6NSfiLerNnF7LGCXk7AiwQsaplrEjo/1 /4NraAqy1eO69SyozSiRuuA5KemlyPwJokpp2HMJX3cry2J7lV0+wnaaorQzz5Fi 7gRRlqXrOGwEcEG6i62VbIv2VW3Zy+qjaD3HRWXfKXXjpXske41Trv2qPI2/kGtJ TRWSWdTQ42oYOaEg/KUh0GnEoZerj50JC1qGmwElKYgd+2XQ8qR7uIB5qQARAQAB tDFNYXR0aGlhcyBHZWlnZXIgPG1hdHRoaWFzLmdlaWdlcjEwMjRAdHV0YW5vdGEu ZGU+iQJUBBMBCgA+FiEEwuGmy/3s5RGopBdtGL0QaztsVHUFAmJGNsQCGwMFCQPC ZwAFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AACgkQGL0QaztsVHVMxQ/+M5JEQ5wk DDblHGUlK8IBnPM5peuDrMdQAsOQ5nSv90gl4z4HkRgomS70xMpvoS+g/8hPym4G PXpSFJsZWjFevACWMzZO84pqJhPaFnmjh3utkkiblNf8Wi350K+luAlRvT1FVD6i HM6kOxU0P9t9+PU38FH299oRw2qEqDw5Wx+Hrnp4gaGv1mssvAMiXeaaPGx4KSz8 sNXADHJDo78U6RGJM/rSng/8M7zd3c6E8MIH958mlWjUb8T10AZ/otH3nFSRIfds 5MdnnrsKAK3DMW4RanRWHPvTsICDDkuRvigd32waQRdZeA3dNbPxM6tKDL9GEH8Q AnkShJ7VmTXP9CV20vj15mleoeDMgqhX5KEOsc3DMnKcVqdb9CzHj6jNSFUverk1 bBNaJpIiWwtwjueR4Hgdof80AAgRin4YnWaOaPTSusrKyN8dCRVcRIbauVooWLil q2OrWftDVmmNciwoHr5/WDPNgkv9DAgY+DX8Y8LMWAkXgpB0KniiQaLzrW34zjnP ALTLTIvNid6YX8KOY6KhAVWfVdMC5j6GEGfbfyMLz63YPxA9Q1Af6oXS8MbdHyBw JV8ns2xm5fD2vZVw6JI1e8AMMDjH2fAqmH23MG0fN0zd2NUToHmvhX9APSzJIbET doFPn/mI/az4Oh24WHf3Ozr+XEDyWcyy1y+5Ag0EYkY2xAEQANL26Ixtq1QMUM+5 MHl2FK4foRODoKHe4ZzdOAumUBPJE/pxGVlVxCqzC+LUeFvA8LTYCt1B60yRveYR 4mmPTA7nAerG2m4aQPeIfzz6HXWkiu9mzgxqjhPxitiMR5f1du1rAWGPZxSkhdW6 fDWT4PkHoY78jbQXWYEnV85rwtZIZIduHGKWzyxln3qjrefmB04QkPJ2BDOsRTtD YeNddHAvcgZtyepqZka9lpowQTY6TXwM8uYArEa7Hll/4r9rcvkVQUxf8jqYpZ3v PLSzvvaDouH7WAg5nUaTeWAQdSq108rNRSTgScLZWjwmhFBA46RneRpij2OJ0lW4 QqFTlldjWXzgGj6u4nbXrSERGaPwyLGIkHoKbnTAm7791d/Y5UQImuPb1tIg5Pf7 OhtyWw3bstVDa5MvIUuGpi5yKPirhrtAfdZ3H2/HR814JuL2BYdjyCuR/Sj/lZTx +gJ0bm+Llr0KZDhjKMeWaqVqsD4bybgEe4d3zE4sj9GZ0tNUvXfPaRGY6tgh9sgT Iy28vnyYpFX+oSIZXRreDpfzyjDhvNbB+AFsPN5OXqaBpmu/378T5nRpUj/qbqEZ EsloCbAmgHfvIysQWYdJ+63S3ZqpbEQRa4Y7DeybaLi8xTMfdWa19T7vQY3mVWn5 ZooycK4fkbedu19+5l8zfhR7oWyBABEBAAGJAjwEGAEKACYWIQTC4abL/ezlEaik F20YvRBrO2xUdQUCYkY2xAIbDAUJA8JnAAAKCRAYvRBrO2xUdRuPD/4tdAf8nxsA upo5O99E4AS59OTXPQuVgt1U2Z7ssDvZ3O6qbZvIBWQ0NqnCsprCt71M6cWC2dkq WUs3oRRu4IzuB4LErcTr597k+iltJ60rhDL/hxSumToH6FSX1w8EWJVg3xgP4U39 HSx6QOlZ3bTgd9dS5S46jOptIYzX5wYkNzyMj1hbmTg0lVyMtWjqfCLNmF3EzGGC BLR3tMOxZURrxx8tL48iJlFyxJG3XahoyxDSNepo5HZ+AUnNq2TJPoPJQfb1/GB/ /LycKSXWgblyWuGRlgoCE1JcdwuRM5hI2xugZQrhgZaPUBch1MSoiIqwgR1A8NPL iypUPnwG4vEaVbMtem7OUghsx+fYwuGq0T7/ezjyVRv86U2gU1bmbxojct1AXSCT FCCR3Y8QAHV9o8U/eZ1XzcEZsXFd6siO5nEBl9HaTHh5gWDrk/molP85S7Y9JIBP wZygBjWOPCCkFlIuiPQlXsJezVu93ydz7uCNIJfHv30oVedcYHN1Wr7B/1j8wXMy wqW4Nw54yZ8zaJIo01Khym6cFFVXoAUZa+5QRvSmjnm1Go+ZwZA9i7zo/6LLSpeR 04+4a1Daysk0fTf+DscrxQbUBZX17e1n/EtLS8/pp+Xb/k1JK1iiNcdpfLJ7RNik GX00szhWs5riRMzIibFDsE/FyYVNX2VHQg== =onWA -END PGP PUBLIC KEY BLOCK-
Bug#991067: marked as done (x4d-icons FTBFS with imagemagick with the #987504 change)
Your message dated Sat, 08 Apr 2023 16:17:09 + with message-id and subject line Bug#991067: fixed in x4d-icons 1.2-2+deb11u1 has caused the Debian Bug report #991067, regarding x4d-icons FTBFS with imagemagick with the #987504 change 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.) -- 991067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: x4d-icons Version: 1.2-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/x4d-icons.html ... dh_auto_build make -j1 make[1]: Entering directory '/build/x4d-icons-1.2' TZ=UTC faketime -f '2014-05-03 00:00:00' ./generate.sh convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @
Bug#1033408: marked as done (apache2: Segmentation fault + 503 on frontpage on 2.4.56-1)
Your message dated Sat, 08 Apr 2023 16:17:08 + with message-id and subject line Bug#1033408: fixed in apache2 2.4.56-1~deb11u2 has caused the Debian Bug report #1033408, regarding apache2: Segmentation fault + 503 on frontpage on 2.4.56-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.) -- 1033408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apache2 Version: 2.4.56-1~deb11u1 Severity: important X-Debbugs-Cc: t...@security.debian.org Unattended-upgrades applied this new version on 22 march @ 6AM. Had Segmentation faults since then, 503 for customers on websites. Since we reverted back to 2.4.54, we've no more issues. Couldn't make any sense of coredump but can provide one if necessary. -- Package-specific info: -- System Information: Debian Release: 11.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-18-amd64 (SMP w/32 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages apache2 depends on: ii apache2-bin 2.4.56-1~deb11u1 ii apache2-data 2.4.56-1~deb11u1 ii apache2-utils2.4.56-1~deb11u1 ii dpkg 1.20.12 ii init-system-helpers 1.60 ii lsb-base 11.1.0 ii mime-support 3.66 ii perl 5.32.1-4+deb11u2 ii procps 2:3.3.17-5 Versions of packages apache2 recommends: ii ssl-cert 1.1.0+nmu1 Versions of packages apache2 suggests: pn apache2-doc pn apache2-suexec-pristine | apache2-suexec-custom ii lynx [www-browser] 2.9.0dev.6-3~deb11u1 Versions of packages apache2-bin depends on: ii libapr1 1.7.0-6+deb11u2 ii libaprutil1 1.6.1-5+deb11u1 ii libaprutil1-dbd-sqlite3 1.6.1-5+deb11u1 ii libaprutil1-ldap 1.6.1-5+deb11u1 ii libbrotli1 1.0.9-2+b2 ii libc62.31-13+deb11u5 ii libcrypt11:4.4.18-4 ii libcurl4 7.74.0-1.3+deb11u7 ii libjansson4 2.13.1-1.1 ii libldap-2.4-22.4.57+dfsg-3+deb11u1 ii liblua5.3-0 5.3.3-1.1+b1 ii libnghttp2-141.43.0-1 ii libpcre3 2:8.44-2+0~20210301.9+debian11~1.gbpa278ad ii libssl1.11.1.1n-0+deb11u4 ii libxml2 2.9.14+dfsg-0+0~20220524.12+debian11~1.gbpc5dc45 ii perl 5.32.1-4+deb11u2 ii zlib1g 1:1.2.11.dfsg-2+deb11u2 Versions of packages apache2-bin suggests: pn apache2-doc pn apache2-suexec-pristine | apache2-suexec-custom ii lynx [www-browser] 2.9.0dev.6-3~deb11u1 Versions of packages apache2 is related to: ii apache2 2.4.56-1~deb11u1 ii apache2-bin 2.4.56-1~deb11u1 -- Configuration Files: /etc/apache2/apache2.conf changed [not included] /etc/apache2/mods-available/mpm_event.conf changed [not included] /etc/apache2/ports.conf changed [not included] /etc/apache2/sites-available/000-default.conf changed [not included] -- no debconf information --- End Message --- --- Begin Message --- Source: apache2 Source-Version: 2.4.56-1~deb11u2 Done: Yadd We believe that the bug you reported is fixed in the latest version of apache2, 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 1033...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated apache2 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: Sun, 02 Apr 2023 07:06:01 +0400 Source: apache2 Architecture: source Version: 2.4.56-1~deb11u2 Distribution: bullseye Urgency: medium Maintainer: Debian Apache Maintainers Changed-By: Yadd Closes: 1018718 1033284 1033408 Changes: apache2 (2.4.56-1~deb11u2) bullseye; urgency=medium . [ Hendrik Jäger ] * Don't
Bug#1018718: marked as done (apache2-doc: despite having been disabled, apache2-doc.conf gets rather silently re-enabled automatically)
Your message dated Sat, 08 Apr 2023 16:17:08 + with message-id and subject line Bug#1018718: fixed in apache2 2.4.56-1~deb11u2 has caused the Debian Bug report #1018718, regarding apache2-doc: despite having been disabled, apache2-doc.conf gets rather silently re-enabled automatically 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.) -- 1018718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018718 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apache2-doc Version: 2.4.54-1~deb11u1 Severity: important Hey. Unfortunately #977014 has been ignored so far, but no I just noted that even when one explicitly disabled apache2-doc.conf via a2disconf, it still gets rather silently re-enabled on upgrading the package, which is IMO quite unfortunate. Please fix at least that, or even better #977014, in which case this bug here would become obsolete. Thanks :-) Chris. --- End Message --- --- Begin Message --- Source: apache2 Source-Version: 2.4.56-1~deb11u2 Done: Yadd We believe that the bug you reported is fixed in the latest version of apache2, 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 1018...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated apache2 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: Sun, 02 Apr 2023 07:06:01 +0400 Source: apache2 Architecture: source Version: 2.4.56-1~deb11u2 Distribution: bullseye Urgency: medium Maintainer: Debian Apache Maintainers Changed-By: Yadd Closes: 1018718 1033284 1033408 Changes: apache2 (2.4.56-1~deb11u2) bullseye; urgency=medium . [ Hendrik Jäger ] * Don't automatically enable apache2-doc.conf (Closes: #1018718) . [ Yadd ] * Fix regression in mod_rewrite introduced in version 2.4.56 (Closes: #1033284) * Fix regression in http2 introduced by 2.4.56 (Closes: #1033408) Checksums-Sha1: 89d02fe86e3ebc78ff891696d693cf3a14dc33f6 3539 apache2_2.4.56-1~deb11u2.dsc 29ea0a273a403079320c83888e14b45e5c65c80d 895464 apache2_2.4.56-1~deb11u2.debian.tar.xz Checksums-Sha256: b8ac3c048efb9ef96a2a4ab1975b89d202d8d9b0f3683e752df721537dc50cc9 3539 apache2_2.4.56-1~deb11u2.dsc 0be84882d86464d4882334f0939411bbec335b64b7062d372e3e898e9033cc0b 895464 apache2_2.4.56-1~deb11u2.debian.tar.xz Files: 79911bbab259494333aa95609c9eabbd 3539 httpd optional apache2_2.4.56-1~deb11u2.dsc 64fbb75abf882e7de027b5d6abe67c83 895464 httpd optional apache2_2.4.56-1~deb11u2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmQw2sYACgkQ9tdMp8mZ 7umUuA//a+g5qa6XkJPfTu78dUMFKqoDbxx06ap586Ai4Iy3WOs38BeA7vViNYGb 92XmZDAiDj+2f2To3mLH4eqNELGkhHDBhF+ikxwc1CtVlDHdlqGMiEL3/HEl8GyL bvosCZTk/8Gg/hMIfAIGBN6XGeyqo2OIibTeNKtU4VD3evxSA7O8e7aTHLWgGeU3 cJwcMtuhtI2ju8PzOl94otqjydmkSIbegdce+OUh2Ytp072nSePHppIrDgWCt8Oq JjcrUl+TYXZMY/leLxF3sk/Lp2kjegQuaoMTTUeTtxPbqlLqhi2dUp0yAobhriHR Zgdg+iPoDxB3hVh2qD831nQNM2GvDyD2JMoRWd7FV5+48R+e++P+mWLvIwB/OSFj RMBUx+jY8Zz9VzmPjpDLe4eTh7KXbg8/7e/Z3HqaF2741RpdRnOdQbK3Zb5jsb7c MNVLz2ke1LTZ3igfJc13/WuRzjd+Wh1rOx63CU/vRdZMzhQhcBu4DdDXHtTTa8cf UKBeoI3XYrBBu6oC1QUBGTQQTwe0Ki8uZ/ZfEjElJ6fGfNmD69OZ4irjhjfOskBd MC3oNmqAgdy/jlNnuniAkof8/XlZO6hmcRha6G0MPMOMAKMnRvZxwx6OjBYs6+9a GZNLAGZ74E3RkzS8kiPmNc1bubDms/Tq3OiNih7yYsBiMuLSEOc= =NyVi -END PGP SIGNATURE End Message ---
Bug#1033732: marked as done (linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message)
Your message dated Sat, 08 Apr 2023 15:55:22 + with message-id and subject line Bug#1033732: fixed in linux 6.1.20-2 has caused the Debian Bug report #1033732, regarding linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message 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.) -- 1033732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033732 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 6.1.20-1 Severity: critical Justification: breaks the whole system Dear Maintainer, Up to now I worked with Linux 6.1.0-7-amd64, without any trouble. I just installed Linux 6.1.0-7-amd64 and I get a kernel panic when launching it. Here is a transcription of what appears on the screen (OCR on a screen picture, I hope there are no remaining errors). [ 0.117782] Kernel panic — not syncing: timer doesn’t work through Interrupt- remapped I0-APIC [ 0.117848] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.0-7-and64 #1 Debian 6.1.20-1 [ 0.117913] Hardware name: Gigabyte Technology Co., Ltd. ABS50M-Gaming 3/AB350M-Gaming 3-CF, BIOS F50d 07/02/2020 [ 0.117982] Call Trace: [ 0.118634] [ 0.118685] dump_stack_lvl+0x44/0x5c [ 0.118143] panic+0x118/0x2ed [ 0.118198] panic_if_irq_remap.cold+0x5/0x5 [ 0.118256] setup_I0_APIC+0x3db/0x64b [ 0.118313] ? _raw_spin_unlock_irqrestore+0x23/0x40 [ 0.118372] ? clear_IO_APIC_pin+0x169/0x240 [ 0.118429] apic_intr_node_init+0x101/0x106 [ 0.118485] x86_late_time_init+0x20/0x34 [ 0.118542] start_kerne1+0x667/0x727 [ 0.118598] secondary_startup_64_no_verify+0xe5/0xeb [ 0.118658] [ 0.118711] ---[ end Kernel panic - not syncing: timer doesn’t work through Interrupt-remapped IO-APIC J--- Hope it helps. Thanks in advance for your help. Best regards. -- Guy Durrieu -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Gigabyte Technology Co., Ltd. product_name: AB350M-Gaming 3 product_version: Default string chassis_vendor: Default string chassis_version: Default string bios_vendor: American Megatrends Inc. bios_version: F50d board_vendor: Gigabyte Technology Co., Ltd. board_name: AB350M-Gaming 3-CF board_version: x.x -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-6-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-6.1.0-7-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.142 ii kmod 30+20221128-1 ii linux-base 4.9 Versions of packages linux-image-6.1.0-7-amd64 recommends: ii apparmor 3.0.8-3 ii firmware-linux-free 20200122-1 Versions of packages linux-image-6.1.0-7-amd64 suggests: pn debian-kernel-handbook ii grub-efi-amd64 2.06-8 pn linux-doc-6.1 Versions of packages linux-image-6.1.0-7-amd64 is related to: ii firmware-amd-graphics 20230210-4 pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas ii firmware-linux-nonfree 20230210-4 ii firmware-misc-nonfree 20230210-4 pn firmware-myricom pn firmware-netxen pn firmware-qlogic ii firmware-realtek 20230210-4 pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information --- End Message --- --- Begin Message --- Source: linux Source-Version: 6.1.20-2 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of linux, 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 1033...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated linux
Processed: found 1034080 in 0.90-1
Processing commands for cont...@bugs.debian.org:
> found 1034080 0.90-1
Bug #1034080 {Done: Andreas Metzler } [src:sdop] sdop:
fails to clean after successful build: No rule to make target 'distclean'.
Marked as found in versions sdop/0.90-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1034080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034080
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1034090: ibus: FTBFS twice in a row: src/ibusenumtypes.h is regenerated too late
Source: ibus Version: 1.5.28-3 Severity: serious Justification: fails to build twice in a row Hi, ibus/experimental fails to build twice in a row. (I haven't verified whether the version in sid is also affected by this bug.) The first build succeeds and a subsequent debian/rules clean removes src/ibusenumtypes.h (and maybe other required files): debian/rules clean dh clean --with gir,python3 dh_auto_clean make -j3 distclean make[1]: Entering directory '/build/ibus-1.5.28' Making distclean in src make[2]: Entering directory '/build/ibus-1.5.28/src' Making distclean in . make[3]: Entering directory '/build/ibus-1.5.28/src' test -z "IBus-1.0.gir IBus-1.0.typelib ibusmarshalers.c ibusmarshalers.h ibusenumtypes.c ibusenumtypes.h ibusresources.c ibusresources.h ibus.gresources.xml stamp-ibusmarshalers.h stamp-ibusenumtypes.h " || rm -f IBus-1.0.gir IBus-1.0.typelib ibusmarshal ers.c ibusmarshalers.h ibusenumtypes.c ibusenumtypes.h ibusresources.c ibusresources.h ibus.gresources.xml stamp-ibusmarshalers.h stamp-ibusenumtypes.h ... That file doesn't get regenerated before it is used during the second build, resulting in: ... ( top_builddir=`cd .. && pwd`; \ cd . && /usr/bin/glib-mkenums --template ibusenumtypes.c.template ibus.h ibusaccelgroup.h ibusattribute.h ibusattrlist.h ibusbus.h ibuscomponent.h ibusconfig.h ibusconfigservice.h ibusdebug.h ibusemoji.h ibusengine.h ibusenginedesc.h ibusenginesimple.h ibuse rror.h ibusfactory.h ibushotkey.h ibusinputcontext.h ibuskeymap.h ibuskeys.h ibuskeysyms-compat.h ibuskeysyms.h ibuslookuptable.h ibusobject.h ibusobservedpath.h ibuspanelservice.h ibusproperty.h ibusproplist.h ibusproxy.h ibusregistry.h ibusserializable.h i busservice.h ibusshare.h ibustext.h ibustypes.h ibusunicode.h ibusutil.h ibusxevent.h ibusxml.h | \ sed 's/i_bus_/ibus_/g' | \ sed 's/I_TYPE_BUS_/IBUS_TYPE_/g') > \ ibusenumtypes.c.tmp && mv ibusenumtypes.c.tmp ibusenumtypes.c ( top_builddir=`cd .. && pwd`; \ cd . && /usr/bin/glib-mkenums --template ibusenumtypes.h.template ibus.h ibusaccelgroup.h ibusattribute.h ibusattrlist.h ibusbus.h ibuscomponent.h ibusconfig.h ibusconfigservice.h ibusdebug.h ibusemoji.h ibusengine.h ibusenginedesc.h ibusenginesimple.h ibuse rror.h ibusfactory.h ibushotkey.h ibusinputcontext.h ibuskeymap.h ibuskeys.h ibuskeysyms-compat.h ibuskeysyms.h ibuslookuptable.h ibusobject.h ibusobservedpath.h ibuspanelservice.h ibusproperty.h ibusproplist.h ibusproxy.h ibusregistry.h ibusserializable.h i busservice.h ibusshare.h ibustext.h ibustypes.h ibusunicode.h ibusutil.h ibusxevent.h ibusxml.h | \ sed 's/i_bus_/ibus_/g' | \ sed 's/I_TYPE_BUS_/IBUS_TYPE_/g') > \ ibusenumtypes.h.tmp && mv ibusenumtypes.h.tmp ibusenumtypes.h INFO: Reading ./ibusmarshalers.list... sed -e "s|\@ENDIAN\@|little|g" \ ibus.gresources.xml.in > ibus.gresources.xml.tmp && \ mv ibus.gresources.xml.tmp ibus.gresources.xml gcc -DHAVE_CONFIG_H -I. -I.. -DG_LOG_DOMAIN=\"IBUS\" -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/incl ude -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gio-unix-2.0 -pthread -DIBUS_CACHE_DIR=\""/var/cache/ibus"\" -DIBUS_DATA_DIR=\"/usr/share/ibus\" -DIBUS_DISABLE_DEPRECATION_WARNINGS -DIBUS_COMPILATION -DISOCODES_PREFIX=\"/usr\" -DX11_DATA_PREF IX=\"/usr\" -DENABLE_EMOJI_DICT -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/build/ibus-1.5.28=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -c -o gen_internal_compose_table-gencomposetable.o `test -f 'gencomposet able.c' || echo './'`gencomposetable.c In file included from ./ibusobject.h:41, from ./ibus.h:31, from gencomposetable.c:23: ./ibusdebug.h:49:31: warning: ISO C does not permit named variadic macros [-Wvariadic-macros] 49 | #define ibus_warning(msg, args...) \ | ^~~ gcc -DHAVE_CONFIG_H -I. -I.. -DG_LOG_DOMAIN=\"IBUS\" -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/incl ude -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gio-unix-2.0 -pthread -DIBUS_CACHE_DIR=\""/var/cache/ibus"\" -DIBUS_DATA_DIR=\"/usr/share/ibus\" -DIBUS_DISABLE_DEPRECATION_WARNINGS -DIBUS_COMPILATION -DISOCODES_PREFIX=\"/usr\" -DX11_DATA_PREF IX=\"/usr\" -DENABLE_EMOJI_DICT -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/build/ibus-1.5.28=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -c -o gen_internal_compose_table-ibuscomposetable.o `test -f 'ibuscompos etable.c' || echo './'`ibuscomposetable.c ./ibus.h:49:10: fatal error: ibusenumtypes.h: No such file or directory 49 | #include |
Bug#1034088: cyrus-imapd: fails to clean after successful build: No rule to make target 'Makefile.PL', needed by 'Makefile'.
Source: cyrus-imapd Version: 3.8.0~beta2-1 Severity: serious Justification: fails to build from source twice in a row Hi, cyrus-imapd/experimental fails to clean after a successful build. (I didn't verify whether the package in sid has the same problem.) ... Making distclean in perl/annotator make[2]: Entering directory '/build/cyrus-imapd-3.8.0~beta2/perl/annotator' make[2]: *** No rule to make target 'Makefile.PL', needed by 'Makefile'. Stop. make[2]: Leaving directory '/build/cyrus-imapd-3.8.0~beta2/perl/annotator' make[1]: *** [Makefile:7537: distclean-recursive] Error 1 make[1]: Leaving directory '/build/cyrus-imapd-3.8.0~beta2' dh_auto_clean: error: make -j3 distclean returned exit code 2 make: *** [debian/rules:57: clean] Error 25 Andreas cyrus-imapd_3.8.0~beta2-1_twice.log.gz Description: application/gzip
Bug#1034080: marked as done (sdop: fails to clean after successful build: No rule to make target 'distclean'.)
Your message dated Sat, 08 Apr 2023 13:34:27 + with message-id and subject line Bug#1034080: fixed in sdop 1.00-2 has caused the Debian Bug report #1034080, regarding sdop: fails to clean after successful build: No rule to make target 'distclean'. 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.) -- 1034080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034080 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sdop Version: 1.00-1 Severity: serious Tags: ftbfs Justification: fails to build from source twice in a row Hi, sdop/experimental fails to build twice in a row. (I haven't checked whether the package in sid has the same problem.) The first build succeeds, but the subsequent clean fails: debian/rules clean dh clean dh_auto_clean make -j3 distclean make[1]: Entering directory '/build/sdop-1.00' make[1]: *** No rule to make target 'distclean'. Stop. make[1]: Leaving directory '/build/sdop-1.00' dh_auto_clean: error: make -j3 distclean returned exit code 2 make: *** [debian/rules:17: clean] Error 25 Andreas sdop_1.00-1_twice.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: sdop Source-Version: 1.00-2 Done: Andreas Metzler We believe that the bug you reported is fixed in the latest version of sdop, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Metzler (supplier of updated sdop 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, 08 Apr 2023 15:19:00 +0200 Source: sdop Architecture: source Version: 1.00-2 Distribution: experimental Urgency: medium Maintainer: Andreas Metzler Changed-By: Andreas Metzler Closes: 1034080 Changes: sdop (1.00-2) experimental; urgency=medium . * 30_fix-dh_auto_clean.diff: Fix failure to build from source twice in a row. Closes: #1034080 Checksums-Sha1: 7dc02c27967329cd3906457b5553b9c3eab633e3 1707 sdop_1.00-2.dsc dbe7805dc91d4131157753c36d8a5fed2ae762a4 5576 sdop_1.00-2.debian.tar.xz Checksums-Sha256: b4bb88f5631afc28484055c78a17a8119b3a75b62aad1ee607e71b7dcf8eacc3 1707 sdop_1.00-2.dsc b9dc976f07e1af236eae2d986273d3829d9c19b05c1dac170317806c15761659 5576 sdop_1.00-2.debian.tar.xz Files: 523e7cedc365bcf7ad23ba8e396e9849 1707 text optional sdop_1.00-2.dsc f7fe121306d101cad51cd400566e734b 5576 text optional sdop_1.00-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmQxawQACgkQpU8BhUOC FIRycg/9Hak/u4SJWwwgLTOfYGd5cHH+U73M1w48CumtyiuGyQbfzvquMx8NBaue ex7psRWoatLIy7bA/v6v+7WDOfa/HZqesIJe64kj8RUObPb7RdUr0WWCNU5PZ/+3 QTZQ4WOm3TSqUsXm1t932ECFYrVdOEmpLlyBMNXmdo2t43KkyRBC1E/nwile4gjj mG7ihB1emsrLgIJ0ePLxFITug2quognXYMIfXFvS/AsBfLydfgQbjjSmeC3ggtz5 x9cym0vc+4m+VMLqJgQKEppnlSXyoNFhz56PHo1rvyMxv6hIetCAOUJqj37v3dqJ bXxawVxaofemnnTTGWyALPSRpRKQCzYioZCY8w/nOdkTpZ4EMQ8s1AkfXzjpf/g/ 5x0WA31Lywyut7cfQO5PtpzLw7aSNTOBEkk7pRZSPHNen0Pd3zpAGITx9KMN6P30 9vafhyaYIsroewWxeGL2OsGWMEc5jTERYzytuUGewvOCVTV3qBFyuUFX0nbqkXtH 18SktibuYRKso8ct5EZx3AfbU/PtfyiXQr7yrJEsCP4DTBr8OCDPMAn4A0Jc1jLl e5fyqzmyQb7udImLPvytALl1uhFdhc/NKCiaDXOjXuYeWG6Of5PKZekiaXOGlzL8 hl6qgH4xRfXqibHa0hbFGyU/a0uBnbp9RY6o0kl49XtTn5WRJFE= =kNAK -END PGP SIGNATURE End Message ---
Processed: ortools: FTBFS everywhere
Processing control commands: > tags -1 - bookworm Bug #1024790 [src:ortools] ortools: FTBFS everywhere Removed tag(s) bookworm. -- 1024790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024790 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024790: ortools: FTBFS everywhere
Control: tags -1 - bookworm This package currently has no rdeps and I do not intent to fix it for bookworm. Removing bookworm tag.
Processed: Re: Bug#1034080: sdop: fails to clean after successful build: No rule to make target 'distclean'.
Processing control commands: > tags -1 - ftbfs Bug #1034080 [src:sdop] sdop: fails to clean after successful build: No rule to make target 'distclean'. Removed tag(s) ftbfs. -- 1034080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034080 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1034080: sdop: fails to clean after successful build: No rule to make target 'distclean'.
Control: tags -1 - ftbfs On 2023-04-08 Andreas Beckmann wrote: > Source: sdop > Version: 1.00-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source twice in a row > Hi, > sdop/experimental fails to build twice in a row. (I haven't checked > whether the package in sid has the same problem.) > The first build succeeds, but the subsequent clean fails: Hello Andreas, thanks, I will fix it. FWIW I think "does not build twice" is something completely different than FTBFS and does not match the tag description. cu Andreas
Processed: tagging 965794
Processing commands for cont...@bugs.debian.org: > tags 965794 + patch Bug #965794 [python3-ooolib] python-ooolib: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 965794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028104: libboost-dev: Boost with C++20 uses unavailable std functions
Hi, I think there is a risk that something needs to be fixed, as there are no RC bugs against libboost-dev. It seems like boost1.81 is not affected by this problem. So, if somebody needs a newer library, they can take libboost1.81-dev, which is available for bookworm. I would not fix anything in boost shortly before release. Paul, if you have some use cases where a small fix is really necessary, we can discuss it. Otherwise, I would leave it as it is. Best regards, Anton Anton Am Di., 21. März 2023 um 22:03 Uhr schrieb Paul Gevers : > > Hi, > > On Sun, 08 Jan 2023 00:26:39 +0100 Andreas Beckmann wrote: > > This happens with g++-12 but not with g++-11. > > It is fixed in the boost version in experimental. > > Any chance for a *targeted* fix in bookworm? > > Paul
Bug#1034081: openbgpd: FTBFS twice in a row: src/bgpd/parse.c cannot be regenerated
Source: openbgpd Version: 7.9-1 Severity: serious Tags: ftbfs Justification: fails to build from source twice in a row Hi, openbgpd/experimental fails to build twice in a row. (I haven't checked whether the version in sid has the same problem.) The first build succeeds, a subsequent make distclean deletes src/bgpd/parse.c: ... Making distclean in src/bgpd make[2]: Entering directory '/build/openbgpd-7.9/src/bgpd' test -z "bgpd.8 bgpd.conf.5 parse.c" || rm -f bgpd.8 bgpd.conf.5 parse.c ... the following dpkg-source reports the file as missing : dpkg-source -b . dpkg-source: info: using source format '3.0 (quilt)' dpkg-source: info: verifying ./openbgpd_7.9.orig.tar.gz.asc dpkg-source: info: building openbgpd using existing ./openbgpd_7.9.orig.tar.gz dpkg-source: info: building openbgpd using existing ./openbgpd_7.9.orig.tar.gz.asc dpkg-source: info: using patch list from debian/patches/series dpkg-source: warning: ignoring deletion of file ltmain.sh, use --include-removal to override dpkg-source: warning: ignoring deletion of file Makefile.in, use --include-removal to override dpkg-source: warning: ignoring deletion of file aclocal.m4, use --include-removal to override dpkg-source: warning: ignoring deletion of file configure, use --include-removal to override dpkg-source: warning: ignoring deletion of file src/bgplgd/Makefile.in, use --include-removal to override dpkg-source: warning: ignoring deletion of file src/bgpctl/Makefile.in, use --include-removal to override dpkg-source: warning: ignoring deletion of file src/bgpd/parse.c, use --include-removal to override dpkg-source: warning: ignoring deletion of file src/bgpd/Makefile.in, use --include-removal to override dpkg-source: warning: ignoring deletion of file compat/Makefile.in, use --include-removal to override dpkg-source: warning: ignoring deletion of file include/Makefile.in, use --include-removal to override dpkg-source: warning: ignoring deletion of file m4/lt~obsolete.m4, use --include-removal to override dpkg-source: warning: ignoring deletion of file m4/ltversion.m4, use --include-removal to override dpkg-source: warning: ignoring deletion of file m4/ltsugar.m4, use --include-removal to override dpkg-source: warning: ignoring deletion of file m4/ltoptions.m4, use --include-removal to override dpkg-source: warning: ignoring deletion of file m4/libtool.m4, use --include-removal to override dpkg-source: info: building openbgpd in openbgpd_7.9-1.debian.tar.xz dpkg-source: info: building openbgpd in openbgpd_7.9-1.dsc but the second build fails: ... /bin/bash ../../ylwrap parse.y y.tab.c parse.c y.tab.h `echo parse.c | sed -e s/cc$/hh/ -e s/cpp$/hpp/ -e s/cxx$/hxx/ -e s/c++$/h++/ -e s/c$/h/` y.output parse.output -- yacc ../../ylwrap: line 175: yacc: command not found make[2]: *** [Makefile:1148: parse.c] Error 127 make[2]: *** Waiting for unfinished jobs make[2]: Leaving directory '/build/openbgpd-7.9/src/bgpd' make[1]: *** [Makefile:401: all-recursive] Error 1 make[1]: Leaving directory '/build/openbgpd-7.9' dh_auto_build: error: make -j3 returned exit code 2 Shouldn't that file be deleted and regenerated during a regular build, too? Andreas openbgpd_7.9-1_twice.log.gz Description: application/gzip
Bug#1030096: marked as done (dask.distributed: autopkgtest failure.)
Your message dated Sat, 8 Apr 2023 13:02:06 +0530 (IST) with message-id <940255638.774694.1680939126...@office.mailbox.org> and subject line Re: Bug#1030096: dask.distributed intermittent autopkgtest fail has caused the Debian Bug report #1030096, regarding dask.distributed: autopkgtest failure. 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.) -- 1030096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030096 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dask.distributed Version: 2022.12.1+ds.1-1 Severity: serious X-debbugs-cc: pkg-grass-de...@lists.alioth.debian.org,debian-science-maintain...@lists.alioth.debian.org The autopkgtest for dask.distributed is failing. https://ci.debian.net/data/autopkgtest/testing/amd64/d/dask.distributed/30859887/log.gz deploy/tests/test_local.py::test_remote_access <- ../../../../usr/lib/python3/dist-packages/distributed/deploy/tests/test_local.py INTERNALERROR> Traceback (most recent call last): INTERNALERROR> File "/usr/lib/python3/dist-packages/_pytest/main.py", line 270, in wrap_session INTERNALERROR> session.exitstatus = doit(config, session) or 0 INTERNALERROR> ^ INTERNALERROR> File "/usr/lib/python3/dist-packages/_pytest/main.py", line 324, in _main INTERNALERROR> config.hook.pytest_runtestloop(session=session) INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 265, in __call__ INTERNALERROR> return self._hookexec(self.name, self.get_hookimpls(), kwargs, firstresult) INTERNALERROR> INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 80, in _hookexec INTERNALERROR> return self._inner_hookexec(hook_name, methods, kwargs, firstresult) INTERNALERROR> ^ INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 60, in _multicall INTERNALERROR> return outcome.get_result() INTERNALERROR> INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/_result.py", line 60, in get_result INTERNALERROR> raise ex[1].with_traceback(ex[2]) INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 39, in _multicall INTERNALERROR> res = hook_impl.function(*args) INTERNALERROR> ^ INTERNALERROR> File "/usr/lib/python3/dist-packages/_pytest/main.py", line 349, in pytest_runtestloop INTERNALERROR> item.config.hook.pytest_runtest_protocol(item=item, nextitem=nextitem) INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 265, in __call__ INTERNALERROR> return self._hookexec(self.name, self.get_hookimpls(), kwargs, firstresult) INTERNALERROR> INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 80, in _hookexec INTERNALERROR> return self._inner_hookexec(hook_name, methods, kwargs, firstresult) INTERNALERROR> ^ INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 60, in _multicall INTERNALERROR> return outcome.get_result() INTERNALERROR> INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/_result.py", line 60, in get_result INTERNALERROR> raise ex[1].with_traceback(ex[2]) INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 39, in _multicall INTERNALERROR> res = hook_impl.function(*args) INTERNALERROR> ^ INTERNALERROR> File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 112, in pytest_runtest_protocol INTERNALERROR> runtestprotocol(item, nextitem=nextitem) INTERNALERROR> File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 131, in runtestprotocol INTERNALERROR> reports.append(call_and_report(item, "call", log)) INTERNALERROR>^^ INTERNALERROR> File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 222, in call_and_report INTERNALERROR> report: TestReport = hook.pytest_runtest_makereport(item=item, call=call) INTERNALERROR> INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 265, in __call__
Bug#1034080: sdop: fails to clean after successful build: No rule to make target 'distclean'.
Source: sdop Version: 1.00-1 Severity: serious Tags: ftbfs Justification: fails to build from source twice in a row Hi, sdop/experimental fails to build twice in a row. (I haven't checked whether the package in sid has the same problem.) The first build succeeds, but the subsequent clean fails: debian/rules clean dh clean dh_auto_clean make -j3 distclean make[1]: Entering directory '/build/sdop-1.00' make[1]: *** No rule to make target 'distclean'. Stop. make[1]: Leaving directory '/build/sdop-1.00' dh_auto_clean: error: make -j3 distclean returned exit code 2 make: *** [debian/rules:17: clean] Error 25 Andreas sdop_1.00-1_twice.log.gz Description: application/gzip
Bug#1034079: wheel: fails to clean after successful build: rm: cannot remove './docs/_build': Is a directory
Source: wheel Version: 0.40.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, wheel/experimental fails to build twice in a row. Cleaning after a successful build fails: dh_clean -O--buildsystem=pybuild rm -f debian/debhelper-build-stamp rm -rf debian/.debhelper/ rm -f debian/python3-wheel-whl.debhelper.log debian/python3-wheel.debhelper.log rm -f -- debian/python3-wheel.substvars debian/python3-wheel.postinst.debhelper debian/python3-wheel.prerm.debhelper debian/python-wheel-common.substvars debian/python3-wheel-whl.substvars ./docs/_build debian/files rm: cannot remove './docs/_build': Is a directory dh_clean: error: rm -f -- debian/python3-wheel.substvars debian/python3-wheel.postinst.debhelper debian/python3-wheel.prerm.debhelper debian/python-wheel-common.substvars debian/python3-wheel-whl.substvars ./docs/_build debian/files returned exit code 1 make: *** [debian/rules:12: clean] Error 25 I haven't checked the source, but this looks like debian/clean is missing a trailing / on the ./docs/_build entry. This might affect the package in sid, too, but I havent checked that. Andreas wheel_0.40.0-1_twice.log.gz Description: application/gzip
Bug#1032392: marked as done (python3-scikit-rf: import fails: AttributeError: module 'collections' has no attribute 'Sequence')
Your message dated Sat, 08 Apr 2023 06:19:12 + with message-id and subject line Bug#1032392: fixed in scikit-rf 0.15.4-2.1 has caused the Debian Bug report #1032392, regarding python3-scikit-rf: import fails: AttributeError: module 'collections' has no attribute 'Sequence' 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.) -- 1032392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032392 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-scikit-rf Version: 0.15.4-2 Severity: serious Dear Maintainer, This import fails in a sid chroot: Python 3.11.2 (main, Feb 12 2023, 00:48:52) [GCC 12.2.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> from skrf import Network Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/skrf/__init__.py", line 14, in from . import frequency File "/usr/lib/python3/dist-packages/skrf/frequency.py", line 39, in from .util import slice_domain,find_nearest_index File "/usr/lib/python3/dist-packages/skrf/util.py", line 289, in class HomoList(collections.Sequence): AttributeError: module 'collections' has no attribute 'Sequence' Kind Regards --- End Message --- --- Begin Message --- Source: scikit-rf Source-Version: 0.15.4-2.1 Done: Josef Schneider We believe that the bug you reported is fixed in the latest version of scikit-rf, 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 1032...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Josef Schneider (supplier of updated scikit-rf 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: Tue, 04 Apr 2023 19:53:06 +0200 Source: scikit-rf Architecture: source Version: 0.15.4-2.1 Distribution: unstable Urgency: medium Maintainer: Debian Electronics Team Changed-By: Josef Schneider Closes: 1032392 Changes: scikit-rf (0.15.4-2.1) unstable; urgency=medium . * Non-maintainer upload. * Add patch to import python package collections.abc instead of collections. + Fixes AttributeError when importing the package (Closes: #1032392). Checksums-Sha1: 533dfdfab684094944908f03a634a0a31ce1edd9 2011 scikit-rf_0.15.4-2.1.dsc 672e1ed514848849d0a9a69ac44fa14f5a51f5a4 5012 scikit-rf_0.15.4-2.1.debian.tar.xz 3a4bc2f9c8a1c392a19596c883826ec2ed3d9840 6802 scikit-rf_0.15.4-2.1_amd64.buildinfo Checksums-Sha256: b200ad58fedaeb56b172f09da6622271e03ce2536ede69474acdb0a9fe1b95e9 2011 scikit-rf_0.15.4-2.1.dsc 317c9fc6bb99fbf020bb2d057a868f0e9d69cb88c7d87c411004838758abe1b8 5012 scikit-rf_0.15.4-2.1.debian.tar.xz ba37dfda63ea6ef991509235a9eea49a165cfb5d9f61a37c0a464ec037610913 6802 scikit-rf_0.15.4-2.1_amd64.buildinfo Files: 0223414eff7b7b38e15dbaa7147e0947 2011 python optional scikit-rf_0.15.4-2.1.dsc 4d51ee4bedd79963aa98d54e8f254fa9 5012 python optional scikit-rf_0.15.4-2.1.debian.tar.xz 3d671351954d9c29695fddb3445a18a7 6802 python optional scikit-rf_0.15.4-2.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEMsxJDlpwsj3Wqlqyouuu0bb5AkEFAmQuXKMACgkQouuu0bb5 AkEvaA/+PEs21pTaugu+dBe046z1I7x+5SUH0gLiYOgsI60BEnCbGvie/Nafssbn SGth4yV32T4VSDBNfWojp/D2FxJpkLsLCxCIwpill3iZYn0Bu2/Cay/+X2I9n7v5 Y8/SlgpkoyWx0bFiPg3g/Bh/hwWcOd2sa52D+8FpC8BYisPpirx7tePut3GYHHx7 BMY8Ny0M5l9YomrL+I157LOmw13f8BCBUdZMfFJpkfvXKZrJKp+LbGlGdATRQPIj S9eFwGbrzxqBgcVE0PNVLtMwtAewWimQxtCz4kg7yInT5PLQtbS2d3QWr5+efhc0 uU/Uu5AjULgJ6LdYuQANKXbLE9SspNVPu0P9Djyj6ixMjaYHtmOMvRzC8G/Hn0sz 3FIKMcaF+dCzMO+qH1M8SzOrGHf7ttOpbr6fqo0XoZu8VHTa0X/ELOyOAVvwURL1 Vg5OKeJuDH6kp6CM1nTKBjIo7dyET2OGxXSlkV5e9AJMA5H8rg5Lvki6V6aDxv7S HDKbV54AeA3YS2oglCbGbsBGAXXgZMvsRsR7hJEXa3gJ3QZ2G7pm3MON5eb/qPOI MPZ/H4DCCWQBvbMkq4VM19yMzoiAZ2GEn9GxhEbDJhRzmVDHM6yeI0UHF/JqWPBT evFcUEhrJGXMTXwkrkfokIj1vv6jlMHBYgeqGtXtEPEAKyOygcw= =I6g0 -END PGP SIGNATURE End Message ---
