BunsenLabs Beryllium experimental packages are available

johnraff · 2021-10-27 05:31:48

^Just pasting in from my todo list:

BLOB:
✅ check TODO markers in bl-obthemes-tweaks
✅ store jgmenurc and compositor settings
✅ getScrot: fix all minimized windows being maximized after scrot
✅ Store conky and tint2 filepaths and desktop ids only ('id path'),
and generate command in script, instead of sourcing whole command.
✅ Improve conky & tint2 session handling (eg spaces in filepaths)
✅ Use conky and tint2 utilities (*-manager *-session) wherever possible?
✅ Default session implemented with conky using a symlink
✅ Need to add mechanism for changing the symlink.
✅ Add diff GUI from bl-user-setup for file-change warnings.
✅ fix yad_warning return value causing script exit when restoring.

Or, possibly more intelligible, see the changelog:
https://github.com/BunsenLabs/bunsen-ut … /changelog

But basically, take it for a spin - save your current theme setup, try some of the preinstalled themesets, change your themes/icons/conkys and save that as a new BLOB, restore what you had before - no nasty surprises or odd events? Anything that needs polishing in the user experience?

Last edited by johnraff (2021-10-27 06:09:06)

hhh · 2021-10-27 23:56:22

Nice, thanks! I'll report back when I use it (soon)!

plemil · 2021-10-28 10:19:38

My bunsen-utilities are "kept back" during the upgrade, so I'm not quite shure how to actually do the update.
Any pointers?

rbh · 2021-10-28 11:19:02

plemil wrote:

My bunsen-utilities are "kept back" during the upgrade, so I'm not quite shure how to actually do the update.
Any pointers?

Hard to know why it failed for you. No one else has reported problem. Is it only bunsen-utilities tat are kept back? Have you investigated with

$ apt policy bunsen*

No more info than it was held back? If you do not rember, look in /var/log/apt/term.log or /var/log/apt/history.log.
Are your sources lists correct configured? command "inxi -r", lists all your sources.

You can always try to download the deb

$ wget https://kelaino.bunsenlabs.org/~johnraff/debian/pool/main/b/bunsen-utilities/bunsen-utilities_11.2-1_all.deb

and install from disk with

$ sudo dpk -i bunsen-utilities_11.2-1_all.deb

plemil · 2021-10-28 20:22:06

Nothing more than the kept back message and as far as I can tell nothing interesting in the logs. No entries from today or yesterday.

noname@nonameBunsenBeryllium:~$ sudo apt-get update
[sudo] password for noname: 
Ign:1 http://repo.vivaldi.com/stable/deb stable InRelease
Hit:2 http://repo.vivaldi.com/stable/deb stable Release                                                                                                     
Hit:3 http://packages.microsoft.com/repos/code stable InRelease                                                                                             
Hit:4 http://apt.svtplay-dl.se svtplay-dl InRelease                                                                                                         
Hit:6 https://deb.debian.org/debian bullseye-backports InRelease                                                                                            
Hit:7 http://deb.debian.org/debian bullseye InRelease                                                                                            
Get:8 http://security.debian.org/debian-security bullseye-security InRelease [44.1 kB]                                     
Hit:9 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium InRelease                  
Fetched 44.1 kB in 6s (7,971 B/s)
Reading package lists... Done
noname@nonameBunsenBeryllium:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  bunsen-utilities linux-image-amd64 svtplay-dl
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.

noname@nonameBunsenBeryllium:~$ apt policy bunsen*
bunsen-images-archives:
  Installed: (none)
  Candidate: 11.0-1
  Version table:
     11.0-1 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
bunsen-images:
  Installed: 11.0-1
  Candidate: 11.0-1
  Version table:
 *** 11.0-1 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
        100 /var/lib/dpkg/status
bunsen-common:
  Installed: 11.0-1
  Candidate: 11.0-1
  Version table:
 *** 11.0-1 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
        100 /var/lib/dpkg/status
bunsen-paper-icon-theme:
  Installed: (none)
  Candidate: 11.0-1
  Version table:
     11.0-1 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
