All posts by jzb

[$] GoFundMe to delete unwanted open-source foundation pages

Post Syndicated from jzb original https://lwn.net/Articles/1043075/

Open-source foundations and projects that have charity status in
the US may want to see if GoFundMe has created a profile
for them without permission. The company has operated since 2010 as a
self-service fundraising platform; individuals or groups could create
pages to raise money for all manner of causes. In June, the company announced
that it would expand its offerings to “manage all aspects of
charitable giving
” for users through its platform. That seems to
include creating profiles for nonprofit organizations without their
involvement. After pushback, the company said
on October 23 that it would be removing the pages. It has not
answered more fundamental questions about how it planned to disburse
funds to nonprofits that had no awareness of the GoFundMe pages in the
first place.

Date bug affects Ubuntu 25.10 automatic updates

Post Syndicated from jzb original https://lwn.net/Articles/1043103/

The Ubuntu Project has announced
that a bug in the Rust-based uutils version of the
date command shipped with Ubuntu 25.10 broke automatic
updates:

Some Ubuntu 25.10 systems have been unable to automatically check
for available software updates. Affected machines include cloud
deployments, container images, Ubuntu Desktop and Ubuntu Server
installs.

The announcement includes remediation instructions for those
affected by the bug. Systems with the rust-coreutils package
version 0.2.2-0ubuntu2 or earlier have the bug, it is fixed in
0.2.2-0ubuntu2.1 or later. It does not impact manual updates using the
apt command or other utilities.

Ubuntu embarked on a project to “oxidize” the distribution by
switching to uutils and sudo-rs
for the 25.10 release, and to see if the Rust-based utilities would be
suitable for the long-term-release slated for next April. LWN covered that project in
March.

Btrfs support coming to AlmaLinux 10.1

Post Syndicated from jzb original https://lwn.net/Articles/1043029/

The AlmaLinux project has announced
that the upcoming 10.1 release will include support for
Btrfs:

Btrfs support encompasses both kernel and userspace enablement, and
it is now possible to install AlmaLinux OS with a Btrfs filesystem
from the very beginning. Initial enablement was scoped to the
installer and storage management stack, and broader support within the
AlmaLinux software collection for Btrfs features is forthcoming.

Btrfs support in AlmaLinux OS did not happen in isolation. This was
proposed and scoped in RFC 0005, and has been built upon prior efforts
by the Fedora
Btrfs SIG
in Fedora Linux and the CentOS Hyperscale SIG
in CentOS Stream.

AlmaLinux OS is designed to be binary compatible with Red Hat
Enterprise Linux (RHEL); Btrfs, however, has never been supported in
RHEL. A technology preview of Btrfs in RHEL 6 and 7 ended with the
filesystem being dropped from RHEL 8 and
onward. AlmaLinux OS 10.1 is currently
in beta
.

Security updates for Thursday

Post Syndicated from jzb original https://lwn.net/Articles/1043027/

Security updates have been issued by AlmaLinux (ipa, kernel, and thunderbird), Debian (gdk-pixbuf, gegl, gimp, intel-microcode, raptor2, request-tracker4, and request-tracker5), Fedora (samba and wireshark), Mageia (haproxy, nginx, openssl, and python-django), Oracle (kernel and thunderbird), Red Hat (redis and redis:7), Slackware (bind), SUSE (aws-cli, local-npm-registry, python-boto3, python- botocore, python-coverage, python-flaky, python-pluggy, python-pytest, python- pytest-cov, python-pytest-html, python-pytest-metada, cargo-audit-advisory-db-20251021, fetchmail, git-bug, ImageMagick, istioctl, kernel, krb5, libsoup, libxslt, python-Authlib, and sccache), and Ubuntu (bind9, linux, linux-aws, linux-azure, linux-azure-6.8, linux-gcp, linux-gkeop,
linux-ibm, linux-ibm-6.8, linux-lowlatency, linux-lowlatency-hwe-6.8,
linux-oracle, linux-azure, linux-azure-5.15, linux-gcp-5.15, linux-gcp-6.8, linux-gke, linux-nvidia, linux-nvidia-6.8,
linux-nvidia-lowlatency, and linux-realtime, linux-realtime-6.8).

Fedora Council approves AI-assisted contributions policy

Post Syndicated from jzb original https://lwn.net/Articles/1042947/

The Fedora Council has approved
an AI-assisted
contributions policy
. This follows several
weeks of discussion, some of which were covered by LWN on
October 1. The final policy contains substantial differences from
the initial
proposal
, and now requires disclosure of AI tools “when the
significant part of the contribution is taken from a tool without
changes
“.

Security updates for Wednesday

Post Syndicated from jzb original https://lwn.net/Articles/1042911/

