Bug#483947: ruby1.9: uses wrong $LOAD_PATH

2008-07-13 Thread Lucas Nussbaum
On 02/06/08 at 13:54 +0200, Lucas Nussbaum wrote:
 On 02/06/08 at 18:23 +0900, akira yamada / ?? wrote:
  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 port from 1.9.0 to 
   1.9.1.
   So we could probably do that as Debian-specific changes if necessary.
   
   I think that this should be raised on ruby-dev@ (others are likely to run 
   into
   the same problem). Akira-san, Daigo-san, could one of you ask for the Ruby
   developers' opinion?
  
  I asked about this change at [ruby-dev:32751] and [ruby-dev:32754].
  
   * the change is for possibility of incompatibility.
 [ruby-dev:32752]
   * 1.9.0 as dirname may be kept if there is no incompatibility.
 [ruby-dev:32759]
 
 OK, thank you. So there's a few packages that need to be fixed:
 [EMAIL PROTECTED]:~$ zcat /org/ftp.debian.org/ftp/dists/sid/Contents-i386.gz 
 | grep ^usr/lib/ruby/1.9/ | awk '{print $2}' | sort | uniq
 devel/rant
 interpreters/libgettext-ruby1.9
 interpreters/libhtree-ruby1.9
 interpreters/libncurses-ruby1.9
 libs/libactiverecord-ruby1.9
 libs/libactivesupport-ruby1.9
 libs/libcairo-ruby1.9
 libs/libflexmock-ruby1.9
 libs/libgpgme-ruby1.9
 libs/libhpricot-ruby1.9
 libs/libopen4-ruby1.9
 libs/libwww-mechanize-ruby1.9
 net/libnet-netrc-ruby1.9
 web/libfcgi-ruby1.9

Updated list:
[EMAIL PROTECTED]:~$ zcat $(ls
/org/ftp.debian.org/ftp/dists/sid/Contents-*.gz |grep -v hurd |grep -v
m68k) | grep ^usr/lib/ruby/1.9/ | awk '{print $2}' | sort | uniq
interpreters/libgettext-ruby1.9 -- fix uploaded
net/libnet-netrc-ruby1.9 -- fix uploaded
web/libfcgi-ruby1.9 -- fix uploaded
libs/libinotify-ruby1.9 -- only mips and mipsel affected. binNMUs
requested.
interpreters/libncurses-ruby1.9 -- only lagging on hppa, fixed
everywhere else
libs/libcairo-ruby1.9 -- blocked by #487204
-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#483947: ruby1.9: uses wrong $LOAD_PATH

2008-07-12 Thread Lucas Nussbaum
severity 483947 important
thanks

This is just a meta-bug to track the other bugs on the same topic.
There's no need to keep it RC.
-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#483947: ruby1.9: uses wrong $LOAD_PATH

2008-06-05 Thread Lucas Nussbaum
retitle 483947 must install ruby1.9 libs in /usr/lib/ruby/1.9.0, not 
/usr/lib/ruby/1.9
clone 483947 -1
reassign -1 ruby-pkg-tools 0.13
clone 483947 -2
clone 483947 -3
clone 483947 -4
clone 483947 -5
clone 483947 -6
clone 483947 -7
reassign -2 libactiverecord-ruby1.9 2.1.0-1
reassign -3 libactivesupport-ruby1.9 2.1.0-1
reassign -4 libflexmock-ruby1.9 0.8.2-1
reassign -5 libhpricot-ruby1.9 0.6-1
reassign -6 libopen4-ruby1.9 0.9.6-2
reassign -7 libwww-mechanize-ruby1.9 0.7.6-1
clone 483947 -8
clone 483947 -9
clone 483947 -10
clone 483947 -11
clone 483947 -12
clone 483947 -13
reassign -8 libfcgi-ruby1.9 0.8.7-4
reassign -9 libgettext-ruby1.9 1.91.0-1
reassign -10 libhtree-ruby1.9 0.7-1
reassign -11 libncurses-ruby1.9 1.1-2
reassign -12 libnet-netrc-ruby1.9 0.2.1-1
reassign -13 rant 0.5.8-4
block 483947 by -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 -11 -12 -13
thanks

