Summary: | dev-libs/unittest++-2.0.0-r2 installs pkg-config files with mismatched Version | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Agostino Sarubbo <ago> |
Component: | Current packages | Assignee: | Louis Sautier (sbraz) <sbraz> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 857654 | ||
Attachments: | build.log |
Description
Agostino Sarubbo
![]() Created attachment 798286 [details]
build.log
build log and emerge --info
It looks like the file relies on a CMake variable that is not set: https://github.com/unittest-cpp/unittest-cpp/blob/v2.0.0/UnitTest%2B%2B.pc.in#L9 I tried applying https://github.com/unittest-cpp/unittest-cpp/commit/bdef2bdd62598afc31e17b24349b47d3813eed57 but it did not help. I'd appreciate any help on the matter. See https://bugs.gentoo.org/857654#c1. This check has been dropped in portage-3.0.35 because of false positives, usually relating to SONAME versioning not corresponding to ${PV}. It may be restored at a later time in an opt-in fashion (either for users/developers to set in e.g. make.conf, or for ebuilds to enable when upstream is known to make errors (possibly could be by setting QA_PKGCONFIG_VERSION?)). Apologies for the noise until now. It was an experiment and while some legitimate bugs were found, it was too noisy and that's unfair to developers. |