|
Description
Agostino Sarubbo
2022-07-11 16:34:50 UTC
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/portage.git/commit/?id=772fdceea5f148d9bb5fd6c87ffd48f87ca93bab commit 772fdceea5f148d9bb5fd6c87ffd48f87ca93bab Author: Sam James <sam@gentoo.org> AuthorDate: 2022-08-23 00:27:52 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-08-23 00:33:19 +0000 bin/install-qa-check.d: drop QA_PKGCONFIG_VERSION checks from 60pkgconfig They've been too noisy. We can consider restoring this with an opt-in check (perhaps by setting QA_PKGCONFIG_VERSION) in future. Bug: https://bugs.gentoo.org/857654 Signed-off-by: Sam James <sam@gentoo.org> NEWS | 3 ++ bin/install-qa-check.d/60pkgconfig | 60 -------------------------------------- 2 files changed, 3 insertions(+), 60 deletions(-) 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. (In reply to Sam James from comment #2) > 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?)). I have portage-3.0.47 and I still see these QA warnings so I suppose it has been restored? Do we need to report these type of issues? |