On 02/06/08 at 13:54 +0200, Lucas Nussbaum wrote:
 On 02/06/08 at 18:23 +0900, akira yamada / ?? wrote:
  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 port from 1.9.0 to 
   1.9.1.
   So we could probably do that as Debian-specific changes if necessary.
   
   I think that this should be raised on ruby-dev@ (others are likely to run 
   into
   the same problem). Akira-san, Daigo-san, could one of you ask for the Ruby
   developers' opinion?
  
  I asked about this change at [ruby-dev:32751] and [ruby-dev:32754].
  
   * the change is for possibility of incompatibility.
 [ruby-dev:32752]
   * 1.9.0 as dirname may be kept if there is no incompatibility.
 [ruby-dev:32759]
 
 OK, thank you. So there's a few packages that need to be fixed:
 [EMAIL PROTECTED]:~$ zcat /org/ftp.debian.org/ftp/dists/sid/Contents-i386.gz 
 | grep ^usr/lib/ruby/1.9/ | awk '{print $2}' | sort | uniq
 devel/rant
 interpreters/libgettext-ruby1.9
 interpreters/libhtree-ruby1.9
 interpreters/libncurses-ruby1.9
 libs/libactiverecord-ruby1.9
 libs/libactivesupport-ruby1.9
 libs/libcairo-ruby1.9
 libs/libflexmock-ruby1.9
 libs/libgpgme-ruby1.9
 libs/libhpricot-ruby1.9
 libs/libopen4-ruby1.9
 libs/libwww-mechanize-ruby1.9
 net/libnet-netrc-ruby1.9
 web/libfcgi-ruby1.9

OK, I split this package list into several categories:
Use the extconf.rb class from ruby-pkg-tools. Cloned to
ruby-pkg-tools, after that the package need to be updated to
build-depend on r-p-t  [version fixed].
libcairo-ruby1.9
libgpgme-ruby1.9

Install the libs manually. Package needs to be fixed. Bug cloned.
Maintained by pkg-ruby-extras:
libactiverecord-ruby1.9
libactivesupport-ruby1.9
libflexmock-ruby1.9
libhpricot-ruby1.9
libopen4-ruby1.9
libwww-mechanize-ruby1.9

Maintained by other maintainers. Bug cloned:
libfcgi-ruby1.9
libgettext-ruby1.9
libhtree-ruby1.9
libncurses-ruby1.9
libnet-netrc-ruby1.9
rant
-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#483947: ruby1.9: uses wrong $LOAD_PATH

2008-06-02 Thread Lucas Nussbaum
On 01/06/08 at 14:29 +0200, Paul van Tilburg wrote:
 Package: ruby1.9
 Version: 1.9.0.1-1
 Severity: grave
 Justification: renders package unusable
 
 The Ruby 1.9 interpreter in Debian uses /usr/lib/ruby/1.9.0 instead of
 /usr/lib/ruby/1.9 as system base in the $LOAD_PATH.  Since all -ruby1.9
 packages install to the /usr/lib/ruby/1.9 directory, they are all
 unusable!

from ruby1.9's NEWS.Debian file:
ruby1.9 (1.9.0.0-1) unstable; urgency=low

  $LOAD_PATH is changed in Ruby 1.9.0-0 as the following:

