-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"swupd verify" and "swupd verify --fix" have different opinions #607
Comments
To be clear: the issue here (bug or, maybe a feature) is the fact that a verify and a fix disagree whether the system is good. |
This is a bug. Swupd fix should be a dry-run for swupd verify --fix |
Related feature request: #536 |
one thing I find strange is that the results from "swupd verify --fix" shown above, are trying to remove files even when the "--picky" option was not used. As far as I know verify should only attempt to remove files if "--fix --picky" are used together. |
@otaviobp I guess what you meant was "swupd verify" should be a dry-run for "swupd verify --fix", right? If so, does that mean that "swupd verify" should list the files with a hash mismatch + files that are missing only? what about files that should be deleted as mentioned in #536? If these need to be included in the output from "swupd verify" then it is not quite a dry-run for "swupd verify --fix", because that doesn't delete extra files, for that you would need to use --picky. I guess in that case the correct statement would be that "swupd verify" should be a dry-run of "swupd verify --fix --picky". |
@castulo |
While debugging clearlinux/distribution#206, I've found this:
Maybe the output of the commands need a better description, but I'd guess that if
swupd verify
is happy, thenswupd verify --fix
would have nothing to fix.The text was updated successfully, but these errors were encountered: