Differences between revisions 319 and 320
Revision 319 as of 2015-06-07 08:43:16
Size: 14819
Comment: replace broken link with another useful one
Revision 320 as of 2015-06-26 19:46:18
Size: 14230
Editor: ?GregorHerrmann
Comment: remove packages from RC bug list that have been removed
Deletions are marked like this. Additions are marked like this.
Line 34: Line 34:
||libscalar-number-perl||107||0||DebianBug:723563, DebianBug:708839|| RM bug filed: DebianBug:786625|| ||
Line 38: Line 37:
||libnet-dri-perl||10||0||DebianBug:710954||Upstream engaged? - RM bug filed: DebianBug:786627|| ||
||librdf-helper-perl||9||0||DebianBug:710983||Still failing even with patch proposed. - RM bug filed: DebianBug:786626||Send update to upstream bug||
Line 44: Line 41:
||libsocialtext-resting-perl||2||1||DebianBug:710993||no upstream reaction. - RM bug filed: DebianBug:786624|| ||
||libtest-cgi-multipart-perl||0||0||DebianBug:720965||no upstream reaction. - RM bug filed: DebianBug:786623|| ||

Debian Perl Group - Open tasks

This page collects ideas for tasks within the Teams/DebianPerlGroup. These tasks can be worked on at DebCamp, at a team sprint or might be tackled by volunteers "at home".

It should have an up to date list of open tasks, please remove completed tasks; for documentation please add links to the History section below (instead of adding them in between the tasks here).

Policy / issues for discussion (DebConf BoF)

Release-critical bugs

Leaf package with RC Bugs

