search

safing / portmaster-packaging

Portmaster packages and installers
GNU General Public License v3.0
49 stars 22 forks source link

AUR not up to date #80

Closed em2943 closed 1 year ago

em2943 commented 1 year ago

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.

OleMortensen8 commented 1 year ago

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

dhaavi commented 1 year ago

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 commented 1 year ago

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

dhaavi commented 1 year ago

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 commented 1 year ago

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.