-
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
imake: add imake/1.0.8 recipe #6677
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@jgsogo |
|
we are on it: #6686 |
This comment has been minimized.
This comment has been minimized.
This is probably because I added |
@jgsogo |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@jgsogo
Where it should be
See #6677 (comment) |
If you have a look at the output table, you can see it says The table is useful to know where the error comes from: ...although I agree the error message in GitHub should provide that information as well. Maybe we can just add the first lines of the log output with the command to the snippet we are showing in Github:
|
Now the actual issue, why package Why it doesn't happen more often? Because typically, when someone pushes changes to a PR and the previous job is cancelled, the changes affect the recipe-revision and it doesn't matter if one of the packages is corrupted. I'll check in Artifactory and (probably) trigger again this PR |
Thanks. |
Thanks! 😊 C3i has some secrets behind the scenes... sometimes it is useful also for me to try to explain the issue, and usually, I mention @danimtb, @uilianries and @SSE4 in case it is something that helps them to improve their understanding of the system (not all of us know about every detail). Indeed, that package-ID is corrupted in Artifactory, it is missing To fix it, we can just remove the package from that repository, or whatever forces Conan to build again the package and upload it. From the user's perspective, all you can do is force a new recipe revision (or a different PR number). PS.- There is a feature requested to the Artifactory team to enforce consistency of packages, making the uploads transactional, or returning that a package doesn't exist if it is not valid. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Something happened with Windows. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
c3i go brrrrrrrrr |
All green in build 12 (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Step by step 💪
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
paso a paso!
stap per stap |
Specify library name and version: imake/1.0.8
For #6387
dependency tree: sdl -> nas -> imake -> xorg-proto -> xorg-macros
conan-center hook activated.