News that might affect BunsenLabs

jeffreyC · 2022-10-06 00:31:16

johnraff wrote:

It's a pity that the SF interface doesn't show what file that big button will bring in

Many times I have seen on those buttons where it does show what file it downloads, but I do not know if you can change it to make it happen or it is something SF does on their own.

johnraff · 2022-10-09 02:46:55

The Debian Firmware discussion continues

Getting down to the techy details here:
https://lists.debian.org/debian-boot/20 … 00044.html

johnraff · 2022-10-10 07:30:46

Fedora contemplates the driverless printing future

Changes have come to the printing world. Most new printers can be accessed directly via WiFi from a smartphone, and if you set it up on your router, from a PC too. No printer drivers need to be installed at all. If you don't want a WiFi connected printer, from Debian Bullseye you can install ipp-usb and go driverless via USB.

In Beryllium bunsen-meta-printer-support already recommends ipp-usb, and today I just noticed sane-airscan and added it too, to go in the next package upgrade. It's supposed to help with scanning on these new "IPP" printer/scanners (although my Canon seemed to scan OK without it).

There's a lot more on this subject on lwn:
https://lwn.net/Articles/857502/

lwn wrote:

There will need to be a lot of work and testing done if the first distributions that release with CUPS 2.4 are to not break vast numbers of printing setups. If that can be done, though, perhaps printers can finally join modems as devices that simply work without the need for a lot of messing around.

Also, on the Debian Wiki:
https://wiki.debian.org/CUPSDriverlessPrinting

johnraff · 2023-01-28 02:46:26

Debian add new repo component: non-free-firmware

From Debian Bookworm, there will be a new apt repository component added to main, contrib and non-free:
non-free-firmware

The idea is that users who need non-free firmware - nearly everybody these days - can get it without having to enable everything else in the non-free section.

So BunsenLabs Boron will eventually ship with that component enabled too. Non-free will remain, but users will be able to disable it without losing their firmware.

https://wiki.debian.org/Firmware
https://lists.debian.org/debian-boot/20 … 00150.html

johnraff · 2023-02-01 08:29:32

merged usr in bookworm

https://forums.bunsenlabs.org/viewtopic … 55#p123255

we still don't know if merged usr will be compulsory for Bookworm or not

Now we know, it is.

And dpkg puts out scary warnings:

Unpacking dpkg (1.21.19) over (1.21.18) ...
Setting up dpkg (1.21.19) ...
dpkg: warning: This system uses merged-usr-via-aliased-dirs, going behind dpkg'
s
dpkg: warning: back, breaking its core assumptions. This can cause silent file
dpkg: warning: overwrites and disappearances, and its general tools misbehavior
.
dpkg: warning: See <https://wiki.debian.org/Teams/Dpkg/FAQ#broken-usrmerge>.

This isn't the unanimous opinion of the whole Debian project of course.

For now, the impression I get is we have to keep our heads down till the shooting stops...

hhh · 2023-02-03 03:21:03

I haven't gone through the thread, so maybe not new news.

That said, the first freeze of Bookworm (the toolchain freeze) has already happened, and the soft freeze is already less than two weeks away...

https://lists.debian.org/debian-devel-a … 00006.html

In light of this, I doubt there will be any development added to Beryllium, @johnraff and I will concentrate all our attention to Boron instead.

Any forum members who would like to add their efforts to the Boron release, please post here and we'll create a new topic from the feedback.

Thanks for your continued support of BunsenLabs, everyone! BunsenLabs, where the future is being made today.

https://www.youtube.com/watch?v=OVnmIbzExOA

LOL, bicycle pump.

cog · 2023-02-03 07:39:34

Please see my steelhead (testing) branch of hatchery for bookworm "surprises" LOL. Hope to help cross pollinate your efforts. BTW I'm using the latest live-build built from salsa.debian.org

Obviously the live build is straight forward, fishbones-live is what I use to manage skel and stuff on the live session.

https://bitbucket.org/troutcobbler/hatc … steelhead/

https://bitbucket.org/troutcobbler/fish … steelhead/

hhh · 2023-02-03 08:02:41

Thanks for all of that! Surprises!

cog · 2023-02-03 08:04:19

Excellent. That new live-build package is paramount too.

cog · 2023-02-03 08:23:23

Calamares for GUI install is way cooler than the GTK2 debian-installer version. It's worth a look-see.

johnraff · 2023-02-05 06:21:43

Refers to the merged-user thing I guess?

hhh wrote:

I haven't gone through the thread, so maybe not new news.

No it's not new news, but the scary dpkg message will be new for BL users playing with Boron. (The Boron packages are in the repo now and as soon as bl-welcome is up to date I'll make an announcement.) In fact, the message when dpkg is updated was silenced for Debian users at dpkg 1.21.7:

dpkg.postinst wrote:

# In Debian some people have gotten so offended by the following _warning_
# that they have resorted to bullying and abuse. Life's too short, sorry.

But BunsenLabs users will see it, as I did, because we set $vendor to BunsenLabs.

The decision to make /bin, /lib, /lib32, /lib64, /libx32 and /sbin into symlinks to /usr/bin etc as the default setup from bookworm onwards was made by the Debian Technical Comittee, but the main dpkg developer strongly disagrees.

Dpkg is a key component of the Debian system and this situation is unfortunate to say the least. Let's hope something eventually works out.

