AUR RPC reply changed today - unfortunately that would require rebuilding pikaur manually
Search Criteria
Package Details: pikaur-git 1.19-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/pikaur-git.git (read-only, click to copy) |
|---|---|
| Package Base: | pikaur-git |
| Description: | AUR helper which asks all questions before installing/building. Inspired by pacaur, yaourt and yay. |
| Upstream URL: | https://github.com/actionless/pikaur |
| Licenses: | GPL3 |
| Conflicts: | pikaur |
| Provides: | pikaur |
| Submitter: | actionless |
| Maintainer: | actionless |
| Last Packager: | actionless |
| Votes: | 28 |
| Popularity: | 0.26 |
| First Submitted: | 2018-01-31 06:20 (UTC) |
| Last Updated: | 2024-04-05 00:42 (UTC) |
Dependencies (12)
- git (git-gitAUR)
- pyalpm (pyalpm-gitAUR)
- python-build (make)
- python-hatchling (python-hatchling-gitAUR) (make)
- python-installer (python-installer-gitAUR) (make)
- python-markdown-it-py (make)
- python-setuptools (make)
- python-wheel (make)
- devtools (devtools32-gitAUR, devtools-gitAUR) (optional) – for Arch Pkgs support in -G/--getpkgbuild operation
- pacman-contrib (pacman-contrib-gitAUR) (optional) – to use in pacman hook/systemd timer for cleaning up pikaur cache
- python-defusedxml (python-defusedxml-gitAUR) (optional) – securely wrap Arch news replies
- python-pysocks (optional) – for socks5 proxy support
Required by (6)
- aptpik (requires pikaur)
- octopi (requires pikaur) (optional)
- octopi-dev (requires pikaur) (optional)
- pacfoster (requires pikaur) (optional)
- pacup-arch-git (requires pikaur) (optional)
- sapphire-butler (requires pikaur)
Sources (1)
actionless commented on 2022-11-27 13:06 (UTC)
katt commented on 2020-08-03 20:10 (UTC) (edited on 2020-09-06 17:02 (UTC) by katt)
I don't know how more specific I can be than what the wiki tells you, that you've decided to completely disregard. VCS packages should at the very least include the revision, why not just copy the first or second example instead of playing clueless?
EDIT: I guess you just don't test your package locally before blindly pushing to AUR. The pkgver() was correct after all but not executed before pushing.
actionless commented on 2020-08-03 16:38 (UTC)
be more specific, otherwise i don't have extra time for playing guesses
katt commented on 2020-08-03 16:15 (UTC)
Please follow the pkgver() guidelines. https://wiki.archlinux.org/index.php/VCS_package_guidelines#The_pkgver()_function
actionless commented on 2018-05-03 15:58 (UTC) (edited on 2018-05-03 15:58 (UTC) by actionless)
@leoteodoro78: please request here: https://github.com/actionless/pikaur/issues
i'll address it according to the workplan (unless someone else will submit a PR earlier)
<deleted-account> commented on 2018-05-03 02:38 (UTC)
could you please add a command to pass a command to makepkg? like ~$ pikaur -S --noconfirm discord --m-arg --skippgpcheck ?
actionless commented on 2018-04-28 14:02 (UTC)
@spider-mario, xorg and gtk3 are using the same versioning schema in the official arch repo
here is also a related discussion: https://github.com/actionless/pikaur/issues/143
spider-mario commented on 2018-04-23 18:30 (UTC) (edited on 2018-04-23 18:30 (UTC) by spider-mario)
This should probably use the recommended pkgver() function: https://wiki.archlinux.org/index.php/VCS_package_guidelines#Git
Otherwise, pacman thinks that going e.g. from 0.10+6+gff6e318-1 to 0.10.1+27+g4071904-1 is a downgrade.
The rationale for that recommended format is here: https://wiki.archlinux.org/index.php/VCS_package_guidelines#The_pkgver.28.29_function
Alad commented on 2018-03-18 21:09 (UTC)
Maybe consider adding a pikaur package (release version), cf. comments on the pacaur page.
Pinned Comments
actionless commented on 2022-11-27 13:06 (UTC)
AUR RPC reply changed today - unfortunately that would require rebuilding pikaur manually