[package] bzip2/1.0.8: setting pkg_config names fails in Conan 1.19.4

Package and Environment Details (include every applicable attribute)

• Package Name/Version: bzip2/1.0.8
• Operating System+version: any
• Compiler+version: any
• Docker image: n/a
• Conan version: conan 1.19.4
• Python version: Python 3.6.8

Conan profile (output of conan profile show default or conan profile show <profile> if custom profile is in use)

[settings]
arch=x86_64
arch_build=x86_64
build_type=Release
compiler=apple-clang
compiler.libcxx=libc++
compiler.version=10.0
os=Macos
os.version=10.9
os_build=Macos
[options]
[build_requires]
*: cmake_installer/[~=3.15]@conan/stable
[env]
DEVELOPER_DIR=/Applications/Xcode-10.3.app/Contents/Developer
MACOSX_DEPLOYMENT_TARGET=10.9

Steps to reproduce (Include if Applicable)

conan install bzip2/1.0.8@

Any profile will do; this is a recipe failure.

Logs (Include/Attach if Applicable)

Click to expand log

Configuration:
[settings]
arch=x86_64
arch_build=x86_64
build_type=Release
compiler=apple-clang
compiler.libcxx=libc++
compiler.version=9.1
os=Macos
os_build=Macos
[options]
[build_requires]
[env]

Installing package: bzip2/1.0.8
Requirements
    bzip2/1.0.8 from 'conan-center-virtual' - Cache
Packages
    bzip2/1.0.8:3c88ad122762d62115d2625c9e8e54c12417952a - Download

bzip2/1.0.8: Retrieving package 3c88ad122762d62115d2625c9e8e54c12417952a from remote 'conan-center-virtual'
Downloading conanmanifest.txt: 100%|##########| 251/251 [00:00<00:00, 339kB/s]
Downloading conaninfo.txt: 100%|##########| 464/464 [00:00<00:00, 981kB/s]
Downloading conan_package.tgz: 100%|##########| 88.7k/88.7k [00:00<00:00, 47.3MB/s]
Decompressing conan_package.tgz: 100%|##########| 88.7k/88.7k [00:00<00:00, 14.1MB/s]
bzip2/1.0.8: Package installed 3c88ad122762d62115d2625c9e8e54c12417952a
bzip2/1.0.8: Downloaded package revision e4cc3886a58b639c0ee7a7895134ccb3
ERROR: bzip2/1.0.8: Error in package_info() method, line 57
	self.cpp_info.names["pkg_config"] = "bzip2"
	TypeError: '_CppInfo' object does not support item assignment

[danimtb]

I think to provide such a window is something unmaintainable since this repo if community driven and we declare it works with the latest Conan version. We cannot test all recipes with different versions of Conan and waiting to introduce new features in recipes will be against the development of Conan itself.

@datalogics-kam I strongly recommend you to upload your 3rd party recipes in an Artifactory and do not sync them continuously to the latest changes of this repo, as that would mean “living on the edge”. I’d recommend you to only sync with conan-center recipes whenever you upgrade the Conan version and try the recipes with small examples before.

Hope that makes sense

[datalogics-kam]

We do some complex work (including using Conan Package Tools) via the API, and the API is not guaranteed to be constant across minor changes, so we depend on it with conan~=1.19.0. When I change that, I have to test some things. This takes a little time, and most of the fixes have been easy. But I have to combine it with my other responsibilities.

I can appreciate that Conan is improving, and the conan-center-index makes it easier to track all the recipes. It also means that the recipes change quickly.

Some kind of version compatiblity window would be great, like maybe if the repo had the Conan version as a property, and the search could find a compatible RREV.

Or I may have to do some pinning…it’d be really great if we could pin RREVs of a certain remote only, so our local stuff could float, and then we could plan points where we do deliberate upgrades, perhaps near the beginning of a release cycle.