You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 15, 2022. It is now read-only.
Repository navigation
This repository was archived by the owner on Dec 15, 2022. It is now read-only.
Unable to push on Linux with newer versions of libcurl #848
@smashwilson not initially. I was chatting with @dscho about this last night, he's given me some thoughts but it seems like A Really Hard Task to put a purely portable Git together for Linux due to the explicit and implicit dependencies.
I've opened desktop/dugite-native#42 to track investigating the libcurl issue. I'm kinda swamped for the next week with conference stuff, but I'll dump some more thoughts in there when I can.
I've installed some of the libraries but still getting this error
/snap/atom/200/usr/share/atom/resources/app.asar.unpacked/node_modules/dugite/git/libexec/git-core/git-remote-https: /snap/core/current/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /usr/lib/x86_64-linux-gnu/libgnutls.so.30)
/snap/atom/200/usr/share/atom/resources/app.asar.unpacked/node_modules/dugite/git/libexec/git-core/git-remote-https: /snap/core/current/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.26' not found (required by /usr/lib/x86_64-linux-gnu/libp11-kit.so.0)
I think dependencies are hard coded and requires the older version to be able to run.
A less hacky way might be to use ELF statifier, as I mentioned elsewhere, but this comes with the big caveat that I have not tried it, and therefore I cannot vouch that it works.
The only thing you can do right now is apm install atom/github, but beware, this will install the in-development GitHub package from the master branch of its repo so there might be bugs. You'll also need to remember to delete it after we ship a hotfix with this fix included.
The workaround no longer works in Ubuntu 18.10 as perhaps to avoid a conflict with libcurl3 libcurl3 has been replaced with libcurl3-gnutls and libcurl-openssl1.0-dev (which depends on libcurl3) has been replaced with libcurl4-openssl-dev (depends libcurl4); /usr/lib/x86_64-linux-gnu/libcurl.so.4 is now owned by package libcurl4.
Error: /usr/share/atom/resources/app.asar.unpacked/node_modules/dugite/git/libexec/git-core/git-remote-https: /usr/lib/x86_64-linux-gnu/libcurl.so.4: version `CURL_OPENSSL_3' not found (required by /usr/share/atom/resources/app.asar.unpacked/node_modules/dugite/git/libexec/git-core/git-remote-https)
@Spitfire1900 till fix is upload to atom i ll recommend to use it as before and when going to push to cloud use console to do it git push this would get all the staged changes and comments that had been done on atom.
I have been trying different things to solve the issue but they end up being more of a head ache that to write a simple line on console. Work around sometimes break when installing new things or updates, etc.
The real fix to this issue is the update to dugite in the GitHub package which we'll include in the 1.32.1 and 1.33.0-beta1 hotfix updates released sometime this week. Thanks for your patience while we get the hotfixes out!
I have confirmed that install of debian package output of atom/atom's commit 24d1bcc31's (current 1.32-releases tip) script/build --create-debian-package can do https publish and fetch.
The real fix to this issue is the update to dugite in the GitHub package which we'll include in the 1.32.1 and 1.33.0-beta1 hotfix updates released sometime this week
1.32.1 and 1.33.0-beta1 have been released ⚡ Going to go ahead and close this but if you're still having issues, please let us know.
/snap/atom/206/usr/share/atom/resources/app.asar.unpacked/node_modules/dugite/git/libexec/git-core/git-remote-https: /snap/core/current/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /usr/lib/x86_64-linux-gnu/libgnutls.so.30)
/snap/atom/206/usr/share/atom/resources/app.asar.unpacked/node_modules/dugite/git/libexec/git-core/git-remote-https: /snap/core/current/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.26' not found (required by /usr/lib/x86_64-linux-gnu/libp11-kit.so.0)
@Amantel - the Snap installation is unofficial but If you can reproduce the error with a supported installation method, please open a new issue with the template filled out and we'll take a look.
I'm on Kubuntu 18.04 and can't update from Atom 1.33 because of the libcurl3 vs libcurl4 dependencies. Not sure this issue was fixed by: atom/atom#18201
@Spitfire1900 Yup I can push just fine... My bad. I meant to post this on the issue of not being able to update to newer versions of Atom since it has libcurl3 as a requirement and will therefor remove libcurl4 and any program using it.
That seems about right, but I can't update to any versions after 1.33. It asks to remove libcurl4 and install libcurl3. Created a ticket in the Atom repo atom/atom#18758
Activity
smashwilson commentedon May 18, 2017
Looks like we're still dynamically loading libcurl from git binaries within dugite. @shiftkey, any thoughts on this?
shiftkey commentedon May 18, 2017
@smashwilson not initially. I was chatting with @dscho about this last night, he's given me some thoughts but it seems like A Really Hard Task to put a purely portable Git together for Linux due to the explicit and implicit dependencies.
I've opened desktop/dugite-native#42 to track investigating the libcurl issue. I'm kinda swamped for the next week with conference stuff, but I'll dump some more thoughts in there when I can.
NormanEdance commentedon Oct 2, 2018
Any progress/quickfix, guys?
davidkwast commentedon Oct 4, 2018
me too, started today on Ubuntu 18.04 with Atom 1.31.1
git-elliot commentedon Oct 5, 2018
I've installed some of the libraries but still getting this error
I think dependencies are hard coded and requires the older version to be able to run.
dscho commentedon Oct 5, 2018
@parasthekoder indeed, the GLIBC versioning hits you.
One way to work around this is to add (ugly) defines for the versioned symbols. I did this in a different project, a long time ago: https://github.com/imagej/imagej-launcher/blob/master/src/main/include/glibc-compat.h (and I wrote a script to update that header based on a built executable: https://github.com/imagej/imagej-launcher/blob/master/force-glibc-compat.sh
A less hacky way might be to use ELF statifier, as I mentioned elsewhere, but this comes with the big caveat that I have not tried it, and therefore I cannot vouch that it works.
The ball is in your park now, @parasthekoder
amirhfarzaneh commentedon Oct 5, 2018
So I think all of ubuntu 18.04 user with the latest update cannot use Atom for GitHub right now.
daviwil commentedon Oct 5, 2018
Lemme see if I can squeeze this into the next Atom hotfix. It'll be dependent on whether this doesn't break things on earlier Ubuntu releases.
schampseix commentedon Oct 11, 2018
should be work with installing : sudo apt install libcurl3/bionic , its working on my side under ubuntu 18.04
risangbaskoro commentedon Oct 11, 2018
I got an output that says
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?What does this mean?
schampseix commentedon Oct 11, 2018
looks like an apt process (update, upgrade or installation) is already in progress
gabrielctn commentedon Oct 11, 2018
Thanks ! It worked perfectly for me.
oliverlj commentedon Oct 12, 2018
Yes , that work but you have to remove curl.
risangbaskoro commentedon Oct 12, 2018
How to remove curl?
oliverlj commentedon Oct 12, 2018
It is automatically. Curl need libcurl4 :(
20 remaining items
daviwil commentedon Oct 26, 2018
The only thing you can do right now is
apm install atom/github, but beware, this will install the in-development GitHub package from themasterbranch of its repo so there might be bugs. You'll also need to remember to delete it after we ship a hotfix with this fix included.Spitfire1900 commentedon Oct 28, 2018
The workaround no longer works in Ubuntu 18.10 as perhaps to avoid a conflict with libcurl3 libcurl3 has been replaced with libcurl3-gnutls and libcurl-openssl1.0-dev (which depends on libcurl3) has been replaced with libcurl4-openssl-dev (depends libcurl4); /usr/lib/x86_64-linux-gnu/libcurl.so.4 is now owned by package libcurl4.
Error:
/usr/share/atom/resources/app.asar.unpacked/node_modules/dugite/git/libexec/git-core/git-remote-https: /usr/lib/x86_64-linux-gnu/libcurl.so.4: version `CURL_OPENSSL_3' not found (required by /usr/share/atom/resources/app.asar.unpacked/node_modules/dugite/git/libexec/git-core/git-remote-https)atom --version:
apm --version
apm list | grep github
├── github@0.20.1lsb_release -a:
dpkg -l | grep libcurl:
apt-file find /usr/lib/x86_64-linux-gnu/libcurl.so.4
Package needs to search for libcurl-gnutls.so.4 or upgrade to libcurl4
apt-file list libcurl3-gnutls
apt-cache show libcurl4-openssl-dev | grep Depends
ezewer commentedon Oct 28, 2018
@Spitfire1900 till fix is upload to atom i ll recommend to use it as before and when going to push to cloud use console to do it
git pushthis would get all the staged changes and comments that had been done on atom.I have been trying different things to solve the issue but they end up being more of a head ache that to write a simple line on console. Work around sometimes break when installing new things or updates, etc.
Spitfire1900 commentedon Oct 29, 2018
Looks like this is associated with desktop/dugite-native#109
Which if so this may be resolved with atom/atom#18201
Which appears will be pushed out with v1.34
daviwil commentedon Oct 29, 2018
The real fix to this issue is the update to
dugitein the GitHub package which we'll include in the 1.32.1 and 1.33.0-beta1 hotfix updates released sometime this week. Thanks for your patience while we get the hotfixes out!Spitfire1900 commentedon Oct 30, 2018
I have confirmed that install of debian package output of atom/atom's commit 24d1bcc31's (current 1.32-releases tip)
script/build --create-debian-packagecan do https publish and fetch.🌮
rsese commentedon Nov 2, 2018
1.32.1 and 1.33.0-beta1 have been released ⚡ Going to go ahead and close this but if you're still having issues, please let us know.
Amantel commentedon Nov 24, 2018
Atom 1.32.2
Ubuntu 18.04
rsese commentedon Nov 27, 2018
@Amantel - the Snap installation is unofficial but If you can reproduce the error with a supported installation method, please open a new issue with the template filled out and we'll take a look.
ecotechie commentedon Jan 28, 2019
I'm on Kubuntu 18.04 and can't update from Atom 1.33 because of the libcurl3 vs libcurl4 dependencies. Not sure this issue was fixed by: atom/atom#18201
Spitfire1900 commentedon Jan 28, 2019
@ecotechie as a Kubuntu 18.10 user I can confirm that atom/atom#18201 resolved my issues per above comments from myself.
ecotechie commentedon Jan 28, 2019
@Spitfire1900 Yup I can push just fine... My bad. I meant to post this on the issue of not being able to update to newer versions of Atom since it has libcurl3 as a requirement and will therefor remove libcurl4 and any program using it.
Spitfire1900 commentedon Jan 28, 2019
Per diff atom/atom@812dcc4, libcurl3 or libcurl4 will both satisfy the libcurl dependency of Atom 1.33's *.deb package.
ecotechie commentedon Jan 28, 2019
That seems about right, but I can't update to any versions after 1.33. It asks to remove libcurl4 and install libcurl3. Created a ticket in the Atom repo atom/atom#18758