bunsen-keyring:
  Installed: 2020.10.10+bl11-1~dev1
  Candidate: 2020.10.10+bl11-1~dev1
  Version table:
 *** 2020.10.10+bl11-1~dev1 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
        100 /var/lib/dpkg/status
bunsen-thunar:
  Installed: 11.0-2
  Candidate: 11.0-2
  Version table:
 *** 11.0-2 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
        100 /var/lib/dpkg/status
bunsen-themes:
  Installed: 11.0-1
  Candidate: 11.0-1
  Version table:
 *** 11.0-1 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
        100 /var/lib/dpkg/status
bunsen-meta-packaging:
  Installed: (none)
  Candidate: 11.0.1-1
  Version table:
     11.0.1-1 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
bunsen-utilities:
  Installed: 11.1-2
  Candidate: 11.2-1
  Version table:
     11.2-1 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
 *** 11.1-2 100
        100 /var/lib/dpkg/status
bunsen-docs:
  Installed: 11.0-1
  Candidate: 11.0-1
  Version table:
 *** 11.0-1 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
        100 /var/lib/dpkg/status
bunsen-conky:
  Installed: 11.1-1
  Candidate: 11.1-1
  Version table:
 *** 11.1-1 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
        100 /var/lib/dpkg/status
bunsen-meta-all:
  Installed: 11.0-2
  Candidate: 11.0-2
  Version table:
 *** 11.0-2 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
        100 /var/lib/dpkg/status
bunsen-pipemenus:
  Installed: 11.2-1
  Candidate: 11.2-1
  Version table:
 *** 11.2-1 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
        100 /var/lib/dpkg/status
bunsen-meta-libreoffice:
  Installed: (none)
  Candidate: 11.0.1-1
  Version table:
     11.0.1-1 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
bunsen-meta-ssh:
  Installed: (none)
  Candidate: 11.0.1-1
  Version table:
     11.0.1-1 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
bunsen-meta-printer-support:
  Installed: (none)
  Candidate: 11.0.1-1
  Version table:
     11.0.1-1 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
bunsen-meta-vcs:
  Installed: 11.0.1-1
  Candidate: 11.0.1-1
  Version table:
 *** 11.0.1-1 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
        100 /var/lib/dpkg/status
bunsen-user-setup:
  Installed: (none)
  Candidate: (none)
  Version table:
bunsen-fortune:
  Installed: 11.0-1
  Candidate: 11.0-1
  Version table:
 *** 11.0-1 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
        100 /var/lib/dpkg/status
bunsen-exit:
  Installed: 11.0-1
  Candidate: 11.0-1
  Version table:
 *** 11.0-1 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
        100 /var/lib/dpkg/status
bunsen-configs-lite:
  Installed: (none)
  Candidate: 11.3-1
  Version table:
     11.3-1 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
bunsen-faenza-icon-theme:
  Installed: (none)
  Candidate: 11.0-1
  Version table:
     11.0-1 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
bunsen-meta-java:
  Installed: (none)
  Candidate: 11.0.1-1
  Version table:
     11.0.1-1 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
bunsen-welcome:
  Installed: 11.0.1-1
  Candidate: 11.0.1-1
  Version table:
 *** 11.0.1-1 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
        100 /var/lib/dpkg/status
bunsen-papirus-icon-theme:
  Installed: 11.0-1
  Candidate: 11.0-1
  Version table:
 *** 11.0-1 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
        100 /var/lib/dpkg/status
bunsen-lock:
  Installed: (none)
  Candidate: (none)
  Version table:
bunsen-configs:
  Installed: 11.3-1
  Candidate: 11.3-1
  Version table:
 *** 11.3-1 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
        100 /var/lib/dpkg/status
bunsen-images-extra:
  Installed: (none)
  Candidate: (none)
  Version table:
bunsen-meta-lamp:
  Installed: (none)
  Candidate: 11.0.1-1
  Version table:
     11.0.1-1 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
bunsen-meta-lite:
  Installed: (none)
  Candidate: 11.0-2
  Version table:
     11.0-2 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
bunsen-meta-bluetooth:
  Installed: 11.0.1-1
  Candidate: 11.0.1-1
  Version table:
 *** 11.0.1-1 500
        500 https://kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
        100 /var/lib/dpkg/status
bunsen-exit-python:
  Installed: (none)
  Candidate: (none)
  Version table:

noname@nonameBunsenBeryllium:~$ inxi -r
Repos:     Active apt repos in: /etc/apt/sources.list 
           1: deb http://deb.debian.org/debian/ bullseye main non-free contrib
           2: deb-src http://deb.debian.org/debian/ bullseye main non-free contrib
           3: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           4: deb-src http://security.debian.org/debian-security bullseye-security main contrib non-free
           No active apt repos in: /etc/apt/sources.list.d/bunsen-bullseye-backports.list 
           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
           Active apt repos in: /etc/apt/sources.list.d/svtplay-dl.list 
           1: deb http://apt.svtplay-dl.se/ svtplay-dl release
           Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
           1: deb http://repo.vivaldi.com/stable/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/vscode.list 
           1: deb [arch=amd64,arm64,armhf] http://packages.microsoft.com/repos/code stable main

This don't tell me much so any help appreciated.

johnraff · 2021-10-29 02:13:20

I think b-u was kept back because it has a couple of new dependencies. Try explicitly requesting its installation with

sudo apt install bunsen-utilities

johnraff · 2021-10-29 09:31:23

bunsen-welcome 11.1-1 has been uploaded.

This incorporates a number of improvements:
*) Scrolling between windows instead of clearing, so you can go back to previous pages. Many thanks to @eight.bit.al for this!
*) Checking of configured debian repos and offering to fix missing stuff. This should be good for people who install offline and end up with some necessary sources missing.
*) No popup terminal on login for people without sudo privileges - ie users added post-install. Only confusing, and they can still run 'bl-welcome' to see a message about why they need sudo.
*) Various bugfixes and other small improvements.

It's a big script and there's still a chance bugs remain so please give it a try. Comment out bits of your sources lists and see if it fixes them OK...

rbh · 2021-10-29 10:40:46

johnraff wrote:

bunsen-welcome 11.1-1 has been uploaded.
This incorporates a number of improvements:
*) Scrolling between windows instead of clearing, so you can go back to previous pages. Many thanks to @eight.bit.al for this!

A text how to go back to previos pages, is needed.

*) Checking of configured debian repos and offering to fix missing stuff. This should be good for people who install offline and end up with some necessary sources missing.

Good to check repositorys. But, I cot complaints about one of my local stored repos:

  You have some unknown repositories enabled:
   [local adress]/ftp.acc.umu.se/debian bullseye-proposed-updates/main amd64 Packages

"Inxi -r" reports:

deb [arch=amd64] [local adress]/ftp.acc.umu.se/debian/ bullseye-proposed-updates non-free contrib main

No complaint about non-free and contrib...

I mirror and use local repos on that computer:
bullseye, bullseye-backports, bullseye-updates, bullseye-proposed-updates, bullseye-security, kelaino[...]beryllium and syncthing

After changing source to

https://ftp.acc.umu.se/debian/ bullseye-proposed-updates non-free contrib main

bl-welcome still reports just main to be unkown.

johnraff · 2021-10-29 11:11:53

^That's OK.
"Unknown" doesn't mean wrong, just that bl-welcome doesn't know about it. There's no check for proposed-updates at the moment.
So it's not a complaint, just asking the user if they are sure they want that repo. If they do, that's fine.

It's intended to catch leftover entries that belonged to a previous release, or some private repo that the user might have enabled long ago and then forgotten.

But I could add {codename}-proposed-updates to the list of Debian repos to check for. That should keep it from appearing as "unknown" at least. @rbh maybe you could post the output of 'apt-cache policy' on your machine, perhaps in both cases - using local repos and with https sources? It would help me choose the right strings to use.

I'm not sure what the script's policy ought to be for local repos, in fact. Can they be verified like official Debian repos? Maybe the script should just tell the user it found them, and then carry on, the same as with "unknown" repos?

The "contrib" and "non-free" checks are only done on Debian, Debian Security and Debian Updates. Those are the cases that might be missing just after an install, and would interfere with package installs (especially Debian main). Other repos installed by hand by the user afterwards can be left as their own responsibility I think.

