search

YunoHost-Apps / akkoma_ynh

Social media based on ActivityPub, fork of Pleroma
https://akkoma.social/
GNU Affero General Public License v3.0
15 stars 6 forks source link

How do we manage non-named/fixed version names ? #2

Closed lapineige closed 1 year ago

lapineige commented 1 year ago

Contrary to Pleroma, Akkoma seems not to provide an URL with a dedicated version number/commit. This means the version provided behind the URL will change after each (stable) release.

This is a trouble for Yunohost app packaging. How do we manage it ?

Right now this means the sha2565sum will fails, and (hopefully) the installation process will stop instead of installing a newer version that might require manual intervention. Hence, until we upgrade the package, installs will no longer be possible.

Tagadda commented 1 year ago

You could download a specific commit with a URL like this : https://akkoma.dev/AkkomaGang/akkoma/archive/4a78c431cfe1373ba09a3c02bc56502063975890.tar.gz (where 4a78c431cfe1373ba09a3c02bc56502063975890 is the commit sha)

Tagadda commented 1 year ago

You could try to adapt the glitch-soc auto updater

lapineige commented 1 year ago

Ok, I will try to take a look later… for now on I'm trying to install it ! 😂

Tagadda commented 1 year ago

Also, for glitchsoc_ynh version number, I use the date of the last commit (eg. 2022.12.20~ynh1), to avoid 3.5.0~ynhinfinity ^^

bugsysop commented 1 year ago

@lapineige How this is managed actualy?

lapineige commented 1 year ago

It is not. I'm getting the latest version, when it will change, install will break because of wrong sha256sum.

Thanks @Tagadda for the suggestion, I may go for this option.