Bug 845695

Summary: lsb_release shows no usefull results
Product: [openSUSE] openSUSE Tumbleweed Reporter: Thomas Zimmermann <bugs>
Component: BasesystemAssignee: E-mail List <bnc-team-screening>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: forgotten_DV81ZEWZkN
Version: 13.1 Beta 1   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Thomas Zimmermann 2013-10-14 07:30:35 UTC 
User-Agent:       Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Firefox/24.0

lsb_release seems to not be able to parse comments in /etc/SuSE-release properly and therefore shows invalid results, because a deprecation comment was added this file.

Reproducible: Always

Steps to Reproduce:
1. run lsb_release -a on 13.1

Actual Results:  
$ lsb_release -a
LSB Version:    n/a
Distributor ID: #/etc/SuSE-releaseisdeprecatedandwillberemovedinthefuture,use/etc/os-releaseinstead
Description:    # /etc/SuSE-release is deprecated and will be removed in the future, use /etc/os-release instead
Release:        n/a
Codename:       n/a


Expected Results:  
$ lsb_release -a
LSB Version:    core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-ia32:core-3.2-ia32:core-4.0-ia32:desktop-4.0-ia32:desktop-4.0-noarch:graphics-2.0-ia32:graphics-2.0-noarch:graphics-3.2-ia32:graphics-3.2-noarch:graphics-4.0-ia32:graphics-4.0-noarch
Distributor ID: SUSE LINUX
Description:    openSUSE 13.1 (i586)
Release:        13.1
Codename:       Bottle
Comment 1 Thomas Zimmermann 2013-10-14 08:01:39 UTC 
lsb-release expects the first line to be the Distribution description:

Line 198: TMP_DISTRIB_DESC=$(head -n 1 $FILENAME 2>/dev/null)

And if the distribution desc is invalid all other fields are not filled.

So either the depration comment has to be removed or one has to change the lsb-release script to ignore comments.
Comment 2 Forgotten User DV81ZEWZkN 2013-10-14 23:51:59 UTC 
Dup of bug 845262

*** This bug has been marked as a duplicate of bug 845262 ***