On Sun, Jan 03, 2016 at 03:38:54PM +0100, Johannes Schauer wrote: > Quoting Niko Tyni (2016-01-03 15:24:38) > > It looks like sbuild doesn't currently take build profiles into account when > > resolving cross build dependencies. This seems to me like a fundamental > > building block for at least the "cross" profile, so maybe I'm missing > > something? > > > > In case I'm not, please consider the attached patch for the APT resolver. > > can you show me an example where sbuild does not respect build profiles for > build dependency resolving?
I was playing with a local repository, and a <cross> build dependency wasn't getting installed for the target architecture even though the profile was activated. Or something like that. Anyway, I'll try to construct a simple test case and get back to you. > Also back when I implemented build profile support in sbuild it was working > just fine. Looking at the code now it still should. Just in case it wasn't obvious: the code path here is specific to the cross build dependency resolving. > Also, because we must support apt in old-old-stable we cannot just push the -P > argument to the apt-get invocation since this will break apt pre-Jessie. Ah, that's unfortunate. Does cross building really work on oldoldstable? Maybe 'apt-get -o "APT::Build-Profiles=[...]" would work instead? It looks like apt-get ignores unknown configuration variables. -- Niko Tyni [email protected]
