[question] Can't reproduce RREV while building binary packages locally

I need some conan-center packages for architectures that currently not supported So I cloned this repo and tried to build something. But the problem is that my locally-cloned recipes and conan-center ones have different RREVs! Looks like that’s because conandata.yml is filtered somehow during CI on conan-center side, so the recipe revision changes. E.g. for protobuf recipe the repo contains

sources:
  3.9.1:
    sha256: 98e615d592d237f94db8bf033fba78cd404d979b0b70351a9e5aaff725398357
    url: https://github.com/protocolbuffers/protobuf/archive/v3.9.1.tar.gz
  3.11.4:
    sha256: a79d19dcdf9139fa4b81206e318e33d245c4c9da1ffed21c87288ed4380426f9
    url: https://github.com/protocolbuffers/protobuf/archive/v3.11.4.tar.gz
patches:
  3.9.1:
    - patch_file: "patches/protobuf-3.9.1.patch"
      base_path: "source_subfolder"
  3.11.4:
    - patch_file: "patches/protobuf-3.11.4.patch"
      base_path: "source_subfolder"

but if I install the package from conan-center, local cache contains the following:

patches:
  3.11.4:
  - base_path: source_subfolder
    patch_file: patches/protobuf-3.11.4.patch
sources:
  3.11.4:
    sha256: a79d19dcdf9139fa4b81206e318e33d245c4c9da1ffed21c87288ed4380426f9
    url: https://github.com/protocolbuffers/protobuf/archive/v3.11.4.tar.gz

This is very unfortunate as it effectively prohibits any local/conan-center package mixing. Any idea how to overcome this?

[jgsogo]

Hi @db4 ! Yes, we are using a hook in ConanCenter to remove other versions from conandata.yml (this one). The rationale behind that is to keep the same revision for existing versions when only the conandata.yml file has been modified (e.g. to add a new version). That way we don’t need to build binaries just because the revision has changed.

One way you can use to get the recipes from conan-center is to download them and generate the binaries you need using (if you don’t need to modify the recipe):

conan download <reference> --recipe

If you need to modify the recipe, then yes, you need to retrieve the recipe to your local workspaces and you need to clone this repo.

[db4]

@jgsogo Thank you for all your help, I’ve managed to setup the necessary infrastructure locally.