Op Mon, 14 Dec 2015 10:52:46 +0100 schreef Simon Josefsson <si...@josefsson.org>:
> Perhaps a first step towards fixing this is to get visibility on which > packages are involved, and what their status is. How about an > automatically generated web page that list all packages that differ > between gNS and Debian? It could contain version number of the > package version in Debian, and in gNS, and pointers to the respective > repositories. If the version in gNS is lagging behind, the package > could be marked in red and float to the top, so that people can easily > find and start to work on fixing that package. There's a wiki page [1] that gives an overview of modified packages. > A similar automatically generated page to track all packages would be > useful, so users can see which packages has been receiving security > fixes in Debian that haven't yet been merged into gNS. I'm currently > a bit hesistant about running gNS because I don't know how well it > tracks all security fixes in Debian. I haven't looked at packages.debian.org's setup yet. I suppose such a comparison feature can be added to that software. gNewSense lags no more than 24 h for unmodified packages. Modified packages are updated manually and can take longer. If mostly the differences are interesting, then maybe packages.gnewsense.org is not the right tool for that job. [1] http://www.gnewsense.org/Documentation/3/DifferencesWithDebian _______________________________________________ gNewSense-dev mailing list gNewSense-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/gnewsense-dev
