-
Notifications
You must be signed in to change notification settings - Fork 23
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
AUR not up to date #80
Comments
I'd have to Agree. At least let people download the latest major version in the AUR. |
Thanks for raising this with us. We have a CI that pushes new versions, but it failed on the last run for the v1 installer. We are looking into it. Until then, you can use the current installer, as it will download the newest version anyway on install. |
It looks like someone today adopted the AUR package and updated it them self and now is hoping safing readopts it. |
How can someone just adopt it? I also clicked the button and it was back with no confirmation or anything. This is actually quite troubling. I hope there are some safeguards here. |
I think what happened was the package had become orphaned do to neglecting to updating the package by Safing them self. Since it was orphaned, anyone with an AUR account can adopt it and start updating the package. If Safing just updated the package them self in a more timely matter, this would not have happened. Users who download things off of the AUR are supposed to review the PKGBUILD file when installing to verify the installer is not malicious. I mostly just wanted to give a heads up since I had read this open report several weeks ago. I just figured Safing had something bigger blocking them from updating it and was going to update it when they were able but then this happened. [EDIT] And I would also like to note that it had no maintainer after the user updated it so I think that may be why you were able to adopt it after. |
the installer on the AUR is not up to date, it shouldn't be hard to update the repo but take as long you need to.
The text was updated successfully, but these errors were encountered: