-
Notifications
You must be signed in to change notification settings - Fork 6k
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
Needs an additional step before installing .NET Core SDK #17537
Comments
Moved to original comment |
@dagood do you prefer a ping or an assignment when I need you to be pulled in? 😄 |
At a base level, this would be a bug with @tuttipazzo, what version of SLES are you using? Can you please show us I'm wondering if you're using a newer version of SLES that we haven't tried this on yet. I would be surprised if this has been a problem so long in SLES 15 and we hadn't seen it until now (although that might be possible I guess). Either way, I don't think adding another step to the instructions is the right move here. The package should be fixed. We could potentially add a step to the doc as a workaround if it ends up necessary though. Thanks for the report! /cc @NikolaMilosavljevic @dleeapho @nakarnam @leecow I've edited the original post to add code formatting and make it a little easier to parse, hope that's alright @tuttipazzo.
They're the same to me. I'm fine with assignment if it helps keep track of things on your end. But... @NikolaMilosavljevic actually owns this area now. He might have a different preference. |
I have no problem with formatting to make it more readable. So let's get SLES-specific here. SLES12 is fine:
But SLES15 of that pkg is not:
Fixing the pkg is fine. NOTE: As far as I know SLE15's zypper has not changed WRT to repos outside of /etc/zypp/repos.d ... |
Interesting, thanks for the extra info and digging into it. Definitely looks like a straightforward bug in the package. The packages.microsoft.com team maintains these configuration packages so we'll get them to fix it. (Unfortunately they have no public presence to file at directly.) |
OK, for completeness sake, I spun up a sles15.sp1 VM:
|
@NikolaMilosavljevic Should this issue be moved out of docs and into the product repo? Or is there something to doc here? |
The product team that owns this feed setup package unfortunately has no public presence. This issue tracks filing an internal issue to get them to fix it. I think it'd be good to keep this feedback issue active so that others hitting this problem can find it from https://docs.microsoft.com/en-us/dotnet/core/install/linux-package-manager-sles15 and see the workaround. If you want to transfer it for some procedural reason (triage, etc.), https://github.com/dotnet/core is the only place I think makes sense other than here. |
The linux package repo team is now tracking this as a bug but haven't provided an ETA. They've made it clear they don't consider it high priority because this bug has been around a while and we have a workaround. (More info is on our ticket (internal Msft link, sorry): https://icm.ad.msft.net/imp/v3/incidents/details/182039364/home.) It turns that, after all, we should incorporate this workaround into our doc, since the bug will probably be around for a while. I think the workaround would be this to make it work from any directory:
@tuttipazzo does that look right, if you don't mind taking a look? @Thraka can you help get this into the doc? |
@dagood Do you have a quick summery I can base the update on? Just a problem statement would be fine. |
Do you mean something like this? The SLES 15 Microsoft repository setup package installs the |
@dagood does this only apply to SLES 15? |
Yep. SLES 12 and others don't have this bug. |
zypper looks for repos in /etc/zypp.repos.d so:
But if we tell zypper where to find the microsoft-prod.repo file:
Now we can refresh it:
And operations on pkgs in that repo can be used:
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: