Bug#1042806: libllvm14: SIGILL Illegal Instructions on POWER5 in libLLVM-14.so
Package: libllvm14 Version: 1:14.0.6-12 Severity: critical Justification: breaks unrelated software Hello, I think the libLLVM-14 contains some instructions not found on IBM POWER5+ (gs) -- vxor is not found in it's IBM reference manual: https://www.ibm.com/docs/en/ssw_aix_72/assembler/assembler_pdf.pdf Maybe this library was built for more recent CPUs but the debian ppc64 support goes back to POWER5 AFAIK(?) $ objdump --disassemble /lib/powerpc64-linux-gnu/libLLVM-14.so.1 |grep vxor As a result there is some difficulty running applications linked to libLLVM, for example rust installation fails with SIGILL, there are likely other affected programs. Thank you Stuart -- System Information: Debian Release: trixie/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: ppc64 Kernel: Linux 5.15.123 (SMP w/2 CPU threads) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages libllvm14 depends on: ii libc6 2.37-6 ii libedit23.1-20221030-2 ii libffi8 3.4.4-1 ii libgcc-s1 13.2.0-1 ii libstdc++6 13.2.0-1 ii libtinfo6 6.4+20230625-2 ii libxml2 2.9.14+dfsg-1.3 ii libz3-4 4.8.12-3.1 ii zlib1g 1:1.2.13.dfsg-1 libllvm14 recommends no packages. libllvm14 suggests no packages. -- no debconf information
Bug#1040477: librust-syn-1-dev fails to coinstall
Hi Peter and Fabian, On Thu, Jul 06, 2023 at 01:27:19PM +0200, Helmut Grohne wrote: > Package: librust-syn-1-dev > Version: 1.0.109-2 > Severity: serious > Justification: fails to (co)install > Control: affects -1 + src:rust-fd-find > User: debian-cr...@lists.debian.org > Usertags: ftcbfs > X-Debbugs-Cc: de...@lists.debian.org > > librust-syn-1-dev has (among other things) the following metadata: > > Provides: librust-syn-1.0.109-dev > Breaks: librust-syn-1.0.109-dev > Multi-Arch: same > > It is not clear to me what this is supposed to mean. Can you shed some > light on what this is supposed to achieve? > > In any case, apt and dpkg disagree about what this shall mean. apt > thinks that self-breaks are to be ignored and asks dpkg to configure > both of these packages, but dpkg doesn't like that: > > | dpkg: dependency problems prevent configuration of librust-syn-1-dev:amd64: > | librust-syn-1-dev:arm64 (1.0.109-2) breaks librust-syn-1.0.109-dev and is > unpacked but not configured. > | librust-syn-1-dev:amd64 (1.0.109-2) provides librust-syn-1.0.109-dev. > | > | dpkg: error processing package librust-syn-1-dev:amd64 (--configure): > | dependency problems - leaving unconfigured > > You can reproduce the installation failure using: > > mmdebstrap unstable /dev/null --architectures=amd64,arm64 --variant=apt > --include=librust-syn-1-dev:amd64,librust-syn-1-dev:arm64 > > If apt and dose were refusing this situation this were a normal bug at > best. But since dpkg fails badly and leaves the system in an > inconsistent state, I am raising this to rc-severity. Even if we deem > this to be an apt bug or dpkg bug in the end, librust-syn-1-dev must > still be changed since we cannot depend on fixed versions of package > managers being used to install packages. This problem, which is reported almost a month ago still persists. I am aware that a generic solution is hard to come by and I need to be patient for a full solution. On the flip side, the current metadata causes dpkg and dose to disagree. This in turn causes https://crossqa.debian.net to believe that there is a temporary problem with the archive as a whole. It thus ceases testing further packages until the next mirror push. This behaviour is very useful in cases where there are M-A:same skews as those tend to affect very many packages. Since rust-syn appears in more and more packages Build-Depends, this particular bug effectively disableds cross compilation testing now as crossqa.d.n tests a few packages until it runs into an affected one and throttles itself. Is there any chance we could have a temporary workaround for this issue? A very simple workaround from my pov would be temporarily removing Multi-Arch: same. Of course that would make the package unavailable to cross compilation, but on the flip side, it already is. After dropping Multi-Arch: same, dose would no longer consider solutions involving coinstallations of it and archive testing could continue. Failing that, the only way I see is blacklisting the package in crossqa, but then I'd probably forget about it and it would also be surprising in the diagnostics as crossqa would always tell that this package does not exist. I prefer having you work around the issue. A simple upload dropping M-A:same removes the worst of pain and gives us time to work on a generic solution. Do you agree? Helmut
Bug#1042776: marked as done (r-bioc-deseq: still depends on obsolete r-api-bioc-3.16)
Your message dated Tue, 01 Aug 2023 04:19:04 + with message-id and subject line Bug#1042776: fixed in r-bioc-deseq 1.39.0-12 has caused the Debian Bug report #1042776, regarding r-bioc-deseq: still depends on obsolete r-api-bioc-3.16 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.) -- 1042776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042776 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: r-bioc-deseq Version: 1.39.0-11 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is no longer installable in sid: The following packages have unmet dependencies: r-bioc-deseq : Depends: r-api-bioc-3.16 but it is not installable Even after a rebuild in sid the package keeps the dependency on the obsolete api. ./DESCRIPTION contains `git_branch: RELEASE_3_16` - is this the location where the version is hardcoded? Cheers, Andreas --- End Message --- --- Begin Message --- Source: r-bioc-deseq Source-Version: 1.39.0-12 Done: Charles Plessy We believe that the bug you reported is fixed in the latest version of r-bioc-deseq, 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 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Charles Plessy (supplier of updated r-bioc-deseq 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: Tue, 01 Aug 2023 11:41:09 +0900 Source: r-bioc-deseq Architecture: source Version: 1.39.0-12 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Charles Plessy Closes: 1042776 Changes: r-bioc-deseq (1.39.0-12) unstable; urgency=medium . * Team upload. * Update patch to rebuild for BioC API 3.17 (Closes: #1042776) Checksums-Sha1: 75dbed612f24f74f5d894138809d6e966656b809 2184 r-bioc-deseq_1.39.0-12.dsc 4eb232273b492b17c56d8ffb57c6bcdce9c514ce 3180 r-bioc-deseq_1.39.0-12.debian.tar.xz 58c246aff43aab42ff1e9f6e72e04191004d3b89 12298 r-bioc-deseq_1.39.0-12_source.buildinfo Checksums-Sha256: 3c4e2f12cfbe14e40fe7eb79413330cdaa525855e9af5e49454f8b6797623c68 2184 r-bioc-deseq_1.39.0-12.dsc 33991f0b7da5ad68c0f7ff1189f7e97a7cc322d35bc676071b26a14b71bc6cf7 3180 r-bioc-deseq_1.39.0-12.debian.tar.xz 5af06ca48e78d44b41f56b4f238094da7eb04208ab786bc8263773d18871e9c3 12298 r-bioc-deseq_1.39.0-12_source.buildinfo Files: d6cc8e1abd26b4761a0811532a0d83c6 2184 gnu-r optional r-bioc-deseq_1.39.0-12.dsc e3cf77a461edcb5b69907fb8f965032a 3180 gnu-r optional r-bioc-deseq_1.39.0-12.debian.tar.xz c9d41861bf0f02ffec9b3239cd931ddd 12298 gnu-r optional r-bioc-deseq_1.39.0-12_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEEc0cUmcxg7Z7ugFlGxb1sjyKV1QIFAmTIgSMSHHBsZXNzeUBk ZWJpYW4ub3JnAAoJEMW9bI8ildUCl0cP/1SMg5Azu0cTyAI8OdbblHGuZ/iWTzjY HLSuHsN99jeSxx9dbfwHo+C2zBCwSgkOt/VYqu70nPkoHfuuKDbvrmppQCIQQvI+ hzFxofxehQhP+72zQbglTgS665NjbkTbx4ToAe98dhdYvS9h6nybBMVfQdYsBhVY tBdHQZrhUIOa25y59hF/tFOT2JBO00huM0J71/N/n2B7pL+2J5n1/pwbyOOwLO9S u9vGbkZVloMduUkEgy5Cf2zjTX3hsFEF9Yh99Ygnv/tbDBa2G0yTEbz7WpyyeRTE L+UfyoDlB5pgAJn1nsyWWGr4JExhTOD+NRuV6gkDNQYkxQ3mcjaYMk8QJ9cFlVra VEMxg7vuP5XIkCvTCV1wu4X5N6mcMRasF6PKcgw58IlTPW/BhC/tW4vIS7XopLuC 0H6r3wXlqWwgNXlB7fuQJgPTrqHzJBz2KfipogomY5U8K0WvNCwVfY2+GrRlo+Oa 4Q78PP2VmyFngQd0rm9DQ38NSFJiaModaoo4S7sOOMRl671tcBMIxXyHXj2+9C9x LxcMc3N9s2fWAGD7KJrp+/Al/pszCWsnD/kALt6WOOOTaSFwYc+iPsSNkWJdLd+p YzsHHmjAg4VpgxB3Ygqxd4pX05vF8T0SGqDgdLR3Ya3cyYplcnOUQD1o9V72Dh0F LYZatGFnS6P6 =9NRz -END PGP SIGNATURE End Message ---
Bug#1029283:
After applying patch[1] I have ran the test suite with the following results:
---
make URL=http://localhost:38028 CREDS="test test" check
make[1]: Entering directory
'/home/vladimirp/git/make-pywebdav/pywebdav/test/litmus-0.13/lib/neon'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory
'/home/vladimirp/git/make-pywebdav/pywebdav/test/litmus-0.13/lib/neon'
gcc -o basic src/basic.o -L. -ltest -Llib/neon -lneon -lexpat
gcc -o copymove src/copymove.o -L. -ltest -Llib/neon -lneon -lexpat
gcc -o props src/props.o -L. -ltest -Llib/neon -lneon -lexpat
gcc -o locks src/locks.o -L. -ltest -Llib/neon -lneon -lexpat
gcc -o http src/http.o -L. -ltest -Llib/neon -lneon -lexpat
-> running `basic':
0. init.. pass
1. begin. pass
2. options... pass
3. put_get... pass
4. put_get_utf8_segment.. pass
5. put_no_parent. pass
6. mkcol_over_plain.. pass
7. delete pass
8. delete_null... pass
9. delete_fragment... pass
10. mkcol. pass
11. mkcol_again... pass
12. delete_coll... pass
13. mkcol_no_parent... pass
14. mkcol_with_body... pass
15. finish pass
<- summary for `basic': of 16 tests run: 16 passed, 0 failed. 100.0%
-> running `copymove':
0. init.. pass
1. begin. pass
2. copy_init. pass
3. copy_simple... pass
4. copy_overwrite pass
5. copy_nodestcoll... pass
6. copy_cleanup.. pass
7. copy_coll. pass
8. copy_shallow.. pass
9. move.. pass
10. move_coll. pass
11. move_cleanup.. pass
12. finish pass
<- summary for `copymove': of 13 tests run: 13 passed, 0 failed. 100.0%
-> running `props':
0. init.. pass
1. begin. pass
2. propfind_invalid.. pass
3. propfind_invalid2. pass
4. propfind_d0... pass
5. propinit.. pass
6. propset... FAIL (PROPPATCH on `/litmus/prop': 423 Locked)
7. propget... SKIPPED
8. propextended.. pass
9. propmove.. SKIPPED
10. propget... SKIPPED
11. propdeletes... SKIPPED
12. propget... SKIPPED
13. propreplace... SKIPPED
14. propget... SKIPPED
15. propnullns SKIPPED
16. propget... SKIPPED
17. prophighunicode... SKIPPED
18. propget... SKIPPED
19. propremoveset. SKIPPED
20. propget... SKIPPED
21. propsetremove. SKIPPED
22. propget... SKIPPED
23. propvalnspace. SKIPPED
24. propwformed... pass
25. propinit.. pass
26. propmanyns FAIL (PROPPATCH on `/litmus/prop': 423 Locked)
27. propget... FAIL (No value given for property
{http://example.com/kappa}somename)
28. propcleanup... pass
29. finish pass
-> 16 tests were skipped.
<- summary for `props': of 14 tests run: 11 passed, 3 failed. 78.6%
See debug.log for network/debug traces.
make: *** [Makefile:65: check] Error 1
--
pywebdav/lib/WebDAVServer.py[2] does not implement ` def
do_PROPPATCH(self):` causing above test failures.
[1]
https://salsa.debian.org/tryton-team/pywebdav/-/commit/e5d5acb5a18ca5e729c836c291350f239fccdcdb
[2]
https://github.com/andrewleech/PyWebDAV3/blob/9c948c8861b7e0b01a2fe97b9f54c256d1ba458b/pywebdav/lib/WebDAVServer.py#L318
Bug#1042776: [R-pkg-team] Bug#1042776: Bug#1042776: r-bioc-deseq: still depends on obsolete r-api-bioc-3.16
Le Tue, Aug 01, 2023 at 09:29:59AM +0900, Charles Plessy a écrit : > > the DESeq Bioconductor package was removed from the 3.17 release > upstream. I think that we can remove it from unstable and testing too. > > I will fill a removal later today. Actually it was removed from BioC 3.10 and the fix is easy, so I just uploaded a fixed version. I will still fill a removal unless somebody objects. The replacement package, r-bioc-deseq2, is well established and I am not aware of people or pipelines using the old version. I note that the med-bio-dev metapackage will need to be updated accordingly. I can to so after my joini request is accepted. Have a nice day, Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Debian Med packaging team http://www.debian.org/devel/debian-med Tooting from home, https://framapiaf.org/@charles_plessy - You do not have my permission to use this email to train an AI -
Processed: Bug#1042776 marked as pending in r-bioc-deseq
Processing control commands: > tag -1 pending Bug #1042776 [r-bioc-deseq] r-bioc-deseq: still depends on obsolete r-api-bioc-3.16 Added tag(s) pending. -- 1042776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042776 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042776: marked as pending in r-bioc-deseq
Control: tag -1 pending Hello, Bug #1042776 in r-bioc-deseq 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/r-pkg-team/r-bioc-deseq/-/commit/bad370412269ea6b7543b3f76d238f1765e3affd r-bioc-deseq (1.39.0-12) unstable; urgency=medium * Team upload. * Update patch to rebuild for BioC API 3.17 (Closes: #1042776) -- Charles Plessy Tue, 01 Aug 2023 11:41:09 +0900 (this message was generated automatically) -- Greetings https://bugs.debian.org/1042776
Bug#1042776: [R-pkg-team] Bug#1042776: r-bioc-deseq: still depends on obsolete r-api-bioc-3.16
Le Mon, Jul 31, 2023 at 09:46:48PM +0200, Andreas Beckmann a écrit : > > The following packages have unmet dependencies: >r-bioc-deseq : Depends: r-api-bioc-3.16 but it is not installable Dear Andreas, thanks for the catch, the DESeq Bioconductor package was removed from the 3.17 release upstream. I think that we can remove it from unstable and testing too. I will fill a removal later today. Have a nice day, Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Debian Med packaging team http://www.debian.org/devel/debian-med Tooting from home https://framapiaf.org/@charles_plessy - You do not have my permission to use this email to train an AI -
Processed: tagging 1038709
Processing commands for cont...@bugs.debian.org:
> tags 1038709 + fixed
Bug #1038709 {Done: Jonas Smedegaard } [sccache] sccache - build
dependency updates/fixes
Added tag(s) fixed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1038709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038709
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1042351: marked as done (binutils-avr: FTBFS: make: *** [debian/rules:88: install] Error 2)
Your message dated Mon, 31 Jul 2023 23:36:43 + with message-id and subject line Bug#1042351: fixed in binutils-avr 2.26.20160125+Atmel3.6.2-6 has caused the Debian Bug report #1042351, regarding binutils-avr: FTBFS: make: *** [debian/rules:88: install] Error 2 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.) -- 1042351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042351 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: binutils-avr Version: 2.26.20160125+Atmel3.6.2-5 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/binutils/libiberty/testsuite' > make[4]: Nothing to be done for 'install'. > make[4]: Leaving directory '/<>/binutils/libiberty/testsuite' > make[3]: Leaving directory '/<>/binutils/libiberty' > make[2]: Nothing to be done for 'install-target'. > make[2]: Leaving directory '/<>/binutils' > make[1]: Leaving directory '/<>/binutils' > #cp debian/gasp.1 debian/binutils-avr/usr/share/man/man1/avr-gasp.1 > # Non standard avr dir to keep FHS happy > mv debian/binutils-avr/usr/avr debian/binutils-avr/usr/lib/ > # Convert hardlinks to softlinks > cd debian/binutils-avr/usr/lib/avr/bin && for f in *; do \ > rm ../../../bin/avr-$f; \ > ln -s ../lib/avr/bin/$f ../../../bin/avr-$f; \ > done > /bin/sh: 1: cd: can't cd to debian/binutils-avr/usr/lib/avr/bin > make: *** [debian/rules:88: install] Error 2 The full build log is available from: http://qa-logs.debian.net/2023/07/26/binutils-avr_2.26.20160125+Atmel3.6.2-5_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: binutils-avr Source-Version: 2.26.20160125+Atmel3.6.2-6 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of binutils-avr, 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 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated binutils-avr package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 01 Aug 2023 01:15:01 +0200 Source: binutils-avr Architecture: source Version: 2.26.20160125+Atmel3.6.2-6 Distribution: unstable Urgency: medium Maintainer: Bastian Germann Changed-By: Bastian Germann Closes: 1042351 Changes: binutils-avr (2.26.20160125+Atmel3.6.2-6) unstable; urgency=medium . * debian/dirs: Recover file lost at 3.0 format conversion (Closes: #1042351) Checksums-Sha1: 5cbd78b26643397a863d2311f02326c409309864 1896 binutils-avr_2.26.20160125+Atmel3.6.2-6.dsc 4b768966ff4ce621986aaccc23f539067d6e29b9 13680 binutils-avr_2.26.20160125+Atmel3.6.2-6.debian.tar.xz 89b66ffd2865efafaeaf646b72fd4ef91eba2b98 5881 binutils-avr_2.26.20160125+Atmel3.6.2-6_source.buildinfo Checksums-Sha256: fd19c87ff0b33072f91739fcc4a2a0d6675247fde4b826a80d68e19b65e2a409 1896 binutils-avr_2.26.20160125+Atmel3.6.2-6.dsc 7d879875bcfb27206bf191e610c50e8e1703f7cf2c6ede3a3b4ff1588cf7de72 13680 binutils-avr_2.26.20160125+Atmel3.6.2-6.debian.tar.xz f2b843346dd72c408f36a55f1a7089b02c0f6d44c7c431cabb99803765152940 5881 binutils-avr_2.26.20160125+Atmel3.6.2-6_source.buildinfo Files: e7b058d8eb094aaa9d50bab1c05228dd 1896 devel optional binutils-avr_2.26.20160125+Atmel3.6.2-6.dsc a96b6b4c921f6ff8ac12bd3f9acf6b12 13680 devel optional
Bug#1037760: marked as done (llvm-toolchain-15: ftbfs with GCC-13)
Your message dated Mon, 31 Jul 2023 22:16:33 + with message-id and subject line Bug#1037760: fixed in llvm-toolchain-15 1:15.0.7-7 has caused the Debian Bug report #1037760, regarding llvm-toolchain-15: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037760 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:llvm-toolchain-15 Version: 1:15.0.7-4 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/llvm-toolchain-15_15.0.7-4_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-13/porting_to.html [...] [2354/2653] cd /<>/build-llvm/runtimes/runtimes-bins/openmp/libomptarget/DeviceRTL && /<>/build-llvm/bin/clang -c -emit-llvm -std=c++17 -fvisibility=hidden -O3 -mllvm -openmp-opt-disable -DSHARED_SCRATCHPAD_SIZE=512 --offload-device-only -nocudalib -nogpulib -nostdinc -fopenmp -fopenmp-cuda-mode -I/<>/openmp/libomptarget/DeviceRTL/include -I/<>/openmp/libomptarget/DeviceRTL/../include -I/<>/llvm/include -I/<>/build-llvm/include -DOMPTARGET_DEBUG=0 --offload-arch=gfx801 -fopenmp-targets=amdgcn-amd-amdhsa -DLIBOMPTARGET_BC_TARGET -D__AMDGCN__ -nogpulib /<>/openmp/libomptarget/DeviceRTL/src/Parallelism.cpp -o Parallelism.cpp-gfx801.bc [2355/2653] cd /<>/build-llvm/runtimes/runtimes-bins/openmp/libomptarget/DeviceRTL && /<>/build-llvm/bin/clang -c -emit-llvm -std=c++17 -fvisibility=hidden -O3 -mllvm -openmp-opt-disable -DSHARED_SCRATCHPAD_SIZE=512 --offload-device-only -nocudalib -nogpulib -nostdinc -fopenmp -fopenmp-cuda-mode -I/<>/openmp/libomptarget/DeviceRTL/include -I/<>/openmp/libomptarget/DeviceRTL/../include -I/<>/llvm/include -I/<>/build-llvm/include -DOMPTARGET_DEBUG=0 --offload-arch=gfx803 -fopenmp-targets=amdgcn-amd-amdhsa -DLIBOMPTARGET_BC_TARGET -D__AMDGCN__ -nogpulib /<>/openmp/libomptarget/DeviceRTL/src/Configuration.cpp -o Configuration.cpp-gfx803.bc [2356/2653] cd /<>/build-llvm/runtimes/runtimes-bins/openmp/libomptarget/DeviceRTL && /<>/build-llvm/bin/clang -c -emit-llvm -std=c++17 -fvisibility=hidden -O3 -mllvm -openmp-opt-disable -DSHARED_SCRATCHPAD_SIZE=512 --offload-device-only -nocudalib -nogpulib -nostdinc -fopenmp -fopenmp-cuda-mode -I/<>/openmp/libomptarget/DeviceRTL/include -I/<>/openmp/libomptarget/DeviceRTL/../include -I/<>/llvm/include -I/<>/build-llvm/include -DOMPTARGET_DEBUG=0 --offload-arch=gfx803 -fopenmp-targets=amdgcn-amd-amdhsa -DLIBOMPTARGET_BC_TARGET -D__AMDGCN__ -nogpulib /<>/openmp/libomptarget/DeviceRTL/src/Debug.cpp -o Debug.cpp-gfx803.bc [2357/2653] cd /<>/build-llvm/runtimes/runtimes-bins/openmp/libomptarget/DeviceRTL && /<>/build-llvm/bin/opt -O3 -openmp-opt-disable /<>/build-llvm/runtimes/runtimes-bins/openmp/libomptarget/DeviceRTL/internalized_libomptarget-nvptx-sm_86.bc -o /<>/build-llvm/runtimes/runtimes-bins/openmp/libomptarget/DeviceRTL/libomptarget-nvptx-sm_86.bc [2358/2653] cd /<>/build-llvm/runtimes/runtimes-bins/openmp/libomptarget/DeviceRTL && /<>/build-llvm/bin/llvm-link -o /<>/build-llvm/runtimes/runtimes-bins/openmp/libomptarget/DeviceRTL/linked_libomptarget-amdgpu-gfx701.bc Configuration.cpp-gfx701.bc Debug.cpp-gfx701.bc Kernel.cpp-gfx701.bc Mapping.cpp-gfx701.bc Misc.cpp-gfx701.bc Parallelism.cpp-gfx701.bc Reduction.cpp-gfx701.bc State.cpp-gfx701.bc Synchronization.cpp-gfx701.bc Tasking.cpp-gfx701.bc Utils.cpp-gfx701.bc Workshare.cpp-gfx701.bc [2359/2653] cd
Bug#1037759: marked as done (llvm-toolchain-14: ftbfs with GCC-13)
Your message dated Mon, 31 Jul 2023 21:21:30 + with message-id and subject line Bug#1037759: fixed in llvm-toolchain-14 1:14.0.6-13 has caused the Debian Bug report #1037759, regarding llvm-toolchain-14: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037759 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:llvm-toolchain-14 Version: 1:14.0.6-12 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/llvm-toolchain-14_14.0.6-12_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-13/porting_to.html [...] [1839/2245] /<>/build-llvm/./bin/clang++ --target=x86_64-pc-linux-gnu -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Domp_EXPORTS -I/<>/build-llvm/runtimes/runtimes-bins/openmp/runtime/src -I/<>/openmp/runtime/src -I/<>/openmp/runtime/src/i18n -I/<>/openmp/runtime/src/include -I/<>/openmp/runtime/src/thirdparty/ittnotify -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -Wimplicit-fallthrough -Wcovered-switch-default -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wsuggest-override -Wstring-conversion -Wmisleading-indentation -fdiagnostics-color -ffunction-sections -fdata-sections -fdebug-p refix-map=/<>/build-llvm/runtimes/runtimes-bins=build-llvm/runtimes/runtimes-bins -fdebug-prefix-map=/<>/= -no-canonical-prefixes -ffile-prefix-map=/<>/build-llvm/runtimes/runtimes-bins=build-llvm/runtimes/runtimes-bins -ffile-prefix-map=/<>/= -no-canonical-prefixes -Wall -Wcast-qual -Wformat-pedantic -Wimplicit-fallthrough -Wsign-compare -Wno-extra -Wno-pedantic -std=c++14 -O3 -DNDEBUG -fPIC -D _GNU_SOURCE -D _REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 -fno-exceptions -fno-rtti -Wno-covered-switch-default -Wno-frame-address -Wno-strict-aliasing -Wno-switch -Wno-uninitialized -Wno-unused-but-set-variable -Wno-return-type-c-linkage -Wno-cast-qual -Wno-int-to-void-pointer-cast -MD -MT openmp/runtime/src/CMakeFiles/omp.dir/kmp_affinity.cpp.o -MF openmp/runtime/src/CMakeFiles/omp.dir/kmp_affinity.cpp.o.d -o openmp/runtime/src/CMakeFiles/omp.dir/kmp_affinity.cpp.o -c /<>/openmp/runtime/src/kmp_affinity.cpp [1840/2245] /<>/build-llvm/./bin/clang --target=x86_64-pc-linux-gnu -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Domp_EXPORTS -I/<>/build-llvm/runtimes/runtimes-bins/openmp/runtime/src -I/<>/openmp/runtime/src -I/<>/openmp/runtime/src/i18n -I/<>/openmp/runtime/src/include -I/<>/openmp/runtime/src/thirdparty/ittnotify -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition -Werror=date-time -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wmissing-field-initializers -Wimplicit-fallthrough -Wcovered-switch-default -Wstring-conversion -Wmisleading-indentation -fdiagnostics-color -ffunction-sections -fdata-sections -fdebug-prefix-map=/<>/build-llvm/runtimes/runtimes-bins=build-llvm/runtimes/runtimes-bins -fdebug-prefix-map=/<>/= -no-canonical-prefixes
Bug#1037757: marked as done (llvm-toolchain-13: ftbfs with GCC-13)
Your message dated Mon, 31 Jul 2023 20:57:25 + with message-id and subject line Bug#1037757: fixed in llvm-toolchain-13 1:13.0.1-12 has caused the Debian Bug report #1037757, regarding llvm-toolchain-13: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:llvm-toolchain-13 Version: 1:13.0.1-11 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/llvm-toolchain-13_13.0.1-11_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-13/porting_to.html [...] [101/2814] /usr/bin/g++-13 -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/<>/build-llvm/lib/Support -I/<>/llvm/lib/Support -I/<>/build-llvm/include -I/<>/llvm/include -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move -Wno-pessimizing-move -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment -Wmisleading-indentation -fdiagnostics-color -ffunction-sections -fdata-sections -ffile-prefix-map=/<>/build-llvm=build-llvm -ffile-prefix-map=/<>/= -no-canonical-prefixes -O3 -DNDEBUG -std=c++14 -fn o-exceptions -MD -MT lib/Support/CMakeFiles/LLVMSupport.dir/SuffixTree.cpp.o -MF lib/Support/CMakeFiles/LLVMSupport.dir/SuffixTree.cpp.o.d -o lib/Support/CMakeFiles/LLVMSupport.dir/SuffixTree.cpp.o -c /<>/llvm/lib/Support/SuffixTree.cpp [102/2814] /usr/bin/g++-13 -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/<>/build-llvm/lib/Support -I/<>/llvm/lib/Support -I/<>/build-llvm/include -I/<>/llvm/include -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move -Wno-pessimizing-move -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment -Wmisleading-indentation -fdiagnostics-color -ffunction-sections -fdata-sections -ffile-prefix-map=/<>/build-llvm=build-llvm -ffile-prefix-map=/<>/= -no-canonical-prefixes -O3 -DNDEBUG -std=c++14 -fn o-exceptions -MD -MT lib/Support/CMakeFiles/LLVMSupport.dir/SourceMgr.cpp.o -MF lib/Support/CMakeFiles/LLVMSupport.dir/SourceMgr.cpp.o.d -o lib/Support/CMakeFiles/LLVMSupport.dir/SourceMgr.cpp.o -c /<>/llvm/lib/Support/SourceMgr.cpp [103/2814] /usr/bin/g++-13 -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/<>/build-llvm/lib/Support -I/<>/llvm/lib/Support -I/<>/build-llvm/include -I/<>/llvm/include -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers
Processed: user debian...@lists.debian.org, usertagging 1042747, found 986475 in 4.1.9-2 ..., affects 1040607 ...
Processing commands for cont...@bugs.debian.org:
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 1042747 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 986475 4.1.9-2
Bug #986475 [libocamlnet-ocaml-doc] libocamlnet-ocaml-doc: broken symlinks:
/usr/share/doc/libocamlnet-ocaml-dev/examples ->
../libocamlnet-ocaml-doc/examples
Marked as found in versions ocamlnet/4.1.9-2.
> found 1040383 23.03.0-2
Bug #1040383 [ovn-common] ovn-common: broken symlink:
/usr/lib/ocf/resource.d/ovn/ovndb-servers ->
/usr/share/openvswitch/scripts/ovndb-servers.ocf
Marked as found in versions ovn/23.03.0-2.
> found 857404 1.0.1-3.2
Bug #857404 [dvi2ps-fontdata-ja] dvi2ps-fontdata-ja: broken symlinks:
/usr/share/texmf/fonts/vf/ptex/a2{wada, vfl, wl, wadaz} -> a2mor2
Marked as found in versions dvi2ps-fontdata/1.0.1-3.2.
> found 1035871 1.14-3
Bug #1035871 [flare-engine] flare-engine: broken symlink:
/usr/share/games/flare/mods/default/fonts/unifont-10.0.06.ttf ->
../../../../../fonts/truetype/unifont/unifont.ttf
Marked as found in versions flare-engine/1.14-3.
> found 972611 1.46.0-2
Bug #972611 [python-mutagen-doc] /usr/share/doc/python-mutagen/rst is a broken
symlink
Marked as found in versions mutagen/1.46.0-2.
> found 1040591 0.6.4-1
Bug #1040591 [postgresql-15-tablelog] postgresql-15-tablelog: broken symlink:
/usr/share/doc/postgresql-15-tablelog/README.md -> table_log.md
Marked as found in versions tablelog/0.6.4-1.
> affects 1040607 - ubuntu-packaging-guide-html-bt-br +
> ubuntu-packaging-guide-html-pt-br
Bug #1040607 [src:ubuntu-packaging-guide] ubuntu-packaging-guide-html-*: broken
symlinks: /usr/share/doc/ubuntu-packaging-guide-html-*/_static/*-stemmer.js ->
../../../ubuntu-packaging-guide/_static/*-stemmer.js
Removed indication that 1040607 affects ubuntu-packaging-guide-html-bt-br
> found 857680 1:13.0.1-11
Bug #857680 {Done: Sylvestre Ledru }
[llvm-13-examples,llvm-14-examples,llvm-15-examples,llvm-16-examples,llvm-17-examples]
llvm-3.8-examples: broken symlinks:
/usr/share/doc/llvm-3.8-examples/Makefile.* ->
../../../lib/llvm-3.8/build/Makefile.*
There is no source info for the package 'llvm-14-examples' at version
'1:13.0.1-11' with architecture ''
There is no source info for the package 'llvm-15-examples' at version
'1:13.0.1-11' with architecture ''
There is no source info for the package 'llvm-16-examples' at version
'1:13.0.1-11' with architecture ''
There is no source info for the package 'llvm-17-examples' at version
'1:13.0.1-11' with architecture ''
Marked as found in versions llvm-toolchain-13/1:13.0.1-11.
> found 857680 1:14.0.6-12
Bug #857680 {Done: Sylvestre Ledru }
[llvm-13-examples,llvm-14-examples,llvm-15-examples,llvm-16-examples,llvm-17-examples]
llvm-3.8-examples: broken symlinks:
/usr/share/doc/llvm-3.8-examples/Makefile.* ->
../../../lib/llvm-3.8/build/Makefile.*
There is no source info for the package 'llvm-13-examples' at version
'1:14.0.6-12' with architecture ''
There is no source info for the package 'llvm-15-examples' at version
'1:14.0.6-12' with architecture ''
There is no source info for the package 'llvm-16-examples' at version
'1:14.0.6-12' with architecture ''
There is no source info for the package 'llvm-17-examples' at version
'1:14.0.6-12' with architecture ''
Marked as found in versions llvm-toolchain-14/1:14.0.6-12.
> found 857680 1:15.0.7-6
Bug #857680 {Done: Sylvestre Ledru }
[llvm-13-examples,llvm-14-examples,llvm-15-examples,llvm-16-examples,llvm-17-examples]
llvm-3.8-examples: broken symlinks:
/usr/share/doc/llvm-3.8-examples/Makefile.* ->
../../../lib/llvm-3.8/build/Makefile.*
There is no source info for the package 'llvm-13-examples' at version
'1:15.0.7-6' with architecture ''
There is no source info for the package 'llvm-14-examples' at version
'1:15.0.7-6' with architecture ''
There is no source info for the package 'llvm-16-examples' at version
'1:15.0.7-6' with architecture ''
There is no source info for the package 'llvm-17-examples' at version
'1:15.0.7-6' with architecture ''
Marked as found in versions llvm-toolchain-15/1:15.0.7-6.
> found 988867 4.5.0-3
Bug #988867 [libtyxml-ocaml-doc] libtyxml-ocaml-doc: broken symlink:
/usr/share/doc/libtyxml-ocaml-doc/api -> ../libtyxml-ocaml-dev/api
Marked as found in versions tyxml/4.5.0-3.
> found 1040565 3.24.38-2
Bug #1040565 [libgtk-3-doc] libgtk-3-doc: broken symlinks:
/usr/share/doc/libgtk-3-{dev,doc}/pango -> ../libpango1.0-doc/pango
Marked as found in versions gtk+3.0/3.24.38-2.
> found 988845 3.0.0-3
Bug #988845 [libcalendar-ocaml-doc] libcalendar-ocaml-doc: broken symlink:
/usr/share/doc/libcalendar-ocaml-doc/html/api -> ../doc
Marked as found in versions calendar/3.0.0-3.
> unarchive 986238
Bug #986238 {Done: Nilesh Patra } [gubbins] gubbins: broken
symlink: /usr/bin/gubbins_drawer -> ../share/gubbins/gubbins_drawer.py
Unarchived Bug 986238
> found 986238 3.3.0-2
Bug #986238 {Done:
Bug#1038405: Bug#1037439: r-cran-rstan/armhf FTBFS with r-cran-bh 1.74
On Mon, Jun 19, 2023 at 04:37:22PM +0300, Adrian Bunk wrote: > On Tue, Jun 13, 2023 at 03:30:18PM -0500, Dirk Eddelbuettel wrote: > > > > On 13 June 2023 at 13:15, Steve Langasek wrote: > > | Control: reassign -1 r-cran-rstan r-cran-bh > > | Control: found -1 r-cran-rstan/2.21.8-1 > > | > > | Unfortunately, at least in Ubuntu it appears the r-cran-rstan build still > > | exhausts the 32-bit memory space even with boost 1.81. > > | > > | > > https://launchpad.net/ubuntu/+source/r-cran-rstan/2.21.8-1/+build/26010118 > > > > :-/ > > > > Not sure that it is fair to point at BH / Boost though. Anyway. > > > > CRAN no longer checks / compiles 32 bit so upstream may not care, but they > > are a good team (if busy). You could ping Ben, he is at > >Benjamin K Goodrich > >... > > The patch below to r-base fixes the build of r-cran-rstan/i386 for me. > > This will reduce debug info in the R ecosystem on 32bit to what is > required for backtraces, but I assume realistically R on 32bit is > anyway only sparsely used these days. > > > Dirk > > cu > Adrian > > --- debian/rules.old 2023-06-18 19:45:14.437261923 + > +++ debian/rules 2023-06-18 19:51:30.097179612 + > @@ -90,6 +90,11 @@ > export DEB_CFLAGS_MAINT_APPEND = -ffloat-store > endif > > +## fewer debug info on 32bit to workaround 2-4 GB address space limitation > +ifeq ($(DEB_HOST_ARCH_BITS), 32) > +export DEB_CFLAGS_MAINT_APPEND += -g1 > +endif > + >... These two entries ended up in the opposite order in the upload, and the -ffloat-store one did not have a += making the -g1 change a nop on i386. Please apply also the patch below. cu Adrian --- debian/rules.old2023-07-26 07:56:06.872438302 + +++ debian/rules2023-07-26 07:56:27.340457680 + @@ -92,7 +92,7 @@ ## Adrian Bunk 20 Jan 2023 workaround excess precision of x87 ifneq (,$(filter $(DEB_HOST_ARCH), i386)) -export DEB_CFLAGS_MAINT_APPEND = -ffloat-store +export DEB_CFLAGS_MAINT_APPEND += -ffloat-store endif ## edd 31 Mar 2014
Bug#1042776: r-bioc-deseq: still depends on obsolete r-api-bioc-3.16
Package: r-bioc-deseq Version: 1.39.0-11 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is no longer installable in sid: The following packages have unmet dependencies: r-bioc-deseq : Depends: r-api-bioc-3.16 but it is not installable Even after a rebuild in sid the package keeps the dependency on the obsolete api. ./DESCRIPTION contains `git_branch: RELEASE_3_16` - is this the location where the version is hardcoded? Cheers, Andreas
Processed: tagging 1036256
Processing commands for cont...@bugs.debian.org: > tags 1036256 + sid trixie Bug #1036256 [src:golang-github-pin-tftp] golang-github-pin-tftp: FTBFS in testing: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/pin/tftp github.com/pin/tftp/netascii returned exit code 1 Ignoring request to alter tags of bug #1036256 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1036256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036256 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1040431
Processing commands for cont...@bugs.debian.org:
> tags 1040431 + sid trixie
Bug #1040431 {Done: Ritesh Raj Sarraf } [src:user-mode-linux]
user-mode-linux: build dependency missing in testing: linux-source-6.1
Added tag(s) trixie and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1040431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040431
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 1026042
Processing commands for cont...@bugs.debian.org: > tags 1026042 + sid trixie Bug #1026042 [src:trx] trx: License is incompatible with that of up-coming ortp 5.2.0 Added tag(s) sid and trixie. > thanks Stopping processing here. Please contact me if you need assistance. -- 1026042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1042531 is important
Processing commands for cont...@bugs.debian.org: > severity 1042531 important Bug #1042531 [src:novnc] novnc: Embded copy of node-pako Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1042531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042531 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1041385, tagging 1041386
Processing commands for cont...@bugs.debian.org:
> tags 1041385 + sid trixie
Bug #1041385 {Done: Reinhard Tartler }
[librust-netlink-proto-dev] librust-netlink-proto-dev: impossible to install
Added tag(s) sid and trixie.
> tags 1041386 + sid trixie
Bug #1041386 {Done: Reinhard Tartler }
[librust-netlink-packet-route-dev] librust-netlink-packet-route-dev: impossible
to install
Added tag(s) sid and trixie.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1041385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041385
1041386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041386
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1041665: closing 1041665
close 1041665 29.1.3+dfsg-1 thanks
Processed: closing 1041665
Processing commands for cont...@bugs.debian.org: > close 1041665 29.1.3+dfsg-1 Bug #1041665 [src:obs-studio] obs-studio: FTBFS with ffmpeg 6.0 Marked as fixed in versions obs-studio/29.1.3+dfsg-1. Bug #1041665 [src:obs-studio] obs-studio: FTBFS with ffmpeg 6.0 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1041665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038207: marked as done (tp-smapi-dkms: module fails to build for Linux 6.4: error: macro "DEFINE_SEMAPHORE" requires 2 arguments, but only 1 given)
Your message dated Mon, 31 Jul 2023 19:11:11 + with message-id and subject line Bug#1038207: fixed in tp-smapi 0.44-1 has caused the Debian Bug report #1038207, regarding tp-smapi-dkms: module fails to build for Linux 6.4: error: macro "DEFINE_SEMAPHORE" requires 2 arguments, but only 1 given 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.) -- 1038207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038207 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tp-smapi-dkms Version: 0.43-3 Severity: important Tags: sid trixie User: debian...@lists.debian.org Usertags: piuparts DKMS make.log for tp_smapi-0.43 for kernel 6.4.0-0-amd64 (x86_64) Fri Jun 16 14:10:47 UTC 2023 make: Entering directory '/usr/src/linux-headers-6.4.0-0-amd64' CC [M] /var/lib/dkms/tp_smapi/0.43/build/thinkpad_ec.o CC [M] /var/lib/dkms/tp_smapi/0.43/build/tp_smapi.o CC [M] /var/lib/dkms/tp_smapi/0.43/build/hdaps.o /var/lib/dkms/tp_smapi/0.43/build/thinkpad_ec.c:94:42: error: macro "DEFINE_SEMAPHORE" requires 2 arguments, but only 1 given 94 | static DEFINE_SEMAPHORE(thinkpad_ec_mutex); | ^ In file included from /var/lib/dkms/tp_smapi/0.43/build/thinkpad_ec.c:45: /usr/src/linux-headers-6.4.0-0-common/include/linux/semaphore.h:34: note: macro "DEFINE_SEMAPHORE" defined here 34 | #define DEFINE_SEMAPHORE(_name, _n) \ | /var/lib/dkms/tp_smapi/0.43/build/thinkpad_ec.c:94:8: error: type defaults to 'int' in declaration of 'DEFINE_SEMAPHORE' [-Werror=implicit-int] 94 | static DEFINE_SEMAPHORE(thinkpad_ec_mutex); |^~~~ /var/lib/dkms/tp_smapi/0.43/build/thinkpad_ec.c: In function 'thinkpad_ec_lock': /var/lib/dkms/tp_smapi/0.43/build/thinkpad_ec.c:112:35: error: 'thinkpad_ec_mutex' undeclared (first use in this function); did you mean 'thinkpad_ec_lock'? 112 | ret = down_interruptible(_ec_mutex); | ^ | thinkpad_ec_lock /var/lib/dkms/tp_smapi/0.43/build/thinkpad_ec.c:112:35: note: each undeclared identifier is reported only once for each function it appears in /var/lib/dkms/tp_smapi/0.43/build/thinkpad_ec.c: In function 'thinkpad_ec_try_lock': /var/lib/dkms/tp_smapi/0.43/build/thinkpad_ec.c:126:30: error: 'thinkpad_ec_mutex' undeclared (first use in this function); did you mean 'thinkpad_ec_lock'? 126 | return down_trylock(_ec_mutex); | ^ | thinkpad_ec_lock /var/lib/dkms/tp_smapi/0.43/build/thinkpad_ec.c: In function 'thinkpad_ec_unlock': /var/lib/dkms/tp_smapi/0.43/build/thinkpad_ec.c:138:13: error: 'thinkpad_ec_mutex' undeclared (first use in this function); did you mean 'thinkpad_ec_lock'? 138 | up(_ec_mutex); | ^ | thinkpad_ec_lock /var/lib/dkms/tp_smapi/0.43/build/thinkpad_ec.c: In function 'thinkpad_ec_try_lock': /var/lib/dkms/tp_smapi/0.43/build/thinkpad_ec.c:127:1: error: control reaches end of non-void function [-Werror=return-type] 127 | } | ^ /var/lib/dkms/tp_smapi/0.43/build/thinkpad_ec.c: At top level: /var/lib/dkms/tp_smapi/0.43/build/thinkpad_ec.c:94:8: warning: 'DEFINE_SEMAPHORE' defined but not used [-Wunused-variable] 94 | static DEFINE_SEMAPHORE(thinkpad_ec_mutex); |^~~~ cc1: some warnings being treated as errors make[1]: *** [/usr/src/linux-headers-6.4.0-0-common/scripts/Makefile.build:257: /var/lib/dkms/tp_smapi/0.43/build/thinkpad_ec.o] Error 1 make[1]: *** Waiting for unfinished jobs /var/lib/dkms/tp_smapi/0.43/build/tp_smapi.c:115:36: error: macro "DEFINE_SEMAPHORE" requires 2 arguments, but only 1 given 115 | static DEFINE_SEMAPHORE(smapi_mutex); |^ In file included from /usr/src/linux-headers-6.4.0-0-common/include/linux/fs.h:25, from /usr/src/linux-headers-6.4.0-0-common/include/linux/proc_fs.h:10, from /var/lib/dkms/tp_smapi/0.43/build/tp_smapi.c:41: /usr/src/linux-headers-6.4.0-0-common/include/linux/semaphore.h:34: note: macro "DEFINE_SEMAPHORE" defined here 34 | #define DEFINE_SEMAPHORE(_name, _n) \ | /var/lib/dkms/tp_smapi/0.43/build/tp_smapi.c:115:8: error: type defaults to 'int' in declaration of 'DEFINE_SEMAPHORE' [-Werror=implicit-int] 115 | static DEFINE_SEMAPHORE(smapi_mutex); |^~~~ /var/lib/dkms/tp_smapi/0.43/build/tp_smapi.c: In function
Bug#1042569: marked as done (tp-smapi-dkms: Kernel 6.4 not supported)
Your message dated Mon, 31 Jul 2023 19:11:11 + with message-id and subject line Bug#1038207: fixed in tp-smapi 0.44-1 has caused the Debian Bug report #1038207, regarding tp-smapi-dkms: Kernel 6.4 not supported 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.) -- 1038207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038207 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tp-smapi-dkms Version: 0.43-3 Severity: important X-Debbugs-Cc: andrey.spit...@gmail.com Dear Maintainer, Dkms module fails to build for 6.4 kernel. Please update debian package to upstream release of tp-smapi. https://github.com/linux-thinkpad/tp_smapi/pull/45 -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (902, 'testing'), (81, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.3.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages tp-smapi-dkms depends on: ii dkms 3.0.11-3 tp-smapi-dkms recommends no packages. tp-smapi-dkms suggests no packages. -- debconf-show failed --- End Message --- --- Begin Message --- Source: tp-smapi Source-Version: 0.44-1 Done: Evgeni Golov We believe that the bug you reported is fixed in the latest version of tp-smapi, 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 1038...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Evgeni Golov (supplier of updated tp-smapi 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: Mon, 31 Jul 2023 20:09:41 +0200 Source: tp-smapi Architecture: source Version: 0.44-1 Distribution: unstable Urgency: medium Maintainer: Evgeni Golov Changed-By: Evgeni Golov Closes: 1038207 Changes: tp-smapi (0.44-1) unstable; urgency=medium . * New upstream version 0.44 + Support 6.4 kernel Closes: #1038207 Checksums-Sha1: abb10a045e2ea27eb4be9a6ffd5a23719bac141f 1907 tp-smapi_0.44-1.dsc 16c2229068628ff58d363f61de0d094b2177ea5c 40724 tp-smapi_0.44.orig.tar.gz 64d8a1f944d9a34a2032392edf18fd943ca64c4e 4980 tp-smapi_0.44-1.debian.tar.xz 9b72246616e80a5dbb7f2ebe40d667ec7b231e1c 6029 tp-smapi_0.44-1_source.buildinfo Checksums-Sha256: 477f895302c88817e9efde36a73a81f251bbe70c04c46b85b6cfd34a01324f3b 1907 tp-smapi_0.44-1.dsc cccff96e8994bfc9dfe2bec071c4dfb6baf060f988bc338bbab95e639fd4c126 40724 tp-smapi_0.44.orig.tar.gz 6a95e1d5d1df6ff60fbac019e025153587d1002ba3709930c231558e5dc45a44 4980 tp-smapi_0.44-1.debian.tar.xz 7122f3f4458accd57d69f8fbc7f6d4a829e473df1449b116b022806bda05f3d6 6029 tp-smapi_0.44-1_source.buildinfo Files: de37c8bbb26684d1230c6213e42fccb8 1907 kernel optional tp-smapi_0.44-1.dsc e74404020e402b2fa871bcc3833632c7 40724 kernel optional tp-smapi_0.44.orig.tar.gz 23d759443963a6f3ff70bbb7ae34c072 4980 kernel optional tp-smapi_0.44-1.debian.tar.xz a5118fba51a0071a241917793df15032 6029 kernel optional tp-smapi_0.44-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEExW57amdnGPa81AdGTrsFQAtaiq4FAmTIAcYACgkQTrsFQAta iq5BwA//UuwIuL3dXPi8doCyHDCrJS82rx5GA95p7bye1cRLr7Kt392o9Bzuj/TD 9zcmtWKwb+kHQn2m/YTVOBcWSAym2HA3BDvdffLy45OQvjGPt/FZxjNsS8joeW9t JjLiu+NrTouCCPxyk/N0qbjNXyMZJyLMntZbDTUvL9QVEUmhRcxcp89VY6v2y7C1 pt2JYOR2POPQCKhA0Vr9nVsQ9i1R7xKZeM9F47WEodmzD1uciuoH+dB023G1S2c7 Ql7iFVnHacZvjVpSk7zbE6gNAc8BQ8Opj5/dD4qSR+0Q0HVZeldZe5IQfrNnEgUs ba0/nVA5BI04Vfqe6AIoKgd8s36nqLM3jrG+lD3Mg/7+pxMhDgvIsVisefr+Q7f0 FigbQdw4cEXSflt/NILQJ2dz4LjWaLObDm41/5HBt+W+FcgsRXeQ7f7DdwComUd6 +iwxkyr7X/hotyat2rX32sCo46mA7NfsAN14d3TZGdl3qV8Y+XHj8aBLeox5fCK3 ZZsetVW19nNoHRiir24RWa8puojs8azCCWYJYL+aawetqdQbyniB/OLeKrar344H 2e2ixwLpdd3t/WcKO5ld85+OeD5rcalYJoQaSekAoUdBhntPvnxK6E/zrcxJ1d4L eTFyrbg3Hr3Q1PCCPGFAHpNAjGxG9dUs++pTuaGShNYeu4Mygko= =an1S -END PGP SIGNATURE End Message ---
Bug#1040898: marked as done (tp-smapi-dkms: Update to support Kernel 6.4+)
Your message dated Mon, 31 Jul 2023 19:11:11 + with message-id and subject line Bug#1038207: fixed in tp-smapi 0.44-1 has caused the Debian Bug report #1038207, regarding tp-smapi-dkms: Update to support Kernel 6.4+ 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.) -- 1038207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038207 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tp-smapi-dkms Version: 0.43-3 Severity: critical Justification: breaks unrelated software X-Debbugs-Cc: j...@ucw.cz Dear Maintainer, DKMS fails to compile the module with the 6.4 kernels; see https://github.com/linux-thinkpad/tp_smapi, and the patch https://github.com/linux-thinkpad/tp_smapi/commit/0c3398b1acf2a2cabd9cee91dc3fe3d35805fa8b Jan -- System Information: Debian Release: trixie/sid APT prefers experimental APT policy: (800, 'experimental'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.3.12-x64v4-xanmod1 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER, TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tp-smapi-dkms depends on: ii dkms 3.0.11-3 tp-smapi-dkms recommends no packages. tp-smapi-dkms suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: tp-smapi Source-Version: 0.44-1 Done: Evgeni Golov We believe that the bug you reported is fixed in the latest version of tp-smapi, 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 1038...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Evgeni Golov (supplier of updated tp-smapi 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: Mon, 31 Jul 2023 20:09:41 +0200 Source: tp-smapi Architecture: source Version: 0.44-1 Distribution: unstable Urgency: medium Maintainer: Evgeni Golov Changed-By: Evgeni Golov Closes: 1038207 Changes: tp-smapi (0.44-1) unstable; urgency=medium . * New upstream version 0.44 + Support 6.4 kernel Closes: #1038207 Checksums-Sha1: abb10a045e2ea27eb4be9a6ffd5a23719bac141f 1907 tp-smapi_0.44-1.dsc 16c2229068628ff58d363f61de0d094b2177ea5c 40724 tp-smapi_0.44.orig.tar.gz 64d8a1f944d9a34a2032392edf18fd943ca64c4e 4980 tp-smapi_0.44-1.debian.tar.xz 9b72246616e80a5dbb7f2ebe40d667ec7b231e1c 6029 tp-smapi_0.44-1_source.buildinfo Checksums-Sha256: 477f895302c88817e9efde36a73a81f251bbe70c04c46b85b6cfd34a01324f3b 1907 tp-smapi_0.44-1.dsc cccff96e8994bfc9dfe2bec071c4dfb6baf060f988bc338bbab95e639fd4c126 40724 tp-smapi_0.44.orig.tar.gz 6a95e1d5d1df6ff60fbac019e025153587d1002ba3709930c231558e5dc45a44 4980 tp-smapi_0.44-1.debian.tar.xz 7122f3f4458accd57d69f8fbc7f6d4a829e473df1449b116b022806bda05f3d6 6029 tp-smapi_0.44-1_source.buildinfo Files: de37c8bbb26684d1230c6213e42fccb8 1907 kernel optional tp-smapi_0.44-1.dsc e74404020e402b2fa871bcc3833632c7 40724 kernel optional tp-smapi_0.44.orig.tar.gz 23d759443963a6f3ff70bbb7ae34c072 4980 kernel optional tp-smapi_0.44-1.debian.tar.xz a5118fba51a0071a241917793df15032 6029 kernel optional tp-smapi_0.44-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEExW57amdnGPa81AdGTrsFQAtaiq4FAmTIAcYACgkQTrsFQAta iq5BwA//UuwIuL3dXPi8doCyHDCrJS82rx5GA95p7bye1cRLr7Kt392o9Bzuj/TD 9zcmtWKwb+kHQn2m/YTVOBcWSAym2HA3BDvdffLy45OQvjGPt/FZxjNsS8joeW9t JjLiu+NrTouCCPxyk/N0qbjNXyMZJyLMntZbDTUvL9QVEUmhRcxcp89VY6v2y7C1 pt2JYOR2POPQCKhA0Vr9nVsQ9i1R7xKZeM9F47WEodmzD1uciuoH+dB023G1S2c7 Ql7iFVnHacZvjVpSk7zbE6gNAc8BQ8Opj5/dD4qSR+0Q0HVZeldZe5IQfrNnEgUs ba0/nVA5BI04Vfqe6AIoKgd8s36nqLM3jrG+lD3Mg/7+pxMhDgvIsVisefr+Q7f0 FigbQdw4cEXSflt/NILQJ2dz4LjWaLObDm41/5HBt+W+FcgsRXeQ7f7DdwComUd6 +iwxkyr7X/hotyat2rX32sCo46mA7NfsAN14d3TZGdl3qV8Y+XHj8aBLeox5fCK3 ZZsetVW19nNoHRiir24RWa8puojs8azCCWYJYL+aawetqdQbyniB/OLeKrar344H 2e2ixwLpdd3t/WcKO5ld85+OeD5rcalYJoQaSekAoUdBhntPvnxK6E/zrcxJ1d4L eTFyrbg3Hr3Q1PCCPGFAHpNAjGxG9dUs++pTuaGShNYeu4Mygko= =an1S -END PGP SIGNATURE End Message ---
Processed: tagging 1040568, tagging 1040573, tagging 1040574, tagging 1040576, tagging 1040578, tagging 1040579
Processing commands for cont...@bugs.debian.org:
> tags 1040568 + sid trixie
Bug #1040568 {Done: Timo Röhling } [src:weresync]
weresync: implicitly depends on python3-py
Added tag(s) sid and trixie.
> tags 1040573 + sid trixie
Bug #1040573 {Done: Étienne Mollier } [src:python-screed]
python-screed: implicitly depends on python3-pkg-resources
Added tag(s) sid and trixie.
> tags 1040574 + sid trixie
Bug #1040574 {Done: Timo Röhling } [src:python-qrcode]
python-qrcode: implicitly depends on python3-pkg-resources
Added tag(s) sid and trixie.
> tags 1040576 + sid trixie
Bug #1040576 {Done: Timo Röhling } [src:python-mongomock]
python-mongomock: implicitly depends on python3-pkg-resources
Added tag(s) trixie and sid.
> tags 1040578 + sid trixie
Bug #1040578 {Done: Timo Röhling } [src:python-molotov]
python-molotov: implicitly depends on python3-pkg-resources
Added tag(s) sid and trixie.
> tags 1040579 + sid trixie
Bug #1040579 {Done: Timo Röhling }
[src:python-gflanguages] python-gflanguages: implicitly depends on
python3-pkg-resources
Added tag(s) sid and trixie.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1040568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040568
1040573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040573
1040574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040574
1040576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040576
1040578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040578
1040579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 1040398, tagging 1040406, tagging 1040410, tagging 1040412, tagging 1040413, tagging 1040424
Processing commands for cont...@bugs.debian.org:
> tags 1040398 + sid trixie
Bug #1040398 {Done: Timo Röhling }
[src:python-pytest-benchmark] python-pytest-benchmark: undeclared dependency on
python3-py
Added tag(s) sid and trixie.
> tags 1040406 + sid trixie
Bug #1040406 {Done: Luca Boccassi } [python3-azure-cli]
python3-azure-cli - fails with No module named 'azure.mgmt.compute.v2022_11_01'
Added tag(s) sid and trixie.
> tags 1040410 + sid trixie
Bug #1040410 {Done: Scott Talbert } [src:apipkg] apipkg:
implicitly depends on python3-py
Added tag(s) trixie and sid.
> tags 1040412 + sid trixie
Bug #1040412 {Done: Timo Röhling } [src:django-q]
django-q: implicitly depends on python3-pkg-resources
Added tag(s) sid and trixie.
> tags 1040413 + sid trixie
Bug #1040413 {Done: Shengjing Zhu } [src:dumb-init] dumb-init:
implicitly depends on python3-py
Added tag(s) sid and trixie.
> tags 1040424 + sid trixie
Bug #1040424 {Done: Timo Röhling }
[src:python-pytest-random-order] python-pytest-random-order: implicitly depends
on python3-py
Added tag(s) trixie and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1040398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040398
1040406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040406
1040410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040410
1040412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040412
1040413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040413
1040424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 1042769, tagging 1041881, tagging 1041666, tagging 1041640, tagging 1041639, tagging 1041341 ...
Processing commands for cont...@bugs.debian.org:
> tags 1042769 + sid trixie
Bug #1042769 [provean] provean: incompatible with cd-hit >= 4.8.1-4
Added tag(s) sid and trixie.
> tags 1041881 + sid trixie
Bug #1041881 [src:winwrangler] RM: winwrangler -- RoQA; depends on gtk2; low
popcon
Added tag(s) sid and trixie.
> tags 1041666 + sid trixie
Bug #1041666 [src:pytorch-vision] pytorch-vision: FTBFS with ffmpeg 6.0
Added tag(s) sid and trixie.
> tags 1041640 + sid trixie
Bug #1041640 [src:sdb] RM: sdb -- RoQA; unpackaged upstream versions;
unmaintained dependency; low popcon
Added tag(s) trixie and sid.
> tags 1041639 + sid trixie
Bug #1041639 [src:mono-debugger-libs] RM: mono-debugger-libs -- RoQA;
unpackaged upstream changes; unmaintained dependency
Added tag(s) trixie and sid.
> tags 1041341 + sid trixie
Bug #1041341 [src:html5lib] html5lib: FTBFS on unstable
Added tag(s) sid and trixie.
> tags 1040580 + sid trixie
Bug #1040580 {Done: Timo Röhling } [src:oz] oz: implicitly
depends on python3-py
Added tag(s) trixie and sid.
> tags 1040718 + sid trixie
Bug #1040718 {Done: Timo Röhling } [src:fclib] fclib:
autopkgtest failure due to new CMake deprecation warning
Added tag(s) trixie and sid.
> tags 1040723 + sid trixie
Bug #1040723 {Done: Stephan Lachnit } [src:cppzmq]
cppzmq: autopkgtest failure due to new CMake deprecation warning
Added tag(s) trixie and sid.
> tags 1040728 + sid trixie
Bug #1040728 {Done: Andrea Pappacoda } [src:glm] glm:
autopkgtest failure due to new CMake deprecation warning
Added tag(s) sid and trixie.
> tags 1040729 + sid trixie
Bug #1040729 [src:oce] oce: autopkgtest failure due to new CMake deprecation
warning
Added tag(s) sid and trixie.
> tags 1040731 + sid trixie
Bug #1040731 [src:wslay] wslay: autopkgtest failure due to new CMake
deprecation warning
Added tag(s) sid and trixie.
> tags 1040733 + sid trixie
Bug #1040733 {Done: Gianfranco Costamagna }
[src:docopt.cpp] docopt.cpp: autopkgtest failure due to new CMake deprecation
warning
Added tag(s) trixie and sid.
> tags 1040735 + sid trixie
Bug #1040735 {Done: Timo Röhling } [src:ms-gsl] ms-gsl:
autopkgtest failure due to new CMake deprecation warning
Added tag(s) trixie and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1040580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040580
1040718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040718
1040723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040723
1040728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040728
1040729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040729
1040731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040731
1040733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040733
1040735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040735
1041341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041341
1041639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041639
1041640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041640
1041666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041666
1041881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041881
1042769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042769
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1040840: marked as done (tp-smapi-dkms: Thinkpad fails to wake from sleep correctly with tp-smapi-dkms after bookworm upgrade)
Your message dated Mon, 31 Jul 2023 20:27:00 +0200 with message-id <20230731182700.tqu6uknsm6wke...@nana.phantasia.die-welt.net> and subject line Re: Bug#1040840: tp-smapi-dkms: Thinkpad fails to wake from sleep correctly with tp-smapi-dkms after bookworm upgrade has caused the Debian Bug report #1040840, regarding tp-smapi-dkms: Thinkpad fails to wake from sleep correctly with tp-smapi-dkms after bookworm upgrade 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.) -- 1040840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040840 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tp-smapi-dkms Severity: serious Justification: Preface/0 X-Debbugs-Cc: senc...@riseup.net Dear Maintainer, After upgrading to from bulleye to bookworm (Kernel version 6.1.0-9) I experienced frequent freezes after wake. The power LED would light up, and I was able to toggle the keyboard backlight, but no other buttons responded (such as Fn-Lock light) and the screen was black. One single time the screen showed the login window, but still everything was unresponsive. After trying various changes I removed all install DKMS modules one by one, until I found that just with tp-smapi-dkms uninstalled there has been no freezes in the last week (before the machine would freeze approx. 60% of times after wake, multiple times a day). Thinkpad T470 -- System Information: Debian Release: 12.0 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-security'), (400, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tp-smapi-dkms depends on: ii dkms 3.0.10-8 tp-smapi-dkms recommends no packages. tp-smapi-dkms suggests no packages. --- End Message --- --- Begin Message --- Hi Caren, On Sun, Jul 30, 2023 at 05:21:16PM +0200, Caren Hern wrote: > Hi Evgeni, > > the problem started haapping again, after i purged the package and recreated > the initramfs. So i can conclude that tmp smapi is not too blame. Thanks for the info, I am therefore marking the bug in Debian as "done", as there was never a bug in that part to begin with. > If you have any suggestions what i could do to find out what causes this, i > would be very happy. I am afraid I have no "good" solution for this. Certainly one way would be to test "all" kernels between bullseye and bookworm (you can find those on https://snapshot.debian.org/) -- but given the issue takes a long time to reproduce, this is probably a very long endavour. Sorry, I am not much of a help here. Evgeni > > Have a nice day! > > Am 12.07.23 um 09:21 schrieb Evgeni Golov: > > On Wed, Jul 12, 2023 at 09:06:36AM +0200, Caren Hern wrote: > > > Hi Evgeni, > > > > > > yes I have suspend active. Hibernate was never working. > > > > Okay, I can at least double-check that against the machines I have here! > > > > > I am also confused now, because I just reinstalled the package (no errors) > > > but indead when I try to manually load it using modprobe it indead throws > > > an > > > error (ERROR: could not insert 'tp_smapi': No such device or address). > > > > Yeah, that's more like what I've expected. The SMAPI interface was > > removed in the *20/*30 series in favor of plain ACPI and the module > > should (rightfully) refuse to load if it can't find SMAPI. > > > > The `thinkpad_ec` module has a `force_io` parameter to make it load on > > *some* half-supported models, but even that shouldn't do anything when > > there is no SMAPI at all. > > > > > I just don't understand how the issue suddenly disappeared after removing > > > the package. I am wondering if its something with some other part of DKMS. > > > Because straight after the upgrade the issue was there a lot, then I > > > reinstalled the two packages which have kernel modules (tp-smapi-dkms and > > > broadcom-sta-dkms) because I thought maybe they were built for the wrong > > > kernel or something and the issue went away for two weeks, until it > > > suddenly > > > reappeared and subsequently disappeared again after I completely removed > > > the > > > tp-smapi package. > > > > dkms *should* properly detect any kernel changes and rebuild stuff. > > > > > One time after a freeze I read through dmesg but didn't find anything that > > > looked of
Bug#1041644: marked as done (smuxi: FTBFS (source pkg): cli-common-dev missing)
Your message dated Mon, 31 Jul 2023 18:18:10 + with message-id and subject line Bug#1041644: fixed in smuxi 1.1-1.1 has caused the Debian Bug report #1041644, regarding smuxi: FTBFS (source pkg): cli-common-dev missing 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.) -- 1041644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041644 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: smuxi Version: 1.1-1 Build-Depends misses the cli-common-dev, which is only included in Build-Depends-Indep. Therefore, building the source package only fails: dh: error: unable to load addon cli: Can't locate Debian/Debhelper/Sequence/cli.pm in @INC (you may need to install the Debian::Debhelper::Sequence::cli module) (@INC contains: /etc/perl /usr/local/lib/i386-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/i386-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/i386-linux-gnu/perl-base /usr/lib/i386-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl) at (eval 4) line 1. --- End Message --- --- Begin Message --- Source: smuxi Source-Version: 1.1-1.1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of smuxi, 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 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated smuxi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 21 Jul 2023 18:06:31 +0200 Source: smuxi Architecture: source Version: 1.1-1.1 Distribution: unstable Urgency: medium Maintainer: Mirco Bauer Changed-By: Bastian Germann Closes: 1041644 Changes: smuxi (1.1-1.1) unstable; urgency=medium . * Non-maintainer upload * Drop notify and gtkspell (part of #967750) * Move cli-common-dev to Build-Depends (Closes: #1041644) . [ Debian Janitor ] * Remove constraints unnecessary since buster Checksums-Sha1: 0ff160b2e9c4221260fc85513528f9d83a4e3099 2339 smuxi_1.1-1.1.dsc 6ac6a53e4eec0bbcb0522a69333cd7edfa140124 14384 smuxi_1.1-1.1.debian.tar.xz e0682df608714127c463fc002c9dc86635ab915e 17190 smuxi_1.1-1.1_source.buildinfo Checksums-Sha256: 58101b861b8411dcb99d0a160695c3b611608deb31c48ae66200f93d1e284527 2339 smuxi_1.1-1.1.dsc 9dd40e7980e475fbc9773a25a0824137bb9fae0ce1c184488201961ba2c22245 14384 smuxi_1.1-1.1.debian.tar.xz c6832ebd69552efea537b68a30e34cadfad62d1d8cfb06aa83fe07679b32cf04 17190 smuxi_1.1-1.1_source.buildinfo Files: 75acb306346a2324e59dce9c2e8245c3 2339 gnome optional smuxi_1.1-1.1.dsc 5c22862dd83397f2813ac1e92384c5a8 14384 gnome optional smuxi_1.1-1.1.debian.tar.xz 8c35085fa1e1a85a70e644bc51f884a9 17190 gnome optional smuxi_1.1-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmS6shYQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFGTRC/wODJbecXXP/DlYgZpXyn4NSYBTrwxTf9XZ nyxxr0wPaUiO+Aps5SBCe8qm+rHAl7pejzLGkik2/Fs20Tk3q5W15/jpNYdoJ9pZ uEuhr3sushCM4eAKMBvWKFP/++ZGpg00rmfWDaow/hXR4bXkiMT9zzVY7ZtiLUN+ 0eYAzILVhWXyzCB1PBHiLCoYB2yDR9PRpvprz1QUdVO1rcDxnZxTfqXlgw7NjTbx gXDg4YfAPTRYdji4jZSjeOTqDKjEXyvsQvccQzjQLrdEZ71QHT9ERwZuJeiWaMas acxfxNxKLV+ZkDynhMwh+atTMfQsu6ScvcQQpv+j5qjk//u2GCtuq4+LbuVpYC3U VDXnR8eGZEiNC0WffWiUgTAQ8+IX/xRtzB/hZlZ18LTWCUINqTVnEMMSyCjaW1ov 09QhpfwXN+jhfChOiAlhquAikLQyj/lV7igQarCbhCQztvNQVXSvu9eVNvhUGRuy WiH5Cn719jpvgAmt3mm+/RS96YMx9ZI= =RF2D -END PGP SIGNATURE End Message ---
Processed: forcibly merging 1040748 1042301
Processing commands for cont...@bugs.debian.org: > forcemerge 1040748 1042301 Bug #1040748 [src:pycairo] ftbfs in pycairo with meson 1.2.0 rc2 Bug #1040748 [src:pycairo] ftbfs in pycairo with meson 1.2.0 rc2 Added tag(s) sid and trixie. Bug #1042301 [src:pycairo] pycairo: FTBFS: dh_missing: error: missing files, aborting Merged 1040748 1042301 > thanks Stopping processing here. Please contact me if you need assistance. -- 1040748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040748 1042301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042301 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1042499, tagging 1042501, tagging 1041493, tagging 1041507, tagging 1041851
Processing commands for cont...@bugs.debian.org:
> tags 1042499 + sid trixie
Bug #1042499 [src:ocaml-duppy] Depends on obsolete pcre
Added tag(s) trixie and sid.
> tags 1042501 + sid trixie
Bug #1042501 [src:ocsigenserver] Depends on obsolete pcre
Added tag(s) trixie and sid.
> tags 1041493 + sid trixie
Bug #1041493 [src:wlroots] wlroots: FTBFFS with ffmpeg 6.0
Added tag(s) sid and trixie.
> tags 1041507 + sid trixie
Bug #1041507 {Done: Pino Toscano } [src:subtitlecomposer]
subtitlecomposer: FTBFS with ffmpeg 6.0
Added tag(s) sid and trixie.
> tags 1041851 + sid trixie
Bug #1041851 {Done: Birger Schacht } [src:cage] cage: FTBFS
with wlroots 0.16
Added tag(s) trixie and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1041493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041493
1041507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041507
1041851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041851
1042499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042499
1042501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042501
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 1041342, tagging 1041381, tagging 1041207, tagging 1040753
Processing commands for cont...@bugs.debian.org:
> tags 1041342 + sid trixie
Bug #1041342 [src:lava] lava: autopkgtest failure with pytest 7.4
Added tag(s) trixie and sid.
> tags 1041381 + sid trixie
Bug #1041381 [ueberzug] ueberzug breaks with pillow 10
Added tag(s) sid and trixie.
> tags 1041207 + sid trixie
Bug #1041207 {Done: Adam Borowski } [debootstrap]
debootstrap: bad NMU produces buildds not supported by dpkg _and_ CTTE
Added tag(s) sid and trixie.
> tags 1040753 + sid trixie
Bug #1040753 [src:gupnp-tools] FTBFS in gupnp-tools with meson 1.2.0 rc2
Added tag(s) sid and trixie.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1040753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040753
1041207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041207
1041342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041342
1041381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041381
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 1040411
Processing commands for cont...@bugs.debian.org:
> tags 1040411 + sid trixie
Bug #1040411 {Done: Diane Trout } [src:cloudpickle]
cloudpickle: implicitly depends on python3-py
Added tag(s) sid and trixie.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1040411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040411
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:yade
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:yade > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1037905 (http://bugs.debian.org/1037905) > # Bug title: yade: ftbfs with GCC-13 > # * https://gitlab.com/yade-dev/trunk/-/issues/315 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1037905 + fixed-upstream Bug #1037905 [src:yade] yade: ftbfs with GCC-13 Added tag(s) fixed-upstream. > usertags 1037905 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1037905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037905 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042769: provean: incompatible with cd-hit >= 4.8.1-4
Package: provean Version: 1.1.5+ds-2 Severity: serious Hello, Current provean package is broken: it segfaults while parsing the output of cd-hit. The most recent compatible version of cd-hit seems to be 4.6.4-1. I hope to come up with a patch sooner or later. Andrius
Bug#1042193: marked as done (wasmedge: FTBFS: ld: ../../lib/api/libwasmedge.so.0.0.3: undefined reference to `WasmEdge::Fault::emitFault(WasmEdge::ErrCode)')
Your message dated Mon, 31 Jul 2023 16:28:31 + with message-id and subject line Bug#1042193: fixed in wasmedge 0.13.3+dfsg-1 has caused the Debian Bug report #1042193, regarding wasmedge: FTBFS: ld: ../../lib/api/libwasmedge.so.0.0.3: undefined reference to `WasmEdge::Fault::emitFault(WasmEdge::ErrCode)' 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.) -- 1042193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042193 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wasmedge Version: 0.13.1+dfsg-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -Wl,--export-dynamic -rdynamic > CMakeFiles/wasmedge.dir/wasmedge.cpp.o -o wasmedge > -Wl,-rpath,"\$ORIGIN/../../lib/api::" > ../../lib/api/libwasmedge.so.0.0.3 > /usr/lib/x86_64-linux-gnu/libspdlog.so.1.10.0 > /usr/lib/x86_64-linux-gnu/libfmt.so.9.1.0 > /usr/bin/ld: ../../lib/api/libwasmedge.so.0.0.3: undefined reference to > `WasmEdge::Fault::emitFault(WasmEdge::ErrCode)' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2023/07/26/wasmedge_0.13.1+dfsg-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: wasmedge Source-Version: 0.13.3+dfsg-1 Done: Faidon Liambotis We believe that the bug you reported is fixed in the latest version of wasmedge, 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 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Faidon Liambotis (supplier of updated wasmedge 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: Mon, 31 Jul 2023 16:47:02 +0300 Source: wasmedge Architecture: source Version: 0.13.3+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Faidon Liambotis Changed-By: Faidon Liambotis Closes: 1042193 Changes: wasmedge (0.13.3+dfsg-1) unstable; urgency=medium . * New upstream release. * Drop libboost-all-dev dependency, as Boost was dropped as a dependency in the 0.13.0 release. * Fix FTBFS with gcc-13, by removing "inline" from Fault::emitFault. (Closes: #1042193) Checksums-Sha1: 18a583b48a1a7fe1ab55b544ea28b400787f0baa 2294 wasmedge_0.13.3+dfsg-1.dsc 78178a198d7b35d532b16786fc65b5e2b98d2d67 2274196 wasmedge_0.13.3+dfsg.orig.tar.xz bf684c3960343fe081983064be300e9717fb8353 10752 wasmedge_0.13.3+dfsg-1.debian.tar.xz bab6609baf1920d2a04ae4743156183b1ad86cd8 9345 wasmedge_0.13.3+dfsg-1_amd64.buildinfo Checksums-Sha256: 7f3758231bb35b6d9ce32d5cbe7792aab5841608f4b025f51b54f25f51568e8d 2294 wasmedge_0.13.3+dfsg-1.dsc 48947d2b43f1c042940799c86988fcd0be34aaa84a70c048fd38a60910144fe3 2274196 wasmedge_0.13.3+dfsg.orig.tar.xz 4022464ab91be70f5534524520ed14f72cd9910a945b97651d26bf8fafc4fbae 10752 wasmedge_0.13.3+dfsg-1.debian.tar.xz 264b079558dc715ce1544b099543bcf65a21e7c7599e9af65711274a66a32a08 9345 wasmedge_0.13.3+dfsg-1_amd64.buildinfo Files: 6358542f688e35944bd0265d40f40463 2294 web optional wasmedge_0.13.3+dfsg-1.dsc fa9042f3dee4cc47b9eedc8df9e05bb0 2274196 web optional wasmedge_0.13.3+dfsg.orig.tar.xz 2eb707588705ce60f0ce39c6b269788e
Bug#1041307: xtrx-dkms: module fails to build for Linux 6.4: error: too many arguments to function 'class_create'
Hi,
Thanks for reporting the bug.
I've made a patch to fix this bug. As attachment.
I plan to do the NMU.
I'll upload to delay/10 queue after 3 days if no one complains.
Yours,
Paul
diff -Nru xtrx-dkms-0.0.1+git20190320.5ae3a3e/debian/changelog
xtrx-dkms-0.0.1+git20190320.5ae3a3e/debian/changelog
--- xtrx-dkms-0.0.1+git20190320.5ae3a3e/debian/changelog2023-06-24
04:22:04.0 +0800
+++ xtrx-dkms-0.0.1+git20190320.5ae3a3e/debian/changelog2023-08-01
00:08:42.0 +0800
@@ -1,3 +1,11 @@
+xtrx-dkms (0.0.1+git20190320.5ae3a3e-3.4) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix dkms build failure with kernel 6.4 (Closes: #1041307)
+- add debian/patches/0004-xtrx.c-fix-build-error-with-kernel-6.4.patch
+
+ -- Ying-Chun Liu (PaulLiu) Tue, 01 Aug 2023 00:08:42
+0800
+
xtrx-dkms (0.0.1+git20190320.5ae3a3e-3.3) unstable; urgency=low
* Non-maintainer upload.
diff -Nru
xtrx-dkms-0.0.1+git20190320.5ae3a3e/debian/patches/0004-xtrx.c-fix-build-error-with-kernel-6.4.patch
xtrx-dkms-0.0.1+git20190320.5ae3a3e/debian/patches/0004-xtrx.c-fix-build-error-with-kernel-6.4.patch
---
xtrx-dkms-0.0.1+git20190320.5ae3a3e/debian/patches/0004-xtrx.c-fix-build-error-with-kernel-6.4.patch
1970-01-01 08:00:00.0 +0800
+++
xtrx-dkms-0.0.1+git20190320.5ae3a3e/debian/patches/0004-xtrx.c-fix-build-error-with-kernel-6.4.patch
2023-08-01 00:08:42.0 +0800
@@ -0,0 +1,20 @@
+From: "Ying-Chun Liu (PaulLiu)"
+Bug-Debian: http://bugs.debian.org/1041307
+Subject: [PATCH] xtrx.c: fix build error with kernel 6.4
+Last-Update: 2023-06-24
+Index: xtrx-dkms-0.0.1+git20190320.5ae3a3e/xtrx.c
+===
+--- xtrx-dkms-0.0.1+git20190320.5ae3a3e.orig/xtrx.c
xtrx-dkms-0.0.1+git20190320.5ae3a3e/xtrx.c
+@@ -1532,7 +1532,11 @@ static int __init xtrx_init(void)
+ goto failed_chrdev;
+ }
+
++#if LINUX_VERSION_CODE < KERNEL_VERSION(6, 4, 0)
+ xtrx_class = class_create(THIS_MODULE, CLASS_NAME);
++#else
++ xtrx_class = class_create(CLASS_NAME);
++#endif
+ if (IS_ERR(xtrx_class)) {
+ printk(KERN_NOTICE PFX "Unable to register xtrx class\n");
+ goto failed_setup_cdev;
diff -Nru xtrx-dkms-0.0.1+git20190320.5ae3a3e/debian/patches/series
xtrx-dkms-0.0.1+git20190320.5ae3a3e/debian/patches/series
--- xtrx-dkms-0.0.1+git20190320.5ae3a3e/debian/patches/series 2023-06-24
04:21:41.0 +0800
+++ xtrx-dkms-0.0.1+git20190320.5ae3a3e/debian/patches/series 2023-08-01
00:08:42.0 +0800
@@ -1,3 +1,4 @@
0001-xtrx-fix-PCI-DMA-allow-free-with-kernel-5.18.patch
0002-xtrx.c-fix-build-error-with-kernel-6.1.patch
0003-xtrx.c-fix-build-error-with-kernel-6.3.patch
+0004-xtrx.c-fix-build-error-with-kernel-6.4.patch
From: "Ying-Chun Liu (PaulLiu)"
Bug-Debian: http://bugs.debian.org/1041307
Subject: [PATCH] xtrx.c: fix build error with kernel 6.4
Last-Update: 2023-06-24
Index: xtrx-dkms-0.0.1+git20190320.5ae3a3e/xtrx.c
===
--- xtrx-dkms-0.0.1+git20190320.5ae3a3e.orig/xtrx.c
+++ xtrx-dkms-0.0.1+git20190320.5ae3a3e/xtrx.c
@@ -1532,7 +1532,11 @@ static int __init xtrx_init(void)
goto failed_chrdev;
}
+#if LINUX_VERSION_CODE < KERNEL_VERSION(6, 4, 0)
xtrx_class = class_create(THIS_MODULE, CLASS_NAME);
+#else
+ xtrx_class = class_create(CLASS_NAME);
+#endif
if (IS_ERR(xtrx_class)) {
printk(KERN_NOTICE PFX "Unable to register xtrx class\n");
goto failed_setup_cdev;
OpenPGP_0x44173FA13D05.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1040223: marked as done (libimage-imlib2-perl: Creates empty package on bookworm upwards (maybe because of libimlib2-dev?))
Your message dated Mon, 31 Jul 2023 16:01:26 +
with message-id
and subject line Bug#1040223: fixed in libimage-imlib2-perl 2.03-1.2
has caused the Debian Bug report #1040223,
regarding libimage-imlib2-perl: Creates empty package on bookworm upwards
(maybe because of libimlib2-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.)
--
1040223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040223
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libimage-imlib2-perl
Version: 2.03-1.1
Severity: grave
Tags: bookworm trixie sid
Justification: renders package unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
While looking at Niko's and Dom's first rebuilds for perl 5.38, I
noticed that libimage-imlib2-perl "successfully" builds but creates
a basically empty package:
http://perl.debian.net/rebuild-logs/perl-5.38/libimage-imlib2-perl_2.03-1.1/libimage-imlib2-perl_2.03-1.1.buildlog
dh_auto_configure -a
dh_auto_configure: warning: Compatibility levels before 10 are deprecated
(level 8 in use)
/usr/bin/perl -I. Build.PL --installdirs vendor
You must install the imlib2 library before you can install
Image::Imlib2. You can obtain imlib2 from
http://sourceforge.net/projects/enlightenment/
Alternatively, if you have downloaded and installed imlib2 and this
still will not work, modify the $CONFIG variable inside Build.PL to
point to the imlib2-config program that provides.
…
drwxr-xr-x root/root 0 2023-06-28 20:39 ./
drwxr-xr-x root/root 0 2023-06-28 20:39 ./usr/
drwxr-xr-x root/root 0 2023-06-28 20:39 ./usr/share/
drwxr-xr-x root/root 0 2023-06-28 20:39 ./usr/share/doc/
drwxr-xr-x root/root 0 2023-06-28 20:39
./usr/share/doc/libimage-imlib2-perl/
-rw-r--r-- root/root 440 2011-10-16 00:34
./usr/share/doc/libimage-imlib2-perl/NEWS.Debian.gz
-rw-r--r-- root/root 215 2023-06-28 20:39
./usr/share/doc/libimage-imlib2-perl/changelog.Debian.amd64.gz
-rw-r--r-- root/root 439 2023-06-28 20:39
./usr/share/doc/libimage-imlib2-perl/changelog.Debian.gz
-rw-r--r-- root/root 1967 2009-11-24 21:41
./usr/share/doc/libimage-imlib2-perl/changelog.gz
-rw-r--r-- root/root 561 2006-02-04 00:17
./usr/share/doc/libimage-imlib2-perl/copyright
drwxr-xr-x root/root 0 2023-06-28 20:39
./usr/share/doc/libimage-imlib2-perl/examples/
-rw-r--r-- root/root 860 2023-06-28 20:39
./usr/share/doc/libimage-imlib2-perl/examples/benchmark.pl
-rw-r--r-- root/root 639 2023-06-28 20:39
./usr/share/doc/libimage-imlib2-perl/examples/benchmark.txt
-rw-r--r-- root/root 1122 2023-06-28 20:39
./usr/share/doc/libimage-imlib2-perl/examples/maeda.pl
I tried locally, and the same happens in a sid chroot, a trixie
chroot, and also a bookworm chroot. bullseye aka oldstable is the
first distribution, where the expected files can be found (and the
above-quoted warning is not present).
The warning ("You must install the imlib2 library …") comes from
Build.PL:
4 # We need to find imlib2-config
5 my $CONFIG = "imlib2-config";
6
7 my $version = `$CONFIG --version`;
8 if (!$version) {
9warn 'You must install the imlib2 library before you can install
10 Image::Imlib2. You can obtain imlib2 from
11 http://sourceforge.net/projects/enlightenment/
12
13 Alternatively, if you have downloaded and installed imlib2 and this
14 still will not work, modify the $CONFIG variable inside Build.PL to
15 point to the imlib2-config program that provides.
16 ';
17exit 0;
18 } else {
19print "Found imlib2 $version";
20 }
21
(The `exit 0' in line 17 is typical because of CPAN testers, and
should be `exit 1' or something in Debian …)
But besides, it looks like `imlib2-config' went missing from libimlib2-dev
somewhere between 1.7.1-2 (oldstable) and 1.10.0-4+b1 (stable).
I've started to work on patch which uses pkg-config instead of
imlib2-config; good news: The package builds (as in: actually builds
code :)) in oldstable+stable+testing+sid and the
perl-5.38-rebuild-repo; but the tests only pass in oldstable,
starting with stable/bookworm (aka libimlib2-dev >= 1.10) they fail
with:
t/simple.t ..
1..21
ok 1 - use Image::Imlib2;
ok 2
ok 3
ok 4
ok 5
ok 6
ok 7
ok 8
ok 9
ok 10
ok 11
not ok 12
# Failed test at t/simple.t line 68.
# got: '0'
# expected: '1'
ok 13
ok 14
ok 15
ok 16
ok 17
ok 18
ok 19
ok 20
ok 21 - got to the
Bug#1042272: marked as done (rust-simdutf8: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 1)
Your message dated Mon, 31 Jul 2023 14:46:36 +
with message-id
and subject line Bug#1042272: fixed in rust-simdutf8 0.1.4-4
has caused the Debian Bug report #1042272,
regarding rust-simdutf8: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo
test --all returned exit code 1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1042272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-simdutf8
Version: 0.1.4-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- test --all
> debian cargo wrapper: options, profiles, parallel: ['parallel=8'] [] ['-j8']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose', '--verbose',
> '-j8', '--target', 'x86_64-unknown-linux-gnu', '--all'],) {}
>Compiling simdutf8 v0.1.4 (/<>)
> Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=simdutf8
> CARGO_MANIFEST_DIR=/<> CARGO_PKG_AUTHORS='Hans Kratz
> ' CARGO_PKG_DESCRIPTION='SIMD-accelerated UTF-8
> validation.' CARGO_PKG_HOMEPAGE='https://github.com/rusticstuff/simdutf8'
> CARGO_PKG_LICENSE='MIT OR Apache-2.0' CARGO_PKG_LICENSE_FILE=''
> CARGO_PKG_NAME=simdutf8
> CARGO_PKG_REPOSITORY='https://github.com/rusticstuff/simdutf8'
> CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=0.1.4 CARGO_PKG_VERSION_MAJOR=0
> CARGO_PKG_VERSION_MINOR=1 CARGO_PKG_VERSION_PATCH=4 CARGO_PKG_VERSION_PRE=''
> CARGO_PRIMARY_PACKAGE=1
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc
> --crate-name simdutf8 --edition=2018 src/lib.rs --error-format=json
> --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib
> --emit=dep-info,metadata,link -C embed-bitcode=no -C debuginfo=2 --cfg
> 'feature="default"' --cfg 'feature="std"' -C metadata=234f342816591bee -C
> extra-filename=-234f342816591bee --out-dir
> /<>/target/x86_64-unknown-linux-gnu/debug/deps --target
> x86_64-unknown-linux-gnu -C
> incremental=/<>/target/x86_64-unknown-linux-gnu/debug/incremental
> -L dependency=/<>/target/x86_64-unknown-linux-gnu/debug/deps -L
> dependency=/<>/target/debug/deps -C debuginfo=2 --cap-lints warn
> -C linker=x86_64-linux-gnu-gcc -C link-arg=-Wl,-z,relro --remap-path-prefix
> /<>=/usr/share/cargo/registry/simdutf8-0.1.4 --remap-path-prefix
> /<>/debian/cargo_registry=/usr/share/cargo/registry`
> Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=simdutf8
> CARGO_MANIFEST_DIR=/<> CARGO_PKG_AUTHORS='Hans Kratz
> ' CARGO_PKG_DESCRIPTION='SIMD-accelerated UTF-8
> validation.' CARGO_PKG_HOMEPAGE='https://github.com/rusticstuff/simdutf8'
> CARGO_PKG_LICENSE='MIT OR Apache-2.0' CARGO_PKG_LICENSE_FILE=''
> CARGO_PKG_NAME=simdutf8
> CARGO_PKG_REPOSITORY='https://github.com/rusticstuff/simdutf8'
> CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=0.1.4 CARGO_PKG_VERSION_MAJOR=0
> CARGO_PKG_VERSION_MINOR=1 CARGO_PKG_VERSION_PATCH=4 CARGO_PKG_VERSION_PRE=''
> CARGO_PRIMARY_PACKAGE=1
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc
> --crate-name simdutf8 --edition=2018 src/lib.rs --error-format=json
> --json=diagnostic-rendered-ansi,artifacts,future-incompat
> --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 --test --cfg
> 'feature="default"' --cfg 'feature="std"' -C metadata=60b7954468578d4b -C
> extra-filename=-60b7954468578d4b --out-dir
> /<>/target/x86_64-unknown-linux-gnu/debug/deps --target
> x86_64-unknown-linux-gnu -C
> incremental=/<>/target/x86_64-unknown-linux-gnu/debug/incremental
> -L dependency=/<>/target/x86_64-unknown-linux-gnu/debug/deps -L
> dependency=/<>/target/debug/deps -C debuginfo=2 --cap-lints warn
> -C linker=x86_64-linux-gnu-gcc -C link-arg=-Wl,-z,relro --remap-path-prefix
> /<>=/usr/share/cargo/registry/simdutf8-0.1.4 --remap-path-prefix
> /<>/debian/cargo_registry=/usr/share/cargo/registry`
> warning: lint `const_err` has been removed: converted into hard error, see
> issue #71800 for more
> information
>--> src/implementation/algorithm.rs:185:21
> |
> 185 | #[allow(const_err)] // the same, but for Rust 1.38.0
> | ^
> |
>::: src/implementation/x86/avx2.rs:261:1
>
Bug#1042379: marked as done (gemmi FTBFS with gcc 13 on i386/s390x/m68k)
Your message dated Mon, 31 Jul 2023 13:18:59 + with message-id and subject line Bug#1042379: fixed in gemmi 0.6.2+ds-5 has caused the Debian Bug report #1042379, regarding gemmi FTBFS with gcc 13 on i386/s390x/m68k 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.) -- 1042379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042379 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gemmi Version: 0.6.2+ds-4 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=gemmi=0.6.2%2Bds-4 ... In file included from /<>/include/gemmi/model.hpp:17, from /<>/include/gemmi/assembly.hpp:11, from /<>/src/assembly.cpp:3: /<>/include/gemmi/elem.hpp: In function ‘double gemmi::molecular_weight(El)’: /<>/include/gemmi/elem.hpp:100:50: error: static assertion failed: Hmm 100 | static_assert(weights[static_cast(El::D)] == 2.0141, "Hmm"); | ~^ ... This can be fixed by adding export CXXFLAGS = -fexcess-precision=fast in debian/rules For background see the first bullet point in the C++ section of https://gcc.gnu.org/gcc-13/changes.html --- End Message --- --- Begin Message --- Source: gemmi Source-Version: 0.6.2+ds-5 Done: Andrius Merkys We believe that the bug you reported is fixed in the latest version of gemmi, 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 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrius Merkys (supplier of updated gemmi 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: Mon, 31 Jul 2023 08:58:05 -0400 Source: gemmi Architecture: source Version: 0.6.2+ds-5 Distribution: unstable Urgency: medium Maintainer: Debichem Team Changed-By: Andrius Merkys Closes: 1042379 Changes: gemmi (0.6.2+ds-5) unstable; urgency=medium . * Append -fexcess-precision=fast to CXXFLAGS to fix builds on i386/s390x/m68k (Closes: #1042379) Checksums-Sha1: d95897a8d0e39ae3a8d96de7711747a8af6e22f4 2280 gemmi_0.6.2+ds-5.dsc 2ce22bb1a429e6385d12e3a4a5a914dce79d7b3a 6892 gemmi_0.6.2+ds-5.debian.tar.xz ed481265d7d1daeb8ebfa7d0301b3be33d6f65a5 8948 gemmi_0.6.2+ds-5_source.buildinfo Checksums-Sha256: f7f470d621149cef18cb456fe7566f0a81095471e74d07b996ad5b9cbaac0041 2280 gemmi_0.6.2+ds-5.dsc 29601527cbbaf4c563e5d45c99caf39e9d64cb12da716e11702e481a393a2a5a 6892 gemmi_0.6.2+ds-5.debian.tar.xz 909d5b804f2f1a6235ddb30ec3f4ada3304ba6771be88abfae4c9bd3d7f9d562 8948 gemmi_0.6.2+ds-5_source.buildinfo Files: 7631f529a20caa9574b2abbdea8c7f28 2280 science optional gemmi_0.6.2+ds-5.dsc 3cf99d31c835aed27c4d912040c3c566 6892 science optional gemmi_0.6.2+ds-5.debian.tar.xz a1402f760d4ac2b47e855eee6f407b6a 8948 science optional gemmi_0.6.2+ds-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAmTHsBMSHG1lcmt5c0Bk ZWJpYW4ub3JnAAoJEOX0P5wnNPKHUuMP/jlrmZcdjFVZyonUNC83LOGi+eZjthE1 rnsjDUwdjMATcesd626PyLOIk6T+YY03e7XdE7Vf2pnrBh6YRfBFmThU/wUQNouC RKY8Y+a6P0z/fLJqjFVJwCXKayRuS2pz2VJSGlw9PHSiQ3wQ+0IvVOhlhc28RtZ0 qw+rtKA31SGl5ZU/jpRQqUVsJxDDYfNyY9xKY4nwZrB0NTgUlXWMzDbJ3rJX+c6u oRGojl7Exsyco+JZ8iqyXeeBiTAngYpvGBnkKUheQLjr2E5O9T0pYREThoG2WH+k ObUGDJD8gS6ih29f4VZkBnq4ktP810bd2oIUdScPo9VT8+BQ7tynLhQ+2LVygddY sNB3HkTTo5IdoONeLHL83/eLuV43oXOYBuOHxu0D1mlmZ/yjmib48Dks3/zbBtBe Boo1iLf+GM5j7UXF0HOl/aaby+G/kzsmW4ap/DgkKBuRsHvx4bdDJH51bFTuI6AH WSmvBPiFDI7imD1XTFVxHnO0cnKw5AKFxWSwK6ltdCIQ/7Ea3Z+s23UF83DAeLTn aPK6l2aqftH9Ko42H4dubzJUMolzpGkE91CUPg/sRFeClZKcAqKimswhIrsvmMwf MJK//Z2kF0E7R9w3txdQ0YJ2gRyf+l1fQcAtqetuIvdb+xC8u2W2zGTAo9X7Wgzn xe05RR6j98KF =dUvD -END PGP SIGNATURE End Message ---
Bug#1042122: marked as done (primus-vk: FTBFS: primus_vk.cpp:7:10: fatal error: vk_layer_dispatch_table.h: No such file or directory)
Your message dated Mon, 31 Jul 2023 13:19:07 + with message-id and subject line Bug#1042122: fixed in primus-vk 1.6.3-1 has caused the Debian Bug report #1042122, regarding primus-vk: FTBFS: primus_vk.cpp:7:10: fatal error: vk_layer_dispatch_table.h: No such file or directory 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.) -- 1042122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042122 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: primus-vk Version: 1.6.2-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > g++ -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security > -DNV_DRIVER_PATH=\"libGLX_nvidia.so.0:/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1\" > --std=c++17 -g3 -I/usr/include/vulkan -shared -fPIC nv_vulkan_wrapper.cpp -o > libnv_vulkan_wrapper.so -Wl,-soname,libnv_vulkan_wrapper.so.1 -lX11 -lGLX > -ldl -Wl,-z,relro -Wl,-z,now > primus_vk.cpp:7:10: fatal error: vk_layer_dispatch_table.h: No such file or > directory > 7 | #include "vk_layer_dispatch_table.h" > | ^~~ > compilation terminated. > make[1]: *** [Makefile:19: libprimus_vk.so] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/07/26/primus-vk_1.6.2-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: primus-vk Source-Version: 1.6.3-1 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of primus-vk, 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 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated primus-vk 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: Mon, 31 Jul 2023 14:49:27 +0200 Source: primus-vk Architecture: source Version: 1.6.3-1 Distribution: unstable Urgency: medium Maintainer: Debian NVIDIA Maintainers Changed-By: Andreas Beckmann Closes: 1042122 Changes: primus-vk (1.6.3-1) unstable; urgency=medium . [ Felix Dörre ] * New upstream release. Resolved build compatibility with newer vulkan-validationlayers (Closes: #1042122) Checksums-Sha1: 4f3023ce7a24fc3b27972e7fc4d4f882f734e0c8 2528 primus-vk_1.6.3-1.dsc c7f2ab5229f484974ec43df535fcfa0567605bab 24806 primus-vk_1.6.3.orig.tar.gz 6ebf10126310464fcb478ff4e5275ce32d842a98 5064 primus-vk_1.6.3-1.debian.tar.xz 6f555cbab2ad9b09533f8c7c5dcdae5ee0a84be2 7907 primus-vk_1.6.3-1_source.buildinfo Checksums-Sha256: 82d517ab2ee39cf9bbc22a3b878b6c78d48c8e2861312235951cfd28c9cc80d0 2528 primus-vk_1.6.3-1.dsc 9973eff8b2eda5f30dba8349dd1e843fee3e18ccbb0f6cd38073fe4c2e61fe33 24806 primus-vk_1.6.3.orig.tar.gz 70a6bc4a4a5a27b68c296c814189bcb7aa9a8ef0332fa6f40a153309ea74cccf 5064 primus-vk_1.6.3-1.debian.tar.xz b62863a95f823413d3d4ccade583abe692c9c3bfa98af03a9274cead4851ec60 7907 primus-vk_1.6.3-1_source.buildinfo Files: 0271870aaefb945454f476b815696a4a 2528 utils optional primus-vk_1.6.3-1.dsc f8068ee9a4ee5a99322625566c5e33a3 24806 utils optional primus-vk_1.6.3.orig.tar.gz 100ba2d4ab2fee4ffe9ebc0e4d94f505 5064 utils optional primus-vk_1.6.3-1.debian.tar.xz 1277c0a5a51b62bd0dd63b83279d543a 7907 utils optional
Bug#1042009: onetbb: FTBFS on armel: error: ‘void __atomic_store_1(volatile void*, unsigned char, int)’ writing 1 byte into a region of size 0 overflows the destination [-Werror=stringop-overflow=]
I managed to reduce it to this patch, now applied to git as
1050-armel-atomic-past-buffer.patch. No idea why it help, but worked
when doing test build on armel / abel.debian.org.
--- tbb.orig/src/tbb/concurrent_monitor.h 2023-07-30 20:28:22.251868539
+
+++ tbb/src/tbb/concurrent_monitor.h2023-07-31 06:47:43.046714530 +
@@ -290,7 +290,10 @@
n = my_waitset.front();
if (n != end) {
my_waitset.remove(*n);
-to_wait_node(n)->my_is_in_list.store(false,
std::memory_order_relaxed);
+wait_node* wn = to_wait_node(n);
+if (wn) {
+wn->my_is_in_list.store(false, std::memory_order_relaxed);
+}
}
}
--
Happy hacking
Petter Reinholdtsen
Bug#1042747: dahdi-dkms: dkms.conf still lists removed pciradio.ko
On 31/07/2023 13.17, Tzafrir Cohen wrote: Trying to figure out the cause for the other error https://ci.debian.net/data/autopkgtest/testing/amd64/d/dahdi-linux/36220583/log.gz 177s MODPOST /usr/src/modules/dahdi/drivers/dahdi/Module.symvers 178s ERROR: modpost: "unregister_hdlc_device" [/usr/src/modules/dahdi/drivers/dahdi/dahdi.ko] undefined! 178s ERROR: modpost: "ppp_unregister_channel" [/usr/src/modules/dahdi/drivers/dahdi/dahdi.ko] undefined! That happens during module-assistant-autopkgtest on the -cloud- kernel ... Try this in d/tests/control: Test-Command: env BUILD_EXCLUSIVE_CONFIG="CONFIG_PCI CONFIG_USB" /usr/share/modass/module-assistant-autopkgtest dahdi (The missing symbols probably depend on other config settings, e.g. CONFIG_HDLC and CONFIG_PPP (not checked), but we don't check for them in the -dkms package either, so just reuse the existing constraint.) Andreas
Bug#1042041: marked as done (tpm2-pkcs11: FTBFS: gcc: error: unrecognized command-line option '-V')
Your message dated Mon, 31 Jul 2023 12:24:28 + with message-id and subject line Bug#1042041: fixed in tpm2-pytss 2.1.0-1 has caused the Debian Bug report #1042041, regarding tpm2-pkcs11: FTBFS: gcc: error: unrecognized command-line option '-V' 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.) -- 1042041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tpm2-pkcs11 Version: 1.9.0-0.2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc version 13.1.0 (Debian 13.1.0-9) > ... rest of stderr output deleted ... > configure:3441: $? = 0 > configure:3430: gcc -V >&5 > gcc: error: unrecognized command-line option '-V' > gcc: fatal error: no input files > compilation terminated. > configure:3441: $? = 1 > configure:3430: gcc -qversion >&5 > gcc: error: unrecognized command-line option '-qversion'; did you mean > '--version'? > gcc: fatal error: no input files > compilation terminated. > configure:3441: $? = 1 > configure:3430: gcc -version >&5 > gcc: error: unrecognized command-line option '-version' > gcc: fatal error: no input files > compilation terminated. > configure:3441: $? = 1 > configure:3461: checking whether the C compiler works > configure:3483: gcc -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now conftest.c >&5 > configure:3487: $? = 0 > configure:3537: result: yes > configure:3540: checking for C compiler default output file name > configure:3542: result: a.out > configure:3548: checking for suffix of executables > configure:3555: gcc -o conftest -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now conftest.c >&5 > configure:3559: $? = 0 > configure:3582: result: > configure:3604: checking whether we are cross compiling > configure:3612: gcc -o conftest -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now conftest.c >&5 > configure:3616: $? = 0 > configure:3623: ./conftest > configure:3627: $? = 0 > configure:3642: result: no > configure:3647: checking for suffix of object files > configure:3670: gcc -c -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 conftest.c >&5 > configure:3674: $? = 0 > configure:3696: result: o > configure:3700: checking whether the compiler supports GNU C > configure:3720: gcc -c -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 conftest.c >&5 > configure:3720: $? = 0 > configure:3730: result: yes > configure:3741: checking whether gcc accepts -g > configure:3762: gcc -c -g -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5 > configure:3762: $? = 0 > configure:3806: result: yes > configure:3826: checking for gcc option to enable C11 features > configure:3841: gcc -c -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 conftest.c >&5 > configure:3841: $? = 0 > configure:3859: result: none needed > configure:3980: checking whether gcc understands -c and -o together > configure:4003: gcc -c conftest.c -o conftest2.o > configure:4006: $? = 0 > configure:4003: gcc -c conftest.c -o conftest2.o > configure:4006: $? = 0 > configure:4018: result: yes > configure:4067: checking build system type > configure:4082: result: x86_64-pc-linux-gnu > configure:4102: checking host system type > configure:4116: result: x86_64-pc-linux-gnu > configure:4157: checking how to print strings > configure:4184: result: printf > configure:4205: checking for a sed that does not truncate output > configure:4275: result: /bin/sed > configure:4293: checking for grep that handles long lines and -e > configure:4357: result: /bin/grep > configure:4362: checking for egrep > configure:4430: result: /bin/grep -E > configure:4435: checking for fgrep > configure:4503: result: /bin/grep -F > configure:4539: checking for ld used by gcc > configure:4607: result: /usr/bin/ld > configure:4614: checking if the linker (/usr/bin/ld) is GNU ld > configure:4630: result: yes > configure:4642: checking for BSD- or MS-compatible name lister (nm) > configure:4697: result: /usr/bin/nm -B >
Bug#976697: webext-umatrix: no longer developed upstream, remove or switch to LibreMatrix or?
Source: umatrix Followup-For: Bug #976697 Forwarded: https://gitlab.com/vannilla/ematrix/ Dear Maintainer, I have asked guidance to the last fork about firefox/chromium support. If not RM is the wayto go Bastien -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386, armel Kernel: Linux 6.3.0-1-rt-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1042757: ublock-origin: embded javascript lib
Source: ublock-origin Severity: serious Justification: not prefered form of modification Dear Maintainer, src/lib include a few library that are already packaged for debian. per se it is not a serious bug, but we should try if possible after testing to use packaged version The serious bug is due that for instance punycode was not in prefered form of modification due to being wepackaged (transpiled) in order to be an ES module. They may be other transpiled package in this subdirectory Bastien signature.asc Description: This is a digitally signed message part.
Bug#1042747: dahdi-dkms: dkms.conf still lists removed pciradio.ko
Hi, Thanks. Those modules were removed. I noticed that and fixed it locally (also added two extra modules zaphfc and icE1usb). Trying to figure out the cause for the other error https://ci.debian.net/data/autopkgtest/testing/amd64/d/dahdi-linux/36220583/log.gz 177s MODPOST /usr/src/modules/dahdi/drivers/dahdi/Module.symvers 178s ERROR: modpost: "unregister_hdlc_device" [/usr/src/modules/dahdi/drivers/dahdi/dahdi.ko] undefined! 178s ERROR: modpost: "ppp_unregister_channel" [/usr/src/modules/dahdi/drivers/dahdi/dahdi.ko] undefined! 178s ERROR: modpost: "ppp_unit_number" [/usr/src/modules/dahdi/drivers/dahdi/dahdi.ko] undefined! 178s ERROR: modpost: "alloc_hdlcdev" [/usr/src/modules/dahdi/drivers/dahdi/dahdi.ko] undefined! 178s ERROR: modpost: "ppp_channel_index" [/usr/src/modules/dahdi/drivers/dahdi/dahdi.ko] undefined! 178s ERROR: modpost: "ppp_register_channel" [/usr/src/modules/dahdi/drivers/dahdi/dahdi.ko] undefined! 178s ERROR: modpost: "hdlc_close" [/usr/src/modules/dahdi/drivers/dahdi/dahdi.ko] undefined! 178s ERROR: modpost: "hdlc_start_xmit" [/usr/src/modules/dahdi/drivers/dahdi/dahdi.ko] undefined! 178s ERROR: modpost: "ppp_input" [/usr/src/modules/dahdi/drivers/dahdi/dahdi.ko] undefined! 178s ERROR: modpost: "ppp_input_error" [/usr/src/modules/dahdi/drivers/dahdi/dahdi.ko] undefined! 178s WARNING: modpost: suppressed 3 unresolved symbol warnings because there were too many) 178s make[4]: *** [/usr/src/linux-headers-6.4.0-1-common/scripts/Makefile.modpost:136: /usr/src/modules/dahdi/drivers/dahdi/Module.symvers] Error 1 178s make[3]: *** [/usr/src/linux-headers-6.4.0-1-common/Makefile:2003: modpost] Error 2 > While updating d/dkms.conf.in, you can probably drop CONFIG_PCI from > BUILD_EXCLUSIVE_CONFIG (and update the comment) CONFIG_PCI is a pre-condition to just about any DAHDI card there except the USB devices (see drivers/dahdi/Kbuild). Will update comment. > and > switch from BUILD_EXCLUSIVE_KERNEL=...(regex)... to the more readable > BUILD_EXCLUSIVE_KERNEL_MIN="5.6" (supported since dkms in trixie). I want to make the job for backporters easy, so I'll avoid this feature for now. -- Tzafrir -- mail / xmpp / matrix: tzaf...@cohens.org.il
Bug#1042532: mediawiki: Vendoring a few javascript library without source
hi, Le lun. 31 juil. 2023 à 08:27, Kunal Mehta a écrit : > > Hi, > > On 7/29/23 16:44, Bastien Roucariès wrote: > > Dear Maintainer, > > > > resources/lib/ > > (https://sources.debian.org/src/mediawiki/1:1.39.4-2/resources/lib/) > > > > include a few library already packaged for debian. > > > > Moreover some source are missing (I have only checked pako). > > These are in the preferred form for modification so I don't think > there's any issue here, but please correct me if I'm wrong. MediaWiki > often patches these libraries (e.g. jquery.ui) in this format hence IMO > meeting the "preferred form of the work for making modifications to it" > requirement of the GPL. No https://sources.debian.org/src/mediawiki/1%3A1.39.4-2/resources/lib/pako/ is webpacked in order to be transformed in es5 No source available before webpack > > > You could use the packaged library under debian > > Older versions of the package did that, but the version mismatches were > not worth it. Plus MediaWiki has a ton of user-written code that's > stored and loaded on-wiki, so deviations from the official version are > incredibly hard to test and just cause breakage everywhere. Pako is stable, I understand for jquery but sinon,,promise stuff and so on could be packaged. Moreover in all the case you should document the embed code in security tracker. And do not stick to lastest jquery is a security problem. Are you sure you have closed all the CVE ? with my javascript hat, I believe that working with upstream to improve the testing (using if needed selenium) will improve the security of mediawiki by using packaged and up to date js This bug should be solved package by package: - first by doing an analysis of stable/not stable api => stable api use packaged - for non stable and patched version => guarantee that source is here - for non stable and patched version try to create test case with upstream using selenium checking integration - move to packaged In all the case it decrease the burden from a security point of view bastien > > -- Kunal
Bug#1042754: tor: don't autostart the service on installation
Package: tor Version: 0.4.7.13-1 Severity: grave Dear Maintainer, please do not autostart the tor system service immediately after installing it using `apt install tor`. Current behavior reveals that the user installed the tor package, because connections to the tor network start immediately after the package is installed. This is problematic for a great many reasons. If apt is configured to use https sources, then it is unlikely a network observer would know that the tor package was being downloaded (unless they can correlate the size of the download with the package size of tor and dependencies, and even that is not a definitive proof). Users don't expect the tor service to start immediately after installing it, nor do they expect it to start automatically on every boot of their system. If users even want to use the tor service, then they generally configure it first before autostarting it (to setup bridges for example). I want to point out that users are not informed about nor asked for any consent to these immediate outside connections to the tor network. No privacy policy or warnings are presented to the user after `apt install tor`, the service simply starts and connects to tor with no indication that this is happening. The service should be shipped in a disabled state, so that it does not start on system boot, nor should the service start immediately after installing tor. If users wish to run the service on the system level automatically on every boot then they can do so by doing `systemctl enable tor.service`. If the tor maintainer really wishes to keep the automatic start of tor service on installation as default behavior, then they should at least create a debconf interface that asks the users if that is what they really wish to happen, so that users can give their informed consent. Additionally, many users simply start the tor executable directly, with configuration files in their home directory, when they need it instead of automatically. When users start the service manually, they are at least presented with this information: [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous Please do not autostart the tor system service immediately after installing it using `apt install tor`. -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-10-amd64 (SMP w/1 CPU thread; PREEMPT) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tor depends on: ii adduser3.134 ii libc6 2.36-9+deb12u1 ii libcap21:2.66-4 ii libevent-2.1-7 2.1.12-stable-8 ii liblzma5 5.4.1-0.2 ii libseccomp22.5.4-1+b3 ii libssl33.0.9-1 ii libsystemd0252.12-1~deb12u1 ii libzstd1 1.5.4+dfsg2-5 ii runit-helper 2.15.2 ii sysvinit-utils [lsb-base] 3.06-4 ii zlib1g 1:1.2.13.dfsg-1 Versions of packages tor recommends: ii logrotate3.21.0-1 ii tor-geoipdb 0.4.7.13-1 ii torsocks 2.4.0-1 Versions of packages tor suggests: pn apparmor-utils pn mixmaster pn nyx pn obfs4proxy pn socat pn torbrowser-launcher -- no debconf information
Bug#1042738: marked as done (ruby-rails-assets-punycode: Do not ship libjs-punycode)
Your message dated Mon, 31 Jul 2023 11:13:29 + with message-id and subject line Bug#1042738: fixed in ruby-rails-assets-punycode 2.2.3+dfsg-1 has caused the Debian Bug report #1042738, regarding ruby-rails-assets-punycode: Do not ship libjs-punycode 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.) -- 1042738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042738 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-rails-assets-punycode Severity: serious Justification: source is missing Dear Maintainer, You package node-punycode without source... I plan to fix this Bastien signature.asc Description: This is a digitally signed message part. --- End Message --- --- Begin Message --- Source: ruby-rails-assets-punycode Source-Version: 2.2.3+dfsg-1 Done: Bastien Roucariès We believe that the bug you reported is fixed in the latest version of ruby-rails-assets-punycode, 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 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastien Roucariès (supplier of updated ruby-rails-assets-punycode 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: Mon, 31 Jul 2023 10:11:49 + Source: ruby-rails-assets-punycode Architecture: source Version: 2.2.3+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Bastien Roucariès Closes: 832239 857821 1042738 Changes: ruby-rails-assets-punycode (2.2.3+dfsg-1) unstable; urgency=medium . * Team upload . [ Cédric Boutillier ] * Bump debhelper compatibility level to 9 * Remove version in the gem2deb build-dependency * Use https:// in Vcs-* fields * Bump Standards-Version to 3.9.7 (no changes needed) * Run wrap-and-sort on packaging files . [ Utkarsh Gupta ] * Add salsa-ci.yml . [ Debian Janitor ] * Trim trailing whitespace. * Use secure copyright file specification URI. * Use secure URI in debian/watch. * Bump debhelper from old 9 to 12. * Set debhelper-compat version in Build-Depends. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Update Vcs-* headers from URL redirect. * Use canonical URL in Vcs-Git. * Apply multi-arch hints. + ruby-rails-assets-punycode: Add :any qualifier for ruby dependency. + libjs-punycode: Add Multi-Arch: foreign. . [ Bastien Roucariès ] * Improve debian watch * Depend on libjs-punycode. Need a repack. (Closes: #1042738, #832239, #857821) Checksums-Sha1: 369431efb30befefb243a46176afc65e36261ea9 2177 ruby-rails-assets-punycode_2.2.3+dfsg-1.dsc 1f0b3545c79494863a27822045c0dca882e69f85 1632 ruby-rails-assets-punycode_2.2.3+dfsg.orig.tar.xz db0497f08e8ae686a6f1ee217d6f3d96df0539ba 3196 ruby-rails-assets-punycode_2.2.3+dfsg-1.debian.tar.xz 4c10c882941ae75fcbf418d8f9b561475eebb12d 15068 ruby-rails-assets-punycode_2.2.3+dfsg-1_source.buildinfo Checksums-Sha256: 9de8243d6fb01d39a79c175cd88de3b3a08f99900c776b7039efc7b463599767 2177 ruby-rails-assets-punycode_2.2.3+dfsg-1.dsc 2f4227028ad7a65c741d1ee5938af3f7fd14431ff07a851b2289d4004c14599a 1632 ruby-rails-assets-punycode_2.2.3+dfsg.orig.tar.xz 8dd287e61c6287328861ac1499ba687bd94f756fafabcba8ed5f8d2b47e3f3a3 3196 ruby-rails-assets-punycode_2.2.3+dfsg-1.debian.tar.xz f03acd99ad98eff820f2ca3881c08f748564ad892fd685f27b8f76cd6a40817f 15068 ruby-rails-assets-punycode_2.2.3+dfsg-1_source.buildinfo Files: 9fc149f8a398225722bbb0e3288d5384 2177 ruby optional ruby-rails-assets-punycode_2.2.3+dfsg-1.dsc 277c977696d1fd97ab74d8eb9ec22239 1632 ruby optional ruby-rails-assets-punycode_2.2.3+dfsg.orig.tar.xz a187c111f7feda4e021fc4b52656466b 3196 ruby optional ruby-rails-assets-punycode_2.2.3+dfsg-1.debian.tar.xz f445f47c70c95b04e213bebf0bb482e2 15068 ruby optional ruby-rails-assets-punycode_2.2.3+dfsg-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEXQGHuUCiRbrXsPVqADoaLapBCF8FAmTHjt4RHHJvdWNhQGRl Ymlhbi5vcmcACgkQADoaLapBCF+N6w/6A4yDxqfQLoSwN9cp2PbBYfv2HyfQeleE 6ijpql0o6h3WrQtN+piZE+X8dC9fbwO+zZiMPfKNWT55HjXG/cqWExUHBq4P45kQ
Bug#1042751: Missing deps when using "dune utop"
Package: utop Version: 2.13.1 Severity: serious After I made utop run by itself (report #1042749), I tried to run it through "dune utop" and found liblambda-term-ocaml-dev is needed for this to work. Cheers, J
Bug#1042749: Dependency issues make the package non-working after installation
Package: utop
Version: 2.13.1-1
Severity: grave
Installing the utop package leads to a non-working utop executable,
because it needs xdg. The libdune-ocaml-dev package provides xdg.
Installing the libdune-ocaml-dev package makes utop fail with:
Fatal error: exception Fl_package_base.No_such_package("uucp",
"required by `lambda-term'")
Installing libuucp-ocaml-dev makes utop run.
Perhaps dh_ocaml doesn't detect those runtime deps?
Cheers,
J
Bug#1042223: marked as done (pilkit: FTBFS: AttributeError: module 'PIL.Image' has no attribute 'ANTIALIAS')
Your message dated Mon, 31 Jul 2023 10:10:50 + with message-id and subject line Bug#1040633: fixed in pilkit 2.0-5 has caused the Debian Bug report #1040633, regarding pilkit: FTBFS: AttributeError: module 'PIL.Image' has no attribute 'ANTIALIAS' 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.) -- 1040633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pilkit Version: 2.0-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > cp debian/reference.png tests/assets/reference.png > dh_auto_build > I: pybuild base:240: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.11_pilkit/build/pilkit > copying pilkit/utils.py -> > /<>/.pybuild/cpython3_3.11_pilkit/build/pilkit > copying pilkit/__init__.py -> > /<>/.pybuild/cpython3_3.11_pilkit/build/pilkit > copying pilkit/exceptions.py -> > /<>/.pybuild/cpython3_3.11_pilkit/build/pilkit > copying pilkit/lib.py -> > /<>/.pybuild/cpython3_3.11_pilkit/build/pilkit > copying pilkit/pkgmeta.py -> > /<>/.pybuild/cpython3_3.11_pilkit/build/pilkit > creating > /<>/.pybuild/cpython3_3.11_pilkit/build/pilkit/processors > copying pilkit/processors/overlay.py -> > /<>/.pybuild/cpython3_3.11_pilkit/build/pilkit/processors > copying pilkit/processors/resize.py -> > /<>/.pybuild/cpython3_3.11_pilkit/build/pilkit/processors > copying pilkit/processors/utils.py -> > /<>/.pybuild/cpython3_3.11_pilkit/build/pilkit/processors > copying pilkit/processors/__init__.py -> > /<>/.pybuild/cpython3_3.11_pilkit/build/pilkit/processors > copying pilkit/processors/base.py -> > /<>/.pybuild/cpython3_3.11_pilkit/build/pilkit/processors > copying pilkit/processors/crop.py -> > /<>/.pybuild/cpython3_3.11_pilkit/build/pilkit/processors > running egg_info > writing pilkit.egg-info/PKG-INFO > writing dependency_links to pilkit.egg-info/dependency_links.txt > writing top-level names to pilkit.egg-info/top_level.txt > writing manifest file 'pilkit.egg-info/SOURCES.txt' > reading manifest file 'pilkit.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no files found matching '*.jpg' under directory 'tests' > adding license file 'LICENSE' > adding license file 'AUTHORS' > writing manifest file 'pilkit.egg-info/SOURCES.txt' > make[1]: Leaving directory '/<>' >dh_auto_test -O--buildsystem=pybuild > I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11_pilkit/build; > python3.11 -m nose -v tests > tests.test_processors.test_smartcrop ... ok > tests.test_processors.test_resizetofill ... ERROR > tests.test_processors.test_resizetofit ... ERROR > Regression test for matthewwithanm/pilkit#1 ... ERROR > tests.test_processors.test_resizetofit_mat ... ERROR > Test that the ColorOverlay processor ... ok > Test that the Resize processor antialiases. ... ERROR > Test that the upscale argument works as expected. ... ERROR > tests.test_processors.test_should_raise_exception_if_anchor_is_passed_and_crop_is_set_to_false > ... ok > tests.test_processors.test_should_set_crop_to_true_if_anchor_is_passed_without_crop > ... ok > tests.test_processors.test_should_raise_exception_when_crop_is_passed_without_height_and_width > ... ok > tests.test_processors.test_make_gifs_opaque ... ok > tests.test_processors.test_should_call_resizetofill_when_crop_and_ancho_is_passed > ... ok > tests.test_processors.test_should_call_resizetofit_when_crop_is_not_passed > ... ok > tests.test_processors.test_should_call_smartresize_when_crop_not_passed ... ok > tests.test_processors.test_should_repass_upscale_option_false ... ok > tests.test_processors.test_should_repass_upscale_option_true ... ok > tests.test_utils.test_extension_to_format ... ok > tests.test_utils.test_format_to_extension_no_init ... ok > tests.test_utils.test_unknown_format ... ok > tests.test_utils.test_unknown_extension ... ok > Ensure default extensions are honored. ... ok > tests.test_utils.test_filewrapper ... ok > Test that ``save_image`` accepts filename strings (not just file objects). > ... ok > Make sure formats are normalized by ``prepare_image()``. ... ok > Make sure the ``quiet`` util doesn't error if devnull is unwriteable. ... ok > > == > ERROR: tests.test_processors.test_resizetofill >
Bug#1040633: marked as done (pilkit autopkg tests fail with pillow 10.0.0)
Your message dated Mon, 31 Jul 2023 10:10:50 + with message-id and subject line Bug#1040633: fixed in pilkit 2.0-5 has caused the Debian Bug report #1040633, regarding pilkit autopkg tests fail with pillow 10.0.0 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.) -- 1040633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pilkit Version: 2.0-4 Severity: serious Tags: sid trixie see https://ci.debian.net/data/autopkgtest/testing/amd64/p/pilkit/35498777/log.gz 41s == 41s ERROR: Test that the upscale argument works as expected. 41s -- 41s Traceback (most recent call last): 41s File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest 41s self.test(*self.arg) 41s File "/tmp/autopkgtest-lxc.6edwevyp/downtmp/autopkgtest_tmp/tests/test_processors.py", line 97, in test_upscale 41s img2 = P(500, 500, upscale=True).process(img) 41s^^ 41s File "/usr/lib/python3/dist-packages/pilkit/processors/resize.py", line 24, in process 41s img = img.resize((self.width, self.height), Image.ANTIALIAS) 41s ^^^ 41s AttributeError: module 'PIL.Image' has no attribute 'ANTIALIAS' 41s 41s -- 41s Ran 26 tests in 0.048s 41s 41s FAILED (errors=6) --- End Message --- --- Begin Message --- Source: pilkit Source-Version: 2.0-5 Done: Graham Inggs We believe that the bug you reported is fixed in the latest version of pilkit, 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. Graham Inggs (supplier of updated pilkit 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: Mon, 31 Jul 2023 09:40:14 + Source: pilkit Built-For-Profiles: noudeb Architecture: source Version: 2.0-5 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Graham Inggs Closes: 1040633 Changes: pilkit (2.0-5) unstable; urgency=medium . * Team upload . [ Dan Bungert ] * Fix autopkgtest failure due to use of deprecated Image.ANTIALIAS (Closes: #1040633) . [ Graham Inggs ] * Update year in debian/copyright * Bump Standards-Version to 4.6.2, no changes Checksums-Sha1: b5962d33f7e11495b87533156f29694b9e842d5a 2063 pilkit_2.0-5.dsc 11c272d71d65b361ea000db4111edd32486fc356 124784 pilkit_2.0-5.debian.tar.xz Checksums-Sha256: a1d4e18c092b6e00e0882678a656eb397303fda59eb24d85785d3dc08ef5d84b 2063 pilkit_2.0-5.dsc 218b000197900834f34f5ffebab6c18f33233eb41042fb57e992c755bb880586 124784 pilkit_2.0-5.debian.tar.xz Files: 7e2d8a6accfa67438e518ce9e1e35de7 2063 python optional pilkit_2.0-5.dsc 3cef0f60f3a06374b8d7dca52755bb86 124784 python optional pilkit_2.0-5.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAmTHhFUACgkQr8/sjmac 4cLgNw//UAaAEcC9gNHdss07aHnXR4qq1ga6FFVprIHcZpFUzOEL3d9RvIdSI+eB zK90Ah268j1OqoW3KT/e4liyeyLJSbMPj8DvxA8kx4+QiZpbcfriRbdv0c78V/jm uMy/eAHkE1K3QbEGkYu1+11DyegQ5U3gyQZCWIUU6eGjwAhXorLceu7SBaorYME7 gla1HEnQ4v20IVyzk8UgS0zQw5cH0JiTCQrxBfRBDL4EZcaeODRIprz7WrrTTNwI EBEHvxH3MWoSsksMJz7UUeWzXCZfsubopJSY6jDiB4xR2YSqA6c+0khjx7fRWT9e oElUQCNwK7FtOXf9DrIEkgJci9g2cal0vvjMGKtFGoP4XG4WonUicoNSENLJgb8U 92TYpIj7/V/YGV4eGlx9HBeIICPVDWCGKn0eoAg/H4D6EiDcz4yNomIc44sGbPkG P8rRbyWCDW4eBh+BCGcqnALtmrIzh26omauacgvFtbnh0BmOUHZl1AAeEAi9L7EC /uiRdHh0rxZTmOPxVhvKiV/tdoMprD8labv/7pZRryemrY+tgbbeAuV2HR60I/vT CqZdA3hChtTj7+J4Gb/RKJIptIHNj3cioyxF3xDit5LAgFWeE1hEEv4s46+Nq0yC e7OI65qgeyKZweBQ4jQi083jbNdyNqq+tz8k5QKEDUErUyWllKg= =vX2r -END PGP SIGNATURE End Message ---
Bug#1042747: dahdi-dkms: dkms.conf still lists removed pciradio.ko
Package: dahdi-dkms Version: 1:3.1.0+git20230717~dfsg-1 Severity: serious Buiding the modules fails because pciradio.ko is no longer built, but still required by dkms.conf: I: Trying to build dahdi/3.1.0+git20230717 for 6.3.0-2-amd64 Sign command: /usr/lib/linux-kbuild-6.3/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Creating symlink /var/lib/dkms/dahdi/3.1.0+git20230717/source -> /usr/src/dahdi-3.1.0+git20230717 Building module: Cleaning build area... (make modules KVERS=6.3.0-2-amd64 MODULES_EXTRA='dahdi_dummy dahdi_echocan_oslec'; make KVERS=6.3.0-2-amd64) Error! Build of pciradio.ko failed for: 6.3.0-2-amd64 (x86_64) Make sure the name of the generated module is correct and at the root of the build directory, or consult make.log in the build directory /var/lib/dkms/dahdi/3.1.0+git20230717/build for more information. E: dahdi/3.1.0+git20230717 failed to build for 6.3.0-2-amd64 make.log has no mention of pciradio at all and does not report any failures, thus it is not attached. While updating d/dkms.conf.in, you can probably drop CONFIG_PCI from BUILD_EXCLUSIVE_CONFIG (and update the comment) and switch from BUILD_EXCLUSIVE_KERNEL=...(regex)... to the more readable BUILD_EXCLUSIVE_KERNEL_MIN="5.6" (supported since dkms in trixie). Andreas
Processed: merge pilkit bugs
Processing commands for cont...@bugs.debian.org: > forcemerge 1040633 1042223 Bug #1040633 [src:pilkit] pilkit autopkg tests fail with pillow 10.0.0 Bug #1040633 [src:pilkit] pilkit autopkg tests fail with pillow 10.0.0 Added tag(s) ftbfs. Bug #1042223 [src:pilkit] pilkit: FTBFS: AttributeError: module 'PIL.Image' has no attribute 'ANTIALIAS' Merged 1040633 1042223 > thanks Stopping processing here. Please contact me if you need assistance. -- 1040633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040633 1042223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042223 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026864: dmrgpp: flaky autopkgtest on amd64: times out
and a comment about this issue https://github.com/g1257/dmrgpp/issues/38#issuecomment-1655740289
Bug#1000020: marked as done (android-platform-external-libselinux: depends on obsolete pcre3 library)
Your message dated Mon, 31 Jul 2023 09:07:51 + with message-id and subject line Bug#120: fixed in android-platform-external-libselinux 10.0.0+r36-2 has caused the Debian Bug report #120, regarding android-platform-external-libselinux: 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.) -- 120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=120 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: android-platform-external-libselinux 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: android-platform-external-libselinux Source-Version: 10.0.0+r36-2 Done: Roger Shimizu We believe that the bug you reported is fixed in the latest version of android-platform-external-libselinux, 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. Roger Shimizu (supplier of updated android-platform-external-libselinux 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: Mon, 31 Jul 2023 01:27:56 -0700 Source: android-platform-external-libselinux Architecture: source Version: 10.0.0+r36-2 Distribution: unstable Urgency: medium Maintainer: Android Tools Maintainers Changed-By: Roger Shimizu Closes: 120 Changes: android-platform-external-libselinux (10.0.0+r36-2) unstable; urgency=medium . * Team upload . [ 殷啟聰 | Kai-Chung Yan ] * Remove myself from Uploaders . [ Adrian Bunk ] * Switch to PCRE2 (Closes: #120). Checksums-Sha1: b1bca6ef79610965b87370f14defc5159341b66f 2677 android-platform-external-libselinux_10.0.0+r36-2.dsc 21a78792a2f51fdd17aad584765427379500d322 6052 android-platform-external-libselinux_10.0.0+r36-2.debian.tar.xz 21f44ff93497ffbd8a9201e533a52d91fadbe27e 6333 android-platform-external-libselinux_10.0.0+r36-2_source.buildinfo Checksums-Sha256: 402f53dbbe2c7b56e031d754388ab93f7e541cceba83fd8e27725725c82166e9 2677 android-platform-external-libselinux_10.0.0+r36-2.dsc 258bdc25ba36c76421183197ac028315d3e03923acebda132f4e6a9a11b2f663 6052 android-platform-external-libselinux_10.0.0+r36-2.debian.tar.xz bd7c2c5d713f7392fc29127cc064a9f146ec4d2439f91b05adc4ddc79fce371f 6333 android-platform-external-libselinux_10.0.0+r36-2_source.buildinfo Files: 93b56bc7e0b488e59a559ea690cb5bde 2677 libs optional android-platform-external-libselinux_10.0.0+r36-2.dsc f971e74abc4eea605591c7a7a5f154e1 6052 libs optional android-platform-external-libselinux_10.0.0+r36-2.debian.tar.xz 649630753b2529a63a61c7fe1ade5332 6333 libs optional android-platform-external-libselinux_10.0.0+r36-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAmTHcXMQHHJvc2hAZGVi aWFuLm9yZwAKCRCkeGsNpwM0qLsFD/9zz8I/evjEayoDefoKPTmcFLP+6KRwkxeY BUXNZaK7kWPk8TbkPDD2est68PFHfRmeUxielvwgbqciYeNZHJ/t/5Q5HIqwQ0XH TdXMeHUYbeQV47zZh28fbyxA7ISjnq+k8AwMRLxslVh2sBeiUCri9X/g6yM0dUGK uA3tAY0MM4GqxDZEARXALvMu3c6xSgwCkAY1aNO1rEg8GEBR0xhHCTH3OR417XPA IylhDco5YCHSdDSr4nfMZF2d1MWFpdDmb3XwUo1WefYNtc5jeh7EOHIo3Q6zy9Y1 zew6ZGg+/zd0NAv7FkKrFvPUm37o0e0voeZCmDbeEMOiot8ahIJgj65vAPjECf1i
Bug#1042738: ruby-rails-assets-punycode: Do not ship libjs-punycode
Source: ruby-rails-assets-punycode Severity: serious Justification: source is missing Dear Maintainer, You package node-punycode without source... I plan to fix this Bastien signature.asc Description: This is a digitally signed message part.
Bug#1042736: golang-github-dgrijalva-jwt-go-dev: Broken transitional package
Package: golang-github-dgrijalva-jwt-go-dev Version: 3.2.3-2 Severity: serious Tags: ftbfs X-Debbugs-Cc: Thomas Goirand Control: affects -1 src:go-cve-dictionary src:go-exploitdb src:gost src:goval-dictionary src:golang-github-labstack-echo.v2 src:golang-github-labstack-echo.v3 https://buildd.debian.org/status/fetch.php?pkg=go-cve-dictionary=riscv64=0.3.1-4=1690766362=0 https://buildd.debian.org/status/fetch.php?pkg=go-exploitdb=riscv64=0.0~git20181130.7c961e7-2=1690766519=0 https://buildd.debian.org/status/fetch.php?pkg=gost=riscv64=0.1.0%2Bgit20181204.5afeda5e-1.1=1690767472=0 https://buildd.debian.org/status/fetch.php?pkg=goval-dictionary=riscv64=0.2.0-4=1690767475=0 ... dh_auto_build -a -O--buildsystem=golang cd obj-riscv64-linux-gnu && go install -trimpath -v -p 4 github.com/kotakanbe/goval-dictionary github.com/kotakanbe/goval-dictionary/commands github.com/kotakanbe/goval-dictionary/config github.com/kotakanbe/goval-dictionary/db github.com/kotakanbe/goval-dictionary/db/rdb github.com/kotakanbe/goval-dictionary/fetcher github.com/kotakanbe/goval-dictionary/models github.com/kotakanbe/goval-dictionary/server github.com/kotakanbe/goval-dictionary/util src/github.com/labstack/echo.v2/middleware/jwt.go:10:2: cannot find package "github.com/dgrijalva/jwt-go" in any of: /usr/lib/go-1.20/src/github.com/dgrijalva/jwt-go (from $GOROOT) /<>/obj-riscv64-linux-gnu/src/github.com/dgrijalva/jwt-go (from $GOPATH) dh_auto_build: error: cd obj-riscv64-linux-gnu && go install -trimpath -v -p 4 github.com/kotakanbe/goval-dictionary github.com/kotakanbe/goval-dictionary/commands github.com/kotakanbe/goval-dictionary/config github.com/kotakanbe/goval-dictionary/db github.com/kotakanbe/goval-dictionary/db/rdb github.com/kotakanbe/goval-dictionary/fetcher github.com/kotakanbe/goval-dictionary/models github.com/kotakanbe/goval-dictionary/server github.com/kotakanbe/goval-dictionary/util returned exit code 1 make: *** [debian/rules:4: binary-arch] Error 25
Processed: golang-github-dgrijalva-jwt-go-dev: Broken transitional package
Processing control commands: > affects -1 src:go-cve-dictionary src:go-exploitdb src:gost > src:goval-dictionary src:golang-github-labstack-echo.v2 > src:golang-github-labstack-echo.v3 Bug #1042736 [golang-github-dgrijalva-jwt-go-dev] golang-github-dgrijalva-jwt-go-dev: Broken transitional package Added indication that 1042736 affects src:go-cve-dictionary, src:go-exploitdb, src:gost, src:goval-dictionary, src:golang-github-labstack-echo.v2, and src:golang-github-labstack-echo.v3 -- 1042736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042736 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042737: libzstd build fails when using "dpkg-buildpackage -us -uc -ui -F"
Source: libzstd Version: 1.5.5+dfsg2-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: u20230731report...@projektzentrisch.de Dear Maintainer, earlier today, an attempted rebuild of "libzstd" in a debootstrap/schroot environment failed with the following error: [...] d=6 steps=40 split=100 Save dictionary of size 112640 into file dictionary make[3]: Leaving directory '/build/packages/libzstd-1.5.5+dfsg2/tests' make[2]: *** [Makefile:85: test] Error 2 make[2]: Leaving directory '/build/packages/libzstd-1.5.5+dfsg2' rm -fr -- /tmp/user/0/dh-xdg-rundir-0tHhrq1P dh_auto_test: error: make -j4 test returned exit code 2 make[1]: *** [debian/rules:71: build] Error 255 make[1]: Leaving directory '/build/packages/libzstd-1.5.5+dfsg2' make: *** [debian/rules:34: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Steps to reproduce this: # debootstrap --arch=amd64 sid debian-sid-amd64 [...] # schroot -c debian-sid-amd64 -u root -d /build/packages -s /bin/bash (debian-sid-amd64)root@vserver19:/build/packages# cat << EOF > /etc/apt/sources.list > deb https://deb.debian.org/debian sid main contrib non-free non-free-firmware deb-src https://deb.debian.org/debian sid main contrib non-free non-free-firmware EOF (debian-sid-amd64)root@vserver19:/build/packages# apt update; apt upgrade -y (debian-sid-amd64)root@vserver19:/build/packages# export EDITOR=nano; apt install -y build-essential devscripts lintian diffutils patch patchutils quilt ca-certificates git equivs less nano (debian-sid-amd64)root@vserver19:/build/packages# dget http://deb.debian.org/debian/pool/main/libz/libzstd/libzstd_1.5.5+dfsg2-1.dsc (debian-sid-amd64)root@vserver19:/build/packages# cd libzstd-1.5.5+dfsg2; mk-build-deps; apt install -y /tmp/user/0/libzstd-build-deps_1.5.5+dfsg2-1_all.deb (debian-sid-amd64)root@vserver19:/build/packages/libzstd-1.5.5+dfsg2# dpkg-buildpackage -us -uc -ui -F The above problem is currently reproducible for a non-root user, an arm64/aarch64 host (using kernel 5.15 w/ Ubuntu "jammy"), and downstream repositories (namely Ubuntu "mantic") as well--all combinations have been tried to no avail. It's my understanding that the above call to "dpkg-buildpackage" should never fail in a current debootstrap/schroot environment on x86_64 hosts if all dependencies are met (in the absence of DEB_xxx environment variables). -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-74-generic (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE, TAINT_SOFTLOCKUP Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect # source /etc/os-release; echo $VERSION; uname -a 20.04.6 LTS (Focal Fossa) Linux vserver19 5.15.0-74-generic #81~20.04.2-Ubuntu SMP Fri May 26 19:56:20 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux # arch x86_64
Bug#1042734: binutils-mingw-w64 FTBFS: Patch debian/patches/specify-timestamp.patch does not apply
Source: binutils-mingw-w64 Version: 11 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/binutils-mingw-w64.html https://buildd.debian.org/status/fetch.php?pkg=binutils-mingw-w64=riscv64=11=1690696627=0 ... pplying patch debian/patches/specify-timestamp.patch patching file upstream/bfd/peXXigen.c Hunk #2 FAILED at 840. 1 out of 2 hunks FAILED -- rejects in file upstream/bfd/peXXigen.c patching file upstream/ld/pe-dll.c Hunk #2 FAILED at 1232. 1 out of 2 hunks FAILED -- rejects in file upstream/ld/pe-dll.c patching file upstream/ld/emultempl/pe.em patching file upstream/ld/emultempl/pep.em Patch debian/patches/specify-timestamp.patch does not apply (enforce with -f) make[1]: *** [debian/rules:71: unpack] Error 1
Bug#1042532: mediawiki: Vendoring a few javascript library without source
Hi, On 7/29/23 16:44, Bastien Roucariès wrote: Dear Maintainer, resources/lib/ (https://sources.debian.org/src/mediawiki/1:1.39.4-2/resources/lib/) include a few library already packaged for debian. Moreover some source are missing (I have only checked pako). These are in the preferred form for modification so I don't think there's any issue here, but please correct me if I'm wrong. MediaWiki often patches these libraries (e.g. jquery.ui) in this format hence IMO meeting the "preferred form of the work for making modifications to it" requirement of the GPL. You could use the packaged library under debian Older versions of the package did that, but the version mismatches were not worth it. Plus MediaWiki has a ton of user-written code that's stored and loaded on-wiki, so deviations from the official version are incredibly hard to test and just cause breakage everywhere. -- Kunal
Processed: tagging 1037756
Processing commands for cont...@bugs.debian.org: > tags 1037756 + upstream Bug #1037756 [src:litecoin] litecoin: ftbfs with GCC-13 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1037756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037756 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1037756 is forwarded to https://github.com/litecoin-project/litecoin/issues/912
Processing commands for cont...@bugs.debian.org: > forwarded 1037756 https://github.com/litecoin-project/litecoin/issues/912 Bug #1037756 [src:litecoin] litecoin: ftbfs with GCC-13 Set Bug forwarded-to-address to 'https://github.com/litecoin-project/litecoin/issues/912'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1037756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037756 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 1042051
Processing commands for cont...@bugs.debian.org: > close 1042051 2.0.19+ds1-1 Bug #1042051 [src:sqlalchemy] sqlalchemy: FTBFS: Could not import extension sphinxcontrib.jquery (exception: No module named 'sphinxcontrib') Marked as fixed in versions sqlalchemy/2.0.19+ds1-1. Bug #1042051 [src:sqlalchemy] sqlalchemy: FTBFS: Could not import extension sphinxcontrib.jquery (exception: No module named 'sphinxcontrib') Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1042051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042051 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042009: onetbb: FTBFS on armel: error: ‘void __atomic_store_1(volatile void*, unsigned char, int)’ writing 1 byte into a region of size 0 overflows the destination [-Werror=stringop-overflow=]
I suspect this trigger a compiler bug on armel, as the code seem just
fine with me. I have tested on armel and managed to get the code
building with the following patch.
diff --git a/src/tbb/concurrent_monitor.h b/src/tbb/concurrent_monitor.h
index 3d20ef5b..b010b2e5 100644
--- a/src/tbb/concurrent_monitor.h
+++ b/src/tbb/concurrent_monitor.h
@@ -23,6 +23,7 @@
#include "concurrent_monitor_mutex.h"
#include "semaphore.h"
+#include
#include
namespace tbb {
@@ -289,8 +290,10 @@ public:
my_epoch.store(my_epoch.load(std::memory_order_relaxed) + 1,
std::memory_order_relaxed);
n = my_waitset.front();
if (n != end) {
+wait_node* wn = to_wait_node(n);
+assert(to_wait_node(n));
+wn->my_is_in_list.store(false, std::memory_order_relaxed);
my_waitset.remove(*n);
-to_wait_node(n)->my_is_in_list.store(false,
std::memory_order_relaxed);
}
}
I have no idea why this help. I am not yet sure if it is the reordering
or the use of assert() improving the situation, as the round trip time
is 2-3 hours on abel.debian.org, but will continue trying to reduce the
change set a bit more. I do not know the code enough to know, but
need to make sure reordering the .remove() and the .store() do not cause
some race condition. I hope the use of my_mutex ensure it does not.
--
Happy hacking
Petter Reinholdtsen
Bug#244289: marked as done (xball: Package includes non-free source code.)
Your message dated Mon, 31 Jul 2023 06:10:38 + with message-id and subject line Bug#244289: fixed in xball 3.0.1+dfsg-1 has caused the Debian Bug report #244289, regarding xball: Package includes non-free source code. 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.) -- 244289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=244289 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xball Severity: serious Hi The package xball contains the source file act_area.c and the license for it is the following: Written by Dan Heller. Copyright 1991, O'Reilly && Associates. This program is freely distributable without licensing fees and is provided without guarantee or warrantee expressed or implied. This program is -not- in the public domain. In my opinion (and some others after a short talk on IRC) is that this is non-free as it doesnt allow modification. "look but dont touch". Hence this is non-free and the package should be moved out of main before we release sarge. Or this issue gets solved. Note: The Debian Maintainer of xball is one of my NMs, so I know he is working on this. This bug is merely that this issue isnt lost. Note2: Upstream was already contacted and sent a statement about his opinions. Which I dont share. But I dont want to make private mails public, so it isnt attached, instead I set a CC to him so he can attach his comment to this bug. debian-legal is in CC to get another opinion on this matter. -- bye Joerg [Es geht um MySQL] (14:35) grummel. als ob ein subselect so kompliziert waere. (14:35) als ob mysql eine db wäre... (14:35) relationales textfile auf drogen? :0 pgp8VeOLCl5EQ.pgp Description: PGP signature --- End Message --- --- Begin Message --- Source: xball Source-Version: 3.0.1+dfsg-1 Done: David da Silva Polverari We believe that the bug you reported is fixed in the latest version of xball, 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 244...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David da Silva Polverari (supplier of updated xball 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: Mon, 31 Jul 2023 02:12:15 -0300 Source: xball Architecture: source Version: 3.0.1+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: David da Silva Polverari Closes: 244289 Changes: xball (3.0.1+dfsg-1) unstable; urgency=medium . * QA upload. * Removed non DFSG-compliant files act_area.c and act_area.h from source. (Closes: #244289) * debian/README.source: created to explain about the removal of the non DFSG-compliant files from source. Checksums-Sha1: 914ed5e26ef4f6e1dffced63941df6e16b14c21d 1774 xball_3.0.1+dfsg-1.dsc 0f4dc19a50021d6fc9cdff367b1e7e85c1f867df 174777 xball_3.0.1+dfsg.orig.tar.gz 8146c8ae2f0f49572dd3d08da770bdb2994597d3 8352 xball_3.0.1+dfsg-1.debian.tar.xz 68fe2dc21f17b8f9a2a8ffc398e836e08d7d7ccc 7320 xball_3.0.1+dfsg-1_source.buildinfo Checksums-Sha256: 358bc0cbc3e3471a3cbbf4af4b74cfb44f5de99fd47e759fe8d7c34de5b737a3 1774 xball_3.0.1+dfsg-1.dsc b0bbc21ac28a494d5a51008de5c5f099c3704ed0a26c1171075b418204affdd9 174777 xball_3.0.1+dfsg.orig.tar.gz 3747d3dcb7e75d756c49405b22aec56c418f06922b5e2bb6bb4398f8eeec7d92 8352 xball_3.0.1+dfsg-1.debian.tar.xz 1b1be6f950bac67a2c50a8ab444610c7d232e98211751eaf4febafa6b1a35311 7320 xball_3.0.1+dfsg-1_source.buildinfo Files: 1f7e9ead037c452d31cb650ca9d0c671 1774 games optional xball_3.0.1+dfsg-1.dsc 1387772fc17041a04fe087acca187eed 174777 games optional xball_3.0.1+dfsg.orig.tar.gz e1139225325e3f78fa18260c59d9e898 8352 games optional xball_3.0.1+dfsg-1.debian.tar.xz 02cb9d312b07430003dd70d943831b80 7320 games optional xball_3.0.1+dfsg-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEDTUunGhzKyZWj9leHIjoaIRpgN4FAmTHQ2sACgkQHIjoaIRp gN7DKA/+Ng8CutjWJZkdgczfN62w4JVcDnitzO4DnnUYLINFY2VLiJElK1lbskQM y6y39qHcxg3J4owCDEKvCM/1SuQxu+u+/7s3tO1lNjYEmVYLk2/2d3wrM10On0Ky wxxy/d/7fMIyH26Fr0DU0txWEW+OzxNrt0GEADgqXMe7DR3okIIwE23Cqx5OZ/C8 lPwFJOzZa2s9QtBFtM181dQd0TR11tDBl2T1fyfN2m4RQa3XfjLxiddf2tymqBu3
Processed: src:mrbuild: fails to migrate to testing for too long: uploader built arch:all binary
Processing control commands: > close -1 1.6-1 Bug #1042724 [src:mrbuild] src:mrbuild: fails to migrate to testing for too long: uploader built arch:all binary Marked as fixed in versions mrbuild/1.6-1. Bug #1042724 [src:mrbuild] src:mrbuild: fails to migrate to testing for too long: uploader built arch:all binary Marked Bug as done -- 1042724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042724 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042724: src:mrbuild: fails to migrate to testing for too long: uploader built arch:all binary
Source: mrbuild Version: 1.2-1 Severity: serious Control: close -1 1.6-1 Tags: sid trixie pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:mrbuild has been trying to migrate for 31 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=mrbuild OpenPGP_signature Description: OpenPGP digital signature
Processed: src:r-cran-tmb: fails to migrate to testing for too long: autopkgtest regression
Processing control commands: > close -1 1.9.4-1 Bug #1042723 [src:r-cran-tmb] src:r-cran-tmb: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions r-cran-tmb/1.9.4-1. Bug #1042723 [src:r-cran-tmb] src:r-cran-tmb: fails to migrate to testing for too long: autopkgtest regression Marked Bug as done -- 1042723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042723 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042723: src:r-cran-tmb: fails to migrate to testing for too long: autopkgtest regression
Source: r-cran-tmb Version: 1.9.2-1 Severity: serious Control: close -1 1.9.4-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:r-cran-tmb has been trying to migrate for 32 days [2]. Hence, I am filing this bug. The autopkgtest of the version in unstable fails everywhere. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=r-cran-tmb OpenPGP_signature Description: OpenPGP digital signature
