Bug relations, '#nnn blocked by #mmm'

[Stefan Potyra]

Hi James,

Am Mittwoch 08 März 2006 08:29 schrieben Sie:
> >
> > I can add a simple use case from MOTU-land: basically any transition
> > matches exactly the #nnn blocked by #mmm relationship.
> >
> > Example: the (still outstanding) allegro -> allegro4.2-transition: First
> > allegro4.2 needs to be synced, then some packages can be rebuilt (e.g.
> > wing #33684, atanks #33679, libdumb #33672). Some packages also
> > build-depend on libdumb and thus cannot be rebuilt before libdumb was
> > rebuilt (e.g. kraptor #33681, rafkill #33685).
>
> Would a single bug with multiple bug tasks (one on each source
> package) cover this particular use case?

It would perfectly cover the use case of transitions, i.e. work that has to be 
done on many packages.

>
> It doesn't make the dependencies between the related tasks explicit,
> but it does group them logically (all the package updates relate to
> the same problem, right?).

Right. As you wrote, it doesn't provide explicit dependencies, and thus 
doesn't exactly match the particular use case above (work on a package, that 
cannot be done due to work that first needs to be done on another package). 
However I guess these are two distinct use-cases ;).

Cheers,
	Stefan.