Skip to content

Userlocal workload installation/updates are broken in 8.0.300 #41420

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

Closed
Tracked by #35455
baronfel opened this issue Jun 5, 2024 · 2 comments · Fixed by #41735
Closed
Tracked by #35455

Userlocal workload installation/updates are broken in 8.0.300 #41420

baronfel opened this issue Jun 5, 2024 · 2 comments · Fixed by #41735
Assignees
Labels
Area-Workloads needs team triage Requires a full team discussion

Comments

@baronfel
Copy link
Member

baronfel commented Jun 5, 2024

          @Mr-MooMoo, I reproduced the issue. It is different from the one @anpin ran into with the 8.0.2xx SDK.

@marcpopMSFT @dsplaisted @baronfel it seems that userlocal is broken in the 8.0.3xx band.

The issue can be reproduced with these commands (on any linux-x64 distro).

mkdir /tmp/repro
cd /tmp/repro
mkdir dotnet
cd dotnet
wget https://download.visualstudio.microsoft.com/download/pr/86497c4f-3dc8-4ee7-9f6a-9e0464059427/293d074c28bbfd9410f4db8e021fa290/dotnet-sdk-8.0.301-linux-x64.tar.gz
tar xvf *.tar.gz
mkdir -p metadata/workloads/8.0.300
touch metadata/workloads/8.0.300/userlocal
chmod -R -w .
export DOTNET_ROOT=$(pwd)
export PATH=$(pwd):$PATH
cd ..
mkdir home
cd home
export HOME=$(pwd)
dotnet workload update

Originally posted by @tmds in #37706 (comment)

We should ensure that userlocal configurations work with workloads sets - all state and workload set packs should go to the userlocal location instead of the SDK location.

NOTE:
When I did the repro steps I had to make sure to change to a user without root permissions so that I couldn't accidentally modify the SDK install

@ghost ghost added Area-Workloads untriaged Request triage from a team member labels Jun 5, 2024
@baronfel baronfel removed the untriaged Request triage from a team member label Jun 5, 2024
@dsplaisted dsplaisted added the needs team triage Requires a full team discussion label Jun 6, 2024
@baronfel
Copy link
Member Author

@tmds I'm assuming that this is broken in 9.0.100 previews as well, right? Since the work from 8.0.300 has flowed into main at this point?

@tmds
Copy link
Member

tmds commented Jun 21, 2024

@tmds I'm assuming that this is broken in 9.0.100 previews as well, right?

Yes, reported for .NET 9 in #41726.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Workloads needs team triage Requires a full team discussion
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants