Carbon TODO

sleekmason · 2025-10-23 11:45:30

@johnraff, This is the only notice I have seen. This one through the common kernel dev packages. They give the user the mirror address in the dialog, so easy to fix. Currently running 17.4 with zero issues.

Mine is really kind of an edge case. I haven't installed any other tools than this, but they do encompass a pretty decent range overall. No issues with anything else.

Maybe a simple notice about development and changing to deb822? If this is the only case (pbuilder), then not really much of a concern, unless someone's using a script to run through a series of commands including the package installation. One example anyway. Pretty far out there really. Eh...

bc
bison
dh-make
pbuilder
build-essential
fakeroot
flex
libelf-dev
libncurses5-dev
libssl-dev
autoconf
libparse-debcontrol-perl
automake
autopoint
autotools-dev
debhelper
dh-autoreconf
dpkg-dev
devscripts
dh-strip-nondeterminism
dwz
gettext
intltool-debian
libarchive-zip-perl
libfl-dev
libdebhelper-perl
libfile-stripnondeterminism-perl
libsub-override-perl
libtool
po-debconf

And of course these drag in another 50 or so dependencies as well.

johnraff · 2025-10-24 00:53:42

^Ah pbuilder. I use it to build the BL packages. I don't recall seeing that popup, but it might be because I've already configured MIRRORSITE in ~/.pbuilderrc. My first guess is that it checks /etc/apt/sources.list and uses the Debian url it finds there as the mirror, if nothing else has been configured. Maybe it can't read the modernized sources.

EDIT: it's probably because I installed pbuilder via bl-welcome and ~/.pbuilderrc got auto-generated.

But I don't think that's a serious issue - a user who's about to use pbuilder can reasonably be expected to know what to fill in that dialog (and they give an example). The url is the same regardless of apt sources format. Some people might want to set a proxy or some kind of data caching software there.

Thanks for bringing it up though.

Last edited by johnraff (2025-10-25 06:06:33)

johnraff · 2025-10-25 06:04:55

sleekmason wrote:

From what I can tell, the modernize-sources script was expecting to find a signing key line within the backports.list file. Easy enough to remedy once I found out it was throwing a warning. Just one of those unexpected odd issues I guess.

I finally ran into the same issue and at last understood what you were saying. modernize-sources is able to find the signing key for all the other debian archives except backports, so you have to put it into the apt line, or add it to the backports sources file after modernization.

bl-welcome now deals with it. The Debian key's location is pretty much fixed at '/usr/share/keyrings/debian-archive-keyring.gpg' so I hard-coded it for backports.

I just uploaded bunsen-welcome 13.2-1 which should handle all these issues. In case you've still got that Carbon system to hand, and have a few minutes spare, maybe you could upgrade bunsen-welcome and run 'bl-welcome' to see if it works for you?

johnraff · 2025-10-25 06:41:34

NEW TODO
Figure out what to do about imgur not working in the UK.
https://forums.bunsenlabs.org/viewtopic.php?id=9569

sleekmason · 2025-10-25 15:43:01

johnraff wrote:
maybe you could upgrade bunsen-welcome and run 'bl-welcome' to see if it works for you?

Well done:)

I tried separate orders of operations a couple of times and didn't see any conflicts or issues. Of course you know how that goes, but looking good at the present moment anyway.

One note would be to remember any other instances where backports might be enabled within the distro to make sure the commands match (whatever). Is there a separate installer for backports? and that would include the backports kernel install as well if there is such a beastie in BL.

johnraff · 2025-10-26 00:28:26

Thanks for checking out bl-welcome.

sleekmason wrote:

One note would be to remember any other instances where backports might be enabled within the distro to make sure the commands match (whatever). Is there a separate installer for backports? and that would include the backports kernel install as well if there is such a beastie in BL.

There are no other installers for backports or for the backported kernel. The kernel might look like a candidate but we have to stop the handholding somewhere!

If $USER enabled backports - or any other sources - by hand, or by some other utility - then bl-welcome would pick it up the next time it was run, and should know what's going on. It doesn't look at any of the config files, but asks apt directly what sources it knows about.

You could try removing a Debian or BL backports .sources file, run bl-welcome to confirm it offers to add it, refuse, close the script, then put the backports in by hand, either as a .list or .sources file. The next time you run bl-welcome it should detect that the backports have already been added, and if it is a .list file will offer to modernize it.

sleekmason · 2025-10-26 11:41:21

@johnraff wrote:
You could try removing a Debian or BL backports .sources file, run bl-welcome to confirm it offers to add it, refuse, close the script, then put the backports in by hand, either as a .list or .sources file. The next time you run bl-welcome it should detect that the backports have already been added, and if it is a .list file will offer to modernize it.

I basically did this through the welcome script, Adding backports and then closing out, etc.. All directions. ( and now manually with no issues for backports)

* May have found something - Please check the 'signed by' for the bunsen sources. Also please double check what happens on manual removal of the bunsen sources. If not found, the script offers to add them, but then errors out, my guess would be trying to add them back to sources.list? dunno.

This problem may also just be a fluke, as I was flinging files in and out. I'll need to reinstall at some point to check further.

johnraff · 2025-10-27 02:31:46

sleekmason wrote:

May have found something - Please check the 'signed by' for the bunsen sources. Also please double check what happens on manual removal of the bunsen sources. If not found, the script offers to add them, but then errors out, my guess would be trying to add them back to sources.list?

I had a look at the code, and to add the BL sources the script is writing an apt line, including signed-by, to /etc/apt/sources.list.d/bunsen.list
That should work OK because the modernize-sources page later on should catch it.

