[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Misc Developer News (#52)

The news are collected on https://wiki.debian.org/DeveloperNews
Please contribute short news about your work/plans/subproject.

In this issue:
 + Updated mentors.debian.net
 + Removal of debhelper compat 5 and 6
 + new Debian world map
 + Lintian Tags on Salsa
 + Janitor Merge Proposals Now Include Debdiff / Diffoscope Output
 + Qt 6 looking for new maintainers

Updated mentors.debian.net

 There has been a heavy update of the codebase of mentors.debian.net,
 including moving from Python 2 to 3 and changing frameworks from Pylons
 to Django. A few new features were also introduced. More details are
 available in the announcement mail[1].

 Please consider being available to support our newcomers by reviewing
 packages, and reporting any bugs you may find while using
 mentors.debian.net in the salsa project.

  -- Baptiste BEAUPLAT, Mattia Rizzolo and mentors.d.n team.

 [1] https://lists.debian.org/5cb7543f-6104-f3d5-e617-04ddb76c709b@cilg.org

Removal of debhelper compat 5 and 6

 As announced, debhelper compat 5 and 6 are now planned for removal[2].
 This is expected to happen no later than during the bookworm development
 cycle (buster + 1).

 Please review your packages affected by the removal and plan their
 migration to a supported compat level. Please keep in mind that compat
 bumps are '''NOT''' accepted during the freeze per the FAQ from the
 Release Team about unblocks[3].

 The differences between compat levels are documented in the debhelper(7)
 manual page[4].

  -- Niels Thykier

 [2] https://lists.debian.org/msgid-search/ae4185bc-af05-8c53-91ae-f29c9817aac4@thykier.net
 [3] https://release.debian.org/bullseye/FAQ.html
 [4] https://manpages.debian.org/unstable/debhelper/debhelper.7.en.html#Supported_compatibility_levels

new Debian world map

 There is a new world map of Debian Developers available[5].
 Currently it contains data from the keysigning offers[6] list in the

 If you spot problems: Development happens at salsa[7], feel free to
 report issues and send pull requests, especially for additional Debian
 location data sources[8].

  -- Uwe Kleine-König

 [5] https://map.debian.net/
 [6] https://wiki.debian.org/Keysigning/Offers
 [7] https://salsa.debian.org/ukleinek/debianmap
 [8] https://wiki.debian.org/DebianLocations

Lintian Tags on Salsa

 View your Lintian tags in a nice web page on Salsa! For more information,
 look at the documentation[9] or contact the Salsa CI team on IRC

  -- Felix Lechner and Iñaki Malerba, on behalf of their teams

 [9] https://salsa.debian.org/salsa-ci-team/pipeline/-/blob/master/README.md

Janitor Merge Proposals Now Include Debdiff / Diffoscope Output

 Merge proposals created by the janitor[10] now include the debdiff
 between a build with and without the changes (showing the impact to the
 binary packages), in addition to the merge proposal diff (which shows the
 impact to the source package).

 New merge proposals also include a link to the diffoscope[11] diff
 between a vanilla build and the build with changes. Unfortunately, these
 can be a bit noisy for packages that are not reproducible yet, due to the
 difference in build environment between the two builds.

 This is part of the effort to keep the changes from the janitor

  -- Jelmer Vernooij

 [10] https://janitor.debian.net/
 [11] https://www.diffoscope.org/

Qt 6 looking for new maintainers

 Dmitry Shachnev and I decided not to maintain Qt 6 whenever it gets
 published[12] based mostly on time issues. We will do our best to keep Qt
 5 in shape for the remainder of its life.

 We will be happy to review and/or sponsor other people's work or even
 occasionally do uploads, but we can't promise to do it regularly.

 So if you would like to have Qt 6 in the archive, you should consider
 stepping up for the job.

  -- Lisandro Damián Nicanor Pérez Meyer

 [12] https://perezmeyer.blogspot.com/2020/08/stepping-down-as-qt-6-maintainers.html



Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: