Bug#852964: golang-github-hashicorp-yamux: FTBFS randomly (failing tests)
Hi, Paul Gevers (2023-06-22): > I'm seeing flaky tests on ci.debian.net too [1]. Because the > unstable-to-testing migration software now blocks on regressions in testing, > flaky tests, i.e. tests that flip between passing and failing without > changes to the list of installed packages, are causing people unrelated to > your package to spend time on these tests. Therefor the Release Team > considers the issue of serious severity. > > Paul > > [1] https://ci.debian.net/packages/g/golang-github-hashicorp-yamux/ I've encountered this a few times already but got told on #debci that there were no problems at all… Right now, that page only lists 0.0+git20190923.df201c7-1 for release architectures in unstable (0.0+git20210316.a95892c-2 for riscv64 only) while that upload happened 20+ days ago. Clicking a random arch (amd64) gives me a huge list of tests for that version, the last one having run on 2023-06-05. This makes no sense to me. This also means that the two archs where the failures seem to happen (armel and armhf) have logs for failed tests with an obsolete version. That doesn't quite help. Migration to testing happened 2023-06-17, and yet the testing column has a mix of both versions. This makes no sense to me either. At least, there, we have logs for failed tests for the most recent version… At the moment, I have only been able to produce a single occurrence of a different problem: === RUN TestGoAway session_test.go:536: err: 2023/07/03 02:33:15 [WARN] yamux: frame for missing stream: Vsn:0 Type:1 Flags:1 StreamID:1 Length:0 2023/07/03 02:33:15 [ERR] yamux: Failed to write header: io: read/write on closed pipe --- FAIL: TestGoAway (0.00s) Cheers, -- Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/ signature.asc Description: PGP signature
Bug#1039724: gpgme: building underbookworm fails with no matches in python3-gpg.install
Or more specifically, why does the debian source package occasionally make the incorrect decision to build differently and use the deprecated path? On Sun, Jul 2, 2023 at 8:08 PM Ted wrote: > This is correct that my environment is not clean. Most packages are > compatible with DEB_CFLAGS_SET flags. Just to be sure, I posted the second > build log, where CFLAGS is set to be empty. > > Debuild is normally fine for package builds outside of a chroot. > I use debian packages. > > If I want to ensure that my packages build well, I can use a chroot, but > this is not actually something that a package should assume. Chroots are a > way to mitigate broad sources of brittleness, but we shouldn't be brittle. > How do we ensure this source package has no spurious imports from the > environment? > -- -Theodoric
Bug#1039724: gpgme: building underbookworm fails with no matches in python3-gpg.install
This is correct that my environment is not clean. Most packages are compatible with DEB_CFLAGS_SET flags. Just to be sure, I posted the second build log, where CFLAGS is set to be empty. Debuild is normally fine for package builds outside of a chroot. I use debian packages. If I want to ensure that my packages build well, I can use a chroot, but this is not actually something that a package should assume. Chroots are a way to mitigate broad sources of brittleness, but we shouldn't be brittle. How do we ensure this source package has no spurious imports from the environment?
Processed: Re: Bug#1039498: gir1.2-harfbuzz-0.0: missing dependency on libharfbuzz0b
Processing commands for cont...@bugs.debian.org: > block 1039498 by 1039714 Bug #1039498 [libharfbuzz-dev] gir1.2-harfbuzz-0.0: missing dependency on libharfbuzz0b 1039498 was not blocked by any bugs. 1039498 was not blocking any bugs. Added blocking bug(s) of 1039498: 1039714 > quit Stopping processing here. Please contact me if you need assistance. -- 1039498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040141: FTBFS: FAIL: TestCheckoutGit
On Sun, Jul 02, 2023 at 01:59:01PM +, Bastien Roucariès wrote: > Source: docker.io > Version: 18.09.1+dfsg1-7.1+deb10u3 > Severity: serious > Justification: FTBFS > X-Debbugs-Cc: debian-...@lists.debian.org > > Dear Maintainer, > > The current security version FTBFS for me with As a general note, maintainers are no longer responsible for the version in LTS. > -- FAIL: TestCheckoutGit (0.52s) > gitutils_test.go:188: assertion failed: error is not nil: exit status 128 > > > I am currently debugging this regression. Trying in reproducible builds, buster built but bullseye failed: https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/amd64/docker.io.html The error message looks like #1024506. > Bastien cu Adrian
Bug#1040167: marked as done (openjdk-8-jre-headless: version 8u382~b04-1 depends on libjpeg8 which is not in Debian)
Your message dated Sun, 02 Jul 2023 22:39:05 + with message-id and subject line Bug#1040167: fixed in openjdk-8 8u382~b04-2 has caused the Debian Bug report #1040167, regarding openjdk-8-jre-headless: version 8u382~b04-1 depends on libjpeg8 which is not in Debian 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.) -- 1040167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040167 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openjdk-8-jre-headless Version: 8u382~b04-1 Severity: important Dear Maintainer, Updating from 8u372-ga-1 which was the previous version in unstable is not possible because openjdk-8-jre-headless_8e382~b04-1 depends on libjpeg8 However libjpeg8 is not to be found in Debian Expected behaviour: correct dependencies or adding the missing libjpeg8 to Debian? -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (991, 'stable-security'), (991, 'stable'), (990, 'proposed- updates'), (390, 'oldstable-security'), (390, 'oldstable'), (389, 'oldstable- updates'), (380, 'oldoldstable'), (379, 'oldoldstable-updates'), (370, 'oldoldstable'), (95, 'testing'), (94, 'unstable'), (93, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr:en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openjdk-8-jre-headless depends on: ii ca-certificates-java 20230103 ii java-common 0.74 ii libc6 2.36-9 ii libcups2 2.4.2-3 ii libfontconfig12.14.1-4 ii libfreetype6 2.12.1+dfsg-5 ii libgcc-s1 12.2.0-14 ii libjpeg62-turbo 1:2.1.5-2 ii liblcms2-22.14-2 ii libnss3 2:3.87.1-1 ii libpcsclite1 1.9.9-2 ii libstdc++612.2.0-14 ii libx11-6 2:1.8.4-2+deb12u1 ii libxext6 2:1.3.4-1+b1 ii libxi62:1.8-1+b1 ii libxrender1 1:0.9.10-1.1 ii libxtst6 2:1.2.3-1.1 ii util-linux2.38.1-5+b1 ii zlib1g1:1.2.13.dfsg-1 openjdk-8-jre-headless recommends no packages. Versions of packages openjdk-8-jre-headless suggests: ii fonts-dejavu-extra2.37-6 pn fonts-indic pn fonts-ipafont-gothic pn fonts-ipafont-mincho pn fonts-wqy-microhei pn fonts-wqy-zenhei ii libnss-mdns 0.15.1-3 -- no debconf information --- End Message --- --- Begin Message --- Source: openjdk-8 Source-Version: 8u382~b04-2 Done: Thorsten Glaser We believe that the bug you reported is fixed in the latest version of openjdk-8, 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 1040...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Glaser (supplier of updated openjdk-8 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: SHA384 Format: 1.8 Date: Mon, 03 Jul 2023 00:17:03 +0200 Source: openjdk-8 Architecture: source Version: 8u382~b04-2 Distribution: unstable Urgency: medium Maintainer: Java Maintenance Changed-By: Thorsten Glaser Closes: 1040167 1040181 Changes: openjdk-8 (8u382~b04-2) unstable; urgency=medium . * Rewrite codename-based if(n)eqs, so they fail safer (Closes: #1040167) * Maybe fix sparc64 Linux build failure * Do not run check for nōn-Hotspot architectures (Closes: #1040181) Checksums-Sha1: 3d77a63a49d70acb0619bcb01cdcdafdbd0fb159 4562 openjdk-8_8u382~b04-2.dsc 5113855e6b61388404d92ebd29ed8f77430b7428 183088 openjdk-8_8u382~b04-2.debian.tar.xz Checksums-Sha256: 6df5be61263e00296d4f0a0b7a5de4616ed1e1d068e0ebe9069c032cd312190a 4562 openjdk-8_8u382~b04-2.dsc 1619ca90373140fb4eb6daaf93e6037b6d9dbe52e2eb633b62005ae4356b1486 183088 openjdk-8_8u382~b04-2.debian.tar.xz Files: 7284308dc663033b384f4380a998020d 4562 java optional openjdk-8_8u382~b04-2.dsc 972d37000c6179da49b317da0a713f67 183088 java optional
Bug#1040129: marked as done (slurm-wlm: binary-any FTBFS)
Your message dated Sun, 02 Jul 2023 22:11:00 + with message-id and subject line Bug#1040129: fixed in slurm-wlm 23.02.3-2 has caused the Debian Bug report #1040129, regarding slurm-wlm: 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.) -- 1040129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040129 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: slurm-wlm Version: 23.02.3-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=slurm-wlm=23.02.3-1 ... dh_missing -a -O--builddirectory dh_missing: warning: usr/lib/aarch64-linux-gnu/slurm-wlm/src/sattach/sattach.wrapper.c exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/usr/lib/x86_64-linux-gnu/slurm-wlm/src/sattach/sattach.wrapper.c") dh_missing: warning: usr/lib/aarch64-linux-gnu/slurm-wlm/src/srun/srun.wrapper.c exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/usr/lib/x86_64-linux-gnu/slurm-wlm/src/srun/srun.wrapper.c") dh_missing: error: missing files, aborting While detecting missing files, dh_missing noted some files with a similar name to those that were missing. This error /might/ be resolved by replacing references to the missing files with the similarly named ones that dh_missing found - assuming the content is identical. As an example, you might want to replace: * debian/tmp/usr/lib/x86_64-linux-gnu/slurm-wlm/src/sattach/sattach.wrapper.c with: * usr/lib/aarch64-linux-gnu/slurm-wlm/src/sattach/sattach.wrapper.c in a file in debian/ or as argument to one of the dh_* tools called from debian/rules. (Note it is possible the paths are not used verbatim but instead directories containing or globs matching them are used instead) Alternatively, add the missing file to debian/not-installed if it cannot and should not be used. The following debhelper tools have reported what they installed (with files per package) * dh_install: libpam-slurm (1), libpam-slurm-adopt (1), libpam-slurm-adopt-dev (2), libpam-slurm-dev (2), libpmi0 (2), libpmi0-dev (4), libpmi2-0 (2), libpmi2-0-dev (4), libslurm-dev (9), libslurm-perl (5), libslurm39 (2), libslurmdb-perl (3), slurm-client (19), slurm-client-emulator (17), slurm-wlm (0), slurm-wlm-basic-plugins (111), slurm-wlm-basic-plugins-dev (218), slurm-wlm-doc (0), slurm-wlm-elasticsearch-plugin (1), slurm-wlm-elasticsearch-plugin-dev (2), slurm-wlm-emulator (3), slurm-wlm-hdf5-plugin (2), slurm-wlm-hdf5-plugin-dev (2), slurm-wlm-influxdb-plugin (1), slurm-wlm-influxdb-plugin-dev (2), slurm-wlm-ipmi-plugins (2), slurm-wlm-ipmi-plugins-dev (4), slurm-wlm-jwt-plugin (1), slurm-wlm-jwt-plugin-dev (2), slurm-wlm-kafka-plugin (1), slurm-wlm-kafka-plugin-dev (2), slurm-wlm-mysql-plugin (2), slurm-wlm-mysql-plugin-dev (4), slurm-wlm-plugins (0), slurm-wlm-plugins-dev (0), slurm-wlm-rrd-plugin (1), slurm-wlm-rrd-plugin-dev (2), slurm-wlm-rsmi-plugin (1), slurm-wlm-rsmi-plugin-dev (2), slurm-wlm-torque (10), slurmctld (1), slurmd (2), slurmdbd (1), slurmrestd (1), sview (1) * dh_installdocs: libpam-slurm (1), libpam-slurm-adopt (1), libpam-slurm-adopt-dev (0), libpam-slurm-dev (0), libpmi0 (0), libpmi0-dev (0), libpmi2-0 (0), libpmi2-0-dev (0), libslurm-dev (0), libslurm-perl (0), libslurm39 (0), libslurmdb-perl (0), slurm-client (0), slurm-client-emulator (0), slurm-wlm (4), slurm-wlm-basic-plugins (0), slurm-wlm-basic-plugins-dev (0), slurm-wlm-doc (1), slurm-wlm-elasticsearch-plugin (0), slurm-wlm-elasticsearch-plugin-dev (0), slurm-wlm-emulator (0), slurm-wlm-hdf5-plugin (0), slurm-wlm-hdf5-plugin-dev (0), slurm-wlm-influxdb-plugin (0), slurm-wlm-influxdb-plugin-dev (0), slurm-wlm-ipmi-plugins (0), slurm-wlm-ipmi-plugins-dev (0), slurm-wlm-jwt-plugin (0), slurm-wlm-jwt-plugin-dev (0), slurm-wlm-kafka-plugin (0), slurm-wlm-kafka-plugin-dev (0), slurm-wlm-mysql-plugin (0), slurm-wlm-mysql-plugin-dev (0), slurm-wlm-plugins (0), slurm-wlm-plugins-dev (0), slurm-wlm-rrd-plugin (0), slurm-wlm-rrd-plugin-dev (0), slurm-wlm-rsmi-plugin (0), slurm-wlm-rsmi-plugin-dev (0), slurm-wlm-torque (0), slurmctld (2), slurmd (0), slurmdbd (0), slurmrestd (0), sview (0) * dh_installexamples: libpam-slurm (0), libpam-slurm-adopt (0), libpam-slurm-adopt-dev (0), libpam-slurm-dev (0), libpmi0 (0), libpmi0-dev (0), libpmi2-0 (0), libpmi2-0-dev (0), libslurm-dev (0), libslurm-perl (0), libslurm39 (0), libslurmdb-perl (0),
Bug#1040167: marked as done (openjdk-8-jre-headless: version 8u382~b04-1 depends on libjpeg8 which is not in Debian)
Your message dated Sun, 02 Jul 2023 21:49:53 + with message-id and subject line Bug#1040167: fixed in openjdk-8 8u382~b04-2~binfix1 has caused the Debian Bug report #1040167, regarding openjdk-8-jre-headless: version 8u382~b04-1 depends on libjpeg8 which is not in Debian 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.) -- 1040167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040167 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openjdk-8-jre-headless Version: 8u382~b04-1 Severity: important Dear Maintainer, Updating from 8u372-ga-1 which was the previous version in unstable is not possible because openjdk-8-jre-headless_8e382~b04-1 depends on libjpeg8 However libjpeg8 is not to be found in Debian Expected behaviour: correct dependencies or adding the missing libjpeg8 to Debian? -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (991, 'stable-security'), (991, 'stable'), (990, 'proposed- updates'), (390, 'oldstable-security'), (390, 'oldstable'), (389, 'oldstable- updates'), (380, 'oldoldstable'), (379, 'oldoldstable-updates'), (370, 'oldoldstable'), (95, 'testing'), (94, 'unstable'), (93, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr:en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openjdk-8-jre-headless depends on: ii ca-certificates-java 20230103 ii java-common 0.74 ii libc6 2.36-9 ii libcups2 2.4.2-3 ii libfontconfig12.14.1-4 ii libfreetype6 2.12.1+dfsg-5 ii libgcc-s1 12.2.0-14 ii libjpeg62-turbo 1:2.1.5-2 ii liblcms2-22.14-2 ii libnss3 2:3.87.1-1 ii libpcsclite1 1.9.9-2 ii libstdc++612.2.0-14 ii libx11-6 2:1.8.4-2+deb12u1 ii libxext6 2:1.3.4-1+b1 ii libxi62:1.8-1+b1 ii libxrender1 1:0.9.10-1.1 ii libxtst6 2:1.2.3-1.1 ii util-linux2.38.1-5+b1 ii zlib1g1:1.2.13.dfsg-1 openjdk-8-jre-headless recommends no packages. Versions of packages openjdk-8-jre-headless suggests: ii fonts-dejavu-extra2.37-6 pn fonts-indic pn fonts-ipafont-gothic pn fonts-ipafont-mincho pn fonts-wqy-microhei pn fonts-wqy-zenhei ii libnss-mdns 0.15.1-3 -- no debconf information --- End Message --- --- Begin Message --- Source: openjdk-8 Source-Version: 8u382~b04-2~binfix1 Done: Thorsten Glaser We believe that the bug you reported is fixed in the latest version of openjdk-8, 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 1040...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Glaser (supplier of updated openjdk-8 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: SHA384 Format: 1.8 Date: Sun, 02 Jul 2023 21:41:14 +0200 Source: openjdk-8 Binary: openjdk-8-dbg openjdk-8-demo openjdk-8-jdk openjdk-8-jdk-headless openjdk-8-jre openjdk-8-jre-headless openjdk-8-jre-zero Architecture: source amd64 arm64 armel armhf i386 ppc64el s390x Version: 8u382~b04-2~binfix1 Distribution: unstable Urgency: medium Maintainer: Thorsten Glaser Changed-By: Thorsten Glaser Closes: 1040167 Description: openjdk-8-dbg - Java runtime based on OpenJDK (debugging symbols) openjdk-8-demo - Java runtime based on OpenJDK (demos and examples) openjdk-8-jdk - OpenJDK Development Kit (JDK) openjdk-8-jdk-headless - OpenJDK Development Kit (JDK) (headless) openjdk-8-jre - OpenJDK Java runtime, using openjdk-8-jre-headless - OpenJDK Java runtime, using (headless) openjdk-8-jre-zero - Alternative JVM for OpenJDK, using Zero Changes: openjdk-8 (8u382~b04-2~binfix1) unstable; urgency=medium . * Rewrite codename-based if(n)eqs, so they fail safer (Closes: #1040167) * first (fake) upload . This is actually the
Bug#1040167: [aure...@debian.org: Re: Fwd: (buildd chroot bug) Re: Bug#1040167: openjdk-8-jre-headless: version 8u382~b04-1 depends on libjpeg8 which is not in Debian]
I realized that message has been forwarded to *all* buildd maintainers, and I answered there. So let me forward the answer to the bug report. - Message transféré de Aurelien Jarno - From: Aurelien Jarno To: Thorsten Glaser Cc: buildd-maintain...@buildd.debian.org User-Agent: Mutt/2.2.9 (2022-11-12) Date: Sun, 2 Jul 2023 23:02:38 +0200 Subject: Re: Fwd: (buildd chroot bug) Re: Bug#1040167: openjdk-8-jre-headless: version 8u382~b04-1 depends on libjpeg8 which is not in Debian Message-ID: [ tl;dr for buildd-maintainers: nothing to do. ] Hi, On 2023-07-02 21:44, Thorsten Glaser wrote: > Hi, > > please check the footnote below. Thanks! > > -- Forwarded message -- > Message-ID: <2d85d8b1-45e2-d6a8-5088-7fd838b7...@tarent.de> > Date: Sun, 2 Jul 2023 20:20:16 +0200 (CEST) > > Dixi quod… > > >Indeed. Weird. > > > >Thanks for reporting, I’ll have two or three looks at it… fixing that > >is going to be… fun. Not. > > OK so first analysis is showing the cause of the problem: > > • the buildd chroots for sid/unstable do not identify themselves as > sid/unstable but instead as trixie/testing, which is a bug onto > itself¹ No the chroots do not identify themselves. I guess you check the output of "lsb_release -a". If you believe the output is not correct, please report the bug to the lsb-release package. > however if the buildd chroot bug could be fixed, I’d be glad. There is nothing to fix on the buildd chroot side, please fix your debian/rules script instead. > ① sid buildd chroots should save the following content… > PRETTY_NAME="Debian GNU/Linux sid" > NAME="Debian GNU/Linux" > ID=debian > HOME_URL="https://www.debian.org/; > SUPPORT_URL="https://www.debian.org/support; > BUG_REPORT_URL="https://bugs.debian.org/; > VERSION_ID=unstable > VERSION_CODENAME=sid > … as /usr/lib/os-release.sid (in the chroot) and run… > # dpkg-divert --rename --divert /usr/lib/os-release.dpkg-dist \ > --add /usr/lib/os-release > # ln -sfT os-release.sid /usr/lib/os-release > … in the chroot, so the reported lsb_release is correct. They used > to have this in /etc/lsb-release, but the lsb-release program no > longer uses that. That's plainly wrong, that's not the job of a buildd to configure that. The chroots are just created using debootstrap --variant=buildd, which is basically a minimal chroot with build-essential. There shouldn't be any further visible configuration to the chroot, as your package is supposed to build the same way on a normal installation outside of a chroot. The functionality you describe should just come by installing additional packages. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net - Fin du message transféré - -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
Bug#1039883: The issue impacts SSD disks as well
I've just faced this issue on the SSD disk as well, so it seems that the probability is just lower on a speedier disk.
Processed: severity of 1040167 is serious
Processing commands for cont...@bugs.debian.org: > severity 1040167 serious Bug #1040167 [openjdk-8-jre-headless] openjdk-8-jre-headless: version 8u382~b04-1 depends on libjpeg8 which is not in Debian Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1040167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040167 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035820: marked as done (9base: leaves entries in /etc/shells after upgrade from bullseye)
Your message dated Sun, 02 Jul 2023 20:49:58 + with message-id and subject line Bug#1035820: fixed in debianutils 5.7-0.5 has caused the Debian Bug report #1035820, regarding 9base: leaves entries in /etc/shells after upgrade from bullseye 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.) -- 1035820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035820 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: 9base Version: 1:6-13 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package leaves modifications in /etc/shells after upgrading from bullseye to bookworm and purging the package. 9base/bullseye called add-shell/remove-shell in its postinst/postrm. 9base/bookworm no longer does that, but it also does not clean up the leftover entries from bullseye in its postinst. >From the attached log (scroll to the bottom...): 0m45.2s ERROR: FAIL: After purging files have been modified: /etc/shellsnot owned The following (untested) snippet for the postinst should perform the neccessary cleanup: if [ "$1" = "install" ] || [ "$1" = "upgrade" ]; then if dpkg --compare-versions "$2" lt-nl "1:6-14~" ; then remove-shell /bin/rc remove-shell /usr/lib/plan9/bin/rc fi fi cheers, Andreas 9base_1:6-13.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: debianutils Source-Version: 5.7-0.5 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of debianutils, 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. Andreas Beckmann (supplier of updated debianutils 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, 22 Jun 2023 21:59:33 +0200 Source: debianutils Architecture: source Version: 5.7-0.5 Distribution: unstable Urgency: medium Maintainer: Clint Adams Changed-By: Andreas Beckmann Closes: 1035820 Changes: debianutils (5.7-0.5) unstable; urgency=medium . * Non-maintainer upload. * update-shells: Do not create duplicate entries in /etc/shells. * update-shells: Manage (/usr)/bin/sh in the state file. * update-shells: Fix canonicalization of shells in aliased locations. (Closes: #1035820) Checksums-Sha1: fd2943022e218ce5c3a979a2d350587f58d484a7 1912 debianutils_5.7-0.5.dsc b194c682d51b2df512dcb672bfd962cbe4deaa66 23072 debianutils_5.7-0.5.debian.tar.xz 82bcb0b37b38639194ce8c58fe4764cdf2f4fc33 4734 debianutils_5.7-0.5_source.buildinfo Checksums-Sha256: 7b11bf08638162c9da93f867441e287bf1966592a371592359139b1ec37c6f5e 1912 debianutils_5.7-0.5.dsc bfca15e17b97016e445ba1b4124c4cbd0b075c8809699ded6403586403a31e03 23072 debianutils_5.7-0.5.debian.tar.xz 8e9793bf565b7dd6bf9e8ca8e05b632007217409a21604f196d47b5b28ca767a 4734 debianutils_5.7-0.5_source.buildinfo Files: e90d5db9c1daf200fd2ceb52b1ba02a1 1912 utils required debianutils_5.7-0.5.dsc bb1cc082e2ba6486b3bf230645f7ef46 23072 utils required debianutils_5.7-0.5.debian.tar.xz db9786f8882a319abf4003a6ad6d4d41 4734 utils required debianutils_5.7-0.5_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmSUqUMQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCHf9EACCJ60oidu7KQx4Aau0X2yn+4oaJTzuSTq6 W/8qNA/QiagYHS3GhmCzpWHX1vInrPGLK+xBx3khMUuho/HsrPbvgpkAz/6TfTv5 3rZuohXjvzVc0+b+MublKxteHTbsQaPpxTwcPrtB7Zqa7eJClxsXWl0GQWje8zN7 NQI+oOJtYegCCmenCWasglnk1lCfMaBeE4dEBR2NU7VYZb6+t/GfaWHcufCG9e3z g6QAdV5ppBwSQVjvDVzJ2vj6FaW7gsvGoqnv6YHIfZNpk9z5pxcI/flpYMjlFt4o tDwFISflpymDqMoq7tgjHRstPvDLMNgwrFcGT6vsFGWh7NcIuJU8qa3uOv2Hfp6B qRy7B5uILeQsfF7Y0pZU0GzlTq91lxr21D7hBxBn22wyOxUZ5RytramGUAmyRR7X jpazSVVJGKlXDL6SkPM3VgF4GzC2o0BkGe89aidjAT7vbwDO3a2L0LTPt5ulNFTk kyEKRh394ceiwPU0OukCLPWuYwsRW45feY0xU0Uysb2WiCw4Rbh7kLoYy0ca8miT PtJox6fS2PbD99akib/T+gRdOGCjDf2RiMlR6QB6A5anTxy5EBs+y84HF3EoL5Ds 6QQXPHVphFz7hZkA0KVV+97vkjn/O4mjVyPz5btS5xXw9e7Rt/7Gr45UdCPgVt7j +/uXxPD/Mw== =Surd -END PGP SIGNATURE End Message ---
Bug#1000031: marked as done (freeradius: depends on obsolete pcre3 library)
Your message dated Sun, 02 Jul 2023 20:51:22 + with message-id and subject line Bug#131: fixed in freeradius 3.2.3+dfsg-2 has caused the Debian Bug report #131, regarding freeradius: depends on obsolete pcre3 library 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.) -- 131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: freeradius Severity: important User: matthew-pcre...@debian.org Usertags: obsolete-pcre3 Dear maintainer, Your package still depends on the old, obsolete PCRE3[0] libraries (i.e. libpcre3-dev). This has been end of life for a while now, and upstream do not intend to fix any further bugs in it. Accordingly, I would like to remove the pcre3 libraries from Debian, preferably in time for the release of Bookworm. The newer PCRE2 library was first released in 2015, and has been in Debian since stretch. Upstream's documentation for PCRE2 is available here: https://pcre.org/current/doc/html/ Many large projects that use PCRE have made the switch now (e.g. git, php); it does involve some work, but we are now at the stage where PCRE3 should not be used, particularly if it might ever be exposed to untrusted input. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00176.html Regards, Matthew [0] Historical reasons mean that old PCRE is packaged as pcre3 in Debian --- End Message --- --- Begin Message --- Source: freeradius Source-Version: 3.2.3+dfsg-2 Done: Bernhard Schmidt We believe that the bug you reported is fixed in the latest version of freeradius, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bernhard Schmidt (supplier of updated freeradius 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 Jul 2023 22:23:21 +0200 Source: freeradius Architecture: source Version: 3.2.3+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian FreeRADIUS Packaging Team Changed-By: Bernhard Schmidt Closes: 131 Changes: freeradius (3.2.3+dfsg-2) unstable; urgency=medium . * Don't build against libpcre3 (Closes: #131) FreeRADIUS will use Posix regular expressions Checksums-Sha1: 3d5153d259074be3de88992552f8916e3dd0da43 3599 freeradius_3.2.3+dfsg-2.dsc 5cdbb45a7519037e8a6d3af3a1ca8e5eba177963 57380 freeradius_3.2.3+dfsg-2.debian.tar.xz ca3d326b25d22962c2a8ab823580106bce292442 19498 freeradius_3.2.3+dfsg-2_amd64.buildinfo Checksums-Sha256: 28e37adcaf0459f616b9fc63e2ad158de16490c0cccef67858a968dd6131dae0 3599 freeradius_3.2.3+dfsg-2.dsc 73a2b77999a0049df1013ba462d7409ec98f660c3e9d17b34b4b56e2e08e6d95 57380 freeradius_3.2.3+dfsg-2.debian.tar.xz a80b7d0113a81a62f644666da53b9b6816c15f86987fc52e5ec8fcbf55fbf322 19498 freeradius_3.2.3+dfsg-2_amd64.buildinfo Files: 641d099bb826e5c0acfa6d72ca10feef 3599 net optional freeradius_3.2.3+dfsg-2.dsc 508bde1280ba426dd1bd200cc94dee5c 57380 net optional freeradius_3.2.3+dfsg-2.debian.tar.xz faff1bdc7df7d64c133f699eca1c6926 19498 net optional freeradius_3.2.3+dfsg-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE1uAexRal3873GVbTd1B55bhQvJMFAmSh3nYRHGJlcm5pQGRl Ymlhbi5vcmcACgkQd1B55bhQvJMrfg//W0vd8ogWBWhXdheUgAwBhloGK2F7b3zH Xl1N7qx/ZTADk6LTssdqGuAgP5TwD+4VWKzUWA3TvDqL+qpvi6+l/DrTv88Sg5qJ 8bZ+ro4FMSWw/6sqRV0uzngT/mgGzcK5nBF75W4snTJ8NQ2fTLHDFJ/IvgKwh1u0 2+Iq3r9FKk2X2+/NKcpP3gkbazY9VDGNwgZWmVKurzuZ2RU9Lyz+BMXRSmLmpMFD 3JeNUCqvrOOy2HxhtIPXBImiwof395bhafxtk1+jOpTBCfRAkLuPPJmPmm5LHiVi yhrH+7B5Em8wgB9/TsGSMTcd7qKuhLs4cPyaorhx1X1s70Kc1STOaMGZ3IvhGKv/ R9yFHcVdQ/J4E4lRbq6LcYvgTxEMCyy6kcClnTwfGiUh9RiIGnCzlmqVkWiYfDqv JYMg54vH/dgHU0BKBxQXUEv3tG8rl0hRMFPEYjkwLcx4mH6OVJw7kOloHa8l1uwy 8YanUpkxyqUGtPoEhFZjMBJVSV/FgU8Fv1tVvtdymyd5CsFiNfbPDI5Ix6sBlicO yj/07FCnY4p1S3LJO1UVZKiMHRdFTG0QWMNwquUC4pWNmm+fAJPonRDIrC3SjiZE 1QU+qsPjOCDUxoNMTali9VdMggGTl9zpmjmt31DqtdcLfNPOMz+lzbovuNRQoqyp grPQMfkwZ1M= =6ez4 -END PGP SIGNATURE End Message ---
Bug#1031680: marked as done (uranium: FTBFS against python3.11: wants python3.10 instead)
Your message dated Sun, 02 Jul 2023 20:32:17 + with message-id and subject line Bug#1031680: fixed in uranium 5.0.0-2 has caused the Debian Bug report #1031680, regarding uranium: FTBFS against python3.11: wants python3.10 instead 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.) -- 1031680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: uranium Version: 5.0.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source uranium/experimental started to FTBFS after Python 3.11 was made the default (and only) Python interpreter: dh_auto_configure -- -DGETTEXT_MSGINIT_EXECUTABLE=msginit -DGETTEXT_MSGCONV_EXECUTABLE=msgconv -DGETTEXT_MSGMERGE_EXECUTABLE=msgmerge -DCURA_BINARY_DATA_DIRECTORY=/usr/share/uranium cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DGETTEXT_MSGINIT_EXECUTABLE=msginit -DGETTEXT_MSGCONV_EXECUTABLE=msgconv -DGETTEXT_MSGMERGE_EXECUTABLE=msgmerge -DCURA_BINARY_DATA_DIRECTORY=/usr/share/uranium .. CMake Error at /usr/share/cmake-3.25/Modules/FindPackageHandleStandardArgs.cmake:230 (message): Could NOT find Python (missing: Python_EXECUTABLE Interpreter) (found suitable exact version "3.10") Reason given by package: Interpreter: Wrong version for the interpreter "/bin/python3" Call Stack (most recent call first): /usr/share/cmake-3.25/Modules/FindPackageHandleStandardArgs.cmake:600 (_FPHSA_FAILURE_MESSAGE) /usr/share/cmake-3.25/Modules/FindPython/Support.cmake:3240 (find_package_handle_standard_args) /usr/share/cmake-3.25/Modules/FindPython.cmake:519 (include) CMakeLists.txt:21 (find_package) -- Configuring incomplete, errors occurred! Andreas --- End Message --- --- Begin Message --- Source: uranium Source-Version: 5.0.0-2 Done: Christoph Berg We believe that the bug you reported is fixed in the latest version of uranium, 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 1031...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Berg (supplier of updated uranium 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: Sun, 02 Jul 2023 19:37:37 + Source: uranium Architecture: source Version: 5.0.0-2 Distribution: unstable Urgency: medium Maintainer: Debian 3-D Printing Packages <3dprinter-gene...@lists.alioth.debian.org> Changed-By: Christoph Berg Closes: 1031680 Changes: uranium (5.0.0-2) unstable; urgency=medium . * Compile against current python version. (Closes: #1031680) Checksums-Sha1: 0b9869c3d506c24ff82ddb08308c18e7d95fb6ae 2234 uranium_5.0.0-2.dsc c55d60d0bc871043bbede00a19db51b2104d10db 8236 uranium_5.0.0-2.debian.tar.xz Checksums-Sha256: 94168b6925a20f4fd323716458443900ec8a3dc849a5060d1c7d37bbc5962998 2234 uranium_5.0.0-2.dsc 6bba7dc4f3acefa6c47c21a5064b3650712565707476bc528c36246002e6085b 8236 uranium_5.0.0-2.debian.tar.xz Files: 3a790f4428d272cab26c4bddb7b1c512 2234 python optional uranium_5.0.0-2.dsc 36d746fb55f6c236564c00afdd7b00e7 8236 python optional uranium_5.0.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAmSh1SsACgkQTFprqxLS p65LxQ//QyCw2F3NnlIXo/P18kUCvKcW7GGwJU0YGdLNG5au0YcRSSC0tuQJo0xZ WOriqSmP0Kow1/W7hiVhA1tgdTj4GSwJh3guiWhYQLuG9REFEAzMWTv7F1xQwj5W qPXnAT76axf3ed8DEZWwo5fnRyyTpl8qfOzG5aUV8EqVIs1brhYa9a14Q2s0vPE3 DsmHwJyafPpB8nAnfJoPboJ0e0892kXPaPHFzBVaGTzvfE67T7SS2GVP1MPaMUyy ZIaGNKZu6p+8k3KqxKuIOElZboz+OxApColhz/zSwlkgxnwQWPZVPnq8Ymwx3klc NCNNeoDjKrU8jqqGy2VqJD18GA6EseIqwhs4u/amOdro6WIB7PC+2PSBGAd8Q8ue TQeOH/y3E3hHORzxq+GGcqfLPiLF13HlxzHyAAzAR3VmLeB351Hv4SAIEDpoXPwc sLC+qlruFShNsv5S28TzpCgep6ZZl92A1oMHSXs296L8DJrKJPKeZUtw5A87ea/v
Processed: Bug#1031680 marked as pending in uranium
Processing control commands: > tag -1 pending Bug #1031680 [src:uranium] uranium: FTBFS against python3.11: wants python3.10 instead Added tag(s) pending. -- 1031680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1031680: marked as pending in uranium
Control: tag -1 pending Hello, Bug #1031680 in uranium 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/3dprinting-team/uranium/-/commit/8e6f6055c13fcc1b5b25aa5a207ef8d5dab03a4c Compile against current python version. (Closes: #1031680) (this message was generated automatically) -- Greetings https://bugs.debian.org/1031680
Processed: bts
Processing commands for cont...@bugs.debian.org: > reassign 1040051 pymodbus Bug #1040051 [src:prompt-toolkit, src:pymodbus] autopkgtest err "Task was destroyed but it is pending!" Bug reassigned from package 'src:prompt-toolkit, src:pymodbus' to 'pymodbus'. No longer marked as found in versions pymodbus/3.0.0-7. Ignoring request to alter fixed versions of bug #1040051 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1040051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040051 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bts
Processing commands for cont...@bugs.debian.org: > notfound 1040051 prompt-toolkit Bug #1040051 [src:prompt-toolkit, src:pymodbus] autopkgtest err "Task was destroyed but it is pending!" The source 'prompt-toolkit' and version 'prompt-toolkit' do not appear to match any binary packages The source 'pymodbus' and version 'prompt-toolkit' do not appear to match any binary packages Ignoring request to alter found versions of bug #1040051 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1040051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040051 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1000016 is forwarded to https://github.com/mp3splt/mp3splt/issues/366
Processing commands for cont...@bugs.debian.org: > forwarded 116 https://github.com/mp3splt/mp3splt/issues/366 Bug #116 [src:mp3splt] mp3splt: depends on obsolete pcre3 library Set Bug forwarded-to-address to 'https://github.com/mp3splt/mp3splt/issues/366'. > thanks Stopping processing here. Please contact me if you need assistance. -- 116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=116 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: prompt-toolkit breaks pymodbus autopkgtest: output on stderr: Task was destroyed but it is pending!
Processing commands for cont...@bugs.debian.org: > notfound 1040051 prompt-toolkit/3.0.38-2 Bug #1040051 [src:prompt-toolkit, src:pymodbus] prompt-toolkit breaks pymodbus autopkgtest: output on stderr: Task was destroyed but it is pending! No longer marked as found in versions prompt-toolkit/3.0.38-2. > retitle 1040051 autopkgtest err "Task was destroyed but it is pending!" Bug #1040051 [src:prompt-toolkit, src:pymodbus] prompt-toolkit breaks pymodbus autopkgtest: output on stderr: Task was destroyed but it is pending! Changed Bug title to 'autopkgtest err "Task was destroyed but it is pending!"' from 'prompt-toolkit breaks pymodbus autopkgtest: output on stderr: Task was destroyed but it is pending!'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1040051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040051 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040051: prompt-toolkit breaks pymodbus autopkgtest: output on stderr: Task was destroyed but it is pending!
notfound 1040051 prompt-toolkit/3.0.38-2 retitle 1040051 autopkgtest err "Task was destroyed but it is pending!" thanks Hi, thanks for reporting this. however, I can't reproduce it - I don't think the bug is caused by prompt-toolkit but by anthing other that is different between testing and unstable. Also the error message doesn't sound like prompt-toolkit is involved here at all. Regards, Daniel
Processed: fixed 1040141 in 20.10.5+dfsg1-1
Processing commands for cont...@bugs.debian.org: > fixed 1040141 20.10.5+dfsg1-1 Bug #1040141 [src:docker.io] FTBFS: FAIL: TestCheckoutGit Marked as fixed in versions docker.io/20.10.5+dfsg1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1040141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040141 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037962: marked as done (chaos-marmosets: autopkgtest failure on arm64 and ppc64el)
Your message dated Sun, 02 Jul 2023 15:34:42 + with message-id and subject line Bug#1037962: fixed in chaos-marmosets 0.1.2-2 has caused the Debian Bug report #1037962, regarding chaos-marmosets: autopkgtest failure on arm64 and ppc64el 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.) -- 1037962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037962 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: chaos-marmosets Version: 0.1.2-1 Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package chaos-marmosets, great. However, it fails on arm64 and ppc64el. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=chaos-marmosets https://ci.debian.net/data/autopkgtest/testing/arm64/c/chaos-marmosets/32979373/log.gz I: Test that divide-by-zero crashes... Trace/breakpoint trap I: divide-by-zero exit code: 133 (expected: 128 + 4 for SIGILL) autopkgtest [21:14:22]: test crashes OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: chaos-marmosets Source-Version: 0.1.2-2 Done: Benjamin Drung We believe that the bug you reported is fixed in the latest version of chaos-marmosets, 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 1037...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Benjamin Drung (supplier of updated chaos-marmosets 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 Jul 2023 17:00:44 +0200 Source: chaos-marmosets Built-For-Profiles: noudeb Architecture: source Version: 0.1.2-2 Distribution: unstable Urgency: medium Maintainer: Benjamin Drung Changed-By: Benjamin Drung Closes: 1037962 Changes: chaos-marmosets (0.1.2-2) unstable; urgency=medium . * test: Expect divide-by-zero to exit with SIGTRAP on arm64 and ppc64el (Closes: #1037962) Checksums-Sha1: 502c0400e9a11326344a0b57a793389a020ed921 2200 chaos-marmosets_0.1.2-2.dsc 5c79e916f71f95bcec87b7c5432e01dd9f139964 9024 chaos-marmosets_0.1.2-2.debian.tar.xz b0dc0618eb8aace4a5e3248c4435f445f763979c 7082 chaos-marmosets_0.1.2-2_source.buildinfo Checksums-Sha256: 44e31c8b2cd825f079e19fda30411e0816761d5d9ceec8ef576414646331a0b1 2200 chaos-marmosets_0.1.2-2.dsc 4e83e1b124bdfcb3c0a0e942eded5e96f395e8e95ca68e554fd2f44ee5960c32 9024 chaos-marmosets_0.1.2-2.debian.tar.xz a2c1ba7edb9f9ea8532ac9d5082f83bea813a3a312a509d47dcdb7db48732929 7082 chaos-marmosets_0.1.2-2_source.buildinfo Files: bf9d6d4a02fb9b404cab99565af9bad9 2200 utils optional chaos-marmosets_0.1.2-2.dsc 71b2f141c42c0e7df91bb5e9b4815e4a 9024 utils optional chaos-marmosets_0.1.2-2.debian.tar.xz ac3833d58ea211430c6224696eadfc3e 7082 utils optional chaos-marmosets_0.1.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEpi0s+9ULm1vzYNVLFZ61xO/Id0wFAmShkZkACgkQFZ61xO/I d0y5KxAAmQOQNZhS+5brp8hNv3yvbX61qFX+Yzp0VeaS70MvdqXTz4XIIlrFUoxZ 3O2ahQh8VLRTx+sUtZ0Ml88u0cHJd57JuMbmUk/PWAOEHlaK+N16vw2+lsYUpTcO lIBZNtE1Murg10TTuUihGP60LT368lYTsihTo1MGNbMhuHIZlMuIfqhTN6dwBRns HLra6wGGcXUY0BYHRQxoUtobP3IvUUS1BSFQwy4hHF+lFqTlEIxFRL4c5oRsWZ+U 1WzgHzjQldZ8vIm1podYuxpuujEtj3cLirpHPwbg7jzKSFjnoTAxg9PZKFd8NL8Y M6EpViRBn1buXN4dqZ0Bist239hMjnrTjLDb7hwRURYQOpcBprCPHWYsCDo0F2oQ I3IS7S/jy4iKUfZCDCxtcHMsoJr/OT/huvYJfOxfNKFgKKKpLvSGqW4k4RW9LBAF wBDfUQVNaJDxWpLQKA6ZyaFsH7TDAcUe76W2/n/c7Vc/V/nav4sTt489BLs0PjIL CQzhVrYh2S3CCuUGmltkPJLcy9XfJx2EDAfb60Ds6AD8Nttp6mEFuUXDtPPZvhLG zlw+paDQQ5O7BmZ/2hmMgKcU1FC+3ESKPXHSRseHCrLd2YA+LxBAwEWyRqIbzRu0 p/56acxf1VQI2Y1dt3o9hWn1B5MljBnuYUqU6tA2hyjbnwf7jIw= =BlhL -END PGP SIGNATURE End Message ---
Bug#1039480: marked as done ([astroplan] Please update to 0.8 for astropy 5.3 compatibility)
Your message dated Sun, 02 Jul 2023 14:33:59 + with message-id and subject line Bug#1039480: fixed in astroplan 0.8-1 has caused the Debian Bug report #1039480, regarding [astroplan] Please update to 0.8 for astropy 5.3 compatibility 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.) -- 1039480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039480 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: astroplan Version: 0.7-4 Severity: serious Tags: affects -1 src:astropy Dear maintainer, two days ago I uploaded the updated astropy_5.3-1 to unstable. With this new version, astroplan's autopkgtests no longer pass. The reason is that Astropys "TestRunner.run_tests()" no longer accepts an "open_files" argument. This is fixed in version astroplan version 0.8, therefore I would ask you to update the package accordingly. I have set the severity to "serious", because the it blocks the migration of Astropy to testing. If you don't want to do the update yourself, I would volunteer to do it as a team upload. Best Ole --- End Message --- --- Begin Message --- Source: astroplan Source-Version: 0.8-1 Done: Vincent Prat We believe that the bug you reported is fixed in the latest version of astroplan, 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 1039...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vincent Prat (supplier of updated astroplan 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: Wed, 28 Jun 2023 19:07:59 +0200 Source: astroplan Architecture: source Version: 0.8-1 Distribution: unstable Urgency: medium Maintainer: Debian Astro Team Changed-By: Vincent Prat Closes: 1039480 Changes: astroplan (0.8-1) unstable; urgency=medium . * New upstream release (Closes: #1039480) * New patch to use mock remote test data: use_mock_remote_test_data.patch Checksums-Sha1: a19317a7336ed56c1563b43171dcf1a6c090d64e 2261 astroplan_0.8-1.dsc 5b011805c991d686e473120f5acfbb661cef2815 134720 astroplan_0.8.orig.tar.gz b769551103ad87555ea0df3ccf3db524f942b1d7 8108 astroplan_0.8-1.debian.tar.xz 7bbd62446cd3d8fb6d45b25d9b53f805a16d6f97 13559 astroplan_0.8-1_amd64.buildinfo Checksums-Sha256: c968dbc2590044b48730a5640bbb1601674724862fdbf4fab4e78eb255c67528 2261 astroplan_0.8-1.dsc 0cc463474e034f5f58f7399ef830ff60e91d2fac32e89cf2224e1de50946bdc7 134720 astroplan_0.8.orig.tar.gz 265386f7fcbc8565018d2526bf5bbd8d93a2200c4c0c49672b8393e78cee4354 8108 astroplan_0.8-1.debian.tar.xz 4811acad4087936452bdee2166fb5e34052bc0917068a16c42c78dc587060d1e 13559 astroplan_0.8-1_amd64.buildinfo Files: 2045c245d52bb276b3991c47eb039bda 2261 python optional astroplan_0.8-1.dsc 5595baf9469ca8c21b5ad05309ec6798 134720 python optional astroplan_0.8.orig.tar.gz 7080a92a04102eea3bf34f702a561aba 8108 python optional astroplan_0.8-1.debian.tar.xz 6036b53e3b0983337339d40a0f2e5ca3 13559 python optional astroplan_0.8-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEEwN+g0Kj2VQgeB/icBzHNjq6Fm38FAmShfcsQHHZpdmlAZGVi aWFuLm9yZwAKCRAHMc2OroWbf+hpD/wJYuC2JljVxlAhnKRdhMqC63LFIk+rcPQL S6mBmfb6EktNZf234FjM97j4vUKyfuYp4txOD+rObCHqTAwHSnM5x2jY6mutsZwn i2mJNB6eJpfzEWIGQdTeqTgXs9Q6rnEnLoFS1A/eQwdAPV+AsWNIRS9aG44QzMtY 7N65atX3hwlJzXJri1rH688lfCUisQl8KyEjGcy8YLH/D3bQhaZedUfmr4K6/CDn cD2bPdUD1eWWQqZY3x9zPXzIvQqFU9HjxObQgGIgzvBoa3JmqVJhjP+OyRCV5Wbs JONILLOHsC6fCW+NIbO1KW/S3Py5H83sQ2S6PJsf55fueL0YAxM/qT0oTUi5AoNP IGiEPBWPtsGtQ2IZtM5tRElo0Wu1yO5XrtTOoVA4RuLPgX+3y51SaYtHmjhBycTT b9F6ONAqcQJqifFEQJBGpyMJj8nfx3/i3iYv+41nYymOMbtVNNYuJZ9bJdCmqJnI ylP3gyTXL7jm/Whq82RPktEWL/I4EGSVXsO33wziSbB2RTVyn/Eigh1zMScV9p8J 3WqCkNkkmZRqEyePEJOyYyGpwF+XW4Owiq/p1jet5usOgtW9Goudj2VGhmTpVXkt CvS64NrbmHUCB94RdhY6XVDI9dehFkQEhvb8pLb81DGKukDbTUyAV+IMKVd3C56N tQgWWgS+cQ== =3VTu -END PGP SIGNATURE End Message ---
Bug#1040141: FTBFS: FAIL: TestCheckoutGit
Source: docker.io Version: 18.09.1+dfsg1-7.1+deb10u3 Severity: serious Justification: FTBFS X-Debbugs-Cc: debian-...@lists.debian.org Dear Maintainer, The current security version FTBFS for me with -- FAIL: TestCheckoutGit (0.52s) gitutils_test.go:188: assertion failed: error is not nil: exit status 128 I am currently debugging this regression. Bastien signature.asc Description: This is a digitally signed message part.
Bug#1040134: marked as done (libaspect-perl: FTBFS: Can't locate inc/Module/Install/DSL.pm in @INC)
Your message dated Sun, 02 Jul 2023 13:33:55 + with message-id and subject line Bug#1040134: fixed in libaspect-perl 1.04-3 has caused the Debian Bug report #1040134, regarding libaspect-perl: FTBFS: Can't locate inc/Module/Install/DSL.pm in @INC 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.) -- 1040134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libaspect-perl Version: 1.04-2 Severity: serious Tags: ftbfs sid trixie This package fails to build from source on current sid. dh_auto_configure /usr/bin/perl Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" "LD=x86_64-linux-gnu-gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro" Can't locate inc/Module/Install/DSL.pm in @INC (you may need to install the inc::Module::Install::DSL module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl) at Makefile.PL line 1. BEGIN failed--compilation aborted at Makefile.PL line 1. dh_auto_configure: error: /usr/bin/perl Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" "LD=x86_64-linux-gnu-gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro" returned exit code 2 I think this was broken by libmodule-install-perl 1.21-1 with this upstream change from 1.20: - Module::Install::DSL has been removed, as its use is highly discouraged. -- Niko Tyni nt...@debian.org --- End Message --- --- Begin Message --- Source: libaspect-perl Source-Version: 1.04-3 Done: gregor herrmann We believe that the bug you reported is fixed in the latest version of libaspect-perl, 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 1040...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libaspect-perl 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 Jul 2023 15:15:42 +0200 Source: libaspect-perl Architecture: source Version: 1.04-3 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Closes: 1040134 Changes: libaspect-perl (1.04-3) unstable; urgency=medium . * Add patch to make Makefile.PL work without Module::Install::DSL. Thanks to Niko Tyni for the bug report. (Closes: #1040134) * Update years of packaging copyright. * Declare compliance with Debian Policy 4.6.2. * Set Rules-Requires-Root: no. * Annotate test-only build dependencies with . * Remove unused libbenchmark-timer-perl from Suggests. Checksums-Sha1: 5be81cb34f0b44fff9f6de1c6b749ea58d009139 2591 libaspect-perl_1.04-3.dsc 8e9a2837be42722ec1ef0409d7864241b33fa0b7 4932 libaspect-perl_1.04-3.debian.tar.xz Checksums-Sha256: 182fa95a514808f998aa0be9bb50e5abfb7e2db1cb861164ddccec9115d9b563 2591 libaspect-perl_1.04-3.dsc 554ff8c2431ccf083f55cf6299d3de9bb0561253867522afd5cf77f518f8acb5 4932 libaspect-perl_1.04-3.debian.tar.xz Files: 8c13effe7670121d529523b76a2581fb 2591 perl optional libaspect-perl_1.04-3.dsc 707ed8ed7fab55af9c83a0d1a2d4b836 4932 perl optional libaspect-perl_1.04-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmSheQ1fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgbU9g//cYZS6ib0Ixdl25QU9holnuAL0K0+n7qgrfSW+cDVEmqhUFkdhYL1lnhe 4XRIBOdwmGvzq29Nmn9lHQ76J8z7CEM3kbcQtqjEeaujbGCADycTG6Mn//dSdpr2 O+KUhFmWLnPbUc8I3nbPUdLhmLaFppoeQjGnAWajOHHaDTWJyHapH2HRyQFvkuXI R6ur07i0Dh8+8oML0QRYp4qze++csDLF/TGjHZCdhBu/495MrMEu28+TYB5QgXQ8
Bug#1040130: marked as done (octave-parallel: FTBFS: error: no matching function for call to ‘verror(octave::execution_exception&, const char [83], const char*)’)
Your message dated Sun, 02 Jul 2023 13:34:05 + with message-id and subject line Bug#1040130: fixed in octave-parallel 4.0.1-7 has caused the Debian Bug report #1040130, regarding octave-parallel: FTBFS: error: no matching function for call to ‘verror(octave::execution_exception&, const char [83], const char*)’ 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.) -- 1040130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040130 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: octave-parallel Version: 4.0.1-6 Severity: serious Tags: ftbfs sid trixie Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=octave-parallel=amd64=4.0.1-6%2Bb1=1688261012=0 g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/octave-8.2.0/octave/.. -I/usr/include/octave-8.2.0/octave -pthread -fopenmp -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-deprecated-declarationsnetwork_set.cc -o network_set.o In file included from parallel-gnutls.h:86, from pconnect.cc:24: pconnect.cc: In function ‘octave_value_list Fpconnect(const octave_value_list&, int)’: error-helpers.h:67:16: error: no matching function for call to ‘verror(octave::execution_exception&, const char [73], const char*)’ 67 | verror (e, __VA_ARGS__); \ | ~~~^~~~ pconnect.cc:173:7: note: in expansion of macro ‘CHECK_ERROR’ 173 | CHECK_ERROR (cm = args(0).char_matrix_value (), retval, | ^~~ In file included from /usr/include/octave-8.2.0/octave/../octave/oct.h:36, from parallel-gnutls.h:25: /usr/include/octave-8.2.0/octave/../octave/error.h:425:27: note: candidate: ‘void verror(const char*, __va_list_tag*)’ 425 | extern OCTINTERP_API void verror (const char *fmt, va_list args); | ^~ /usr/include/octave-8.2.0/octave/../octave/error.h:425:27: note: candidate expects 2 arguments, 3 provided /usr/include/octave-8.2.0/octave/../octave/error.h:433:1: note: candidate: ‘void verror(octave::execution_exception&, const char*, __va_list_tag*)’ 433 | verror (octave::execution_exception&, const char *fmt, va_list args); | ^~ /usr/include/octave-8.2.0/octave/../octave/error.h:433:64: note: no known conversion for argument 3 from ‘const char*’ to ‘__va_list_tag*’ 433 | verror (octave::execution_exception&, const char *fmt, va_list args); |^~~~ error-helpers.h:67:16: error: no matching function for call to ‘verror(octave::execution_exception&, const char [58], const char*)’ 67 | verror (e, __VA_ARGS__); \ | ~~~^~~~ pconnect.cc:230:7: note: in expansion of macro ‘CHECK_ERROR’ 230 | CHECK_ERROR (options = args(1).scalar_map_value (), retval, | ^~~ /usr/include/octave-8.2.0/octave/../octave/error.h:425:27: note: candidate: ‘void verror(const char*, __va_list_tag*)’ 425 | extern OCTINTERP_API void verror (const char *fmt, va_list args); | ^~ /usr/include/octave-8.2.0/octave/../octave/error.h:425:27: note: candidate expects 2 arguments, 3 provided /usr/include/octave-8.2.0/octave/../octave/error.h:433:1: note: candidate: ‘void verror(octave::execution_exception&, const char*, __va_list_tag*)’ 433 | verror (octave::execution_exception&, const char *fmt, va_list args); | ^~ /usr/include/octave-8.2.0/octave/../octave/error.h:433:64: note: no known conversion for argument 3 from ‘const char*’ to ‘__va_list_tag*’ 433 | verror (octave::execution_exception&, const char *fmt, va_list args); |^~~~ error-helpers.h:67:16: error: no matching function for call to ‘verror(octave::execution_exception&, const char [47], const char*)’ 67 | verror (e, __VA_ARGS__); \ | ~~~^~~~ pconnect.cc:241:11: note: in expansion of macro ‘CHECK_ERROR’ 241 | CHECK_ERROR (use_gnutls = tmp.bool_value (), retval, | ^~~ /usr/include/octave-8.2.0/octave/../octave/error.h:425:27: note: candidate: ‘void verror(const char*, __va_list_tag*)’ 425 | extern OCTINTERP_API void verror (const char *fmt, va_list args); | ^~ /usr/include/octave-8.2.0/octave/../octave/error.h:425:27: note: candidate
Processed: Bug#1040130 marked as pending in octave-parallel
Processing control commands: > tag -1 pending Bug #1040130 [src:octave-parallel] octave-parallel: FTBFS: error: no matching function for call to ‘verror(octave::execution_exception&, const char [83], const char*)’ Added tag(s) pending. -- 1040130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040130 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040130: marked as pending in octave-parallel
Control: tag -1 pending
Hello,
Bug #1040130 in octave-parallel 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-parallel/-/commit/d549d260c437587f1f81d9b8924962181d544918
octave8-part{1,2}.patch: new patches, fix FTBFS against Octave 8
Closes: #1040130
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/1040130
Processed: tagging 1038603
Processing commands for cont...@bugs.debian.org: > tags 1038603 - moreinfo Bug #1038603 [libisl23] libisl23: amd64/i386 baseline violation: uses BMI instructions Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 1038603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038603 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000024: marked as done (cppcheck: depends on obsolete pcre3 library)
Your message dated Sun, 02 Jul 2023 11:34:06 + with message-id and subject line Bug#124: fixed in cppcheck 2.11-3 has caused the Debian Bug report #124, regarding cppcheck: depends on obsolete pcre3 library 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.) -- 124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=124 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cppcheck Severity: important User: matthew-pcre...@debian.org Usertags: obsolete-pcre3 Dear maintainer, Your package still depends on the old, obsolete PCRE3[0] libraries (i.e. libpcre3-dev). This has been end of life for a while now, and upstream do not intend to fix any further bugs in it. Accordingly, I would like to remove the pcre3 libraries from Debian, preferably in time for the release of Bookworm. The newer PCRE2 library was first released in 2015, and has been in Debian since stretch. Upstream's documentation for PCRE2 is available here: https://pcre.org/current/doc/html/ Many large projects that use PCRE have made the switch now (e.g. git, php); it does involve some work, but we are now at the stage where PCRE3 should not be used, particularly if it might ever be exposed to untrusted input. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00176.html Regards, Matthew [0] Historical reasons mean that old PCRE is packaged as pcre3 in Debian --- End Message --- --- Begin Message --- Source: cppcheck Source-Version: 2.11-3 Done: Joachim Reichel We believe that the bug you reported is fixed in the latest version of cppcheck, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joachim Reichel (supplier of updated cppcheck 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: Sat, 01 Jul 2023 12:01:04 +0200 Source: cppcheck Architecture: source Version: 2.11-3 Distribution: unstable Urgency: medium Maintainer: Joachim Reichel Changed-By: Joachim Reichel Closes: 124 Changes: cppcheck (2.11-3) unstable; urgency=medium . * Disable rules support and remove build dependency on PCRE1 due to the removal of PCRE1 (Closes: #124). Checksums-Sha1: f15e5aa97c4c54475835c824eaca7427e5149b08 2129 cppcheck_2.11-3.dsc 1b2d847e222602acb4d7b98f8f7cce388939f9d0 12668 cppcheck_2.11-3.debian.tar.xz 3c44b4c7632cc443ad3ddf02cfa608ec3e88c8fe 12733 cppcheck_2.11-3_amd64.buildinfo Checksums-Sha256: 4624c63bd5d2d314f5b46d6ea6dcac8c196fb388282629bef8ac3aa86ae5f89a 2129 cppcheck_2.11-3.dsc 0bb0b2b3a041f5e005a30c3dd537f2b44ff22f0bc0c9e2d20b2a549c72809de7 12668 cppcheck_2.11-3.debian.tar.xz b462ff36e6f135d09b3ba26423d662530d29173d61cd689e49bcd40458f3a367 12733 cppcheck_2.11-3_amd64.buildinfo Files: a8c441f0a6af57172101c205528bcf49 2129 devel optional cppcheck_2.11-3.dsc 439e45c2394969484a019ad18e90b3cc 12668 devel optional cppcheck_2.11-3.debian.tar.xz 23dbee04f0dac6380007f5fb3534cc21 12733 devel optional cppcheck_2.11-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEErX6NzLwwsr4xjsEVuPr/HEOIZ3EFAmShXckACgkQuPr/HEOI Z3EYWxAA27tGE5pn+Zo4tpUho9EFuX/KukYvl9qazvrxtHoZRNILSKl9Yb9FrIgB E3tmdTFmcli/khgUlQqSSjfzM19ksr3pCHN6xEpwxpbFbjnG8F8Kvc4emYBfWQTq D31ioPueXHocuGkPpKw3vxy5+642cif+5Sf2XM5yjQu14TOMKhX8aSmE5rRefUDd 6TQnKJBMd44bOqQpsgXDxCv9y7HXC0bfRz0TD3RK8zKxVOXw15qkfcBYqfH/IbjE JU7DyMFZ4jithVdlrC//mI23YpOmqZYyuHOghNHtT9MKHf3sa0TDMDc80oIMVwuS r8U1qcwvSTidqMrn+AKvupQeBp4D/nqm6yqE1myY9vHuIZSMaRhdsY2G9nW6FFxA xeLtMWRT8J2egKtERhHfYYbmVsKxxXKqzPQairA3ETivV/rmOVKJgnbVgk0ML5nQ WtcSQxsre+KKTR6z6vLiIpkX6ocpIWUmrSEHtPGa8M/2p4i85z2qqGJ/z25U47KG EaM4eQJOhXQ335CWMOW6WYZzjxtm9UIPL63dW5J9j390WRVaqaHy2jqMBWPZo4uA Ynt1JfJiPI8qyXhJe+RzpMuEyEqNnJ5gvCcuegAG1pZMRmvL6oJR9OxfOuOa+IDp kY7hIk/SQ5VExmrMy+xR+xXN9dhQEQO7m65cZGMYnN15pBBrK60= =0miq -END PGP SIGNATURE End Message ---
Processed: tagging 1037920
Processing commands for cont...@bugs.debian.org: > tags 1037920 + sid trixie Bug #1037920 [src:python-django] python-django: FTBFS due to test failures (ValueError: '::1:2::3' does not appear to be an IPv4 or IPv6 address) Added tag(s) sid and trixie. > thanks Stopping processing here. Please contact me if you need assistance. -- 1037920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037920 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1000012 is forwarded to https://github.com/nmap/nmap/pull/2668 https://github.com/nmap/nmap/issues/1335 https://seclists.org/nmap-dev/2022/q2/11 ...
Processing commands for cont...@bugs.debian.org: > forwarded 112 https://github.com/nmap/nmap/pull/2668 > https://github.com/nmap/nmap/issues/1335 > https://seclists.org/nmap-dev/2022/q2/11 Bug #112 [src:nmap] nmap: depends on obsolete pcre3 library Changed Bug forwarded-to-address to 'https://github.com/nmap/nmap/pull/2668 https://github.com/nmap/nmap/issues/1335 https://seclists.org/nmap-dev/2022/q2/11' from 'https://github.com/nmap/nmap/issues/1335 https://seclists.org/nmap-dev/2022/q2/11'. > tags 112 + patch upstream Bug #112 [src:nmap] nmap: depends on obsolete pcre3 library Added tag(s) upstream and patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1000012 is forwarded to https://github.com/nmap/nmap/issues/1335 https://seclists.org/nmap-dev/2022/q2/11
Processing commands for cont...@bugs.debian.org: > forwarded 112 https://github.com/nmap/nmap/issues/1335 > https://seclists.org/nmap-dev/2022/q2/11 Bug #112 [src:nmap] nmap: depends on obsolete pcre3 library Set Bug forwarded-to-address to 'https://github.com/nmap/nmap/issues/1335 https://seclists.org/nmap-dev/2022/q2/11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040131: marked as done (octave-stk: FTBFS: Some tests failed. Giving up...)
Your message dated Sun, 02 Jul 2023 10:31:14 + with message-id and subject line Bug#1040131: fixed in octave-stk 2.8.1-1 has caused the Debian Bug report #1040131, regarding octave-stk: FTBFS: Some tests failed. Giving up... 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.) -- 1040131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: octave-stk Version: 2.8.0-2 Severity: serious Tags: ftbfs sid trixie Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=octave-stk=amd64=2.8.0-2%2Bb1=1688258543=0 * error u = apply (x, 3, @min, []); * test t = [1; 3; 2]; x = stk_dataframe (t); [M, k] = apply (x, 1, @max, []); assert ((M == 3) && (k == 2)); 11 tests, 11 passed, 0 known failure, 0 skipped [inst/arrays/@stk_dataframe/acosh.m] > /<>/inst/arrays/@stk_dataframe/acosh.m * test u = rand (4, 3); x = stk_dataframe (u); v = acosh (x); assert (strcmp (class (v), class (u)) && isequal (v, acosh (u))) 1 test, 1 passed, 0 known failure, 0 skipped [inst/arrays/@stk_dataframe/acosd.m] > /<>/inst/arrays/@stk_dataframe/acosd.m * test u = rand (4, 3); x = stk_dataframe (u); v = acosd (x); assert (strcmp (class (v), class (u)) && isequal (v, acosd (u))) 1 test, 1 passed, 0 known failure, 0 skipped [inst/arrays/@stk_dataframe/acos.m] > /<>/inst/arrays/@stk_dataframe/acos.m * test u = rand (4, 3); x = stk_dataframe (u); v = acos (x); assert (strcmp (class (v), class (u)) && isequal (v, acos (u))) 1 test, 1 passed, 0 known failure, 0 skipped [inst/arrays/@stk_dataframe/abs.m] > /<>/inst/arrays/@stk_dataframe/abs.m * test u = rand (4, 3); x = stk_dataframe (u); v = abs (x); assert (strcmp (class (v), class (u)) && isequal (v, abs (u))) 1 test, 1 passed, 0 known failure, 0 skipped Checking C++ files ... Summary: 1558 tests, 1552 passed, 0 known failures, 0 skipped Some tests failed. Giving up... make: *** [debian/rules:5: binary-arch] Error 1 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: octave-stk Source-Version: 2.8.1-1 Done: Sébastien Villemot We believe that the bug you reported is fixed in the latest version of octave-stk, 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 1040...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sébastien Villemot (supplier of updated octave-stk 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 Jul 2023 11:35:13 +0200 Source: octave-stk Architecture: source Version: 2.8.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Octave Group Changed-By: Sébastien Villemot Closes: 1040131 Changes: octave-stk (2.8.1-1) unstable; urgency=medium . * Team upload . [ Sébastien Villemot ] * New upstream version 2.8.1 Fixes testsuite with Octave 8 (Closes: #1040131) * octave7.patch: drop patch, no longer needed . [ Rafael Laboissière ] * d/copyright: Update Source URL Checksums-Sha1: 41ce1b8b1e0b0f895d35591bdbe638d86c446ac8 2008 octave-stk_2.8.1-1.dsc 125dcf45346c408222cdcc60cd5f257b544dbe53 389336 octave-stk_2.8.1.orig.tar.gz a9b5026b0c78553ee4e7c3b47a78964d2a8b405a 4848 octave-stk_2.8.1-1.debian.tar.xz 540ffed26320c3d86f98a34411fee0845f115161 22381 octave-stk_2.8.1-1_amd64.buildinfo Checksums-Sha256: ed1487d3ba438f947a32506850572c3d88c346b65328be3dc776c0a6cd0bf323 2008 octave-stk_2.8.1-1.dsc c138ccf4b51c0bc0448f74cdc40cfcefb2ea26fba8c5652c7bd3c86685869c85 389336 octave-stk_2.8.1.orig.tar.gz 274b5044599b1c1d1af6c2eba15dca901e1850f8f4e7bf12779c4a2a5b07acc9 4848 octave-stk_2.8.1-1.debian.tar.xz a95ab82a46c42e11e3d79593d20151519b0b0710fba0a5e2264c4d2ba1369dd1 22381 octave-stk_2.8.1-1_amd64.buildinfo Files: f580be40d34083468a2c93c4e25671d3 2008 math optional octave-stk_2.8.1-1.dsc f91cd81d748373ded935166f88667e4a 389336 math optional octave-stk_2.8.1.orig.tar.gz c29b423544f53064a3db5310f6b00016 4848 math optional octave-stk_2.8.1-1.debian.tar.xz
Bug#1040134: libaspect-perl: FTBFS: Can't locate inc/Module/Install/DSL.pm in @INC
Source: libaspect-perl Version: 1.04-2 Severity: serious Tags: ftbfs sid trixie This package fails to build from source on current sid. dh_auto_configure /usr/bin/perl Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" "LD=x86_64-linux-gnu-gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro" Can't locate inc/Module/Install/DSL.pm in @INC (you may need to install the inc::Module::Install::DSL module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl) at Makefile.PL line 1. BEGIN failed--compilation aborted at Makefile.PL line 1. dh_auto_configure: error: /usr/bin/perl Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" "LD=x86_64-linux-gnu-gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro" returned exit code 2 I think this was broken by libmodule-install-perl 1.21-1 with this upstream change from 1.20: - Module::Install::DSL has been removed, as its use is highly discouraged. -- Niko Tyni nt...@debian.org
Bug#1039724: gpgme: building underbookworm fails with no matches in python3-gpg.install
On 2023-07-01 Ted wrote: > Build still fails under debuild with no funny flags. Here's log. [...] Hello, Looking at the log it looks like your are overriding CFLAGS somewhere (-g -O2 -ffile-prefix-map=/... is missing). This warning is missing in your log: [BUILDPATH]/gpgme1.0-1.18.0/build/lang/python/setup.py:21: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives from distutils.core import setup, Extension So I think you are running with an unclean environment which causes the build to either use locally installed (older) python modules or which causes the python modules to behave differently. printenv might be enlightening. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Processed: tagging 1040066
Processing commands for cont...@bugs.debian.org: > tags 1040066 + sid trixie Bug #1040066 [src:python-marshmallow-enum] python-marshmallow-enum: Intent to remove from the archive Added tag(s) sid and trixie. > thanks Stopping processing here. Please contact me if you need assistance. -- 1040066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1039611
Processing commands for cont...@bugs.debian.org:
> tags 1039611 - bookworm
Bug #1039611 {Done: Michael Fladischer } [src:celery,
src:python-django-celery-beat] celery breaks python-django-celery-beat
autopkgtest: 'zoneinfo.ZoneInfo' object has no attribute 'zone'
Removed tag(s) bookworm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1039611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039611
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1040131: octave-stk: FTBFS: Some tests failed. Giving up...
Source: octave-stk Version: 2.8.0-2 Severity: serious Tags: ftbfs sid trixie Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=octave-stk=amd64=2.8.0-2%2Bb1=1688258543=0 * error u = apply (x, 3, @min, []); * test t = [1; 3; 2]; x = stk_dataframe (t); [M, k] = apply (x, 1, @max, []); assert ((M == 3) && (k == 2)); 11 tests, 11 passed, 0 known failure, 0 skipped [inst/arrays/@stk_dataframe/acosh.m] > /<>/inst/arrays/@stk_dataframe/acosh.m * test u = rand (4, 3); x = stk_dataframe (u); v = acosh (x); assert (strcmp (class (v), class (u)) && isequal (v, acosh (u))) 1 test, 1 passed, 0 known failure, 0 skipped [inst/arrays/@stk_dataframe/acosd.m] > /<>/inst/arrays/@stk_dataframe/acosd.m * test u = rand (4, 3); x = stk_dataframe (u); v = acosd (x); assert (strcmp (class (v), class (u)) && isequal (v, acosd (u))) 1 test, 1 passed, 0 known failure, 0 skipped [inst/arrays/@stk_dataframe/acos.m] > /<>/inst/arrays/@stk_dataframe/acos.m * test u = rand (4, 3); x = stk_dataframe (u); v = acos (x); assert (strcmp (class (v), class (u)) && isequal (v, acos (u))) 1 test, 1 passed, 0 known failure, 0 skipped [inst/arrays/@stk_dataframe/abs.m] > /<>/inst/arrays/@stk_dataframe/abs.m * test u = rand (4, 3); x = stk_dataframe (u); v = abs (x); assert (strcmp (class (v), class (u)) && isequal (v, abs (u))) 1 test, 1 passed, 0 known failure, 0 skipped Checking C++ files ... Summary: 1558 tests, 1552 passed, 0 known failures, 0 skipped Some tests failed. Giving up... make: *** [debian/rules:5: binary-arch] Error 1 Cheers -- Sebastian Ramacher
Bug#1040130: octave-parallel: FTBFS: error: no matching function for call to ‘verror(octave::execution_exception&, const char [83], const char*)’
Source: octave-parallel Version: 4.0.1-6 Severity: serious Tags: ftbfs sid trixie Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=octave-parallel=amd64=4.0.1-6%2Bb1=1688261012=0 g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/octave-8.2.0/octave/.. -I/usr/include/octave-8.2.0/octave -pthread -fopenmp -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-deprecated-declarationsnetwork_set.cc -o network_set.o In file included from parallel-gnutls.h:86, from pconnect.cc:24: pconnect.cc: In function ‘octave_value_list Fpconnect(const octave_value_list&, int)’: error-helpers.h:67:16: error: no matching function for call to ‘verror(octave::execution_exception&, const char [73], const char*)’ 67 | verror (e, __VA_ARGS__); \ | ~~~^~~~ pconnect.cc:173:7: note: in expansion of macro ‘CHECK_ERROR’ 173 | CHECK_ERROR (cm = args(0).char_matrix_value (), retval, | ^~~ In file included from /usr/include/octave-8.2.0/octave/../octave/oct.h:36, from parallel-gnutls.h:25: /usr/include/octave-8.2.0/octave/../octave/error.h:425:27: note: candidate: ‘void verror(const char*, __va_list_tag*)’ 425 | extern OCTINTERP_API void verror (const char *fmt, va_list args); | ^~ /usr/include/octave-8.2.0/octave/../octave/error.h:425:27: note: candidate expects 2 arguments, 3 provided /usr/include/octave-8.2.0/octave/../octave/error.h:433:1: note: candidate: ‘void verror(octave::execution_exception&, const char*, __va_list_tag*)’ 433 | verror (octave::execution_exception&, const char *fmt, va_list args); | ^~ /usr/include/octave-8.2.0/octave/../octave/error.h:433:64: note: no known conversion for argument 3 from ‘const char*’ to ‘__va_list_tag*’ 433 | verror (octave::execution_exception&, const char *fmt, va_list args); |^~~~ error-helpers.h:67:16: error: no matching function for call to ‘verror(octave::execution_exception&, const char [58], const char*)’ 67 | verror (e, __VA_ARGS__); \ | ~~~^~~~ pconnect.cc:230:7: note: in expansion of macro ‘CHECK_ERROR’ 230 | CHECK_ERROR (options = args(1).scalar_map_value (), retval, | ^~~ /usr/include/octave-8.2.0/octave/../octave/error.h:425:27: note: candidate: ‘void verror(const char*, __va_list_tag*)’ 425 | extern OCTINTERP_API void verror (const char *fmt, va_list args); | ^~ /usr/include/octave-8.2.0/octave/../octave/error.h:425:27: note: candidate expects 2 arguments, 3 provided /usr/include/octave-8.2.0/octave/../octave/error.h:433:1: note: candidate: ‘void verror(octave::execution_exception&, const char*, __va_list_tag*)’ 433 | verror (octave::execution_exception&, const char *fmt, va_list args); | ^~ /usr/include/octave-8.2.0/octave/../octave/error.h:433:64: note: no known conversion for argument 3 from ‘const char*’ to ‘__va_list_tag*’ 433 | verror (octave::execution_exception&, const char *fmt, va_list args); |^~~~ error-helpers.h:67:16: error: no matching function for call to ‘verror(octave::execution_exception&, const char [47], const char*)’ 67 | verror (e, __VA_ARGS__); \ | ~~~^~~~ pconnect.cc:241:11: note: in expansion of macro ‘CHECK_ERROR’ 241 | CHECK_ERROR (use_gnutls = tmp.bool_value (), retval, | ^~~ /usr/include/octave-8.2.0/octave/../octave/error.h:425:27: note: candidate: ‘void verror(const char*, __va_list_tag*)’ 425 | extern OCTINTERP_API void verror (const char *fmt, va_list args); | ^~ /usr/include/octave-8.2.0/octave/../octave/error.h:425:27: note: candidate expects 2 arguments, 3 provided /usr/include/octave-8.2.0/octave/../octave/error.h:433:1: note: candidate: ‘void verror(octave::execution_exception&, const char*, __va_list_tag*)’ 433 | verror (octave::execution_exception&, const char *fmt, va_list args); | ^~ /usr/include/octave-8.2.0/octave/../octave/error.h:433:64: note: no known conversion for argument 3 from ‘const char*’ to ‘__va_list_tag*’ 433 | verror (octave::execution_exception&, const char *fmt, va_list args); |^~~~ error-helpers.h:67:16: error: no matching function for call to ‘verror(octave::execution_exception&, const char [55], const char*)’ 67 | verror (e, __VA_ARGS__); \ | ~~~^~~~ pconnect.cc:251:11: note: in expansion of macro ‘CHECK_ERROR’ 251 | CHECK_ERROR (cpfile = tmp.string_value (),
Bug#1040129: slurm-wlm: binary-any FTBFS
Source: slurm-wlm Version: 23.02.3-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=slurm-wlm=23.02.3-1 ... dh_missing -a -O--builddirectory dh_missing: warning: usr/lib/aarch64-linux-gnu/slurm-wlm/src/sattach/sattach.wrapper.c exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/usr/lib/x86_64-linux-gnu/slurm-wlm/src/sattach/sattach.wrapper.c") dh_missing: warning: usr/lib/aarch64-linux-gnu/slurm-wlm/src/srun/srun.wrapper.c exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/usr/lib/x86_64-linux-gnu/slurm-wlm/src/srun/srun.wrapper.c") dh_missing: error: missing files, aborting While detecting missing files, dh_missing noted some files with a similar name to those that were missing. This error /might/ be resolved by replacing references to the missing files with the similarly named ones that dh_missing found - assuming the content is identical. As an example, you might want to replace: * debian/tmp/usr/lib/x86_64-linux-gnu/slurm-wlm/src/sattach/sattach.wrapper.c with: * usr/lib/aarch64-linux-gnu/slurm-wlm/src/sattach/sattach.wrapper.c in a file in debian/ or as argument to one of the dh_* tools called from debian/rules. (Note it is possible the paths are not used verbatim but instead directories containing or globs matching them are used instead) Alternatively, add the missing file to debian/not-installed if it cannot and should not be used. The following debhelper tools have reported what they installed (with files per package) * dh_install: libpam-slurm (1), libpam-slurm-adopt (1), libpam-slurm-adopt-dev (2), libpam-slurm-dev (2), libpmi0 (2), libpmi0-dev (4), libpmi2-0 (2), libpmi2-0-dev (4), libslurm-dev (9), libslurm-perl (5), libslurm39 (2), libslurmdb-perl (3), slurm-client (19), slurm-client-emulator (17), slurm-wlm (0), slurm-wlm-basic-plugins (111), slurm-wlm-basic-plugins-dev (218), slurm-wlm-doc (0), slurm-wlm-elasticsearch-plugin (1), slurm-wlm-elasticsearch-plugin-dev (2), slurm-wlm-emulator (3), slurm-wlm-hdf5-plugin (2), slurm-wlm-hdf5-plugin-dev (2), slurm-wlm-influxdb-plugin (1), slurm-wlm-influxdb-plugin-dev (2), slurm-wlm-ipmi-plugins (2), slurm-wlm-ipmi-plugins-dev (4), slurm-wlm-jwt-plugin (1), slurm-wlm-jwt-plugin-dev (2), slurm-wlm-kafka-plugin (1), slurm-wlm-kafka-plugin-dev (2), slurm-wlm-mysql-plugin (2), slurm-wlm-mysql-plugin-dev (4), slurm-wlm-plugins (0), slurm-wlm-plugins-dev (0), slurm-wlm-rrd-plugin (1), slurm-wlm-rrd-plugin-dev (2), slurm-wlm-rsmi-plugin (1), slurm-wlm-rsmi-plugin-dev (2), slurm-wlm-torque (10), slurmctld (1), slurmd (2), slurmdbd (1), slurmrestd (1), sview (1) * dh_installdocs: libpam-slurm (1), libpam-slurm-adopt (1), libpam-slurm-adopt-dev (0), libpam-slurm-dev (0), libpmi0 (0), libpmi0-dev (0), libpmi2-0 (0), libpmi2-0-dev (0), libslurm-dev (0), libslurm-perl (0), libslurm39 (0), libslurmdb-perl (0), slurm-client (0), slurm-client-emulator (0), slurm-wlm (4), slurm-wlm-basic-plugins (0), slurm-wlm-basic-plugins-dev (0), slurm-wlm-doc (1), slurm-wlm-elasticsearch-plugin (0), slurm-wlm-elasticsearch-plugin-dev (0), slurm-wlm-emulator (0), slurm-wlm-hdf5-plugin (0), slurm-wlm-hdf5-plugin-dev (0), slurm-wlm-influxdb-plugin (0), slurm-wlm-influxdb-plugin-dev (0), slurm-wlm-ipmi-plugins (0), slurm-wlm-ipmi-plugins-dev (0), slurm-wlm-jwt-plugin (0), slurm-wlm-jwt-plugin-dev (0), slurm-wlm-kafka-plugin (0), slurm-wlm-kafka-plugin-dev (0), slurm-wlm-mysql-plugin (0), slurm-wlm-mysql-plugin-dev (0), slurm-wlm-plugins (0), slurm-wlm-plugins-dev (0), slurm-wlm-rrd-plugin (0), slurm-wlm-rrd-plugin-dev (0), slurm-wlm-rsmi-plugin (0), slurm-wlm-rsmi-plugin-dev (0), slurm-wlm-torque (0), slurmctld (2), slurmd (0), slurmdbd (0), slurmrestd (0), sview (0) * dh_installexamples: libpam-slurm (0), libpam-slurm-adopt (0), libpam-slurm-adopt-dev (0), libpam-slurm-dev (0), libpmi0 (0), libpmi0-dev (0), libpmi2-0 (0), libpmi2-0-dev (0), libslurm-dev (0), libslurm-perl (0), libslurm39 (0), libslurmdb-perl (0), slurm-client (6), slurm-client-emulator (0), slurm-wlm (0), slurm-wlm-basic-plugins (0), slurm-wlm-basic-plugins-dev (0), slurm-wlm-doc (0), slurm-wlm-elasticsearch-plugin (0), slurm-wlm-elasticsearch-plugin-dev (0), slurm-wlm-emulator (0), slurm-wlm-hdf5-plugin (0), slurm-wlm-hdf5-plugin-dev (0), slurm-wlm-influxdb-plugin (0), slurm-wlm-influxdb-plugin-dev (0), slurm-wlm-ipmi-plugins (0), slurm-wlm-ipmi-plugins-dev (0), slurm-wlm-jwt-plugin (0), slurm-wlm-jwt-plugin-dev (0), slurm-wlm-kafka-plugin (0), slurm-wlm-kafka-plugin-dev (0), slurm-wlm-mysql-plugin (0), slurm-wlm-mysql-plugin-dev (0), slurm-wlm-plugins (0), slurm-wlm-plugins-dev (0), slurm-wlm-rrd-plugin (0), slurm-wlm-rrd-plugin-dev (0), slurm-wlm-rsmi-plugin (0), slurm-wlm-rsmi-plugin-dev (0), slurm-wlm-torque (0),
Bug#1040071: marked as done (libelf-dev: Missing dep from libelf-dev to libzstd-dev)
Your message dated Sun, 02 Jul 2023 08:49:48 +
with message-id
and subject line Bug#1040071: fixed in elfutils 0.189-3
has caused the Debian Bug report #1040071,
regarding libelf-dev: Missing dep from libelf-dev to libzstd-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.)
--
1040071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040071
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libelf-dev
Version: 0.189-2
Severity: serious
Tags: patch
Justification: Makes glib2.0 FTBFS
Hello,
Since version 0.189, libelf.pc has libzstd in its Requires.private.
The libelf-dev package should thus depend on the libzstd-dev package,
otherwise we get:
$ pkg-config --cflags libelf
Package libzstd was not found in the pkg-config search path.
Perhaps you should add the directory containing `libzstd.pc'
to the PKG_CONFIG_PATH environment variable
Package 'libzstd', required by 'libelf', not found
thus breaking various packages that use libelf, e.g. glib2.0.
Samuel
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500,
'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500,
'oldoldstable-proposed-updates'), (500, 'oldoldstable'), (500,
'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1,
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64
Kernel: Linux 6.3.0 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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 libelf-dev depends on:
ii libelf1 0.188-2.1
ii zlib1g-dev 1:1.2.13.dfsg-1
libelf-dev recommends no packages.
libelf-dev suggests no packages.
-- no debconf information
--
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.
--- debian/control.original 2023-07-02 02:27:55.928634126 +0200
+++ debian/control 2023-07-02 02:28:07.188696284 +0200
@@ -53,7 +53,7 @@
Section: libdevel
Architecture: any
Multi-Arch: same
-Depends: libelf1 (= ${binary:Version}), ${misc:Depends}, zlib1g-dev
+Depends: libelf1 (= ${binary:Version}), ${misc:Depends}, zlib1g-dev,
libzstd-dev
Conflicts: libelfg0-dev
Description: libelf1 development libraries and header files
libelf1 provides a shared library which allows reading and writing of ELF
--- End Message ---
--- Begin Message ---
Source: elfutils
Source-Version: 0.189-3
Done: Matthias Klose
We believe that the bug you reported is fixed in the latest version of
elfutils, 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 1040...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthias Klose (supplier of updated elfutils 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 Jul 2023 09:41:46 +0200
Source: elfutils
Built-For-Profiles: noudeb
Architecture: source
Version: 0.189-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Elfutils Maintainers
Changed-By: Matthias Klose
Closes: 1040071
Changes:
elfutils (0.189-3) unstable; urgency=medium
.
* libelf-dev: Depend on libzstd-dev. Closes: #1040071.
Checksums-Sha1:
958231760dbdc3f431e4f2ae2589974819fea457 3248 elfutils_0.189-3.dsc
8da419f723a5f0029ed8b18fe9a02dbfc42e221e 43192 elfutils_0.189-3.debian.tar.xz
7acb1f4d25cf8af280bcbc2e48d59a2dd7194a87 6791 elfutils_0.189-3_source.buildinfo
Checksums-Sha256:
f6b6702e4ad0e50c6885a3e9669d12b59879a79855b06e6a69f5c49c5143d168 3248
elfutils_0.189-3.dsc
e219ae1d321f7a6be2f5ca1f3ab1e02ac93dfa2e777effdd130d7655c6ce9a95 43192
elfutils_0.189-3.debian.tar.xz
404d1c8651f52c2ebac3f55475cae0291967325ba94da077a6e4b49ca76170f8 6791
elfutils_0.189-3_source.buildinfo
Files:
7a6507ad21c327d32db7d07e8058e82d 3248 libs optional
Bug#1040128: relion-cuda: FTBFS with cub 2.0.1: error: function "cub::Debug" has already been defined
Source: relion-cuda Version: 3.1.3-2 Severity: serious Tags: ftbfs sid trixie Justification: fails to build from source Hi, relion-cuda FTBFS in the combination of CUDA 11.8 and CUB 2.0.1: ... nvcc warning : The 'compute_35', 'compute_37', 'sm_35', and 'sm_37' architectures are deprecated, and may be removed in a future release (Use -Wno-deprecated-gpu-targets to suppress warning). /usr/include/cub/util_debug.cuh(184): error: function "cub::Debug" has already been defined /usr/include/cub/util_debug.cuh(184): error: function "cub::Debug" has already been defined /usr/include/cub/util_debug.cuh(184): error: function "cub::Debug" has already been defined Generated /build/relion-cuda-3.1.3/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_backprojector.cu.o successfully. Generated /build/relion-cuda-3.1.3/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_projector.cu.o successfully. /usr/include/cub/util_debug.cuh(184): error: function "cub::Debug" has already been defined 1 error detected in the compilation of "/build/relion-cuda-3.1.3/src/acc/cuda/cuda_projector_plan.cu". -- Removing /build/relion-cuda-3.1.3/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_projector_plan.cu.o /usr/bin/cmake -E rm -f /build/relion-cuda-3.1.3/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_projector_plan.cu.o CMake Error at relion_gpu_util_generated_cuda_projector_plan.cu.o.Release.cmake:280 (message): Error generating file /build/relion-cuda-3.1.3/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_projector_plan.cu.o make[4]: *** [src/apps/CMakeFiles/relion_gpu_util.dir/build.make:129: src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/relion_gpu_util_generated_cuda_projector_plan.cu.o] Error 1 make[4]: *** Waiting for unfinished jobs Generated /build/relion-cuda-3.1.3/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_benchmark_utils.cu.o successfully. 1 error detected in the compilation of "/build/relion-cuda-3.1.3/src/acc/cuda/cuda_autopicker.cu". 1 error detected in the compilation of "/build/relion-cuda-3.1.3/src/acc/cuda/cuda_helper_functions.cu". -- Removing /build/relion-cuda-3.1.3/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_autopicker.cu.o -- Removing /build/relion-cuda-3.1.3/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_helper_functions.cu.o /usr/bin/cmake -E rm -f /build/relion-cuda-3.1.3/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_autopicker.cu.o /usr/bin/cmake -E rm -f /build/relion-cuda-3.1.3/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_helper_functions.cu.o CMake Error at relion_gpu_util_generated_cuda_autopicker.cu.o.Release.cmake:280 (message): Error generating file /build/relion-cuda-3.1.3/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_autopicker.cu.o make[4]: *** [src/apps/CMakeFiles/relion_gpu_util.dir/build.make:80: src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/relion_gpu_util_generated_cuda_autopicker.cu.o] Error 1 CMake Error at relion_gpu_util_generated_cuda_helper_functions.cu.o.Release.cmake:280 (message): Error generating file /build/relion-cuda-3.1.3/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_helper_functions.cu.o make[4]: *** [src/apps/CMakeFiles/relion_gpu_util.dir/build.make:101: src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/relion_gpu_util_generated_cuda_helper_functions.cu.o] Error 1 1 error detected in the compilation of "/build/relion-cuda-3.1.3/src/acc/cuda/cuda_ml_optimiser.cu". -- Removing /build/relion-cuda-3.1.3/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_ml_optimiser.cu.o /usr/bin/cmake -E rm -f /build/relion-cuda-3.1.3/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_ml_optimiser.cu.o CMake Error at relion_gpu_util_generated_cuda_ml_optimiser.cu.o.Release.cmake:280 (message): Error generating file /build/relion-cuda-3.1.3/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_ml_optimiser.cu.o make[4]: *** [src/apps/CMakeFiles/relion_gpu_util.dir/build.make:115: src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/relion_gpu_util_generated_cuda_ml_optimiser.cu.o] Error 1 Generated /build/relion-cuda-3.1.3/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/cuda_kernels/./relion_gpu_util_generated_helper.cu.o successfully. make[4]: Leaving directory '/build/relion-cuda-3.1.3/build' make[3]: *** [CMakeFiles/Makefile2:300:
