Microsoft's dpkg packages themselves do some fairly weird/annoying stuff in their maintainer scripts.<p>e.g., azuredatastudio contains code that manages a /usr/local/bin/code symlink...<p>... 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)...<p>... 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!<p>... 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...<p>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...
The packages.microsoft.com repositories are regularly broken, which results in perennial build failures if you use GitHub Actions which includes it by default.<p>GitHub's response to "your default configuration is broken" was basically "welp, NOMFP":<p><a href="https://github.com/actions/virtual-environments/issues/3410" rel="nofollow">https://github.com/actions/virtual-environments/issues/3410</a>
Not only Ubuntu. And not for the first time [0], [1], [3] (Stack Overflow). Would be surprised, however, if the servers are in space instead of under water [2].<p>[0] <a href="https://social.msdn.microsoft.com/Forums/en-US/5d090bb8-6c22-4e8d-a534-3e79b3cb3113/failed-to-fetch" rel="nofollow">https://social.msdn.microsoft.com/Forums/en-US/5d090bb8-6c22...</a><p>[1] <a href="https://github.com/MicrosoftDocs/windowsserverdocs/issues/5051" rel="nofollow">https://github.com/MicrosoftDocs/windowsserverdocs/issues/50...</a><p>[2] <a href="https://news.microsoft.com/innovation-stories/project-natick-underwater-datacenter/" rel="nofollow">https://news.microsoft.com/innovation-stories/project-natick...</a><p>[3] <a href="https://stackoverflow.com/questions/59624773/failed-to-fetch-https-packages-microsoft-com-repos-azure-cli-dists-bionic-main" rel="nofollow">https://stackoverflow.com/questions/59624773/failed-to-fetch...</a>
Just to clarify the title, Space in this context is the 'Biggest Key on your Keyboard' kind not the 'On Disk' kind.<p>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.<p>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. -- <a href="https://github.com/dotnet/core/issues/6381#issuecomment-863157425" rel="nofollow">https://github.com/dotnet/core/issues/6381#issuecomment-8631...</a>
None commented yet on the suggested issue? They ran out of space? Really? Azure Monitoring, Azure Sentinel - surely they have the simplest metric: used vs remaining space.<p>Or did they hit a limit in the blob/file storage. Still: no monitoring?<p>You may have noticed I have so many questions on Microsoft Ops.
> because of space issues<p>yeah, spaces in filenames. A well-known yet insidious problem.<p>Is there any mount option to change raw spaces in the exposed filesystem with an unicode non-breaking space, or something?
Wanted to update my Teams on Ubuntu 20 in the morning (after coming to office after months working from home) and had the same issue. Removed the package and installed it from snap. Works like charm so far.
What SLA are Ubuntu mirrors held to? This doesn't seem great, but won't a quick run of mirrorselect remove the offending repos and let you get on with life?