question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[bug] conan export then conan install does not update sources

See original GitHub issue

Environment Details (include every applicable attribute)

  • Operating System+version: Any
  • Compiler+version: Any
  • Conan version: 1.19.2
  • Python version: 3.7

Steps to reproduce (Include if Applicable)

On our ci server, we have the following workflow.

$ conan export alex/dev /path/to/dep1
$ conan install /path/to/app/conanfile.txt --update --install-folder=/path/to/install_dir --build missing

the conanfile contains the reference to dep1/dev@alex/dev.

Logs (Executed commands with output) (Include/Attach if Applicable)

conan export /path/to/dep1 alex/dev
Exporting package recipe
dep1/dev@tanker/dev exports_sources: Copied 34 '.txt' files
//... all sources are being copied
**dep1/dev@tanker/dev: The stored package has not changed**
dep1/dev@tanker/dev: Using the exported files summary hash as the recipe revision: aee801aab70f4f4d6d4c1bec690c700e 
dep1/dev@tanker/dev: Exported revision: aee801aab70f4f4d6d4c1bec690c700e

Then the build called by conan install fails for the dep1, because the sources are not up-to-date. The exported source seems not be used. The updated sources are in the export_source folder but conan uses the sources from the source folder.

We do exports_sources = "*" in the dep1’s conanfile.py. We don’t know where the source folder comes from.

Our current workaround is to conan remove the dep1/dev@alex/dev on the CI server, which is pretty annoying.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:27 (19 by maintainers)

github_iconTop GitHub Comments

1reaction
Timencommented, Jul 7, 2022

Yeah seems a small but important detail, sorry about that. But I agree this might not be worth a fix at this time (additionally you could argue it’s expected behaviour). Anyways thank you for helping out, I will just stop using keep sources 😃

0reactions
memshardedcommented, Jul 19, 2022

Considering this as closed by #11659 (for Conan 2.0-beta.2), please read the above recommendation for 1.X

Read more comments on GitHub >

github_iconTop Results From Across the Web

Troubleshooting — conan 1.55.0 documentation
By default, Conan doesn't build packages from sources. There are several possibilities to overcome this error: You can try to build the package...
Read more >
conan export-pkg — conan 1.53.0 documentation
Exports a recipe, then creates a package from local source and build folders. If '–package-folder' is provided it will copy the files from...
Read more >
conan export-pkg — conan 1.21.3 documentation
Exports a recipe, then creates a package from local source and build folders. If '–package-folder' is provided it will copy the files from...
Read more >
Package development flow — conan 1.53.0 documentation
conan build¶. The build method takes a path to a folder that has sources and also to the install folder to get the...
Read more >
Changelog — conan 1.14.5 documentation
#4842; Bugfix: Fix metadata not being updated for conan export-pkg when using ... Packages can package sources, and specify their location, which will...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found