Status from Nov 2014 (based on https://lists.debian.org/debian-perl/2014/09/msg00071.html)

Ping upstream means tell them we are going to remove it from Debian unstable in 3 weeks if no action New forwarded reports should wait 3 months until the next step

Leaf means either 0 or $few rdeps






next steps





popcon-based cutoff point (n=50)





perl 5.20 manual binNMU

Wait for response from Julián





depends on removed module Email::Send

Remove after 12th October 2014 if no upstream response





Upstream are interested in this.





active upstream ticket





upstream activity but no conclusion

Here is a template mail used by Dom:

Dear Maintainer,

The Debian perl group is reviewing packages with bugs which make them un-releasable; in particular when they are not heavily used by Debian users. We would like to remove such modules from Debian if we don't think they are likely to be fixed.

Module::Packaged is one such module, owing to this bug, and we would like to know whether you have any plans to look at the bug in the foreseeable future before we remove the package from Debian.

If we don't hear anything we will remove the package from Debian on or around 23rd February. This of course does not affect the standing of your module on CPAN.

Thank you for maintaining this module so far!



List of tasks that need to be performed on all/many of our packages; or maintenance tools ...

  • bundle packages: just do it, and see what happens (notes: pkg-components, ftp-master clarification)

  • QA: cast to pointer from integer of different size: file bugs/fix (http://lists.debian.org/debian-perl/2012/02/msg00029.html, https://qa.debian.org/bls/bytag/I-pointer-cast-size-mismatch.html)

  • Package an awesome Moo development environment, push to remove software that use the (deprecated) Mouse or Any::Moose towards moving to Moo, and remove Mouse and Any::Moose in Jessie.
  • Sort out the future of DateTime::?TimeZone respectively its successors. (work in progress, intri).

  • Unify our debian/watch files, esp. all the variants how uversionmangle is used.

  • Switch repackaging framework from repack.{stub,local,sh} to uscan's Files-Excluded.

  • Change remaining /usr/lib/perl5 occurences (lintian-overrides, doc-base files, ...).

  • Check all libapp-*-perl (and potentially other) packages for real applications whose (binary) packages should rather be named foo instead of libapp-foo-perl.

    • All those packages likely also need to moved outside the perl section, i.e. into utils, misc, text, devel, etc.

    • Known packages affected by this:
      • libapp-termcast-perl
      • libapp-nopaste-perl
  • Explicitly (build-)depend on modules removed from perl core (Module::Build, CGI, ...).
  • After the jessie release and after perl adds versioned provides: simplify (build-) depends on dual-lifed modules.
  • Add/check autopkgtests to all packages.
  • Fix reproducible build issues. wiki, pkg-perl-maintainer


(not exclusively a pkg-perl topic but still)

To be done:

  • list (and possibly implement -- in Python) features we need in PET:
    • track patches
    • show all versions in archive / all suites
    • ci.debian.net (#786664)
    • duck.debian.net (at least nice to have)
    • others?
  • update-watch likes to hang
    • timelimit(1) ?
    • pet should program an alarm and kill the jobs itself



  • find a co-maintainer for dh-make-perl
  • continue breaking it into isolated modules
  • improve POD coverage
  • TODO

  • bugs

  • combine dh-make-perl's "refresh" with cme's update functionality


  • Rewrite packagecheck (in Perl, modular, maybe not only for pkg-perl)
    • packagecheck provides some function of "cme check dpkg". It may be better to improve dpkg model taking into account our needs (dod)

lintian profile

  • a lintian vendor profile exists now in pkg-perl-tools; list of things we could want to add there:
    • uploading d/changelog with unresolved TODO / WAITS-FOR / IGNORE-VERSION / etc.
    • boilerplate README
    • metacpan URLs
    • watchfile regexp
    • unversioned perl in Depends:

    • not using cgit in Vcs-Browser:
    • cf. TODO in pkg-perl-tools source package

Recurring tasks

  • Check RFP/ITP packages

  • Yearly cleanup (remove packages from Git that were injected but never finished for upload)
    • retrieve the list is taken from PET ("New packages" section)

    • send the list to our mailing-list, with some deadline (example email)

    • wait until the deadline expires
    • delete the Git repositories using the remove-repository script

      • [Last cleanup: August/September 2014, gregoa]
  • Check packages not uploaded for more than 6 years using the sort_unreleased_packages.pl script. (6 years because there's a quite sharp edge. The cleanup in December 2013 found about 30 packages not uploaded for > 6 years, but 120 packages last uploaded between 5 and 6 years.)

    • [Last check: December 2013, XTaran]
  • Run duck in all git repositories and check the errors it found. Do not rely to much on the duck website as it only checks the state of packages in the archive, and many issues are already fixed or were only added in the git repositories.

  • Next alioth project member ping: send a "ping" ("Do you still want to be a member?") to those who haven't done something for $time, and remove those who reply with "No" or who don't reply. In order to get a more realistic picture, and maybe also to remove unnecessary permissions. Ansgar has run such a "ping" once (only for non-DD group members, IIRC), and this is a reminder to do it again.
  • Run 'dpt get-ubuntu-packages | sort -u | dpt lp-mass-subscribe' (scripts located in scripts/ directory in pkg-perl git repository) to subscribe our Launchpad team, ~pkg-perl-maintainers to all bugs concerning packages we maintain. This script must be run by a Launchpad team administrator.

    • [Last run: 2015-05-23, gregoa]
  • Check for packages which don't have Debian Perl Group in its Maintainer field: http://pkg-perl.alioth.debian.org/qa/maintainers.txt

    • [Last check: 2014-11-21, alexm]
  • Check in PET for repos with missing (not pushed) tags, and ping people. Ping template:

    PET shows that $PACKAGE is missing tags, could you run "dpt push" or "git push --all; git push --tags" from your working copy?
    • [Last check: 2014-11-21, alexm]
      • libbssolv-perl (pinged on 2014-11-21)
      • libdancer2-perl (tags present, PET bug)
      • libgd-perl (tags present, PET bug)
      • libnet-dns-zonefile-fast-perl (mailed on 2014-11-21)
      • libsocket-msghdr-perl (pinged on 2014-11-21)

When a new Perl hits unstable

When oldstable is archived

  • Update (build) dependencies. E.g. once Lenny is archived, there's no need for "perl (>= 5.10.1) | libFOO-perl ()" anymore, or to depend on versions of packages that are already satisfied in current stable.

  • cme fix dpkg -from control -filter Depends, with mass-commit in our script repo

  • Review/remove Breaks/Replaces against package versions that are not even in oldstable. (Not (yet?) in cme fix.)


List of tasks that need to be (better) documented and promoted to get wider adoption:

  • autopkgtest: pkg-tool-autopkgtest exists, autopkgtest understands Testsuite: autopkgtest-pkg-perl, ci.debian.net will pick up perl packages. time to document and use it.

  • group-specific lintian checks are not widely known.
  • Integrating upstream git repos into our workflow: the tools are there, we need to document/advertise/use them.
    • Announcement mail for both lintian and dpt-*.

Background tasks

Things that would be nice to do, often repetitive. Can be done globally, or every time you work on a specific package.

  • Forward all (non Debian specific) patches upstream and add the CPAN RT ids to the patch headers [tools: 'dpt forward' exists (ghedo++), patchedit exists (jozef++)]
  • Fix common lintian-errors repo-wide (e.g. errors from pod2man, missing patch descriptions, ...) - some stuff fixed, other is more easily fixed by "dh-make-perl --refresh" on the next upgrade ...

Nice to have, some day

  • Write team-specific questions for NM templates (Enrico's mail).

    • Random ideas: fix a Perl bug, update a Perl package to the group standards, adopt a package into the Perl group.
  • NM tasks for teams -- found in an even older mail from Enrico :)