#A4# #Developed by Kevin Mark (c) 2004,2005 with S. Müller, M. Schulze, G. von Brederlow, M. Krafft, F. Küster and other debianistas using Free software and the FLOSS culture (updated 2005-02-25)# #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# #PPC buildd# #PPC64 buildd# #AMD64 buildd# #MIPS buildd# #SPARC buildd# #i386 buildd# #ARM buildd# #the Debian development process# #BTS forwards bugs to upstream# #maintainer processes# #**START HERE **# #unstable packages usually propagate to testing based upon urgency tags and no additional RC bugs# #note about Debian created software# #source packages contains this: (.dsc + .tar.gz)# #the upstream source (.orig.tar.gz)# #incoming propagates the experimental binary packages# #Other directories new(1st upload or new binary) byhand(needs special ftpmaster care) rejected(failed checks)# #stable proposed updates propagate to stable by stable ʀʍˈs choice# #testing proposed updates propagate to testing by release managerˈs choice# #LEGEND# #manual transfer# #automated transfer# #maintainer related# #FTP master maintained servers# #developer related processes# #user related# #the buildd maintainer 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# #the buildd maintainer builds binary packages from the source package for all architectures# #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# #the maintainer checks upstream# #the maintainer reads the bugreports# #BTS forwards bugs to the maintainer# #the debian source based upon it is modified# #a maintainer forwards patches and other source changes to upstream# #a maintainer retrieves the upstream source# #a maintainer debianizes the source# #a maintainer creates and tags the source package for non-Debian software:(.dsc + .diff.gz + orig.tar.gz)# #a maintainer creates and tags the binary package# #maintainer submits an ITA: bug in the BTS# #maintainer submits an O: bug against a WNPP in the BTS# #the maintainer finds a free software package that interests them on the internet# #a maintainer files an ITP in the BTS# #a maintainer finds a WNPP in the BTS# #a maintainer files an ITA after reading about an orphanded package on the debian-devel maling list# #all testing packages migrate to stable after there are no release critical bugs and there is a decision to release# #FTP master maintained scripts # #“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)# #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)# #'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)# ## #'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# #a developer uploads the source and binary packages to incoming# #developer processes# #rejected# #byhand# #new# #accepted# #unchecked# #incoming server# #UploadQueue# #katie# #the binary packages are uploaded to incoming after being signed by the buildd maintainer# #britney# #dput or dupload# #build database for package and build status# #quinn-diff script# #wanna-build script# #uploads to incoming# #upload mailing lists# #buildd# #PPC64 buildds# #autobuilder network# #new queue package list is mailed to ftp-masters# #'accepted' status is email to maintainer which includes notification of closed bugs# #I386 dep info# #buildd# #build database for package and build status# #quinn-diff script# #wanna-build script# #buildd# #SPARC buildds# #sbuild script# #buildd script# #andrea script# #maintainer replys with ok# #sends status to maintainer# #sends status to BTS# #sbuild script# #buildd script# #andrea script# #maintainer replys with ok# #sends status to maintainer# #sends status to BTS# #sbuild script# #buildd script# #andrea script# #maintainer replys with ok# #sends status to maintainer# #sends status to BTS# #build when idle list do not build list# #build when idle list do not build list# #build when idle list do not build list# ## #* As a sidenote, wanna-build and buildd completly ignore the architecture line (apart from arch:all) and build packages anyway. G. V. B on -Devel.#