Search Criteria
Package Details: ryzen-controller-bin 2.6.0-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/ryzen-controller-bin.git (read-only, click to copy) |
---|---|
Package Base: | ryzen-controller-bin |
Description: | (DEPRECATED) A minimal Electron application to use ryzenAdj through a friendly interface |
Upstream URL: | https://gitlab.com/ryzen-controller-team/ryzen-controller |
Licenses: | CC0 1.0 Universal |
Conflicts: | ryzen-controller, ryzencontroller |
Provides: | ryzen-controller |
Submitter: | termuellinator |
Maintainer: | termuellinator |
Last Packager: | termuellinator |
Votes: | 8 |
Popularity: | 0.33 |
First Submitted: | 2020-08-29 15:27 (UTC) |
Last Updated: | 2023-09-20 10:02 (UTC) |
Dependencies (2)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- ryzenadj-gitAUR (ryzenadjAUR)
Latest Comments
« First ‹ Previous 1 2 3
yochananmarqos commented on 2020-08-26 20:34 (UTC) (edited on 2020-08-26 20:36 (UTC) by yochananmarqos)
@termuellinator: First, the new package
ryzen-controller-bin
would need to be created, then a merge request would need to be submitted to mergeryzencontroller-bin
intoryzen-controller-bin
.In the new
ryzen-controller-bin
package, you would add the old package to conflicts() and replaces():termuellinator commented on 2020-08-26 17:46 (UTC)
you are right @yochananmarqos , that is indeed more elegant, thank you :)
And i noticed the missing dash too late after creating the package - and there is no good way (that i know of) to rename an AUR-Package, is there?
yochananmarqos commented on 2020-08-26 14:10 (UTC) (edited on 2020-08-26 14:11 (UTC) by yochananmarqos)
Why not extract the tarball directly into the
$pkgdir
?Also, this should be renamed to
ryzen-controller-bin
to match the project name and filenames.termuellinator commented on 2020-04-09 08:22 (UTC)
Ah, thank you very much! First i suspected some kind of formating error (newline for example) and checked if the file was unicode - it never dawned to me that makepkg needs ASCII though ^^
archi42 commented on 2020-04-09 07:15 (UTC) (edited on 2020-04-09 07:16 (UTC) by archi42)
Your PKGBUILD has leading three bytes as a Unicode Byte Order Mark (BOM). This is not shown by vim (most editors probably know how to interpret it), but messes up makepkg:
No idea how to change that with vim, but with kate I opened the file, changed UTF-8 at the bottom right corner to Western European -> ISO-8859-1, hit Ctrl+S and the BOM was gone:
Someone(tm) probably should open up a bug with the makepkg folks to check that the file is ASCII, not unicode.
termuellinator commented on 2020-03-31 10:29 (UTC)
even so i still get the error, just with
PKGBUILD: line 1: #: command not found
I already tried several variations but keep getting this error - i'm also curious to why this is but am kind of out of ideas tbhSpanner_Man commented on 2020-03-30 23:46 (UTC)
PKGBUILD line 1 should read as;
# Maintainer: termuellinator
otherwise the following error;PKGBUILD: line 1: #Maintainer:: command not found
« First ‹ Previous 1 2 3