This points to the fact that the command-not-found package was never
uploaded to cosmic at time of beta release like it is supposed to be.
** Package changed: linux (Ubuntu) => command-not-found (Ubuntu)
** Changed in: command-not-found (Ubuntu)
Importance: Undecided => Medium
** Changed in: command-not-found (Ubuntu)
Status: New => In Progress
** Changed in: command-not-found (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Steve Langasek
(vorlon)
** Also affects: command-not-found (Ubuntu Cosmic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802462
Title:
When s390-tools-zkey package is not installed 'zkey -h' lists wrong
package name in apt hint
Status in Ubuntu on IBM z Systems:
Triaged
Status in command-not-found package in Ubuntu:
In Progress
Status in command-not-found source package in Cosmic:
New
Bug description:
[SRU Justification]
The contents of command-not-found-data in cosmic are out of date with respect
to the archive, resulting in misleading suggestions offered to users for some
commands.
[Test case]
1. Install command-not-found
2. . /etc/bash.bashrc
3. Install btrfs-progs.
4. Ensure that the package cloud-init is not installed.
5. Type 'btrfs-debug-tree'. Observe that bash suggests installing
btrfs-progs, even though btrfs-progs is installed (and does not provide a
btrfs-debug-tree command).
6. Type 'cloud-id'. Observe that bash returns the general 'command not
found' error.
7. Install command-not-found from -proposed.
8. Type 'btrfs-debug-tree' again. Observe that bash correctly reports
'command not found'.
9. Type 'cloud-id' again. Observe that bash suggests to install the
cloud-init package.
[Regression potential]
In the event that there is bad data in the database update, command-not-found
may return wrong suggestions after this SRU. It is already doing so currently,
and there are no known instances of bad data in the database updates, so this
possibility is not a reason to block the SRU.
OS: Ubuntu 18.10 providing s390-tools_2.6.0-0ubuntu7_s390x.deb
When the 's390-tools-zkey' package is NOT installed, the installation hint
given by zkey -h is not as expected
Environment:
IBM Z 13 or Z 14 LPAR or z/VM
Details
=======
On an IBM Z13 or Z14 based Ubuntu 18.10 system where the 'zkey' tool is not
yet installed,
the installation hint given by zkey is misleading.
The hint should read: 'apt install s390-tools-zkey'
The apt-cache search for zkey displays the expected package name,
though.
Ran the above install command which succeeded as expected, the zkey
tool was available.
---uname output---
Linux system 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:06:06 UTC 2018
s390x s390x s390x GNU/Linux
Machine Type = IBM Type: 3906 LIC Identifier: 505724ff5b747876
---Debugger---
A debugger is not configured
---Steps to Reproduce---
1.) Install Ubuntu 18.10 onto an LPAR or z/VM system
2.) Ensure the zkey tool is not installed
3.) run: zkey -h
# zkey -h
Command 'zkey' not found, but can be installed with:
apt install s390-tools
Userspace tool common name: apt
The userspace tool has the following bit modes: 64bit
Userspace rpm: s390-tools_2.6.0-0ubuntu7_s390x.deb
Userspace tool obtained from project website: na
*Additional Instructions for [email protected]:
-Attach ltrace and strace of userspace application.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1802462/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
