Summary: | openssh needs older version of libopensc | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Evan Langlois <evan> |
Component: | Current packages | Assignee: | Daniel Ahlberg (RETIRED) <aliz> |
Status: | RESOLVED INVALID | ||
Severity: | major | CC: | vapier |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Evan Langlois
2005-01-30 11:05:15 UTC
Did you try `revdep-rebuild -p`? re-emerge opensc I already tried re-emerging opensc, as you can see the error listed : warning: libscconf.so.0, needed by /usr/lib/libopensc.so, not found And scp says that file doesn't exist, and as you might expect, its not there. libopensc.so.1 is there, a newer one, and its going to install an older no matter how many times I re-emerge packages. I think libopensc needs to have a slot for the older lib and openssh needs to require the old one. How is this bug invalid? If I can't scp into a box because portage upgraded something (and revdep-rebuild is done regularly after every world update!), then its a BUG! I've given up on helping Gentoo find bugs. I used to run all ACCEPT_KEYWORDS for everything, knowing that I'd find issues like this that would need to be reported and fixed and many people simply don't report them, so I intentionally did so things would get reported and fixed before going into the more "stable" tree. But, I'm tired of arguing with developers on what is or isn't a bug. I'm setting the couple of items I need ~x86 into package.keywords and downgrading the whole box. So ... since this bug is already closed as "invalid", I'll fix it by downgrading everything ... you guys can fix this yourself when opensc gets bumped into the regular "stable" tree. well you neglected to mention any of that in your original bug report that said, emerging opensc-0.9.4 installs the correct files for me: >>> /usr/lib/libopensc.la >>> /usr/lib/libopensc.so -> libopensc.so.1.0.0 >>> /usr/lib/libopensc.so.1 -> libopensc.so.1.0.0 >>> /usr/lib/libopensc.so.1.0.0 >>> /usr/lib/libscconf.la >>> /usr/lib/libscconf.so >>> /usr/lib/libscconf.so.1 >>> /usr/lib/libscconf.so.1.0.0 if something needs .so.0 then it means it's still linked against the old version; re-emerge it the original bug report did mention that - I thought it was obvious from the description. As you can see from the emerge output, it wants .so.0. Please READ what I keep posting. Re-emerging the "something that needs .so.0" is what failed, its what I posted, and why I posted the bug! I think you guys just assume that the bug is invalid without actually reading whats posted. So ... maybe my suggestion that libopensc needs a slot to have both libs installed would be the fix. If I could just re-emerge it and have it work, I wouldn't have opened a bug in the first place! your original analysis was incorrect then, openssh works fine with openct-0.5.0 and opensc-0.9.4 (i just tested it on my box) SLOTing is not the solution since SLOTing is for completely different setups Well, I'm not a developer. You tell me why openssh won't emerge. because it had a bad day emerge sync and re-emerge opensc-0.9.4 and then re-emerge openssh and all should be well in the world (and your box) tried all that before posting the bug, and its too late to do it again. I've already started to downgrade world. no more ~x86, no more bug posts, no more fixing 20 problems trying to get something done while being told my computer software doesn't have bugs unless I put them there. |