[DONE] Migration of BL packages to the Carbon repo has started

johnraff · 2024-06-09 09:46:47

Some of the BunsenLabs packages are now available in a newly created "carbon" apt repository, compatible with Debian Trixie. On GitHub, the source code of migrated packages is on newly created "carbon" branches. You will see that there is as yet no difference from the Boron packages, with the one exception of bunsen-meta-all, where some packages are no longer available on Debian Trixie and had to be substituted:

libfuse2 > libfuse2t64
cpufrequtils > linux-cpupower
https://bugs.debian.org/cgi-bin/bugrepo … bug=877016
libblockdev-crypto2 > libblockdev-crypto3
libgtk-3-0 > libgtk-3-0t64
mlocate > plocate
plocate looks better anyway

And xserver-xorg-video-qxl has a bug atm blocking it from arriving in Trixie:
https://tracker.debian.org/pkg/xserver-xorg-video-qxl

There are enough BL packages up there to put together a Trixie/Carbon "base" install - if you want to try, just follow the Boron instructions, but
A) get a Trixie netinstall iso here: https://cdimage.debian.org/cdimage/week … etinst.iso (there are no i386 isos available).
B) of course substitute boron > carbon and bookworm > trixie when editing files.
C) don't use the netinstall script, it's not ready yet You can choose to follow the "USING THE NETINSTALL SCRIPT" or "USING THE METAPACKAGE" instructions.

The remaining BL packages should be up soon are up too, so you can try the full or lite installs too.

Last edited by johnraff (2024-06-27 08:45:02)

Bearded_Blunder · 2024-06-10 01:49:43

So in my usual spirit of trying to break everything, off to setting up I go...

johnraff wrote:

A) get a Trixie netinstall iso here: https://cdimage.debian.org/cdimage/week … etinst.iso (there are no i386 isos available).

Dusted off the ancient ThinkPad (literally), spent a while looking for a 15v power brick of the correct connecter & polarity..
Downloaded the 32 bit iso from here & proceeded to see what b0rkage might ensue...
First of which it wasn't having ANY of booting that image from USB, tried all the methods, resorted to burning an actual disc.
Then it booted.
Remembered that ancient thing needs forcepae as a kernel parameter & booted the installer with it added.
Off to the races
Of course no b43 firmware for the Broadcom WiFi, but being ancient it has ethernet.. duly plugged in.
Seemed to go well the installer (in expert mode) even offered me b43 something, so I thought I'd won.
That specifically spat a ton of errors when I rebooted, ended up installing isenkram-cli & running it.
Now wlan0 finally makes an appearance..

But apt is messed up isenkram added contrib & non-free in sources.list.d/isenkram-autoinstall-firmware.list in spite of them already being in sources.list correctly, might re-run & possibly file a bug, no idea if that happens on 64 bit (yet).

Dillo can't navigate here despite being bookmarked, forum doesn't respond to ping, sending me down the proverbial rabbit hole... only it seems you've got it set not to I find after wondering what was up.

Nothing was up, just had to install firefox-esr.

And xserver-xorg-video-qxl has a bug atm blocking it from arriving in Trixie:
https://tracker.debian.org/pkg/xserver-xorg-video-qxl

as do picom https://tracker.debian.org/pkg/picom (won't build on arm64 or something)

and geany https://tracker.debian.org/pkg/geany (some policy thing & a library)

it'll be nice when the other bunsen-* packages drop....
material-solarized-suruplusplus-icon-theme seems also MIA.

Hehe now just wait for me to try really breaking things..

Last edited by Bearded_Blunder (2024-06-10 01:51:04)

johnraff · 2024-06-10 04:59:56

Thanks - a lot of useful feedback in there!

Bearded_Blunder wrote:

So in my usual spirit of trying to break everything...

People trying to break things is exactly what we need at this stage of development.

Downloaded the 32 bit iso from here & proceeded to see what b0rkage might ensue...
First of which [the ancient ThinkPad] wasn't having ANY of booting that image from USB, tried all the methods, resorted to burning an actual disc.
Then it booted.

