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

[REQ] Restore appimage update information #32

Open
qurious-pixel opened this issue May 31, 2022 · 3 comments
Open

[REQ] Restore appimage update information #32

qurious-pixel opened this issue May 31, 2022 · 3 comments

Comments

@qurious-pixel
Copy link

Restore appimage update information.

--appimage-updateinformation is not yet implemented in version

static-tools breaks updates.

@probonopd
Copy link
Owner

hello @qurious-pixel

static-tools breaks updates

Why? Just because --appimage-updateinformation should not mean that AppImageUpdate and similar tools can't read the update information.

Please provide more information. Thanks!

@qurious-pixel
Copy link
Author

Is there a way to override the calculated update information?
I don't really need update-information; it was just that in my first attempt, I broke all updates for my project, and had to revert the change.

Calculated updateinformation: gh-releases-zsync|probonopd|go-appimage|continuous|appimaged-*-x86_64.AppImage.zsync
Calculated updateinformation: gh-releases-zsync|qurious-pixel|<repo>|latest|<appname>-*-x86_64.AppImage.zsync

I am also using the continuous tag, but it applied the latest tag. for appname. I also do not want the version in the name so that I can maintain compatiblity with older versions of the app already deployed, which dont have version in the name.

@probonopd
Copy link
Owner

For go-appimage, my goal is to make this all automatic and without a chance for the user to change (which always has the risk to mess up).

If continuous vs. latest is wrong, then maybe you are running into
probonopd/go-appimage#54 (comment)

We should imho fix that.

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

No branches or pull requests

2 participants