Roberto C. Sánchez dijo [Fri, Jan 07, 2011 at 06:10:27PM -0500]:
Lucas,
Unfortunately, I only have time to maintain the packages for which I am
already an uploader, but I do wish to remain a part of the team. My
Alioth login is roberto.
Roberto, and should all of the packages listed for
Hi,
I am still in.
As for the packages for which I am listed as {,co}maintainer,
I'm interested in keeping them:
libbarby-ruby
libcolor-tools-ruby
libevent-loop-ruby
libgettext-activerecord-ruby
libgettext-rails-ruby
libgpgme-ruby
libhaml-ruby
Lucas Nussbaum dijo [Sat, Jan 08, 2011 at 12:11:54AM +0100]:
libsetup-ruby (U)
ncurses-ruby (U)
Adding myself as an uploader to both in SVN.
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
Antono Vasiljev dijo [Mon, Jan 17, 2011 at 01:53:55PM +0200]:
Hello, All.
I cloned svn repo with git-svn and experimented a little bit.
(...)
Almost every big ruby project use git today. Why should we use SVN?
So. I would like to know your cons/pros about switching to git.
Its my
Lucas Nussbaum dijo [Wed, Jan 26, 2011 at 09:45:11AM +0100]:
(...)
Regarding my involvement in this team, I will not fall in the trap of
being the center point where most sponsorship requests go. I know that
it's often very hard to find a sponsor inside Debian, and that sucks.
But as a DD,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 08 Feb 2011 20:58:03 -0600
Source: libole-ruby
Binary: libole-ruby-doc libole-ruby1.8 libole-ruby1.9.1 libole-ruby
Architecture: source all
Version: 1.2.11.1-2
Distribution: experimental
Urgency: low
Maintainer: Gunnar Wolf gw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 08 Feb 2011 21:02:36 -0600
Source: libhaml-ruby
Binary: libhaml-ruby1.8 libhaml-ruby libhaml-ruby-doc haml-elisp
Architecture: source all
Version: 3.0.25-2
Distribution: unstable
Urgency: low
Maintainer: Gunnar Wolf gw
Urgency: low
Maintainer: Gunnar Wolf gw...@debian.org
Changed-By: Gunnar Wolf gw...@debian.org
Description:
libspreadsheet-ruby - Ruby library for manipulating .xls spreadsheets
libspreadsheet-ruby-doc - Ruby library for manipulating .xls spreadsheets
libspreadsheet-ruby1.8 - Ruby library
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 09 Feb 2011 13:41:13 -0600
Source: libole-ruby
Binary: libole-ruby-doc libole-ruby1.8 libole-ruby1.9.1 libole-ruby
Architecture: source all
Version: 1.2.11.1-3
Distribution: unstable
Urgency: low
Maintainer: Gunnar Wolf gw
Urgency: low
Maintainer: Gunnar Wolf gw...@debian.org
Changed-By: Gunnar Wolf gw...@debian.org
Description:
libspreadsheet-ruby - Ruby library for manipulating .xls spreadsheets
libspreadsheet-ruby-doc - Ruby library for manipulating .xls spreadsheets
libspreadsheet-ruby1.8 - Ruby library
Package: mongrel
Version: 1.1.5-5
Severity: important
Tags: patch upstream squeeze wheezy sid
After the Lenny⇒Squeeze update, two out of my six Rails systems
(served under Mongrel) broke — Or rather, the systems continued
working, but giving incomplete headers (and thus rendering the results
tags 621436 +confirmed
thanks
First of all, sorry for not acting on this bug earlier, it completely
slipped below my radar :(
Urgh... Even with your patch applied, it still FTBFSes:
VERSION of BDB is Berkeley DB 5.1.25: (January 28,
Ralf Treinen dijo [Fri, Oct 07, 2011 at 05:43:18PM +0200]:
This dependency is calculated at package build time:
Package: libeventmachine-ruby
Architecture: all
Depends: libeventmachine-ruby1.8 (= ${source:Version}),
libeventmachine-ruby1.8 ( ${source:Version}.1~), ${misc:Depends}
Antonio Terceiro dijo [Sun, Oct 16, 2011 at 01:50:58PM -0300]:
Yes, I find it very sensible. Of course, this could be part of the
gem2deb procedure, overridable in case lib is either not correctly
guessed, or in case there is more than one library. The ideal would be
to include every
Paul Battley dijo [Tue, Nov 15, 2011 at 10:14:28AM +]:
Hi,
$ ruby1.9.1 -e 'require htmlentities;
t=HTMLEntities.new.encode(élan); puts t; puts t.encoding'
lt;élangt;
UTF-8
That's the expected behaviour: only the basic entities are escaped by
default, i.e. only that which is
@lists.alioth.debian.org
Changed-By: Gunnar Wolf gw...@debian.org
Description:
mongrel- Small fast HTTP library and server for Ruby webapps
Changes:
mongrel (1.1.5-6) unstable; urgency=low
.
* Repackaged using the gem2deb infrastructure
* mongrel-doc binary package is no longer generated
Checksums
reassign 653582 ruby1.9.1
retitle 653582 Segfaults when running ruby-hpricot's test suite
thanks
Hi,
I do not have access to IA64 hardware, but this smells much like a bug
in Ruby itself, in which ruby-hpricot's tests trip. I think the proper
course is to report this to the upstream bugtracker,
Hi,
I am the package's sponsor (and should have checked for this
dependency :-/ ). I have applied your NMU to the package's VCS, and am
uploading it to the archive. Gastón, I guess you (as the maintainer)
will not object!
Thanks,
signature.asc
Description: Digital signature
Hi,
You sent a patch to this bug report and said you'd be uploading a NMU
- Several weeks ago. So, I'm uploading the patched package.
Thanks!
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
tags 652802 + unreproducible
thanks
I have rebuilt the package under AMD64, using cowbuilder, and could
not reproduce the failure. Your report mentions some permission
problems regarding /var/lib/sbuild - Can you verify whether it was a
problem in your side?
reassign 665266 ruby-pdf-reader 1.0.0-1
thanks
As of 1.0.0-1, ruby-pdf-reader build-depends on ruby-rc4, but as it
does not depend on it, it fails to run.
___
Pkg-ruby-extras-maintainers mailing list
Lucas Nussbaum dijo [Thu, Mar 22, 2012 at 05:52:47PM +0100]:
During a rebuild of all packages in sid, your package failed to build on
amd64.
Hi,
This failure is caused by the OpenSSL 1.0.0h → 1.0.1 upgrade. I have
not taken a deeper look into this, but when installing a pre-1.0.1
libssl1.0.0
Package: ruby-commandline
Version: 0.7.10-13
Severity: grave
Justification: renders package unusable
CommandLine::Application fails to work under Ruby 1.9.1, which is now
the default Ruby version in Debian. This makes any application built
on 1.9.1 die silently:
$ cat app2.rb
require
Package: bundler
Version: 1.1.4-4
Severity: important
Bundler wants to have less installed in order to give information
about itself:
$ bundle --help
sh: 1: less: not found
This can be avoided by substituting 'less' by 'sensible-pager' in
/usr/lib/ruby/vendor_ruby/bundler/cli.rb
-- System
Package: haml-elisp
Version: 1:3.0.15-4
Severity: important
As emacs24 has entered unstable, haml-elisp no longer works with it,
and can break setups. When installing haml-elisp, I get:
(...)
Install haml-elisp for emacs24
+ set -e
+ SRC_FILE=haml-mode.el
+ SUPPORTED_EMACSEN=^emacs23$
+
Luca Falavigna dijo [Fri, May 31, 2013 at 11:56:11AM +]:
Hi,
please remove the boilerplate entries in the copyright file.
Ugh, gross oversight from me. Of course, fortunately it's not missing
information, but has the extra boilerplate ;-)
Doing it right away. Thanks!
Package: ftp.debian.org
Severity: normal
ruby-parsetree is not (and will not be) compatible with Ruby versions
above 1.8.x, and as we aim to remove it for Jessie, we have agreed to
start removing packages with low popcon. Ruby-parsetree is *not* a
leaf package, but for newer Ruby versions, a
Package: ftp.debian.org
Severity: normal
ruby-ruby2ruby is not (and will not be) compatible with Ruby versions
above 1.8.x, and as we aim to remove it for Jessie, we have agreed to
start removing leaf packages with low popcon.
Thank you,
___
Package: wnpp
Severity: wishlist
Owner: Gunnar Wolf gw...@gwolf.org
* Package name: ruby-http-cookie
Version : 1.0.1
Upstream Author : Akinori MUSHA k...@idaemons.org, Eric Hodel, Aaron
Patterson, Mike Dalessio
* URL : https://github.com/sparklemotion/http-cookie
Jérémy Bobbio dijo [Mon, Sep 02, 2013 at 09:08:35AM +0200]:
(...)
Oh crap… my bad.
gettext 3.0 dropped support for Ruby 1.8. But given this is still our
default interpreter, its reverse dependencies are likely to fail.
Given the following:
(...)
Trying to re-introduce compatibility with
Package: librfilter-ruby1.8
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi YAEGASHI Takeshi,
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
Package: libgdal-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Debian GIS Project,
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
Package: libwebapp-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi NIIBE Yutaka,
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
Package: liblangscan-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi NIIBE Yutaka,
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
Package: libescape-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi NIIBE Yutaka,
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
Package: libamrita2-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi TANIGUCHI Takaki,
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
Package: libhdfeos5-ruby1.8
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Debian GIS Project,
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
Package: libstfl-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Nico Golde,
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
Package: libhtml-htmltokenizer-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Deepak Tripathi,
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
Package: libneedle-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Tatsuki Sugiura,
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
Package: libgv-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi David Claughton,
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
Package: libmaruku-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Debian Ruby Extras Maintainers,
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
Package: librdf-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Dave Beckett,
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
Package: libabstract-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Bryan McLellan,
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
Package: libneedle-extras-ruby1.8
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Tatsuki Sugiura,
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
Package: libsvn-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Peter Samuelson,
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
Package: libobexftp-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Hendrik Sattler,
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
Package: libmapscript-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Debian GIS Project,
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
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
tags 720250 + confirmed
thanks
Hi,
I confirm I stumbled upon this problem as well. It is caused by
ruby-inline, where I filed it as #725115. I am not just reassigning as
there are subtleties to both sides of the problem :-|
___
I tried to upload to the newest upstream release, 3.12.2, but the bug
behaviour persists.
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
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
Source: ruby-bdb
Version: 0.6.6-1
Severity: serious
Justification: FTBFS on amd64
Attempting to build this package on AMD64, I got the following
results:
88
/usr/bin/install -c -m 0755 bdb.so ./.gem.20140313-22704-1exw4lh
make[1]:
reopen 730960
tags 730960 + pending
thanks
David Suárez dijo [Fri, Mar 14, 2014 at 07:29:52PM +0100]:
Maybe I miss something, but on current unstable version (0.6.5-7), we have:
Vcs-Browser: http://git.debian.org/?p=pkg-ruby-extras/ruby-bdb.git;a=summary
Homepage:
tags 747736 + unreproducible
thanks
Hi,
I have attempted to build this package on a clean chroot, and found no
problem (and thus would like to confirm with you whether this RC bug
report can be closed).
What I found in your failure build log is that all of the failing
tests I checked mention:
Package: ruby-gruff
Version: 0.6.0-1
Followup-For: Bug #841133
This bug does not only happen at build time, it makes Gruff completely
unusable :-(
$ irb
>> require 'gruff'
=> true
>> g=Gruff::Bar.new '100x100'
/usr/lib/ruby/vendor_ruby/gruff/base.rb:968: [BUG] Segmentation fault at
101 - 156 of 156 matches
Mail list logo
