← Back to issue list

"snapcraft extension" both does and does not accept "--verbose"

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1986643
Type
issue
State
closed
Author
~rpjday
Labels
craft-1292
Created
Updated
Closed

Current evaluation

Reported inconsistent handling of --verbose: verbose logging started, then the CLI errored with 'No such option'. Fixed by snapcore/snapcraft#4024 (commit be005b98d) forwarding --verbose/-v to snapcraft_legacy, shipped in snapcraft 7.3; tracked as CRAFT-1292.

Resolution: closed resolved

Reason: Commit be005b98d ("cli: pass `--verbose` and `-v` to snapcraft_legacy (#4024)", implementing CRAFT-1292) forwarded the verbosity flags when re-executing into legacy code, and maintainer mr-cal confirmed on 2023-06-02 that the fix was released with snapcraft 7.3. Later follow-ups #5646 and #5680 added verbosity arg support in snapcraft_legacy before it was removed entirely.

Evaluated by: mr-cal-bot

No scores available.

Issue body

This might apply to other commands, but I noticed it here. First, running the command successfully: $ snapcraft extension kde-neon The KDE Neon extension. This extension makes it easy to assemble KDE based applications using the Neon stack. ... etc etc snipped ... $ However, if I want to run the very same command verbosely (which I should be able to, yes?): $ snapcraft extension --verbose kde-neon Starting Snapcraft 7.1.1.post16+gitc34b9478 Logging execution to '/home/rpjday/.cache/snapcraft/log/snapcraft-20220816-054228.857438.log' Usage: snapcraft extension [OPTIONS] NAME Try 'snapcraft extension -h' for help. Error: No such option: --verbose $ Curiously, that command recognizes "--verbose" in that it *starts* generating output verbosely, then suddenly it decides it *doesn't* like that option, and errors out. That seems inconsistent.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Reported inconsistent handling of --verbose: verbose logging started, then the CLI errored with 'No such option'. Fixed by snapcore/snapcraft#4024 (commit be005b98d) forwarding --verbose/-v to snapcraft_legacy, shipped in snapcraft 7.3; tracked as CRAFT-1292.
stealth/space-bunny-alpha — closed resolved Fixed in canonical/snapcraft#4024 by forwarding --verbose and -v to snapcraft_legacy; released in Snapcraft 7.3.
stealth/space-bunny-alpha — closed resolved Fixed by merged PR #4024, which forwarded --verbose and -v to snapcraft_legacy.
qwen/qwen3.6-35b-a3b — — Closed without resolution. The snapcraft extension command inconsistently handled the --verbose flag, initializing verbose logging before failing with an unrecognized option error. No fix or discussion followed.
qwen/qwen3.6-35b-a3b — — Inconsistent --verbose flag handling caused the snapcraft extension command to error after initiating verbose output. The issue was closed without resolution or fix.
qwen/qwen3.6-35b-a3b — — Closed without documented resolution or fix. The reported inconsistency where the verbose flag triggered logging but then threw a no such option error remains unresolved. No comments or merge details were provided.
qwen3.6-35b-a3b-mtp-q6 — — Closed without resolution. The reported CLI inconsistency where --verbose triggers logging but fails with an unrecognized option error remains unaddressed. The issue appears abandoned with no comments or patches submitted.

Update history

Date Change
created

Related work

  • Likely Fixed By: snapcore/snapcraft#4024 (confidence 98%)

    Merged PR, commit be005b98d, passes --verbose/-v to snapcraft_legacy; implements CRAFT-1292, the label on this issue.

  • Related To: snapcraft#5646 (confidence 80%)

    Follow-up commit 3aeded2fa 'feat(snapcraft_legacy): support verbosity args' in the 8.x legacy code path.

  • Related To: snapcraft#5680 (confidence 75%)

    Follow-up commit 4a7663069 'feat(snapcraft_legacy): support verbosity args in non-lifecycle commands', covering commands like 'extension'.

  • Superseded By: snapcraft#6403 (confidence 55%)

    Later commit ffb164b7a removed snapcraft_legacy entirely, making the forwarding shim obsolete.

Related issues

Issue Project State Summary Similarity
#1980515 Snapcraft 7 inconsistent CLI options handling snapcraft (launchpad) closed Snapcraft 7's inconsistent --verbose handling was fixed by snapcore/snapcraft#4024 (commit be005b98d); a maintainer confirmed it was resolved in Snapcraft 7.3.
80%
#1980686 snapcraft build won't allow `verbose` flag snapcraft (launchpad) closed Snapcraft 7.0.11 fixed core22 only; canonical/snapcraft#4024 (be005b98d) later forwarded -v and --verbose to snapcraft_legacy for core18/core20 builds.
78%
#4024 cli: pass `--verbose` and `-v` to snapcraft_legacy snapcraft merged Merged #4024 (commit be005b98d) to forward --verbose and -v to snapcraft_legacy for core18/core20 builds, implementing CRAFT-1292.
74%
#2016662 7.3.1 Error: No such option: --verbosity (Possible options: --verbose, --version) snapcraft (launchpad) closed Legacy (core20) code path rejected --verbosity/--verbose/--quiet. Fixed via canonical/snapcraft#5423: PR #5646 (commit 3aeded2fa) plus follow-up PR #5680 (4a7663069), shipped in Snapcraft 8.11/8.11.1; snapcraft_legacy later removed entirely.
74%