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

[TAF] templates://mini-buildd/{mini-buildd-common.templates,mini-buildd-rep.templates,mini-buildd-bld.templates}



The mini-buildd package introduced new or modified debconf
templates. This is the perfect moment for a review to help the package
maintainer following the general suggested writing style and track
down typos and errors in the use of English language.

If someone wants to pick up this review, please answer to this mail,
in the mailing list, with an [ITR] (Intent To Review) label.

The templates file is attached.

To propose the file you reviewed for peer review, please send a [RFR]
(Request For Review) mail with the reviewed file attached...then a few
days later, when no more contributions come, a summary mail with a
[LCFC] (Last Chance For Comments) label.

Finally, after no more comments coming to the LCFC mail, you can send
the reviewed templates file as a bug report against the package.

Then, please notify the list with a last mail using a [BTS] label
with the bug number.

Helping the package maintainer to deal with induced translation
updates at that moment will be nice. If you're not comfortable with
that part of the process, please hand it off to a translator.

-- 


Template: mini-buildd-common/purging_repository
Type: note
_Description: About to purge your repository
 You have selected to purge mini-buildd on a repository host.
 .
 Puging means to remove the mini-buildd user along with all its
 files, including the repository in "/home/mini-buildd/rep".
 .
 If you want to keep that data,
 .
       BACK IT UP NOW BEFORE CONTINUING.
Template: mini-buildd-rep/mbd_id
Type: string
Description: Mini-buildd's identity:
 Identity of the mini-buildd network.
 .
 The identity is used on several places; most importantly, the
 distributions created will be called "BASEDIST-ID". For version
 strings, it plays the same role as "bpo" as used by
 backports.org.
 .
 Should be a short mnemonic made with letters only.

Template: mini-buildd-rep/mbd_rephost
Type: string
Description: Repository host name:
 Give the repository's host name; this is usually just the
 hostname you get via "hostname -f". This will be used to create
 URLs for HTTP acccess, and for ssh/scp commands.

Template: mini-buildd-rep/mbd_httpport
Type: string
Default: 80
Description: HTTP port to use:
 If you use a dedicated HTTP server not using a standard port;
 note that the whole network (i.e., build hosts too) must use
 that port.

Template: mini-buildd-rep/mbd_sshport
Type: string
Default: 22
Description: SSH port to use:
 If you use a dedicated SSH server not using a standard port;
 note that the whole network (i.e., build hosts too) must use
 that port.

Template: mini-buildd-rep/mbd_mail
Type: string
Description: Mail address (uploads/builds/failures):
 All install, failure or log mails go here; usually, it's a good
 idea to set up a mailing list for that.

Template: mini-buildd-rep/mbd_extdocurl
Type: string
Description: External documentation URL:
 URL to external documentation.
 .
 This is just for convenience to provide a link to that URL on
 the overview page; just leave empty if you don't have any.

Template: mini-buildd-rep/mbd_dists
Type: multiselect
Choices: ${DISTS}
Description: Basis distributions to support:
 Space separated list of basis distributions to support.

Template: mini-buildd-rep/mbd_archs
Type: multiselect
Choices: ${ARCHS}
Description: Architectures to support:

Template: mini-buildd-rep/mbd_apt_allow_unauthenticated
Type: boolean
Default: false
Description: Allow unauthenticated apt?
 This flag correspondents to the respective apt and sbuild
 options.
 .
 If you set this to false (highly recommended), you will need to
 manually add the keys for extra sources you might have
 configured (see ~/.mini-buildd/README for further instructions).
 .
 The standard Debian Keys should be managed fine by the
 *-keyring packages (the paranoid may manually check the
 fingerprints after initial chroot setups).
 .
 Set this to true only if you really trust your configured
 sources.

Template: mini-buildd-rep/mbd_archall
Type: select
Choices: ${ARCHS}
Description: Arch of builder to build non-arch binary packages:
 One builder machine must have the part to compile arch=all
 binary packages; just give that architecture here.

Template: mini-buildd-rep/mbd_source
Type: string
Description: "${KIND}" sources for architecture "${ARCH}":
 Apt sources for "${DIST}": ${DESC}
 .
 Notes:
  * To specify more than one source, separate via "backslash n".
  * With PIN and PRIO you may optionally set an apt-pin; useful
    if an extra source is not in "not-automatic" mode.
  * Give arch-specific sources only if needed ("any" is
    fallback).
  .
  Syntax : Apt sources line without leading "deb "[;PIN;PRIO]
  Example: ${EXAMPLE}

Template: mini-buildd-rep/mbd_bldhost
Type: string
Description: Build host for architecture ${ARCH}:
 Build hosts are installations of mini-buildd-bld for a specific
 architecture; they manage the chroots and building for that
 architecture.
 .
 Please give a full hostname here.
 .
 You may safely give a build host to-be here, and set it up later.

