Bug#761348: ftp.debian.org: need machine-readable metadata about suites & repositories

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 wrote: > On Fri, 2017-04-21 at 09:28 +0200, Michael Stapelberg wrote: > > > pabs, what’s the

Bug#761348: ftp.debian.org: need machine-readable metadata about suites & repositories

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 >

Bug#761348: ftp.debian.org: need machine-readable metadata about suites & repositories

Hi, On Fri, 2017-04-21 at 09:28 +0200, Michael Stapelberg wrote: > pabs, what’s the current status on this? 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. > > Is there any way to help? > >

Bug#761348: ftp.debian.org: need machine-readable metadata about suites & repositories

Hey, pabs, what’s the current status on this? 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. Is there any way to help? I’m also interested in this issue due to hardcoding in manpages.d.o, which

Bug#761348: ftp.debian.org: need machine-readable metadata about suites repositories

Hi! On Sat, 2014-09-13 at 15:24:58 +0800, Paul Wise wrote: Package: ftp.debian.org Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org Various places in Debian infrastructure (QA especially) hard-code aspects of the Debian archive (suite, code, component, arch names etc). This

Bug#761348: ftp.debian.org: need machine-readable metadata about suites repositories

On Mon, 2014-09-15 at 08:31 +0800, Paul Wise wrote: Tagged the bug moreinfo, over the next months I will look at existing hardcoding, consult with service maintainers and try to come up with a spec on the RepositoryFormat page about what data is needed. ftp-masters seem to be open to the idea

Bug#761348: ftp.debian.org: need machine-readable metadata about suites repositories

On Wed, 17 Sep 2014, Paul Wise wrote: ftp-masters seem to be open to the idea but want a spec for what data needs to be exported where. I would like to invite service maintainers and maintainers of derivative distros to document what info they hard-code from the Debian archive and their

Bug#761348: ftp.debian.org: need machine-readable metadata about suites repositories

On 13700 March 1977, Paul Wise wrote: If we export it archive side it (IMO) ends up on the mirror, so we can either just sign it with the archive keys and put the sig beside it, or have the files listed in Release files. I prefer Release files. The problem is the files I propose are one file

Bug#761348: ftp.debian.org: need machine-readable metadata about suites repositories

Hi Paul, On Samstag, 13. September 2014, Paul Wise wrote: Various places in Debian infrastructure (QA especially) hard-code aspects of the Debian archive (suite, code, component, arch names etc). This is a problem because after new suites or architectures are added, we have lots of places

Bug#761348: ftp.debian.org: need machine-readable metadata about suites repositories

[Drop the bug since it seems OT there] On Sun, Sep 14, 2014 at 9:02 PM, Holger Levsen wrote: we have the python-distro-info package which at least holds some of that info. how/where would you see that in your picture? That has the same problem; it hardcodes information about the archive in a

Bug#761348: ftp.debian.org: need machine-readable metadata about suites repositories

On Sat, Sep 13, 2014 at 03:24:58PM +0800, Paul Wise wrote: Various places in Debian infrastructure (QA especially) hard-code aspects of the Debian archive (suite, code, component, arch names etc). This is a problem because after new suites or architectures are added, we have lots of places

Bug#761348: ftp.debian.org: need machine-readable metadata about suites repositories

Generated on a per-repository basis so that consumers get the data they are interested in. Here I mean one for ftp.d.o/debian and one for each of the archive.d.o/* repositories. I'm confused about this. We have several additional archives ATM, for instance security and lts. lts is not a

Bug#761348: ftp.debian.org: need machine-readable metadata about suites repositories

On 13698 March 1977, Paul Wise wrote: Various places in Debian infrastructure (QA especially) hard-code aspects of the Debian archive (suite, code, component, arch names etc). This is a problem because after new suites or architectures are added, we have lots of places that need to be

Bug#761348: ftp.debian.org: need machine-readable metadata about suites repositories

2014-09-14 15:08 GMT+02:00 Paul Wise p...@debian.org: [Drop the bug since it seems OT there] On Sun, Sep 14, 2014 at 9:02 PM, Holger Levsen wrote: we have the python-distro-info package which at least holds some of that info. how/where would you see that in your picture? That has the

Bug#761348: ftp.debian.org: need machine-readable metadata about suites repositories

On Sun, 2014-09-14 at 18:12 +0200, Stefano Zacchiroli wrote: I'm confused about this. We have several additional archives ATM, for instance security and lts. Does the above mean that the maintainer of an infrastructure piece that spans multiple archives will have to separately retrieve the

Bug#761348: ftp.debian.org: need machine-readable metadata about suites repositories

Control: tags -1 + moreinfo Glad to have a positive response from ftpmaster, thanks! On Sun, 2014-09-14 at 22:15 +0200, Joerg Jaspert wrote: If we export it archive side it (IMO) ends up on the mirror, so we can either just sign it with the archive keys and put the sig beside it, or have the

Bug#761348: ftp.debian.org: need machine-readable metadata about suites repositories

Package: ftp.debian.org Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org Various places in Debian infrastructure (QA especially) hard-code aspects of the Debian archive (suite, code, component, arch names etc). This is a problem because after new suites or architectures are added,