[Cooker] Cooker Condition proposal
I propose a method by which those of us who use Cooker frequently can tell if Cooker is installable or broken. Maybe we could have a Red Yellow Green condition to show the current status: RED= Broken (pending updates, not installable) YELLOW = Installable, but a few things not fully functional GREEN = Installable, most things work - maybe small bugs This would be extremely helpful so some of us don't waste out time trying to install a Cooker which is know to be broke or in transition. Perhaps a simple text file with the condition could be placed in the Cooker tree for us to check before downloading . . . I just tried today's Cooker (30.10.01) with no luck . . . and this has happened many times before . . . Just an idea! Thx, R.Fox
Re: [Cooker] Cooker Condition proposal
On 30 Oct 2001, Robert Fox wrote: I propose a method by which those of us who use Cooker frequently can tell if Cooker is installable or broken. Maybe we could have a Red Yellow Green condition to show the current status: RED= Broken (pending updates, not installable) YELLOW = Installable, but a few things not fully functional GREEN = Installable, most things work - maybe small bugs Something like the Mozilla tinderbox would be really nice (http://tinderbox.mozilla.org/showbuilds.cgi?tree=SeaMonkey) Especially if there was a way of showing what packages failed to build on either x86 or PPC , who broke it, and when. Ian --- Ian White email: [EMAIL PROTECTED]
Re: [Cooker] Cooker Condition proposal
Ian White wrote: On 30 Oct 2001, Robert Fox wrote: I propose a method by which those of us who use Cooker frequently can tell if Cooker is installable or broken. Maybe we could have a Red Yellow Green condition to show the current status: RED= Broken (pending updates, not installable) YELLOW = Installable, but a few things not fully functional GREEN = Installable, most things work - maybe small bugs Something like the Mozilla tinderbox would be really nice (http://tinderbox.mozilla.org/showbuilds.cgi?tree=SeaMonkey) Especially if there was a way of showing what packages failed to build on either x86 or PPC , who broke it, and when. I've got some scripts running on my box rebuilding packages and sorting the buildoutputs. Check out: http://cm61-10-20-87.hkcable.com.hk/build/cooker/i586/ I'd like to make a nice webinterface for it, keep history longer, put it in a database, make it a bit smarter, etc. Maybe an idea for a new project (something like debians buildd). Right now it's only a shellscript... Stefan
Re: [Cooker] Cooker Condition proposal
- Original Message - From: Robert Fox [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, October 30, 2001 12:11 PM Subject: [Cooker] Cooker Condition proposal I propose a method by which those of us who use Cooker frequently can tell if Cooker is installable or broken. This would be nice ;-) snip I just tried today's Cooker (30.10.01) with no luck . . . and this has happened many times before . . . Ditto. I just tried to do a freshed install yesterday and the installer was barfing in some area related to urpmi I don't have the error in front of me. I will re-rsync and see if I can reproduce the error for the group. Dan