But anyway, I'll do a run of bl-welcome in a VM and see if I can reproduce the issue...

---
BTW bl-welcome makes a log in ~/.cache/bunsen-welcome/bl-welcome.log
The apt checking section is quite verbose.

johnraff · 2025-10-27 04:27:36

OK I've found it - a bug in bl-welcome running grep on a string containing square brackets [ ] :

  Adding BunsenLabs carbon repository repo to apt sources...
  
grep: Invalid range end
Failed to add BunsenLabs to apt sources.
  
  Error checking repositories.

I hit the same thing before with the sections adding Debian and BL backports - trying to grep 'deb [signed-by-"..."] https...' to check the line was added correctly. In regular expressions [ stuff ] denotes a character range. The fix is the -F option which disables regular expressions and just looks for plain strings. The offending line 186 in welcome/apt-update-check-upgrade is now:

grep -qFx "${repo_line}" "$sources_file" || { echo "Failed to add $name to apt sources." >&2; return 1;}

https://github.com/BunsenLabs/bunsen-we … 28cedc309f

And bl-welcome now seems to cope with missing BL apt sources. I'll push an upgrade soon.

And thanks for the catch!

sleekmason · 2025-10-27 13:16:18

Nice!

okay, Not sure if you already pushed a fix, but this gets somewhat interesting anyway.

So, this was after running through bl-welcome once, without any changes.
Then, removed /etc/apt/sources.list.d/bunsen.list.
Then restarted the script and received the above error.

However, after a reboot, when I wanted to reproduce it for a shot without the desktop, bl-welcome ran correctly, and the bunsen.list was correctly placed.

johnraff · 2025-10-28 01:30:28

^A bit mysterious. I hadn't yet upgraded bunsen-welcome at that point (pushed just now) so I guess the machine you ran it on hadn't been upgraded for a while and caught last week's package upgrade. The forced restart code went in a year or two ago - if the apt upgrade the script does at the start detects that the script itself might have changed. That could cause errors.

So I don't know why bl-welcome ran correctly yesterday - it should still have had that bug.

sleekmason · 2025-10-28 01:37:44

So I don't know why bl-welcome ran correctly yesterday - it should still have had that bug.

If you are talking about my testing? I'm keeping two versions in Virtualbox. The installed version I began testing on was several days/week? old.

The new version was installed this morning, and I'll do another one to see what the updated script does from a fresh install. Only takes a minute or two to set them up in Virtualbox.

sleekmason · 2025-10-28 01:58:17

^^ Read that incompletely. I'll look again either way:)

sleekmason · 2025-10-28 02:46:44

Just tested bl-welcome on a new install.
Started bl-welcome and ran the upgrade only.
Removed bunsen.list
restarted bl-welcome, ran the upgrade, and the script offered to add it back.
Said yes, and it did, and then ran the rest of the upgrade without issue.

So also tried removing the 'signed by' line on debian backports, and the upgrade ran without issue.

And finally, removed the 'signed by' from bunsen backports just for kicks and grins ... and zero issues there as well.

Looking good currently:)

A few more ways to try, but I think they would have been caught considering everything so far.

Last edited by sleekmason (2025-10-28 03:54:15)

DeepDayze · 2025-10-29 01:34:00

Synaptic package manager seems to choke on deb822.

johnraff · 2025-10-29 01:55:17

^Synaptic does its regular job of listing and installing packages OK.
What seems not to work is the settings>repositories window. So for people who use that to edit their repositories it could be a reason not to "modernize". Just say No™ when the prompt appears.

johnraff · 2025-10-29 06:35:54

johnraff wrote:

NEW TODO
Figure out what to do about imgur not working in the UK.
https://forums.bunsenlabs.org/viewtopic.php?id=9569

Came up here too:
https://forums.bunsenlabs.org/viewtopic … 30#p146630

For now, let's just just tweak our existing bl-imgbb-upload script so the existing screenshot and image uploading utilities go on working using imgbb instead of imgur. Shouldn't take very long.

Later we can make it better...
eg r.chaffee's suggestion: https://forums.bunsenlabs.org/viewtopic … 40#p133040

DeepDayze · 2025-10-29 19:39:06

Imgbb sounds like a great alternative for now at least (for those in UK or other EU countries if the Imgur situation affects them as well down the road).

Last edited by DeepDayze (2025-10-29 19:39:55)

#21 2025-10-23 11:45:30

Re: Carbon TODO

#22 2025-10-24 00:53:42

Re: Carbon TODO

#23 2025-10-25 06:04:55

Re: Carbon TODO

#24 2025-10-25 06:41:34

Re: Carbon TODO

#25 2025-10-25 15:43:01

Re: Carbon TODO

#26 2025-10-26 00:28:26

Re: Carbon TODO

#27 2025-10-26 11:41:21

Re: Carbon TODO

#28 2025-10-27 02:31:46

Re: Carbon TODO

#29 2025-10-27 04:27:36

Re: Carbon TODO

#30 2025-10-27 13:16:18

Re: Carbon TODO

#31 2025-10-28 01:30:28

Re: Carbon TODO

#32 2025-10-28 01:37:44

Re: Carbon TODO

#33 2025-10-28 01:58:17

Re: Carbon TODO

#34 2025-10-28 02:46:44

Re: Carbon TODO

#35 2025-10-29 01:34:00

Re: Carbon TODO

#36 2025-10-29 01:55:17

Re: Carbon TODO

#37 2025-10-29 06:35:54

Re: Carbon TODO

#38 2025-10-29 19:39:06

Re: Carbon TODO

Board footer