The main reasons this functionality was added were these two cases:
1) Offline installs with Debian-Installer (or the BL installer) result in sources lists missing the main Debian repository.
2) Installs from the Debian netinstaller will not enable contrib and non-free by default, and users sometimes forget to add them.
Both those cases have occurred multiple times up to now, and the new bl-welcome is expected to be able to deal with them.

@rbh thanks for the feedback. It helps a lot!

DeepDayze · 2021-10-29 15:21:47

You could also add any 3rd party repos as well for BL welcome to catch and ask user if they are still used or not and offer to delete any that are stale or old if user opts not to keep them.

rbh · 2021-10-29 16:30:28

I am just now updating that box to bookworm...
Has a little tight scheme just now.
I can run 'apt-cache policy' on my default desktop later, but will edit out everything but debian repos.
I have not examined the script, Does it not search for Release file?

unklar · 2021-10-29 17:29:46

johnraff wrote:

But basically, take it for a spin - save your current theme setup, try some of the preinstalled themesets, change your themes/icons/conkys and save that as a new BLOB, restore what you had before - no nasty surprises or odd events? Anything that needs polishing in the user experience?

@John, Thank you, for this excellent work.

I tested this earlier and can tell you, everything was restored with my setup. No surprises. Just as it should be.
I took a few pictures to go with it.
Not quite sure if the BLOB manager wanted to save the chosen "crunchbang-theme" finally also under my setup "flight", which I refused as a precaution. But I can also be wrong...

In detail, my setup:

Save Settings:Comparison of the differences on the example "Conky" and "tint2" new topic "Crunchbang" the missing icon theme "Faenza" is installed afterwards password for the greeter is required Voila! BINGO!

Last edited by unklar (2021-10-29 17:42:02)

rbh · 2021-10-29 19:57:08

johnraff wrote:

^That's OK.
"Unknown" doesn't mean wrong, just that bl-welcome doesn't know about it.

Yes, i know, but all official sources for Debian and Bunsenlabs should be known by bl-welcome.

So it's not a complaint, just asking the user if they are sure they want that repo.

Some semantics...

But I could add {codname}-proposed-updates to the list of Debian repos to check for.

Yes, I think it can avoid unnesessary confusion.

@rbh maybe you could post the output of 'apt-cache policy' on your machine, perhaps in both cases - using local repos and with https sources? It would help me choose the right strings to use.

It is no difference with http or https. First policy for al local repos, then for only security. Actual ip replaced.

