So I guess what I'm saying with my previous comment is that until expac-git is resolved aurman will be broken for some of us. I wasn't having the netcat-openbsd issue so I switched the deps to expac.
Search Criteria
Package Details: aurman 2.22-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/aurman.git (read-only, click to copy) |
|---|---|
| Package Base: | aurman |
| Description: | AUR helper with almost pacman syntax |
| Upstream URL: | https://github.com/polygamma/aurman |
| Licenses: | MIT |
| Submitter: | polygamma |
| Maintainer: | polygamma |
| Last Packager: | polygamma |
| Votes: | 200 |
| Popularity: | 0.57 |
| First Submitted: | 2018-03-20 21:31 (UTC) |
| Last Updated: | 2023-05-14 20:28 (UTC) |
Dependencies (9)
- expac (expac-gitAUR)
- git (git-gitAUR)
- pyalpm (pyalpm-gitAUR)
- python (python37AUR, python311AUR, python310AUR)
- python-dateutil
- python-feedparser
- python-regex (python-regex-gitAUR)
- python-requests
- python-setuptools
Required by (1)
- aconfmgr-git (optional)
Sources (1)
<deleted-account> commented on 2018-06-21 18:48 (UTC)
xantares commented on 2018-06-19 09:22 (UTC)
pkgdesc should not contain the package name
eschwartz commented on 2018-06-18 18:43 (UTC)
@Cavsfan, I've already explained this. This is a GnuPG issue, not an issue with aurman itself. It is erroneous to ask for GnuPG support here, please consult one of the many Arch Linux support channels, e.g. the Wiki, the BBS, #archlinux on Freenode, and ask for help fixing your GnuPG which is unable to import PGP keys. This will get you an actual solution, unlike complaining here that this one key does not work (to which the only answer is "yes it does, you're wrong").
The aurman developer does not want to know about your GnuPG issues. His GnuPG works fine, and aurman works fine too. He's not necessarily an expert in GnuPG, but it's irrelevant because if he wanted to spend time providing support for GnuPG, he'd be on those other support channels providing general support on miscellaneous topics. Whereas this is the aurman-specific location for getting support specific to aurman itself.
There's no reason to "wait until it sorts itself out" -- if your GnuPG is broken, that won't magically fix itself, and it is something you should try to get fixed... by asking for support for GnuPG, in the appropriate places to get support for GnuPG on Arch Linux. Which is not here.
polygamma commented on 2018-06-18 18:26 (UTC) (edited on 2018-06-18 19:05 (UTC) by polygamma)
@Cavsfan that still does not make it an aurman PKGBUILD problem, but a problem with importing PGP keys. You can find the needed public key e.g. here: https://github.com/polygamma.gpg and you may import it manually
Cavsfan commented on 2018-06-18 18:23 (UTC) (edited on 2018-06-18 18:23 (UTC) by Cavsfan)
@polygamma, I read, duly noted and fully understood the pinned comments. The PKGBUILD was asking for this key to be installed and it failed. I thought that you would want to know as the package cannot be updated without the key. I fully apologize for making any comments on this page. @andreyv, thanks I tried that and it did not work. I'll just wait until it sorts itself out.
Pinned Comments