Lately i am facing multiple issues with CI pipelines failing on extrepo for instance:

500 Can't connect to extrepo-team.pages.debian.net:443 at /usr/share/perl5/Debian/ExtRepo/Data.pm line 27.

i am seriously considering dropping the use of extrepo which is a shame because i really liked this tool.

dell xps 15 7590 - Kernel Linux 6.12.113+deb13-amd64 - FW. 1.9.1 - gome48 - wayland

i don't know since when it's the case but i just saw that and didn't know why it was like that.

someone else has the same problem? is it debian or gnome and what can i do to fix it if it is even fixable for non os dev?

Hi all,

I'm working on a Linux remaster project and would appreciate some guidance on two points.

Context: I need a base that is minimal yet functionally complete — not as stripped as TinyCore (missing packages, limited app support), and not as bare as Arch (where everything must be assembled manually). The project has two phases: (1) environment preparation — debranding, identity renaming, and DE selection; (2) integrating my own custom tooling,tools that integrate with the system. Keeping phase 1 short is important, since the real value of the project is in phase 2.

Question 1 Base selection:
Is Debian netinst a good fit for this? I understand that netinst is an installer medium rather than a minimal system by itself, and that the resulting system is a fully modifiable Debian install. My question is whether netinst + selective tasksel (no DE, standard utilities only) is a practical starting point for a remaster, or whether starting from debootstrap directly gives a cleaner/smaller rootfs that is worth the extra manual work. Any guidance on package selection to stay lean without leaving the system incomplete would also help.

Question 2 Tooling:

• What tool would you recommend for building/exporting the system as an ISO? I'm considering live-build — are there better-suited alternatives for a custom remaster?
• After producing the ISO, what's the recommended path to a reliable bootable image (hybrid ISO, El Torito, UEFI + BIOS)? Is xorriso/isohybrid sufficient, or is an additional layer needed?

Thanks , any help is appreciated

Hey everyone,

I’ve been hopping around various distros for side projects over the last few years—testing rolling releases, heavily immutabled setups, and shiny new tech. But time and time again, I find myself coming back to Debian for anything that actually matters.

In an era where operating systems are becoming increasingly bloated with forced telemetry, unrequested AI integrations, and snap/container layers forced down our throats, Debian stands out like a beacon of sanity. It just works, respects user sovereignty, and sticks to its Social Contract.

What’s interesting to me is that "Debian Stable being outdated" feels like a myth of the past now. Between Flatpak/AppImage for user apps, Backports for modern kernels/drivers, and Podman/Docker for dev work, Debian Stable is arguably the most modern, rock-solid base anyone could ask for without the fragility of rolling releases.

My question to the community:

As Linux continues to gain desktop market share (especially with Linux gaming booming), do you think Debian should maintain its conservative, "quiet giant" approach, or is there room for the project to actively market its stability and ethics to refugees from Windows/Ubuntu?

Would love to hear your thoughts on how Debian can keep its core identity while welcoming the new wave of Linux users.

Cheers to all the maintainers and contributors who keep the universal OS rockin'!

KDE and Debian on iPhone!

LinuxRunner brings Debian ARM64 to iOS, including desktop environments like KDE Plasma and apps like Blender.

No jailbreak, JIT, or virtualization needed. It runs Linux binaries through an ARM64 interpreter.

Still early in development, but pretty interesting to experiment with. Feel free to try it out!

GitHub: https://github.com/mxhm11cr/LinuxRunner

Just moved my mum who's 79 from her Windows laptop onto Debian with GNOME de and she loves it, just gave her one of my old Lenovo, i7 6th gen with 16gb laptops. Tbf she only really uses Firefox on it but she was happy that it came with Firefox, she signed into her Mozilla account and away she went, prints first time to her wireless printer too which is all good :)

Hello all,

I use Debian on a mostly battle-tested Am4 setup, but paired with a 9060 XT. Since the card only came out in 2025 and was like 2 months old when Debian trixie came out, I wonder if I'm missing out on driver improvements using Debian stable. I played around with the testing and unstable branches in the past, but eventually figured I'm happy with stable, so I'd rather keep it that way.

What I've done so far is install the backported kernel with apt install -t trixie-backports linux-image-amd64 linux-headers-amd64. The installed backports (output of dpkg -l | awk '/^ii/ && $3 ~ /bpo[0-9]/ {print $2}') are:

• libdw1t64:amd64
• libelf1t64:amd64
• libelf1t64:i386
• linux-base
• linux-base-7.2.9+deb13-amd64
• linux-base-amd64
• linux-binary-7.2.9+deb13-amd64
• linux-headers-7.2.9+deb13-amd64
• linux-headers-7.2.9+deb13-common
• linux-headers-amd64
• linux-image-7.2.9+deb13-amd64
• linux-image-amd64
• linux-kbuild-7.2.9+deb13
• linux-modules-7.2.9+deb13-amd64
• linux-sysctl-defaults

But I guess I should also get backported versions of the userland companions of the driver. I'm not entirely sure what packages make sense to get for that. Also, what implications for updating to forky next year do these backports have? Should I continue getting backports once forky is out or use the occasion to go back to pure stable?

I have set my battery to charge to 80% using KDE's settings and somehow it keeps getting reset with the original settings after reboot. This worked fine for the last three weeks so maybe it was a package update.