There now is even a debian backport version for emacs-jabber (aka jabber.el) - including omemo support:
If you don't know debian backports yet:
There now is even a debian backport version for emacs-jabber (aka jabber.el) - including omemo support:
If you don't know debian backports yet:
SeaGL talks in 30 min:
* Resist Tech Monopolies: Community Photo Hosting
* Kernel backport automation and validation in CentOS/RHEL
* Observability is for the Frontend, Too!
A half hour later:
* Patch management / BareMetal as a service on Linux ( RedHat / Suse /tbd other ) Windows? Vmware?
https://pretalx.seagl.org/2025/talk/
#SeaGL #SeaGL2025 #FLOSSconf #FLOSSevent #Seattle #today #PeerTube #DateTime #ke
rnel #backport #LibreGraphics
Impatient to get a #Backport of #Dino 0.5 for #Debian #Bookworm
... but the build logs were already published, including the hashes of all the binaries, I went ahead and performed a #ReproducibleBuilds check of locally built packages for amd64, arm64 and the "all" architecture... and came up with bit-for-bit identical results!
https://people.debian.org/~vagrant/dino-im-reproduced/
By the time you read this, identical binaries may already land on the Debian archive. I have a newer dino installed now! Try for yourself!
So I am on #debian stable (#bookworm) using the #xfce desktop.
Today the #xfce4-weather-plugin stopped working. This was due to a change upstream that the xfce developers had already fixed in version 0.11.3 but #debian doesn't have that version yet.
So I spent a bit of time to create my own #backport package by downloading the .dsc file and source, adding the fixes to the source, updating the .dsc file to match changes and hashes, then compiling to a .deb file via a docker baseline image (so I don't taint my main install).
Took a few attempts to work through this to get it working as I was trying to also adjust libsoup version but that wasn't required (yet) and just added complication.
Anyway, 30 minutes later I now have a working weather panel applet, as crucially this is a #bpo .deb file and properly installed so can be upgraded by #debian if and when the time comes.
@cwansart IMO, the answer is no, as it depends more on many other factors. E.g. I have seen often enough that things are sometimes no longer fixed in #debian. It could even be that with rolling releases you get a fix earlier than the #backport for an #lts version is ready.
Of course, #distribution also plays a role, but I think it is more important to keep the #attackvectors as low as possible, i.e. to keep the system as minimal as possible. Fewer packages mean fewer potential #vulnerabilities.
@Cfkschaller How crazy and/or how much of a non-starter this idea would even be:
RHEL Workstation's desktop components as an application stream.
The core motivation here is to enable RHEL customers to use the latest Workstation environment on older RHEL versions (within logistical and practical reasoning). For example, GNOME 47 from RHEL 10 available for installation on RHEL 9.
#RedHat #RHEL #Workstation #Desktop #Backport #Module #GNOME #GNOMEShell #AppStream #ApplicationStream
A question for #Debian users. Would you subscribe to backports for something as recent as bookworm ? Trying the polling option on here !