Package Details: python3-aur 2021.11.20.1-1

Git Clone URL: https://aur.archlinux.org/python3-aur.git (read-only, click to copy)
Package Base: python3-aur
Description: AUR-related modules and helper utilities (aurploader, aurquery, aurtomatic).
Upstream URL: https://xyne.dev/projects/python3-aur
Keywords: arch_linux aur python
Licenses: GPL
Conflicts: aurploader
Provides: aurploader
Replaces: aurploader
Submitter: Xyne
Maintainer: Xyne
Last Packager: Xyne
Votes: 211
Popularity: 1.22
First Submitted: 2011-07-04 03:22
Last Updated: 2021-11-20 04:03

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 ... Next › Last »

onoakino commented on 2014-12-30 14:45

Hi Xyne. Forgive my ignorance but I was trying to do a system upgrade today when I encountered this error:

error: python3-aur: signature from "Xyne. (key #3) <xyne@archlinux.ca>" is invalid
:: File /var/cache/pacman/pkg/python3-aur-2014.12-1-any.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
debug: returning error 33 from check_validity : invalid or corrupted package
error: failed to commit transaction (invalid or corrupted package)
Errors occurred, no packages were upgraded.

Can you suggest what I'm doing wrong? I already did this:

sudo pacman-key --init; sudo pacman-key --populate archlinux; sudo pacman-key --refresh-keys

and still the error remains.

Xyne commented on 2014-12-30 03:37

I have added the new validpgpkeys array too all of my PKGBUILDs. Let me know if this solves the problem.

anatolik commented on 2014-12-29 18:03

Recent makepkg gives error

==> Verifying source file signatures with gpg...
python3-aur-2014.12.tar.xz ... FAILED (the public key EC3CBE7F607D11E663149E811D1F0DC78F173680 is not trusted)


I believe validpgpkeys=() is needed when using signatures

Xyne commented on 2014-12-25 03:57

he package now includes AUR.PkgList and aurpkglist to access the full list of AUR packages. See the website for details.

Xyne commented on 2014-11-23 00:17

@xantares
Sorry for the late reply. I saw your message a week ago but got distracted before I could reply and then forgot about it.

The help message explains why that happens. If you want to avoid it, pass it the path(s) to the archive(s) that you are trying to upload instead of relying on it globbing the directory.

xantares commented on 2014-11-14 10:52

hi,
I discovered a bug with aurploader and I dont' know where to report it:

I could not upload mingw-w64-libiconv-1.14 source tarball
as a patch was named libiconv-1.14-2.src.patch was chosen to be uploaded when typing:
aurploader --auto --keep-cookiejar

Uploading libiconv-1.14-2.src.patch
error: AUR submission error:
• Error - unsupported file format (please submit gzip
• ed tarballs generated by makepkg(8) only)

I renamed the patch to libiconv-1.14-2-mingw.patch and the right mingw-w64-libiconv-1.14-9.src.tar.gz was uploaded

xan.

Xyne commented on 2014-06-05 18:10

Orphaning, deletions and mergers should work now with AUR 3.1.0.

Xyne commented on 2014-06-01 19:43

Warning: orphaning, deletions and mergers are currently broken due to changes in the AUR 3.0.0. The RPC only reports the package ID at the moment but these actions require the pkgbase ID. Lukas has already created a patch to add this information and I hope that it will be pushed soon.

Xyne commented on 2014-05-31 03:08

Updated for 3.0.0. There is at least one bug in the AUR itself (incorrect IDs reported by the RPC interface for recently updated packages) and likely some bugs in python3-aur. Let me know if you find any.

Xyne commented on 2014-05-31 00:06

The error message is normally scraped from the returned HTML page. The AUR was updated to 3.0.0 on Tuesday and I haven't had time to update python3-aur yet.