yasm_1.3.0-6_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 28 Apr 2025 23:48:47 +0200 Source: yasm Architecture: source Version: 1.3.0-6 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Petter Reinholdtsen Closes: 1098187 1103250 Changes: yasm (1.3.0-6) unstable; urgency=medium . * QA upload. . * Switched d/watch to current github repository. * Switched homepage in d/control to https://github.com/yasm/yasm/ while https://www.tortall.net/projects/yasm/ is dead. * Added 000-gcc-15.patch to fix GCC 15 build problem (Closes: #1098187). * Disabled non-working parallel build (Closes: #1103250). * Updated Standards-Version from 4.7.0 to 4.7.2. Checksums-Sha1: 108843ec138fa94570c861409756ace396097382 1815 yasm_1.3.0-6.dsc 872dc6ce625fd9e979ef785f72c06542adf7cbed 9456 yasm_1.3.0-6.debian.tar.xz 8985d51c0a551d7f1b71660b5664811a80293e9f 7033 yasm_1.3.0-6_source.buildinfo Checksums-Sha256: ca4b697c3469c2e1852a133aa73daed88d84920f5acdb25eb0dd3ec87e7d1ab8 1815 yasm_1.3.0-6.dsc 9b83a95e500df9c8ba8f6012885b955d049e49f994fb6c9315ce05ba966486d7 9456 yasm_1.3.0-6.debian.tar.xz 264ddfdd42e1474396516693a8d03c616c0af93fc39a9cff5b6c8a5dffa76647 7033 yasm_1.3.0-6_source.buildinfo Files: 817b23a2d6a069d4dbee11de73083ba0 1815 devel optional yasm_1.3.0-6.dsc 8c69120099366e410759fbe3d9936609 9456 devel optional yasm_1.3.0-6.debian.tar.xz 6eaaecc43b2a55e99e456f734ce75a35 7033 devel optional yasm_1.3.0-6_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmgP+LIACgkQgSgKoIe6 +w4D6A//XWoWAY/Sf834uYF6APncJMPGDzDnx2uUqNLjGV80OaO/E+sNSvzKpvrk djnLwNh9uOiey5RnJHTZ+1p8WnjAo2kEEa/Irk2mnyRzn9U0jaDqDyvVFhivOpQH O3VBhoW1Y74hEqVPqo6VWgcsLrOnZwJqd+zli3JL0lD/OyRc20J4JvDVlpZrQV0V 6ZcIjzOsNByj4PajGl96jtNembSOSQxKd/9U4cIbGIptY5oUWvUB09fRQya35bNn X4UPObQpl0UYi+taxmCn5qh5zwpQqTL5k1v1L+/nzmXfyByHRPpN6Z/mVdljUS9w c2AGzUpV2O1lw/gG7IO7C+mIGM0fPdQjpd8T4yvm7nnqV12ugeB7TLg0XL5V5D/q TPgRhh8l3MaJbmqLM9AoZjrACv84H6n8UD9/K0IOwrwH9kL+yPND1XEsjEaR5+Wt wRbxv4YlSu70eS8ASCXP9rxsK7Dde09AJTAhgTCp+8KiWFjILC2QnupOD1SnsGxr LDWNd8BrGnDxl1sP5mGUmH5Pp1VyzA4jcipExuzV0viVXi4GMFYHmZPb5T29ePjH +HGevaD1qI7aG291bFWRShHS+ausxlWom43CDuU6X12EVbGwQXDeszcAzlJJSWZs QnvfgcmP2jfex21IJeIp9IH6Hbzs1GxptHDDoC+ORp4aI+ULb/Q= =hK2x -END PGP SIGNATURE- pgpUw9UO1acbL.pgp Description: PGP signature
Processing of yasm_1.3.0-6_source.changes
yasm_1.3.0-6_source.changes uploaded successfully to localhost along with the files: yasm_1.3.0-6.dsc yasm_1.3.0-6.debian.tar.xz yasm_1.3.0-6_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#1098187: marked as done (yasm: ftbfs with GCC-15)
Your message dated Mon, 28 Apr 2025 22:07:18 + with message-id and subject line Bug#1098187: fixed in yasm 1.3.0-6 has caused the Debian Bug report #1098187, regarding yasm: ftbfs with GCC-15 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.) -- 1098187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098187 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:yasm Version: 1.3.0-5 Severity: important Tags: sid forky User: debian-...@lists.debian.org Usertags: ftbfs-gcc-15 [This bug is NOT 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-15/g++-15, but succeeds to build with gcc-14/g++-14. The severity of this report will be raised before the forky release. The full build log can be found at: http://qa-logs.debian.net/2025/02/16/amd64exp/yasm_1.3.0-5_unstable_gccexp.log.gz The last lines of the build log are at the end of this report. To build with GCC 15, either set CC=gcc-15 CXX=g++-15 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ GCC 15 now defaults to the C23/C++23 standards, exposing many FTBFS. Other 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-15/porting_to.html [...] ./genmacro nasm-version.c nasm_version_mac version.mac ./genmacro win64-nasm.c win64_nasm_stdmac ./modules/objfmts/coff/win64-nasm.mac ./genmacro win64-gas.c win64_gas_stdmac ./modules/objfmts/coff/win64-gas.mac gcc -o genperf genperf.o gp-perfect.o gp-phash.o gp-xmalloc.o gp-xstrdup.o ./genperf x86insn_nasm.gperf x86insn_nasm.c ./genperf x86insn_gas.gperf x86insn_gas.c fail to map group of size 2 for tab size 512 gcc -o re2c re2c-main.o re2c-code.o re2c-dfa.o re2c-parser.o re2c-actions.o re2c-scanner.o re2c-mbo_getopt.o re2c-substr.o re2c-translate.o ./re2c -b -o gas-token.c ./modules/parsers/gas/gas-token.re ./re2c -b -o nasm-token.c ./modules/parsers/nasm/nasm-token.re make all-recursive make[2]: Entering directory '/build/reproducible-path/yasm-1.3.0' Makefile:4369: warning: ignoring prerequisites on suffix rule definition Making all in po make[3]: Entering directory '/build/reproducible-path/yasm-1.3.0/po' make[3]: Nothing to be done for 'all'. make[3]: Leaving directory '/build/reproducible-path/yasm-1.3.0/po' Making all in . make[3]: Entering directory '/build/reproducible-path/yasm-1.3.0' Makefile:4369: warning: ignoring prerequisites on suffix rule definition ./genperf ./modules/arch/x86/x86cpu.gperf x86cpu.c ./genperf ./modules/arch/x86/x86regtmod.gperf x86regtmod.c ./re2c -s -o lc3bid.c ./modules/arch/lc3b/lc3bid.re gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/yasm-1.3.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c -o gas-token.o gas-token.c gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/yasm-1.3.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c -o nasm-token.o nasm-token.c gcc -I. -c -o genmodule.o `test -f libyasm/genmodule.c || echo './'`libyasm/genmodule.c gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/yasm-1.3.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c -o frontends/yasm/yasm.o frontends/yasm/yasm.c gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/yasm-1.3.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c -o frontends/yasm/yasm-options.o frontends/yasm/yasm-options.c gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/yasm-1.3.0=. -fstack-
Bug#1103250: marked as done (yasm: FTBFS on amd64, arm64, armel, armhf, i386, ppc64el, ppc64, powerpc, riscv64)
Your message dated Mon, 28 Apr 2025 22:07:18 + with message-id and subject line Bug#1103250: fixed in yasm 1.3.0-6 has caused the Debian Bug report #1103250, regarding yasm: FTBFS on amd64, arm64, armel, armhf, i386, ppc64el, ppc64, powerpc, riscv64 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.) -- 1103250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103250 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: yasm Version: 1.3.0-5 Severity: serious Tags: ftbfs upstream Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: debian-am...@lists.debian.org, debian-...@lists.debian.org, debian-powe...@lists.debian.org, debian-ri...@lists.debian.org User: debian-powe...@lists.debian.org Usertags: powerpc ppc64 ppc64el User: debian-...@lists.debian.org Usertags: arm64 armel armhf User: debian...@lists.debian.org Usertags: i386 User: debian-am...@lists.debian.org Usertags: amd64 User: debian-ri...@lists.debian.org Usertags: riscv64 Hello! yasm fails to build from source on these architectures I tested on: amd64, arm64, armel, armhf, i386, ppc64el, ppc64, powerpc, riscv64. You should be able to reproduce it with the usual "sbuild -d unstable" (I use the unshare backend). All of them failed because of 1~3 failed tests: FAIL: modules/objfmts/elf/tests/amd64/elf_amd64_test.sh FAIL: modules/objfmts/elf/tests/gasx32/elf_gasx32_test.sh FAIL: modules/objfmts/elf/tests/gas64/elf_gas64_test.sh I don't know how to fix it. And here are the fragments of build logs: amd64: System information (uname -a): Linux 6.12.17-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.17-1 (2025-03-01) x86_64 Distribution information (/etc/os-release): PRETTY_NAME="Debian GNU/Linux trixie/sid" NAME="Debian GNU/Linux" VERSION_CODENAME=trixie ID=debian HOME_URL="https://www.debian.org/"; SUPPORT_URL="https://www.debian.org/support"; BUG_REPORT_URL="https://bugs.debian.org/"; .. contents:: :depth: 2 FAIL: modules/objfmts/elf/tests/amd64/elf_amd64_test.sh === Test elf_amd64_test: O.OO +1-3/4 25% ** O: elf-rip did not match object file! ** O: gotpcrel did not match object file! ** O: multiplefixup did not match object file! FAIL modules/objfmts/elf/tests/amd64/elf_amd64_test.sh (exit status: 3) FAIL: modules/objfmts/elf/tests/gasx32/elf_gasx32_test.sh = Test elf_gasx32_test: O... +3-1/4 75% ** O: crosssect did not match object file! FAIL modules/objfmts/elf/tests/gasx32/elf_gasx32_test.sh (exit status: 1) Testsuite summary for yasm 1.3.0 # TOTAL: 44 # PASS: 42 # SKIP: 0 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 arm64: System information (uname -a): Linux 6.12.21-arm64 #1 SMP Debian 6.12.21-1 (2025-03-30) aarch64 Distribution information (/etc/os-release): PRETTY_NAME="Debian GNU/Linux trixie/sid" NAME="Debian GNU/Linux" VERSION_CODENAME=trixie ID=debian HOME_URL="https://www.debian.org/"; SUPPORT_URL="https://www.debian.org/support"; BUG_REPORT_URL="https://bugs.debian.org/"; .. contents:: :depth: 2 FAIL: modules/objfmts/elf/tests/amd64/elf_amd64_test.sh === Test elf_amd64_test: O... +3-1/4 75% ** O: elf-rip did not match object file! FAIL modules/objfmts/elf/tests/amd64/elf_amd64_test.sh (exit status: 1) FAIL: modules/objfmts/elf/tests/x32/elf_x32_test.sh === Test elf_x32_test: ..OO +2-2/4 50% ** O: gotpcrel did not match object file! ** O: multiplefixup did not match object file! FAIL modules/objfmts/elf/tests/x32/elf_x32_test.sh (exit status: 2) FAIL: modules/objfmts/elf/tests/gas64/elf_gas64_test.sh === Test elf_gas64_test: O... +3-1/4 75% ** O: crosssect did not match object file! FAIL modules/objfmts/elf/tests/gas64/elf_gas64_test.sh (exit status: 1) Testsuite summary for yasm 1.3.0 # TOTAL: 44 # PASS: 41 # SKIP: 0 # XFAIL: 0 # FAIL: 3 # XPASS: 0 # ERROR: 0 armel: System information (uname -a): Linux 6.12.21-arm64 #1 SMP Debian 6.
Processed: your mail
Processing commands for cont...@bugs.debian.org: > close 850805 Bug #850805 [unpaper] not enough frames to estimate rate Marked Bug as done > close 865357 Bug #865357 [kodi] kodi: Debians language/keyboard settings ignored by Kodi Marked Bug as done > close 1019446 Bug #1019446 [kde-config-cron] kde-config-cron: Binary missing Marked Bug as done > close 1066902 Bug #1066902 [wiki.debian.org] wiki.debian.org: Loggin page typographical incorrect Marked Bug as done > close 847838 Bug #847838 [xfce4] xfce4: ~/.xfce4-session.verbose-log.last without timestamps Marked Bug as done > End of message, stopping processing here. Please contact me if you need assistance. -- 1019446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019446 1066902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066902 847838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847838 850805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850805 865357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865357 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
helm-projectile is marked for autoremoval from testing
helm-projectile 0.14.0-8 is marked for autoremoval from testing on 2025-05-08 It (build-)depends on packages with these RC bugs: 1099238: helm: FTBFS: helm-command.el:23:11: Error: Wrong type argument https://bugs.debian.org/1099238 For more information on the autoremoval process, including hints to prevent autoremoval can be found on the wiki: https://wiki.debian.org/Autoremoval This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
helm-org is marked for autoremoval from testing
helm-org 1.0-4 is marked for autoremoval from testing on 2025-05-08 It (build-)depends on packages with these RC bugs: 1099238: helm: FTBFS: helm-command.el:23:11: Error: Wrong type argument https://bugs.debian.org/1099238 For more information on the autoremoval process, including hints to prevent autoremoval can be found on the wiki: https://wiki.debian.org/Autoremoval This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
key-chord-el is marked for autoremoval from testing
key-chord-el 0.6-8 is marked for autoremoval from testing on 2025-05-08 It is affected by these RC bugs: 1098905: elpa-key-chord: incompatibility with Gnu Emacs 30 https://bugs.debian.org/1098905 For more information on the autoremoval process, including hints to prevent autoremoval can be found on the wiki: https://wiki.debian.org/Autoremoval This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
