Re: Limiting piuparts results in DDPO
Re: Holger Levsen 2014-05-24 <201405241551.17305.holger@layer-acht.org>
> Hi,
>
> why is this private between the three of us? Reply to -qa@l.d.o please....
Cc'ing now.
> On Samstag, 24. Mai 2014, Christoph Berg wrote:
> > I think the status as shown in DDPO should be more detailed, like the
> > debcheck results do. Many maintainers will want to handle problems in
> > unstable with higher priority than in stable, so if most of their "F"
> > are for dists they are less interested in, they'd probably ignore the
> > piuparts column pretty quickly. The overall status is only interesting
> > if it's "all ok".
>
> do you have an example showing this?
http://qa.debian.org/developer.php?packages=postgresql-plsh
https://piuparts.debian.org/lenny2squeeze/source/p/postgresql-plsh.html
> > So it will probably make sense to directly show where the problem(s)
> > are. I guess it's a bit harder for piuparts than for debcheck because
> > it also checks upgrades, so there'd be S, S2T, T, U, ... results.
>
> *nods*
>
> > (Oldstable plus O2S should probably not appear there at all, as few
> > people are going to care.)
>
> *nods*
Christoph
--
cb@df7cb.de | http://www.df7cb.de/
Reply to: