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

[TAF] templates://distributed-net/{distributed-net.templates}

The distributed-net 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: 741107

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: distributed-net/fullconfig
Type: boolean
Default: false
_Description: Run the distributed.net client configuration utility?
 The distributed.net client needs to be configured before it can be used.
 While most options have reasonable defaults, you need to specify the e-mail
 address to which you would like distributed.net to credit any work done by
 the client.  If you are installing the distributed-net package for the first
 time, then you must configure the client, otherwise the distributed.net client
 will refuse to start.
 When the distributed.net client is run as a daemon (via /etc/init.d/distributed-net),
 the output will be redirected to /var/log/distributed-net.log.  You do not
 need to set up a log file.  Since the init script is controlling the
 distributed.net client, you should not enable "quiet mode" as that break the
 init script.
Source: distributed-net
Section: non-free/misc
Priority: optional
Maintainer: James E. Stark <jstark@ieee.org>
Homepage: http://www.distributed.net/
Build-Depends: debhelper (>= 5.0.0), po-debconf
Standards-Version: 3.9.5

Package: distributed-net
Architecture: i386 amd64 sparc powerpc armel mipsel
Conflicts: rc564
Replaces: rc564
Suggests: apmd, acpid
Depends: host | bind9-host, libc6 | libc6.1, ${misc:Depends}
Recommends: logrotate
Description: donate unused CPU cycles - client for distributed.net
 Donate your extra CPU cycles to a worthy cause!
 distributed.net started in 1997 as a project whose purpose was to win a
 series of contests sponsored by RSA Data Security Inc., to crack their RC5
 encryption by brute-force methods. These contests were meant to show
 governments of nations such as the United States, who limit exports or
 use of cryptography, that the standards allowed are too weak for general
 Since this time, distributed.net has changed their focus from solely
 cracking RSA's RC5 and DES projects to working on more diverse
 distributed computing problems.
 The ongoing projects are RC5-72 and Optimal Golomb Rulers (25-mark), the
 latter of which has practical applications in science. There are also a
 number of other projects which are either periodic or upcoming. You may
 choose which project you wish to participate in.
 By installing this package, unused CPU cycles on your computer will be used
 to work on cracking the code. There should be no noticeable slowdown of
 your system, since the client runs niced, and only uses CPU time when
 your computer would otherwise be idle.
 For more information, see http://www.distributed.net/

Attachment: signature.asc
Description: Digital signature

Reply to: