Hi, wirelessd...@gmail.com writes:
>> On 17 Apr 2018, at 06:34, aitor_czr <aitor_...@gnuinos.org> wrote: >> >> The output of 'lsb_release -a' is defined in the 'base-files' package. So, >> for the same version of the package, you should get the same output. The >> command needs the 'lsb-base' package to work, i think. > > I just checked and both machines have both packages installed at the same > version. > > base-files: 9.9+devuan2.3 > lsb-base: 4.1+devuan2 > > I noticed this problem was occurring when I added Devuan support to the > official nodejs installer script which relies on output of “lsb_release -c > -s”. > > Running that command on the devuan2 machine will return “ascii” while running > it on devuan1 returns “n/a”. I get the same 'n/a' with the same versions of base-files and lsb-base. FTR, lsb-release has the same version as lsb-base. I've been poking around in the Python source code for the lsb_release command and noticed a code path that sources the output of apt-cache policy and looks for entries that have a label of Devuan, component of main and origin of Devuan (or an alternative that mentions packages.devuan.org and Devuan Ports). My `apt-cache policy` output does not match any of that so I *think* that's why I get an 'n/a' for the codename. # The code is a bit hard to follow which is why I am not sure :-/ Any chance the `apt-cache policy` output on your machines is different in a way that would explain the behaviour you see? 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
