P3As default dependencies don't include $distro-updates

Bug #316576 reported by Emilio Pozuelo Monfort
Affects Status Importance Assigned to Milestone
Launchpad itself
Celso Providelo

Bug Description

I have uploaded a package to a Private PPA which has a build dependency only satisfyable in hardy-updates. The P3A has:
 * Default (security dependencies and recommended updates).

yet it didn't work, setting a DEPWAIT on the package.

00:13 < cprov> pochu: the 'default' option presented in the UI (release + security + updates) internally represents "no dependencies overrides" which for P3As still hard-coded as release + security only

Celso Providelo (cprov)
Changed in soyuz:
assignee: nobody → cprov
importance: Undecided → High
milestone: none → 2.2.1
status: New → In Progress
Revision history for this message
Celso Providelo (cprov) wrote :

RF 7562. Now P3As dependencies are not hardcoded anymore, so the form will be telling the truth (default pockets + all components). P3As that rely on the embargoed environment will have to select that explicitly.

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

Forgot to mention that it will only work correctly when it get cherry-picked in production, so the builddmaster can benefit of the same default dependencies to all PPAs. I will communicate the CP here, too

Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :


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

Other bug subscribers