Hi,

looking at the transition tracker pages, I sometimes would like to know
about the state of a transition in testing, not unstable.
E.g. when I filed 729214 I had no clue whether the openmpi1.6 packages
had started migrating to testing ...

Not sure how this could be presented, perhaps an additional column to
the left with four possible values (colors): good, bad, unknown,
sid-only.


Andreas

Le 10/11/2013 14:55, Andreas Beckmann a écrit :

What would be the meaning of "good, bad, unknown" in this case? Note
that there is already "sid-only".


Cheers,

Whether the package in testing satisfies the transition properties as
they are defined for sid.

At the initial setup of a transition I would expect that everything
starts with bad/unknown/sid-only which turns into good/unknown/sid-only
once the full transition migrates - except in a few cases where
something is forcefully hinted intentionally breaking something (like
the 99% complete "almost finished" transitions) or something weird
happened (as for hypre, see #729214).
Thinking about libopenmpi1.6 there might be more cases where packagea
are initially "good".
But packages that are "bad" in jessie usually indicate "this blocks the
removal of something obsolete".


Andreas

Le 10/11/2013 15:28, Andreas Beckmann a écrit :
per-arch states) if the monitor were run on testing?

This basically means running the monitor twice: once for unstable, and
once for testing. It would even produce less data (loss of per-arch
states in testing) for the same amount of computation. I think this
should be done directly on the release.debian.org setup.


Cheers,

Hi,

Is there anything to be done about this bug?


Cheers,