Package Details: aurman 2.20.1-2

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.62
First Submitted: 2018-03-20 21:31
Last Updated: 2021-06-19 12:54

Pinned Comments

polygamma commented on 2018-08-21 18:02

aurman development for public use has been stopped. i suggest migrating to yay, i am not interested in any kind of feedback, bug reports, feature requests etc. anymore.

Latest Comments

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

Akrai commented on 2018-07-20 17:41

i just want to thank polygamma for this helper

eschwartz commented on 2018-07-09 17:15

That's got nothing to do with aurman.

dawcek commented on 2018-07-09 16:54

Thanks @Eschwartz. I set this option like you suggested. There is error related to that as normal user I cannot write anything in system directory /var/cache/pacman/pkg/

eschwartz commented on 2018-07-09 15:43

makepkg itself supports PKGDEST, see the makepkg.conf(5) manpage.

dawcek commented on 2018-07-09 15:28

Hello everyone. May you tell me if there possibility automatically move built package to main packages cache(/var/cache/pacman/pkg) ?? Thanks in advance for your response.

polygamma commented on 2018-06-24 13:07

aurman depends on "expac" again.

eschwartz commented on 2018-06-24 07:21

Heads up -- expac 9 has now been tagged as a stable release.

Morganamilo commented on 2018-06-24 02:25

@Eschwartz thanks for clearing that up, I'd say add the r, epoch or not. Not that big of a deal though obviously, if it's not worth the effort then whatever.

eschwartz commented on 2018-06-24 01:58

I removed a bunch of comments (and the no-longer-needed replies) which were just providing help for GnuPG. Stop doing that. It's inappropriate.

Stop suggesting people break the package by messing with the dependencies. This is advice that moved on from being a waste of space, to being downright dangerous.

Morganamilo: on the topic of expac-git's version format, it uses the standard git describe format, but doesn't insert an "r" into the commit count. 8.2 is not the release tag, 8 is the release tag and 2 is the commit count. Yes, I agree the format is confusing, but it definitely doesn't break vercmp unless dreisner chooses to publish a major.minor release which is is unlikely since he's never done so before (and also knows the dangers of changing the versioning format in non-backwards-compatible ways).

The missing "r" is something that cannot be fixed anyway, without either adding an epoch or waiting until a stable release, since 9.r0.g${sha} is greater than 8.2.g{$sha}, while 8.r2.g${sha} is lesser.

Morganamilo commented on 2018-06-23 16:25

Oh well in that case it doesn't really matter then due to the .2 being more important than the commit.

Although depending on a specific commit doesn't really mean anything when it comes to alpm's vercmp.

I would still talk to falconindy about using the standard pkgver format though.