Adding support for testing/unstable debian

[JimKirk1]

I was able to get the script to run by commenting out the section for the os check but it does have some issues. I was wondering if there would be an update for bullseye so that I could run this automated thanks :+1:

[V33m]

For Bullseye to be supported, a developer has to test and run the script. You could do apt-pinning which I've done for some years, but it won't help if you want to use Bullseye alone. Give me the following information by running each line:

lsb_release -sd
lsb_release -si
lsb_release -sr | cut -d. -f1
grep -oP '(?<=^ID=).+' /etc/os-release | tr -d '"'
grep -oP '(?<=^VERSION_ID=).+' /etc/os-release | tr -d '"'

• Which php version is being used with Bullseye? Ubuntu 20 uses 7.4.
• Which libc version? Ubuntu 20 uses libcurl4.

[JimKirk1]

lsb_release -sd Debian GNU/Linux bullseye/sid lsb_release -si Debian

lsb_release -sr | cut -d. -f1 testing damiendadog@damien:~$ grep -oP '(?<=^VERSION_ID=).+' /etc/os-release | tr -d '"' damiendadog@damien:~$ grep -oP '(?<=^ID=).+' /etc/os-release | tr -d '"' debian

PHP 7.4 Libcurl is 4 LIbc is 2.31

On Mon, Nov 9, 2020 at 3:51 AM V33m notifications@github.com wrote:

For Bullseye to be supported, a developer has to test and run the script. You could do apt-pinning which I've done for some years, but it won't help if you want to use Bullseye alone. Give me the following information by running each line:

lsb_release -sd lsb_release -si lsb_release -sr | cut -d. -f1 grep -oP '(?<=^ID=).+' /etc/os-release | tr -d '"' grep -oP '(?<=^VERSION_ID=).+' /etc/os-release | tr -d '"'

• Which php version is being used with Bullseye? Ubuntu 20 uses 7.4.
• Which libc version? Ubuntu 20 uses libcurl4.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/arakasi72/rtinst/issues/542#issuecomment-723865632, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMFDUVB2GRJQXZ6VNV3KYQTSO6UPJANCNFSM4TO2XZFA .

[V33m]

So the issue lies in the distribution specific information and the release number as the command lsb_release -sr | cut -d. -f1 shows testing while it should be a number, 11 to be exact for Debian Bullseye. rtinst has support for Debian Bullseye when the distribution specific information displays the correct release number, and not testing. You can either modify the release number of the distribution manually or consult with the providers of the OS. At least Debian Bullseye is supported when the distribution specific information is correct.