Could not install maui workload because of Inconsistency in mono.toolchain workload manifest #18972
Labels
Comments
|
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
yamachu
changed the title
|
Was the workload already installed? I see the first dependencies are |
|
Thanks @srpeirce However, as described in the reproduction procedure, when I then tried to install or update via And dotnet workload list showed empty list. I tried uninstall them via dotnet worklaod command, but ... not found maui ... And tried repair and install too, it failed After that, I couldn't build iOS or mac applications, so I had to re-install it with maui-check again. |
|
The workloads are not guaranteed to upgrade cleanly between previews and if even less so with maui-check involved. Your workload install appears to be in an inconsistent state. |
|
I see. But |
|
@dsplaisted unless the resolver looks for an advertising manifest in the feeds is there anyway to resolve this chicken and egg problem. |
|
I'm not sure exactly what's going on here, it looks like it's getting a mix of preview 6 and preview 7 manifests. Ideally if it gets one preview 7 manifest it should get all of them. Did the Preview 7 version of the microsoft.net.workload.mono.toolchain manifest get pushed to a feed which otherwise only has the preview 6 manifests? |
|
@dsplaisted the issue is that we had to split the workload into two workloads for VS and now microsoft.net.workload.mono.toolchain depends on microsoft.net.workload.emscripten but Preview6 has no baseline manifest for that so it errors out even though the dependency is listed and there is a manifest in the feed. I'm mostly curious if this sort of scenario is something that might eventually be supported. |
|
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
|
No, I don't think we'd support this kind of change within the same feature band (ie in a patch to the SDK release). Changes to the structure of the workloads and manifests would need to wait for a new feature release of the .NET SDK. It's also OK to make these changes during previews, though as we've found it can be kind of painful. |
|
Understood, closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
When trying to install maui workload, it would fail because of message
Workload installation failed: Inconsistency in workload manifest 'microsoft.net.workload.mono.toolchain': missing dependency 'Microsoft.NET.Workload.Emscripten'.Repro steps:
(and try too sudo dotnet workload update ...)
console shows that
Configuration
Other information
There is a difference between the code in the repository and the installed definitions.
So it may be resolved if the repository manifest is provided.
https://github.com/dotnet/runtime/blob/7aaffcb2b3d42c79a23a86aecd6d0e2df049ee44/src/mono/nuget/Microsoft.NET.Workload.Mono.Toolchain.Manifest/WorkloadManifest.json.in
The text was updated successfully, but these errors were encountered: