@Aleks ? I understand that it is complex to get somethingās right and that software can be complex at not meeting expectations etc etc. I am only asking in the hope that there might be a resolution. But no matter. Iāll leave it.
I would revert this change, since in the case someone would like to install Vaultwarden, they would need to upgrade or install to YunoHost v12 beta. Not sure when the stable release is planned. Just saying. As a developer, I can install it on the commit before YnH v12 enforcement. But, as a User, you stay stuck or take the risk to break your installation installing an unstable release.
Edit: Ok, I see going further with the installation, the service doesnāt starts because it requires libssl3 which is not in bullseye.
@ericg thanks very much for this. Do you know if this version works with the latest release of the official iOS app which is where all this has come from.
On a wider note. I do appreciate the work and efforts that devs make to bring these apps to us, but this one is a bit of a pain.
I am interested to understand how the latest release for Vaultwarden is listed as an update for YNH 12 only when YNH 12 is still in beta but available for YNH 11. Iām sure that itās understandable that as users we rightly or wrongly become attached and in some cases reliant on our mobile apps and YNH apps, so we like to keep them up to date for all the obvious reasons.
Not all users are ready for ynh12. Please Iām not bitching, I wouldnāt dare and I know itās not your fault or problem, Iām just putting it out there as politely as I can before someone barks at me.
I am interested to understand how the latest release for
Vaultwarden is listed as an update for YNH 12 only when YNH 12 is still in beta but available for YNH 11. Iām sure that itās understandable that as users we rightly or wrongly become attached and in some cases reliant on our mobile apps and YNH apps, so we like to keep them up to date for all the obvious reasons.
We are humans, sometimes we make mistakes will we be forgiven?
latest release of the official iOS app will not work with latest release dor YNH 11.
Of course we all make mistakes we are all humanā¦ Jesus Iāve done a few f*** ups myself and paid a priceā¦ As I said Iām not bitching or moaning, Iām grateful, but I think its ok to askā¦
I have tweaked a few things in the GitHub Action. I switched the base container to Debian Bullseye. I also had to reduce parallelism for the Docker build and reduce core count for the Cargo compilation so that the build could complete (Iām just using the free tier).