I had a hard time trying to get my Panasonic CF-T5 to boot off that mini.iso on a USB stick, but eventually it did. I don't know whether it was a bad USB socket, or a bad copy (I redid with dd) or what, but eventually the stick booted and the installer started to run. (I took it out at that point as I wanted to keep the current Boron install for now.)

One possibly tricky point - if you're trying to check if a USB copy of an iso file is uncorrupted, just doing an MD5sum on /dev/sdc (or whatever) to compare with the sum on the original iso won't match because the usb on /dev/sdc usually has empty space after the iso which affects the checksum. One workaround is to use cmp with its -n option to limit the comparison to the size of the iso:

john@boron:~/downloads/isos/Debian$ iso=debian-13-i386-daily2-mini.iso
john@boron:~/downloads/isos/Debian$ sudo cmp -n "$(stat -c '%s' "$iso")" "$iso" /dev/sdc && echo OK || echo MISMATCH
OK

Of course no b43 firmware for the Broadcom WiFi, but being ancient it has ethernet.. duly plugged in.
Seemed to go well the installer (in expert mode) even offered me b43 something, so I thought I'd won.
That specifically spat a ton of errors when I rebooted, ended up installing isenkram-cli & running it.
Now wlan0 finally makes an appearance..

Built-in b43 firmware is an extra goodie on the iso, thanks to @hhh's work some years ago.
Good to hear that isenkram is actually capable of fixing things. To date I've not had any need for extra firmware that it might find.

But apt is messed up isenkram added contrib & non-free in sources.list.d/isenkram-autoinstall-firmware.list in spite of them already being in sources.list correctly, might re-run & possibly file a bug, no idea if that happens on 64 bit (yet).

That sounds like a bug with isenkram, yes.

Dillo can't navigate here despite being bookmarked

Dillo from Debian has issues with our forum, and with Debian sites. https://forums.bunsenlabs.org/viewtopic.php?id=8285
So I built and lightly patched a fork on GitHub, which is usable again. https://forums.bunsenlabs.org/viewtopic … 46#p124046
https://github.com/BunsenLabs/dilloNG
That version is in the Boron repos and I could push it to Carbon too, but I'm thinking of trying one of the other dillo forks, which have been getting more attention lately. As long as it can be got to build without too much hacking of the original debian packaging...

...forum doesn't respond to ping, sending me down the proverbial rabbit hole... only it seems you've got it set not to I find after wondering what was up.

Little bit of security from ex-webmaster @nobody.

And xserver-xorg-video-qxl has a bug atm blocking it from arriving in Trixie:
https://tracker.debian.org/pkg/xserver-xorg-video-qxl
as do picom https://tracker.debian.org/pkg/picom (won't build on arm64 or something)
and geany https://tracker.debian.org/pkg/geany (some policy thing & a library)

Thanks for catching those. I thought I'd checked over all the packages yesterday.

it'll be nice when the other bunsen-* packages drop....
material-solarized-suruplusplus-icon-theme seems also MIA.

I'll get the other BL packages up ASAP. Hopefully a couple of days. I always seem to have 3 or 4 pots on the stove at once, along with some IRL stuff...

johnraff · 2024-06-10 06:22:12

Picom's bug looks like a build-dependency on another package, maybe now fixed:
https://bugs.debian.org/cgi-bin/bugrepo … ug=1069378
https://bugs.debian.org/cgi-bin/bugrepo … ug=1069408

Geany looks like one of those 64bit time things:
https://bugs.debian.org/cgi-bin/bugrepo … ug=1061346

Fingers crossed that those two get sorted out soon - they're both quite important.

Bearded_Blunder · 2024-06-10 07:02:04

johnraff wrote:

I had a hard time trying to get my Panasonic CF-T5 to boot off that mini.iso on a USB stick, but eventually it did. I don't know whether it was a bad USB socket, or a bad copy (I redid with dd) or what, but eventually the stick booted and the installer started to run. (I took it out at that point as I wanted to keep the current Boron install for now.)

In my case it could even be the USB stick, it's old, & presents as an overgrown 1GB floppy rather than a hdd from a partitioning standpoint, plus the BIOS build date on that ThinkPad is 2004, but it wasn't having any even using dd.

Built-in b43 firmware is an extra goodie on the iso, thanks to @hhh's work some years ago.

