| 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: | 199 |
| Popularity: | 0.006525 |
| First Submitted: | 2018-03-20 21:31 (UTC) |
| Last Updated: | 2023-05-14 20:28 (UTC) |
While I am here though. The dependency on expac-git>=8.1.g5ae006f should probably be changed. vercmp just checks the ascii codes and can not tell which git commit comes after which. This means g5ae006f could change to become something that evaluated as less than the last commit.
Instead expac should be using the more standard 8.1.r100.g5ae006f versioning where you can then dep a specific revision expac-git>=8.1.r100
@regeya,
This is expected and any users using the AUR should be aware of how this works. Yelling about outdated VCS packages and claiming that an Arch Dev and an AUR helper developer doesn't understand the basics is just insulting to say the least.
It is even documented in the page we expect you to read. https://wiki.archlinux.org/index.php/Arch_User_Repository#Foo_in_the_AUR_is_outdated.3B_what_should_I_do.3F
@regeya - https://github.com/polygamma/aurman/issues/153#issuecomment-399194590 I even provided "proof", that the version is going to be the needed one.
And you know, had someone said, "just install the package manually or from your current aur helper, some black magic bleepery will give it the right version number upon install despite the version number being wrong in the PKGBUILD," that would have been more or less acceptable. In fact, that's what I'm saying right now. :-) No need for the open hostility or the condescending behavior; could you leave this all here so that anyone else running into the problem will know?
The goal of bootstrapping packages which require versioned dependencies, of VCS packages for which the version will only be calculated when actually running makepkg to build the package, is fundamentally incompatible with upfront dependency resolution. In order to install expac-git and aurman at the correct versions, it is necessary to first install expac-git on its own, then install aurman.
This is not a problem to be solved by AUR helpers. AUR helpers can do a lot, but they cannot completely obviate the need for human interaction.
You're a Turing-complete user -- act like it.
@regeya the dependency listed in the PKGBUILD of aurman is correct. aurman needs expac-git>=8.1.g5ae006f, whereas 8.1.g5ae006f-1 is the version you get, if you build expac-git as of now, so what is your problem?
Pinned Comments