2010/8/26 Lucas Nussbaum lu...@lucas-nussbaum.net:
That worked fine until Ruby 1.9.1, but apparently a change in Ruby
1.9.2 broke Rubygems 1.3.7. This is exhibited by two bugs:
[...]
- rubygems doesn't work:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588125
I trace the following error:
Hi,
Thanks for the follow-up. Quantlib (upstream) and I figured out a workaround.
In previous versions we had gotten by without the configure step -- and hence
no Makefile was created and present. That did not seem to upset earlier
versions but it set up the current versions. Switching to
Hi,
Now, however, using what is in unstable, ie
Get:33 http://ftp.us.debian.org unstable/main libruby1.8 1.8.7.173-1 [1679kB]
Get:34 http://ftp.us.debian.org unstable/main ruby1.8 1.8.7.173-1 [290kB]
Get:35 http://ftp.us.debian.org unstable/main ruby 4.2 [20.6kB]
Get:36
Hi,
Can someone please comment on the status of a fix for this bug in
Etch?
We are working on our svn-repos.
Thank you.
--
ay
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hi,
Such a layout only makes sense if someone want to coinstall ruby 1.9.0 and
ruby
1.9.1: if we have only one dir (for 1.9), then won't be able to install two
versions of the same lib (one for 1.9.0, one for 1.9.1). On the other hand, if
a lib was ported to 1.9.0, it's likely to be easy to
Hi,
upstream ruby removed file version.h . But we already have lots of fixes
based on string RUBY_VERSION_CODE, so it's easier to recreate this
version.h for ruby1.9 package. This patch fix this bug.
It also fix another bug introduced by ruby1.9 upstream changes.
Basically, we should not
# Automatically generated email from bts, devscripts version 2.10.7
# This is changes of ruby1.9, so Bug#441489 is of libinotify-ruby.
reassign 441489 libinotify-ruby
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Junichi Uekawa wrote:
Please follow up this discussion in 399706. I agree Ruby is stupid
here, but I don't intend to work around it.
I don't think so.
It is not a bug of Ruby and it is bug of apt-listbugs.
I think that the behaviour is intended by the upstream author of SOAP4r.
The current
Daniel Schepler wrote:
Makefile:143: *** missing separator. Stop.
Does the line 143 contain |#_!!_#|?
--
akira yamada
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
must be accompanied
by a verbatim copy of its copyright and distribution license
in the file `/usr/share/doc/package/copyright'.
So, we will add a note of this fact in copyright
and close this bug.
--
akira yamada
that it is not a serious bug.
--
akira yamada
is distributed with dual-license which is Ruby's License or GPL.
URL:http://www.ruby-lang.org/en/LICENSE.txt
--
akira yamada
tk' from irb1.8
I could not reproduce the problem.
$ irb1.8
irb(main):001:0 require tk
= true
Please send me another reproduceable code.
--
akira yamada
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
/usr/lib/ruby/1.8/yaml.rb:133:in `load'
from /usr/bin/raggle:4795:in `load_config'
from /usr/bin/raggle:5441:in `main'
from /usr/bin/raggle:6461
I posted a workaround to ruby-core list:
URL:http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/6159
--
akira yamada
Martin Pitt wrote:
There is a safe mode bypass in all Ruby versions:
I already prepared the new package and
sent a notice to security team.
But I cannot yet get DSA
--
akira yamada
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
ruby1.8_1.8.3-1 is in unstable. please try it.
If you get SEGV with 1.8.3-1, please send the backtrace.
Thank you.
--
akira yamada
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
.
--
akira yamada
17 matches
Mail list logo
