Package: lsb-release
Version: 4.1+devuan2
Severity: normal
Dear Maintainer,
-- Package-specific info:
lsb_release output
-*- -*- -*- -*- -*-
Distributor ID: Devuan
Description: Devuan GNU/Linux testing/unstable
Release: testing/unstable
Codename: n/a
-*- -*- -*- -*- -*-
Apt policy
-*- -*- -*- -*- -*-
Package files:
100 /var/lib/dpkg/status
release a=now
500 https://download.docker.com/linux/debian stretch/edge amd64 Packages
release o=Docker,a=stretch,l=Docker CE,c=edge,b=amd64
origin download.docker.com
100 http://deb.devuan.org/devuan experimental/main amd64 Packages
release
v=1.0.0,o=Devuan,a=experimental,n=experimental,l=Master,c=main,b=amd64
origin deb.devuan.org
100 http://deb.devuan.org/devuan ascii-proposed/main amd64 Packages
release v=2.0.0,o=None,a=ascii-proposed,n=None,l=None,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
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/main amd64 Packages
release
v=2.0,a=testing-security,n=ascii-security,l=Devuan-Security,c=main,b=amd64
origin deb.devuan.org
Pinned packages:
-*- -*- -*- -*- -*-
sources.list
-*- -*- -*- -*- -*-
deb http://deb.devuan.org/merged/ ascii-security main
deb http://deb.devuan.org/merged/ ascii-updates main
deb http://deb.devuan.org/merged/ ascii main
-*- -*- -*- -*- -*-
/etc/lsb_release
-*- -*- -*- -*- -*-
- none
The lsb_release -c invocation yields results that are dependent on one's
APT sources.list. Absence of the Origin: field in some of the Devuan
package repository mirrors means that on some systems people see `n/a`
as the codename. When switching mirrors *and without changing installed
packages*, the output suddenly becomes `ascii`.
# I have only tested this on ascii systems.
I have submitted an issue against the mirrors psuedo-package to get the
Origin: field added, but all the same, I think that lsb_release should
not consult whatever happens to be in the systems /var/lib/apt/lists/
directory as that may have next to no bearing on what is actually
installed when the command is issued.
Inspection of /usr/share/pyshared/lsb_release.py strongly hints that
this behaviour is Devuan specific. I don't know if it is and, if so,
why it got in but I think it should be removed.
See also
https://lists.dyne.org/lurker/message/20180420.115057.d298af7b.en.html
-- System Information:
Distributor ID: Devuan
Description: Devuan GNU/Linux testing/unstable
Release: testing/unstable
Codename: n/a
Architecture: x86_64
Kernel: Linux 4.9.0-6-amd64 (SMP w/2 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages lsb-release depends on:
ii python 2.7.13-2
Versions of packages lsb-release recommends:
ii apt 1.4.8
Versions of packages lsb-release suggests:
pn lsb <none>
-- no debconf information
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
