Arch Linux User Repository

Search Criteria

Enter search criteria

Search by

Keywords

Out of Date

Sort by

Sort order

Per page

Package Details: pikaur 1.32-2

Package Actions

Git Clone URL:	https://aur.archlinux.org/pikaur.git (read-only, click to copy)
Package Base:	pikaur
Description:	AUR helper which asks all questions before installing/building. Inspired by pacaur, yaourt and yay.
Upstream URL:	https://github.com/actionless/pikaur
Keywords:	aur aur-helper pacman wrapper
Licenses:	GPL-3.0-only
Conflicts:	pikaur-git
Provides:	pikaur
Submitter:	actionless
Maintainer:	actionless
Last Packager:	actionless
Votes:	286
Popularity:	3.23
First Submitted:	2018-03-24 23:58 (UTC)
Last Updated:	2024-12-22 14:35 (UTC)

Dependencies (12)

git (git-git^AUR, git-gl^AUR)
pyalpm (pyalpm-git^AUR)
python-build (make)
python-hatchling (python-hatchling-git^AUR) (make)
python-installer (python-installer-git^AUR) (make)
python-markdown-it-py (make)
python-setuptools (make)
python-wheel (make)
devtools (devtools32-git^AUR, devtools-git^AUR, devtools-doas^AUR) (optional) – for Arch Pkgs support in -G/--getpkgbuild operation
pacman-contrib (pacman-contrib-git^AUR) (optional) – to use in pacman hook/systemd timer for cleaning up pikaur cache
python-defusedxml (python-defusedxml-git^AUR) (optional) – securely wrap Arch news replies
python-pysocks (optional) – for socks5 proxy support

Required by (6)

aptpik
arch-update (optional)
octopi (optional)
pacfoster (optional)
pacup-arch-git (optional)
sapphire-butler

Sources (1)

pikaur-1.32.tar.gz

Pinned Comments

actionless commented on 2024-09-03 17:51 (UTC)


      /:}               _
     /--1             / :}
    /   |           / `-/
   |  ,  --------  /   /
   |'                 Y
  /                   l
  l  /       \        l
  j  ●   .   ●        l
 { )  ._,.__,   , -.  {
  Y    \  _/     ._/   \

  _____/|__________________________________________________
 /                                                         \
 |  Make sure to read                                      |
 |  https://wiki.archlinux.org/title/Arch_User_Repository  |
 |  thouroughly before asking any questions                |
 \_________________________________________________________/

actionless commented on 2022-11-26 04:55 (UTC)

DONT REPORT ANY ISSUES HERE

actionless commented on 2018-12-10 10:20 (UTC) (edited on 2020-12-03 17:37 (UTC) by actionless)

please report your issue here with attaching the full output with --pikaur-debug flag: https://github.com/actionless/pikaur/issues

Latest Comments

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 Next › Last »

actionless commented on 2018-12-10 10:20 (UTC) (edited on 2020-12-03 17:37 (UTC) by actionless)

please report your issue here with attaching the full output with --pikaur-debug flag: https://github.com/actionless/pikaur/issues

vivaeltopo commented on 2018-12-10 09:06 (UTC)

1.3.2-1 fails when updating aur packages:

File "/usr/lib/python3.7/site-packages/pikaur/install_cli.py", line 561, in review_build_files reason=_("installing for the first time") KeyError: 'package'

1.3.1 was fine

mueslo commented on 2018-10-11 08:59 (UTC)

Finally an AUR helper that doesn't shit the bed when a single package fails to build. Thanks for your great work!

actionless commented on 2018-10-07 17:41 (UTC)

reverted

andreyv commented on 2018-10-07 17:35 (UTC)

gettext is in the base-devel group. PKGBUILDs don't need to depend on this group: https://wiki.archlinux.org/index.php/Arch_User_Repository#Prerequisites

actionless commented on 2018-10-07 17:31 (UTC)

@clasick, thanks, updated the PKGBUILD

clasick commented on 2018-10-07 17:28 (UTC) (edited on 2018-10-07 17:28 (UTC) by clasick)

package building now fails.

gettext is a dependency for building but is not listed as such.

installing gettext resolves the issue.

Toric commented on 2018-09-01 21:15 (UTC)

how do you change the program to open packagebuilds for review in? The man page doesnt seem to mention it.

actionless commented on 2018-08-28 18:27 (UTC)

i see, it should 80 characters, however i guess it will be better to leave pacaur and other inspirations in the description, because i think they're much more useful for understanding what the application does (otherwise description could raise either even bigger or less clear)

also it seems what directly specifying inspirations is not a considered to be a bad practice in official repos: pacman -Ss | grep -i "inspired" -B 1

I'll update the description soon after will come up how to shrink it all to 80 chars

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 Next › Last »