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 per apt repo (because > they list all suites) not one per suite, so it doesn't make much sense > to list them in the per-suite Release files.
Ok. >> archive.d.o is no longer in any database. So for all of those we have to >> write them once by hand. If we have them exported from dak in the >> future, all future archivals will automatically have them. > Hmm, ok. Of course if its not by-suite but archive, then we need to ensure it goes to archive too. Makes archiving a bit more complicated, as it will mean a change of the file there plus a resign, but luckily we don't do it that often. >> > Be named Suites (in the dists dir) & Repositories (on ftp-master). >> Or just one file that lists em all? >> Though I think it depends what all goes into. > I think I would prefer the per-repo solution so that this can be adopted > in more places than just Debian, I would like reprepro and other tools > used by derivatives to automatically generate these files. Sure. One file "repodata" (or however) in the root of the archive, with a sig beside it. > 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. Good. When done ensure we really get the ping you are ready, its easy to miss a simple tag removal of moreinfo. -- bye, Joerg Mal verlierst Du und mal gewinnen die anderen: Immer im Wechsel! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
