[pkg-bacula-commits] [bacula] 01/07: Removed obsolete information from README.Debian, spelling fixes, whitespace cleanup

Carsten Leonhardt leo at moszumanska.debian.org
Tue Sep 6 12:07:57 UTC 2016


This is an automated email from the git hooks/post-receive script.

leo pushed a commit to branch migrate-files
in repository bacula.

commit 5cc46420bc61dba6cc1a25e5d566b0bbce5f4ab9
Author: Carsten Leonhardt <leo at debian.org>
Date:   Mon Sep 5 17:24:42 2016 +0200

    Removed obsolete information from README.Debian, spelling fixes,
    whitespace cleanup
---
 debian/README.Debian                   | 74 ++++++++++++++--------------------
 debian/additions/common-functions.dpkg | 10 ++---
 debian/bacula-fd.postinst              |  4 +-
 debian/bacula-sd.postinst              |  2 +-
 debian/changelog                       |  1 +
 5 files changed, 38 insertions(+), 53 deletions(-)

diff --git a/debian/README.Debian b/debian/README.Debian
index f3c93c1..d75b2f9 100644
--- a/debian/README.Debian
+++ b/debian/README.Debian
@@ -3,7 +3,7 @@ http://www.bacula.org
 ===============================================================================
 
 The 'bacula-common' package provides some of the common infrastructure
-for Bacula.  You can find Bacula READMEs and other documentation files
+for Bacula. You can find Bacula READMEs and other documentation files
 there.
 
 DFSG-FREE PACKAGE
@@ -17,7 +17,7 @@ from the upstream sources.
 
 Please note that thanks to a patch by Alexander Golovko there was no
 loss of functionality: luckily, the SHA-1 implementation provided by
-the OpenSSL library is compatible with the own in Bacula.  The fact
+the OpenSSL library is compatible with the own in Bacula. The fact
 that Bacula is already linked with OpenSSL also means that nothing
 changed for the Debian package.
 
@@ -28,16 +28,16 @@ Please see the following bug report for a complete explanation:
 BASIC INFORMATION
 -----------------
 
-To use bacula you must install one of the flavors of director,
+To use Bacula you must install one of the flavors of director,
 depending on your preferred database, onto a server.
 
 You must also install bacula-sd on the machine where you will be
-storing your backed-up data.  And you'll need bacula-fd on any machine
+storing your backed-up data. And you'll need bacula-fd on any machine
 that you want to back up.
 
 The installation will run the necessary daemons automatically, but to
 get any backups working you must customize the relevant configuration
-files in /etc/bacula as described in the bacula manual.  Once you have
+files in /etc/bacula as described in the Bacula manual. Once you have
 edited the files you should issue an appropriate /etc/init.d/bacula-xx
 force-reload.
 
@@ -45,9 +45,9 @@ NETWORK ENABLING
 ----------------
 
 By default, Debian's Bacula packages install config files in which the
-servers listen only on localhost by default.  If you want to be able
+servers listen only on localhost by default. If you want to be able
 to do backups over the network, you'll need to find the lines in
-bacula-dir.conf, bacula-sd.conf, and bacula-fd.conf that reference
+bacula-dir.conf, bacula-sd.conf and bacula-fd.conf that reference
 127.0.0.1 and remove them.
 
 Note that all hostnames used in "Address"-lines need to be resolvable
@@ -98,11 +98,6 @@ Bacula, so that users can contact the director.
 The BAT graphical admin console is contained in the
 bacula-console-qt package.
 
-There are no wrappers for bacula-console-qt since it
-will likely be run from the corresponding
-launchers with appropriate '-c /etc/bacula/<flavor>.conf' arguments.
-The convenient '.menu' files are provided, too.
-
 USERS & SECURITY
 ================
 
@@ -110,19 +105,19 @@ The passwords in the configuration files in /etc/bacula have been
 auto-generated individually during installation. They are saved in
 /etc/bacula/common_default_passwords.
 
-The installation will create a bacula user on the system, and the
-daemons and RunBefore/RunAfter jobs will run as that user.  However,
-the file daemon run as root, as will your ClientRunBefore/After
-jobs. File daemon can use linux capabilities(7) for drop root
-privileges, but it require root privileges for correctly restore
-original files permissions. For run file daemon without root 
-privileges you can add ARGS="-k -u <username>" into
-/etc/default/bacula-fd. This is linux specific feature. Installation 
-of a director will ask you for a database user to use.
+The installation will create a "bacula" user on the system, and the
+daemons and RunBefore/RunAfter jobs will run as that user. However,
+the file daemon runs as root, as will your ClientRunBefore/After
+jobs. The file daemon can use Linux capabilities(7) to drop root
+privileges, but it requires root privileges to correctly restore the
+original file permissions. To run the file daemon without root
+privileges you can add ARGS="-k -u <username>" in
+/etc/default/bacula-fd. This is a Linux specific feature. The
+installation of the director will ask you for a database user to use.
 
 You can run Bacula consoles as any user, but the user you use will
-need to be able to read the console config files.  These files are, by
-default, under /etc/bacula.  You'll need to specify the config file
+need to be able to read the console config files. These files are, by
+default, under /etc/bacula. You'll need to specify the config file
 with -c for any of the consoles.
 
 PERFORMANCE NOTES
@@ -131,51 +126,42 @@ PERFORMANCE NOTES
 This was announced on Bacula's website with the release of Bacula 5.0.1:
 
  Some of you have encountered performance problems with your
- database (mainly with MySQL) with Bacula version 5.0.0.  This is
+ database (mainly with MySQL) with Bacula version 5.0.0. This is
  mainly because we've changed the SQL query used for restore,
