Subject: bug#363 closed by "Ralph Ronnquist (rrq)" <[email-masked]> (appears to be fixed)

From: "Devuan bug Tracking System" <[email-masked]>
Date: Fri, 17 Jan 2020 23:18:06 +0000

This is an automatic notification regarding your bug report
which was filed against the lsb-release package:

#363: lsb-release: breakiing critical non standar output for LSB release and codename

It has been closed by "Ralph Ronnquist (rrq)" <[email-masked]>.

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact "Ralph Ronnquist (rrq)" <[email-masked]> by
replying to this email.

-- 
363: bugs.devuan.org//cgi/bugreport.cgi?bug=363
Devuan Bug Tracking System
Contact [email-masked] with problems

Subject: appears to be fixed
From: "Ralph Ronnquist (rrq)" <[email-masked]>
To: [email-masked]
Date: Sat, 18 Jan 2020 10:05:38 +1100

This would have been an amprolla bug rather; the release code (2.1) is obtained 
by referring to the "apt-cache policy" output which derives the release version 
from the downloaded distribution. This ultimately refers the "Version" field of 
the downloaded "InRelease" file, which (now) is 2.1 for ascii, and 3.0 for beowulf.

Ralph.

Subject: lsb-release: breakiing critical non standar output for LSB release and codename
From: PICCORO McKAY Lenz <[email-masked]>
To: Devuan Bug Tracking System <[email-masked]>
Date: Tue, 26 Nov 2019 14:31:20 -0400

Package: lsb-release
Version: 4.1+devuan2
Severity: important

Dear Maintainer,

Every know what are the LSB standar so i'll not explain why this are a
important bug:

   * What led up to the situation?
insert in a script the code $(lsb_release -s -c) and does not work

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
LSB output are incorrect, for Release we have "ascii" and codename we have "n/a"
The corrected output must be "2.1" for Release and "asci" for codename

   * What was the outcome of this action?
again?

   * What outcome did you expect instead?
$(lsb_release -s -c) = asci
$(lsb_release -s -r) = 2.1

-- Package-specific info:
lsb_release output
-*- -*- -*- -*- -*-
Distributor ID:    Devuan
Description:    Devuan GNU/Linux ascii
Release:    ascii
Codename:    n/a
-*- -*- -*- -*- -*-
    Apt policy
-*- -*- -*- -*- -*-
Package files:
 100 /var/lib/dpkg/status
     release a=now
 500 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-11-19
10:51:46 UTC] ascii/non-free amd64 Packages
     release c=non-free,b=amd64
     origin Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-11-19 10:51:46 UTC
 500 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-11-19
10:51:46 UTC] ascii/main amd64 Packages
     release c=main,b=amd64
     origin Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-11-19 10:51:46 UTC
 500 cdrom://[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-11-19
10:51:46 UTC] ascii/contrib amd64 Packages
     release c=contrib,b=amd64
     origin Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-11-19 10:51:46 UTC
Pinned packages:
-*- -*- -*- -*- -*-
   sources.list
-*- -*- -*- -*- -*-
deb cdrom:[Devuan GNU/Linux 2.1 (ascii) amd64 DVD1 - 2019-11-19
10:51:46 UTC]/ ascii contrib main non-free
-*- -*- -*- -*- -*-
 /etc/lsb_release
-*- -*- -*- -*- -*-
- none

-- System Information:
Distributor ID:    Devuan
Description:    Devuan GNU/Linux ascii
Release:    ascii
Codename:    n/a

Architecture: x86_64

Kernel: Linux 4.9.0-11-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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.9

Versions of packages lsb-release suggests:
pn  lsb  <none>

-- no debconf information

Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com