You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm using the export-pkg command to create a Conan package of pre-built binaries, with the -f json format flag to capture information on the created package for further processing. But the exported package seems to have null for package revision (prev) in the json output. Am I missing something here, or is it perhaps intentional?
There is nothing wrong with the exported package, and when uploading it to a remote, the prev seems to be computed as expected. But it would be useful to obtain prev from the json output of export-pkg.
Conan version: 2.0.13
Os: Windows
Python: 3.11.2
Steps to reproduce with zlib from conan-center:
conan source --version 1.3 .
cd src
conan install ..
Then build zlib as an ordinary CMake project (might need to drop the CMAKE_INSTALL_PREFIX from the leading set() commands in zlib's CMakeLists.txt for the build to work), and create a Conan package of the results:
What is your question?
Hi, I'm using the
export-pkg
command to create a Conan package of pre-built binaries, with the-f json
format flag to capture information on the created package for further processing. But the exported package seems to havenull
for package revision (prev) in the json output. Am I missing something here, or is it perhaps intentional?There is nothing wrong with the exported package, and when uploading it to a remote, the prev seems to be computed as expected. But it would be useful to obtain prev from the json output of export-pkg.
Conan version: 2.0.13
Os: Windows
Python: 3.11.2
Steps to reproduce with zlib from conan-center:
Then build zlib as an ordinary CMake project (might need to drop the CMAKE_INSTALL_PREFIX from the leading set() commands in zlib's CMakeLists.txt for the build to work), and create a Conan package of the results:
Thanks for your fantastic work,
/J
Have you read the CONTRIBUTING guide?
The text was updated successfully, but these errors were encountered: