-
Notifications
You must be signed in to change notification settings - Fork 33
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
Issuing a new release because the latest one (v0.1.3) fails to build now? #134
Comments
spantaleev
added a commit
to spantaleev/matrix-docker-ansible-deploy
that referenced
this issue
Jan 5, 2024
… users The latest tagged release (v0.1.3) does not pin any versions in its Dockerfile and as such fails to build right now. The `main` branch of rust-synapse-compress-state has already addressed this and is buildable, but there's no tagged release yet. Reported here: matrix-org/rust-synapse-compress-state#134
cvwright
pushed a commit
to cvwright/matrix-docker-ansible-deploy
that referenced
this issue
Jan 11, 2024
… users The latest tagged release (v0.1.3) does not pin any versions in its Dockerfile and as such fails to build right now. The `main` branch of rust-synapse-compress-state has already addressed this and is buildable, but there's no tagged release yet. Reported here: matrix-org/rust-synapse-compress-state#134
KarolosLykos
pushed a commit
to KarolosLykos/matrix-docker-ansible-deploy
that referenced
this issue
Mar 5, 2024
… users The latest tagged release (v0.1.3) does not pin any versions in its Dockerfile and as such fails to build right now. The `main` branch of rust-synapse-compress-state has already addressed this and is buildable, but there's no tagged release yet. Reported here: matrix-org/rust-synapse-compress-state#134
Yes, for example I get this error. And I managed to build it a couple of months ago.
|
Thank you for reporting this! v0.1.4 has been released, based off of latest |
spantaleev
added a commit
to spantaleev/matrix-docker-ansible-deploy
that referenced
this issue
Apr 13, 2024
This also removes the condition that made it use `latest` when self-building is enabled. v0.1.4 is expected to build correctly now, given that this issue is fixed: matrix-org/rust-synapse-compress-state#134
venimus
pushed a commit
to superhero-com/matrix-docker-ansible-deploy
that referenced
this issue
May 21, 2024
This also removes the condition that made it use `latest` when self-building is enabled. v0.1.4 is expected to build correctly now, given that this issue is fixed: matrix-org/rust-synapse-compress-state#134
Chasethechicken
pushed a commit
to Chasethechicken/matrix-docker-ansible-deploy
that referenced
this issue
Jul 6, 2024
This also removes the condition that made it use `latest` when self-building is enabled. v0.1.4 is expected to build correctly now, given that this issue is fixed: matrix-org/rust-synapse-compress-state#134
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It looks like the container image for the currently-latest release/tag (v0.1.3) fails to build now, because it doesn't pin any versions in its Dockerfile.
For people running matrix-docker-ansible-deploy on architectures other than
amd64
(for which there is a prebuilt container image), we do "self-building" (building the container image from theDockerfile
), which is causing errors.Looks like the main branch has already been fixed and the Dockerfile pins various versions, making it more reproducible.
Are you planning on stabilizing it and tagging a new release?
For matrix-docker-ansible-deploy, I'm adding a workaround for non-
amd64
architectures, so that people on such architectures would getlatest
(self-built from the latest commit inmain
).However, that's a moving target and potentially unstable. A tagged release would be appreciated!
The text was updated successfully, but these errors were encountered: