Bug#328811: very old package, should this be removed?
Peter S Galbraith [EMAIL PROTECTED] writes: Marc 'HE' Brockschmidt [EMAIL PROTECTED] wrote: During the Debian QA meeting hold during Sept. 09th till 11th, we decided that looking at packages that haven't been uploaded for a very long time could cover up some QA problems. I've done this now and your package showed up on the list. I propose to remove it. The package has almost no users, is quite out of date wrt Debian's policies and there are some alternatives available. I disagree. I use it! There will be an upload at some point, some I have figured out a defconf script bug. The powerstatd-crypt package will disappear but the regular powerstatd package will function with encryption (i.e. will have the functionality of powerstatd-crypt). Well, perhaps you should ask on debian-mentors@lists.debian.org to find help for the debconf issue. Please close my two bugs with your new upload, thanks. Marc -- BOFH #301: appears to be a Slow/Narrow SCSI-0 Interface problem pgp3hwum8gdyk.pgp Description: PGP signature
Bug#328811: very old package, should this be removed?
Marc 'HE' Brockschmidt [EMAIL PROTECTED] wrote: Package: powstatd Version: 1.5.1-1 Severity: serious Hi, During the Debian QA meeting hold during Sept. 09th till 11th, we decided that looking at packages that haven't been uploaded for a very long time could cover up some QA problems. I've done this now and your package showed up on the list. I propose to remove it. The package has almost no users, is quite out of date wrt Debian's policies and there are some alternatives available. I disagree. I use it! There will be an upload at some point, some I have figured out a defconf script bug. The powerstatd-crypt package will disappear but the regular powerstatd package will function with encryption (i.e. will have the functionality of powerstatd-crypt). The alternative (simpler for upgrades) would be to remove `powerstatd' and keep `powerstatd-crypt', but since the upstream package is named `powerstatd' it is better in the long-run to keep that name. -- Peter S. Galbraith, Debian Developer [EMAIL PROTECTED] http://people.debian.org/~psg GPG key 1024/D2A913A1 - 97CE 866F F579 96EE 6E68 8170 35FF 799E -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#328811: very old package, should this be removed?
Package: powstatd Version: 1.5.1-1 Severity: serious Hi, During the Debian QA meeting hold during Sept. 09th till 11th, we decided that looking at packages that haven't been uploaded for a very long time could cover up some QA problems. I've done this now and your package showed up on the list. I propose to remove it. The package has almost no users, is quite out of date wrt Debian's policies and there are some alternatives available. This usually means that your package matched some of the following criteria: [1] Your packages has not had a maintainer upload for more than three 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. 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! Marc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