Security updates have been issued by Fedora (inih, mingw-exiv2, and mod_http2), SUSE (ffmpeg-4, kernel, libqt5-qtbase, protobuf, python-ldap, and python313), and Ubuntu (erlang, ffmpeg, linux, linux-aws, linux-gcp, linux-oem-6.14, linux-oracle,
linux-oracle-6.14, linux-raspi, linux-realtime, linux-aws, linux-azure, linux-azure-6.14, linux-azure-nvidia-6.14, linux-azure-fips, linux-oracle-5.4, and linux-realtime-6.14).

Valkey 9.0.0 released

Post Syndicated from jzb original https://lwn.net/Articles/1042851/

Version
9.0.0
of the Valkey distributed key-value database has been
released. Notable features of this release include Multipath TCP
(MPTCP) support
, new filters for
client commands
, multi-database
support for cluster mode
and much more. See the Valkey 9.0.0 RC1
release notes
for a full list of new features in this major
release.

According to a recent blog post, this
release includes major improvements to performance and scaling of
Valkey clusters to more than 2,000 nodes and one billion requests per
second. Valkey began as a
fork
of the Redis key-value database in March 2024, but has
evolved separately since then.

[$] The RubyGems.org takeover

Post Syndicated from jzb original https://lwn.net/Articles/1040778/

In September, a group of long-time maintainers of Ruby packaging tools
projects had their GitHub privileges for revoked by nonprofit corporation Ruby Central
in what many people are calling a
hostile takeover. Ruby Central and its board members have issued
several public statements that have, so far, failed to satisfy many in
the Ruby community. In response, some of the former contributors to
RubyGems are working on an alternative service called gem.coop. On October 17, ownership
of the RubyGems and
Bundler
repositories was handed over to the Ruby core team, even though those projects had never been part of core Ruby
previously. The takeover and subsequent events have raised a number of
questions in the Ruby community.

Transition of RubyGems Repository Ownership

Post Syndicated from jzb original https://lwn.net/Articles/1042480/

The Ruby community has experienced some turbulence
of late after Ruby Central took
control
of the GitHub repositories for a number of projects
including RubyGems
and Bundler. Those projects have historically been developed
separately
from Ruby itself. They are now being put under the
control of Ruby’s core team, according to Ruby creator Yukihiro
Matsumoto (a.k.a. “Matz”):

To provide the community with long-term stability and continuity,
the Ruby core team, led by Matz, has decided to assume stewardship of
these projects from Ruby Central. We will continue their development
in close collaboration with Ruby Central and the broader
community.

Ruby Central has also issued a statement.

[$] A brief history of RubyGems.org

Post Syndicated from jzb original https://lwn.net/Articles/1042131/

Ruby libraries and
applications are distributed via a packaging format called a gem. RubyGems.org has been the central
hosting service for gems since about 2010. This article is part one of
a two-part series on the RubyGems.org takeover by Ruby Central. Understanding the
history of RubyGems.org, and the contributor community behind it, is
vital to making sense of the current power
struggle
between Ruby Central and members of the Ruby
community who have maintained those services and tools for many
years.

Linux Mint Debian Edition (LMDE) 7 released

Post Syndicated from jzb original https://lwn.net/Articles/1042079/

Linux Mint Debian Edition (LMDE) 7, based on Debian 13
(“trixie”), has been released:

Its goal is to ensure Linux Mint would be able to continue to deliver
the same user experience, and how much work would be involved, if
Ubuntu was ever to disappear. LMDE is also one of our development
targets, to guarantee the software we develop is compatible outside of
Ubuntu.

The LMDE release notes
are rather sparse; users are also advised to review Debian 13’s
release
notes
.

Security updates for Wednesday

Post Syndicated from jzb original https://lwn.net/Articles/1042076/

Security updates have been issued by AlmaLinux (kernel, kernel-rt, vim, and webkit2gtk3), Debian (distro-info-data, https-everywhere, and php-horde-css-parser), Fedora (inih, mingw-exiv2, mirrorlist-server, rust-maxminddb, rust-monitord-exporter, rust-prometheus, rust-prometheus_exporter, rust-protobuf, rust-protobuf-codegen, rust-protobuf-parse, and rust-protobuf-support), Mageia (fetchmail), Oracle (gnutls, kernel, vim, and webkit2gtk3), Red Hat (kernel, kernel-rt, and webkit2gtk3), Slackware (mozilla), SUSE (curl, libxslt, and net-tools), and Ubuntu (linux-azure-5.15, linux-azure-6.8, linux-azure-fips, linux-oracle, linux-oracle-6.14, and linux-raspi).

[$] Debian Technical Committee overrides systemd change

Post Syndicated from jzb original https://lwn.net/Articles/1041316/

Debian packagers have a great deal of latitude when it comes to the
configuration of the software they package; they may opt, for example,
to disable default
features
in software that they feel are a security
hazard. However, packagers are expected to ensure that their packages
comply with Debian Policy,
regardless of the upstream’s preferences. If a packager fails to
comply with the policy, the Debian Technical
Committee
(TC) can step in to override them, which it has
done in the case of a recent systemd change that broke several
programs that depend on a world-writable /run/lock
directory.