Kernel kerfuffle kiboshes Debian 12.3 release

Trending 2 months ago

The Debian maintainers person identified a problem successful kernel 6.1 that tin origin corruption connected ext4 volumes. As a result, nan planned 12.3 merchandise won't happen.

The rumor is Debian bug #1047843, and it's been assigned a severity level of "grave" – which is worse than "serious" and only 1 measurement down from "critical."

Unfortunately, nan rumor was identified while nan rollout of Debian 12.3 to nan various reflector servers was already nether way. As a result, nan rollout of 12.3 has been cancelled. It will beryllium replaced pinch type 12.4 instead.

What happened is simply a small complicated. At nan clip of writing, it seems that a small, performance-enhancing change from November 1 was back-ported to nan semipermanent support type of kernel 6.1. SUSE kernel developer Jan Kara isolated nan problem, and reported it to nan kernel mailing list.

It turned retired that nan November 1 alteration required another, different change from June 10, which was not back-ported pinch it. With nan June 10 change, nan November 1 1 is fine, truthful this is not a bug arsenic specified – there's thing incorrect pinch it, unless nan earlier alteration wasn't made.

The rumor seems to impact only kernel versions 6.1.64 and 6.1.65 – it was fixed successful kernel 6.1.66. However, 6.1.66 introduced a new, different issue, besides caused by nan aforesaid type of problem: a minor fix was back-ported without nan earlier change it required. This alteration was reverted connected December 11, resulting successful kernel 6.1.67, which astatine nan clip of penning is nan existent type of 6.1 and resolves some issues.

We dream that's clear.

These dependency problems punctual america of nan bad aged days of Linux successful nan precocious 1990s. During that time, package-management devices specified arsenic Red Hat's RPM bid were not smart capable to way erstwhile 1 package required different package and activity retired connected their ain what different packages were needed to make thing work. Installing mini programs – specified arsenic a matter editor – mightiness impact manually tracing each its dependencies, making notes connected insubstantial aliases successful a matter file, and installing each of them. But of people nan limitations mightiness person limitations of their own, making this a recursive process. You mightiness person to download a twelve packages conscionable to get 1 to install.

  • Systemd 255 is present pinch improved UKI support
  • Veteran editors Notepad++ and Geany deed milestone versions
  • Two caller versions of OpenZFS hole long-hidden corruption bug
  • Steam customer drops support connected macOS, but adds it connected Linux

The Reg FOSS table still recalls nan dread caused by upgrading KDE 1.x to KDE 2.x connected an early type of Red Hat Linux, which required successful excess of 200 packages to beryllium manually identified, downloaded individually, and manus installed – in nan correct order, of course.

The first distro to hole this horrific process was Debian successful 1999, erstwhile type 2.1 "Slink" came pinch nan caller Advanced Package Tool – aliases apt – which could do this for you automatically. Frankly, while Debian backmost past was still very intimidating, it gained a monolithic method separator complete Red Hat connected nan spot.

Red Hat yet picked up nan yum package manager from nan PowerPC-specific Yellow Dog Linux, and regained immoderate benignant of parity. We deliberation that it mightiness person been included successful Red Hat Linux 8 successful 2002 – but if so, it wasn't mentioned successful nan release announcement.

It took astir a decade for automatic dependency solution to travel to Linux distributions, and until it did, this conscionable seemed to beryllium an insolubly analyzable problem. Perhaps it's clip for personification to invent immoderate benignant of automatic dependency search and solution system for Linux kernel codification changes. ®