- accurate jobs and base jobs.  We have extensively tested this
+ accurate jobs and base jobs. We have extensively tested this
  change, and though it should be a little bit slower than the previous
  versions, on a well configured database it should run
- extremely well.  
+ extremely well.
 
  We strongly recommend to avoid the temptation to add new indexes.
  In general, these will cause very significant performance
- problems in other areas.  A better approch is to carefully check
+ problems in other areas. A better approach is to carefully check
  that all your MySQL memory configuration parameters are
- suitable for the size of your installation.  If you backup
+ suitable for the size of your installation. If you backup
  millions of files, you need to adapt the database memory
  configuration parameters concerning sorting, joining and global
- memory.  By default, sort and join parameters are very small
+ memory. By default, sort and join parameters are very small
  (sometimes 8Kb), and having sufficient memory specified by those
- parameters is extremely important to run fast.  
+ parameters is extremely important to run fast.
 
  If adjusting your MySQL memory configuration values does not
  solve your problem, you can also consider switching to
  PostgreSQL, which performs much better with Bacula on big
- installations (many millions of files per Job).  However for
+ installations (many millions of files per Job). However for
  large installations, you will also need to adjust the default
  PostgreSQL memory configuration parameters.
 
 from http://www.bacula.org/en/?page=news
 
-POSTGRESQL NOTES
-================
-
-The PostgreSQL Bacula packages are designed to work with PostgreSQL 8.4.
-If you are using an older version, you may need to edit some scripts
-in /etc/bacula/scripts so that it uses the correct version of the
-PostgreSQL binaries.  As it is possible to have multiple PostgreSQL
-versions on a single Debian system, we cannot handle this in a completely
-automated way.
-
 UPGRADES
 ========
 
 Debian packages will, unless you have asked them not to, attempt to
 automatically upgrade your catalog during a major Bacula upgrade.
 
-However, please be sure to examine /usr/share/doc/bacula-common/ReleaseNotes
-for potential changes in the configuration files.
+However, please be sure to examine the Release Notes in
+/usr/share/doc/bacula-common/ for potential changes in the
+configuration files.
 
 CATALOG BACKUPS
 ===============
@@ -194,4 +180,4 @@ http://www.bacula.org.
 
 based on a file by Jose Luis Tallon
 
- -- Carsten Leonhardt <leo at debian.org>, Wed,  3 Aug 2016 21:01:24 +0200
+ -- Carsten Leonhardt <leo at debian.org>, Mon,  5 Sep 2016 17:22:42 +0200
diff --git a/debian/additions/common-functions.dpkg b/debian/additions/common-functions.dpkg
index 247dee1..b0c777d 100644
--- a/debian/additions/common-functions.dpkg
+++ b/debian/additions/common-functions.dpkg
@@ -48,7 +48,7 @@ EOF
 
 
 #
-# Function for substitute variables into template
+# Function to substitute variables into template
 # Usage: substitute <template> <output>
 #
 # will replace all occurance of XXX_var_XXX to value of environment variable `var'
@@ -76,7 +76,7 @@ substitute() {
 
 
 #
-# Function for check if config already registered by the same package for 
+# Function to check if config already registered by the same package for
 # other database type.
 # Usage: config_from_other_dbtype <package> <config>
 #
@@ -95,13 +95,13 @@ config_from_other_dbtype() {
 
 
 #
-# Function for install config file from template
+# Function to install config file from template
 # Usage: install_config <package> <config name> [ <template> ]
 #
 # use substitute() for generate config
 # use config_from_other_dbtype() for force reregister file with ucf
 # install and register generated file with ucf
-# 
+#
 
 install_config() {
   local PACKAGE CONFIG OLD_VERSION TEMPLATE tempfile
@@ -145,7 +145,7 @@ install_config() {
 
 
 #
-# Function for setup /etc/default/*
+# Function to setup /etc/default/*
 # Usage: call from postins script "setup_etc_default <package> $@"
 #
 # if there is fresh install, generate default /etc/default/* file
diff --git a/debian/bacula-fd.postinst b/debian/bacula-fd.postinst
index 5d1231f..3edfc64 100644
--- a/debian/bacula-fd.postinst
+++ b/debian/bacula-fd.postinst
@@ -20,7 +20,7 @@ case "$1" in
 		-e s~XXX_MONFDPASSWORD_XXX~$FDMPASSWD~ \
 		-i $TARGET
 	fi
-    ;; 
+    ;;
 esac
 
 # dh_installdeb will replace this with shell code automatically
@@ -29,5 +29,3 @@ esac
 #DEBHELPER#
 
 exit 0
-
-
diff --git a/debian/bacula-sd.postinst b/debian/bacula-sd.postinst
index cd6bf83..db47d65 100644
--- a/debian/bacula-sd.postinst
+++ b/debian/bacula-sd.postinst
@@ -20,7 +20,7 @@ case "$1" in
 		-e s~XXX_MONSDPASSWORD_XXX~$SDMPASSWD~ \
 		-i $TARGET
 	fi
-   ;;
+    ;;
 esac
 
 # dh_installdeb will replace this with shell code automatically
diff --git a/debian/changelog b/debian/changelog
index 68872f2..d9e3953 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -8,6 +8,7 @@ bacula (7.4.3+dfsg-5) unstable; urgency=medium
   * Cleanup of postinst scripts, safer password handling,
     no longer create unneeded .dist files of config files (Closes: #493092)
   * deleted obsolete code from various places in debian/*
+  * Removed obsolete information from README.Debian
 
  --
 

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-bacula/bacula.git



More information about the pkg-bacula-commits mailing list