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

[Tomas Pospisek]

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.

<rant>
Also I own a HP 6710 series laptop that contains an AMD Seymour Radeon HD 
6400M/7400M Series discrete gfx chip that aparently can't be switched 
off and completely randomly switches itself on and sucks all power out 
of the batteries, so working off grid over more than an hour is 
practically impossible. A true piece of shit hw.
</rant>

So please if anybody feels like fixing my package up, the please do so, 
thanks a lot and greets to you all,
*t

On Tue, 10 Sep 2013, Gunnar Wolf wrote:

> Package: libposixlock-ruby
> Severity: normal
> Usertags: ruby18-removal, update-ruby-policy
>
> Hi Tomas Pospisek,
>
> As you may know, during the Wheezy release cycle, the pkg-ruby-extras
> team¹ has worked to update the Ruby libraries/modules/gems packages to
> follow a new policy, much easier for the maintainers (as we no longer
> require a separate package for each interpreter version), to the
> archive (as it strongly reduces code duplication), and much more
> sensical to the users (as they no longer require to fiddle with which
> among many almost-identical binary packages to install).
>
> While we achieved a quite good success level during the Wheezy cycle²,
> we decided to act only on the packages maintained by the group — There
> are many Ruby library packages maintained by kind people (like
> yourself!) which have not yet adopted this new style. According to our
> records, you are currently maintaining the package:
>
>  libposixlock-ruby