Is Helium still supported?

dbickin · 2022-07-07 20:43:28

I can never keep this stuff straight. But I think the version of Debian that Helium is based on went end of Life on July 1.

Is that the case? What horrible things are likely to happen if I keep using Helium?

I didn't like Lithium when I tried it, and was hoping to wait for Beryllium before I tried to upgrade again.

Thanks,
David

johnraff · 2022-07-08 01:02:26

Helium was based on Debian Stretch whose Debian long term support ended last month.

But if you want to continue with that release it's not impossible - a company called Freexian will provide upgrades of a selection of packages for another five years. It's supported by commercial sponsors but free to use. You'd have to add the apt line for stretch: see the instructions.

That said, what was it you didn't like about Lithium? If it was the appearance, it's quite easy to get it looking like Helium. If it was the under-the-hood mechanisms, then Beryllium is pretty much the same as Lithium in that regard. Either way, it's always best to do upgrades in steps, fixing issues as you go, rather than jump directly between two separated releases.

dbickin · 2022-07-08 04:48:26

Thanks. Good to know I have a choice.

What didn't I like about Lithium? Combination of small theming nitpicks and some underlying changes like using jgmenu and I seem to recall conky changed it config so my old changes no longer parse correctly. All quite fixable but I figured I'd wait for Beryllium to go through that hassle since Beryllium is coming real soon now... Helium still works for me.

David

johnraff · 2022-07-08 04:55:20

It's still probably a good idea to go to Lithium in between, even if you don't stay there long. Fix any issues that come up before going on to Beryllium. Of course small things like conky you can just leave till later.

DeepDayze · 2022-07-08 13:30:31

Come on in the water's great. Stretch has had a great run but it is time to move on and change is hard, but if you do run into issues in migrating to Lithium then to Beryllium there's people who can help you get thru the hurdles.

You can even just back up your data and do a clean install of Lithium then reinstall all your apps then restore your data. There's even a netinstall script to setup BL right from a minimal, clean Debian netinstall setup.

Sector11 · 2022-07-12 17:56:29

From Dedian 10 to Debian 11
I followed the links John pointed out and hit this line:

894 upgraded, 91 newly installed, 0 to remove and 441 not upgraded.
Need to get 676 MB of archives.
After this operation, 1329 MB of additional disk space will be used.
Do you want to continue? [Y/n]

I copied the "not upgraded section to a text editor then barged ahead.

One done I jupmed in with the "not updated" list:

sudo apt install {not updated list}

First file "adb" caused an error - deleted it from the list and continued on ... deleteing files that caused errors.

Finally the rest were all installed and:

 12 Jul 22 @ 14:35:37 ~
   $ upd
[sudo] password for sector11: 
Hit:1 https://deb.debian.org/debian bullseye InRelease
Get:2 https://deb.debian.org/debian bullseye-updates InRelease [39.4 kB]
Get:3 https://deb.debian.org/debian bullseye-backports InRelease [44.2 kB]
Get:4 https://deb.debian.org/debian bullseye-backports/main amd64 Packages.diff/Index [63.3 kB]
Get:5 https://deb.debian.org/debian bullseye-backports/main Translation-en.diff/Index [63.3 kB]
Get:6 https://deb.debian.org/debian bullseye-backports/main amd64 Contents (deb).diff/Index [63.6 kB]
Get:7 https://deb.debian.org/debian bullseye-backports/main all Contents (deb).diff/Index [63.6 kB]
Get:8 https://deb.debian.org/debian bullseye-backports/main amd64 Packages T-2022-07-12-1408.33-F-2022-07-12-0809.30.pdiff [3,330 B]
Get:8 https://deb.debian.org/debian bullseye-backports/main amd64 Packages T-2022-07-12-1408.33-F-2022-07-12-0809.30.pdiff [3,330 B]
Get:9 https://deb.debian.org/debian bullseye-backports/main Translation-en T-2022-07-12-0809.30-F-2022-07-12-0809.30.pdiff [2,227 B]
Get:9 https://deb.debian.org/debian bullseye-backports/main Translation-en T-2022-07-12-0809.30-F-2022-07-12-0809.30.pdiff [2,227 B]
Get:10 https://deb.debian.org/debian bullseye-backports/main amd64 Contents (deb) T-2022-07-12-0809.30-F-2022-07-12-0809.30.pdiff [511 B]
Get:10 https://deb.debian.org/debian bullseye-backports/main amd64 Contents (deb) T-2022-07-12-0809.30-F-2022-07-12-0809.30.pdiff [511 B]
Get:11 https://deb.debian.org/debian bullseye-backports/main all Contents (deb) T-2022-07-12-1408.33-F-2022-07-12-0809.30.pdiff [17.5 kB]
Get:11 https://deb.debian.org/debian bullseye-backports/main all Contents (deb) T-2022-07-12-1408.33-F-2022-07-12-0809.30.pdiff [17.5 kB]
Fetched 361 kB in 4s (82.1 kB/s)    
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
 
 12 Jul 22 @ 14:35:55 ~
   $ upd
Hit:1 https://deb.debian.org/debian bullseye InRelease
Hit:2 https://deb.debian.org/debian bullseye-updates InRelease
Hit:3 https://deb.debian.org/debian bullseye-backports InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
 
 12 Jul 22 @ 14:36:00 ~
   $ alias upd
alias upd='sudo apt update'

ALL GOOD!

System running smooth as silk.

Have no idea why "upd" gets all those extra lines every now and then.
And really strange that nothing has been updated since Sunday.

 12 Jul 22 @ 14:57:01 ~
   $ uname -a
Linux Debian 5.10.0-16-amd64 #1 SMP Debian 5.10.127-1 (2022-06-30) x86_64 GNU/Linux

#1 2022-07-07 20:43:28

Is Helium still supported?

#2 2022-07-08 01:02:26

Re: Is Helium still supported?

#3 2022-07-08 04:48:26

Re: Is Helium still supported?

#4 2022-07-08 04:55:20

Re: Is Helium still supported?

#5 2022-07-08 13:30:31

Re: Is Helium still supported?

#6 2022-07-12 17:56:29

Re: Is Helium still supported?

Board footer