View Single Post
Nyrath's Avatar
Posts: 92 | Thanked: 50 times | Joined on Jan 2006 @ the praeternatural tower
#303
Originally Posted by Benson View Post
Okay, you did one dangerous (but perfectly OK, if you know what you're doing) thing, and one pointless (if less risky) thing. You are not to install the SDK repo on a device, because it contains some packages that conflict with packages that half your system depends on; that is, packages which you can install, but your system will never boot again. Red pill, though, was unnecessary; since libruby depended on libssl0, it should have been pulled in automatically (now that you added the SDK repo) when you tried libruby or rubybox again, so you don't need to be able to manually select it.

I'd recommend going back to blue-pill; anything you need red-pill for is, imho, better done with dpkg/apt-get on the command line, because they give more useful feedback about what they're doing, anyway. As for the SDK repo, generally it should be disabled when you're not trying to install particular software from it.
Now you've got me worried.
(for the record, I only stayed in red-pill mode long enough to install libssl0, I immediately returned to blue-pill)

Now, if I am understanding you, I should not have used the libssl0 from the Maemo diablo/sdk repository. The only other repository that had it was Maemo Chinook. Since my tablet is running Diablo, I uses the diablo/sdk repository, not knowing that sdk is a synonym for "danger".
(Yes, I know that SDK means "software development kit")

To be safe, what should I do? I'm figuring that I should uninstall libssl0, the ruby files, and RubyBox, remove the Maemo diablo/sdk from the App Manager's list, add Maemo Chinook to the App Manager's list, then just reinstall the ruby files and RubyBox. Is this correct?

Last edited by Nyrath; 2008-09-11 at 17:34.
 

The Following User Says Thank You to Nyrath For This Useful Post: