command-not-found advice for LLVM programs is wrong

Bug #682267 reported by Matt Giuca
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
command-not-found (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: llvm

I don't know if this is a problem with the llvm package or the llvm-2.7 package, but the command-not-found advice I was given for LLVM programs on Maverick is wrong.

I tried to use the program "opt" and it told me to install llvm-2.7. I installed llvm-2.7 and it didn't install the program "opt". I finally installed the package llvm, which installed the correct program. Oddly, this installed llvm-2.8 and symlinked to that, so llvm-2.7 wasn't even the correct version of the package to suggest.

The command-not-found should suggest to install the package "llvm", not "llvm-2.7".

$ opt
The program 'opt' is currently not installed. You can install it by typing:
sudo apt-get install llvm-2.7
$ sudo apt-get install llvm-2.7
<installed>
$ opt
The program 'opt' is currently not installed. You can install it by typing:
sudo apt-get install llvm-2.7
$ dpkg -L llvm-2.7
...
/usr/bin/opt-2.7
...
<hmm...>
$ sudo apt-get install llvm
<installed>
$ opt
<works>

Matthias Klose (doko)
affects: llvm (Ubuntu) → command-not-found (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.