Devuan bug report logs - #363
lsb-release: breakiing critical non standar output for LSB release and codename

version graph

Package: lsb-release; Maintainer for lsb-release is Franco Lanza <nextime@devuan.org>; Source for lsb-release is src:lsb-release-minimal.

Reported by: PICCORO McKAY Lenz <mckaygerhard@gmail.com>

Date: Tue, 14 Jan 2020 13:05:13 UTC

Severity: normal

Found in version 4.1+devuan2

Done: "Ralph Ronnquist (rrq)" <ralph.ronnquist@gmail.com>

Full log


🔗 View this message in rfc822 format

MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
X-Loop: owner@bugs.devuan.org
From: "Devuan bug Tracking System" <owner@bugs.devuan.org>
To: "Ralph Ronnquist (rrq)" <ralph.ronnquist@gmail.com>
Subject: bug#363: marked as done (lsb-release: breakiing critical non
 standar output for LSB release and codename)
Message-ID: <handler.363.D363.157930260310790.ackdone@bugs.devuan.org>
References: <ec16dfef-1b6f-6135-337f-465aeb418640@gmail.com>
 <CALci+FQFqJbT8W3oZa3Xzh6hcvMbaqya4Gxah==KNNjHVCS6dw@mail.gmail.com>
X-Devuan-PR-Message: closed 363
X-Devuan-PR-Package: lsb-release
Reply-To: 363@bugs.devuan.org
Date: Fri, 17 Jan 2020 23:18:02 +0000
Content-Type: multipart/mixed; boundary="----------=_1579303082-10809-0"
[Message part 1 (text/plain, inline)]
Your message dated Sat, 18 Jan 2020 10:05:38 +1100
with message-id <ec16dfef-1b6f-6135-337f-465aeb418640@gmail.com>
and subject line appears to be fixed
has caused the Devuan bug report #363,
regarding lsb-release: breakiing critical non standar output for LSB release and codename
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.devuan.org
immediately.)


-- 
363: bugs.devuan.org//cgi/bugreport.cgi?bug=363
Devuan Bug Tracking System
Contact owner@bugs.devuan.org with problems
[Message part 2 (message/rfc822, inline)]
From: PICCORO McKAY Lenz <mckaygerhard@gmail.com>
To: Devuan Bug Tracking System <submit@bugs.devuan.org>
Subject: lsb-release: breakiing critical non standar output for LSB release and codename
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
[Message part 3 (message/rfc822, inline)]
From: "Ralph Ronnquist (rrq)" <ralph.ronnquist@gmail.com>
To: 363-done@bugs.devuan.org
Subject: appears to be fixed
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.

Send a report that this bug log contains spam.


Devuan BTS -- Powered by Debian bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.

Devuan Bugs Owner <owner@bugs.devuan.org>.
Last modified: Fri Apr 26 04:03:51 2024;