Command 'lsb_release -a' returned non-zero exit status 1 #260
Labels
Milestone
Comments
|
I can confirm this observation. This also happens in OBS builds, where there is no |
|
Actually fixed in #260, and released as v1.6.0, closing here. |
yphus
added a commit
to yphus/monorepo-sandbox
that referenced
this issue
Aug 31, 2022
yphus
added a commit
to canonical/checkbox
that referenced
this issue
Jun 29, 2023
… on s16/18 python3-distro was broken until the 1.6 release. See python-distro/distro#260
yphus
added a commit
to canonical/checkbox
that referenced
this issue
Jun 29, 2023
… on s16/18 python3-distro was broken until the 1.6 release. See python-distro/distro#260
mz2
pushed a commit
to canonical/checkbox
that referenced
this issue
Jun 29, 2023
… on s16/18 (#590) python3-distro was broken until the 1.6 release. See python-distro/distro#260
diohe0311
pushed a commit
to canonical/checkbox
that referenced
this issue
Jul 18, 2023
… on s16/18 (#590) python3-distro was broken until the 1.6 release. See python-distro/distro#260
diohe0311
pushed a commit
to canonical/checkbox
that referenced
this issue
Jul 31, 2023
… on s16/18 (#590) python3-distro was broken until the 1.6 release. See python-distro/distro#260
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
I have encountered an issue in a Linux server where the
lsb_releasecommand is broken.I have researched a bit and it seems that it might happen on some ubuntu distributions (maybe also on others).
I think that this should be handled properly by ignoring errors on
lsb_releaseexecution.I will submit a PR for a fix.
The text was updated successfully, but these errors were encountered: