News that might affect BunsenLabs

DeepDayze · 2025-01-16 16:02:54

johnraff wrote:

^Yes the tint2 dev announced some time ago that there would be no more development.
https://gitlab.com/o9000/tint2
The final release of tint2 is 17.0.2. The code is frozen and no more feature requests are accepted.
Sid is still on 17.0.1 and that has been blocked from Trixie:
https://tracker.debian.org/news/1579766 … m-testing/
If that doesn't get fixed then we'll have to switch to eg xfce4-panel for Carbon.

Or maybe host the last tint2 package in BL repo at least for Carbon?

johnraff · 2025-01-17 02:36:58

^If it will build for us. The reason it's not in Trixie is that it Failed To Build From Source.
Let's hope it's something simple and will soon be put back.

johnraff · 2025-01-19 02:49:02

The Debian Project mourns the loss of Steve Langasek (vorlon)

https://www.debian.org/News/2025/20250117

johnraff · 2025-03-31 06:55:01

Debian 13 "Trixie" Freeze Process Begins
https://lists.debian.org/debian-devel-a … 00011.html
https://www.phoronix.com/news/Debian-13-Freeze-Begins

Head_on_a_Stick · 2025-03-31 14:45:34

Note the release name is "trixie", and is not capitalised. Phoronix mis-spelled it, which is a common error.

Last edited by Head_on_a_Stick (2025-03-31 14:45:51)

johnraff · 2025-04-01 01:28:51

^It's not an "error" to capitalise the names of Debian releases:
https://www.debian.org/releases/
https://wiki.debian.org/DebianReleases

Most people on the Debian mailing lists I look at use upper case for release names most of the time.

Of course in apt sources, and code in general, lower case is required.

Last edited by johnraff (2025-04-01 01:32:13)

Head_on_a_Stick · 2025-04-01 06:19:46

johnraff wrote:

It's not an "error" to capitalise the names of Debian releases

Yes it is :-)

The two links you have given are user-editable pages that have both lowercase and capitalised names.

The official Debian FAQ uses only lowercase for the names: https://www.debian.org/doc/manuals/debi … #codenames

And these messages from Bruce Perens show that he used all lowercase for the original releases:

https://lists.debian.org/debian-devel/1 … 00515.html

https://lists.debian.org/debian-user/19 … 00011.html

johnraff wrote:

Most people on the Debian mailing lists I look at use upper case for release names most of the time

Those people are wrong. I remember Thorsten Glaser (a Debian maintainer) correcting people on the lists in that respect but I can't find the link.

johnraff · 2025-04-01 07:12:49

Head_on_a_Stick wrote:

johnraff wrote:
It's not an "error" to capitalise the names of Debian releases
Yes it is :-)
The two links you have given are user-editable pages that have both lowercase and capitalised names.

The first link is on the official Debian site, and is not user-editable.
Having both upper and lower case names means that upper case is not an error.

The official Debian FAQ uses only lowercase for the names: https://www.debian.org/doc/manuals/debi … #codenames
And these messages from Bruce Perens show that he used all lowercase for the original releases:
https://lists.debian.org/debian-devel/1 … 00515.html
https://lists.debian.org/debian-user/19 … 00011.html

I didn't say upper case was the preferred form, simply that it wasn't wrong. In an English sentence, I think for a proper noun, the capitalized first letter is appropriate.

I remember Thorsten Glaser (a Debian maintainer) correcting people on the lists in that respect but I can't find the link.

Till you find that link I remain totally unconvinced. I'm somewhat familiar with Thorsten Glaser, but anyway an individual DM's condemnation does not official policy make. I'll leave it at that.

hhh · 2025-04-01 12:34:48

The answer is option 1...

https://lists.debian.org/debian-user/19 … 00011.html

And my favorite fact...

https://lists.debian.org/debian-user/19 … 00015.html

hhh · 2025-04-01 17:37:06

At the risk of derailing this thread even further, since this is decidedly NOT news that might affect BunsenLabs, I think these links are a good indication that lowercase code names are not a strict rule...

https://www.debian.org/releases/
https://www.debian.org/devel/debian-installer/
https://www.debian.org/devel/debian-ins … 4/20241231

I did find this, however...

https://live-team.pages.debian.net/live … de.en.html

Debian Live Manual style-guide wrote:

Keep in mind that the proper names of the releases, such as trixie or sid, should not be capitalized when referred to as code names.

Make of it what you will. Open a new thread to continue the discussion, thanks.

johnraff · 2025-04-02 01:15:51

johnraff wrote:

...the tint2 dev announced some time ago that there would be no more development.
https://gitlab.com/o9000/tint2
The final release of tint2 is 17.0.2. The code is frozen and no more feature requests are accepted.
Sid is still on 17.0.1 and that has been blocked from Trixie:
https://tracker.debian.org/news/1579766 … m-testing/
If that doesn't get fixed then we'll have to switch to eg xfce4-panel for Carbon.

