Differences between revisions 75 and 76
Revision 75 as of 2011-05-11 16:41:40
Size: 5267
Editor: ?GregorHerrmann
Comment: minor additions
Revision 76 as of 2011-05-25 18:15:42
Size: 5355
Editor: ?GregorHerrmann
Comment: 1) check packages in svn vs. git; 2) PET2 instances
Deletions are marked like this. Additions are marked like this.
Line 48: Line 48:
 * Check for duplicate packages in svn and git.
Line 68: Line 69:
 * PET2: maybe setup another instance

Debian Perl Group - Open tasks

This page collects ideas for tasks within the Teams/DebianPerlGroup. These tasks can be worked on at DebCamp 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).

History

Policy/discussion

List of issues that affect our work mode and need discussion.

Packages/tools

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

  • Investigate possible migration from Subversion to Git (waits for report from investigators)
  • Create the header/identifier for debian/rules that allows mass-updates. (diocles)
  • Rewrite packagecheck (in Perl, modular, maybe not only for pkg-perl; see also below) (jeremiah)
  • Patches:
    • forward all (non Debian specific) patches upstream and add the CPAN RT ids to the patch headers; wait for DEP3 to be finalised? write a nice bug/patch forwarding helper tool; first versions of forward-bug/forward-patch exist (ghedo++)
    • we need a tool for easy editing of patch headers according to DEP3; first version of 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 ...

  • Policy 3.8.4: mass update packages? Very old standards-versions might warrant (just for QA work) to be updated, as they were built with very old toolchains. We should at least check packages that have not been updated since Sarge release.
  • After squeeze: remove B-D on "perl (>= 5.10) | libFOO-perl"

  • After squeeze: remove transitional dummy packages (and debian/TODO items for them)
  • After squeeze: remove alternative dependencies / versioned dependencies that refer to oldstable (etch)
  • Next summer cleanup (remove packages from svn that were injected but never finished for upload)
  • Next alioth project member ping
  • perl 5.12 transition: fix bugs, change some build dependencies after 5.12 hits unstable (partly done)

  • Check the documentation on our website.

  • Policy 3.9.1 (and base-files) has introduced /usr/share/common-licenses/GPL-1. #436105

  • Check RFP/ITP packages
  • Finish uploading packages where the version in the archive doesn't have the group as the maintainer (i.e. adopted packages etc.)
  • bundle packages: get out of the insanity :) (notes: pkg-components, ftp-master clarification)

  • Which tests do we run / which variables do we set? -> consistency over packages

  • Maybe add debian/source/local-options with unapply-patches and abort-on-upstream-changes to all packages? (packagecheck, see also below)
  • Switch modules and tools to use Digest::SHA instead of Digest::SHA1 and remove libdigest-sha1-perl from the archive #594273 Transitions/DigestSHA1ToDigestSHA (http://deb.li/digestsha)

  • Check for duplicate packages in svn and git.

dh-make-perl

  • continue breaking it to isolated modules
  • make POD coverage pass (by completing the docs)
  • TODO

  • bugs

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

packagecheck{,.pl}

  • discuss git support and way forward
  • review the code that Jeremiah has written to see if it fits our needs
  • suggestions for more functionality, feedback, etc.

PET

(not exclusively a pkg-perl topic but still)

  • multi-repo support?
  • merge ansgar's PET2? (demo, repo) -- it's now in the PET project's repo: git+ssh://git.debian.org/git/pet/pet2.git

  • PET2: maybe setup another instance