The (to be) attached -r3 ebuild fixes multiple issues over the -r2 currently in the tree: - Set GIT_COMMIT to the correct commit id (as listed on [1]) - Make sure the binary is installed as 'blackbox_exporter'. At least here, the build produces a binary 'blackbox_exporter-0.18' [2]. - Explicitly call the postinst scripts for all the used eclasses. WIthout this change, only go-module_pkg_postinst gets called, meaning file capabilities are not applied. [1]: https://github.com/prometheus/blackbox_exporter/releases/tag/v0.18.0 [2]: This behavior might depend on the version of dev-util/promu used for the build. I currently have version 0.11.1. Reproducible: Always
Created attachment 706641 [details] blackbox_exporter-0.18.0-r3.ebuild
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=296cda93328bb4787cf5d369cfaab09a5f968ab0 commit 296cda93328bb4787cf5d369cfaab09a5f968ab0 Author: William Hubbs <williamh@gentoo.org> AuthorDate: 2021-05-13 15:26:18 +0000 Commit: William Hubbs <williamh@gentoo.org> CommitDate: 2021-05-13 15:28:22 +0000 app-metrics/blackbox_exporter: 0.19.0 bump Signed-off-by: William Hubbs <williamh@gentoo.org> Closes: https://bugs.gentoo.org/788952 app-metrics/blackbox_exporter/Manifest | 449 ++++++++++++++++++ .../blackbox_exporter-0.19.0.ebuild | 513 +++++++++++++++++++++ 2 files changed, 962 insertions(+)
