Package: ruby2.0
Version: 2.0.0.353-1
Severity: important
Dear Maintainer,
After installing ruby2.0 from unstable, I used `update-alternatives` to
switch the default interpreter, with the following result.
$ sudo update-alternatives --config ruby
There are 3 choices for the alternative ruby (providing /usr/bin/ruby).
Selection Path Priority Status
------------------------------------------------------------
* 0 /usr/bin/ruby1.9.1 51 auto mode
1 /usr/bin/ruby1.8 50 manual mode
2 /usr/bin/ruby1.9.1 51 manual mode
3 /usr/bin/ruby2.0 50 manual mode
Press enter to keep the current choice[*], or type selection number: 3
update-alternatives: using /usr/bin/ruby2.0 to provide /usr/bin/ruby
(ruby) in manual mode
update-alternatives: warning: skip creation of
/usr/share/man/man1/rdoc.1.gz because associated file
/usr/share/man/man1/rdoc2.0.1.gz (of link group ruby) doesn't exist
update-alternatives: warning: skip creation of
/usr/share/man/man1/testrb.1.gz because associated file
/usr/share/man/man1/testrb2.0.1.gz (of link group ruby) doesn't exist
Indeed, attempting to read the rdoc and testrb man pages doesn't work.
`apt-file` also shows that the the 2.0.1 versions of the man pages don't
appear to be in the archive:
$ apt-file search man1/rdoc
ruby1.8: /usr/share/man/man1/rdoc1.8.1.gz
ruby1.9.1: /usr/share/man/man1/rdoc1.9.1.1.gz
ruby1.9.3: /usr/share/man/man1/rdoc1.9.3.1.gz
Thanks for your hard work bringing ruby 2 to Debian!
Regards,
Scott.
-- System Information:
Debian Release: 7.3
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable'),
(500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages ruby2.0 depends on:
ii libc6 2.17-97
ii libruby2.0 2.0.0.353-1
ii rubygems-integration 1.4
ruby2.0 recommends no packages.
ruby2.0 suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
