Package Details: pakku 0.17-3

Git Clone URL: https://aur.archlinux.org/pakku.git (read-only, click to copy)
Package Base: pakku
Description: Pacman wrapper and AUR helper with a pacman-like user interface
Upstream URL: https://github.com/zqqw/pakku
Keywords: aur aur-helper helper nim pacman pakku wrapper
Licenses: GPL-3.0-only
Submitter: kitsunyan
Maintainer: apropos (IOAOI)
Last Packager: apropos
Votes: 32
Popularity: 0.000001
First Submitted: 2018-03-10 21:55 (UTC)
Last Updated: 2024-12-07 23:15 (UTC)

Pinned Comments

apropos commented on 2022-02-05 01:48 (UTC)

I've adopted this package, and plan to update it to use the community-maintained version at https://github.com/zqqw/pakku unless there are any complaints.

Latest Comments

1 2 3 4 Next › Last »

Dirk commented on 2026-11-09 08:33 (UTC)

@gavinhungry thanks for the hint and explanation. So it was really a change and not just a newer library dependency. Just built from master branch ans it’s working again, thanks!

gavinhungry commented on 2026-11-07 10:23 (UTC)

@Dirk,

Try building against the latest in the git repo - specifically, you need a232a0f.

Anubis (which protects the AUR) doesn't like an empty user-agent, and pakku chokes on trying to parse the error page as JSON. The above commit fixes both issues.

Dirk commented on 2026-11-07 10:14 (UTC)

Checking AUR database for upgrades does not work anymore. I manually built the currently available version AUR (version 0.16). Running a system upgrade results in the following.

% pakku -Syu
[sudo] password for root:
:: Synchronizing package databases...
 core is up to date
 extra is up to date
:: Starting full system upgrade...
 there is nothing to do
:: Resolving build targets...
checking AUR database for upgrades...
error: failed to parse server response
error: failed to parse server response
error: failed to parse server response
error: failed to parse server response
warning: commons-downloader-git was not found in AUR
warning: cura-bin was not found in AUR
warning: cura-binary-data was not found in AUR
warning: cura-resources-materials was not found in AUR
warning: fstl was not found in AUR
warning: invo-git was not found in AUR
warning: menu-builder-git was not found in AUR
warning: minetest-game-cdb was not found in AUR
warning: nvidia-580xx-dkms was not found in AUR
warning: nvidia-580xx-utils was not found in AUR
warning: pakku was not found in AUR
warning: phpdoc-phar was not found in AUR
warning: static-web-server-bin was not found in AUR
warning: wl-color-picker was not found in AUR
warning: wofimoji was not found in AUR
 there is nothing to do

My config:

[options]
AurComments
CheckIgnored
PrintAurNotFound
PrintLocalIsNewer

marralesfios commented on 2026-05-30 08:02 (UTC)

Why is it now suddenly opening my text editor (gedit) in the TAG_EDITMSG file after every AUR package upgrade?

abd commented on 2024-12-02 00:25 (UTC)

Got:

==> Making package: pakku 0.17-2 (Mon Dec 2 07:22:24 2024)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found v0.17.tar.gz
==> Validating source files with sha256sums...
v0.17.tar.gz ... Passed
==> Extracting sources...
-> Extracting v0.17.tar.gz with bsdtar ==> Removing existing $pkgdir/ directory... ==> Starting build()... GEN: doc/pakku.8.in Traceback (most recent call last): File "/usr/bin/a2x", line 5, in <module>
from asciidoc.a2x import cli
ModuleNotFoundError: No module named 'asciidoc'
make: *** [Makefile:99: doc/pakku.8.in] Error 1

micwoj92 commented on 2024-08-08 21:30 (UTC)

Please add pacman to dependencies and use SPDX license identifier.

lenhuppe commented on 2023-07-19 22:20 (UTC) (edited on 2023-07-19 23:54 (UTC) by lenhuppe)

The pakku build process is intermittently failing. Reverting nim to version 1.6.6-2 appears to fix the problem. This happened to me once in the past. Here is what the failure looks like:

CC: bisect.nim
CC: ../../../../../../usr/lib/nim/pure/collections/sequtils.nim
.CC: install.nim
...CC: tools.nim
........Traceback from system (most recent call last)
SIGSEGV: Illegal storage access. (Attempt to read from nil?)
make: *** [Makefile:121: src/pakku] Segmentation fault (core dumped)
make: *** Waiting for unfinished jobs....
Hint:  [Link]
Hint: gc: refc; opt: speed; options: -d:release
55737 lines; 2.237s; 75.461MiB peakmem; proj: /tmp/makepkg/pakku/src/pakku-0.17/lib/tools.nim; out: /tmp/makepkg/pakku/src/pakku-0.17/lib/tools [SuccessX]
==> ERROR: A failure occurred in build().
    Aborting...

apropos commented on 2023-03-01 02:35 (UTC)

Okay, I successfully triggered the below error. It appears to be nondeterministic: if you run into it, please retry the build again.

apropos commented on 2023-02-17 17:27 (UTC)

Strange, I can't reproduce. Are you using choosenim or the official Nim package?

lenhuppe commented on 2023-02-17 03:03 (UTC) (edited on 2023-05-22 21:47 (UTC) by lenhuppe)

Got this with nim version 1.6.10-2 and pakku 0.17-2:

CC: tools.nim
......Traceback from system (most recent call last)
SIGSEGV: Illegal storage access. (Attempt to read from nil?)
make: *** [Makefile:121: src/pakku] Segmentation fault (core dumped)
make: *** Waiting for unfinished jobs....
Hint:  [Link]
Hint: gc: refc; opt: speed; options: -d:release
55737 lines; 2.191s; 75.375MiB peakmem; proj: /tmp/makepkg/pakku/src/pakku-0.17/lib/tools.nim; out: /tmp/makepkg/pakku/src/pakku-0.17/lib/tools [SuccessX]
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'pakku'

Reverting nim to version 1.6.6-2 resolves the issue.