PPA upload and build notifications and Release::Origin do not consider named-ppas

Bug #366113 reported by Celso Providelo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Celso Providelo

Bug Description

Currently, the upload notification from any PPA owner by me has a subject like:

{{{
[PPA cprov] [ubuntu/jaunty] python-setuptools 0.6c9-0ubuntu5~cprov1 (Accepted)
}}}

Even when it's target to my 'experimental' PPA.

The same issue happens with its Release file at http://ppa.launchpad.net/cprov/experimental/ubuntu/dists/jaunty/Release. It says:

{{{
Origin: LP-PPA-cprov
...
}}}

which makes version pinning amongst PPA for the same user/team impossible.

In both cases we can certainly suppress changes when it's the default PPA (the one named 'ppa') for keeping existing configuration working (email filterts and apt-preferences), but for new named-ppas we should make it clearer by using $OWNER_NAME/$PPA_NAME as reference.

Tags: lp-soyuz ppa
Celso Providelo (cprov)
Changed in soyuz:
assignee: nobody → Celso Providelo (cprov)
importance: Undecided → High
milestone: none → pending
status: New → Triaged
Celso Providelo (cprov)
Changed in soyuz:
milestone: pending → 2.2.4
status: Triaged → In Progress
Revision history for this message
Celso Providelo (cprov) wrote :

r8298 (devel)

summary: - PPA upload notifications and Release:Origin do not consider named-ppas
+ PPA upload and build notifications and Release::Origin do not consider
+ named-ppas
Changed in soyuz:
status: In Progress → Fix Committed
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.