---

That said, the first freeze of Bookworm (the toolchain freeze) has already happened, and the soft freeze is already less than two weeks away...
https://lists.debian.org/debian-devel-a … 00006.html
In light of this, I doubt there will be any development added to Beryllium

"Bugfixes only" would get my vote.

@johnraff and I will concentrate all our attention to Boron instead.

In fact, in view of the approaching release date, I think we should keep improvements to Boron to a minimum too - things that can be applied without big code base upheavals. That way we should have a good chance of getting Boron released more-or-less in sync with Debian Bookworm.

There are things coming up on the horizon, but if we can get Boron out soon, we should then have a good year or more to get them sorted in time for Carbon.

Any forum members who would like to add their efforts to the Boron release, please post here and we'll create a new topic from the feedback.

So when the Boron development packages announcement is made, we should also start a suggestions topic. This is the point in the development cycle when community members can make the biggest contribution to the project, even if some ideas will more likely go in Carbon than Boron.

johnraff · 2023-02-05 06:29:22

@cog thanks for all that input. We should indeed share ideas and discoveries.

Live-build has had a lot of attention the last year or two and the new release 1:20230131 has a lot of improvements.
Some of the hacks we previously used can now probably come out.

Calamares didn't look too good at first to be honest, and I'm still wondering how much time I should put into configuring it compared with continuing to rely on the Debian Installer. What kind of things did you like about it?

johnraff · 2023-02-05 07:48:25

deb822-sources in debian:bookworm container images

https://lists.debian.org/debian-devel-a … 00000.html

So the new deb822-sources format moves closer to mainstream. It's easier to read or edit, for humans and machines, and will eventually become the default. The old single-line format will likely be supported for a long time to come though.

For BL, something for Carbon maybe, unless live-build supports it in time for Boron.

Last edited by johnraff (2023-02-05 07:51:16)

johnraff · 2023-02-05 09:35:16

Please post issues with Debian Bookworm (as opposed to Linux news) in this new thread:
Bookworm/Boron issues

Last edited by johnraff (2023-02-08 01:03:11)

johnraff · 2023-02-08 01:05:01

The European chat control law could block the functioning of open source operating systems

Worrying, if only because of the lack of understanding in high EU government that it shows.

https://lists.debian.org/debian-project … 00004.html

https://mullvad.net/en/blog/2023/2/1/eu … g-systems/

hhh · 2023-02-08 03:57:31

^ Meh, it's like the US net neutrality kerfuffle. Just carry on, the laws will catch up when they do. They are not coming for a small Japanese-ish open source deer hunter. And if they do, post that stuff until it goes viral. You'll win with a settlement.

jeffreyC · 2023-02-08 06:17:12

The full implications of that make Brexit look like it was an act of genius.

cog · 2023-02-09 01:35:37

@johnraff, sounds good.

This is only comparing the d-I gui version, I’m using the cli version and calamares. Calamares can be an install option within live-session and not just from the boot menu. It’s using a more modern toolkit, qt5 instead of gtk2, you can really do anything you want with the modules. D-I is hard to customize. It’s a simple install process and similar to ubuntus or something. Worth a look see. You really need to have calamares and d-I both to get it to work right, with shiny new live-build.

hhh · 2023-02-15 06:42:47

The CrunchBang forums are officially dead...

https://crunchbang.org/forums/

I thought they had been archived for the last 7 years or so, but no more.

jeffreyC · 2023-02-15 14:06:23

hhh wrote:

The CrunchBang forums are officially dead...
https://crunchbang.org/forums/
I thought they had been archived for the last 7 years or so, but no more.

Not entirely surprised by that.

There were a lot of posts deleted over the years making huge gaps.

#221 2022-10-06 00:31:16

Re: News that might affect BunsenLabs

#222 2022-10-09 02:46:55

Re: News that might affect BunsenLabs

#223 2022-10-10 07:30:46

Re: News that might affect BunsenLabs

#224 2023-01-28 02:46:26

Re: News that might affect BunsenLabs

#225 2023-02-01 08:29:32

Re: News that might affect BunsenLabs

#226 2023-02-03 03:21:03

Re: News that might affect BunsenLabs

#227 2023-02-03 07:39:34

Re: News that might affect BunsenLabs

#228 2023-02-03 08:02:41

Re: News that might affect BunsenLabs

#229 2023-02-03 08:04:19

Re: News that might affect BunsenLabs

#230 2023-02-03 08:23:23

Re: News that might affect BunsenLabs

#231 2023-02-05 06:21:43

Re: News that might affect BunsenLabs

#232 2023-02-05 06:29:22

Re: News that might affect BunsenLabs

#233 2023-02-05 07:48:25

Re: News that might affect BunsenLabs

#234 2023-02-05 09:35:16

Re: News that might affect BunsenLabs

#235 2023-02-08 01:05:01

Re: News that might affect BunsenLabs

#236 2023-02-08 03:57:31

Re: News that might affect BunsenLabs

#237 2023-02-08 06:17:12

Re: News that might affect BunsenLabs

#238 2023-02-09 01:35:37

Re: News that might affect BunsenLabs

#239 2023-02-15 06:42:47

Re: News that might affect BunsenLabs

#240 2023-02-15 14:06:23

Re: News that might affect BunsenLabs

Board footer