[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Alpha coordination and building



On Thu, Jun 10, 1999 at 10:45:04AM -0500, John Goerzen wrote:
> Hello,
> First, you need to be aware of the website for this:
> 
>   http://www.complete.org/~buildd/

I think for this information is not relevent for the database. An interface to
wanna-build is though. So if ppl want to help building they should consult
these packages and inform the wanna-build. If you can create some *protected*
area where uploaders can store their patches this can also be a central
repository. This is relevent for your build proces if I understand it
correctly.

An ideal proces for me could be:
* Pick a/some packages you want to upload (preferably the ones that do not
  autobuild) and inform wanna-build
* Wanna-build logic consults database and informs me if/which problems are 
  posted on this package and supply an url to the patch(es) needed to build it
  last time
* Make it work
* Upload the patch (if needed) to the repository 
* Upload packages to master or an upload queue
* Send problem discription and patchname+bugreport to database if they are not
  already noted. The database handles submission of bugreport and inserts the
  bugnumber in the database.
* Weekly or dayly reports available via www and/or mail on buildproblems


Buildproblems that arise today:
1. Inproper configure settings for alpha
2. Inproper packaging like broken package or installation in / instead of
   $DESTDIR
3. Invalid buildresults like using 'ldconfig -n .' to generate symlinks in a
   build directory
4. Compiler hickups, like internal compiler errors or bad result when using
   -O2 optimization
5. Invalid dependencies. Example: building devel packges that depend on
   libc6-dev instead of libc6.1-dev
6. Erroneous debian/control file like build-rules for libc5 or wrong
   architecture settings
7. Installation failure: wrong package results like using fakeroot to build
   suid packages where the DEBIAN/postinst contains the builders account info
   (happened to me at least twice...)
8. There must be more than these mentioned above...


Possible dB model:


        Packages
       ---------------------
	
 +---	pkgID          long PK
 |	pkgName        text
 |	pgkVersion     text
 |	pkgDebRelease  text
 |	pkgBuildsOk    bool
 |	dateInstall    date/time
 |	uploader       text       (example: Bart Warmerdam <bartw@xs4all.nl>)
 |      btsNotificationDate date/time
 |
 |
 |      ReportedBugs
 |     ---------------------
 |
 |      btsBugNr       long PK
 +---   pkgID          long 
 |
 |
 |      Patches
 |     ---------------------
 |
 |      bugID          long PK
 +---   pkgID          long
        url            text
 

Waiting for comments....

B.


--
B. Warmerdam                                              GNU/Debian Linux
bartw@xs4all.nl, bartw@debian.org (Keyid: 10A0FDD1)       ----------------


Reply to: