Dear Debian maintainer, On Wednesday, March 12, 2014, I notified you of the beginning of a review process concerning debconf templates for distributed-net. The debian-l10n-english contributors have now reviewed these templates, and the final proposed changes are attached to this update to the original bug report. Please review the suggested changes, and if you have any objections, let me know in the next 3 days. However, please try to avoid uploading distributed-net with these changes right now. The second phase of this process will begin on Friday, April 04, 2014, when I will coordinate updates to translations of debconf templates. The existing translators will be notified of the changes: they will receive an updated PO file for their language. Simultaneously, a general call for new translations will be sent to the debian-i18n mailing list. Both these calls for translations will request updates to be sent as individual bug reports. That will probably trigger a lot of bug reports against your package, but these should be easier to deal with. The call for translation updates and new translations will run until about Friday, April 25, 2014. Please avoid uploading a package with fixed or changed debconf templates and/or translation updates in the meantime. Of course, other changes are safe. Please note that this is an approximative delay, which depends on my own availability to process this work and is influenced by the fact that I simultaneously work on many packages. Around Saturday, April 26, 2014, I will contact you again and will send a final patch summarizing all the updates (changes to debconf templates, updates to debconf translations and new debconf translations). Again, thanks for your attention and cooperation. --
# These templates have been reviewed by the debian-l10n-english # team # # If modifications/additions/rewording are needed, please ask # debian-l10n-english@lists.debian.org for advice. # # Even minor modifications require translation updates and such # changes should be coordinated with translators and reviewers. 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 breaks 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: client to donate unused CPU cycles to 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
use.
.
Since this time, distributed.net's focus has changed 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 (28-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.
.
Installing this package will allow unused CPU cycles on your computer to
contribute to 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.
--- distributed-net.old/debian/distributed-net.templates 2014-03-08 17:59:47.657657134 +0100
+++ distributed-net/debian/distributed-net.templates 2014-04-01 10:56:18.822335943 +0200
@@ -1,3 +1,12 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# debian-l10n-english@lists.debian.org for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
Template: distributed-net/fullconfig
Type: boolean
Default: false
@@ -5,12 +14,12 @@
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
+ 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
+ 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 breaks the
init script.
--- distributed-net.old/debian/control 2014-03-08 17:59:47.657657134 +0100
+++ distributed-net/debian/control 2014-03-18 07:31:37.692042288 +0100
@@ -13,7 +13,7 @@
Suggests: apmd, acpid
Depends: host | bind9-host, libc6 | libc6.1, ${misc:Depends}
Recommends: logrotate
-Description: donate unused CPU cycles - client for distributed.net
+Description: client to donate unused CPU cycles to 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
@@ -23,18 +23,16 @@
use of cryptography, that the standards allowed are too weak for general
use.
.
- Since this time, distributed.net has changed their focus from solely
+ Since this time, distributed.net's focus has changed 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
+ The ongoing projects are RC5-72 and Optimal Golomb Rulers (28-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
+ Installing this package will allow unused CPU cycles on your computer to
+ contribute to 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