On Fri, Mar 03, 2006 at 09:51:12PM +0100, Stefan Potyra wrote:
> It's not exactly what I believe would be most useful. What I actually want to 
> know is, wether a package I uploaded built fine on all arches or if (and 
> where) there have been problems. If it built fine, that usually means that I 
> won't need to touch the package again. However if a build on one arch fails, 
> I'll need to examine what went wrong. 

I've added two columns: the upload date and build failures. Note that if
a package still needs building, is in dependency-wait or chroot-wait, it
will indicate "Not yet built"; only when it has finished attempting to
build /on all architectures/ will it give you feedback on anything that
actually failed. We can pack more information in that table, but it
needs some more work than I can put in today.

If you are in a hurry you will need to check the source package release
page; to make this easier I've also changed the link from the version to
the correct page for the source package release; that way you can
directly get to a page which lists and links to all the relevant builds.

This might not make this next week's rollout; if it does you'll see it
in the next Launchpad report. Fingers crossed!

When I come back to this page again I'll try addressing Matt's request
for reorganization -- the table is sortable, so I agree it would make
sense to put everything in the same table. This will require changing
the way data gets to the template, though, so it is more than a Saturday
morning hack. The performance of the page may be an issue, as it takes
quite a while to list the page for a very busy maintainer:

    https://launchpad.net/people/fabbione/+packages
    https://launchpad.net/people/kamion/+packages

Thanks,
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3376 0125

-- 
launchpad-users mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/launchpad-users

Reply via email to