Differences between revisions 124 and 125
Revision 124 as of 2011-08-02 02:44:16
Size: 7156
Editor: ?GregorHerrmann
Comment: some cleanup, git related
Revision 125 as of 2011-10-05 16:58:02
Size: 5590
Editor: ?GregorHerrmann
Comment: remove some post-git tasks that are already done
Deletions are marked like this. Additions are marked like this.
Line 27: Line 27:
 * Polish rough edges after migration from Subversion to Git

   - Migration tasks/tools
      * there is a git repo

        to collect scripts and documents in progress.

      * svn-all-fast-export config (generated by script, db to handle)
         - svn-all-fast-export now available on vasks, thanks to Mithrandir. Unfortunately my (db) current config requires a patched version for the "substitute" operation.
        The patched version is available at
   - Post Migration tasks/tools/docs
      * post-migration TODO: copy the standard hook in all repositories
      * create repo tool (remote-ize setup repo) -> alioth-git-repo (in git/meta.git, uses /git/pkg-perl/setup-repository on vasks)
      * mr config management: should be done, cf. [[http://pkg-perl.alioth.debian.org/git.html#track_all_repositories_on_alioth_with_mr_1_|documentation]] (CGI? - also [[http://pkg-perl.alioth.debian.org/cgi-bin/mrconfig.cgi|exists]] but probably useless)
      * docs:
        * (maybe) tips.pod
        * [howto/quilt-copyable.pod *cough*]
      * scripts:
        * apt-pm/ and http://pkg-perl.alioth.debian.org/cpan2deb/ probably too
 * Post svn->git migration tasks/tools/docs
    * docs:
      * (maybe) tips.pod
      * [howto/quilt-copyable.pod *cough*]
Line 67: Line 48:
 * Maybe add debian/source/local-options with unapply-patches and abort-on-upstream-changes to all packages? (packagecheck, see also below) -- might be unnecessary if dpkg changes its defaults, cf. recent (May 2011) [[http://lists.debian.org/debian-devel/2011/05/msg01130.html|discussions on debian-devel@l.d.o]]
Line 69: Line 49:
 * Check for duplicate packages in svn and git; started 2011-07-18
* After the alioth changes: what needs to be done? (Svn-* headers? documentation? website? scripts?)
 * After the alioth changes: what needs to be done? (Vcs-* headers? documentation? website? scripts?)

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).



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

  • -


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

  • Post svn->git migration tasks/tools/docs

    • docs:
      • (maybe) tips.pod
      • [howto/quilt-copyable.pod *cough*]
  • Maintenance of applications in the Debian Perl Group -- included in our Policy already, there are some packages that still need adjustment (→ file bugs with usertags)

  • 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; 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. (fabreg)
  • 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); started 2011-07-18
  • Next alioth project member ping
  • perl 5.12 transition: fix bugs, change some (build) dependencies after 5.12 hits unstable (partly done)

  • perl 5.14 transition: fix bugs, change some (build) dependencies later

  • 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)

  • 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)

  • After the alioth changes: what needs to be done? (Vcs-* headers? documentation? website? scripts?)
  • Team-specific questions for NM templates (Enrico's mail).

  • Multi-arch / cross-building


  • 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


  • review the code that Jeremiah has written to see if it fits our needs
  • suggestions for more functionality, feedback, etc.


(not exclusively a pkg-perl topic but still)

  • it's PET3 in the meantime :)

  • PET project's repo: git+ssh://git.debian.org/git/pet/pet3.git

  • PET3: maybe setup another instance
  • PET3 on Alioth; first talks pet-team - alioth admins; should happen ~ end of August 2011
  • web: http://pet.debian.net/pkg-perl/pet.cgi