You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Minimal information detected when lsb-release isn't installed #152
Sorry, I hadn't included the expected output. I think the codename should indeed be stretch/sid, or just stretch as seems to be the case on some systems.
Unfortunately, this seems to be something that will have to be addressed as part of #109.
In debian 8, the codename appeared in parentheses and in stretch, it isn't. That's inconsistent with almost all distributions. It's also rather sad that they're not providing the version anymore.
The information from when this ticket was created was when stretch was not yet a released version. Debian in this case chose to not fill out the release information. It is filed out now that it is released however \o/
Activity
nir0s commentedon Jan 12, 2017
@lenormf I assume you mean that you would expect to see "stretch/sid" in the codename?
lenormf commentedon Jan 12, 2017
Sorry, I hadn't included the expected output. I think the
codenameshould indeed bestretch/sid, or juststretchas seems to be the case on some systems.nir0s commentedon Jan 15, 2017
Unfortunately, this seems to be something that will have to be addressed as part of #109.
In debian 8, the codename appeared in parentheses and in stretch, it isn't. That's inconsistent with almost all distributions. It's also rather sad that they're not providing the version anymore.
I will start working on a distro inconsistencies framework soon, at which point i'll address this as well.
asottile commentedon Dec 3, 2017
fwiw, the latest
stretchdocker image has an os-release file that looks like this:and these look roughly correct:
nir0s commentedon Dec 30, 2017
I'm confused. In Docker it's different? :)
asottile commentedon Dec 30, 2017
The information from when this ticket was created was when stretch was not yet a released version. Debian in this case chose to not fill out the release information. It is filed out now that it is released however \o/
sethmlarson commentedon Dec 31, 2017
So can this be closed?
asottile commentedon Dec 31, 2017
I believe so, yes