The post discusses various topics in the tech and Linux community, including VPN usage, user accounts on computers, and recent news like Arch Linux disabling AUR package adoption to counter malware, upcoming features in Ubuntu 26.10, and Sony's response to backlash regarding PlayStation discs. It also mentions community activities and participant project links.

Dear Tumbleweed users and hackers,

This week saw the release of 5 snapshots (0723, 0724, 0726, 0728, and 0729).

A major milestone was reached as GCC 16 has officially landed as Tumbleweed’s new default system compiler in snapshot 0726. Because this transition required rebuilding the entire repository to benefit from the new compiler optimizations, snapshot 0726 was exceptionally large. Along with this compiler shift, the linux-glibc-devel 7.1 headers successfully made their way to users in snapshot 0728.

Additionally, we saw the return of multipath-tools 0.15~1 in snapshot 0726 after its brief “yo-yo” revert last week.

These 5 snapshots delivered the following updates:

• GCC 16 as the default system compiler
• linux-glibc-devel 7.1
• Mozilla Firefox 153.0
• systemd 261.2
• OpenSSH 10.4p1
• multipath-tools 0.15~1
• ntfs-3g_ntfsprogs 2026.7.7
• btrfsprogs 7.1
• python-numpy 2.4.6
• java-25-openjdk 25.0.4.0
• AppStream 1.1.5
• freerdp 3.30.0
• bind 9.20.26
• cryptsetup 2.8.7
• virtualbox 7.2.14
• wicked 0.6.80
• util-linux 2.42.2
• fwupd 2.1.7
• libostree 2026.2
• rpmlint: enforce whitelisting for capabilities in SUIDPermissionsCheck via bugreports

With these updates successfully rolled out, it is time to turn our gaze forward and see what the staging areas are cooking up for the near future.

• Podman 6.0.0: Undergoing integration and sync testing with buildah and skopeo.
• Linux Kernel 7.1.5
• Mozilla Firefox 153.0.1
• Samba 4.24.5
• PHP 8.5.9
• python-Sphinx 9.1.0: This update is currently breaking python311:doc and python312:doc.
• glibc 2.44

The author describes a journey of upgrading their home office setup, initially using a six-monitor rig with inadequate screens. They found improvements in an LG DualUP monitor and decided on a dual setup using INNOCN displays to enhance productivity. Despite some connection issues and pixel density discrepancies, the new layout significantly increased usability and desk efficiency.

🚢 Shipped this week Fixed issues, small features, security updates, minor releases, new external contributors… de-group when filter_search_text on top of filter_labels - #20097 Fix overlapping labels on image template radio buttons - #19931 make it visually clear that attributes are expandable - #19984 Fix backlog link for users in beta - #20092 Do not link hidden monitor workers to build logs - #20023 Reject release targets that point back to the same repository -...

For many years, I didn’t think that Tor could be useful for me. However, I’ve recently found a Gist on GitHub that describes how you can use it to harden your central syslog-ng server. And while I have yet to try it, at least now I have a reason to actually test Tor.

The Tor website describes the project as follows: “Protect yourself against tracking, surveillance, and censorship.” I live in a country where thankfully I do not need these, nor do I perform any activities for which Tor would be useful. However, sometimes I hear from syslog-ng users that they want to hide their logging infrastructure with something more than what mutual TLS authentication makes possible. This is where this short how-to might be useful for you:

https://gist.github.com/hashgh0st/19bcfa4bfc96fbf0bbd2897b66c77db7/

The Gist is about how to install / configure syslog-ng and Tor on a FreeBSD client and server. I have a couple of FreeBSD boxes lying around, so I will test the instructions there. However, with minimal changes, the procedure should work on any Linux distribution as well.

Originally published at https://www.syslog-ng.com/community/b/blog/posts/syslog-ng-hardening-using-tor

🚢 Shipped this week Fixed issues, small features, security updates, minor releases, new external contributors… Unify release API parameter naming and document it#20054 BSPublisher/Registry: support the cosign newbundle format#20026 PBuild: Fix auth for multiple remote registry assets#1162 Make obs-service-kiwi_metainfo_helper use BUILD_BUILDTIME#1367165 👩‍💻 Operations this week Statistics, deployments and incidents of https://build.opensuse.org/ In the last 7 days build.opensuse.org served 25.3 million HTTP requests resulting in 2.45 million package builds. With ~200.000 builds more than last week...

The content discusses various technology and Linux-related updates, including a live weekend discussion about user experiences with Fedora and job openings at Epic Games focused on Linux security. It also covers IBM's new chip architecture advancements and Dell surpassing HP in U.S. PC sales amid a shrinking market.

Back when I was working at Canonical on the Ubuntu phone project, test-driven development was the default and natural way to work. One thing I noticed and genuinely liked was how Ubuntu and Debian ship functional tests alongside many of their packages. Not only build-time unit tests hidden in the CI pipeline, but installable test binaries that you can run against the actual packages on an actual system. They are named *-tests or *-test, and they live in the archive next to the production packages.

The author praises the atomic update-like mechanism integrated within openSUSE Tumbleweed, highlighting its reliability and user-friendliness. This method effectively combines the flexibility of traditional updates with the stability of atomic ones, ensuring minimal disruption during software installations. The experience has greatly improved daily Linux usage, appealing to both novice and experienced users.

Dear Tumbleweed users and hackers,

This week was quite busy and successful, with 6 snapshots (0716, 0717, 0718, 0720, 0721, and 0722) published to our users.

From last week’s outlook, we successfully checked off three major updates: KDE Plasma 6.7.3, systemd 261.1, and Perl 5.44.0 are now in your hands.

We also had a brief “yo-yo” moment with multipath-tools. In snapshot 0720, we upgraded it to version 0.15~1, which enabled asynchronous path checkers by default and deprecated some options. This quickly turned out to cause some integration ripples, so in snapshot 0721 we chose safety first and reverted back to version 0.14.3.

These six snapshots delivered the following updates:

• KDE Plasma 6.7.3
• systemd 261.1
• Perl 5.44.0
• Linux Kernel 7.1.4
• Wayland 1.26.0
• firewalld 2.3.2
• Mozilla Firefox 152.0.6
• Python 3.13.14
• Ruby 4.0.6
• Mesa 26.1.5
• libzypp 17.38.14
• libupnp 22.0.4
• ipxe 2.0.0
• libtool 2.6.2
• google-noto-fonts 20260701

As we close out this week’s chapter, here is a sneak peek at what is brewing in the staging projects for the coming days.

• linux-glibc-devel 7.1: Last holdup at this time is llvm (15 – 21).
• Podman 6.0.0: Undergoing integration and sync testing with buildah and skopeo.
• GCC 16 as the default system compiler: This major upgrade has now been moved to Staging:N, where openQA will soon be triggered to verify integration.
• rpmlint: The upcoming update will enforce whitelisting for capabilities in SUIDPermissionsCheck