FS#32895 - {archweb} Request for repo list in server status JSON ouput.

Attached to Project: Arch Linux
Opened by Xyne (Xyne) - Thursday, 29 November 2012, 01:25 GMT
Last edited by Kristian (klausenbusk) - Monday, 05 June 2023, 17:43 GMT
Task Type Feature Request
Category Web Sites
Status Closed
Assigned To Jelle van der Waa (jelly)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Please add the list of mirrored repos to the JSON output when returning server status results.

E.g.

"repos" : ["core","extra","community","testing",...]

This would be very useful for scripts and other applications that need to determine for which repos the mirrorlist can be used. Currently this list needs to either be hard-coded, scraped from a mirror, or guessed by checking which repo sections in pacman.conf include the mirrorlist (some applications do not require a pacman.conf file, and guessing is limited to enabled repos).
This task depends upon

Closed by  Kristian (klausenbusk)
Monday, 05 June 2023, 17:43 GMT
Reason for closing:  Upstream
Additional comments about closing:  Please report upstream if this is still relevant: https://github.com/archlinux/aurweb.
Comment by Pierre Schmitz (Pierre) - Thursday, 29 November 2012, 06:20 GMT
Any mirror that does not include all of our repos should be considered broken. It either needs to be fixed or removed.
Comment by Xyne (Xyne) - Thursday, 29 November 2012, 15:43 GMT
@Pierre
You have misunderstood my request.

I do not want a list for each repo in the "urls" dictionary. I want a single list in the root dictionary.

For example, the current repos are
'community',
'community-staging',
'community-testing',
'core',
'extra',
'gnome-unstable',
'kde-unstable',
'multilib',
'multilib-testing'
'staging',
'testing'

I would like to be able to retrieve that list directly from the web interface instead of having to scrape mirrors/hard code the list/rely on local guesswork.
Comment by Dan McGee (toofishes) - Saturday, 20 April 2013, 16:51 GMT
I have no problem making this available, but I think it belongs at its own URL. There are many attributes about each of these repositories people might care about, such as testing/staging status, that are not captured in a simple test list. I've attached sample output of something I just whipped up. Will this work?
Comment by Dan McGee (toofishes) - Saturday, 20 April 2013, 16:52 GMT
I should actually attach the file...
   repos.json (0.7 KiB)
Comment by Xyne (Xyne) - Saturday, 20 April 2013, 18:24 GMT
A separate URL with additional metadata would be very useful. Take a look at the JSON repo metadata files that I use for repoman:
http://xyne.archlinux.ca/projects/repoman/

I think dependencies, architectures and options such as SigLevel would be very useful. If you want to use those files as a starting point, grab the source archive from the project page.

Loading...