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

Bug#448284: marked as done (RFH: dctrl-tools -- Command-line tools to process Debian package information)

Your message dated Mon, 26 Mar 2012 10:15:39 +0300
with message-id <20120326071537.GA6275@kukkaseppele.kaijanaho.fi>
and subject line Closing
has caused the Debian Bug report #448284,
regarding RFH: dctrl-tools -- Command-line tools to process Debian package information
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
448284: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=448284
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: normal

I request assistance with maintaining the dctrl-tools package.

There are several tasks that could use more manpower (in no particular
order):

  1. Writing test cases 

     One could mine the BTS for past bug reports and create regression
     tests for them.

     One could use standard black-box and white-box testing techniques
     to generate general tests.

  2. Writing documentation

     The whole suite of tools could use a unified tutorial manual on
     how to best use it.  The current documentation is reference
     material in the man pages.

  3. Internationalise the man pages

     Use po4a?

  3. Swatting the BTS wishlist entries

     I've kept the BTS clean of actual bugs pretty well, but there are a
     number of wishlist reports still outstanding.

  4. Take over maintaining the debian/ directory

     If you commit to maintaining it (and I trust your judgment),
     you'll get last say in that part of the package (including deciding
     what helper to use).

  4. Whatever you wish :)

     Discuss on the dctrl-tools-devel mailing list first though.
     
Eventually I'd like to pass the package on to competent successors, but
I have too much emotional attachment to the package to do that without a
transitional period where I still retain a veto on what goes in the
package.  I also have some ideas for future tools that I'd like to be
able to concentrate on, and having co-maintainers might allow that.

The package is now under Git in collab-maint.  See 
  http://git.debian.org/?p=collab-maint/dctrl-tools.git;a=blob_plain;f=debian/README;hb=HEAD
for information and a push-access code of conduct.

The package description is:
 Debian package information is generally stored in files having a
 special file format, dubbed the Debian control file format (the dctrl
 format), a special case of the record jar file format.  These tools
 operate on any files conforming in a general sense to that format and
 are therefore widely applicable whenever those formats are in play.
 .
 Included are:
 .
   grep-dctrl     - Grep dctrl-format files
   grep-available - Grep the DPKG available database
   grep-status    - Grep the DPKG status database
   grep-aptavail  - Grep the APT available database
 .
   sort-dctrl     - Sort dctrl-format files
 .
   tbl-dctrl      - Tabulate dctrl-format files
 .
   sync-available - Sync the dpkg available database with
                    the apt database

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.23.1-ibid (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

--- End Message ---
--- Begin Message --- 
While I would still appreciate help, this RFH bug has outlived its usefulness
:-)

-- Antti-Juhani Kaijanaho, Jyväskylä, Finland
http://antti-juhani.kaijanaho.fi/newblog/

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: