Dear Debian community,
This is bits from the DPL for October.
The Delayed Queue - a great place to learn
==========================================
In recent weeks, many packages started to fail to build due to the CMake
4 and GCC 15 transitions, turning quite a few bugs into release-critical
ones. The good news: many of these issues are easy to fix and offer an
excellent way to get started with Debian development.
For CMake 4 bugs, most fixes are simple - either adding
-DCMAKE_POLICY_VERSION_MINIMUM=3.5
to some override_dh_auto_configure target in debian/rules or replacing
cmake_minimum_required(VERSION X) # X < 3.5
by
cmake_minimum_required(VERSION 3.1...3.10) # or just 3.5
in CMakeLists.txt by using a quilt patch.
This resolves the majority of cases. GCC-15 bugs can be trickier, but
often GCC points directly to a missing include or similar issue. Even if
you can't finish a fix, tagging the bug "help" and sharing your findings
already helps others.
So where to start? The Delayed Queue[q01] is full of examples.
Dedicated contributors regularly upload Non-Maintainer Uploads (NMUs)
there, helping to keep the archive in shape. Each upload corresponds to
a bug report with a patch that you can study and learn from. The patches
are available via the Debian Bug Tracking System. Just browse the
Delayed Queue[q01] -- every entry links to a bug log containing the
corresponding patch. Reviewing these is a great way to see how others
fix build failures and to try similar fixes yourself. For instance:
sudo apt install devscripts
bts bugs usertag:cmake@packages.debian.org
lists all CMake 4 related bugs.
You don't need upload rights to help -- analyzing bugs and sharing your
insights already makes a real difference. The Delayed Queue is not just
where fixes wait -- it's also a great place to learn. If you have
questions or would like some mentoring, feel free to drop by the Debian
Tiny Tasks Matrix channel[q02].
[q01] https://ftp-master.debian.org/deferred.html
[q02] https://matrix.to/#/#debian-tiny-tasks:matrix.org
Seeking new members for the DFSG team
=====================================
The package acceptance process (the "NEW queue") has often been
perceived by contributors as one of the more challenging parts of
getting packages into Debian -- despite the enormous dedication of our
reviewers. Reviewing new packages is careful, repetitive work that
requires patience and attention to detail. I am currently seeking
volunteers to reinforce the DFSG team, which will focus on sharing this
responsibility and, in close collaboration with the Debian community, on
defining how the NEW queue should evolve in the future.
Engaging the wider Debian community in this discussion is an essential
step toward addressing long-standing communication and sustainability
challenges, so that newcomers can contribute effectively and we can
build a more open, maintainable process together. Strengthening this
area is key to ensuring a sustainable workflow and transparent
communication around package acceptance.
The DFSG team will play a central role in defining how Debian's
commitment to software freedom is applied in practice. This includes
interpreting the DFSG as it applies to the Debian archive -- that is,
determining which packages meet our standards -- and making decisions
about the content of the archive, such as reviewing new packages and
addressing cases where existing packages no longer comply.
The new team will have full freedom to explore and design improved ways
of handling NEW processing. Whether that involves refining existing
workflows or developing new approaches, the goal is to build a
sustainable, transparent, and collaborative process that reflects
Debian's values and practical needs. I have full trust in the future
team members to lead this discussion and shape the direction that best
serves the project. As DPL, I will not steer this work -- DPLs come and
go, but the delegated team members will define and operate under the
processes they establish together.
If you are interested in helping shape how Debian evaluates and accepts
new software -- and in ensuring our handling of DFSG questions remains
both rigorous and transparent -- please consider joining this new team.
Kind regards
Andreas.
Attachment:
signature.asc
Description: PGP signature