Bug#729223: ben: provide state of the package in testing, too

2013-11-10 Thread Andreas Beckmann
Package: ben
Version: 0.6.6
Severity: wishlist

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#729223: ben: provide state of the package in testing, too

2013-11-10 Thread Stéphane Glondu
Le 10/11/2013 14:55, Andreas Beckmann a écrit :
 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.

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


Cheers,

-- 
Stéphane


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#729223: ben: provide state of the package in testing, too

2013-11-10 Thread Andreas Beckmann
On 2013-11-10 15:13, Stéphane Glondu wrote:
 Le 10/11/2013 14:55, Andreas Beckmann a écrit :
 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.
 
 What would be the meaning of good, bad, unknown in this case? Note
 that there is already sid-only.

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#729223: ben: provide state of the package in testing, too

2013-11-10 Thread Stéphane Glondu
Le 10/11/2013 15:28, Andreas Beckmann a écrit :
 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.

 What would be the meaning of good, bad, unknown in this case? Note
 that there is already sid-only.
 
 Whether the package in testing satisfies the transition properties as
 they are defined for sid.

You mean the color of the source column (which is a combination of
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,

-- 
Stéphane


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org