Hi. libbz2.so.1 is coming from the package bzip2-libs, which is created as a subpackage by bzip2. Bzip2 is a part of the MeeGo core repository.
Carrick is being built against MeeGo:1.0:Netbook (https://build.meego.com/project/show?project=MeeGo%3A1.0%3ANetbook), and MeeGo:1.0:Netbook is built against MeeGo:1.0 (https://build.meego.com/project/show?project=MeeGo%3A1.0) That MeeGo:1.0 repository doesn't have any packages. I'm not sure whether it should have, but there is no bzip2 in the repository you're building against. Someone who's familiar with the Netbook repository setup, shouldn't the netbook repo be compiled against MeeGo core? BR, Topi On 11/03/2010 12:43 PM, Jussi Kukkonen wrote: > Hi, > > I was fixing a packaging bug in carrick in MeeGo 1.0 and build.meego.com > gave me "status unresolvable" with this message: > "nothing provides libbz2.so.1 needed by rpm-libs, nothing provides > libbz2.so.1 needed by elfutils-libs, nothing provides libbz2.so.1 > needed by python" > I did generate the .spec with a newer specify, but I don't see how the > changes would lead to this. Link: > https://build.meego.com/package/show?package=carrick&project=home%3Ajku%3Abranches%3AMeeGo%3A1.0%3ANetbook%3AUpdate%3ATesting > <https://build.meego.com/package/show?package=carrick&project=home%3Ajku%3Abranches%3AMeeGo%3A1.0%3ANetbook%3AUpdate%3ATesting> > > I see banshee is in a similar state in MeeGo:1.0:Netbook:Update:Testing. > > Is there something I need to do or is the build system somehow broken? > > - Jussi > _______________________________________________ > MeeGo-packaging mailing list > [email protected] > http://lists.meego.com/listinfo/meego-packaging > _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
