You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For CLI options, I think there are indeed some options we need to pass to the remote host (WSL/VM/remote execution), e.g., see #557, #558, and my thought on this is that we should make all cli options platform-agnostic. For configuration files, I think we should respect the file on the host. I would like to hear your thoughts on this:)
I think that WSL is a special remote. I, myself, do not think it’s remote, it’s more a unix shell.
In my head, it is the same host.
Others might consider it a complete remote.
So, for me, I would prefer that it obeys my windows configuration, and use the same parameter as what was used from win cli.
For total remotes, physical or virtual, I agree that the remote should use the remote configuration.
And I think it still should obey command-line arguments.
So topgrade would update the intersection between configuration and command-line.
Erroneous Behavior
If I disable "snap" from command-line or configuration file on Windows, topgrade still try to update snap inside WSL.
Expected Behavior
topgrade should not try to update "snap".
Steps to reproduce
On windows, with an Ubuntu WSL, just run "topgrade --disable snap"
Possible Cause (Optional)
topgrade win launches topgrade wsl without the same options.
Did you run topgrade through
Remote Execution
Configuration file (Optional)
Additional Details
Operation System/Version
Windows 10, WSL 2, Ubuntu 22.04
Topgrade version (
topgrade -V
)Topgrade 15.0.0
Verbose Output (
topgrade -v
)Snap errors are another problem that comes from proxy.
The text was updated successfully, but these errors were encountered: