Hi all,
As a newcomer to the Ruby team over the past few weeks, I've noticed
some aspects of Ruby packaging that could be easily clarified with
documentation or, better yet, in the Ruby policy.
I'd like to lay out some proposals, which can be discussed further on
IRC on Friday.
VCS vs Gem
I have uploaded a new version of sup-mail to git.
This *was* a package with 2 RC bugs, ruby1.9 use, and a dead RubyForge
homepage. I have worked on it for several weeks. Unfortunately, last
week it was removed from unstable because the FTP master thought it was
dead.[1] His advice was to conta
OK, all changes have been made and uploaded.
Caitlin
On 21/08/14 05:32 AM, Cédric Boutillier wrote:
On Wed, Aug 20, 2014 at 05:42:35PM -0400, Caitlin Matos wrote:
In the generated TextFormattingRules html file, you changed the link to
load the Debian logo, but you didn't change the text just
Hello,
On Mon, Aug 25, 2014 at 8:59 AM, NOKUBI Takatsugu wrote:
> Currently Debian has the ruby-kakasi package.
> The original upstream was hosted in RAA, but it was
> closed last year.
>
> OTOH, there is a new ruby binding for KAKASI in
> rubygems.
> https://rubygems.org/gems/kakasi
> https://
Dear all,
A new version of gem2deb 0.9.0 has been uploaded and is waiting in the
NEW queue at the moment. The reason for it to pass through the NEW queue
again is that it provides a new binary package: gem2deb-test-runner.
With this new version, gem2deb has gain support for automatic
as-installed
On Monday 25 August 2014 06:07 PM, Pirate Praveen wrote:
> kill any left out redis process (they don't get killed if the build fails)
>
> now one error and one failure is left
>
> I can get myapp from github but has so many errors so I'm inclined to
> disable this test for now. If anyone is inter
6 matches
Mail list logo