Duplicating that little feat was something I was looking at, and embedding a preseed file to result in an unoffical netinstall cd, when things went nutty IRL, & also my home-lab (old HP server) let the blue smoke out... I've not looked since. Though I have backups, just not the spare hardware to restore them to.

Good to hear that isenkram is actually capable of fixing things. To date I've not had any need for extra firmware that it might find.

It certainly did the actual task, little bug aside, which saved some time chasing down what package I actually needed. Seemed the perfect opportunity to see if it actually ever would find anything, for me previously it never had.

I'll get the other BL packages up ASAP. Hopefully a couple of days. I always seem to have 3 or 4 pots on the stove at once, along with some IRL stuff...

I feel that, feels like 2 stoves here, most of it IRL stuff.

Well certainly fingers crossed on picom & geany being fixed soon, though if I had to for the limited occasions I need something more powerful than mousepad, I could transition to scite, which I use in Windows anyway, & has nice syntax highlighting etc.

johnraff · 2024-06-17 07:13:41

Dillo: for now I'll just migrate the dilloNG build from Boron to Carbon, but that project looks abandoned. There are two currently maintained forks which we should choose from IMO:
https://github.com/dillo-browser/dillo
https://github.com/crossbowerbt/dillo-plus

Dillo-browser's developer recently posted to the Debian bug thread that came up some time ago: https://bugs.debian.org/cgi-bin/bugrepo … ug=1022726

johnraff · 2024-06-27 08:40:51

Migration done.
https://forums.bunsenlabs.org/viewtopic.php?id=9041

altman · 2024-06-27 12:46:07

Thx for the hard work to the team.

Bearded_Blunder · 2024-06-28 20:38:02

I'm sure I'll enjoy doing some testing & attempted breakage, once I get clear of the stuff I'm snowed under with.

Looking forward to seeing the fruits of your labour.

jimjamz · 2025-05-18 06:06:04

I attempted a BunsenLabs Carbon Lite install using the meta packages, but ran into an error related to missing dependency packages.

I installed the new Debian Trixie RC1 netinst.
I then applied the bunsen key. After updating apt, I was informed that bunsen-keyring needed to be upgraded.
I then proceeded to install bunsen-meta-lite via apt, but got this error:

Reading package lists...
Building dependency tree...
Reading state information...
Solving dependencies...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

Unsatisfied dependencies:
 bunsen-meta-lite : Depends: dillo but it is not going to be installed
                    Depends: firmware-iwlwifi but it is not installable
                    Depends: firmware-linux but it is not installable
                    Depends: firmware-realtek but it is not installable
                    Depends: intel-microcode but it is not installable
                    Depends: qt5-style-plugins but it is not installable
