Hi, wirelessd...@gmail.com writes:
> [... in follow-up to a nodejs related question ...] > > Unfortunately those instructions rely on lsb_release providing the > correct output. There is a bug with lsb-release in ascii where it > relies on parsing sources.list for detection. If “lsb_release -sc” > returns “ascii” then you’re all fine but if it returns “testing” > then you’ll just have to add the repo with the manual instructions. Which reminded me of a discussion that happened here on the list and led me to file http://bugs.devuan.org//cgi/bugreport.cgi?bug=199 against the "mirrors" pseudo-package. In my case, `lsb_release -cs` yields 'n/a'. There may or may not be an issue with lsb_release itself but there is definitely an issue with the *_InRelease files for some of the package repositories. Is anyone looking at this? Hope this helps, -- Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Software https://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