”Package”-filer:
 100 /var/lib/dpkg/status
     release a=now
  500 Local.adres/mirror/eu.pkg.bunsenlabs.org/debian beryllium/main amd64 Packages
     release o=bunsenlabs,a=beryllium,n=beryllium,l=bunsenlabs,c=main,b=amd64
     origin Local.ip
 500 Local.adres/mirror/kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
     release o=bunsenlabs,a=beryllium,n=beryllium,l=bl_beryllium_experimental,c=main,b=amd64
     origin Local.ip
 500 Local.adres/mirror/security.debian.org/debian-security bullseye-security/main amd64 Packages
     release v=11,o=Debian,a=stable-security,n=bullseye-security,l=Debian-Security,c=main,b=amd64
     origin Local.ip
 500 Local.adres/ftp.acc.umu.se/debian bullseye-proposed-updates/main amd64 Packages
     release v=11-updates,o=Debian,a=proposed-updates,n=bullseye-proposed-updates,l=Debian,c=main,b=amd64
     origin Local.ip
 500 Local.adres/ftp.acc.umu.se/debian bullseye-updates/main amd64 Packages
     release v=11-updates,o=Debian,a=stable-updates,n=bullseye-updates,l=Debian,c=main,b=amd64
     origin Local.ip
 100 Local.adres/ftp.acc.umu.se/debian bullseye-backports/non-free amd64 Packages
     release o=Debian Backports,a=bullseye-backports,n=bullseye-backports,l=Debian Backports,c=non-free,b=amd64
 500 Local.adres/mirror/eu.pkg.bunsenlabs.org/debian beryllium/main amd64 Packages
     release o=bunsenlabs,a=beryllium,n=beryllium,l=bunsenlabs,c=main,b=amd64
     origin Local.ip
 500 Local.adres/mirror/kelaino.bunsenlabs.org/~johnraff/debian beryllium/main amd64 Packages
     release o=bunsenlabs,a=beryllium,n=beryllium,l=bl_beryllium_experimental,c=main,b=amd64
     origin Local.ip
 500 Local.adres/mirror/security.debian.org/debian-security bullseye-security/main amd64 Packages
     release v=11,o=Debian,a=stable-security,n=bullseye-security,l=Debian-Security,c=main,b=amd64
     origin Local.ip
 500 Local.adres/ftp.acc.umu.se/debian bullseye-proposed-updates/main amd64 Packages
     release v=11-updates,o=Debian,a=proposed-updates,n=bullseye-proposed-updates,l=Debian,c=main,b=amd64
     origin Local.ip
 500 Local.adres/ftp.acc.umu.se/debian bullseye-updates/main amd64 Packages
     release v=11-updates,o=Debian,a=stable-updates,n=bullseye-updates,l=Debian,c=main,b=amd64
     origin Local.ip
 100 Local.adres/ftp.acc.umu.se/debian bullseye-backports/non-free amd64 Packages
     release o=Debian Backports,a=bullseye-backports,n=bullseye-backports,l=Debian Backports,c=non-free,b=amd64
     origin Local.ip
 100 Local.adres/ftp.acc.umu.se/debian bullseye-backports/contrib amd64 Packages
     release o=Debian Backports,a=bullseye-backports,n=bullseye-backports,l=Debian Backports,c=contrib,b=amd64
     origin Local.ip
 100 Local.adres/ftp.acc.umu.se/debian bullseye-backports/main amd64 Packages
     release o=Debian Backports,a=bullseye-backports,n=bullseye-backports,l=Debian Backports,c=main,b=amd64
     origin Local.ip
 500 Local.adres/ftp.acc.umu.se/debian bullseye/non-free amd64 Packages
     release v=11.1,o=Debian,a=stable,n=bullseye,l=Debian,c=non-free,b=amd64
     origin Local.ip
 500 Local.adres/ftp.acc.umu.se/debian bullseye/contrib amd64 Packages
     release v=11.1,o=Debian,a=stable,n=bullseye,l=Debian,c=contrib,b=amd64
     origin Local.ip
 500 Local.adres/ftp.acc.umu.se/debian bullseye/main amd64 Packages
     release v=11.1,o=Debian,a=stable,n=bullseye,l=Debian,c=main,b=amd64
     origin Local.ip

500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages
     release v=11,o=Debian,a=stable-security,n=bullseye-security,l=Debian-Security,c=main,b=amd64
     origin security.debian.org

And last, just for the sake of it; http://kelaino...

500 [url]http://kelaino.bunsenlabs.org/~johnraff/debian[/url] beryllium/main amd64 Packages
     release o=bunsenlabs,a=beryllium,n=beryllium,l=bl_beryllium_experimental,c=main,b=amd64
     origin kelaino.bunsenlabs.org

I'm not sure what the script's policy ought to be for local repos, in fact. Can they be verified like official Debian repos?

If they could not, I would not have any use of my mirrors.

Maybe the script should just tell the user it found them, and then carry on, the same as with "unknown" repos?

If I had the bandwith, I could have added my mirrors to Debian list of mirrors... Everyting at ftp.acc.umu.se, is verified aginst upstream servers. My content is also verified. So, that is a bad idea.

The "contrib" and "non-free" checks are only done on Debian, Debian Security and Debian Updates. Those are the cases that might be missing just after an install, and would interfere with package installs (especially Debian main).

Here I am lost. I think that bl-welcome for beryllium/bullseye, should know the bullseye/stable suite and all components (main, contrib and nonfree).

Other repos installed by hand by the user afterwards can be left as their own responsibility

Yes.

johnraff · 2021-10-30 01:41:33

Thanks to everybody for the feedback!

rbh wrote:

I have not examined the script, Does it not search for Release file?

A couple more responses later, but first to explain the script's inner workings a bit:

Instead of trying to directly parse sources lists, it talks to apt and gets all its information via apt's own mechanisms. The main source is the output of 'apt-cache policy' which lists up all the sources that apt was able to find, including the information got from (yes @rbh) the downloaded Release files. But the files are downloaded by apt, not directly by the script.