[/usr/local/lib/site_ruby/1.9.0,
 /usr/local/lib/site_ruby/1.9.0/i486-linux,
 /usr/local/lib/site_ruby/1.9/i386-linux,
 /usr/local/lib/site_ruby,
 /usr/lib/ruby/vendor_ruby/1.9.0,
 /usr/lib/ruby/vendor_ruby/1.9.0/i486-linux,
 /usr/lib/ruby/vendor_ruby,
 /usr/lib/ruby/1.9.0,
 /usr/lib/ruby/1.9.0/i486-linux,
 /usr/lib/ruby/1.9/i386-linux,
 .]

  This changes was introduced because Ruby 1.9.1 (or later version) may be
  incompatible with this version of Ruby.  If you have libraries in old
  $LOAD_PATH, please rebuild it with this version of ruby1.9-dev package.

 -- akira yamada [EMAIL PROTECTED]  Wed, 26 Dec 2007 10:34:48 +0900

It's not a Debian change, it's an upstream one.

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 port from 1.9.0 to 1.9.1.
So we could probably do that as Debian-specific changes if necessary.

I think that this should be raised on ruby-dev@ (others are likely to run into
the same problem). Akira-san, Daigo-san, could one of you ask for the Ruby
developers' opinion?
-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#483947: ruby1.9: uses wrong $LOAD_PATH

2008-06-02 Thread akira yamada / ??????
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 port from 1.9.0 to 1.9.1.
 So we could probably do that as Debian-specific changes if necessary.
 
 I think that this should be raised on ruby-dev@ (others are likely to run into
 the same problem). Akira-san, Daigo-san, could one of you ask for the Ruby
 developers' opinion?

I asked about this change at [ruby-dev:32751] and [ruby-dev:32754].

 * the change is for possibility of incompatibility.
   [ruby-dev:32752]
 * 1.9.0 as dirname may be kept if there is no incompatibility.
   [ruby-dev:32759]

-- 
ay



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#483947: ruby1.9: uses wrong $LOAD_PATH

2008-06-02 Thread Lucas Nussbaum
On 02/06/08 at 18:23 +0900, akira yamada / ?? wrote:
 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 port from 1.9.0 to 
  1.9.1.
  So we could probably do that as Debian-specific changes if necessary.
  
  I think that this should be raised on ruby-dev@ (others are likely to run 
  into
  the same problem). Akira-san, Daigo-san, could one of you ask for the Ruby
  developers' opinion?
 
 I asked about this change at [ruby-dev:32751] and [ruby-dev:32754].
 
  * the change is for possibility of incompatibility.
[ruby-dev:32752]
  * 1.9.0 as dirname may be kept if there is no incompatibility.
[ruby-dev:32759]

OK, thank you. So there's a few packages that need to be fixed:
[EMAIL PROTECTED]:~$ zcat /org/ftp.debian.org/ftp/dists/sid/Contents-i386.gz | 
grep ^usr/lib/ruby/1.9/ | awk '{print $2}' | sort | uniq
devel/rant
interpreters/libgettext-ruby1.9
interpreters/libhtree-ruby1.9
interpreters/libncurses-ruby1.9
libs/libactiverecord-ruby1.9
libs/libactivesupport-ruby1.9
libs/libcairo-ruby1.9
libs/libflexmock-ruby1.9
libs/libgpgme-ruby1.9
libs/libhpricot-ruby1.9
libs/libopen4-ruby1.9
libs/libwww-mechanize-ruby1.9
net/libnet-netrc-ruby1.9
web/libfcgi-ruby1.9
-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#483947: ruby1.9: uses wrong $LOAD_PATH

2008-06-01 Thread Paul van Tilburg
Package: ruby1.9
Version: 1.9.0.1-1
Severity: grave
Justification: renders package unusable

The Ruby 1.9 interpreter in Debian uses /usr/lib/ruby/1.9.0 instead of
/usr/lib/ruby/1.9 as system base in the $LOAD_PATH.  Since all -ruby1.9
packages install to the /usr/lib/ruby/1.9 directory, they are all
unusable!

Regards,
Paul

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (102, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.22-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages ruby1.9 depends on:
ii  libc6 2.7-11 GNU C Library: Shared libraries
ii  libruby1.91.9.0.1-1  Libraries necessary to run Ruby 1.

ruby1.9 recommends no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]