-
Notifications
You must be signed in to change notification settings - Fork 9
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
What happened to the AUR Package? #6
Comments
Hey @nigelwarning, Thanks for reporting, I can investigate and perhaps if necessary put it up. |
Hello @webketje and @nigelwarning a few Users reported problems with the Package. Also they say that the PKGBUILD of the AUR Package was not okay. Since I don't know how I could have satisfied the community about the PKGBUILD, I made a deletion request. In retrospect it might have been better to disown the package. I hope you understand it. But just feel free to upload it again to the AUR. |
@StevenSeifried thx for the info, could you clarify the AUR package was not okay ? |
No, imho there is no problem with the AUR Package. I had take a quick look at v0.7. It also works without problems (a few colors are not really correct, but this is no problem with the Package). |
AUR Package worked great for me too! Sad to hear that there were problems with the PKGbuild then. |
@nigelwarning you can feel free to upload it in the AUR again. The PKGBUILD file is still avalible. If you find the PKGBUILD file is correct, you can update it to v0.7 and upload it again. It would be great if the package is back in the AUR (because it's a great piece of software!). But please understand that i don't want to maintain this AUR package after my last "experience". |
Uploaded the 0.6 version back to AUR again since the 0.7 is still in pre-lease it just clones the latest master. |
I made a git package because of the rules: |
@nigel, tyvm for your efforts on this project. Could you do us and the community a service and keep the latest PKGBUILD in sync with the one in the repo? (i.e. could you create a pull request starting from this branch: https://github.com/webketje/tuxedo-backlight-control/pull/new/feature/aur-pkg) |
I fixed it and switched to the new branch. Because of the rules of the AUR. I have to use -git in the package name and use the pkgver git version. https://aur.archlinux.org/packages/tuxedo-backlight-control-git/ |
@nigelwarning thx but you misunderstood. I meant: Then I will approve it, and merge it back into master and when that is done you can republish it. Right now, your package is broken (the source should not be the feature branch but master). Also now there are 2 AUR packages which is confusing Unfortunately I cannot publish AUR packages myself as it requires to have Arch running. @StevenSeifried can the original AUR pkg still be updated? In any case, 1 of the 2 needs to be deprecated |
@webketje yes, the original AUR pkg can still be updated or someone can made a deletion request |
@webketje - I've updated AUR to build from master rather than the feature branch. Have also added tuxedo-keboard as a dependency as per @StevenSeifried's request. Will request the original AUR pkg to be deleted. |
Hey!
Normally I used a AUR Package for this great piece of software. Why? Because the AUR is easy and updates automatically.
Since a few weeks, this package has been removed from the AUR. What is the reason for that?
Orginal link:
https://aur.archlinux.org/packages/tuxedo-backlight-control/
Thanks!
The text was updated successfully, but these errors were encountered: