Containerized Debian package builds, artifact diffs, and automated maintenance, test running, new upstream imports and more. If you previously struggled with .deb work, this might make things a lot easier now.

I have two Debian 13 (Trixie) (13.7) machines, both tell me they are up to date, but first one tells me:

vstubbs@infinity:~ $ php -v
PHP 8.4.24 (cli) (built: Jul 31 2026 05:11:11) (NTS)
Copyright (c) The PHP Group
Built by Debian
Zend Engine v4.4.24, Copyright (c) Zend Technologies
    with Zend OPcache v8.4.24, Copyright (c), by Zend Technologies

this machine has a debian.sources file of:

vstubbs@infinity:~ $ cat /etc/apt/sources.list.d/debian.sources

Types: deb deb-src
URIs: https://deb.debian.org/debian/
Suites: trixie
Components: main non-free-firmware contrib non-free
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

Types: deb deb-src
URIs: https://security.debian.org/debian-security/
Suites: trixie-security
Components: main non-free-firmware contrib non-free
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

Types: deb deb-src
URIs: http://deb.debian.org/debian/
Suites: trixie-updates
Components: main non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

second one tells me:

vstubbs@overwatch:~ $ php -v
PHP 8.4.27 (cli) (built: Oct 21 2026 07:53:46) (NTS)
Copyright (c) The PHP Group
Built by Debian
Zend Engine v4.4.27, Copyright (c) Zend Technologies
    with Zend OPcache v8.4.27, Copyright (c), by Zend Technologies

this machine has a a sources.list file of:

vstubbs@overwatch:~ $ cat /etc/apt/sources.list

#deb cdrom:[Debian GNU/Linux 13.4.0 _Trixie_ - Official amd64 NETINST with firmware 20260314-11:53]/ trixie contrib main non-free-firmware

deb http://mirror.csclub.uwaterloo.ca/debian/ trixie main non-free-firmware
deb-src http://mirror.csclub.uwaterloo.ca/debian/ trixie main non-free-firmware

deb http://security.debian.org/debian-security trixie-security main non-free-firmware
deb-src http://security.debian.org/debian-security trixie-security main non-free-firmware

# trixie-updates, to get updates before a point release is made;
# see https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports
deb http://mirror.csclub.uwaterloo.ca/debian/ trixie-updates main non-free-firmware
deb-src http://mirror.csclub.uwaterloo.ca/debian/ trixie-updates main non-free-firmware

# This system was installed using removable media other than
# CD/DVD/BD (e.g. USB stick, SD card, ISO image file).
# The matching "deb cdrom" entries were disabled at the end
# of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.

They both used to point to the Canadian mirror, but when the first one refused to update PHP, I changed the first one to the main repository source but that didn't help.

This is driving me absolutely crazy, the machines are on the same network, same switch, same router. the only difference between them is one has 48GB of memory the other has 16GB memory, and the first one runs docker the second one doesn't, but that shouldn't matter...should it?

TIA...your very thankfully the insane ;-)

If anyone still (like me) neeed old Debian systems running I made backports for a number os combinations
Best regards to all Debian users

https://git.iscsp.ulisboa.pt/trincheiras/php-cve-2026-109618-cve-2026-109619

Hi All,
Version: Bullseye
Im maybe missing something.... But today I go to update and and get all sorts of errors.

Included the pics I have of sources list and the update result.
Is something up with that IP address.

Im happy to update it all the the newest version but this has me lost.
Apologies Debian isnt my main language.

Can anyone help ?

Edit: Sorry for my crap spelling but was rushing... "Debian"

Thanks.

I know that this is not necessary and interesting for everyone, but... how will things be on Debian? Will the anti-cheat work with Nvidia dkms driver from nvidia cuda?

My goal is to make a partition of my ssd in the Debian installation usb. I cannot do it in windows.

Usually, this would just be selecting “manual” as the format when setting up the disk, but when I do that, only the usb flash drive itself shows up, and not the ssd itself. I tried going into busybox and using fdisk but that didn’t work, and neither did cfdisk or part.

After I partition it, I will use the free partition to install Debian and dual boot windows

I've been trying to setup unattended-upgrades to update tailscale along with the rest of the system. However whenever I try doing a dry run it doesn't seem to catch it even though I checked and made sure an upgrade is needed at the moment.

Here's my current config for sources.

Unattended-Upgrade::Origins-Pattern {

// Codename based matching:

// This will follow the migration of a release through different

// archives (e.g. from testing to stable and later oldstable).

// Software will be the latest available for the named release,

// but the Debian release itself will not be automatically upgraded.

"origin=Debian,codename=${distro_codename}-updates";

// "origin=Debian,codename=${distro_codename}-proposed-updates";

"origin=Debian,codename=${distro_codename},label=Debian";

"origin=Debian,codename=${distro_codename},label=Debian-Security";

"origin=Debian,codename=${distro_codename}-security,label=Debian-Security";

// "o=Debian Backports,n=${distro_codename}-backports,l=Debian Backports";

"origin=https://pkgs.tailscale.com/stable/debian ,codename=${distro_codename},label=tailscale"

Any help is appreciated.

Hey everyone, does anyone else experience a bug on Debian 13 Stable where characters keep repeating/getting stuck as if the key is still pressed?

This happens with both the laptop's built-in keyboard and Bluetooth keyboards. I've noticed this issue specifically on Debian, while other distributions with the exact same hardware don't have it. The bug is intermittent and only happens sometimes.

System Specs:

OS: Debian GNU/Linux 13 (trixie) x86_64

Host: Dell Latitude 3420 (Intel i7-1165G7)

DE/WM: GNOME / Mutter (Wayland)

Kernel: Linux 6.12

Has anyone run into this or know how to fix it?