Well, Trunk:Testing is there just to detect such issues :) Regarding the dependencies, someone (Pkg XYZ) along the line has a requires on ofono and when building a package that BuildRequires that something (Pkg XYZ) it also pulls its' Requires, hence the requirement on ofono and the expansion error. When things really go crazy with such dependencies, we exclude those in the project config, ofono probably is a good example, since it does not have a devel package or libraries that someone might depend on?
Anas On 2010-10-13, at 11:26 AM, Shane Bryan wrote: > On Wed, 13 Oct 2010 12:52:10 +0300 > Marko Saukko <[email protected]> wrote: > >> Hi, >> >> why does ofono require ofono-configs? > > And why was an SR accepted when the newly added package requirement is > not available in any repo (home:jouni.peltonen does not count)? > > Now it seems ofono is blocked, and, for some strange reason, so are > about 36 other packages in Trunk:Testing, due to "nothing provides > ofono-config needed by ofono" unresolvable condition. > > (Side note: *WHY* on earth does SDL (or gvfs, or installer, or...) > depend on ofono? It's not listed as build requirements for these > packages... Something is not right if this is happening) > > So, regardless of the agreed to resoluion for the need of an > ofono-config package, this SR should have never been accepted until the > package it requires is also SR'd and accepted. > > According to the list archives, no such SR for ofono-config has ever > been seen. > > Shane... > _______________________________________________ > 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
