-
Notifications
You must be signed in to change notification settings - Fork 6k
Add some info about error with deb packages #16857
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
Conversation
The "Unable to locate" section is a workaround for a bug in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is needed for RPM package repos as well, 2 hour max expected outage there.
docs/core/install/includes/package-manager-heading-hack-pkgname.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, one more tweak for the RPM repos, then LGTM.
|
||
### Failed to fetch | ||
|
||
While installing the .NET Core package, you may see an error similar to `Failed to fetch ... File has unexpected size ... Mirror sync in progress?`. Generally speaking, this error means that the package feed for .NET Core is being upgraded with newer package versions, and that you should try again later. During an upgrade, the package feed should not be unavailable for more than 2 hours. If you continually receive this error for more than 2 hours, please file an issue at <https://github.com/dotnet/core/issues>. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, maybe this should be in something we INCLUDE
? I'm not familiar with the docs infra, just remembered it from the diff context. 🙂 This bit may change (without going away completely) as we figure out what we can do about this. (Also makes it easier to review.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes I think so. I started without the include because I thought it was only the ubuntu items 😁 I'll convert it.
|
||
### Failed to fetch | ||
|
||
While installing the .NET Core package, you may see an error similar to `Failed to fetch ... File has unexpected size ... Mirror sync in progress?`. Generally speaking, this error means that the package feed for .NET Core is being upgraded with newer package versions, and that you should try again later. During an upgrade, the package feed should not be unavailable for more than 2 hours. If you continually receive this error for more than 2 hours, please file an issue at <https://github.com/dotnet/core/issues>. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The error's actually different for RPM repository clients, sorry I missed adding this to the actual doc issue: dotnet/core#4167.
I think this would work:
similar to
Signature verification failed for file 'repomd.xml' from repository 'packages-microsoft-com-prod'
.
@dagood OK I changed it up. I didn't mean to re-request since you're signed off. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@@ -0,0 +1,2 @@ | |||
|
|||
While installing the .NET Core package, you may see an error similar to `Failed to fetch ... File has unexpected size ... Mirror sync in progress?`. Generally speaking, this error means that the package feed for .NET Core is being upgraded with newer package versions, and that you should try again later. During an upgrade, the package feed should not be unavailable for more than 30 minutes. If you continually receive this error for more than 30 minutes, please file an issue at <https://github.com/dotnet/core/issues>. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We usually avoid use of "please".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tdykstra I know. Acro complains that it doesn't add anything. But in this case, I think it does. We're really requesting users to file an issue so that we can be alerted to the problem. Thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's your call -- if you think it's justified in this instance I'm fine with it. I agree it would sound a bit abrupt here without it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree it makes sense for this message. Style guide on please:
Avoid please except in situations where the customer is asked to do something inconvenient or the application or site is to blame for the situation.
Example
The network connection was lost. Please reenter your password.
The service is to blame, and it's inconvenient to have to file an issue to let us know.
@@ -0,0 +1,2 @@ | |||
|
|||
While installing the .NET Core package, you may see an error similar to `signature verification failed for file 'repomd.xml' from repository 'packages-microsoft-com-prod'`. Generally speaking, this error means that the package feed for .NET Core is being upgraded with newer package versions, and that you should try again later. During an upgrade, the package feed should not be unavailable for more than 2 hours. If you continually receive this error for more than 2 hours, please file an issue at <https://github.com/dotnet/core/issues>. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please
Summary
@dagood I'm unsure if the Unable to locate error section should be ported to the debian articles. the steps don't exactly align to ubuntu (the user isn't told to download a
packages-microsoft-prod.deb
file).Fixes #16670