Your message dated Sat, 16 Jan 2021 22:33:46 +0000 with message-id <e1l0u8g-000gp7...@fasolo.debian.org> and subject line Bug#966882: fixed in buici-clock 0.4.9.4+nmu1 has caused the Debian Bug report #966882, regarding buici-clock: FTBFS: res_y.cxx:149:10: fatal error: res_y.hxx: 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.) -- 966882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: buici-clock Version: 0.4.9.4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > g++ -c -g -O2 -o o/res_y.o res_y.cxx > res_y.cxx:149:10: fatal error: res_y.hxx: No such file or directory > 149 | #include "res_y.hxx" > | ^~~~~~~~~~~ > compilation terminated. > make[2]: *** [Makefile:91: o/res_y.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/08/02/buici-clock_0.4.9.4_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! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---Source: buici-clock Source-Version: 0.4.9.4+nmu1 Done: Sudip Mukherjee <sudipm.mukher...@gmail.com> We believe that the bug you reported is fixed in the latest version of buici-clock, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sudip Mukherjee <sudipm.mukher...@gmail.com> (supplier of updated buici-clock 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: Thu, 14 Jan 2021 22:05:45 +0000 Source: buici-clock Architecture: source Version: 0.4.9.4+nmu1 Distribution: unstable Urgency: medium Maintainer: Marc Singer <e...@debian.org> Changed-By: Sudip Mukherjee <sudipm.mukher...@gmail.com> Closes: 966882 Changes: buici-clock (0.4.9.4+nmu1) unstable; urgency=medium . * Non-maintainer upload. * Fix FTBFS. (Closes: #966882) - Remove rename and use res_y.hxx Checksums-Sha1: 80a1d33d04f6db014f88e181c0c92bb7f4b1b3c8 1500 buici-clock_0.4.9.4+nmu1.dsc b78001777fc9ebe577d4012278e7805af4c989ee 108220 buici-clock_0.4.9.4+nmu1.tar.xz 0e3503ee839ef46a8ea7b2c197d797c71a1d6db4 8753 buici-clock_0.4.9.4+nmu1_amd64.buildinfo Checksums-Sha256: b27fa8fb7d54bc747d5595aba2e88085ce1bfdfffd4d4685dc9b46edfaec5a60 1500 buici-clock_0.4.9.4+nmu1.dsc f274d9aeb359fbe820df94035cf24bf2a4f8560dc6242e7f6a05f145575f1a50 108220 buici-clock_0.4.9.4+nmu1.tar.xz 9da79a3d15ea53c04dab0fa5c736b14daaae9b4b6054f2d58376753dcf76a7ce 8753 buici-clock_0.4.9.4+nmu1_amd64.buildinfo Files: 2c4321b49a1454de5ede5021f18c6bdc 1500 x11 optional buici-clock_0.4.9.4+nmu1.dsc fc456ea22add722aab46256ab18de1a4 108220 x11 optional buici-clock_0.4.9.4+nmu1.tar.xz 3ed723d910457eca9b1b2cd899e99ef7 8753 x11 optional buici-clock_0.4.9.4+nmu1_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEuDQJkCg9jZvBlJrHR5mjUUbRKzUFAmAAwPIACgkQR5mjUUbR KzVGsxAAqaBCl/Q+WYj9B2GNMw75sPWxs+tWO4WPvgjwH6zElPc3kIy5cFTwRE2W MaFEM6anjzXURvqDibnI9v05cONsrT5FSeusEyIYL5ECGlX12jJ1YkIX6peFGVva 0ZAE04/XHkvo+7/V2XNy7/5Dgfw2cUZncFf/6O6gAueiWBHE2TH+j206yz0XeS62 GvGmmtdZfvbhvCX1lpOmUkTVfN9R+f93Yh0BBRlzvJ1jRIYfMcPJ+e4dRiQnB8RU ZS8mSue17PXIkqWUHXWoFkHlhz+DH3lxKOnRRqaKIKKPB1JhoTblEnJ65dFIOr74 CPCNaxia0wEWJr9da+5h8U/n6HIdyjarfpn9hBjkMEGtakHVxJrXWiYjjCulEuvu Om222rMCe6vmM+Mo3CYD71R8JsK87BqwU5KKIX+91SrN+3DS9g091XdZNXHgCFx8 mNTSEm/AQXtaQ1d+ZmWH4rd/fwlC6MkAwdkZVfz9yo5tHwR+7QxukpxuP7NbkxsT lgxqVLuK0BGuMYmL2ZsuA2T6eiPYQMSfq3S+TPi33o1FleXeU5wCg5i2vUsqKmea BYdZWlsnQceR8wTOSm6ukM+HdQpv9aIneCkJKTTrKuog0EKPadgJ2VpsnDnX9/Jz hMhHSugoJbZiptan1h8tTSBL5TddN04L1t8D/N7bTGS/SVCkHnM= =C1A4 -----END PGP SIGNATURE-----
--- End Message ---
