DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
New to debian, just installed 2 days ago. Im liking it and im planning on keeping it, but I am running into a issue that may cause me to go back to Ubuntu.
A software that I MUST have installed and working (for work) needs libc.so.6 to be 2.15+ but as far as I can see debian has 2.13 shipped in test and unstable, while 2.17 is in experimental.
/opt/gloCOM/bin/gloCOM: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.15' not found (required by /opt/gloCOM/bin/gloCOM)
/opt/gloCOM/bin/gloCOM: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.17' not found (required by /opt/gloCOM/bin/gloCOM)
/opt/gloCOM/bin/gloCOM: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.15' not found (required by /opt/gloCOM/lib/libgloox.so.8)
/opt/gloCOM/bin/gloCOM: /lib/i386-linux-gnu/i686/cmov/libm.so.6: version `GLIBC_2.15' not found (required by /opt/gloCOM/lib/libavcodec.so.55)
The question is, how can I safely update to 2.17 (or 2.15), what is the procedure?
If I do update to 2.17 (or 2.15) what can it break or can it cause other issues.
rebourn@laftof:/opt/gloCOM/bin$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 7.4 (wheezy)
Release: 7.4
Codename: wheezy
Stable will never have anything newer than the one it has (2.13). You should either use testing/unstable or preload a newer libc (this worked using Ubuntu's libc when Steam requited 2.15 and Debian had 2.13).
I updated libc from sid repo to 2.18. The software works beautifully, just wondering is there something I could break besides the mentioned software by running libc on 2.18 now.
I updated libc from sid repo to 2.18. The software works beautifully, just wondering is there something I could break besides the mentioned software by running libc on 2.18 now.
You might break other stuff. But that you will find out yourself if it (hopefully not) happens...
I never had any issues after i upgraded to 2.17 from 2.13.
But beware: you ONLY should use testing/sid/experimental OR stable/stable-backports. DO NOT mix stable with anything else tha maybe the official backports.
You might break other stuff. But that you will find out yourself if it (hopefully not) happens...
I never had any issues after i upgraded to 2.17 from 2.13.
But beware: you ONLY should use testing/sid/experimental OR stable/stable-backports. DO NOT mix stable with anything else tha maybe the official backports.
So apperantly im screwed now, considering I pulled just libc from sid and after removed it from the repo list?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.