Activity log for bug #1800544

Date Who What changed Old value New value Message
2018-10-29 21:15:50 Dan Streetman bug added bug
2018-10-29 21:16:23 Dan Streetman nominated for series Ubuntu Cosmic
2018-10-29 21:16:23 Dan Streetman bug task added nvme-cli (Ubuntu Cosmic)
2018-10-29 21:16:23 Dan Streetman nominated for series Ubuntu Xenial
2018-10-29 21:16:23 Dan Streetman bug task added nvme-cli (Ubuntu Xenial)
2018-10-29 21:16:23 Dan Streetman nominated for series Ubuntu Bionic
2018-10-29 21:16:23 Dan Streetman bug task added nvme-cli (Ubuntu Bionic)
2018-10-29 21:16:30 Dan Streetman nvme-cli (Ubuntu Xenial): status New Invalid
2018-10-29 21:16:34 Dan Streetman nvme-cli (Ubuntu Bionic): status New In Progress
2018-10-29 21:16:37 Dan Streetman nvme-cli (Ubuntu Cosmic): status New In Progress
2018-10-29 21:16:39 Dan Streetman nvme-cli (Ubuntu Cosmic): importance Undecided Low
2018-10-29 21:16:41 Dan Streetman nvme-cli (Ubuntu Bionic): importance Undecided Low
2018-10-29 21:16:43 Dan Streetman nvme-cli (Ubuntu Bionic): assignee Dan Streetman (ddstreet)
2018-10-29 21:16:44 Dan Streetman nvme-cli (Ubuntu Cosmic): assignee Dan Streetman (ddstreet)
2019-04-04 12:42:02 Dan Streetman bug task deleted nvme-cli (Ubuntu Xenial)
2020-03-27 18:19:56 Dan Streetman nvme-cli (Ubuntu Cosmic): status In Progress Won't Fix
2020-03-27 18:55:44 Dan Streetman nvme-cli (Ubuntu): status In Progress Fix Released
2020-03-27 18:57:14 Dan Streetman description [impact] The nvme-cli tool includes a bash completion script, but it drops it in the wrong location. This prevents it from actually being sourced and so the nvme tool doesn't do param autocompletion. [test case] install the nvme-cli package and try to auto-complete any of its params. They do not auto-complete. [regression potential] moving where this bash autocompletion file is only has the potential to break nvme's autocompletion. As that does not currently work at all, the regression potential seems low. [other info] bash completion files appear to be managed inside the 'bash-completion' pkg, and only rarely are managed directly by owning packages. Those that do should drop their scripts into /etc/bash_completion.d/, not /usr/share/bash_completion.d/. [impact] The nvme-cli tool includes a bash completion script, but it drops it in the wrong location. This prevents it from actually being sourced and so the nvme tool doesn't do param autocompletion. [test case] install the nvme-cli package and try to auto-complete any of its params. They do not auto-complete. [regression potential] moving where this bash autocompletion file is only has the potential to break nvme's autocompletion. As that does not currently work at all, the regression potential seems low. [other info] bash completion files appear to be managed inside the 'bash-completion' pkg, and only rarely are managed directly by owning packages. Those that do should drop their scripts into /usr/share/bash-completion/completions/, not /usr/share/bash_completion.d/. While the packaging has not changed in how it lists the bash completion script, the eoan and later packages do place the completion into the correct location; only bionic places it in the wrong location.
2020-03-27 18:58:51 Dan Streetman description [impact] The nvme-cli tool includes a bash completion script, but it drops it in the wrong location. This prevents it from actually being sourced and so the nvme tool doesn't do param autocompletion. [test case] install the nvme-cli package and try to auto-complete any of its params. They do not auto-complete. [regression potential] moving where this bash autocompletion file is only has the potential to break nvme's autocompletion. As that does not currently work at all, the regression potential seems low. [other info] bash completion files appear to be managed inside the 'bash-completion' pkg, and only rarely are managed directly by owning packages. Those that do should drop their scripts into /usr/share/bash-completion/completions/, not /usr/share/bash_completion.d/. While the packaging has not changed in how it lists the bash completion script, the eoan and later packages do place the completion into the correct location; only bionic places it in the wrong location. [impact] The nvme-cli tool includes a bash completion script, but it drops it in the wrong location. This prevents it from actually being sourced and so the nvme tool doesn't do param autocompletion. [test case] install the nvme-cli package and try to auto-complete any of its params. They do not auto-complete. [regression potential] moving where this bash autocompletion file is only has the potential to break nvme's autocompletion. As that does not currently work at all, the regression potential seems low. [other info] bash completion files appear to be managed inside the 'bash-completion' pkg, and only rarely are managed directly by owning packages. Those that do should drop their scripts into /usr/share/bash-completion/completions/, not /usr/share/bash_completion.d/. The Makefile in Eoan and later does place the bash completion file into the correct subdir; only Bionic needs updating.
2020-03-27 20:36:15 Dan Streetman description [impact] The nvme-cli tool includes a bash completion script, but it drops it in the wrong location. This prevents it from actually being sourced and so the nvme tool doesn't do param autocompletion. [test case] install the nvme-cli package and try to auto-complete any of its params. They do not auto-complete. [regression potential] moving where this bash autocompletion file is only has the potential to break nvme's autocompletion. As that does not currently work at all, the regression potential seems low. [other info] bash completion files appear to be managed inside the 'bash-completion' pkg, and only rarely are managed directly by owning packages. Those that do should drop their scripts into /usr/share/bash-completion/completions/, not /usr/share/bash_completion.d/. The Makefile in Eoan and later does place the bash completion file into the correct subdir; only Bionic needs updating. [impact] The nvme-cli tool includes a bash completion script, but it drops it in the wrong location. This prevents it from actually being sourced and so the nvme tool doesn't do param autocompletion. [test case] install the nvme-cli package and try to auto-complete any of its params. They do not auto-complete. [regression potential] moving where this bash autocompletion file is only has the potential to break nvme's autocompletion. As that does not currently work at all, the regression potential seems low. [scope] fixed upstream in commit df3a06243da0433d8737cdbfa0e3ac101a3a330e that is included starting in version 1.7, so Eoan and later are already fixed. This package does not provide any bash completion script in Xenial. So only Bionic needs fixing. [other info] bash completion files appear to be managed inside the 'bash-completion' pkg, and only rarely are managed directly by owning packages. Those that do should drop their scripts into /usr/share/bash-completion/completions/, not /usr/share/bash_completion.d/. The Makefile in Eoan and later does place the bash completion file into the correct subdir; only Bionic needs updating.
2020-03-27 20:36:27 Dan Streetman description [impact] The nvme-cli tool includes a bash completion script, but it drops it in the wrong location. This prevents it from actually being sourced and so the nvme tool doesn't do param autocompletion. [test case] install the nvme-cli package and try to auto-complete any of its params. They do not auto-complete. [regression potential] moving where this bash autocompletion file is only has the potential to break nvme's autocompletion. As that does not currently work at all, the regression potential seems low. [scope] fixed upstream in commit df3a06243da0433d8737cdbfa0e3ac101a3a330e that is included starting in version 1.7, so Eoan and later are already fixed. This package does not provide any bash completion script in Xenial. So only Bionic needs fixing. [other info] bash completion files appear to be managed inside the 'bash-completion' pkg, and only rarely are managed directly by owning packages. Those that do should drop their scripts into /usr/share/bash-completion/completions/, not /usr/share/bash_completion.d/. The Makefile in Eoan and later does place the bash completion file into the correct subdir; only Bionic needs updating. [impact] The nvme-cli tool includes a bash completion script, but it drops it in the wrong location. This prevents it from actually being sourced and so the nvme tool doesn't do param autocompletion. [test case] install the nvme-cli package and try to auto-complete any of its params. They do not auto-complete. [regression potential] moving where this bash autocompletion file is only has the potential to break nvme's autocompletion. As that does not currently work at all, the regression potential seems low. [scope] fixed upstream in commit df3a06243da0433d8737cdbfa0e3ac101a3a330e that is included starting in version 1.7, so Eoan and later are already fixed. This package does not provide any bash completion script in Xenial. So only Bionic needs fixing. [other info]
2020-03-27 20:37:04 Dan Streetman description [impact] The nvme-cli tool includes a bash completion script, but it drops it in the wrong location. This prevents it from actually being sourced and so the nvme tool doesn't do param autocompletion. [test case] install the nvme-cli package and try to auto-complete any of its params. They do not auto-complete. [regression potential] moving where this bash autocompletion file is only has the potential to break nvme's autocompletion. As that does not currently work at all, the regression potential seems low. [scope] fixed upstream in commit df3a06243da0433d8737cdbfa0e3ac101a3a330e that is included starting in version 1.7, so Eoan and later are already fixed. This package does not provide any bash completion script in Xenial. So only Bionic needs fixing. [other info] [impact] The nvme-cli tool includes a bash completion script, but it drops it in the wrong location. This prevents it from actually being sourced and so the nvme tool doesn't do param autocompletion. [test case] install the nvme-cli package and try to auto-complete any of its params. They do not auto-complete. check if the bash auto-completion script is correctly located at: /usr/share/bash-completion/completions/nvme [regression potential] moving where this bash autocompletion file is only has the potential to break nvme's autocompletion. As that does not currently work at all, the regression potential seems low. [scope] fixed upstream in commit df3a06243da0433d8737cdbfa0e3ac101a3a330e that is included starting in version 1.7, so Eoan and later are already fixed. This package does not provide any bash completion script in Xenial. So only Bionic needs fixing. [other info]
2020-03-30 17:45:59 Dan Streetman tags sts-sponsor-volunteer
2020-11-17 15:31:31 Dan Streetman nvme-cli (Ubuntu Cosmic): assignee Dan Streetman (ddstreet)
2020-11-17 15:31:33 Dan Streetman nvme-cli (Ubuntu Bionic): assignee Dan Streetman (ddstreet)
2020-11-17 15:31:34 Dan Streetman nvme-cli (Ubuntu): assignee Dan Streetman (ddstreet)
2020-11-17 15:31:37 Dan Streetman nvme-cli (Ubuntu Bionic): status In Progress New
2021-06-02 14:52:36 Dan Streetman description [impact] The nvme-cli tool includes a bash completion script, but it drops it in the wrong location. This prevents it from actually being sourced and so the nvme tool doesn't do param autocompletion. [test case] install the nvme-cli package and try to auto-complete any of its params. They do not auto-complete. check if the bash auto-completion script is correctly located at: /usr/share/bash-completion/completions/nvme [regression potential] moving where this bash autocompletion file is only has the potential to break nvme's autocompletion. As that does not currently work at all, the regression potential seems low. [scope] fixed upstream in commit df3a06243da0433d8737cdbfa0e3ac101a3a330e that is included starting in version 1.7, so Eoan and later are already fixed. This package does not provide any bash completion script in Xenial. So only Bionic needs fixing. [other info] [impact] The nvme-cli tool includes a bash completion script, but it drops it in the wrong location. This prevents it from actually being sourced and so the nvme tool doesn't do param autocompletion. [test case] install the nvme-cli package and try to auto-complete any of its params. They do not auto-complete. check if the bash auto-completion script is correctly located at: /usr/share/bash-completion/completions/nvme [regression potential] moving where this bash autocompletion file is only has the potential to break nvme's autocompletion. [scope] fixed upstream in commit df3a06243da0433d8737cdbfa0e3ac101a3a330e that is included starting in version 1.7, so Eoan and later are already fixed. This package does not provide any bash completion script in Xenial. So only Bionic needs fixing. [other info]
2021-11-24 16:40:11 Heitor Alves de Siqueira nvme-cli (Ubuntu Bionic): assignee Heitor Alves de Siqueira (halves)
2021-11-24 16:40:17 Heitor Alves de Siqueira nvme-cli (Ubuntu Bionic): status New In Progress
2021-11-24 17:38:09 Heitor Alves de Siqueira tags sts-sponsor-volunteer sts-sponsor-halves
2021-11-30 21:13:24 Brian Murray nvme-cli (Ubuntu Bionic): status In Progress Fix Committed
2021-11-30 21:13:25 Brian Murray bug added subscriber Ubuntu Stable Release Updates Team
2021-11-30 21:13:28 Brian Murray bug added subscriber SRU Verification
2021-11-30 21:13:32 Brian Murray tags sts-sponsor-halves sts-sponsor-halves verification-needed verification-needed-bionic
2021-12-01 13:07:38 Heitor Alves de Siqueira tags sts-sponsor-halves verification-needed verification-needed-bionic sts-sponsor-halves verification-done verification-done-bionic
2021-12-08 00:19:14 Launchpad Janitor nvme-cli (Ubuntu Bionic): status Fix Committed Fix Released
2021-12-08 00:19:19 Chris Halse Rogers removed subscriber Ubuntu Stable Release Updates Team