Olissipo

joined 1 year ago
sorted by: new top controversial old
Am upgrading from thinkpad to framework 16 with amd. Looking for distro reccommendations. in c/linux@programming.dev
[–] Olissipo@programming.dev 3 points 1 month ago (1 children)

Ok, I understand what you meant, thanks.

Basically, after I’ve read all of that, it’s clear as day that security is not a priority on Testing. And while band-aid solutions do exist, it’s simply not designed to be secure.

Yeah, I wouldn't run it in a production environment.

Am upgrading from thinkpad to framework 16 with amd. Looking for distro reccommendations. in c/linux@programming.dev
[–] Olissipo@programming.dev 1 points 1 month ago (3 children)

Sure, but even in those "few cases" Testing will get them soon.

I did read at some point that Testing may receive security updates later than stable, might be in those cases in which backports come straight from unstable.

Am upgrading from thinkpad to framework 16 with amd. Looking for distro reccommendations. in c/linux@programming.dev
[–] Olissipo@programming.dev 1 points 1 month ago (5 children)

I don’t recommend going for (Debian’s/Devuan’s) testing (branch) as it targets a peculiar niche that I fail to understand; e.g. it doesn’t receive the security backports like Stable does nor does it receive them as soon as Unstable/Sid does. Unstable/Sid could work, but I would definitely setup (GRUB-)Btrfs + Timeshift/Snapper to retain my sanity.

From https://backports.debian.org/ :

Backports are packages taken from the next Debian release (called "testing"), adjusted and recompiled for usage on Debian stable

So by definition, security backports in stable are present in Testing in the form of regular packages, right?

Issue with KDE Plasma 5 and Spotify in c/linux@lemmy.ml
[–] Olissipo@programming.dev 1 points 2 months ago* (last edited 2 months ago) (1 children)

I remember having some issue like that, but I'm not sure if this was the fix.

Try unchecking "Show desktop notifications when the song changes" on Spotify's settings (right now it's under the Display section).

2
Debian 10 LTS reaching end-of-life (www.debian.org)
submitted 2 months ago* (last edited 2 months ago) by Olissipo@programming.dev to c/linux@programming.dev
2 comments fedilink
 

The Debian Long Term Support (LTS) Team hereby announces that Debian 10 "buster" support will reach its end-of-life on June 30, 2024, nearly five years after its initial release on July 6th, 2019.

Starting in July, Debian will not provide further security updates for Debian 10. A subset of "buster" packages will be supported by external parties. Detailed information can be found at Extended LTS.

The Debian LTS Team will prepare afterwards the transition to Debian 11 "bullseye", the current oldstable release. Thanks to the combined effort of different teams including the Security Team, the Release Team, and the LTS Team, the Debian 11 life cycle will also encompass five years. To make the life cycle of Debian releases easier to follow, the related Debian teams have agreed on the following schedule: three years of regular support plus two years of Long Term Support. The LTS Team will take over support from the Security and the Release Teams on August 14, 2024, three years after the initial release on August 14, 2021. The final point update release for "bullseye" will be published soon after the final Debian 11 Security Advisory (DSA) will be issued.

Debian 11 will receive Long Term Support until August 31, 2026. The supported architectures remain amd64, i386, arm64 and armhf.

1
Symfony 7.1.0 released (Symfony Blog) (symfony.com)
 

See new features here (related blog posts list)

1
WooCommerce - weird behaviour and fix (programming.dev)
submitted 4 months ago* (last edited 4 months ago) by Olissipo@programming.dev to c/wordpress@lemmy.world
0 comments fedilink
 

This might not be new, I hadn't dealt with WordPress/WooCommerce in a while.

Currently (v8.8.2) in a new WooCommerce installation the "Checkout" page is created using blocks, like so:

<!-- wp:woocommerce/checkout-payment-block -->
<div class="wp-block-woocommerce-checkout-payment-block"></div>
<!-- /wp:woocommerce/checkout-payment-block -->

(...)

The problem

This might introduce breaking changes to the plugins and themes you normally use. For example, I couldn't add a new field - programatically or using a plugin.

The fix

Remove the blocks and revert to using the shortcode:

[woocommerce_checkout]

1
Symfony 7.0.0 released (Symfony Blog) (symfony.com)
 

Also released Symfony version 6.4.0 (LTS)

See Symfony 7.0.0 / 6.4.0 features here (related blog posts list)