#A4# #Developed by Kevin Mark (c) 2004,2005 with S. Müller, M. Schulze, G. von Brederlow, M. Krafft, F. Küster, J. Mouette and other debianistas using Free software and the FLOSS culture (updated 2005-03-24)# #build process produces a report that is sent to the BTS # #incoming propagates the unstable binary packages# #experimental# #unstable# #incoming propagates the testing proposed updates binary packages# #testing proposed updates# #testing# #incoming propagates the stable proposed updates binary packages# #stable proposed updates# #stable# #user systems# #BTS# #the Debian development process# #unstable packages usually propagate to testing based upon urgency tags and no additional RC bugs# #incoming propagates the experimental binary packages# #Other directories new(1st upload or new binary) byhand(needs special ftpmaster care) rejected(failed checks)# #testing proposed updates propagate to testing by release managerˈs choice# #users of stable install the binary package# #users of stable issue bugreports# #users of testing install the binary package# #users of testing issue bugreports# #users of unstable install the binary package# #users of unstable issue bugreports# #user files a WNPP in the BTS# #users of experimental issue bugreports# #all testing packages migrate to stable after there are no release critical bugs and there is a decision to release# #“britney” is the name of the scripts that manage Debian’s testing distribution; it uses a number of criteria, including time since upload, number of open bugs, where it’s been ported to, and dependency information to maintain a set of packages that meet Debian’s release goals. (tbm)# ## #'dupload' is a script to automatically upload packages to the archive, to log the upload, and to send mail about the upload of a package. The 'dput' script does much the same thing as dupload, but in a different way. It has some features over dupload, such as the ability to check the GnuPG signature and checksums before uploading, and the possibility of running dinstall in dry-run mode after the upload. (dev-ref)# #users of experimental install the package# #britney# #LEGEND# #manual transfer# #automated transfer# #maintainer related# #FTP master maintained servers# #developer related processes# #user related# #FTP master maintained scripts # #maintainer/porter processes# #a maintainer creates and tags the binary package usually with Pbuilder# #the porter retrieves the source packages from incoming if the package has a new binary or if it is a new package otherwise it retrieves it from the appropriate repository# #**START HERE **# #note about Debian created software# #source packages contains this: (.dsc + .tar.gz)# #creates and tags the source package for non-Debian software:(.dsc + .diff.gz + orig.tar.gz)# #debianizes the source# #a maintainer retrieves the upstream source# #the upstream source (.orig.tar.gz)# #the debian source based upon it is modified# #BTS forwards bugs# #checks upstream# #forwards patches and other source changes to upstream# #reads the bug reports# #BTS forwards bugs# #maintainer submits an ITA: bug in the BTS# #files an ITA after reading about an orphanded package on the debian-devel maling list# #maintainer submits an O: bug against a WNPP in the BTS# #a maintainer files an ITP in the BTS# #the maintainer finds a free software package that interests them on the internet# #maintainer adopts package# #a maintainer finds a WNPP in the BTS# #maintainer orphans package# #package adoption# #package repositories# #dput or dupload# #INCOMING.debian.org server# #new# #accepted# #rejected# #byhand# #unchecked# #katie# #UploadQueue# #new queue package list is mailed to ftp-masters# #Packages are uploaded to incoming by all the maintainers into a directory called unchecked. This directory is scanned every 15 minutes by the "katie" script, which verifies the integrity of the uploaded packages and their cryptographic signatures.(dev-ref)# #autobuilder network consists of the per-arch wanna-build database and 1 or more buildd servers per-arch# #sbuild script# #buildd script# #andrea script# #sends status to BTS# #buildd# #porting building processes# #buildd maintainer# #a developer inspects the changes file and signs it. They then uploads the source and binary packages to incoming# #'sbuild' uses an existing chroot, copies the source there, installs the build dependencies, builds the package, copies the generated packages out and deinstalls the build dependencies. (F. Lichenheld)# #'pbuilder' untars a tarball of a clean build system, copies the source into the chroot, installs the build dependencies there, builds the package, copies the generated packages out and deletes the whole chroot. (F. Lichtenheld)# #katie sends email to nnn-close@bugs.debian.org to close bug #nnn in the BTS# #katie sends ACCEPTED status email to the debian-devel-changes list and update the wanna-build database and is sent to maintainer.# #'packages-arch-specific' is a data file that lists specific packages that need to excluded from being built on certain archatectures. This file is used by the wanna-build to control whether a package is feed to a buildd to be built. (S. Langasek)# #stable proposed updates propagate to stable by stable RMˈs choice# #quinn-diff uses the 'Architecture' field of sources. P-A-S is used by UNKNOWN. And when a conflict arises, X happens. When more archs are added (or 'any' appears), wanna-build will pick it up for those archs automatically build for those. Debian policy dictates that, where possible, all archs have to be supported. (G v B)# #'sbuild' checks the 'architecture' list of a source upload and fails if the current arch of the buildd is not on the list (Steve Langasek)# #Porters read bug reports from the bts and from buiildd logs to address port bugs. These result in either patches being submitted to the bts or modification of the debian source. FIXME FIXME FIXME# #$arch@buildd.debian.org recieves buildd's failed package logs. FIXME FIXME FIXME# #buildd admins setup a server to take messages from the wanna-build to build packages. buildd admins maintain these machines and the scripts. They do not fix package creation errors, porters do. buildd admins can requeue a package with an incorrect build-depends. FIXME FIXME FIXME# #In other words, p-a-s is separate from the debian/control Architecture lines for the same reason the ftpmasters' override file is separate from the debian/control Section and Priority lines. Because the buildd admins, and ftpmasters, *want* to maintain this information manually (P. Samuelson).# #Also any buildd admin can set the package to Not-For-Us status in wanna-build. That has the same effect as P-a-s except that it skews the stats. But it is a perfect temporary solution. (G v B). # ## ## #build database for package and build status# #quinn-diff script# #wanna-build script# #packages file from ftp.debian.org# #packages-arch-specific file# #build when idle list do not build list 'not-for-us' list# #the binary packages are uploaded to incoming after build success# #failed build logs result in an error message and the package status being updated in the buildd database# #maintainer replys with signed changes file when success# #sends build log to maintainer# ## #http://svn.cyberhqz.com/svn/wanna-build/README.overview# ## #'sbuild' is an automated builder that can use chrooted environments as part of a networked, distributed build environment(buildd) that is part of the system used by porters to build binary packages for all the available architectures. (dev-ref)# #There is a new funcionality in sbuild to report build state info. This info will be used by the buildd scripts and reported back into the build database with wanna-build script as updated status info. (paraphrase from mrvn on #debian-devel, 2006)#