Unix & Linux Stack Exchange
Q&A for users of Linux, FreeBSD and other Unix-like operating systems
Latest Questions
1
votes
0
answers
87
views
Why has the October 2023 release of the Arch Linux ISO been delayed?
Here are the releases of Arch Linux in the last months before this month: - `2023-05-03` - `2023-06-01` - `2023-07-01` - `2023-08-01` - `2023-09-01` As we can see, ISO releases were published on the first day of each month, or a few days later. But for the last release, it took 2 weeks and it was pu...
Here are the releases of Arch Linux in the last months before this month:
-
2023-05-03
- 2023-06-01
- 2023-07-01
- 2023-08-01
- 2023-09-01
As we can see, ISO releases were published on the first day of each month, or a few days later.
But for the last release, it took 2 weeks and it was published in October 14th: 2023-10-14
What caused the delay of this particular release?
Source: https://archlinux.org/releng/releases/
A.L
(1834 rep)
Oct 24, 2023, 10:05 PM
• Last activity: Oct 24, 2023, 10:30 PM
13
votes
2
answers
7562
views
How to determine which Ubuntu flavor I'm on?
I am on Xubuntu (16.04, btw) however `lsb_release -a` gives me: user@host:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial Should it display `Xubuntu`, or is this legit output? And if it is, how can I (by the CLI)...
I am on Xubuntu (16.04, btw) however
lsb_release -a
gives me:
user@host:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial
Should it display Xubuntu
, or is this legit output?
And if it is, how can I (by the CLI) know the exact Ubuntu distro I'm on?
And what does the warning No LSB modules are available.
mean anyway?
(It is output to *stderr*:
user@host:~$ lsb_release -a >/dev/null
No LSB modules are available.
so I'm guessing in nominal case it shouldn't be there)
joH1
(948 rep)
Aug 8, 2017, 06:59 PM
• Last activity: Sep 19, 2023, 03:44 AM
9
votes
3
answers
21163
views
Remove "No LSB modules are available." message from 'lsb_release -a'
I try to write a script to get the version of my distro so that I can pass it to a variable. The following command is what I wrote to achieve the result. ``` lsb_release -ar | grep -i release | cut -s -f2 ``` The unwanted output: ``` No LSB modules are available. 18.04 ``` As you can see, the `No LS...
I try to write a script to get the version of my distro so that I can pass it to a variable.
The following command is what I wrote to achieve the result.
lsb_release -ar | grep -i release | cut -s -f2
The unwanted output:
No LSB modules are available.
18.04
As you can see, the No LSB modules are available
message is the unwanted part.
Since I prefer my script to be portable across servers, I don't want to install any extra packages beside utilizing the lsb_release -a
command.
vincent pham
(311 rep)
Jan 7, 2020, 12:33 AM
• Last activity: Jun 9, 2023, 05:09 PM
23
votes
12
answers
32054
views
How to get the Debian codename without lsb_release
I am trying to create a script that requires me to print the Debian codename so that I may echo it into the `sources.list` file. I am trying to make this script work across any version of Debian, so I had hoped to set a bash variable of the release codename. This would be simple to do with `lsb_rele...
I am trying to create a script that requires me to print the Debian codename so that I may echo it into the
sources.list
file.
I am trying to make this script work across any version of Debian, so I had hoped to set a bash variable of the release codename.
This would be simple to do with lsb_release -c
.
However, our deployment images do not contain lsb_release
by default - and with this script being required to fix the sources.list
, installing lsb-release
with apt-get
would not be an option.
I have found numerous ways to get the release number and other info about the system, but cannot find a reliable place to get the codename.
(I am testing this with Debian Squeeze.)
Woody
(231 rep)
Jan 24, 2015, 03:01 AM
• Last activity: Nov 22, 2022, 04:17 PM
0
votes
0
answers
1664
views
Manjaro lsb-release set to Arch (lsb-release: /etc/lsb-release exists in filesystem)
I tried upgrading my packages with `pacman -Syu` and got an error message. ``` error: failed to commit transaction (conflicting files) lsb-release: /etc/lsb-release exists in filesystem (owned by manjaro-release) Errors occurred, no packages were upgraded. ``` So I thought I could try backing up the...
I tried upgrading my packages with
pacman -Syu
and got an error message.
error: failed to commit transaction (conflicting files)
lsb-release: /etc/lsb-release exists in filesystem (owned by manjaro-release)
Errors occurred, no packages were upgraded.
So I thought I could try backing up the /etc/lsb-release
file (with another name) so maybe the conflict would be resolved after doing another upgrade.
Although running pacman -Syu
again now succeeds without errors, the /etc/lsb-release
file contains the following:
LSB_VERSION=1.4
DISTRIB_ID=Arch
DISTRIB_RELEASE=rolling
DISTRIB_DESCRIPTION="Arch Linux"
While it used to contain:
DISTRIB_ID=ManjaroLinux
DISTRIB_RELEASE=21.1.6
DISTRIB_CODENAME=Pahvo
DISTRIB_DESCRIPTION="Manjaro Linux"
So my system is now recognizing Arch as its distribution which is not right. Is it possible to reverse this action and what did I do wrong?
axtck
(101 rep)
Nov 17, 2021, 05:58 PM
• Last activity: Nov 17, 2021, 06:06 PM
3
votes
2
answers
2787
views
Why lsb_release -c command , returns n/a?
recently I switched from **zorin os** to **deepin 20** for it's outstanding UI and eases of use for daily operations. it's almost OK but if I need some newer packages which are not listed in official deepin repositories, I have to use some community installer scripts that rely on this command to obt...
recently I switched from **zorin os** to **deepin 20** for it's outstanding UI and eases of use for daily operations.
it's almost OK but if I need some newer packages which are not listed in official deepin repositories, I have to use some community installer scripts that rely on this command to obtain the correct linux LSB version :
-c
the problem is : **the return value is "n/a"** that consequently, breaks down the installation process. how can I fix this ?
smbanaei
(141 rep)
Aug 8, 2020, 06:06 PM
• Last activity: Apr 15, 2021, 05:26 AM
0
votes
1
answers
1448
views
circular dependency between lsb-release and python3 (ubuntu 18.04)
I've managed to get into a situation where I have a circular dependency between lsb-release and python3. When I try to `sudo apt install python3 --reinstall` I get the following (just pasting the key lines) (Reading database ... 470097 files and directories currently installed.) Preparing to unpack...
I've managed to get into a situation where I have a circular dependency between lsb-release and python3. When I try to
sudo apt install python3 --reinstall
I get the following (just pasting the key lines)
(Reading database ... 470097 files and directories currently installed.)
Preparing to unpack .../python3_3.6.7-1~18.04_amd64.deb ...
Could not find platform independent libraries
Could not find platform dependent libraries
Consider setting $PYTHONHOME to [:]
Fatal Python error: Py_Initialize: Unable to get the locale encoding
ModuleNotFoundError: No module named 'encodings'
[~] lsb_release
Could not find platform independent libraries
Could not find platform dependent libraries
Consider setting $PYTHONHOME to [:]
Fatal Python error: Py_Initialize: Unable to get the locale encoding
ModuleNotFoundError: No module named 'encodings'
Current thread 0x00007fa905a81740 (most recent call first):
Aborted (core dumped)
Clearly my lsb_release is broken. But if I run sudo apt-get install lsb-release
I get
dpkg: error processing package python3 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
dpkg: dependency problems prevent configuration of lsb-release:
lsb-release depends on python3:any (>= 3.4~); however:
Package python3 is not configured yet.
So I can't fix my python3 installation without fixing lsb-release, and vice versa.
GTK
(125 rep)
Apr 15, 2019, 02:31 AM
• Last activity: Apr 15, 2019, 07:38 AM
2
votes
1
answers
8158
views
Check Armbian version on the command line
I have an *Orangepi+2e* device with Armbian OS. How can I check Armbian version? I tried with these commands, but can not found Armbian type. $ sudo lsb_release -a Out: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.2 LTS Release: 16.04 Codename: xenial and $ sudo una...
I have an *Orangepi+2e* device with Armbian OS.
How can I check Armbian version?
I tried with these commands, but can not found Armbian type.
$ sudo lsb_release -a
Out:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.2 LTS
Release: 16.04
Codename: xenial
and
$ sudo uname -r
Out:
Linux orangepiplus2e 3.4.113-sun8i #16 SMP PREEMPT Tue Jun 13 14:15:57 CEST 2017 armv7l armv7l armv7l GNU/Linux
Benyamin Jafari
(237 rep)
Jun 20, 2018, 05:42 AM
• Last activity: Jan 7, 2019, 06:55 AM
1
votes
3
answers
1542
views
Can't compare lsb_release result to string in Bash
I'm doing something wrong on the string comparison below. It works if I set a variable and compare that, but I can't copy the value to a string. Does anyone know what's wrong? $ if [ "$(lsb_release -i)" = "Distributor ID: RedHatEnterpriseClient" ]; then echo yes; else echo no; fi no $ lsb_release -i...
I'm doing something wrong on the string comparison below. It works if I set a variable and compare that, but I can't copy the value to a string. Does anyone know what's wrong?
$ if [ "$(lsb_release -i)" = "Distributor ID: RedHatEnterpriseClient" ]; then echo yes; else echo no; fi
no
$ lsb_release -i
Distributor ID: RedHatEnterpriseClient
$ var="$(lsb_release -i)"
$ if [ "$(lsb_release -i)" = "$var" ]; then echo yes; else echo no; fi
yes
Aido
(164 rep)
Jul 6, 2017, 02:15 PM
• Last activity: Jul 6, 2017, 03:50 PM
0
votes
1
answers
134
views
What is the differences between distributions, the OS and code names (stable, testing) in linux and what order is that listed in /etc/*release?
Overall, I'm trying to understand the differences between distributions, Operating systems and release code names (stable, experimental, testing) for Linux and how can those are listed in release files. I know some are based on toy story characters and I'm using Ubuntu but I'm not sure as to what th...
Overall, I'm trying to understand the differences between distributions, Operating systems and release code names (stable, experimental, testing) for Linux and how can those are listed in release files. I know some are based on toy story characters and I'm using Ubuntu but I'm not sure as to what the different names mean. Not where to look for them. When I run lsb_release it says ubuntu 14.04.3 but if cat /etc/debian_version it says jessie/sid.
ubercoo
(1 rep)
Feb 28, 2016, 04:36 PM
• Last activity: Feb 28, 2016, 05:41 PM
1
votes
1
answers
193
views
why lsb_release looks slower than a program supposed to print few bytes?
i'm just wondering why in all linux boxs , lsb_release take longer time to print few infos about distro, anyone could enlighten me about this fact ? please.
i'm just wondering why in all linux boxs , lsb_release take longer time to print few infos about distro,
anyone could enlighten me about this fact ? please.
Yunus
(1732 rep)
Jan 11, 2016, 01:14 PM
• Last activity: Jan 12, 2016, 12:00 AM
Showing page 1 of 11 total questions