Template: mini-buildd-rep/mbd_deb_build_options
Type: string
Description: Debian build options for architecture ${ARCH}:
 Build options as defined for DEB_BUILD_OPTIONS environment
 variable (see policy, chapter 4.9.1).
 .
 The only option that is useful here is "parallel=n"; use this
 if you have multiple CPUs/Cores at your hand for this archs
 build host. You will then have parallel builds (i.e. faster
 builds) for packages that support it.

Template: mini-buildd-rep/overview
Type: note
Description: Repository configuration finished
 After the package installation is complete, visit the new home
 of your build network:
 .
 ${URL}
 .
 CAVEAT: You need to enable your httpd's "userdir" option manually.
 .
 Please note:
  * On initial installs, or if you configured new build hosts:
    *install* package "mini-buildd-bld" on all resp. build hosts.
  * On reconfiguration with changes to supported dists or archs:
    *reconfigure* package "mini-buildd-bld" on all build hosts.
Template: mini-buildd-bld/mbd_defer
Type: boolean
Default: false
Description: Defer builder configuration?
 To configure builder hosts, the repository host must already be
 set up and configured (as all the common configuration is
 pulled from there by builder hosts).
 .
 Defer configuration in case your mini-buildd repository host is
 not yet set up correctly. You must complete your setup by
 running dpkg-reconfigure manually later.
 .
 ${STATUS}

Template: mini-buildd-bld/mbd_rephttphost
Type: string
Description: Repository (http) host name:
 Give the full host name of the repository here -- that is the
 machine where mini-buildd-rep is installed. This will be used
 to retrieve the configuration of the mini-buildd network
 automatically via http.
 .
 If you need to specify a different port than the default (80),
 use something like "my.host.com:8088".

Template: mini-buildd-bld/mbd_bldhost
Type: select
Choices: ${BLDHOSTS}
Description: This builder's id:
 This builder's host name; you see the selection from the
 configuration of mini-buildd-rep. If your host is not listed,
 you need to reconfigure mini-buildd-rep.
 .
 Default is the host matching $(hostname -f).

Template: mini-buildd-bld/mbd_lvm_vg
Type: string
Default: auto
Description: LVM2 volume group to use:
 You need a dedicated lvm volume group where the chroots are
 maintained (via schroot).
 .
 In that volume group, mini-buildd will automatically maintain
 chroots named mbd-BASEDIST-ID-ARCH (ID is the identity you
 configured in mini-buildd-rep).  These names should not collide
 with existing logical volumes in that group, else any
 reasonably sized volume group should work. Either
 .
  * Set this to "auto": An image file will be used automagically
    in mini-buildd's home, and a lvm volume group named
    "mini-buildd" be build on that via a loop device.
  * Set it to an existing or to-be custom volume group (if your
    create the volume group manually later, you need to
    reconfigure this package).
Source: mini-buildd
Section: devel
Priority: extra
Maintainer: Stephan Sürken <absurd@debian.org>
Build-Depends: debhelper (>= 7), man-db (>= 2.5.1), po-debconf
Standards-Version: 3.8.3
Vcs-Git: git://git.debian.org/git/collab-maint/mini-buildd.git
Vcs-Browser: http://git.debian.org/?p=collab-maint/mini-buildd.git;a=summary

Package: mini-buildd-common
Architecture: all
Depends: ${misc:Depends}, adduser, bsd-mailx | mailx, apache2-mpm-worker | httpd, openssh-client, gnupg, wget, sbuild (>= 0.57.7)
Description: Minimal Debian buildd (common)
 Mini-buildd is an easy-to-setup Debian autobuilder and
 repository. Its general notion is that of addons for a Debian
 base distribution (like etch, lenny, or sid) with an emphasis
 on clean builds and package checking.
 .
 This package includes common parts for both repository and
 builder installations.

Package: mini-buildd-rep
Architecture: all
Depends: ${misc:Depends}, mini-buildd-common, python, mini-dinstall (>> 0.6.24), cron, procps
Recommends: logrotate, dwww
Description: Minimal Debian buildd (repository)
 Mini-buildd is an easy-to-setup Debian autobuilder and
 repository. Its general notion is that of addons for a Debian
 base distribution (like etch, lenny, or sid) with an emphasis
 on clean builds and package checking.
 .
 Install this package on the machine that should hold the
 autobuilder network's repository.

Package: mini-buildd-bld
Architecture: all
Depends: ${misc:Depends}, mini-buildd-common, lvm2, debootstrap (>= 1.0.10lenny1), schroot, dput, dpkg-dev, devscripts (>= 2.10.15)
Recommends: logrotate
Description: Minimal Debian buildd (builder)
 Mini-buildd is an easy-to-setup Debian autobuilder and
 repository. Its general notion is that of addons for a Debian
 base distribution (like etch, lenny, or sid) with an emphasis
 on clean builds and package checking.
 .
 Install this package on any machine that should act as a
 builder for a specific architecture. To successfully configure
 a builder, the repository host (see package mini-buildd-rep)
 must be fully set up first.

Attachment: signature.asc
Description: Digital signature


Reply to: