AUR web interface

**This is the bug tracker for the AUR web interface.**

Use this tracker to report bugs or make feature requests regarding the behaviour or implementation of the AUR software.
Please read the Reporting Bug Guidelines before filing a new task.

- Please report bugs related to Arch Linux official packages here:
- Please report bugs for [community] packages here:
- For any packages in the AUR contact the maintainer or leave a comment on the package's detail page.

Source Code:

FS#57230 - Ability to query pkgbase via AurJson

Attached to Project: AUR web interface
Opened by Alad Wenter (Alad) - Thursday, 25 January 2018, 21:42 GMT
Task Type Feature Request
Category Backend
Status Unconfirmed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 4.6.0
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 1
Private No


As of aurweb 4.6.0, only packages can be queried via the RPC, and not package bases. "virtualfish" [1] for example:

# virtualfish (multiinfo query)
"version": 5,
"type": "multiinfo",
"resultcount": 0,
"results": []

# python-virtualfish (multiinfo query)
"version": 5,
"type": "multiinfo",
"resultcount": 1,
"results": [
"ID": 446208,
"Name": "python-virtualfish",
"PackageBaseID": 125823,
"PackageBase": "virtualfish",
"Version": "1.0.5-5",
"Description": "A virtualenv wrapper for the Fish shell",
"URL": "",
"NumVotes": 1,
"Popularity": 0.348799,
"OutOfDate": null,
"Maintainer": "XenGi",
"FirstSubmitted": 1506266254,
"LastModified": 1506266254,
"URLPath": "/cgit/aur.git/snapshot/virtualfish.tar.gz",
"Depends": [
"License": [
"Keywords": []

A particular use case is that make/depends may (and should) be listed globally for split packages, see PKGBUILD(5): [2]

"Note that makepkg does not consider split package depends when checking if dependencies are installed before package building and with --syncdeps. All packages required to make the package are required to be specified in the global depends and makedepends arrays."

Thus if these global make/depends are not duplicated in the split packages, there's no way to retrieve them from the RPC as with other make/depends.

This task depends upon

Comment by Eli Schwartz (eschwartz) - Thursday, 25 January 2018, 22:01 GMT
I'm super-confused, shouldn't it already show make/depends for the split package? How does querying the package base instead, get you that info?

That specific package, seems to have a bug whereby the global depends are abused as makedepends, then overwritten when running package_*()

The PKGBUILD should be fixed, and the AurJson should not be modified for use cases which only ever affect badly written PKGBUILDs.
Comment by Alad Wenter (Alad) - Thursday, 25 January 2018, 22:13 GMT
The point is that by PKGBUILD(5) any depends required to build a package should be listed globally. There's no need that these should be listed in the split packages as well, particularly for makedepends that are not required at run-time.

That's just the definition, not badly written PKGBUILDs, and you can't retrieve these global depends from the RPC as it stands.

In any event this is just an example - pkgbase is available from the web interface so it makes sense it's available from the RPC too.
Comment by Eli Schwartz (eschwartz) - Thursday, 25 January 2018, 22:22 GMT
Okay, so as mentioned on IRC, there is the inconsistency involved in excluding it from being offered.

Question is, should we then only offer the same information available on which basically boils down to the PackageBase*, list of split packages, and information associated with the aurweb record itself like: maintainer and git repo information, votes, keywords. Or maybe expand the pkgbase page.

EDIT: Right.
Except, I do feel that any split PKGBUILD which is overwriting a global depends=() is doing it wrong. ;) Appending, maybe... but then the package/ page will anyways list everything actually needed for makepkg, while not including things which are required by the other split package as runtime-only depends.

OTOH runtime depends on a split package page are not necessarily needed for the build at all, then.


I think any solution should apply both to the web interface and the RPC.