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

AUR not up to date #80

Closed
em2943 opened this issue Dec 11, 2022 · 5 comments
Closed

AUR not up to date #80

em2943 opened this issue Dec 11, 2022 · 5 comments
Assignees
Labels
suggestion TYPE: idea for new feature or improvements

Comments

@em2943
Copy link

em2943 commented Dec 11, 2022

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.

@em2943 em2943 added the suggestion TYPE: idea for new feature or improvements label Dec 11, 2022
@OleMortensen8
Copy link

OleMortensen8 commented Jan 31, 2023

I'd have to Agree. At least let people download the latest major version in the AUR.

@dhaavi
Copy link
Member

dhaavi commented Mar 6, 2023

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.

@SuperMewio
Copy link

It looks like someone today adopted the AUR package and updated it them self and now is hoping safing readopts it.

@dhaavi
Copy link
Member

dhaavi commented May 12, 2023

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.

@SuperMewio
Copy link

SuperMewio commented May 12, 2023

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.

@em2943 em2943 closed this as completed May 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
suggestion TYPE: idea for new feature or improvements
Projects
None yet
Development

No branches or pull requests

4 participants