Skip to content
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

Assets (zip+md5) are missing in release v1.3.0 #15

Open
fabasoad opened this issue Sep 25, 2023 · 6 comments
Open

Assets (zip+md5) are missing in release v1.3.0 #15

fabasoad opened this issue Sep 25, 2023 · 6 comments

Comments

@fabasoad
Copy link

Problem

  1. Go to v1.3.0 release page.
  2. Look at the assets:

Screenshot 2023-09-26 at 8 28 40

Expected behavior

6 additional assets should be present there (zip+md5 for each OS). Example of v1.2.0 release:

Screenshot 2023-09-26 at 8 28 33

@fabasoad
Copy link
Author

fabasoad commented Oct 8, 2023

@bzz Hi! Please let me know how can I help to move this ticket further. Thanks!

@bzz
Copy link
Member

bzz commented Oct 9, 2023

Thanks for reporting! The best way is to check the gh actions for CI automation and their logs from the last release and post here any errors/irregularities (as compared to running the same steps locally).

@bzz
Copy link
Member

bzz commented Oct 13, 2023

CI for our releases use a base image that relies an old address for debian stretch

2023-10-09T22:02:09.4817874Z #7 0.331 E: Failed to fetch http://security.debian.org/debian-security/dists/stretch/updates/main/binary-amd64/Packages  404  Not Found [IP: 151.101.66.132 80]

Upstream's base image is up to date and as for this CLI binary we don't use cgo (AFAIK, the only change in the fork) - we probably should be good moving to it instead.

@miguelusque
Copy link

Hi! I am also interested in the missing assets. Thanks!

@bzz
Copy link
Member

bzz commented Feb 21, 2024

Hey @miguelusque - I'm sorry, I didn't have time to look into it.

So probably rather then waiting when me or @lafriks will have time to update the CI - you could probably try to submit a PR that changes project's GH CI action to start using the linked upstream image directly.

Hope this helps!

@lafriks
Copy link
Collaborator

lafriks commented Feb 21, 2024

I can try to look into it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants