Re: Question about Multistrap
+++ Vivek Raghunathan [2010-08-05 22:39 -0700]:
[can you not top-post please - it's confusing]
> In my local repository, instead of pulling in the dependencies for the
> latest package, multistrap kind of goes through all the versions of
> available package and throws out an error saying the dependencies were
> not met.
>
> This is what I'm getting. I have a single meta package which pulls in
> all the dependencies it needs and for example libdbixx0-dev is not in
> the dependency tree for my meta package
>
> log:
>
> The following packages have unmet dependencies:
> libdbixx0-dev: Depends: libdbixx0 (=
> 0.0.3kal1-1.20100418.030553.0bef81f) but
> 0.0.3kal1-1.20100628.124113.d9904bd is to be installed
> libksettings1-dev: Depends: libksettings1 (=
> 0.0.0-1.20100418.030847.b729848) but 0.0.0-1.20100430.031002.4173846
> is to be installed
> xlibs: Conflicts: xorg-conf
> xorg-startup: Conflicts: wmakerstartup-conf
> E: Broken packages
> apt download failed. Exit value: 100
OK, that's apt complaining, not multistrap, strictly speaking. Those
version numbers are pretty funky - do you really upload packages so
often that you need date.time.magic?
libdbixx0 is your invented local package, right?, as only libdbi0-dev
seems to exist in the normal ubuntu archive. (I'm testing on maverick).
I think you problem seems to be that you have stricit dependencies of -dev
packages on their corresponding library packages, but you don't have
said versions of the library packages available in the repo.
You need to actually have the packages that other packages depend on -
mothing multistrap can do about that.
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
Reply to: