Your message dated Thu, 18 Jun 2020 22:03:43 +0000 with message-id <e1jm2dl-000dnk...@fasolo.debian.org> and subject line Bug#959573: fixed in facter 3.11.0-4.2 has caused the Debian Bug report #959573, regarding facter FTBFS with yaml-cpp 0.6.3 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.) -- 959573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959573 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: facter Version: 3.11.0-4.1 Severity: important Tags: sid bullseye User: team+bo...@tracker.debian.org Usertags: boost1.71 facter fails to build with boost 1.71 | Running tests... | /usr/bin/ctest --force-new-ctest-process -j5 | Test project /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu | Start 1: libfacter tests | 1/1 Test #1: libfacter tests ..................Child aborted***Exception: 1.81 sec | | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | libfacter_test is a Catch v1.12.1 host application. | Run with -? for options | | ------------------------------------------------------------------------------- | Scenario: using a double fact value | When: serialized to YAML | Then: it should have the same value | ------------------------------------------------------------------------------- | /<<PKGBUILDDIR>>/lib/tests/facts/double_value.cc:27 | ............................................................................... | | /<<PKGBUILDDIR>>/lib/tests/facts/double_value.cc:30: FAILED: | REQUIRE( string(emitter.c_str()) == "42.4242" ) | with expansion: | "42.424199999999999" == "42.4242" | | free(): invalid pointer | ------------------------------------------------------------------------------- | Scenario: using the fact collection | Given: default facts | Then: facts should resolve | ------------------------------------------------------------------------------- | /<<PKGBUILDDIR>>/lib/tests/facts/collection.cc:91 | ............................................................................... | | /<<PKGBUILDDIR>>/lib/tests/facts/collection.cc:91: FAILED: | {Unknown expression after the reported line} | with expansion: | | due to a fatal error condition: | SIGABRT - Abort (abnormal termination) signal | | =============================================================================== | test cases: 7 | 5 passed | 2 failed | assertions: 141 | 139 passed | 2 failed | | | | 0% tests passed, 1 tests failed out of 1 | | Total Test time (real) = 1.81 sec | | The following tests FAILED: | 1 - libfacter tests (Child aborted) | Errors while running CTest | make[1]: *** [Makefile:133: test] Error 8 I'm not sure if this is a real issue or caused by linking boost 1.67 (via dependencies): | /usr/bin/ld: warning: libboost_locale.so.1.67.0, needed by /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libcpp-hocon.so, may conflict with libboost_locale.so.1.71.0 | /usr/bin/ld: warning: libboost_thread.so.1.67.0, needed by /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libcpp-hocon.so, may conflict with libboost_thread.so.1.71.0 | /usr/bin/ld: warning: libboost_regex.so.1.67.0, needed by /usr/lib/x86_64-linux-gnu/libleatherman_curl.so.1.4.2, may conflict with libboost_regex.so.1.71.0 | /usr/bin/ld: warning: libboost_filesystem.so.1.67.0, needed by /usr/lib/x86_64-linux-gnu/libleatherman_curl.so.1.4.2, may conflict with libboost_filesystem.so.1.71.0 | /usr/bin/ld: warning: libboost_chrono.so.1.67.0, needed by /usr/lib/x86_64-linux-gnu/libleatherman_util.so.1.4.2, may conflict with libboost_chrono.so.1.71.0 So this issue might simply disappear, once we do the rebuilds for the transition. Cheers -- Sebastian Ramacher
--- End Message ---
--- Begin Message ---Source: facter Source-Version: 3.11.0-4.2 Done: Sebastian Ramacher <sramac...@debian.org> We believe that the bug you reported is fixed in the latest version of facter, 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 959...@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 facter 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, 17 Jun 2020 23:21:32 +0200 Source: facter Architecture: source Version: 3.11.0-4.2 Distribution: unstable Urgency: medium Maintainer: Puppet Package Maintainers <pkg-puppet-de...@lists.alioth.debian.org> Changed-By: Sebastian Ramacher <sramac...@debian.org> Closes: 959573 Changes: facter (3.11.0-4.2) unstable; urgency=medium . * Non-maintainer upload. * debian/patches: Fix tests with yaml-cpp 0.6.3 (Closes: #959573) Checksums-Sha1: 793fef5b8271c989826911e482f39c2025df04fb 2551 facter_3.11.0-4.2.dsc b5619c40674ed40a3fa3f560c4de7f6aafc59bbe 16588 facter_3.11.0-4.2.debian.tar.xz Checksums-Sha256: e7c7ca51229968956b4825639f5a4ecb60f3d97572d31f8be10adb67f0870722 2551 facter_3.11.0-4.2.dsc e1eec64122a8cf764e21d8d2e3535bec1310843fe825e2d28a495a7b71ec8e81 16588 facter_3.11.0-4.2.debian.tar.xz Files: bf178fce817395ead501e7e9239e6e14 2551 admin optional facter_3.11.0-4.2.dsc 3a63a28f5d0cf1ed1aa7951e47900204 16588 admin optional facter_3.11.0-4.2.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl7qjB8ACgkQafL8UW6n GZOcNg//SODwjXtSov+M/HM4cHxbAoaskNrs1k0bF8g/ZqNMhZ+7MGzr+vKCw9TZ PX+QSPzCmQ+K5IFLabzCgWF/P9MearlQEoVw+kQiViFx5Lqv6H/k58xK7AHOVHUS ekRTqF95sPfK52YLX6WHcgQxkfjaPzaBAQnN81lPJdcy2mk0rAg1OSH99+Qw+ANS t6NBESZciySA53pO7eSrI3fGy2ehYNJrrZHvFxHTCkojZbLJdS3Qef4BcTTp7jKO QViY31Qv5/ACdkDK+h2Akbrkk6CEUBhnM2USt14NadQ9K5t3hDmwDxakX2L73K3I mjw2997J79W8Xdg+o7dpSwNJ0uav0D8WaBneIZse7dMvK6/hR9Ca6k2cYYALsrvK 6Qach+5xZI5hUFEEg8aySY1J2Vuzees+iZZRHQ+BVOWtKU6lBPy+kq1vztSCc3NT oXPrLq3KOhd5O7M+XC5P59IUTIvKZmOtdTekPsT4fGevhLX7TtawI+eY+u6ZlLx1 CoaiK4MEbkpKFxn08HmPIB8PmiVqUVI32/d89j06a7veqhLWEtdOqUFoLwpkkWHX dA5vOGZC64AkUK8DR8SL3i33iEsVG3W1S1PWuWwS7rBSwofE3b4rQYRGajFceutu NmNNN6ZghKXK4NkEEdNqr+CXl1/OBhTyHjjBPzOs22QslDODsO8= =cNLY -----END PGP SIGNATURE-----
--- End Message ---
