You are not logged in.
Some day soon I need to take a look at whether live-build has caught up with DEB822....
Bug report about DEB822:
https://bugs.debian.org/cgi-bin/bugrepo … ug=1032131Roland Clobus Wed, 22 Jan 2025 wrote:It will take some effort to migrate to deb822 for d-i, and additionally live-build needs to migrate to deb822 as well.
And very little after that...
And a placeholder bug report for live-build:
https://bugs.debian.org/cgi-bin/bugrepo … ug=1110886
So no DEB822 in Trixie debian-installer or live-build, and BL will have to try to do something with scripts or hooks.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
@johnraff you can do it with preseed.cfg . That’s what I did. Not ideal but it works.
Offline
^Thanks cog, I saw your solution a while ago and will probably use something like that - maybe a linked script instead of putting all the commands in preseed.cfg.
Of course a live-build hook (as I suggested yesterday) won't work because it has to happen at install time, not iso-build time. The Debian-Installer sets up apt sources then.
I was also wondering about wrapping a script around 'apt modernize-sources'.
Since for BunsenLabs there's no queston of choosing a mirror, it might work to hard-code that part - including "signed-by" - while leaving the Debian sources under apt's control. Even the Debian sources will need modernizing though, because the D-I doesn't yet know about deb822.
It might be OK to make a modern deb822 sources file for BL and ship it in the squashed filesystem in the iso. Some testing will be needed...
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
The trixie 13.0 installer doesn't leave any sources at all, see https://forums.debian.net/viewtopic.php?t=163399 for more on this.
I've used this in preseed.cfg:
d-i preseed/late_command string printf 'Types: deb\nURIs: http://deb.debian.org/debian/\nSuites: trixie trixie-updates\nComponents: main contrib non-free non-free-firmware\nSigned-By: /usr/share/keyrings/debian-archive-keyring.gpg\n\nTypes: deb\nURIs: http://deb.debian.org/debian-security/\nSuites: trixie-security\nComponents: main contrib non-free non-free-firmware\nSigned-By: /usr/share/keyrings/debian-archive-keyring.gpg' > /target/etc/apt/sources.list.d/deadbang.sources ; in-target apt updateIt's basically the same as cog's solution.
EDIT: that didn't work because the late_commands use the busybox version of printf. Oops.
Trying this instead (with the deadbang.sources file added to config/includes.installer/):
d-i preseed/late_command string cp deadbang.sources /target/etc/apt/sources.list.d/deadbang.sourcesLast edited by Head_on_a_Stick (2025-08-31 19:05:36)
Offline
^ Debian bug: https://bugs.debian.org/cgi-bin/bugrepo … ug=1110717
It seems to be about whether User enables a mirror during installation or not.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
Thank you sir!
This is strange though because I set the mirror manually in the preseed file. I think I'll just drop those lines and copy the sources file directly into the system, that way deadbang will be DEB822-compliant from the trixie release.
Last edited by Head_on_a_Stick (2025-09-01 06:28:57)
Offline
Sorry, I missed this at the time:
Actually, I'm not a friend of Trixi/sid(Testing).
I expect this was a typo, but Sid is not "Testing", it's "Unstable". When that was written, Trixie was Testing, but now Testing is Forky, and Trixie is Stable. Sid is always Unstable.
I think Head_on_a_Stick already discussed the differences between Testing and Unstable. Some people prefer Unstable over Testing because although it breaks more often, fixes usually come in quickly.
Personally, I'm a fan of Stability. ![]()
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
@johnraff, nice job creating banners and walls for carbon. I'll have to GIMP up some images myself, but I want to point out the BL logo. I want to erase the mistake that I made on boron, using the wrong typeface. It should be two fonts, like the original...
https://en.wikipedia.org/wiki/File:Buns … -flame.svg
Only with the flame centered over the "l" to make a Bunsen burner. The forum has it right...
https://forums.bunsenlabs.org/img/bl.svg
Please bring back this logo.
I don't care what you do at home. Would you care to explain?
Offline
^You're talking about the installer here, right? In particular logo_debian.png in includes.installer/usr/share/graphics/ ?
I threw in a hastily-made image just hacked from what went in Boron, hoping that some day you'd make something nice for us. Note though, that the flame isn't above the l at all because the image is very long and thin (800 x 75). Perhaps it needs redoing from scratch.
"walls" though? What are you referring to there? The splash.png background of the boot login menu? That's @micko's work. We had a discussion about it a while ago but for the life of me can't find it now. @micko01?
(btw if we shift to sage instead of bark as default, those colours will have to change to match.)
Please bring back this logo.
Where?
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
Well, we have done desktop walls with logo and without, so I think those logo walls should be created. Grub screen, installer, these are secondary but should also be consistent regarding the logo.
I don't care what you do at home. Would you care to explain?
Offline
^You're talking about the installer here, right? In particular logo_debian.png in includes.installer/usr/share/graphics/ ?
I threw in a hastily-made image just hacked from what went in Boron, hoping that some day you'd make something nice for us.
Roger that.
I don't care what you do at home. Would you care to explain?
Offline
Well, we have done desktop walls with logo and without, so I think those logo walls should be created. Grub screen, installer, these are secondary but should also be consistent regarding the logo.
Right now we've got pawel-czerwinski-bark.png and pawel-czerwinski-sage.png here:
https://github.com/BunsenLabs/bunsen-im … rs/default
Would you like to make versions of those with a logo?
(Possibly move the Ruby variants out of -base?)
Can't really do any more work on the grub screen till default bark vs sage is decided.
But on my lo-res VM I found the grub boot logo was in the wrong place:
This file: https://github.com/BunsenLabs/bunsen-im … efault.png
Could right in the centre be safe?
Or just raise the logo up a bit so it's in that dark area?
Last edited by johnraff (2025-10-29 03:06:02)
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
^Centre I think. And since it's the grub screen no need of transparency in the writing, just a solid bark colour will do. On my ToDo for tomorrow.
#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen
Online
Thanks! In view of what looks like the majority support for sage I guess the image source will have to be changed to the sage wallpaper.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
^ That's a pretty small poll. Regardless, I'll spin some walls soon.
I don't care what you do at home. Would you care to explain?
Offline
+1 to moving the Ruby walls out. My preference is to strip all the previous walls into extra packages (the redundancy of different wall resolutions in our old images is unnecessary, IMO).
Slap a basic resolution wall selection in there, one resolution from each previous release, plus cog's wallpapers, done.
I don't care what you do at home. Would you care to explain?
Offline
I just installed the alpha on my wife's new Linux ASUS Vivobook.
The USER opens a system file with Geany (e.g., fstab). Then, “Open with root” is selected in the menu. After entering the root password, Geany is “superimposed” over the USER's Geany. There is no color difference(!). Only moving it with the mouse reveals the risk of root editing.
ALL suggestions from the bl-welcome-script (except dev packages) were accepted and executed.
Unfortunately, after restarting, the ‘battery/computer icon’ in the bar has been replaced with a “not available” icon again.
Edit: Correction.
After ‘waking up’, the battery icon is there. ![]()
Last edited by unklar (2025-10-31 11:32:43)
Offline
I've got images for default.png (grub) for bark and sage:
I couldn't find the image I overlaid on the original bark but it's close enough. Also bark is a bit busier in the centre than sage.
I think that either is ok for the grub screen.
#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen
Online
^ Sweet logo.
Nice fonts.
Gotta move it for Bark a bit up and right so it reads better but stays away from the grub text that will be there. Into the armpit.
For a sage grub splash, I'd say that's pretty near to perfect.
I don't care what you do at home. Would you care to explain?
Offline
Ha! I tried to color-shift the sage grub to get something bark-ish, but I guess the colors are indexed because I just ended up with slightly psychadelic sage. The name of my new band, when I form one.
Slightly Psychadelic Sage, presented by Acetylsalicylic Acid...
I like it. I has a whole Alien vibe going on. "In sage, no one can hear you scream."
Last edited by hhh (2025-11-01 03:26:54)
I don't care what you do at home. Would you care to explain?
Offline