[DRE-maint] Bug#722375: Updating the Ruby packaging policy for your package «libposixlock-ruby»

[Tomas Pospisek]

On Sat, 21 Sep 2013, Gunnar Wolf wrote:

> Tomas Pospisek dijo [Sat, Sep 14, 2013 at 12:52:52PM +0200]:
>> Hello Gunnar and dear Ruby maintainers,
>>
>> I'm currently off, travelling the world. Possibly I will try to
>> bring my Ruby package up to speed, but more probably I won't.
>> Finding the time and calm, internet and AC current is too much of a
>> rare coincidence.
>>
>> So please if anybody feels like fixing my package up, the please do
>> so, thanks a lot and greets to you all,
>> *t
>
> I downloaded your package to take a stab at repackaging it, but found
> you had this in your README:
>
>  The upstream posixlock gem has not been ported and doesn't compile
>  under ruby 1.9.
>
>   -- Tomas Pospisek <tpo_deb at sourcepole.ch>  Tue, 03 Jul 2012
>
> The last time upstream appears to have touched the code is in 2009,
> but Web references I found to it seem to be from 2005-2007 (maybe the
> http://www.codeforpeople.com/ server was installed in 2009?); the code
> is really tied into the C structures of Ruby objects, and I agree with
> your comment: It fails to build for 1.9.3.
>
> Now, although this functionality seems important, the package has no
> reverse dependencies, and has a very low popcon index. So, I'd suggest
> filing a bug for its removal.
>
> It would be best if you could file this bug; otherwise, I can do it,
> but please tell me if I should proceed (or, of course, if I should
> _not_ do so).

according to popcon there are a few user using the package. I don't know 
if the number there is statistically relevant - or in other words if those 
users really *are* using the package.

If we leave the package in Debian as is, then at least we serve those few 
users.

I'm not sure what we gain by dropping the package.

But please proceed as you judge right.

Thank you Gunnar and greets,
*t