The command-not-found package is responsible for showing that
information. I'm not sure how the internals work though, so it's
possible there's something wonky with the systemd package that confuses
command-not-found.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
** Also affects: command-not-found (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
** Changed in: command-not-found (Ubuntu)
Importance: Undecided => Low
** Summary changed:
- When running bootctl, wrong promt is displayed
+ command-not-found claims bootctl can be installed with `sudo apt install
systemd`
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1996820
Title:
command-not-found claims bootctl can be installed with `sudo apt
install systemd`
Status in command-not-found package in Ubuntu:
New
Status in systemd package in Ubuntu:
Incomplete
Bug description:
On a fresh 22.10 install, I tried to install systemd-boot by running
bootctl. I get a message saying
"
Command 'bootctl' not found, but can be installed with:
sudo apt install systemd
"
But actually the package to install is systemd-boot.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1996820/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
