-
Website
http://dancameron.org/ -
Original page
http://dancameron.org/pownce/error-failed-dependencies-the-crux-of-linux -
Subscribe
All Comments -
Community
-
Top Commenters
-
LillyLipscomb
1 comment · 1 points
-
paynito
1 comment · 1 points
-
stevehahn
8 comments · 1 points
-
futurelevel
2 comments · 1 points
-
Jason Hansen
4 comments · 2 points
-
-
Popular Threads
-
Splitting Content into Two Columns, e.g. Word Wrap with PHP or CSS + Javascript
2 weeks ago · 11 comments
-
Display a loading image until the page completes loading
4 days ago · 1 comment
-
Go Dodgers!
3 weeks ago · 1 comment
-
Splitting Content into Two Columns, e.g. Word Wrap with PHP or CSS + Javascript
Of course, I'm running Debian which is well known for having a quality repository system, but even with the rare source-only stuff, I almost never run into dependency issues these days.
Especially for most users who are likely to only be installing stuff from the repos, this will luckily not be a major issue.
The problem is upgrading glibc, it's highly recommended *not* to upgrade individually. Far to many packages rely on the glibc-2.3 and upgrading to 2.4 or 2.5 would break some packages or most likely break the system.
I'm going to figure out my options to just update to CentOS 5 which has glibc 2.5.
And all of this mess because one program I want to install has a chain of dependencies stopping at glibc.
So, it's not bad luck it's just the cost of freedom; work to make it work.
Sounds like a good candidate for virtualization.
Virtualization? Where? Within the VPS? No way.
(mt) is actually being really cool right now, they're going to let me get another (dv), I'll upgrade it to CentOS5 after moving everything to the new (dv) cancel my current one with a money back guarantee.
Yeah, virtualization within your existing VM wouldn't be a good idea, although depending on what it's used for, you could always run it on a different server (other than your VPS) and still have access to it through your server. That's actually how I have my Trac+SVN server set up - it's in a Xen VM running on a box in my garage, but it's accessed through my public server.
PS - I must say I find it humorous that you seem to be taking subtle shots at Linux and free software in general, when the app that's actually the root of the problem is non-free. :)
I probably could set it up at home but that's what I have my server for at (mt).
It was meant to be slightly humorous but the root of the problem is the framework not working for the application to be installed; even though the reason I need the framework *now* is because of the app.
I was just giving you a hard time since it turned out to be a non-free app that was bringing the issue to the forefront.
I would just hesitate attributing this problem to Linux in any way, since you can run into dependency conflict problems on any platform, depending on the applications involved.