The pybit package introduced new or modified debconf templates. This is often a good 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. A bug report has been sent against the package: 709001 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. These RFR and LCFC mails should CC the opened bug report. Finally, after no more comments coming to the LCFC mail, you can send the reviewed templates file in the bug report. 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: pybit-client/clientid Type: string _Description: PyBit client-ID string: Please specify a unique string that can be used to identify this client within the job list and queues. Template: pybit-client/lvmsnapshot Type: boolean Default: false _Description: Use LVM snapshots on this client? If the sbuild configuration uses LVM snapshots, pybit-client can ensure that your snapshot APT cache data is kept up-to-date whilst keeping the snapshot clean. Template: pybit-client/buildroot Type: string Default: /home/buildd/pybit _Description: Buildd location: Please specify a writeable directory where the version control handler and the upload task can write files. . If this is left blank, the default /home/buildd/pybit will be used. Template: pybit-client/rabbitmqhost Type: string _Description: Host machine running RabbitMQ: Please specify the server running RabbitMQ that this buildd client will communicate with, receiving details of the jobs it needs to attempt to build. Template: pybit-client/dputdest Type: string _Description: Destination for dput package uploads: Please specify the machine that this client will use as upload host. This destination will be stored in its dput configuration. . This entry must not be empty. Template: pybit-client/missingid Type: note _Description: Client-ID string cannot be empty! This client will fail to start until it receives a unique client-ID. Template: pybit-client/missinghost Type: note _Description: Missing RabbitMQ hostname! This client will not receive any messages from the queue and will not build any packages until a RabbitMQ host is specified. . Please edit /etc/pybit/client/client.conf after configuration. Template: pybit-client/defaultdput Type: note _Description: Missing dput destination! pybit-client is not intended to upload to unspecified dput destinations like ftp-master.debian.org and does not currently support GnuPG signed uploads.
Template: pybit-web/rabbitmqhost Type: string _Description: Host machine running RabbitMQ: Please specify the server running RabbitMQ with which the web front-end and the pyBit controller need to communicate, sending the details of the jobs to be built. Template: pybit-web/hostname Type: string Default: localhost _Description: Fully qualified hostname for the web front-end: Please specify the host running the web front-end (which will also be running the pyBit controller). . You may choose to use a named Apache virtual host or accept the default if all the pyBit clients also run on this one machine. . The hostname is passed down to the build clients to allow them to post failure messages back to the controller. Template: pybit-web/port Type: string Default: 80 _Description: Port for web front-end: Please specify the port that the web front-end should be available on. If it is serving localhost, it is probably easiest to use port 8080. . If the web front-end is running on a dedicated host or an Apache virtual host, it may be preferable to use port 80. Template: pybit-web/missinghost Type: note _Description: Missing RabbitMQ hostname! If no RabbitMQ host is specified for the pyBit controller, the build clients will not receive any messages on the queue or build any packages. . Please edit /etc/pybit/web/web.conf after configuration.
Source: pybit
Section: devel
Priority: extra
Maintainer: Neil Williams <codehelp@debian.org>
Uploaders: Nick Davidson <nickd@toby-churchill.com>,
Simon Haswell <simonh@toby-churchill.com>,
Nick Bane <nick@cecomputing.co.uk>,
James Bennet <James.Bennet@toby-churchill.com>
Build-Depends: debhelper (>= 7.0.50~), docbook-xsl, xsltproc, po-debconf,
python (>= 2.6.6-3~), python2.6 | python2.7, python-setuptools,
python-jsonpickle,
python-requests (>= 0.10.1-1~),
python-amqplib
X-Python-Version: 2.6, 2.7
Standards-Version: 3.9.3
Homepage: http://nicholasdavidson.github.com/pybit/
Vcs-Git: git://github.com/nicholasdavidson/pybit.git
Vcs-Browser: https://github.com/nicholasdavidson/pybit
Package: pybit-svn
Architecture: all
Depends: subversion, curl, ${misc:Depends}
Description: Subversion post commit hook for pybit
pyBit uses message queues to create a distributed, cross-platform
buildd toolkit using a collection of buildds, using source from
various VCS clients. pyBit is intended to support rapidly evolving
software collections and can support multiple VCS frontends and
multiple build backends.
.
This package provides a Subversion post commit hook to check for
interesting changes in the repository and post a directory back
to the controller using curl.
.
Currently, only Subversion is supported. The svn hook
does not depend on the rest of pyBit or on Python.
Package: pybit-client
Architecture: all
Depends: sbuild, dput, dpkg-dev, pybit-common, python-requests,
subversion, pbuilder, libcrypt-ssleay-perl, libjson-perl,
${python:Depends}, ${misc:Depends}
Description: buildd client support for pybit
pyBit uses message queues to create a distributed, cross-platform
buildd toolkit using a collection of buildds, using source from
various VCS clients. pyBit is intended to support rapidly evolving
software collections and can support multiple VCS frontends and
multiple build backends.
.
This package provides the Debian buildd client for pyBit to build
packages using sbuild.
.
Each pyBit buildd client needs to install and configure this package
to give each client a unique identifier per pyBit database.
Package: pybit-web
Architecture: all
Depends: python-psycopg2 (>= 2.4.2-1~), pybit-common,
dbconfig-common, libjson-perl, ucf, adduser,
${python:Depends}, ${misc:Depends}
Recommends: libjs-jquery (>= 1.4.2-2), libjs-jquery-form,
postgresql-client, libapache2-mod-wsgi
Suggests: rabbitmq-server (>=1.8), postgresql (>=8.4)
Replaces: pybit-common (<= 0.1.1)
Description: buildd toolkit based on message queues (web frontend)
pyBit uses message queues to create a distributed, cross-platform
buildd toolkit using a collection of buildds, using source from
various VCS clients. pyBit is intended to support rapidly evolving
software collections and can support multiple VCS frontends and
multiple build backends.
.
This package provides a reporting and custom-build request
interface for the status database and the controller agent for
PyBit. The static web pages do need to be served from the same
machine as is running the pybit-web application.
.
A single RabbitMQ server is also required, it can be installed on
any machine which is visible to the controller and all clients.
Package: pybit-common
Architecture: all
Depends: python-amqplib, python-jsonpickle, python-daemon,
${python:Depends}, ${misc:Depends}
Description: Common objects for pybit
pyBit uses message queues to create a distributed, cross-platform
buildd toolkit using a collection of buildds, using source from
various VCS clients. pyBit is intended to support rapidly evolving
software collections and can support multiple VCS frontends and
multiple build backends.
.
This package contains the object definitions of Python objects
common to pyBit components as well as the Postgres database
schema for pyBit.
Package: pybit-watcher
Architecture: all
Depends: python-pyinotify, python-daemon, pybit-common, reprepro,
${python:Depends}, ${misc:Depends}
Description: watches incoming directories for reprepro
pyBit uses message queues to create a distributed, cross-platform
buildd toolkit using a collection of buildds, using source from
various VCS clients. pyBit is intended to support rapidly evolving
software collections and can support multiple VCS frontends and
multiple build backends.
.
This package provides a watcher which runs as a daemon and monitors a
directory for changes files then runs the appropriate reprepro rule.
.
This allows pybit clients to upload without waiting for the packages
to be processed by reprepro.
Attachment:
signature.asc
Description: Digital signature