ERROR: Remote recipe is newer than local recipe
See original GitHub issueGetting this with Jenkins, I thought I remember seeing that CPT had a force built in to override this error but I guess not. Should it?
conans.errors.ConanException: Remote recipe is newer than local recipe:
Remote date: 1524688506
Local date: 1524688499
Issue Analytics
- State:
- Created 5 years ago
- Comments:30 (16 by maintainers)
Top Results From Across the Web
Recipe and Sources in the Same Repo - Conan Docs
When you export the recipe (or when conan create is called) the exported recipe will capture the remote and commit of the local...
Read more >c++ - Conan - changing the recipe of existing packages and ...
I would like to update the channel of some existing conan packages in my local conan/artifactory server without having to recompile/rebuild ...
Read more >7 devtool Quick Reference - the Yocto Project Documentation
7.10 Upgrading a Recipe . As software matures, upstream recipes are upgraded to newer versions. As a developer, you need to keep your...
Read more >autobump — Bioconda documentation
The Scanner initializes the asyncio loop and for each recipe, loads the ... If the remote branch exists and is newer than master,...
Read more >Contributing packages - conda-forge
If you would like to add more than one related packages, they can be added to staged-recipes in a single pull request (in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I would try to explain what is this issue about and why we don’t force the uploads by default.
Conan, when you upload a recipe or a package, check the manifest containing the checksums of the recipe files (usually just a conanfile.py). If the contents are the same, Conan doesn’t care about the dates, because, actually will skip the real upload as it is already there.
But if the recipe is different, by default, we want to warn the user if you are trying to overwrite a newer recipe. How can it happen? well, if a slave takes less time to build a package than others, it could happen that the recipe uploaded is newer than the local one.
But why are they different? Usually, this is an issue with the CRLF characters. If you see some traces like the following you have the answer:
Here are some docs about it: https://docs.conan.io/en/latest/faq/using.html?highlight=crlf#packages-got-outdated-when-uploading-an-unchanged-recipe-from-a-different-machine
Otherwise, if they are different, maybe you are mixing or overriding on purpose different recipes in the CI? Several consecutive pushes? Should it be happening? These are some questions to clarify before take the decission of forcing an upload. Please, shed some light about you use case and we could enable a configuration to opt-in the package overwritting.
@michaelmaguire you mentioned a promotion process, could you explain a bit more?
No thanks, I just ran into these line ending issues…