Package Details: pakku 0.14-1

Git Clone URL: https://aur.archlinux.org/pakku.git (read-only, click to copy)
Package Base: pakku
Description: Pacman wrapper with AUR support
Upstream URL: https://github.com/kitsunyan/pakku
Licenses: GPL3
Submitter: kitsunyan
Maintainer: None
Last Packager: kitsunyan
Votes: 29
Popularity: 0.109116
First Submitted: 2018-03-10 21:55
Last Updated: 2019-12-20 05:13

Latest Comments

« First ‹ Previous 1 2

mrksngl commented on 2019-10-29 08:45

Rebuilding fails:

GEN: completion/bash

1 out of 4 hunks FAILED

make: *** [Makefile:90: completion/bash] Error 1

Morganamilo commented on 2019-10-29 00:31

Linking will lead to undefined behaviour and breakage. Just rebuild your package.

Nolle commented on 2019-10-28 09:41

After updating pacman to 5.2.0 I get the following error:

pakku: error while loading shared libraries: libalpm.so.11: cannot open shared object file: No such file or directory

linking /usr/lib/libalpm.so.12 to /usr/lib/libalpm.so.11 gives a workaround.

arch1t3cht30 commented on 2019-01-12 11:38

I get the error http://ix.io/1y78 (on Manjaro/KDE, everything works fine on arch):

bash_completion is installed. Copying over the file from another system makes it work.

kitsunyan commented on 2018-12-03 15:54

@Ranguvar don't use nim from testing repo. This package is broken and pakku doesn't support nim 0.19 yet.

@benjamin-l no, it doesn't. asciidoc is requred to generate man pages, which are included to release tarballs.

benjamin-l commented on 2018-12-03 08:24

This package appears to depend on 'asciidoc', even though that's not declared as a dependency.

Ranguvar commented on 2018-11-09 04:49

Fails for me ..

http://ix.io/1rnq

Morganamilo commented on 2018-10-14 11:40

No they are part of base-devel.

https://wiki.archlinux.org/index.php/Arch_User_Repository#Prerequisites

pkoretic commented on 2018-10-14 09:43

'patch' and 'fakeroot' needs to be added as a dependency

Morganamilo commented on 2018-09-11 23:42

It would appear this pkgbuild is set to build in debug mode. Should it not be targeting a release build instead?