PPA & ogre-model combination causes unnecessary extra work

Bug #137769 reported by Matthias Klose
8
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Celso Providelo

Bug Description

see https://launchpad.net/~ubuntu-toolchain/+archive/+build/382957

libxul-dev is available in universe, why isn't the package built? or was gcc-4.3 moved implicitly to main?

Revision history for this message
Celso Providelo (cprov) wrote :

Well, gcc-4.3 is in main in your PPA (it wasn't overridden as in ubuntu as you'd expect), thus ogre-model forced builder to only look for build-deps in 'main' component.

Changed in soyuz:
assignee: nobody → cprov
status: New → Invalid
Revision history for this message
Matthias Klose (doko) wrote :

please consider to reopen this report; it's odd, we do see build failures because of component mismatches. why hide them? a user doesn't expect that the debian pocket is the relevant one.

Revision history for this message
Celso Providelo (cprov) wrote :

Ok, you are right, I've modified the summary to make clear that there is no "wrong error", but instead, a side-effect caused by the enforcement of ogre-model in the PPA scope where we do not have the ability to perform [auto-]overrides.

Changed in soyuz:
status: Invalid → Confirmed
Christian Reis (kiko)
Changed in soyuz:
importance: Undecided → High
Revision history for this message
Christian Reis (kiko) wrote :

I am in favor of making pockets and components irrelevant for PPAs, and updating the ogre code accordingly.

Revision history for this message
Mark Shuttleworth (sabdfl) wrote :

Just so I can follow this discussion better, what is the ogre code?

Revision history for this message
Celso Providelo (cprov) wrote :

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.

Revision history for this message
William Grant (wgrant) wrote :

I think the best idea would be to actually have overrides for PPAs, and have them default to the Ubuntu ones... but I presume there's a reason for not having them.

Celso Providelo (cprov)
Changed in soyuz:
status: Confirmed → In Progress
Revision history for this message
Celso Providelo (cprov) wrote :

RF 5088

Changed in soyuz:
status: In Progress → Fix Committed
Celso Providelo (cprov)
Changed in soyuz:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.