Package pages say Failures: None when Not yet built

[Jonathan Riddell]

Package pages e.g. https://launchpad.net/people/jr/+packages says Failures: None even when the package has not been built at all, this makes it impossible to tell if the package has been built or still needs to be built. It should say "Not yet built" which is what happens if there is a chroot problem.

[Diogo Matsubara (matsubara)]

Is this still a problem?

[Patricio Gonzalez (pagondel)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[Emmet Hikory (persia)]

I've been able to reproduce this as recently as 29th June 2008. Unfortunately, it's hard to reproduce today, as the build queues are fairly empty, but unless there's a known change to the algorithm by which this is determined (appears to be polling the build queues for failed builds), it probably didn't go away.

[William Grant (wgrant)]

Could the indicator used on IArchive:+index be suitable? That has had quite some polish recently, and actually makes a bit of sense.

[Celso Providelo (cprov)]

Yes, that's a very good idea, but we would have to join the publishing history for the packages, which could make the page rendering slow.

On the bright side, we already have mechanisms in place for making it faster (used in PPA:+index) and this would be the solution for bug #115078 (broken links).