Your message dated Fri, 20 May 2022 07:04:07 +0000 with message-id <e1nrwgb-00024e...@fasolo.debian.org> and subject line Bug#997338: fixed in yasm 1.3.0-2.2 has caused the Debian Bug report #997338, regarding yasm: FTBFS: configure: error: Standard (ANSI/ISO C89) header files are required. 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.) -- 997338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: yasm Version: 1.3.0-2.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for strings.h... (cached) yes > checking for libgen.h... yes > checking for unistd.h... (cached) yes > checking for direct.h... no > checking for sys/stat.h... (cached) yes > configure: error: Standard (ANSI/ISO C89) header files are required. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2021/10/23/yasm_1.3.0-2.1_unstable.log 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 marking 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: yasm Source-Version: 1.3.0-2.2 Done: Sebastian Ramacher <sramac...@debian.org> We believe that the bug you reported is fixed in the latest version of yasm, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher <sramac...@debian.org> (supplier of updated yasm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Wed, 18 May 2022 08:36:44 +0200 Source: yasm Architecture: source Version: 1.3.0-2.2 Distribution: unstable Urgency: medium Maintainer: Sam Hocevar <s...@debian.org> Changed-By: Sebastian Ramacher <sramac...@debian.org> Closes: 943303 997338 Changes: yasm (1.3.0-2.2) unstable; urgency=medium . * Non-maintainer upload. * debian/patches/autoconf.patch: Apply upstream patch to fix build failure (Closes: #997338) * debian/control: Build-Depend on python3. (Closes: #943303) Checksums-Sha1: 367fe76c1e29a52f05b56c4dd7509bb39df3372a 1870 yasm_1.3.0-2.2.dsc 507aaf7bc5fa16bc0086c6b5a1cc010441d9d49b 8796 yasm_1.3.0-2.2.debian.tar.xz Checksums-Sha256: 7e0e5361e9a2b5ef672bbfd8010a1003fa14cec2ede08ed39ddc29632b70e80f 1870 yasm_1.3.0-2.2.dsc 87ff4aa968fe99f156670877d5194100d0e00e96c7369e11ebf02d1576528aee 8796 yasm_1.3.0-2.2.debian.tar.xz Files: e100ab6da0e4e7cdbf5b6623d6419f9b 1870 devel optional yasm_1.3.0-2.2.dsc 142eaddbacdaff1e50fec990e27e72ca 8796 devel optional yasm_1.3.0-2.2.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmKElHIACgkQafL8UW6n GZPxGhAAh9/iTmX/hrmwyR2dkjhY1UHENNgeBOtWTX70moefS8D8b5LH+pozp6Nr U2Aaxi4OsjYlx4L8zpPjbtjpPhiQzX6ffGrBLNkev22b6agkktJ2POUaLdeXNIfN gIzw0V2O5mHVK00EAmKBbac/XOG8l0tLon5rM0H9iDqdJEfgcmJNTO1Y+mm/dlrP pP3o7PRxwXqNizQo02HUNLHDMkO1tTEZ+yCU4qSBN57odcyQkuBNM1QYc/3PXw9h +Cis11EgzRVHgEWthG2Ki7shYYxnB2//TMZnMKUm57M3wpHpyKrbMyiprkcMfj7O UiF+A8u/9Fjyn0pIGYKIb+ANabpLFzMC01nvQPVwtvaALYkF2uuajTGPVAzIvpFz ZdIS4EVaXPmo7smTrCn0YRk581ysTFgAKcPx8XUVlmk1ffsg9LeajJ0WXdZwYJ4X GaxkgOevcPigWF1NI8iTD/YZEs8TVota+M6nujDD/jOYA/j2dK9RJKgCWXDb+Oj5 0aqjs0g3Zp/h8wYTNg3yxKYR5o2ZZwb5JlA9Sm8Za7qqrEX0MnKNGdXNlkWTht3M oyjtc79sg3r0giLa50ybkMPEr+6cXOiOem+Z0nOWS5CX/QQ21KIZUTcjXbkbBX/I 8t65dOi8qjc/5qLkN/Tqo1PtLQEvswxhvyh3SsPLr21IWAWwXTE= =R2xZ -----END PGP SIGNATURE-----
--- End Message ---
