-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
.NET Core Linux Feeds -- Now available #3995
Comments
My 10 cents: The Visual Studio Code team did overwrite the InRelease file (and more?) for every repository. |
I just got an update from the Linux repo admins: they've reverted the recent changes to the underlying service that caused this problem in the first place, and they're now working on fixing up the individual feeds so that they can be used again. |
Please speed up the fix, been waiting for it for about 16 hours now, I built a new pc and can't install vscode nor .net. |
The feeds are starting to work again. I'm getting successful |
Successful for Ubuntu-18.04 LTS. |
Debian 10 is now working for me (and others in #3988)! I'm trying out more feeds now to try to find any gaps. |
The problem has still been happening with the VS Code feed. They're working on fixing that one as well. It just now started working for me, but it may take up to 15 minutes from now for the fix to sync across the world. |
It looks like we're finally in the clear! I haven't seen any new reports after the repo admins confirmed the feeds were fixed, and it's been 15 minutes since VS Code feed was fixed, so we expect that fix to be available to everyone now. There are some reports of success on that thread as well (microsoft/vscode#86858). |
Please share any new reports of issues that you see. We want to ensure that we really are "in the clear". |
Works on Mint (based on Ubuntu Bionic) |
I'm in touch with the Microsoft repo admins and will work with them on a post-mortem of this issue. I'll work with the repo admins on both responsiveness and prevention. |
Closing this issue now. The incident appears to have passed. We're sorry this happened, and we are investigating the cause. We don't want this to happen again. |
The underlying problem is now fixed: dotnet/core#3995
Seen again today
|
Both the 18.04 and 19.04 repos are down. |
Can agree with both. repro is a dockerfile: FROM mcr.microsoft.com/dotnet/core/sdk:3.1
RUN wget -qO- https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor > microsoft.asc.gpg \
&& mv microsoft.asc.gpg /etc/apt/trusted.gpg.d/ \
&& wget -q https://packages.microsoft.com/config/debian/10/prod.list \
&& mv prod.list /etc/apt/sources.list.d/microsoft-prod.list \
&& chown root:root /etc/apt/trusted.gpg.d/microsoft.asc.gpg \
&& chown root:root /etc/apt/sources.list.d/microsoft-prod.list \
&& apt-get update \
&& apt-get install aspnetcore-runtime-2.2 |
https://packages.microsoft.com/debian/10/prod/dists/buster/main/binary-amd64/Packages.bz2 File has unexpected size Error is occurring again. |
Just encountered the same issue today 7/23/2020. Ticket opened to Microsoft support. |
Just got this error: Steps in my dockerfile: |
When you see this happening, please open a new issue (feel free to include a link back to this issue as a reference) or look for an issue currently tracking it--commenting on a closed issue isn't likely to ping the right person. The current problems are tracked by #6381. |
.NET Core Linux Feeds
The .NET Core teams provides a set of Linux feeds for a variety of distros. We support the following package managers: APT, Yum, DNF, and ZYpp. We rely on a Microsoft-only service provided by the Azure organization for the actual underlying feeds infrastructure.
We are seeing widespread reports of errors (with strange messages) when people are pulling .NET Core packages via APT. Both Ubuntu, Debian use APT. We also discovered the problem ourselves. We are not seeing any issues with the other package managers listed above.
We are working closely with the team that maintains the underlying infrastructure. They are working on it with the highest priority. We have a "severity 1" ticket with them.
We will use this issue for tracking and reporting until the issue is resolved, and updated when we have new information.
We are very sorry that this is happening. After resolution, we will look for new safeguards to prevent this situation in future.
Reports we are tracking:
The text was updated successfully, but these errors were encountered: