Cannot determine OS detailed information on not LSB-compliant Linux systems

[Daeron]

If a Linux system, eg. Gentoo, is not LSB-compliant, and thus doesn't contain a lsb_release -command, a lot of useless stack traces are printed because josm tries to get the version of the system by calling it.

As it doesn't affect the operation of josm at all, this stack trace is completely useless.

Attached patch removes printing of the stack trace.

[Don-vip]

This is not totally useless as it points out we need to implement something else for Gentoo. What is the equivalent command ?

[Don-vip]

Funny, some people seem to have lsb_release on Gentoo:

O          6 ( 0.2%) Linux Gentoo Base System release 2.1
O          1 ( 0.0%) Linux Gentoo Base System release 2.2

[Don-vip]

Can you please post the contents of your /etc/*-release file(s) ? Thanks.

[Daeron]

Replying to Don-vip:

Can you please post the contents of your /etc/*-release file(s) ? Thanks.

$ ls /etc/*-release
/etc/gentoo-release
$ cat /etc/gentoo-release
Gentoo Base System release 2.1

That version is essentially the version of the ​baselayout package.

There exists also a package for ​lsb_release, but AFAIK no package depends on it, so most Gentoo users won't have it installed.

See also: ​https://bugs.gentoo.org/show_bug.cgi?id=107162

[Don-vip]

Ok thanks, I commit something right now, tell me if it works :)

[Don-vip]

In 5877/josm:

see #8616 - Attempt to determine OS detailed version on some non LSB-compliant Linux systems

[Don-vip]

(it's working if in your status report, the line starting with "Identification" contains "Gentoo")

[Don-vip]

Dirk, ​this change you've made won't work, it's caused by what I did in this ticket. Looks like Gentoo uses two different formats for the very same file, that's a shame !

[stoecker]

Why it won't work? We get proper NAME=Gentoo entries from lsb_release call (a bug I assume). This change strips "NAME=" from it.

[stoecker]

And no, we got these also before this change.

[Don-vip]

It will work if it comes from lsb_release, but not if it comes from a direct read of /etc/gentoo-release

If it contains NAME=Gentoo, then the file must probably be parsed the same way as /etc/os-release

[stoecker]

I now again get "" encapsulated strings. Probably the ""replace needs to be added for your workaround system detection as well.

[stoecker]

In 5885/josm:

fix quoted texts (fix #8616)

[Don-vip]

Thanks, it effectively fixes this problem with quoted strings.
I still need to make other changes to handle the case of "NAME=XXX" to parse the file correctly.

[stoecker]

I still need to make other changes to handle the case of "NAME=XXX" to parse the file correctly.

As said, these were there before your changes, so it can't be related.

[Don-vip]

Mmmm ok let's see if I'm wrong :)