epspdf: dependency on ruby missing in texlive-pictures

[Martin Weilandt]

Hello,
I'm new to this business but I'm sure the following behavior is a bug: When (with texlive-pictures installed) running
"epspdf test.eps"
I got the error
"/usr/bin/epspdf: 3: ruby: not found"
After running
"sudo apt-get install ruby"
the program epspdf worked just fine.

I checked the packages and there is no dependency on ruby in texlive-pictures, although epspdf (as one of the programs in texlive-picture) needs ruby to run. I would call this a bug (although it's easy to fix).

I'm running an updated Ubuntu 11.04.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: texlive-pictures 2009-11
ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic i686
Architecture: i386
Date: Sun Aug 21 00:40:51 2011
InstallationMedia: Lubuntu 11.04 "Natty Narwhal" - i386 (20101203)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SourcePackage: texlive-base
UpgradeStatus: No upgrade log present (probably fresh install)

[Martin Konrad (info-martin-konrad)]

I can confirm that issue on 12.04. Please add the missing dependency to package "ruby".

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Norbert Preining (preining)]

There are a lot of different things in texlive-picture, epspdf being one of it only.
ruby is already a *recommends*. If you decided to *not* install recommends, which are installed normally by default, it is up to you to deal with that.

From my side (as maintainer of the Debian packages) I will not change anything here as I consider this bug invalid.

Norbert

[Logan Rosen (logan)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 713210, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.