Thanks for the details, everyone. I’ll have a look at updating manpages.d.o to use the ftp-master API and will report back on how that goes.
On Fri, Apr 21, 2017 at 9:55 AM, Paul Wise <p...@debian.org> wrote: > On Fri, 2017-04-21 at 09:28 +0200, Michael Stapelberg wrote: > > > pabs, what’s the current status on this? > > Mostly at the 'collecting information' stage; about what hard-coding > exists and what requirements there might be etc. > > > AFAICT, you mentioned you wanted to come up with a spec on the > > RepositoryFormat wiki page. I don’t see that on the RepositoryFormat > > wiki page yet. > > I wrote a couple of sketches of possible ideas here: > > https://wiki.debian.org/SuitesAndReposExtension#Possible_solutions > > FYI the repository format page has moved here: > > https://wiki.debian.org/DebianRepository/Format > > > Is there any way to help? > > Help on this is very much welcome as I don't have much time for it. > Go through as many Debian services as possible, look for hard-coding of > suites, codenames, architectures, compression formats etc and add it to > the SuitesAndReposExtension wiki page and send patches to reduce > hard-coding by getting architecture info from the archive or > suites information from the ftp-master API. > > https://api.ftp-master.debian.org/list_paths > > > I’m also interested in this issue due to hardcoding in manpages.d.o, > > which I’ve now described on > > https://wiki.debian.org/SuitesAndReposExtension#manpages.debian.org > > Thanks for that. > > -- > bye, > pabs > > https://wiki.debian.org/PaulWise > -- Best regards, Michael
