command-not-found fails to work on ports architectures
Bug #533031 reported by
Emmet Hikory
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
command-not-found (Ubuntu) |
Fix Released
|
Low
|
Michael Vogt | ||
Natty |
Fix Released
|
Low
|
Michael Vogt |
Bug Description
Binary package hint: command-not-found
When used on any architecture on ports.ubuntu.com, command-not-found is unable to determine candidate commands.
ProblemType: Bug
Architecture: powerpc
Date: Sat Mar 6 09:02:47 2010
DistroRelease: Ubuntu 9.10
Package: command-not-found 0.2.38ubuntu4
PackageArchitec
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: command-not-found
Uname: Linux 2.6.31-19-powerpc ppc
Related branches
tags: | added: iso-testing |
Changed in command-not-found (Ubuntu Natty): | |
assignee: | Tobin Davis (gruemaster) → Michael Vogt (mvo) |
tags: | added: bitesize |
Changed in command-not-found (Ubuntu Natty): | |
milestone: | ubuntu-11.04-beta-1 → ubuntu-11.04-beta-2 |
To post a comment you must log in.
Further testing indicates that command-not-found does work on ports, but only for arch:all packages. This can lead to odd results, like the following (lucid armel):
No command 'strace' found, did you mean:
Command 'dtrace' from package 'systemtap-sdt-dev' (universe)