← Back to issue list

Make `quiet` verbosity print nothing in snapcraft _legacy

View original Github issue

Metadata

Project
snapcraft
Number
#5658
Type
issue
State
closed
Author
mr-cal
Labels
Status: Triaged Type: Enhancement
Created
Updated
Closed

Current evaluation

Won't fix. The snapcraft_legacy module is scheduled for removal in Snapcraft 9, rendering the quiet verbosity enhancement obsolete. Issue closed without implementation.

Suggested action:

No scores available.

Issue body

### What needs to get done `quiet` level verbosity still outputs some text for core20 snaps. This includes a few commands to setup containers and the output of `override-` scripts. This text should be not be printed in quiet mode. ### Why it needs to get done To make quiet mode actually quiet.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Won't fix. The snapcraft_legacy module is scheduled for removal in Snapcraft 9, rendering the quiet verbosity enhancement obsolete. Issue closed without implementation.
qwen/qwen3.6-35b-a3b Won't fix. The maintainer rejected the quiet verbosity enhancement for snapcraft legacy because snapcraft 9 will remove the legacy component, rendering the fix obsolete.
qwen/qwen3.6-35b-a3b Won't fix. The maintainer closed the issue because Snapcraft 9 will remove snapcraft_legacy, making the quiet verbosity enhancement unnecessary.
qwen3.6-35b-a3b-mtp-q6 Marked won't fix. The snapcraft_legacy module is scheduled for removal in Snapcraft 9, making this verbosity enhancement obsolete.
qwen3.6-35b-a3b-mtp-q6 Won't fix. The snapcraft_legacy module will be removed in Snapcraft 9, making the quiet verbosity enhancement obsolete. Issue closed without implementation.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#5423 Add `--verbosity`, `--verbose`, and `--quiet` for legacy commands in Snapcraft 8 snapcraft closed The verbosity flag enhancement for legacy Snapcraft 8 commands was closed without implementation. A maintainer outlined a level mapping, but the feature was deferred following triage and Jira ticket creation.
73%