On 17 April 2018 at 21:46, fsmithred <fsmith...@gmail.com> wrote:
> You can create your own /etc/lsb-release file to control the output of the
> lsb_release command.
Thanks, that looks interesting, but seems too much effort to set that
manually on every machine here. I'm not running any
puppet/chef/ansible that would handle that easily.
On 17 April 2018 at 22:17, Olaf Meeuwissen <paddy-h...@member.fsf.org> wrote:
> 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,
On the machine that returns "n/a" for "lsb-release -c -s", it has the
following apt policy:
# apt-cache policy
Package files:
100 /var/lib/dpkg/status
release a=now
500 http://deb.devuan.org/merged ascii-updates/main amd64 Packages
release v=2.0.0,a=testing-updates,n=ascii-updates,l=Devuan,c=main,b=amd64
origin deb.devuan.org
500 http://deb.devuan.org/merged ascii-security/non-free amd64 Packages
release
v=2.0,a=testing-security,n=ascii-security,l=Devuan-Security,c=non-free,b=amd64
origin deb.devuan.org
500 http://deb.devuan.org/merged ascii-security/main amd64 Packages
release
v=2.0,a=testing-security,n=ascii-security,l=Devuan-Security,c=main,b=amd64
origin deb.devuan.org
500 http://deb.devuan.org/merged ascii/main amd64 Packages
release v=2.0,a=testing,n=ascii,l=Devuan,c=main,b=amd64
origin deb.devuan.org
Pinned packages:
On the other machine that returns "ascii" for "lsb-release -c -s", it
seems to have included packages.devuan.org in there:
# apt-cache policy
Package files:
100 /var/lib/dpkg/status
release a=now
500 http://packages.devuan.org/merged ascii/non-free amd64 Packages
release v=2.0,o=Devuan,a=testing,n=ascii,l=Devuan,c=non-free,b=amd64
origin packages.devuan.org
500 http://packages.devuan.org/merged ascii/main amd64 Packages
release v=2.0,o=Devuan,a=testing,n=ascii,l=Devuan,c=main,b=amd64
origin packages.devuan.org
500 http://deb.devuan.org/merged ascii-updates/main amd64 Packages
release v=2.0.0,a=testing-updates,n=ascii-updates,l=Devuan,c=main,b=amd64
origin deb.devuan.org
500 http://deb.devuan.org/merged ascii-security/non-free amd64 Packages
release
v=2.0,a=testing-security,n=ascii-security,l=Devuan-Security,c=non-free,b=amd64
origin deb.devuan.org
500 http://deb.devuan.org/merged ascii-security/main amd64 Packages
release
v=2.0,a=testing-security,n=ascii-security,l=Devuan-Security,c=main,b=amd64
origin deb.devuan.org
500 http://deb.devuan.org/merged ascii/main amd64 Packages
release v=2.0,a=testing,n=ascii,l=Devuan,c=main,b=amd64
origin deb.devuan.org
Pinned packages:
# cat /etc/apt/sources.list
deb http://deb.devuan.org/merged/ ascii main
deb-src http://deb.devuan.org/merged/ ascii main
# ascii-security, previously known as 'volatile'
deb http://deb.devuan.org/merged/ ascii-security main non-free
deb-src http://deb.devuan.org/merged/ ascii-security main non-free
# ascii-updates, previously known as 'volatile'
deb http://deb.devuan.org/merged/ ascii-updates main non-free
deb-src http://deb.devuan.org/merged/ ascii-updates main non-free
# Devuan repositories
deb http://packages.devuan.org/merged ascii main non-free
deb-src http://packages.devuan.org/merged ascii main non-free
If I comment out the lines in /etc/apt/sources.list for
packages.devuan.org and then run "lsb-release -c -s", then it shows
"n/a". Uncommenting those lines again shows "ascii" for "lsb-release
-c -s".
--Tom
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
