BunsenLabs Beryllium experimental packages are available

sleekmason · 2021-10-31 15:40:17

johnraff wrote:

(One more possible thing to add to bl-welcome before Beryllium: a "firmware" page, offering to install and run isenkram-cli.
https://www.debian.org/releases/bullsey … led-system )

----

That is one cool program! Gave good info showing I was missing some firmware. Gave specific info as to which firmware was missing/needed. Checked for the missing firmware, found nothing to do, and exited. No extra file added to /etc/apt/sources.list.d.

Don't know if that is because it couldn't find the missing firmware, or because I have non-free sources already enabled.

Good stuff. Easy list to hunt down what I need

johnraff · 2021-11-12 05:13:13

I just did a plain Debian CLI install (no non-free firmware) on an oldish Thinkpad. Because the needed wireless firmware (iwlwifi*) was missing it had to be done with a wired connection, but post-install I installed isenkram-cli (2MB d/l - 9MB on disk) and ran 'sudo isenkram-autoinstall-firmware'. It discovered the missing firmware, added the missing "config" and "non-free" to apt sources and installed:
firmware-iwlwifi
firmware-misc-nonfree
firmware-realtek

If this works equally well for other hardware then it might allow us to drop large firmware bundles from the default BL install. Especially for the squashed "CD" iso it might help get the size down a bit.

Last edited by johnraff (2021-11-13 10:26:00)

manyroads · 2021-11-12 13:36:56

FWIW @johnraff I tried installing firmware-misc-non-free using apt on MX21 and it was not located. Perhaps there's a typo?!?!?

unklar · 2021-11-12 14:35:52

apt policy firmware-misc-nonfree
firmware-misc-nonfree:
  Installiert:           20190114-2
  Installationskandidat: 20190114-2
  Versionstabelle:
 *** 20190114-2 500
        500 https://deb.debian.org/debian buster/non-free i386 Packages
        100 /var/lib/dpkg/status

manyroads · 2021-11-12 15:00:58

@unklar It turns out that the package is installed by MX. It was just that sudo apt install was not happy with the name. Sorry for the confusion. I

johnraff · 2021-11-13 10:25:28

^and sorry for the typo!

johnraff · 2021-11-22 06:27:10

bunsen-welcome 11.2.1-1 is now in the repo.

Apart from adding a firmware page using isenkram-cli, the apt sources check no longer reports proposed-updates as "unknown" and 'man bl-welcome' has been slightly extended (thanks @rbh for suggestions). Some bits of text have also been tweaked here and there.

Anyone who can check it out - there's still time to incorporate small improvements.

unklar · 2021-11-22 18:44:03

Here the script says goodbye already with call of the page 2 without comment.
The message from the log:

------------------------------------------------------[ page 2 of 16 ]-------------------------------------------------------

  UPDATE SOFTWARE SOURCES, CHECK SOURCES AND UPGRADE INSTALLED PACKAGES
  ---------------------------------------------------------------------
  
  Before we can continue, we need to make sure your system's software is up-to-date. This script will execute the commands:
  
      sudo apt-get update
      sudo apt-get upgrade --with-new-pkgs
  
  It will also check your configured apt sources to make sure that all necessary repositories are available.
  
  If you do not want to upgrade now, you can run this welcome script any time later in a terminal with the command "bl-welcome"
  
  Would you like to upgrade your software? [Y/n] 
Hit:1 https://ftp.halifax.rwth-aachen.de/debian bullseye InRelease
Hit:2 https://security.debian.org/debian-security bullseye-security InRelease
Hit:3 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium InRelease
Reading package lists...
  Finished update
  
  Checking apt sources... 

Checked repositories status.
Data:
declare -A repo_status=([debian_contrib]=" 500 https://ftp.halifax.rwth-aachen.de/debian bullseye/contrib amd64 Packages" [bunsen_main]=" 500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages" [debian_main]=" 500 https://ftp.halifax.rwth-aachen.de/debian bullseye/main amd64 Packages" [debian_non-free]=" 500 https://ftp.halifax.rwth-aachen.de/debian bullseye/non-free amd64 Packages" [deb_sec_main]=" 500 https://security.debian.org/debian-security bullseye-security/main amd64 Packages" )


contrib was found missing from bullseye-security + https://security.debian.org/debian-security in apt policy - checking local configs


bullseye-security contrib found in user apt sources


non-free was found missing from bullseye-security + https://security.debian.org/debian-security in apt policy - checking local configs


bullseye-security non-free found in user apt sources

/usr/lib/bunsen/welcome/apt-update-check-upgrade: Zeile 39: repo_status[${repo}_main] ist nicht gesetzt.

My Repos

inxi -r
Repos:     Active apt repos in: /etc/apt/sources.list 
           1: deb https://ftp.halifax.rwth-aachen.de/debian/ bullseye main non-free contrib
           2: deb-src https://ftp.halifax.rwth-aachen.de/debian/ bullseye main non-free contrib
           3: deb https://security.debian.org/debian-security bullseye-security main contrib non-free
           4: deb-src https://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/bunsen.list 
           1: deb https://kelaino.bunsenlabs.org/~johnraff/debian beryllium main

It is also impractical that the log does not start at line 1. It continues the entries of all previous "script calls".
Maybe a new bunsen-welcome could delete the old log of the predecessor first.

johnraff · 2021-11-23 02:43:59

^ Many thanks @unklar, you've found a bug.

Luckily, this one should be easy to fix:

unklar wrote:

/usr/lib/bunsen/welcome/apt-update-check-upgrade: Zeile 39: repo_status[${repo}_main] ist nicht gesetzt.

OK guessing Zeile=line and 'nicht gesetzt'=unset, the problem is indeed on line 39:

if [[ -z ${repo_status[${repo}_main]} ]]

If any of debian/debian security/debian updates are missing, the variable is unset, which causes the script to error out because of

set -o nounset # do not accept unset variables

at the top of /usr/bin/bl-welcome. Just changing that line to

if [[ -z ${repo_status[${repo}_main]-} ]]

Should convert the unset variable to an empty variable and fix it. I'm puzzled, though how I managed to test this script without hitting that bug already. Maybe it came in during a rewrite? Anyway, I'll push up a fixed bunsen-welcome today, and thanks again!

BTW the script will try to add debian-updates to your sources. Is there some reason you've left them out? Generally, they're good to have.
---

About the log file. In the past we thought about deleting old logs, but considering most users won't run bl-welcome more than once or twice, the consensus was that it was useful to keep the previous output for bugtracking.

But, it would help if the new session was easier to find, so let's add another line-break or two before

bl-welcome wrote:

Starting bl-welcome for <user> at <date>

and maybe a line of hashmarks too:
##############################################################################

johnraff · 2021-11-23 04:42:34

bunsen-welcome 11.2.2-1
Uploaded. Any more bug reports always welcome!

unklar · 2021-11-23 08:35:07

Thank you @johnraff, for your work.

I have now tested the new script without errors.

johnraff wrote:

BTW the script will try to add debian-updates to your sources. Is there some reason you've left them out? Generally, they're good to have.

No, it was not a specific intention. If I'm honest, I wanted to see if the script would do it for me.

before

inxi -r
Repos:     Active apt repos in: /etc/apt/sources.list 
           1: deb https://ftp.halifax.rwth-aachen.de/debian/ bullseye main non-free contrib
           2: deb-src https://ftp.halifax.rwth-aachen.de/debian/ bullseye main non-free contrib
           3: deb https://security.debian.org/debian-security bullseye-security main contrib non-free
           4: deb-src https://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/bunsen.list 
           1: deb https://kelaino.bunsenlabs.org/~johnraff/debian beryllium main

after

inxi -r
Repos:     Active apt repos in: /etc/apt/sources.list 
           1: deb https://ftp.halifax.rwth-aachen.de/debian/ bullseye main non-free contrib
           2: deb-src https://ftp.halifax.rwth-aachen.de/debian/ bullseye main non-free contrib
           3: deb https://security.debian.org/debian-security bullseye-security main contrib non-free
           4: deb-src https://security.debian.org/debian-security bullseye-security main contrib non-free
           5: deb https://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/bunsen-bullseye-backports.list 
           1: deb https://pkg.bunsenlabs.org/debian bullseye-backports main
           Active apt repos in: /etc/apt/sources.list.d/bunsen.list 
           1: deb https://kelaino.bunsenlabs.org/~johnraff/debian beryllium main
           Active apt repos in: /etc/apt/sources.list.d/debian-bullseye-backports.list 
           1: deb https://deb.debian.org/debian bullseye-backports main contrib non-free

once again, thank you very much!

johnraff · 2021-11-24 04:07:06

^And thank you for taking the time to test it! Happy to hear it seems to work. I'm hoping these additions to the script will help those users who install offline and end up with some repos missing from their sources.list.

johnraff · 2021-11-24 05:45:30

bunsen-utilities 11.3-1 uploaded.
Some of the BL utilities, like conky/tint2 editors and BLOB, now have .desktop files so they appear in auto-generated menus or jgmenu search.

juancuyo · 2022-04-10 20:40:39

Good afternoon I wanted to know if they have any date scheduled for the launch of the beryllium version
I apologize if this was not the place to ask

Bearded_Blunder · 2022-04-10 21:35:31

I've seen some indications that at least a beta or release candidate could appear shortly..

Things appear to use the same scheduling engine as Debian.. the next release is "When it's ready".

I don't think it'll be too long, but it'll be when it is.

deleted0 · 2022-04-10 21:58:03

And that will be an undesirable amount of time.

Bearded_Blunder · 2022-04-11 01:28:51

Well @eight.bit.al you're not the only one who can hardly wait but @johnraff has mentioned trial building a 32bit .iso which suggests he's doing similar for amd64 too.

The repo seems to be present on the main server, even if not fully populated with the packages.. no I'm not mentioning what's missing unless asked by johnraff or someone else with github access, but I'm thinking we're getting close to seeing at least something pre-release.

All I'll say about that is.. it's not much that's not there yet.

Last edited by Bearded_Blunder (2022-04-11 01:36:21)

deleted0 · 2022-04-11 02:52:13

I understand. Some Distro gets the honor of being the last one to upgrade.
A search on DW for 'Based on Debian (Stable)' lists some 30 or so Distros.

BL and SolydXK are the only two left to upgrade. So there's that.

Last edited by deleted0 (2022-04-11 02:53:51)

Bearded_Blunder · 2022-04-11 02:56:00

Well I suspect that the missing package(s) are possibly deliberate to prevent leakage.
Plus BL is a small team.

I can hardly wait though.. except that for my laptop I'm also waiting for delivery of an SSD laptop drives are a bit slow when they're still spinning rust.

On the whole though, I'd rather wait a bit than get something that required a nuke-&-pave reinstall than it got rushed.. especially given how long Debian takes to do the wipe for LVM over LUKS.. quite why they use urandom rather than take advantage of the extra speed that /dev/zero affords when using mapper affords really defeats me.. you have to have an OLD processor to not have aes built in.

Last edited by Bearded_Blunder (2022-04-11 03:01:58)

deleted0 · 2022-04-11 03:01:38

I'm sure you already know; you will be so pleased with that upgrade.

Last edited by deleted0 (2022-04-11 03:03:09)

#41 2021-10-31 15:40:17

Re: BunsenLabs Beryllium experimental packages are available

#42 2021-11-12 05:13:13

Re: BunsenLabs Beryllium experimental packages are available

#43 2021-11-12 13:36:56

Re: BunsenLabs Beryllium experimental packages are available

#44 2021-11-12 14:35:52

Re: BunsenLabs Beryllium experimental packages are available

#45 2021-11-12 15:00:58

Re: BunsenLabs Beryllium experimental packages are available

#46 2021-11-13 10:25:28

Re: BunsenLabs Beryllium experimental packages are available

#47 2021-11-22 06:27:10

Re: BunsenLabs Beryllium experimental packages are available

#48 2021-11-22 18:44:03

Re: BunsenLabs Beryllium experimental packages are available

#49 2021-11-23 02:43:59

Re: BunsenLabs Beryllium experimental packages are available

#50 2021-11-23 04:42:34

Re: BunsenLabs Beryllium experimental packages are available

#51 2021-11-23 08:35:07

Re: BunsenLabs Beryllium experimental packages are available

#52 2021-11-24 04:07:06

Re: BunsenLabs Beryllium experimental packages are available

#53 2021-11-24 05:45:30

Re: BunsenLabs Beryllium experimental packages are available

#54 2022-04-10 20:40:39

Re: BunsenLabs Beryllium experimental packages are available

#55 2022-04-10 21:35:31

Re: BunsenLabs Beryllium experimental packages are available

#56 2022-04-10 21:58:03

Re: BunsenLabs Beryllium experimental packages are available

#57 2022-04-11 01:28:51

Re: BunsenLabs Beryllium experimental packages are available

#58 2022-04-11 02:52:13

Re: BunsenLabs Beryllium experimental packages are available

#59 2022-04-11 02:56:00

Re: BunsenLabs Beryllium experimental packages are available

#60 2022-04-11 03:01:38

Re: BunsenLabs Beryllium experimental packages are available

Board footer