AUR web interface

Tasklist

FS#46549 - AUR4 prefers AUR packages over official packages

Attached to Project: AUR web interface
Opened by Wim Herremans (herremaw) - Saturday, 03 October 2015, 11:57 GMT
Last edited by Lukas Fleischer (lfleischer) - Saturday, 24 October 2015, 16:17 GMT
Task Type Bug Report
Category Backend
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version 4.1.0
Due in Version 4.2.0
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Looking at the AUR4 web page for package tkpacman (https://aur.archlinux.org/packages/tkpacman), I see that in the dependencies list, the AUR web interface prefers packages in the AUR over packages in the official repositories.

Whenever there is a package that also has a version in the AUR, only the AUR package gets a hyperlink.

E.g. there is no link to the official tcl and tk packages, but there is a link to tcl85 and tk85 in the AUR.

Similarly, there is only a hyperlink to 'sudo-selinux' in the AUR, but not to the normal 'sudo' in the official repository.

This is not only misleading, but even wrong. tkPacman would not work with tcl85 and tk85: the PKGBUILD (and also .SCRINFO) explicitly requires version 8.6 of Tcl/Tk or later.
This task depends upon

Closed by  Lukas Fleischer (lfleischer)
Saturday, 24 October 2015, 16:17 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 4.2.0. Backported to our live setup.
Comment by Lukas Fleischer (lfleischer) - Saturday, 03 October 2015, 12:16 GMT
aurweb does not know anything about official packages. Maybe we need to reintroduce dummy packages...
Comment by Wim Herremans (herremaw) - Saturday, 03 October 2015, 12:30 GMT
But still, if a dependency only appears in the official repositories, aurweb does show a link to it. See gksu, xfce4-terminal, xterm in the dependencies of tkpacman (https://aur.archlinux.org/packages/tkpacman).
Comment by Lukas Fleischer (lfleischer) - Saturday, 03 October 2015, 12:53 GMT
Sure. If there is no package in the AUR, aurweb simply assumes that the package must exist in the official repositories and adds a link. This doesn't work with provides, though. AUR packages can have virtual provisions that either exist or don't exist in the official repositories.
Comment by Lone_Wolf (Lone_Wolf) - Monday, 12 October 2015, 14:04 GMT
If aurweb can't distinguish between official packages and aur packages using provides= , then maybe aurweb should ignore all provides= from aur packages ?



Comment by Levente Polyak (anthraxx) - Tuesday, 20 October 2015, 00:50 GMT
I agree that we should really do something about this. On one hand its really handy to show AUR package links that provide the depending package, however its *incredibly* annoying that there is no link if its also an official package.
Even if it sounds like a lot of work... but can't we make AUR somehow aware of official packages? That would be a win-win situation so we have the advantage of both
Comment by Wim Herremans (herremaw) - Tuesday, 20 October 2015, 15:17 GMT
@Levente Polyak

If there is an official package, but no package in the AUR, then it already shows a link to the official package.

So, the AUR already seems to be aware of official packages.

If there is an official package and also a package in the AUR, then it only shows the link to the AUR package.

I would be happy if, in the latter case, it would show a link to both the official and the AUR package.
Comment by Lukas Fleischer (lfleischer) - Tuesday, 20 October 2015, 15:49 GMT
No, as I already explained in my previous reply, aurweb is not aware of official packages. It certainly is possible to implement that but it really is a lot of work...
Comment by Wim Herremans (herremaw) - Wednesday, 21 October 2015, 06:59 GMT
@Lukas Fleischer
I am sorry. I had forgotten to reread the previous comments before I wrote my comment of 20 October 2015.
I will not insist.

Loading...