Package Details: powerpill 2021.11-15

Git Clone URL: https://aur.archlinux.org/powerpill.git (read-only, click to copy)
Package Base: powerpill
Description: Pacman wrapper for faster downloads.
Upstream URL: https://xyne.dev/projects/powerpill
Keywords: arch_linux pacman system
Licenses: GPL
Submitter: Xyne
Maintainer: Xyne
Last Packager: Xyne
Votes: 244
Popularity: 0.23
First Submitted: 2012-11-29 03:58 (UTC)
Last Updated: 2024-05-17 23:43 (UTC)

Dependencies (10)

Required by (1)

Sources (2)

Latest Comments

« First ‹ Previous 1 .. 14 15 16 17 18 19 20 Next › Last »

Xyne commented on 2013-07-06 11:54 (UTC)

Some servers do not correctly handle HEAD requests and/or conditional GET requests. Without knowing if "powerpill -Syy" would have worked or if "pacman -Sy" would have failed, I can't tell if it is a powerpill error or a server error, but I expect that it is the latter. If it happens again, try "powerpill -Syy", then switch to a different mirror. If it happens with other mirrors, pastebin your pacman and powerpill configuration files (including the mirrorlist) so that I can (try to) :determine the cause of the problem.

idupree commented on 2013-07-05 23:30 (UTC)

Powerpill corrupted my sync DBs somehow (fixable by `sudo pacman -Syy`). I installed powerpill today and did `sudo powerpill -Syuw`, then I tried to double-check with pacman: % sudo pacman -Syuw error: GPGME error: No data error: GPGME error: No data error: GPGME error: No data error: GPGME error: No data :: Synchronizing package databases... core is up to date extra is up to date community is up to date multilib is up to date error: database 'core' is not valid (invalid or corrupted database (PGP signature)) error: database 'extra' is not valid (invalid or corrupted database (PGP signature)) error: database 'community' is not valid (invalid or corrupted database (PGP signature)) error: database 'multilib' is not valid (invalid or corrupted database (PGP signature)) Did I do something wrong?

Xyne commented on 2013-05-10 20:18 (UTC)

2013.5.10 supports the new Python 3 version of Pacserve and should be noticeably faster now due to both more efficient pacserve querying and better pacserve peer detection.

Xyne commented on 2013-04-29 21:24 (UTC)

It looks like a pyalpm error. Try re-installing pyalpm (and maybe pacman).

beanaroo commented on 2013-04-27 10:40 (UTC)

ImportError: libalpm.so.7: cannot open shared object file: No such file or directory I assume this is related to the release of Pacman 4.1? Not sure.

Xyne commented on 2013-01-29 23:50 (UTC)

@atyoung pacman -Si python Name : python ... Provides : python3 I prefer explicitly versioned Python dependencies. It's future-proof. For the same reason, all of my Python 3 packages are named python3-* instead of python-*. Using a naming and dependency scheme that requires massive renaming when upstream changes is silly when there is a perfectly logical way to avoid it without any issues whatsoever.

<deleted-account> commented on 2013-01-29 16:05 (UTC)

Dependency needs to be python not python3. python2 has the number appended to the package name, python 3 is just python.

Xyne commented on 2012-12-12 14:54 (UTC)

@ranger Thanks, I have added rsync as an optional dependency. @oboedad55 Please try again with the current PKGBUILD.

ranger commented on 2012-12-12 12:51 (UTC)

rsync shouldn't be a dependency?

« First ‹ Previous 1 .. 14 15 16 17 18 19 20 Next › Last »