On Sun, 12 Aug 2018 19:53:43 +0200 Evilham <dev...@evilham.com> wrote:
[snip] > This may be the place you reached: this now runs a web server, > leave this command running. Thanks! That's the bit that counts... [snip] > 4. Edit lib/debian-releases.mk accordingly > 5. Check if it works with devuan config, basically repeat 2. It does. [snip] > Also notice that if you want, you can just git clone my repository and > follow 2. (the commands do take "forever" :-D so do that if you trust > what I did, which maybe you should not as you may have read more about > this!). Reading is one thing, knowing what you're doing is another... > > Another interesting thing is that in 2.d I used /oldstable to test, > since that was "jessie" in both Debian and Devuan, /stable returns no > entries (which is wrong!) it may have something to do with > /data/config.json or sth like that, I'll leave that for your further > testing I've managed to get some of these pages filled with data. >(you have write permissions to that repo, so please update > that if you make progress). I have cloned it, and made a few commits. The devuan version looks devuanized: although there are some empty pages, some of them appear to be where they should be e.g. bugs for ascii-backports. > If we are going to use this, we want to merge back to Debian's repo as > much as possible to minimise long-term maintenance overhead; that > means some refactoring because, of course, this is built with a very > specific Debian-only mindset. > Ideally running this ends up being a matter of cloning upstream, > adding a config file or (some) env var(s) and that's it, i.e.: no > fiddling with Makefiles and the likes. I'd be happy to do what I can. > That may prove to be unrealistic since along with the software, there > is a bunch of data in the same repository and their workflow appears > to take advantage of that. I am certain you will know better than > me :-). > > If you need any more help, just reply (but make sure you CC me :-D). Many Thanks. Please let me know what next steps would be most helpful towards turning this into a useful tool. Perhaps the question that is uppermost in my mind is how to verify that the new database contains the correct combinations of packages, bugs and patches, i.e. is it trustworthy. Thanks again for your most helpful advice. leloft _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
