[regression] ppa does not find packages that were published to !main components, before the component combining

Bug #163716 reported by Sarah Kowalik
12
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Celso Providelo

Bug Description

In the 1.1.11 rollout, the ogre model was blown away, and all packages are now put in the "main" component, and build against {main, universe, multiverse, restricted} in the ubuntu archives.

However, the packages in the ppa that are NOT in main, ie {restricted, universe, multiverse}, are now never found (when the deb/deb-src lines are added to a sources.list, and when things build-depend on them). Thus, these packages never build (eg, the great kdebase-workspace blowup).

The solution would be to override all of the packages in {restricted, universe, multiverse} of the ppa's into the main component, and republish the Packages lists. This should be a once-off.

Thanks!

Hobbsee

Tags: lp-soyuz
description: updated
Revision history for this message
Celso Providelo (cprov) wrote :

Ok, the 'mass-override' was performed this morning, so all PPA packages should be published in main component. Symbolic links remained in the original components and will be removed as soon as all references to the package become obsolete.

Changed in soyuz:
assignee: nobody → cprov
importance: Undecided → High
milestone: none → 1.1.11
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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