Here's the Debian Security entry that @rbh posted - they're all in this form:

500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages
     release v=11,o=Debian,a=stable-security,n=bullseye-security,l=Debian-Security,c=main,b=amd64
     origin security.debian.org

The v, o, a, n, l, c, b (version origin archive/suite codename label component architecture) values on the second line (and occasionally the uri on the first line) are what we use - in fact only o, n, l and c are enough to determine exactly what repo/suite/component it is.
(See man apt_preferences for explanations of those values.)

Deb Security goes through a change between buster and bullseye which makes it necessary to check l (label) to distinguish between security and updates on Lithium. In fact this script is intended for Beryllium but I tried to make it backward-compatible just in case we wanted to backport it to Lithium later.

An array is generated holding everything found in 'apt-cache policy' - all "known" repos are given a name, the others are "unknown_1" etc.

Checking algorithm:
1) Look for Debian, Debian Security and Debian Updates ("main" component here) and offer to add any of those three that are missing. Others (like Debian Backports, and OK Debian Proposed Updates too) are just silently added to the array if found. User gets to choose: Add automatically, or Exit now and do the editing by hand. Continuing without them is not an option for bl-welcome.

2) Again for Debian, Debian Security and Debian Updates, check if "contrib" and "non-free" are also found, and if not, offer to add them. This time user can choose: Add, Exit and edit yourself, or Continue without them. Some users might not want non-free software.

3) Any repositories that are not "known" are added to the "unknown" list and reported to the user:

bl-welcome wrote:

You have some unknown repositories enabled:
$unknown_list
If you are aware of these and want to go on using them, you can continue.
Otherwise, you might want to exit this script now and investigate
/etc/apt/sources.list and /etc/apt/sources.list.d
before running 'bl-welcome' again.

Choice this time is Continue or Exit.

---
A complication is that if a certain release/component repository holds no packages, then apt will not download a Release file and there's no entry in 'apt-cache policy' and no element in the array. This happens right now with Debian_Security/contrib for example, giving a false negative result. If user added "contrib" again, apt would complain about the double entry. But we still want the user to have "contrib" enabled in case packages arrive later, so it's necessary to check the local situation without asking apt to download anything. Not simple unless you resort to parsing the sources.list files after all. Finally (this took some days of googling and thinking) I found 'apt-get indextargets --no-release-info' which can tell us what we need to know, though it's not simple. (See Acquire additional files in 'update' operations for detail.) With that, it's possible to check for contrib and non-free but it depends on already having the source uri from a valid 'policy' entry, usually the corresponding "main" repo.

So it's all quite complicated and right now I don't feel inclined to add any extra functionality beyond simple additions to the framework that already exists. After all, bl-welcome is intended to be run only once or twice, to help new users get their system set up. I think now we have the two main itchy spots scratched: missing Debian Main after an offline install, and missing contrib non-free after a default Debian Installer install. Advanced users who edit their repository sources can be left alone.

---
If you want to see the code, the bunsen-welcome page apt-update-check-upgrade runs a function checkRepos() which in turn uses getRepoStatus() and checkAptTargets() which are defined on the bl-welcome root page because they're also used elsewhere, like when adding backports.

Last edited by johnraff (2021-10-30 05:29:47)

johnraff · 2021-10-30 01:46:44

DeepDayze wrote:

You could also add any 3rd party repos as well for BL welcome to catch and ask user if they are still used or not and offer to delete any that are stale or old if user opts not to keep them.

3rd party repos will be displayed as "unknown_<number>" along with the source line (the first line in the policy entry) so users can identify them. For now, let's leave it at that, and let the user delete them by hand?

johnraff · 2021-10-30 01:57:39

rbh wrote:

...all official sources for Debian and Bunsenlabs should be known by bl-welcome.

Agreed. Let's add bullseye-proposed-updates. Are there any others?

@rbh maybe you could post the output of 'apt-cache policy' on your machine
First policy for al local repos, then for only security. Actual ip replaced.
”Package”-filer:
 100 /var/lib/dpkg/status
     release a=now
