Hi, Am Montag, den 20.05.2013, 19:58 +0200 schrieb Mehdi Dogguy: > Le 2013-05-20 17:14, Joachim Breitner a écrit : > > Hi, > > > > as discussed on IRC: Support for actually displaying the buildd status > > on developer.php. > > > > There are up to two lines, one for unstable and one (possibly) for > > experiemntal). If the package is in good shape on all arches > > (Installed > > or Not-For-Us), a summary is displayed, otherwise all arches are > > shown. > > > > Pabs suggested to sum up the individual states, but I prefer it this > > way, as it allows to spot with one glance what arches are affected, > > and > > if one arch is doing particularly bad. > > > > Cronjob script untested, the rest can be seen in action on > > http://qa.debian.org/~nomeata/developer.php?login=nomeata > > > > I can see the need for such view, but somehow, it also makes it less > clear than the old version...
The old version is just a static link to buildd, and no mention of exp at all... or what view are you referring to? > since sid and exp look the same. Also, it > is not true that "exp is always the same" since you could have a package > in exp, and not in sid. In that case, there is a "-" in the first line: http://qa.debian.org/~nomeata/developer.php?packages=haskell-blaze-svg > IMHO, it would be "nicer" if buildd links could be colored when some > package is failing to build on some arch. It would still be visually clear > which suite is impacted, and adds the information about the buildd state. How so, there is only one link. Also, there are quite a few package where there is one arch always in a bad state (such as BD-Uninstallable); just exposing one bit of information is not a lot, when we can expose much more. Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata
signature.asc
Description: This is a digitally signed message part
