Re: [DRE-maint] Bug#722375: Updating the Ruby packaging policy for your package «libposixlock-ruby»
Hello Gunnar, On Mon, 14 Oct 2013, Gunnar Wolf wrote: Tomas Pospisek dijo [Fri, Oct 11, 2013 at 03:46:32PM +0200]: 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. Hi Tomas, The problem is that, as this bug is not compatible with Ruby ≥ 1.9.1, and upstream no longer supports it, it would not allow us to drop Ruby 1.8 (which is planned to happen during this release cycle). Jessie will ship with support for Ruby 1.9.1 and 2.0, but 1.8 will be dropped. Ah, OK, I understand. In that case, I'd be *very grateful*, if you'd have the the package removed from sid/the next release. Thanks a lot Gunnar! *t___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
Re: [DRE-maint] Bug#722375: Updating the Ruby packaging policy for your package «libposixlock-ruby»
Tomas Pospisek dijo [Fri, Oct 11, 2013 at 03:46:32PM +0200]: 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. Hi Tomas, The problem is that, as this bug is not compatible with Ruby ≥ 1.9.1, and upstream no longer supports it, it would not allow us to drop Ruby 1.8 (which is planned to happen during this release cycle). Jessie will ship with support for Ruby 1.9.1 and 2.0, but 1.8 will be dropped. ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
Re: [DRE-maint] Bug#722375: Updating the Ruby packaging policy for your package «libposixlock-ruby»
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_...@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 ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
Re: [DRE-maint] Bug#722375: Updating the Ruby packaging policy for your package «libposixlock-ruby»
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 Hi Tomas, 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_...@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). 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 Ugh. :( signature.asc Description: Digital signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
Re: [DRE-maint] Bug#722375: Updating the Ruby packaging policy for your package «libposixlock-ruby»
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___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
