vscode: Can't upgrade on Ubuntu 18.04
Does this issue occur when all extensions are disabled?: Yes
- VS Code Version: 1.78
- OS Version: Ubuntu 18.04
Steps to Reproduce:
- sudo apt upgrade code
ubuntu@oracle-vm:~$ sudo apt upgrade code
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
code : Depends: libc6 (>= 2.28) but 2.27-3ubuntu1.6 is to be installed
E: Broken packages
The version available in the apt repo will have to be built on a system using an older version of glibc. Bear in mind that 18.04 doesn’t hit EoL until 2028, with security patches available on the free tier for ESM from Canonical.
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 2
- Comments: 24 (8 by maintainers)
Commits related to this issue
- VS Code: mark as hidden on jetson-18.04, broken upstream https://github.com/microsoft/vscode/issues/181720 — committed to Botspot/pi-apps by theofficialgman a year ago
- VS Code: mark as hidden, broken upstream https://github.com/microsoft/vscode/issues/181720 — committed to cobalt2727/L4T-Megascript by theofficialgman a year ago
- Update category-overrides-jetson-18.04 disable VSCodium until https://github.com/microsoft/vscode/issues/181720 is resolved — committed to Botspot/pi-apps by theofficialgman a year ago
Deepak is working on that
@cobalt2727 @deepak1556 can confirm that
code-insidersworks I would be very good if the tunnel repo also used this ubuntu bionic base image though since technically the deb dep-lists are wrong until code-tunnel-insiders is also corrected.The fix in this PR only affects the GUI
code-insidersbinary, the tunnel binarycode-tunnel-insidersis built on a different base image and remains unaffected. /cc @connor4312 in case you want to track https://github.com/microsoft/vscode/issues/181720#issuecomment-1596456924 in a new issue.This bug has been fixed in the latest release of VS Code Insiders!
@cobalt2727, you can help us out by commenting
/verifiedif things are now working as expected.If things still don’t seem right, please ensure you’re on version 0e9c2fa760932b13f81516aff15f2b0112aa6eeb of Insiders (today’s or later - you can use
Help: Aboutin the command palette to check), and leave a comment letting us know what isn’t working as expected.Happy Coding!
Sorry for the silence, I was on vacation. I will address the tunnel binary dependency this week.
@joaomoreno @deepak1556 refer to PR https://github.com/microsoft/vscode-linux-build-agent/pull/29 I am unable to test as I don’t have your tooling but I have no reason to believe it won’t work
Why so when you didn’t for x86_64 builds? Using debian as build agents was a bad idea in the first place though since support has long ended for them. You should be using Ubuntu LTS agents. Even Ubuntu 16.04 is still getting security updates.
What tool chain do you require that is different on armhf/arm64? Cpp-17 support is a pretty low bar and repo gcc/g++ toochains on the older Ubuntu LTSs have it.
All of this questioning could be avoided if you distro repo was open source.
@deepak1556 please revert to distro
9b27f67c15920833310305fce2d42cf2426f34eeas was last used in release 1.77.3Unfortunately your repository https://github.com/microsoft/vscode-distro is closed source and we have no ability to determine what has been done to break compatibility (ie: raise GLIBC requirements)
as you are likely aware, this has broken the requirements you have set https://code.visualstudio.com/docs/supporting/requirements
Same issue on Jetson Nano running Ubuntu 18.04.