Comment 6 for bug 137769

Ok, 'ogre-model' is a rule that tells the builder to lookup for build-dependencies only in the target source component or lowers, as in the chart below:

{{{
|| target component || build-dep lookup ||
|| main || main ||
|| restricted || main, restricted ||
|| universe || main, restricted, universe ||
|| multiverse || main, restricted, universe, multiverse ||
|| partner || main, restricted, partner ||
}}}

It is a pretty valid mechanism in primary archive because it ensure that components are self-sustained, i.e., they can be rebuilt without depending on unknown binaries.

Although, the whole discussion is if this mechanism is valid for PPAs, where users don't have easy control of package-overrides.

We could simply avoid ogre-model enforcement on PPA build, but sooner or later it would bite us, specially if we copying/syncing the source to ubuntu primary archive.