Tint2 7.0.1-1.2 is in Trixie as of 2025-03-16.

But the upstream announcement of a development freeze at 17.0.2 still stands, and I think the BL team are agreed we should move to xfce4-panel going forward. The long-standing power management icon issue should go away, and above all, it will continue to work on Wayland.

johnraff · 2025-05-10 07:46:04

Debian Project Leader's monthly report for April

Not news perhaps, but a regular report from Andreas Tille, the current DPL. Interesting for the insights it gives into how Debian handle various issues:
https://lists.debian.org/debian-devel-a … 00001.html

hhh · 2025-05-24 02:04:58

Clement Levefrbrrrrre/Linux Mint "soft forks" libadwaita to enable theming...

https://github.com/xapp-project/libadapta

https://www.osnews.com/story/142412/lin … e-support/

johnraff · 2025-05-24 03:41:53

^That looks like good news! @hhh thanks for digging it up.

Something we can think about for Forky/Nitrogen?

hhh · 2025-05-25 03:09:30

johnraff wrote:

Something we can think about for Forky/Nitrogen?

I have no idea. There are only a few applications so far that have adopted libadapta, as it's brand new...

https://github.com/xapp-project/libadapta-examples

If it works OOTB by adapting GTK3 or 4 as advertised, great.

I'm not even sure what this means yet... "All a theme needs to support libAdapta is a libadapta-1.5 directory with a few CSS files inside of it."

It's promising. libadwaita already obeys Adwaita light and dark modes, (same as Yaru, which is what I chose for the Carbon themes) except for the highlight color, which is stubbornly blue.

I can't remember where that setting is for dark mode. Maybe...

gsettings set org.gnome.desktop.interface color-scheme prefer-dark

... ? Or the same setting via dconf-editor, which is what I use.

Anyway, it's something promising for the future, hopefully.

johnraff · 2025-05-25 04:27:18

Isn't the future sort of closing in on adwaita? Like, while theming's still possible now, maybe not in a release or two?

hhh · 2025-05-25 19:25:37

No idea. IMO, GNOME GTK has sort of screwed itself by being so insular. On the other hand, Qt has screwed itself by having no focus.

BTW, why still two toolkits? Get yourself together, Linux.

Time will tell.

greenjeans · 2025-05-25 23:21:44

That is awesome news! Gnome has really gone off the rails with this nonsense. Have been deleting multiple apps for theme infractions.

Windows wannabe's should really just go to work for microsoft or apple.

100% in agreement with hhh, too many toolkits, it's getting a bit absurd.

johnraff · 2025-06-22 09:38:28

Debian Buster will move to archives
https://lists.debian.org/debian-devel-a … 00001.html

We plan to remove 10/buster from the main and security archives soon, that is in about four weeks or two weeks before a planned Debian 13/trixie release, whichever happens sooner.

johnraff · 2025-07-15 02:51:05

trixie release date

August looks quite likely. Thread to follow:
https://lists.debian.org/debian-release … 00500.html

#261 2025-01-16 16:02:54

Re: News that might affect BunsenLabs

#262 2025-01-17 02:36:58

Re: News that might affect BunsenLabs

#263 2025-01-19 02:49:02

Re: News that might affect BunsenLabs

#264 2025-03-31 06:55:01

Re: News that might affect BunsenLabs

#265 2025-03-31 14:45:34

Re: News that might affect BunsenLabs

#266 2025-04-01 01:28:51

Re: News that might affect BunsenLabs

#267 2025-04-01 06:19:46

Re: News that might affect BunsenLabs

#268 2025-04-01 07:12:49

Re: News that might affect BunsenLabs

#269 2025-04-01 12:34:48

Re: News that might affect BunsenLabs

#270 2025-04-01 17:37:06

Re: News that might affect BunsenLabs

#271 2025-04-02 01:15:51

Re: News that might affect BunsenLabs

#272 2025-05-10 07:46:04

Re: News that might affect BunsenLabs

#273 2025-05-24 02:04:58

Re: News that might affect BunsenLabs

#274 2025-05-24 03:41:53

Re: News that might affect BunsenLabs

#275 2025-05-25 03:09:30

Re: News that might affect BunsenLabs

#276 2025-05-25 04:27:18

Re: News that might affect BunsenLabs

#277 2025-05-25 19:25:37

Re: News that might affect BunsenLabs

#278 2025-05-25 23:21:44

Re: News that might affect BunsenLabs

#279 2025-06-22 09:38:28

Re: News that might affect BunsenLabs

#280 2025-07-15 02:51:05

Re: News that might affect BunsenLabs

Board footer