Bug#577612: hadoop: General update after the debconf review process
Christian PERRIER
bubulle at debian.org
Wed May 5 05:36:48 UTC 2010
Dear Debian maintainer,
On Friday, March 26, 2010, I sent you a notification about the beginning of a review
action on debconf templates for hadoop.
Then, I sent you a bug report with rewritten templates and announcing
the beginning of the second phase of this action: call for translation
updates.
Translators have been working hard and here is now the result of their efforts.
Please consider using it EVEN if you committed files to your
development tree as long as they were reported.
The attached tarball contains:
- debian/changelog with the list of changes
- debian/control with rewrites of packages' descriptions
- debian/<templates> with all the rewritten templates file(s)
- debian/po/*.po with all PO files (existing ones and new ones)
As said, please use *at least* the PO files as provided here,
preferrably over those sent by translators in their bug reports. All
of them have been checked and reformatted. In some cases, formatting
errors have been corrected.
The patch.rfr file contains a patch for the templates and control
file(s) alone.
Please note that this patch applies to the templates and control
file(s) of your package as of Friday, March 26, 2010. If your package was updated
in the meantime, I may have updated my reference copy....but I also
may have missed that. This is indeed why I suggested you do not
modified such files while the review process was running,
remember..:-)
It is now safe to upload a new package version with these changes.
Please notify me of your intents with regards to this.
There is of course no hurry to update your package but feel free to
contact me in case you would need sponsoring or any other action to
fix this.
--
-------------- next part --------------
A non-text attachment was scrubbed...
Name: patch.tar.gz
Type: application/octet-stream
Size: 8529 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20100505/7389541f/attachment-0001.obj>
-------------- next part --------------
--- hadoop.old/debian/hadoop-namenoded.templates 2010-03-22 09:56:11.717948376 +0100
+++ hadoop/debian/hadoop-namenoded.templates 2010-04-13 07:16:51.506026053 +0200
@@ -1,17 +1,25 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# debian-l10n-english at lists.debian.org for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
Template: hadoop-namenoded/format
Type: boolean
Default: false
-_Description: Should the namenode's filesystem be formatted now?
- The namenode manages the Hadoop Distributed FileSystem (HDFS). Like a
- normal filesystem, it needs to be formatted prior to first use. If the
- HDFS filesystem is not formatted, the namenode daemon will fail to
+_Description: Should namenoded's file system be formatted?
+ The Name Node daemon manages the Hadoop Distributed File System (HDFS).
+ Like a normal file system, it needs to be formatted prior to first use.
+ If the HDFS file system is not formatted, the Name Node will fail to
start.
.
- This operation does not affect the "normal" filesystem on this
- computer. If you're using HDFS for the first time and don't have data
- from previous installations on this computer, it should be save to
- proceed with yes.
+ This operation does not affect other file systems on this
+ computer. You can safely choose to format the file system if you're
+ using HDFS for the first time and don't have data from previous
+ installations on this computer.
.
- You can later on format the filesystem yourself with
- .
- su -c"hadoop namenode -format" hadoop
+ If you choose not to format the file system right now, you can do it
+ later by executing "hadoop namenode -format" as the user "hadoop".
--- hadoop.old/debian/control 2010-03-22 09:56:11.717948376 +0100
+++ hadoop/debian/control 2010-03-31 06:59:53.610677495 +0200
@@ -29,7 +29,7 @@
Package: libhadoop-java
Architecture: all
-Depends: ${misc:Depends},
+Depends: ${misc:Depends},
libcommons-cli-java,
libcommons-codec-java,
libcommons-el-java,
@@ -44,20 +44,46 @@
libslf4j-java,
libxmlenc-java
Suggests: libhsqldb-java
-Description: software platform for processing vast amounts of data
- This package contains the core java libraries.
+Description: data-intensive clustering framework - Java libraries
+ Hadoop is a software platform for writing and running applications
+ that process vast amounts of data on a distributed file system.
+ .
+ Here's what makes Hadoop especially useful:
+ * Scalable: Hadoop can reliably store and process petabytes.
+ * Economical: It distributes the data and processing across clusters
+ of commonly available computers. These clusters can number
+ into the thousands of nodes.
+ * Efficient: By distributing the data, Hadoop can process it in parallel
+ on the nodes where the data is located. This makes it
+ extremely rapid.
+ * Reliable: Hadoop automatically maintains multiple copies of data and
+ automatically redeploys computing tasks based on failures.
+ .
+ This package contains the core Java libraries.
Package: libhadoop-index-java
Architecture: all
Depends: ${misc:Depends}, libhadoop-java (= ${binary:Version}),
liblucene2-java
-Description: Hadoop contrib to create lucene indexes
- This contrib package provides a utility to build or update an index
- using Map/Reduce.
- .
- A distributed "index" is partitioned into "shards". Each shard corresponds
- to a Lucene instance. org.apache.hadoop.contrib.index.main.UpdateIndex
- contains the main() method which uses a Map/Reduce job to analyze documents
+Description: data-intensive clustering framework - Lucene index support
+ Hadoop is a software platform for writing and running applications
+ that process vast amounts of data on a distributed file system.
+ .
+ Here's what makes Hadoop especially useful:
+ * Scalable: Hadoop can reliably store and process petabytes.
+ * Economical: It distributes the data and processing across clusters
+ of commonly available computers. These clusters can number
+ into the thousands of nodes.
+ * Efficient: By distributing the data, Hadoop can process it in parallel
+ on the nodes where the data is located. This makes it
+ extremely rapid.
+ * Reliable: Hadoop automatically maintains multiple copies of data and
+ automatically redeploys computing tasks based on failures.
+ .
+ The org.apache.hadoop.contrib.index.main.UpdateIndex library provides
+ support for managing an index using MapReduce. A distributed "index" is
+ partitioned into "shards", each corresponding to a Lucene instance.
+ This library's main() method uses a MapReduce job to analyze documents
and update Lucene instances in parallel.
Package: hadoop-bin
@@ -65,9 +91,9 @@
Architecture: all
Depends: ${misc:Depends}, libhadoop-java (= ${binary:Version}),
default-jre-headless | java6-runtime-headless
-Description: software platform for processing vast amounts of data
- Hadoop is a software platform that lets one easily write and
- run applications that process vast amounts of data.
+Description: data-intensive clustering framework - tools
+ Hadoop is a software platform for writing and running applications
+ that process vast amounts of data on a distributed file system.
.
Here's what makes Hadoop especially useful:
* Scalable: Hadoop can reliably store and process petabytes.
@@ -86,33 +112,73 @@
nodes around the cluster. MapReduce can then process the data where it is
located.
.
- This package contains the hadoop shell interface. See the packages hadoop-.*d
- for the hadoop daemons.
+ This package provides the hadoop command line interface. See the hadoop-.*d
+ packages for the Hadoop daemons.
Package: hadoop-daemons-common
Section: misc
Architecture: all
Depends: ${misc:Depends}, hadoop-bin (= ${binary:Version}), daemon, adduser,
lsb-base (>= 3.2-14)
-Description: Creates user and directories for hadoop daemons
- Prepares some common things for all hadoop daemon packages:
- * creates the user hadoop
- * creates data and log directories owned by the hadoop user
- * manages the update-alternatives mechanism for hadoop configuration
- * brings in the common dependencies
+Description: data-intensive clustering framework - common files
+ Hadoop is a software platform for writing and running applications
+ that process vast amounts of data on a distributed file system.
+ .
+ Here's what makes Hadoop especially useful:
+ * Scalable: Hadoop can reliably store and process petabytes.
+ * Economical: It distributes the data and processing across clusters
+ of commonly available computers. These clusters can number
+ into the thousands of nodes.
+ * Efficient: By distributing the data, Hadoop can process it in parallel
+ on the nodes where the data is located. This makes it
+ extremely rapid.
+ * Reliable: Hadoop automatically maintains multiple copies of data and
+ automatically redeploys computing tasks based on failures.
+ .
+ This package provides infrastructure for the Hadoop daemon packages,
+ creating the hadoop user (with data and log directories) and maintaining
+ the update-alternatives mechanism for hadoop configuration.
Package: libhadoop-java-doc
Section: doc
Architecture: all
Depends: ${misc:Depends}, libhadoop-java (= ${binary:Version})
-Description: Contains the javadoc for hadoop
- contains the api documentation of hadoop
+Description: data-intensive clustering framework - Java documentation
+ Hadoop is a software platform for writing and running applications
+ that process vast amounts of data on a distributed file system.
+ .
+ Here's what makes Hadoop especially useful:
+ * Scalable: Hadoop can reliably store and process petabytes.
+ * Economical: It distributes the data and processing across clusters
+ of commonly available computers. These clusters can number
+ into the thousands of nodes.
+ * Efficient: By distributing the data, Hadoop can process it in parallel
+ on the nodes where the data is located. This makes it
+ extremely rapid.
+ * Reliable: Hadoop automatically maintains multiple copies of data and
+ automatically redeploys computing tasks based on failures.
+ .
+ This package provides the API documentation of Hadoop.
Package: hadoop-tasktrackerd
Section: misc
Architecture: all
Depends: ${misc:Depends}, hadoop-daemons-common (= ${binary:Version})
-Description: Task Tracker for Hadoop
+Description: data-intensive clustering framework - Task Tracker
+ Hadoop is a software platform for writing and running applications
+ that process vast amounts of data on a distributed file system.
+ .
+ Here's what makes Hadoop especially useful:
+ * Scalable: Hadoop can reliably store and process petabytes.
+ * Economical: It distributes the data and processing across clusters
+ of commonly available computers. These clusters can number
+ into the thousands of nodes.
+ * Efficient: By distributing the data, Hadoop can process it in parallel
+ on the nodes where the data is located. This makes it
+ extremely rapid.
+ * Reliable: Hadoop automatically maintains multiple copies of data and
+ automatically redeploys computing tasks based on failures.
+ .
The Task Tracker is the Hadoop service that accepts MapReduce tasks and
computes results. Each node in a Hadoop cluster that should be doing
computation should run a Task Tracker.
@@ -121,34 +187,90 @@
Section: misc
Architecture: all
Depends: ${misc:Depends}, hadoop-daemons-common (= ${binary:Version})
-Description: Job Tracker for Hadoop
- The jobtracker is a central service which is responsible for managing
- the tasktracker services running on all nodes in a Hadoop Cluster.
- The jobtracker allocates work to the tasktracker nearest to the data
+Description: data-intensive clustering framework - Job Tracker
+ Hadoop is a software platform for writing and running applications
+ that process vast amounts of data on a distributed file system.
+ .
+ Here's what makes Hadoop especially useful:
+ * Scalable: Hadoop can reliably store and process petabytes.
+ * Economical: It distributes the data and processing across clusters
+ of commonly available computers. These clusters can number
+ into the thousands of nodes.
+ * Efficient: By distributing the data, Hadoop can process it in parallel
+ on the nodes where the data is located. This makes it
+ extremely rapid.
+ * Reliable: Hadoop automatically maintains multiple copies of data and
+ automatically redeploys computing tasks based on failures.
+ .
+ The Job Tracker is a central service which is responsible for managing
+ the Task Tracker services running on all nodes in an Hadoop Cluster.
+ The Job Tracker allocates work to the Task Tracker nearest to the data
with an available work slot.
Package: hadoop-namenoded
Section: misc
Architecture: all
Depends: ${misc:Depends}, hadoop-daemons-common (= ${binary:Version})
-Description: Name Node for Hadoop
- The Hadoop Distributed Filesystem (HDFS) requires one unique server, the
- namenode, which manages the block locations of files on the filesystem.
+Description: data-intensive clustering framework - Name Node
+ Hadoop is a software platform for writing and running applications
+ that process vast amounts of data on a distributed file system.
+ .
+ Here's what makes Hadoop especially useful:
+ * Scalable: Hadoop can reliably store and process petabytes.
+ * Economical: It distributes the data and processing across clusters
+ of commonly available computers. These clusters can number
+ into the thousands of nodes.
+ * Efficient: By distributing the data, Hadoop can process it in parallel
+ on the nodes where the data is located. This makes it
+ extremely rapid.
+ * Reliable: Hadoop automatically maintains multiple copies of data and
+ automatically redeploys computing tasks based on failures.
+ .
+ The Hadoop Distributed File System (HDFS) requires one unique server, the
+ Name Node, which manages the block locations of files on the file system.
Package: hadoop-secondarynamenoded
Section: misc
Architecture: all
Depends: ${misc:Depends}, hadoop-daemons-common (= ${binary:Version})
-Description: Secondary Name Node for Hadoop
- The Secondary Name Node is responsible for checkpointing file system images.
- It is _not_ a failover pair for the namenode, and may safely be run on the
- same machine.
+Description: data-intensive clustering framework - secondary Name Node
+ Hadoop is a software platform for writing and running applications
+ that process vast amounts of data on a distributed file system.
+ .
+ Here's what makes Hadoop especially useful:
+ * Scalable: Hadoop can reliably store and process petabytes.
+ * Economical: It distributes the data and processing across clusters
+ of commonly available computers. These clusters can number
+ into the thousands of nodes.
+ * Efficient: By distributing the data, Hadoop can process it in parallel
+ on the nodes where the data is located. This makes it
+ extremely rapid.
+ * Reliable: Hadoop automatically maintains multiple copies of data and
+ automatically redeploys computing tasks based on failures.
+ .
+ The secondary Name Node is responsible for checkpointing file system images.
+ It is _not_ a failover partner for the name node, and may safely be run on
+ the same machine.
Package: hadoop-datanoded
Section: misc
Architecture: all
Depends: ${misc:Depends}, hadoop-daemons-common (= ${binary:Version})
-Description: Data Node for Hadoop
+Description: data-intensive clustering framework - Data Node
+ Hadoop is a software platform for writing and running applications
+ that process vast amounts of data on a distributed file system.
+ .
+ Here's what makes Hadoop especially useful:
+ * Scalable: Hadoop can reliably store and process petabytes.
+ * Economical: It distributes the data and processing across clusters
+ of commonly available computers. These clusters can number
+ into the thousands of nodes.
+ * Efficient: By distributing the data, Hadoop can process it in parallel
+ on the nodes where the data is located. This makes it
+ extremely rapid.
+ * Reliable: Hadoop automatically maintains multiple copies of data and
+ automatically redeploys computing tasks based on failures.
+ .
The Data Nodes in the Hadoop Cluster are responsible for serving up
- blocks of data over the network to Hadoop Distributed Filesystem
+ blocks of data over the network to Hadoop Distributed File System
(HDFS) clients.
--- hadoop.old/debian/changelog 2010-03-22 09:56:11.717948376 +0100
+++ hadoop/debian/changelog 2010-05-01 20:05:36.832270350 +0200
@@ -1,3 +1,19 @@
+hadoop (0.20.2+dfsg1-2) UNRELEASED; urgency=low
+
+ * Debconf templates and debian/control reviewed by the debian-l10n-
+ english team as part of the Smith review project. Closes: #577612
+ * [Debconf translation updates]
+ * Vietnamese (Clytie Siddall). Closes: #578134
+ * Russian (Yuri Kozlov). Closes: #578220
+ * Portuguese (Pedro Ribeiro). Closes: #578248
+ * Czech (Michal Simunek). Closes: #578536
+ * Swedish (Martin Bagge). Closes: #579301
+ * French (Alexandre Ho?d). Closes: #579354
+ * Spanish (Francisco Javier Cuadrado). Closes: #579629
+ * German (Martin Eberhard Schauer). Closes: #579823
+
+ -- Christian Perrier <bubulle at debian.org> Sat, 17 Apr 2010 08:00:21 +0200
+
hadoop (0.20.2+dfsg1-1) unstable; urgency=low
* New upstream version 0.20.2
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20100505/7389541f/attachment-0001.pgp>
More information about the pkg-java-maintainers
mailing list