Package: gnubg
Version: 0.12-4
Severity: serious

Hi.

During the Debian QA meeting hold during Sept. 09th till 11th, we begun to
go through the list of the oldest packages in Debian that are not in testing
(http://bjorn.haxx.se/debian/oldest.html) to search for packages that should
be either orphaned or removed completly from Debian (unstable and testing)
since they have been obviously neglected by their maintainer.

Your package did show up on this list and we propose to orphan it.

This usually means that your package matched some of the following criteria:

      [1] Your packages has not had an upload for more than two years
      [2] has one or more RC bugs with no answer from the maintainer (**)
      [3] the state of your packages in general seems to indicate that
          you might be MIA
      [4] (if we propose a removal) it shows in popcon as having less
          than 100 users with the package installed.
      [5] the package was not released with sarge

and at least ([1] and ( [2] or [3] or [4] or [5] )) was true.

(**) The maintainer not answering to RC bugs refers to bugs filed more
than one month before the time the check was performed.

Your package has not had an upload in over three years, a new upstream
version is available, and two RC bugs open without answer from you.

After 7 days without answer from you (the maintainer) we will reassign
this bug to either WNPP (in case we propose to orphan it) or ftp.debian.org
(in case we propose to remove it).

The package will need an upload or an explanation for this action not
to proceed.

Please do *not* upload a package just to get off this list - it won't
help the package at all. Maintainers should be responsive and feel
responsible for their packages without needing other people to force them
to do work. Sometimes, finding a new maintainer or even removing the
package completly from the archive is better for Debian's users.

Thanks!
-- 
Frank Lichtenheld <[EMAIL PROTECTED]>



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to