Bug#713073: PTS: show library transition message also on the source package page

[Niels Thykier <niels@thykier.net>]

On 2013-08-20 09:24, Stéphane Glondu wrote:
> Le 16/08/2013 17:29, Giovanni Mascellani a écrit :
>> @Release team: Joachim Breitner asked to patch PTS so that it displays
>> not only the packages involved in a transition, but also the packages
>> that cause the transition (see the example below).
>> [...]
>> Is Ben aware of this information? If so, could you please export it in a
>> machine parsable way? If not, would you consider adding it?
> 
> Ben is aware of the packages that match the "affected" predicate. It
> seems that predicates the release team uses exclude the packages that
> cause the transition. For example, in libcogl12, the "affected"
> predicate is:
> 
> .depends ~ /libcogl(9|12)|libcogl-pango(0|12)/ & !(.source ~ "cogl")
> 

In the particular case, yes.  We have had (and suppose sometimes still
have) transitions where the "introducing source package" is not "affected".

> The last clause explicitly excludes the cogl source package, and
> therefore cogl doesn't appear in the transition monitoring page (nor in
> its PTS). I don't know why this clause was added.
> 
> 
> Cheers,
> 


I think the reason why we prefer having the introducing source package
as "unaffected", is because it will be taken care of by a source upload
(i.e. there is usually nothing for us to do about that package).  The
introducing package also tends to create its own "dependency level" in
the tracker, so excluding almost always removes a dependency level in
the tracker.

~Niels