while trying to install the target SDK via smart it fails to install eglibc dev package since eglibc-extra-nss-dev is really missing root@localhost:~# smart install libgcc-s-dev Loading cache... Updating cache... ########################################################### [100%] Computing transaction... error: Can't install libgcc-s-dev-4.7.2-r19.2@ppc64e5500: all packages providing libc6-dev failed to install: error: Can't install libc6-dev-2.17-r3.2@ppc64e5500: no package provides eglibc-extra-nss-dev error: Can't install libc6-dev-2.17-r3.1@ppc64e5500: no package provides eglibc-extra-nss-dev error: Can't install libc6-dev-2.17-r3.0@ppc64e5500: no package provides eglibc-extra-nss-dev error: Can't install eglibc-dev-2.17-r3.2@lib32_ppce5500: no package provides eglibc-extra-nss-dev error: Can't install eglibc-dev-2.17-r3.1@lib32_ppce5500: no package provides eglibc-extra-nss-dev error: Can't install eglibc-dev-2.17-r3.0@lib32_ppce5500: no package provides eglibc-extra-nss-dev
I'm not convinced creating this package is the correct way to solve this issue...
if we could find out why libc6-dev is creating this artificial dependency on an empty package then yes that would be a better one and i have a hunch that we may be having this issue systemwide
Is the dependency a DEPENDS or a RECOMMENDS?
At least here, eglibc-extra-nss-dev is a RRECOMMENDS so the error shouldn't be fatal even if it is missing.
I think this is an issue with smart not handling recommends on target properly, hopefully Paul can comment.
I can't reproduce this (with qemuarm, which is what I had around to test). Any suggestions? I'll examine the code in the meantime.
Looking at the Smart transaction code I suspect this is not a recommends case, because the "no package provides" error can only occur if the package is in the requires and not the recommends list. It's possible there is something misbehaving before this code that means the recommends list doesn't have the package in it, but I think I need to be able to reproduce the error first before I can figure out where the problem really lies.
Khem, can you help me to reproduce this?
We can't reproduce this and everything we've tried to test checks out and works fine. Please reopen this if more details can be provided.