500 Local.adres/mirror/eu.pkg.bunsenlabs.org/debian beryllium/main amd64 Packages
     release o=bunsenlabs,a=beryllium,n=beryllium,l=bunsenlabs,c=main,b=amd64
     origin Local.ip
etc...

Thanks! So it looks as if local repos are detected OK.

Scrolling between windows instead of clearing, so you can go back to previous pages.
A text how to go back to previous pages, is needed.

Good point. The current documentation is quite sparse. (See 'man bl-welcome' or 'bl-welcome -h')

What else could usefully be added there?

rbh · 2021-10-30 12:45:21

johnraff wrote:

rbh wrote:
...all official sources for Debian and Bunsenlabs should be known by bl-welcome.
Agreed. Let's add bullseye-proposed-updates. Are there any others?

No. Lets keep oficial Debian repos like debian-debug, out. When running bl-welcome on bullseye/stable, the skript should recognize:

With stable means both bullseye and stable.
debian/ stable main contrib non-free
debian/ stable-backports main contrib non-free
debian/ stable-updates main contrib non-free
debian/ stable-proposed-updates main contrib non-free
and
security.debian.org/...

What else could usefully be added there?

In the script or the manpage...

Maybe something like:

This script makes a sanity-check of your sources. It is not bulletproof. Still god that you know your sources. Command "inxi -r", lists them.

DeepDayze · 2021-10-30 21:47:21

johnraff wrote:

DeepDayze wrote:
You could also add any 3rd party repos as well for BL welcome to catch and ask user if they are still used or not and offer to delete any that are stale or old if user opts not to keep them.
3rd party repos will be displayed as "unknown_<number>" along with the source line (the first line in the policy entry) so users can identify them. For now, let's leave it at that, and let the user delete them by hand?

Fair enough and that sounds good.

johnraff · 2021-10-31 05:15:18

rbh wrote:

In the script or the manpage...
Maybe something like:

This script makes a sanity-check of your sources. It is not bulletproof. Still god that you know your sources. Command "inxi -r", lists them.

Looks good. Maybe a terse description of other pages too.

But, let's bear in mind that hardly anybody will read the documentation anyway. The welcome popup comes just after installation, so really needs to be self-explanatory as much as possible.

(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 )

rbh · 2021-10-31 07:19:41

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 )

Yes, sounds good.

#21 2021-10-27 05:31:48

Re: BunsenLabs Beryllium experimental packages are available

#22 2021-10-27 23:56:22

Re: BunsenLabs Beryllium experimental packages are available

#23 2021-10-28 10:19:38

Re: BunsenLabs Beryllium experimental packages are available

#24 2021-10-28 11:19:02

Re: BunsenLabs Beryllium experimental packages are available

#25 2021-10-28 20:22:06

Re: BunsenLabs Beryllium experimental packages are available

#26 2021-10-29 02:13:20

Re: BunsenLabs Beryllium experimental packages are available

#27 2021-10-29 09:31:23

Re: BunsenLabs Beryllium experimental packages are available

#28 2021-10-29 10:40:46

Re: BunsenLabs Beryllium experimental packages are available

#29 2021-10-29 11:11:53

Re: BunsenLabs Beryllium experimental packages are available

#30 2021-10-29 15:21:47

Re: BunsenLabs Beryllium experimental packages are available

#31 2021-10-29 16:30:28

Re: BunsenLabs Beryllium experimental packages are available

#32 2021-10-29 17:29:46

Re: BunsenLabs Beryllium experimental packages are available

#33 2021-10-29 19:57:08

Re: BunsenLabs Beryllium experimental packages are available

#34 2021-10-30 01:41:33

Re: BunsenLabs Beryllium experimental packages are available

#35 2021-10-30 01:46:44

Re: BunsenLabs Beryllium experimental packages are available

#36 2021-10-30 01:57:39

Re: BunsenLabs Beryllium experimental packages are available

#37 2021-10-30 12:45:21

Re: BunsenLabs Beryllium experimental packages are available

#38 2021-10-30 21:47:21

Re: BunsenLabs Beryllium experimental packages are available

#39 2021-10-31 05:15:18

Re: BunsenLabs Beryllium experimental packages are available

#40 2021-10-31 07:19:41

Re: BunsenLabs Beryllium experimental packages are available

Board footer