Your message dated Fri, 09 Mar 2012 13:02:12 +0000
with message-id <[email protected]>
and subject line Bug#567553: fixed in backup-manager 0.7.10.1-1
has caused the Debian Bug report #567553,
regarding backup-manager: config file problems after upgrade
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
567553: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567553
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: backup-manager
Version: 0.7.9-1
Severity: normal
This bug report is related to #567477. In that bug report I am
quoting an error message:
/etc/cron.daily/backup-manager:
When validating the configuration file /etc/backup-manager.conf, 1
warnings were found.
In the same bug report, the configuration of backup-manager is
reported as follows:
-- debconf information:
backup-manager/upload-key:
backup-manager/name-format: long
backup-manager/upload-hosts:
backup-manager/upload-user-ftp:
backup-manager/cron_frequency: daily
backup-manager/cron_d_remove_deprecated: false
backup-manager/blacklist: /var/archives
backup-manager/time-to-live: 5
backup-manager/burning-maxsize: 650
backup-manager/encryption_recipient:
backup-manager/transfert_mode: scp
backup-manager/dump_symlinks: false
backup-manager/upload-user-scp: bmngr
backup-manager/burning-device: /dev/cdrom
backup-manager/upload-dir: /var/archives/uploads
backup-manager/enable_encryption: false
* backup-manager/directories: /home/mbelow
* backup-manager/repo_group: root
backup-manager/filetype: tar.gz
* backup-manager/repo_user: root
* backup-manager/backup-repository: /var/archives
backup-manager/burning-method: CDRW
backup-manager/burning-enabled: false
backup-manager/want_to_upload: false
This is not what was set in /etc/backup-manager.conf at that time.
For me it looks like the config file is not read, maybe because of
the warning, and debconf uses some kind of defaults for its report.
I had changed the config file by hand, but AFAIK it was correct (it worked).
The actual config file was:
# Backup Manager Configuration File
#
# * This configuration file is divided into sections.
# The 'global' section is mandatory, every keys defined in
# this section are inherited in the other sections.
# * There is one section per "backup method", you have to
# fill the section of the chosen method.
#
##############################################################
##############################################################
# Repository - everything about where archives are
#############################################################
# Where to store the archives
export BM_REPOSITORY_ROOT="/var/archives"
# Where to place temporary files
export BM_TEMP_DIR="/tmp"
# For security reasons, the archive repository and the generated
# archives will be readable/writable by a given user/group.
# This is recommended to set this to true.
export BM_REPOSITORY_SECURE="true"
# The repository will be readable/writable only by a specific
# user:group pair if BM_REPOSITORY_SECURE is set to true.
export BM_REPOSITORY_USER="root"
export BM_REPOSITORY_GROUP="root"
# You can also choose the permission to set the repository, default
# is 770, pay attention to what you do there!
export BM_REPOSITORY_CHMOD="770"
##############################################################
# Archives - let's focus on the precious tarballs...
##############################################################
# Each archive generated will be chmoded for security reasons
# (BM_REPOSITORY_SECURE should be enabled for this).
export BM_ARCHIVE_CHMOD="660"
# Number of days we have to keep an archive (Time To Live)
export BM_ARCHIVE_TTL="5"
# Do you want to purge only the top-level directory or all
# directories under BM_REPOSITORY_ROOT?
export BM_REPOSITORY_RECURSIVEPURGE="false"
# Do you want to replace duplicates by symlinks?
# (archive-DAY is a duplicate of archive-(DAY - 1) if they
# are both the same according to MD5 hashes).
export BM_ARCHIVE_PURGEDUPS="true"
# Prefix of every archive on that box (default is HOSTNAME)
export BM_ARCHIVE_PREFIX="$HOSTNAME"
# Should we purge only archives built with $BM_ARCHIVE_PREFIX
export BM_ARCHIVE_STRICTPURGE="true"
# You may want to nice the commands run for archive-creation
# (Recommanded for desktop users.)
# Choose a nice level from -20 (most favorable scheduling) to 19 (least
favorable).
export BM_ARCHIVE_NICE_LEVEL="10"
# The backup method to use.
# Available methods are:
# - tarball
# - tarball-incremental
# - mysql
# - svn
# - pipe
# - none
# If you don't want to use any backup method (you don't want to
# build archives) then choose "none"
export BM_ARCHIVE_METHOD="tarball"
##############################################################
# Encryption - because you cannot trust the place your
# archives are
##############################################################
# If you want to encrypt your archives locally, Backup Manager
# can use GPG while building the archive (so the archive is never
# written to the disk without being encrypted.
# Note: this feature is only possible with the following archive types:
# tar, tar.gz, tar.bz2
# Uncomment the following line if you want to enable encryption
# available method: gpg
export BM_ENCRYPTION_METHOD="false"
# The encryption will be made using a GPG ID
# Examples:
# export BM_ENCRYPTION_RECIPIENT=""
# export BM_ENCRYPTION_RECIPIENT=""
export BM_ENCRYPTION_RECIPIENT=""
##############################################################
# Section "TARBALL"
# - Backup method: tarball
#############################################################
# Archive filename format
# long : host-full-path-to-folder.tar.gz
# short : parentfolder.tar.gz
export BM_TARBALL_NAMEFORMAT="long"
# Type of archives
# Available types are:
# tar, tar.gz, tar.bz2, tar.lz, dar, zip.
# Make sure to satisfy the appropriate dependencies
# (bzip2, dar, lzma, ...).
export BM_TARBALL_FILETYPE="dar"
# You can choose to build archives remotely over SSH.
# You will then need to fill the BM_UPLOAD_SSH variables
# (BM_UPLOAD_SSH_HOSTS, BM_UPLOAD_SSH_USER, BM_UPLOAD_SSH_KEY).
# If this boolean is set to true, archive will be saved locally (in
# BM_REPOSITORY_ROOT but will be built by the remote host).
# Thus, BM_TARBALL_DIRECTORIES will be used to backup remote directories.
# Those archive will be prefixed with the remote host name.
export BM_TARBALL_OVER_SSH="false"
# Do you want to dereference the files pointed by symlinks ?
# enter true or false (true can lead to huge archives, be careful).
export BM_TARBALL_DUMPSYMLINKS="false"
# Targets to backup
# You can use two different variables for defining the targets of
# your backups, either a simple space-separated list (BM_TARBALL_DIRECTORIES)
# or an array (BM_TARBALL_TARGETS[]).
# Use the first one for simple path that doesn't contain spaces in their name.
# Use the former if you want to specify paths to backups with spaces.
# It's recommanded to use BM_TARBALL_TARGETS[] though.
# Warning! You *must not* use both variables at the same time.
# NOTE: The Debian package will only update BM_TARBALL_DIRECTORIES
# Paths without spaces in their name:
export BM_TARBALL_DIRECTORIES="/home/mbelow"
# If one or more of the targets contain a space, use the array:
# declare -a BM_TARBALL_TARGETS
# BM_TARBALL_TARGETS[0]="/etc"
# BM_TARBALL_TARGETS[1]="/boot"
# export BM_TARBALL_TARGETS
# Files to exclude when generating tarballs, you can put absolute
# or relative paths, Bash wildcards are possible.
export BM_TARBALL_BLACKLIST="/home/mbelow/temp /home/mbelow/.recoll"
# With the "dar" filetype, you can choose a maximum slice limit.
export BM_TARBALL_SLICESIZE="4100M"
# Extra options to append to the tarball generation
# (take care to what you do; this will be silently added to the
# command line.)
export BM_TARBALL_EXTRA_OPTIONS=""
##############################################################
# The tarball-incremental method uses the same keys as the
# tarball method, plus two others.
#############################################################
# Which frequency to use for the master tarball?
# possible values: weekly, monthly
export BM_TARBALLINC_MASTERDATETYPE="weekly"
# Number of the day, in the BM_TARBALLINC_MASTERDATETYPE frequency
# when master tarballs should be made
export BM_TARBALLINC_MASTERDATEVALUE="5"
# Examples: you want to make master tarballs every friday:
# BM_TARBALLINC_MASTERDATETYPE="weekly"
# BM_TARBALLINC_MASTERDATEVALUE="5"
#
# Or every first day of the month:
# BM_TARBALLINC_MASTERDATETYPE="monthly"
# BM_TARBALLINC_MASTERDATEVALUE="1"
##############################################################
# Backup method: MYSQl
#############################################################
# This method is dedicated to MySQL databases.
# You should not use the tarball method for backing up database
# directories or you may have corrupted archives.
# Enter here the list of databases to backup.
# Wildcard: __ALL__ (will dump all the databases in one archive)
export BM_MYSQL_DATABASES="__ALL__"
# The best way to produce MySQL dump is done by using the "--opt" switch
# of mysqldump. This make the dump directly usable with mysql (add the drop
table
# statements), lock the tables during the dump and other things.
# This is recommended for full-clean-safe backups, but needs a
# privileged user (for the lock permissions).
export BM_MYSQL_SAFEDUMPS="true"
# The user who is allowed to read every databases filled in BM_MYSQL_DATABASES
export BM_MYSQL_ADMINLOGIN="root"
# its password
export BM_MYSQL_ADMINPASS=""
# the host where the database is
export BM_MYSQL_HOST="localhost"
# the port where MySQL listen to on the host
export BM_MYSQL_PORT="3306"
# which compression format to use? (gzip or bzip2)
export BM_MYSQL_FILETYPE="bzip2"
##############################################################
# Backup method: svn
#############################################################
# Absolute paths to the svn repositories to archive
export BM_SVN_REPOSITORIES=""
# You can compress the resulting XML files
# Supported compressor are: bzip2 and gzip
export BM_SVN_COMPRESSWITH="bzip2"
##############################################################
# Backup method: pipe
#############################################################
# The "pipe" method is a generic way of making archive.
# Its concept is simple, for every kind of archive you want
# to make, you give: a command which will send output on stdout,
# a name, a file type and optionnaly, a compressor.
# Be careful, this feature uses arrays!
declare -a BM_PIPE_COMMAND
declare -a BM_PIPE_NAME
declare -a BM_PIPE_FILETYPE
declare -a BM_PIPE_COMPRESS
# You can virtually implement whatever backup scenario you like
# with this method.
#
# The resulting archives will be named like this:
# $BM_ARCHIVE_PREFIX-$BM_PIPE_NAME.$DATE.$BM_PIPE_FILETYPE
# If you specified a BM_PIPE_COMPRESS option, the resulting filename
# will change as expected (eg, .gz if "gzip").
#
# Here are a couple of examples for using this method:
# Archive a remote MySQL database through SSH:
# BM_PIPE_COMMAND[0]="ssh host -c \"mysqldump -ufoo -pbar base\""
# BM_PIPE_NAME[0]="base"
# BM_PIPE_FILETYPE[0]="sql"
# BM_PIPE_COMPRESS[0]="gzip"
# This will make somthing like: localhost-base.20050421.sql.gz
# Archive a specific directory, on a remote server through SSH:
# BM_PIPE_COMMAND[0]="ssh host -c \"tar -c -z /home/user\""
# BM_PIPE_NAME[0]="host.home.user"
# BM_PIPE_FILETYPE[0]="tar.gz"
# BM_PIPE_COMPRESS[0]=""
# This will make somthing like: localhost-host.home.user.20050421.tar.gz
export BM_PIPE_COMMAND
export BM_PIPE_NAME
export BM_PIPE_FILETYPE
export BM_PIPE_COMPRESS
##############################################################
# Section "UPLOAD"
# You can upload archives to remote hosts with different
# methods.
#############################################################
# Which method to use for uploading archives, you can put
# multiple methods here.
# Available methods:
# - scp
# - ssh-gpg
# - ftp
# - rsync
# - s3
# - none
# If you don't want to use any upload method (you don't want to
# upload files to remote hosts) then choose "none"
export BM_UPLOAD_METHOD=""
# where to upload (global to all methods. Not required to be set for S3)
export BM_UPLOAD_HOSTS=""
# Where to put archives on the remote hosts (global)
export BM_UPLOAD_DESTINATION=""
##############################################################
# The SSH method
#############################################################
# the user to use for the SSH connections/transfers
export BM_UPLOAD_SSH_USER=""
# The private key to use for opening the connection
export BM_UPLOAD_SSH_KEY=""
# specific ssh hosts
export BM_UPLOAD_SSH_HOSTS=""
# port to use for SSH connections (leave blank for default one)
export BM_UPLOAD_SSH_PORT=""
# destination for ssh uploads (overrides BM_UPLOAD_DESTINATION)
export BM_UPLOAD_SSH_DESTINATION=""
# purge archives on remote hosts before uploading?
export BM_UPLOAD_SSH_PURGE="true"
# If you set BM_UPLOAD_SSH_PURGE, you can specify a time to live
# for archives uploaded with SSH.
# This can let you use different ttl's locally and remotely
# By default, BM_ARCHIVE_TTL will be used.
export BM_UPLOAD_SSH_TTL=""
##############################################################
# The SSH-GPG method
# The ssh-gpg method uses the same configuration keys as the
# ssh method, plus one other
#############################################################
# The gpg public key used for encryption, this can be a short
# or long key id, or a descriptive name. See gpg man page for
# all possibilities how to specify a key.
export BM_UPLOAD_SSHGPG_RECIPIENT=""
##############################################################
# The FTP method
#############################################################
# Use FTP secured transfers (FTP over TLS)
# User, password and data will be uploaded encrypted with SSL.
# Passive mode will be automaticaly activated
export BM_UPLOAD_FTP_SECURE="false"
# Do you want to use FTP passive mode?
# This is mandatory for NATed/firewalled environments
export BM_UPLOAD_FTP_PASSIVE="true"
# the user to use for the FTP connections/transfers
export BM_UPLOAD_FTP_USER=""
# the FTP user's password
export BM_UPLOAD_FTP_PASSWORD=""
# FTP specific remote hosts
export BM_UPLOAD_FTP_HOSTS=""
# purge archives on remote hosts before uploading?
export BM_UPLOAD_FTP_PURGE="true"
# You can specify a time to live for archives uploaded with FTP
# This can let you use different ttl's locally and remotely
# By default, BM_ARCHIVE_TTL will be used.
export BM_UPLOAD_FTP_TTL=""
# destination for FTP uploads (overrides BM_UPLOAD_DESTINATION)
export BM_UPLOAD_FTP_DESTINATION=""
##############################################################
# The S3 method
#############################################################
# The Amazon S3 method requires that you secure an S3
# account. See http://aws.amazon.com
# The bucket to upload to. This bucket must be dedicated to backup-manager
export BM_UPLOAD_S3_DESTINATION=""
# the S3 access key provided to you
export BM_UPLOAD_S3_ACCESS_KEY=""
# the S3 secret key provided to you
export BM_UPLOAD_S3_SECRET_KEY=""
# purge archives on remote hosts before uploading?
export BM_UPLOAD_S3_PURGE="false"
##############################################################
# The RSYNC method
#############################################################
# Which directories should be backuped with rsync
export BM_UPLOAD_RSYNC_DIRECTORIES=""
# Destination for rsync uploads (overrides BM_UPLOAD_DESTINATION)
export BM_UPLOAD_RSYNC_DESTINATION=""
# The list of remote hosts, if you want to enable the upload
# system, just put some remote hosts here (fqdn or IPs)
# Leave it empty if you want to use the hosts that are defined in
# BM_UPLOAD_HOSTS
export BM_UPLOAD_RSYNC_HOSTS=""
# Do you want to dereference the files pointed by symlinks?
# enter true or false (true can lead to huge archives, be careful).
export BM_UPLOAD_RSYNC_DUMPSYMLINKS="false"
##############################################################
# Section "BURNING"
# - Automatic CDR/CDRW/DVDR burning
#############################################################
# the method of burning archives from the list :
# - DVD : burn archives on a DVD medium
# (that doesn't need formatting, like DVD+RW).
#
# - DVD-RW : blank the DVD medium and burn archives
# (recommanded for DVD-RW media).
#
# - CDRW : blank the CDRW and burn the whole
# ARCHIVES_REPOSITORY or only
# the generated archives.
#
# - CDR : burn the whole ARCHIVES_REPOSITORY or
# only the generated archives.
# - none : disable the burning system
export BM_BURNING_METHOD="DVD"
# When the CD is burnt, it is possible to check every file's
# MD5 checksum to see if the CD is not corrupted.
export BM_BURNING_CHKMD5="true"
# The device to use for mounting the cdrom
export BM_BURNING_DEVICE="/dev/dvd"
# You can force cdrecord to use a specific device
# Fill in the full path to the device to use or even
# e.g. BM_BURNING_DEVFORCED="/dev/cdrom"
# If none specified, the default cdrecord device will be used.
export BM_BURNING_DEVFORCED=""
# By default backup-manager will make Joliet media (using the mkisofs switches
# : "-R -J"). You can change these if you want to use non-Joliet disc images.
# Change this only if you know what you're doing. Refer to mkisofs(8) for
# details.
export BM_BURNING_ISO_FLAGS="-R -J"
# enter here the max size of your media
# (usal sizes are 4200 for DVD media and 700 or 800 for CDR media)
export BM_BURNING_MAXSIZE="4200"
##############################################################
# Advanced settings, use this with care.
#############################################################
# Every output made can be sent to syslog
# set this to "true" or "false"
export BM_LOGGER="true"
# You can choose which facility to use
export BM_LOGGER_FACILITY="user"
# Enter here some shell script.
# It will be executed before the first action of backup-manager.
export BM_PRE_BACKUP_COMMAND=""
# Enter here some shell script.
# It will be executed after the last action of backup-manager.
export BM_POST_BACKUP_COMMAND=""
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages backup-manager depends on:
ii debconf [debconf-2.0] 1.5.28 Debian configuration management sy
ii findutils 4.4.2-1 utilities for finding files--find,
ii ucf 3.0025 Update Configuration File: preserv
backup-manager recommends no packages.
Versions of packages backup-manager suggests:
ii anacron 2.3-14 cron-like program that doesn't go
ii backup-manager-doc 0.7.9-1 documentation package for Backup M
ii dar 2.3.9-2 Disk ARchive: Backup directory tre
ii dvd+rw-tools 7.1-6 DVD+-RW/R tools
ii genisoimage 9:1.1.10-1 Creates ISO-9660 CD-ROM filesystem
ii gettext-base 0.17-8 GNU Internationalization utilities
ii libfile-slurp-perl 9999.13-1 single call read & write file rout
ii libnet-amazon-s3-perl 0.52-1 Amazon S3 Perl API - Simple Storag
ii openssh-client 1:5.2p1-2 secure shell (SSH) client, for sec
ii perl 5.10.1-9 Larry Wall's Practical Extraction
ii wodim 9:1.1.10-1 command line CD/DVD writing tool
ii zip 3.0-1 Archiver for .zip files
-- debconf information:
backup-manager/upload-key:
* backup-manager/name-format: long
backup-manager/upload-hosts:
backup-manager/upload-user-ftp:
* backup-manager/cron_frequency: weekly
backup-manager/cron_d_remove_deprecated: false
* backup-manager/blacklist: /home/mbelow/temp /home/mbelow/.recoll
* backup-manager/time-to-live: 8
* backup-manager/burning-maxsize: 4200
backup-manager/encryption_recipient:
backup-manager/transfert_mode: scp
* backup-manager/dump_symlinks: false
backup-manager/upload-user-scp: bmngr
* backup-manager/burning-device: /dev/dvd
backup-manager/upload-dir: /var/archives/uploads
* backup-manager/enable_encryption: false
* backup-manager/directories: /home/mbelow
* backup-manager/repo_group: root
* backup-manager/filetype: dar
* backup-manager/repo_user: root
* backup-manager/backup-repository: /var/archives
* backup-manager/burning-method: DVD
* backup-manager/burning-enabled: true
* backup-manager/want_to_upload: false
--- End Message ---
--- Begin Message ---
Source: backup-manager
Source-Version: 0.7.10.1-1
We believe that the bug you reported is fixed in the latest version of
backup-manager, which is due to be installed in the Debian FTP archive:
backup-manager-doc_0.7.10.1-1_all.deb
to main/b/backup-manager/backup-manager-doc_0.7.10.1-1_all.deb
backup-manager_0.7.10.1-1.debian.tar.gz
to main/b/backup-manager/backup-manager_0.7.10.1-1.debian.tar.gz
backup-manager_0.7.10.1-1.dsc
to main/b/backup-manager/backup-manager_0.7.10.1-1.dsc
backup-manager_0.7.10.1-1_all.deb
to main/b/backup-manager/backup-manager_0.7.10.1-1_all.deb
backup-manager_0.7.10.1.orig.tar.gz
to main/b/backup-manager/backup-manager_0.7.10.1.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sven Joachim <[email protected]> (supplier of updated backup-manager package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Wed, 07 Mar 2012 19:08:15 +0100
Source: backup-manager
Binary: backup-manager backup-manager-doc
Architecture: source all
Version: 0.7.10.1-1
Distribution: unstable
Urgency: low
Maintainer: Sven Joachim <[email protected]>
Changed-By: Sven Joachim <[email protected]>
Description:
backup-manager - command-line backup tool
backup-manager-doc - documentation package for Backup Manager
Closes: 491199 567553 602633 608237 610413 637743 638803 638920 655985 659162
Changes:
backup-manager (0.7.10.1-1) unstable; urgency=low
.
[ Sven Joachim ]
* New upstream release (Closes: #655985).
- Adds a new "postgresql" backup method (Closes: #637743).
* Remove the fragile translation-updates.diff patch. Instead, backup
the upstream po files before the build and restore them in the clean
target (Closes: #602633).
* Depend on perl (via ${perl:Depends}), rather than than suggesting it,
since perl is required by backup-manager-purge (LP: #941919).
* Drop the debian-perl-location.diff patch, setting PERL5DIR in
debian/rules instead.
* Refresh the remaining Debian patches.
* Fill out the same "Language:" header in debian/po/*.po.
* Drop findutils dependency, even the version in Etch is new enough.
* Upgrade Standards-Version to 3.9.3, no changes needed.
* Update lintian override for Lintian 2.5.
* Update debian/watch to find the 0.7.10.1 release tarball.
* Add build-indep and (empty) build-arch targets to debian/rules.
* Update Vcs-* fields in debian/control, switching to collab-maint.
* Fix a few typos in the debconf templates, thanks to Daniele Forsi
for the report.
* Update README.Debian, the Amazon S3 upload method not longer needs
libfile-slurp-perl (see #491199).
* Demote the priority of the repo_user/repo_group debconf templates to
medium.
* Update debian/copyright.
.
[ Georgios M. Zarkadas ]
* Add Greek debconf translation.
* Allow absolute paths in BM_TARBALL_BLACKLIST even when backing up
the root (/) directory (Closes: #608237).
* Fix missed archive uploads when backups are crossing the day
limit (Closes: # 638803).
* Provide a configuration option to record all uploaded archives in
a single text database file (Closes: #638920).
* Fix upstream makefile to make the build/clean process of gettext (po)
files idempotent and bring sanity back to the package's build process.
* Fix a security issue in pgsql backup method regarding the .pgpass
file handling.
* Add support for local unix sockets connections to the pgsql backup method.
* Add existence check for pg_dumpall to the pgsql backup method.
* Use the same naming convention for database methods generated archives.
* Add myself to Uploaders.
* Add cron script to remove old entries from uploaded archives database.
* Update control file to reflect upstream fix of Amazon S3 uploading
method's dependencies (Closes: #491199).
* Fix missed warnings when BM_LOGGER* variables are undefined or wrongly
configured (Closes: #567553).
* Change configurator to dynamically update BM_TARBALL_BLACKLIST when
user selections change during configuration (Closes: #610413).
* Add backtracking support to the configurator.
.
[ Sven Joachim, Georgios M. Zarkadas ]
* Switch source format to 3.0 (quilt).
- Drop debian/README.source.
* Change debian/rules to use the generic 'dh$@' rule plus overrides.
.
[ Joe Dalton ]
* Add Danish debconf translation (Closes: #659162).
Checksums-Sha1:
52102a178a9a5c99d031b2be7f1a756f7c441d90 2193 backup-manager_0.7.10.1-1.dsc
a08768acff444275c3b33e35a808280106060641 150963
backup-manager_0.7.10.1.orig.tar.gz
e54e17f9a6ff9a78bb983f6d9f1653f1f9ac19b8 75326
backup-manager_0.7.10.1-1.debian.tar.gz
b959bc66c6b042ce36240bc3f9a2dc0e367fca3f 159432
backup-manager_0.7.10.1-1_all.deb
db61174d7f10f7a06d7e5c90c6e29772486523b1 234504
backup-manager-doc_0.7.10.1-1_all.deb
Checksums-Sha256:
bcf6a886a56bf649734293a6729642b762cbfa4d5cebb3ab56892d2a34561995 2193
backup-manager_0.7.10.1-1.dsc
16994520d3fded41e166d17c946405dd192acf960603044aa6c915465e78d41f 150963
backup-manager_0.7.10.1.orig.tar.gz
46b68be7b01a990c5e9a869d7fcf7d2f7ae82d5dd614210d66f5342db45faaac 75326
backup-manager_0.7.10.1-1.debian.tar.gz
b701261e84675312ba11b9a6204698b42be333c4ba31b41cd50728bf64a60621 159432
backup-manager_0.7.10.1-1_all.deb
f09760ba85ad0716f4ca37e20c630a76db5912f78779a45d673a80de8dbaf323 234504
backup-manager-doc_0.7.10.1-1_all.deb
Files:
e1e1cbd3b3ed95849724296c81bbc390 2193 admin optional
backup-manager_0.7.10.1-1.dsc
b7f1e6ecfb6c45116e9aef2de92ffb12 150963 admin optional
backup-manager_0.7.10.1.orig.tar.gz
6c36718a802ebea270f79a162a9dab10 75326 admin optional
backup-manager_0.7.10.1-1.debian.tar.gz
626a3bd130e39ac359c0d98240026396 159432 admin optional
backup-manager_0.7.10.1-1_all.deb
6efe622a55bb99d2701966eb2e23d5b8 234504 doc optional
backup-manager-doc_0.7.10.1-1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJPWf2oAAoJEMcZdpmymyMqGWEQAJ+XQDnWcjnvTlPA7U1TQpOz
L4H45lB5N0w9pkxORnxw6qG9KU1FZFtdtiFUNqEsNFYdN4h6FI/NL9Un5xMh6Zhb
ApMKftW5BVdLaXqW0Wr+y0+ejeeZDmr/3DACGqQgKFEelna6It2bp4UeNQEqSRdZ
EH2LldQNCw5nhsJt9WDoXofyjTPA3jiD9BpYal9PXoRKWuFRTvWBB1GTm5mi5LCB
M92IhvELpd1TEG3eC4OHLI1gaQsHe9n6G2sPBSU7VGbSkCUBfjXBG4iAUPAcQO+G
eFAt0Yfml/6o76Q762OJN27/0c7LmwS3WwzhDGYbpL1nWIBiscbK2Aw2CzrtY58r
IOw0nLOUolj04PmfF9Mgs39EVrxxr4teix3hyBuxnuga2Ftih/NH3hT8Zb9Y+TA4
umeSKu0DRCNuRAMfaGS+iKaqSnpTFlp4P1hynNkPcVptY6fhqfpGuOLHZrkr9kmF
IK8Tue561mFQNUqx/AqOiNMs46xlDy7kci/zrLIUhjKnZ7QMEtiNTqqewz6YUZfD
jZWHioJIFSHTLCuiILDdFGrW01o9a/Rt/kNJmn6xCJfQ3j1iuKEwVWSWKOy1JQo/
sUL5SJzuPKl3WKYvy7DOFKd5JIOVMLubtNpeg5LMoEBs/Tobmuj0hbjOAtAkwzvW
WOjEZGO/1zC7FbWL+ZlE
=OHCS
-----END PGP SIGNATURE-----
--- End Message ---
