Your message dated Sat, 14 May 2022 07:48:34 +0000 with message-id <e1npmvu-0000cj...@fasolo.debian.org> and subject line Bug#1009467: fixed in r-bioc-biostrings 2.64.0-1 has caused the Debian Bug report #1009467, regarding r-bioc-biostrings: FTBFS: BitMatrix.c:9:10: fatal error: S.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.) -- 1009467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009467 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: r-bioc-biostrings Version: 2.62.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220412 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -I"/usr/share/R/include" -DNDEBUG > -I'/usr/lib/R/site-library/S4Vectors/include' > -I'/usr/lib/R/site-library/IRanges/include' > -I'/usr/lib/R/site-library/XVector/include' -fpic -g -O2 > -ffile-prefix-map=/build/r-base-uzEjFP/r-base-4.1.3.20220408=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -c BitMatrix.c -o BitMatrix.o > BitMatrix.c:9:10: fatal error: S.h: No such file or directory > 9 | #include <S.h> /* for Salloc() */ > | ^~~~~ > compilation terminated. > make[1]: *** [/usr/lib/R/etc/Makeconf:168: BitMatrix.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/04/12/r-bioc-biostrings_2.62.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220412;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220412&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 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: r-bioc-biostrings Source-Version: 2.64.0-1 Done: Andreas Tille <ti...@debian.org> We believe that the bug you reported is fixed in the latest version of r-bioc-biostrings, 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 1009...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille <ti...@debian.org> (supplier of updated r-bioc-biostrings package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Sat, 14 May 2022 08:52:07 +0200 Source: r-bioc-biostrings Architecture: source Version: 2.64.0-1 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers <r-pkg-t...@alioth-lists.debian.net> Changed-By: Andreas Tille <ti...@debian.org> Closes: 1009467 Changes: r-bioc-biostrings (2.64.0-1) unstable; urgency=medium . * New upstream version Closes: #1009467 * Reorder sequence of d/control fields by cme (routine-update) * Standards-Version: 4.6.1 (routine-update) Checksums-Sha1: b815776de6a938d176c8d40c16cf22f92b948cc1 2258 r-bioc-biostrings_2.64.0-1.dsc 8f94572c18a0a92de53fc67d60ad39711d5d9a3a 12424145 r-bioc-biostrings_2.64.0.orig.tar.gz c7d576b5d8d99f83e48e1ce596f7a8f94e0b8a2a 4808 r-bioc-biostrings_2.64.0-1.debian.tar.xz e81dd8e921efc65711cf3e1a9016bce655b10640 11151 r-bioc-biostrings_2.64.0-1_amd64.buildinfo Checksums-Sha256: 3e5e4a4fb884026d9c4d9832b93c83d24689845df1cae4319881da03f6ad30e0 2258 r-bioc-biostrings_2.64.0-1.dsc e8c1dfbeb4b00d1dec1234693ab5ed6152fdd93c3afabd84173cd1843e14e5eb 12424145 r-bioc-biostrings_2.64.0.orig.tar.gz 6ad2dbc1a9bae8139e898e055e498ed122fdc4d89319cd6e1e137be69f1d1a29 4808 r-bioc-biostrings_2.64.0-1.debian.tar.xz f32e070d706c2981c7ef5a4e6278f529b974e784888a337b6deac4d646313b55 11151 r-bioc-biostrings_2.64.0-1_amd64.buildinfo Files: a7c51f42cbb7b2139ecc13a6c9f99992 2258 gnu-r optional r-bioc-biostrings_2.64.0-1.dsc e5545321cd5ce36b655c355e501ed9e0 12424145 gnu-r optional r-bioc-biostrings_2.64.0.orig.tar.gz 72b448d4f6992a85f0e339080d859752 4808 gnu-r optional r-bioc-biostrings_2.64.0-1.debian.tar.xz 79c099edf1fdc684402754433d80deb8 11151 gnu-r optional r-bioc-biostrings_2.64.0-1_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmJ/VsURHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtGIeA/6A23xrYTHdbRhlSn79i9Yu/CLJiAIEQgI +pgX/UejCEhJkBbqRUKr8EREG355QlxxZwXjx73ssSc8rWdOyLLw/2GLRK9luOcr BlPLv5XvLvHiVNhP21vgmjUHDDfnFEsSlSLKEK4UtzmREy2MKY0BsMYHzBj0dp2b xIO8pgpuGkDQZI/30MX2q+hZY8h/iGqgPeCd0b7DQ1+9NDdVxAWJEFgIsZv1YiwM eCSxm1so/yShjzVGAHkQOY5DQzBNDabqe84vaKwiY7vYYaKSpHw04FA6wJF58DRv azCdcHWsFAe74TFwG7on4T5pETM2b/xeNIxDwcjfjrRQ/SpNoKtC3suRII2+3e9M bMsanu/O+sAgblo3fkba7KndGSUzJjuh+tYb0BdmCfj2IS+OjZWmH7EU2Y+w9h+Z UhEmatiA7HJFqMfGbTFN8ZmjvL2Up2FZ1H0/HAP44sdilFerzXbMl0C1f52zPv0U pwt96SUKM/VAS2lHb72q50zZbruZXyTw2y/mSu1HpXAggI7X4MLyKeGMxK55t/xP 7cPGukRUpmyJnuUVQTfw98ccjMs1p1QKhIC7MokESCu2Po7eBpYRlo0gPtdHwcp3 MikLkgWdYhwNf9Omz4wl7KDaco6HERU7E9NcS68ywyUjD8+arRO+k4ntHSeJOCaj jzM4hb6VBTE= =D2Y6 -----END PGP SIGNATURE-----
--- End Message ---