[1;31mError: [0m[1mUnable to correct problems, you have held broken packages.[0m
[1;31mError: [0m[1mThe following information from --solver 3.0 may provide additional context:
   Unable to satisfy dependencies. Reached two conflicting decisions:
   1. bunsen-meta-lite:amd64=13.0-7 is selected for install
   2. bunsen-meta-lite:amd64 Depends firmware-iwlwifi
      but none of the choices are installable:
      [no choices][0m

johnraff · 2025-05-19 05:44:15

^All those packages should be installable on a Debian Trixie system. Maybe a temporary glitch in the upstream repository?

If the issue isn't fixed by now, try running

apt policy dillo

and likewise with the other packages mentioned. It might give you a hint.

jimjamz · 2025-05-19 13:16:00

I realised that the issue was being caused by Dillo, and after reading in earlier posts that there was some issue with this package, I simply removed Dillo and used a local customised bunsen-meta list to install the packages instead:

apt install --no-install-recommends $( < ./conf/bunsen-meta-custom )

johnraff · 2025-05-20 07:20:00

What was this issue with dillo? It installs OK on my Carbon VM.

Head_on_a_Stick · 2025-05-20 14:59:56

Probably best to avoid dillo anyway: https://bugs.debian.org/cgi-bin/bugrepo … ug=1022726

EDIT: and johnraff is in the bug report. Nice work!

I should have read to the end of the report because the package has just been updated in March. Sorry for the noise but in fairness they should have closed the bug report.

Last edited by Head_on_a_Stick (2025-05-20 15:02:21)

johnraff · 2025-05-21 00:34:45

Dillo has not yet been upgraded in the Debian repos and the bug is rightly still open. (The maintainer is Axel Beckert not Rodrigo Arias.) There are at least two forks in Github and the BL build of 3.1.1 is based on one of those because Debian's 3.0.5-7.1 lacks the TLS support needed to display its own website!

There's a lot to say about dillo in fact, but if anyone wants to discuss it in more detail please open a new thread.
( Recent mention: https://forums.bunsenlabs.org/viewtopic … 09#p135909 )

---
Meanwhile @jimjamz, if you have the time, I would very much like to know what problems you found installing dillo on BL Carbon, because it's an important component of the "lite" package list.

Last edited by johnraff (2025-05-21 00:40:32)

unklar · 2025-05-21 08:23:10

@johnraff,
it's probably still this problem: https://forums.bunsenlabs.org/viewtopic … 39#p141139

johnraff · 2025-05-22 02:25:56

^ @unklar do you still get that issue of dillo being unavailable?
I wonder if you could try again

sudo apt install dillo

and see if it still reports those libraries as being "not installable"? I was presuming it was a bit of Sid instability.

Also, would you and @jimjamz mind posting the output of

apt policy dillo

when you have a moment? Thanks!

jimjamz · 2025-05-22 08:39:36

Sorry for the late reply, I've only just read the replies.
I haven't yet had time to any further investigation since removing Dillon from the list of meta-lite packages and finding that the apt upgrade was then accepted.

I hope to have some free time this weekend to do some more testing.
I'll look at trying to get dillo installed, I will also then try a meta-all upgrade, and will check out the apt policy on dillo.

unklar · 2025-05-22 10:53:36

johnraff wrote:

^ @unklar do you still get that issue of dillo being unavailable?
I wonder if you could try again
sudo apt install dillo
and see if it still reports those libraries as being "not installable"? I was presuming it was a bit of Sid instability.

@johnraff, yes, it is still the case.

the system

inxi -Sxxx
System:
  Host: carbon Kernel: 6.12.27-amd64 arch: x86_64 bits: 64 compiler: gcc
    v: 14.2.0 clocksource: tsc
  Desktop: Openbox v: 3.6.1 with: jgmenu,tint2 tools: light-locker vt: 7
    dm: LightDM v: 1.32.0 Distro: BunsenLabs 13 (Carbon)
    base: Debian GNU/Linux 13

the output

LC_ALL=C apt policy dillo
dillo:
  Installed: (none)
  Candidate: 3.1.1-0.1~bl3
  Version table:
     3.1.1-0.1~bl3 500
        500 https://pkg.bunsenlabs.org/debian carbon/main amd64 Packages
     3.1.1-0.1~bl2 100
        100 https://01micko.github.io/debian carbon-trixie/main amd64 Packages
     3.0.5-7.1 500
        500 https://deb.debian.org/debian trixie/main amd64 Packages

LC_ALL=C apt install dillo -s
NOTE: This is only a simulation!
      apt needs root privileges for real execution.
      Keep also in mind that locking is deactivated,
      so don't depend on the relevance to the real current situation!

Solving dependencies... Error!  
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

Unsatisfied dependencies:
 dillo : Depends: libmbedcrypto7t64 (>= 2.28.0) but it is not installable
         Depends: libmbedtls14t64 (>= 2.28.0) but it is not installable
         Depends: libmbedx509-1t64 (>= 2.28.0) but it is not installable
Error: Unable to correct problems, you have held broken packages.
Error: The following information from --solver 3.0 may provide additional context:
   Unable to satisfy dependencies. Reached two conflicting decisions:
   1. dillo:amd64=3.1.1-0.1~bl3 is selected for install
   2. dillo:amd64=3.1.1-0.1~bl3 Depends libmbedcrypto7t64 (>= 2.28.0)
      but none of the choices are installable:
      [no choices]

-----------------
dillo would be installed on sid(uction) without any problems.

apt policy dillo
dillo:
  Installiert:           (keine)
  Installationskandidat: 3.0.5-7.1
  Versionstabelle:
     3.1.1-0.1~bl2 100
        100 https://01micko.github.io/debian carbon-trixie/main amd64 Packages
     3.0.5-7.1 500
        500 https://deb.debian.org/debian unstable/main amd64 Packages

LC_ALL=C apt install dillo -s
NOTE: This is only a simulation!
      apt needs root privileges for real execution.
      Keep also in mind that locking is deactivated,
      so don't depend on the relevance to the real current situation!

Installing:                     
  dillo

Installing dependencies:
  libfltk1.3t64

Summary:
  Upgrading: 0, Installing: 2, Removing: 0, Not Upgrading: 0
Inst libfltk1.3t64 (1.3.11-2 Debian:unstable [amd64])
Inst dillo (3.0.5-7.1 Debian:unstable [amd64])
Conf libfltk1.3t64 (1.3.11-2 Debian:unstable [amd64])
Conf dillo (3.0.5-7.1 Debian:unstable [amd64])

inxi -Sxxx
System:
  Host: T500 Kernel: 6.14.7-1-siduction-amd64 arch: x86_64 bits: 64
    compiler: gcc v: 14.2.0 clocksource: hpet
  Desktop: LabWC v: N/A with: waybar tools: swayidle vt: 1 dm: SDDM
    Distro: siduction 2024.1.0 shine-on - xfce - (202501132151) base: Debian
    GNU/Linux 13 (trixie)

Last edited by unklar (2025-05-22 11:24:23)

johnraff · 2025-05-23 04:55:14

(dillo install issue) Found it.

Testing being Testing, some libraries had changed and although dependencies in the dillo source code stay the same, the dependencies in the built binary package have changed. ( eg libmbedtls14t64 has become libmbedtls21 )

I built dillo 3.1.1-0.1~bl4 from the same source code as before, and now it installs sucessfully. Uploaded to the repositories, so now 'sudo apt install dillo' should run with no problems.

Thanks to @jimjamz and @unklar for bringing this bug to light.

#1 2024-06-09 09:46:47

[DONE] Migration of BL packages to the Carbon repo has started

#2 2024-06-10 01:49:43

Re: [DONE] Migration of BL packages to the Carbon repo has started

#3 2024-06-10 04:59:56

Re: [DONE] Migration of BL packages to the Carbon repo has started

#4 2024-06-10 06:22:12

Re: [DONE] Migration of BL packages to the Carbon repo has started

#5 2024-06-10 07:02:04

Re: [DONE] Migration of BL packages to the Carbon repo has started

#6 2024-06-17 07:13:41

Re: [DONE] Migration of BL packages to the Carbon repo has started

#7 2024-06-27 08:40:51

Re: [DONE] Migration of BL packages to the Carbon repo has started

#8 2024-06-27 12:46:07

Re: [DONE] Migration of BL packages to the Carbon repo has started

#9 2024-06-28 20:38:02

Re: [DONE] Migration of BL packages to the Carbon repo has started

#10 2025-05-18 06:06:04

Re: [DONE] Migration of BL packages to the Carbon repo has started

#11 2025-05-19 05:44:15

Re: [DONE] Migration of BL packages to the Carbon repo has started

#12 2025-05-19 13:16:00

Re: [DONE] Migration of BL packages to the Carbon repo has started

#13 2025-05-20 07:20:00

Re: [DONE] Migration of BL packages to the Carbon repo has started

#14 2025-05-20 14:59:56

Re: [DONE] Migration of BL packages to the Carbon repo has started

#15 2025-05-21 00:34:45

Re: [DONE] Migration of BL packages to the Carbon repo has started

#16 2025-05-21 08:23:10

Re: [DONE] Migration of BL packages to the Carbon repo has started

#17 2025-05-22 02:25:56

Re: [DONE] Migration of BL packages to the Carbon repo has started

#18 2025-05-22 08:39:36

Re: [DONE] Migration of BL packages to the Carbon repo has started

#19 2025-05-22 10:53:36

Re: [DONE] Migration of BL packages to the Carbon repo has started

#20 2025-05-23 04:55:14

Re: [DONE] Migration of BL packages to the Carbon repo has started

Board footer