Il giorno sabato 01/05/2010 16:48:58 CEST Sam Geeraerts <sam...@elmundolibre.be> ha scritto:
> Karl Goetz schreef: > > On Fri, 30 Apr 2010 11:52:56 +0200 > > al3xu5 / dotcommon <dotcom...@autistici.org> wrote: > [...] > >> so please let me suggest having a "gNS repositories reference > >> page" on the gnewsense website (better if in the main index), in > >> order to: > >> - have a list of all the sources.list entries (all components: > >> main, security, updates, backports, ...) for each gNS release > >> (deltad, > > > > deltad no longer has binary packages, so only source URIs would be > > available. > > > >> metad, ...) > > > > This will loose its public binaries a year or two after gns3 > > releases. > > So relevant for at least another two years. > > >> - have a list of all the corresponding signatures (linking the > >> pubkeys for downloading) > >> - have a changelog (maybe it could be the page history) > > the idea was just to have a centralized *reference* page with all the relevant infos about all the gNS repositories > > changelog of repositories ?? > As in the recent metad/updates change. But those changes are only > interesting when they happen, not a few months after. They get > announced on the mailing list, so I don't see a need for a changelog. no need indeed... possibly just for "historycal" reference, but no need anyway > >> so the advantage having just such one place where put all the > >> repositories related infos should be either for developers (which > >> could put here all the infos, keep them updated, and use just links > > > > Developers change the repository info in python-apt, and only i have > > access to the signing keys. > > I guess al3xu5 means developers in the broad sense, including user > support. yes, basically this is what i meant also this could be useful when a change of some repositories/keys occurs or when a key expires etc. > >> writing to the gNS mailing lists) or for users (which could quickly > >> find all the updated references they need, without asking > >> developers or writing to the gNS mailing lists) > > > > We should really fix /usr/share/doc/apt/examples/sources.list and > > cite that. ( High priority bug, since it talks about debians > > non-free repos) https://savannah.nongnu.org/bugs/index.php?29724 > > Also a bug in deltah, it seems: > https://savannah.nongnu.org/bugs/index.php?29729 > > >> to me, it seems to be a good idea but... > >> if it is not, please sorry :-) > > > > Its not a /bad/ idea, i'm just not sure duplicating the data is > > helpful. Other thoughts? i did not havetought about duplication... and i agree duplication is not good... but, excuse me if i repeat this, the idea was just to have a quick and updated place where (specially users and testers) to find all the gNS repositories related infos > I don't remember any questions about the keys (apart from when they > expired), so when we have the example sources.list I don't see a need > to put something on the wiki. you are probably right anyway, consider the above bugs and that may be novice users do not know about /usr/share/doc/apt/examples/sources.list ... > Anyone is free to do it anyway, of > course. If that happens and it turns out there's a real use for it > then we can still move it to www. ok... so (as i have time) i will try to write such a page in the wiki, hoping you all will check the infos i will put regards al3xu5 / dotcommon -- Support free software! Join FSF: http://www.fsf.org/jf?referrer=7535 ______________________________________________________________________ Public GPG/PGP key block ID: 1024D/11C70137 Fingerprint: 60F1 B550 3A95 7901 F410 D484 82E7 5377 11C7 0137 Key download: http://bitfreedom.noblogs.org/gallery/5721/dotcommon.asc [ Please, do not send my key to any keyserver! ]
signature.asc
Description: PGP signature
_______________________________________________ gNewSense-dev mailing list gNewSense-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/gnewsense-dev