e.g., azuredatastudio contains code that manages a /usr/local/bin/code symlink...
... and it contains code that converts a PGP key in armored form to binary form and dumps it in /etc/apt/trusted.gpg.d, even if the sysadmin already took the time to verify the PGP key and put it into their own .asc file in the same directory (ok, I guess at least they aren't force-appending their key to the old/deprecated/monolithic /etc/apt/trusted.gpg file like many others)...
... oh and in doing so they dump out microsoft.gpg to the current directory, whatever that may be... they should at least be using mktemp!
... and they are doing other things that they should be relying on debhelper to do for them, e.g. installing shared-mime-info-spec files manually rather than with dh_installmime; installing desktop-entry-spec files manually rather than relying on the triggers that already handle installation of such files...
As for teams, it has its own oddball way of monkeying with /etc/apt, and one other weirdness: it explicitly changes /usr/share/teams/chrome-sandbox to be setuid. If that file is supposed to be setuid then ship it as such... shipping it non-setuid and then modifing it in a maintainer script sets off alarm bells and breaks dpkg-statoverride...
This is why I decided to bite the bullet and go flatpak for the likes of teams, slack and other proprietary software.
I always recommend this now if it is an option. Even if Microsoft does nothing wrong, it is way too easy for me to make an error and somehow enable Microsoft antivirus stuff on my Fedora machine which I still don't know how I managed to do.
These kinds of hacks are pretty consistant with my few experiences with Microsoft (and other vendor's) closed software on Linux. It's all best avoided for community maintained solutions.
GitHub's response to "your default configuration is broken" was basically "welp, NOMFP":
Hadn't seen it before and big G suggests NMFP is way more common, with no hit that I saw explaining the 'O'.
(It's a quote from the UK political satire series "The Thick Of It", in which the character Malcolm Tucker remarks, "NOMFP. N-O-M-F-P. Not My Fucking Problem. I quite like that. Did you like that? I'll use that quite a lot today.")
That said, I’d also like to know.
for broken_apt_repository in `grep -lr microsoft /etc/apt/sources.list.d/`; do sudo rm $broken_apt_repository; done
It looks like a parsing issue where something in MS's automated process is replacing various parts of filenames with spaces. Looks like / and _ at a glance, but there could be more.
Just trying to prevent this type of comment, which I can only assume came from HN as nowhere in the Github issue does anyone mention disk space. -- https://github.com/dotnet/core/issues/6381#issuecomment-8631...
What is mentioned is ambiguous. So while disk space isn't specifically mentioned, neither is spaces in the context of filenames.
Here's what people are reading in that issue:
"Update: our infra team is still working to resolve this issue. They ran into some space issues but this issue should be resolved quickly. Unfortunately, I do not have an ETA yet."
There isn't enough context to know what it means.
I thought there was some diskspace issue
Or did they hit a limit in the blob/file storage. Still: no monitoring?
You may have noticed I have so many questions on Microsoft Ops.
yeah, spaces in filenames. A well-known yet insidious problem.
Is there any mount option to change raw spaces in the exposed filesystem with an unicode non-breaking space, or something?
It'll be fixed as soon as they finish their Backslash Conversion Project!
What's much more annoying is that this breaks CI/Docker builds. Right now you can't deploy new container images that depend on a MS repository. I hope it's resolved soon.
Many different caches can be used, in case one is down as well.
Simple example download script at .
You plan for failure. What happens if your cache fails? You fall back to Microsoft. But what happens if Microsoft fails and you don't have a cache? Well you build a cache in advance and default to that.
Caches can also improve build time, allow for security tools to scan, and other such benefits too. So there are other benefits outside of creating a redundancy.
also there are cache misses :-(