-
Notifications
You must be signed in to change notification settings - Fork 10
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
Missing python module pyparsing #23
Comments
I assume this is regarding the asciidoctor-spec container? If so, are you using the current version (the one whose SHA is in .gitlab-ci.yml)? There are some weird Docker caching issues at play both inside and outside of CI and referring by SHA is the only reliable way I've found to get the right version of the container image. If you are using that image, how are you invoking the build resulting in this error? I don't have any trouble building using it. |
Related: #22 |
It appears my issue is that I was using the vulkan-docs-base image which hasn't been updated in dockerhub since |
Is |
Note that we have had a bit of a versioning mess while trying to work out the best way to label images in this repo, and I don't think (but haven't double-checked) that all the erroneous tags were revoked, or if that's even possible (EDIT: looks like that happened, there are no |
It looks like it is sourcing |
@jekstrand I cleaned up the inner workings of that so that pushing all containers is just a IIRC it might have also been @oddhack to request keeping |
vulkan-docs* are not being updated any more. They are no longer used in the recent Vulkan repos as you noticed and I don't want to be on the hook for keeping them updated and working indefinitely - the current spec repo identifies the asciidoctor-spec image as the one to use and refers only to that. I do not know how to deprecate a Docker image, if that's even possible in a way which is visible to people using it. If there's a way we should probably do that. |
Regarding how the images get updated, when there's a need I generate and push a new one by hand, then update the SHA256 in the CI scripts to pull that specific one. |
Tried to build the Vulkan spec today and got
The text was updated successfully, but these errors were encountered: