On Fri, Aug 24, 2012 at 1:51 AM, Nicolas Couchoud
<[email protected]> wrote:
> Vincent Chen a écrit :
>> I realize Debian is under freeze right now, so this might be an awkward
>> time for new packages.
>
>   Clause 5.(a) of http://release.debian.org/wheezy/rc_policy.txt states
> that packages should not be too much out of date. So, in my opinion, since
> the version of fvwm currently present in Debian testing stopped being
> maintained upstream more than a year ago, it can be argued that this bug
> and the ones it duplicates (#681255 and #623194) should be considered
> release-critical. This argument should make acceptance of your package by
> release managers easier.

Thanks for the info, Nicolas. Didn't know out-of-date packages are
also considered release-critical.

Manoj, have you decided what to do about the fvwm package? I haven't
started looking for a mentor since this package does not belong to me.
I am willing to maintain it myself if you're no longer interested in
dealing with fvwm.

Forgot to mention:
- The package at https://mentors.debian.net/package/fvwm is what I'm
using everyday.
- The package compiles using pbuilder on Debian Sid.
- No error from lint. I've also tried reading all the relevant
documentations, so the package should also satisfy the Debian Policy.

Since I use FVWM everyday, I'd love to see an up-to-date version as
part of Debian, along with some bugs closed. Again, I don't want to
appear to be hijacking your package, but merely making my intention to
help known.


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

Reply via email to