-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[aws-crt-cpp] aws-crt-cpp/0.17.23: Builds fails due to using aws-c-common component that no longer exists #17382
Comments
+1 |
Will be fixed by #17120 |
this also impacts: s2n, aws-c-io, aws-c-compression, aws-c-http, aws-c-sdkutils, aws-c-auth aws-c-io, aws-c-compression, aws-c-http, aws-c-sdkutils, aws-c-auth look for aws-c-common::aws-c-common-lib and/or s2n::s2n-lib |
Too bad it wasn't a single PR, however big it's interconnected
I'm screwed untill all of them are accepted
How can I help?
M.
May 5, 2023 8:43 PM, "SpaceIm" ***@***.*** ***@***.******@***.***>)> wrote:
Yes there is a PR for each impacted recipe to not depend anymore on component of these recipes.
—
Reply to this email directly, view it on GitHub (#17382 (comment)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AB6R5S5WX7G3PQAAZHMMCQTXEVC3DANCNFSM6AAAAAAXU6CYWE).
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
A am running into this as well. We actually rolled back to Conan pre-2.0 due to so many common packages not working. Now it seems that the 2.0 changes have broken the older versions as well. I have tried using recipe revisions with no luck. |
@mattubereckenpr Give recipe revisions one more go. It did fix it for me, however you need to remember to turn it on in global settings.
|
There is #17120, which is waiting other PRs, which are waiting team reviews for more than 1 month. |
@kwach , which revision did you pin to? I'm having a similar issue with aws-sdk-cpp and it's not very clear how to "rollback" |
That worked for me. I'm using S3, Transfers...
|
I ended up having to pin to revisions that had
and these others:
It's possible that the version number could be higher but I started with the versions that worked in our previous build and looked for a package revision that allowed the service to build successfully. |
I made a script to reset the aws packages back to a certain date (note for conan 1)
Run it something like this:
I'd recommend after doing this creating a lock file to stop further updates |
Description
When including
aws-crt-cpp/0.17.23
as a requirement in a conanfile, theconan install
command fails with the error:Looking at the aws-c-common recipe, there was a commit last week which removed the
aws-c-common-lib
component: 430521eHowever, the aws-crt-cpp recipe still references this component:
conan-center-index/recipes/aws-crt-cpp/all/conanfile.py
Line 103 in 746eeba
Package and Environment Details
Conan profile
[settings]
os=Linux
os_build=Linux
arch=x86_64
arch_build=x86_64
compiler=gcc
compiler.version=9
compiler.libcxx=libstdc++11
build_type=Release
[options]
[build_requires]
[env]
Steps to reproduce
conan install . -pr:b=default -pr:h=default
was run with a custom conanfile that has a requirementaws-crp-cpp/0.17.23
and is using thecmake
andCMakeDeps
generatorsLogs
Click to expand log
The text was updated successfully, but these errors were encountered: