Your message dated Fri, 06 Oct 2006 21:47:07 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#363297: fixed in backupninja 0.9.4-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: backupninja
Version: 0.9.3-6
Severity: important
Tags: patch

pgsql handler can't backup to the backupdir because the shell variables are not 
expanded
because the command string is enclosed in ' not ". - my patch changes that and 
adds eval
to the command call.


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (800, 'testing'), (700, 'stable'), (500, 'proposed-updates'), 
(70, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12.6-xen
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages backupninja depends on:
ii  bash                      3.1-4          The GNU Bourne Again SHell
ii  dialog                    1.0-20060221-1 Displays user-friendly dialog boxe
ii  mawk                      1.3.3-11       a pattern scanning and text proces

backupninja recommends no packages.

-- no debconf information


--- pgsql.orig  2006-04-08 23:03:53.000000000 +0200
+++ pgsql       2006-04-18 12:39:04.000000000 +0200
@@ -72,13 +72,13 @@
 # if $databases = all, use pg_dumpall
 if [ "$databases" == "all" ]; then
     if [ $usevserver = yes ]; then
-       execstr='$VSERVER $vsname exec su - postgres -c \"$PGSQLDUMPALL > 
$backupdir/${vsname}.sql\"'
+       execstr="$VSERVER $vsname exec su - postgres -c \"$PGSQLDUMPALL > 
$backupdir/${vsname}.sql\""
     else
-       execstr='su - postgres -c \"$PGSQLDUMPALL > 
$backupdir/${localhost}-all.sql\"'
+       execstr="su - postgres -c \"$PGSQLDUMPALL > 
$backupdir/${localhost}-all.sql\""
     fi
     debug "$execstr"
     if [ ! $test ]; then
-       output=`$execstr 2>&1`
+       output=`eval $execstr 2>&1`
        code=$?
        if [ "$code" == "0" ]; then
            debug $output
@@ -94,13 +94,13 @@
     for db in $databases; do
        if [ $usevserver = yes ]
            then
-           execstr='$VSERVER $vsname exec su - postgres -c \"$PGSQLDUMP $db > 
$backupdir/${db}.sql\"'
+           execstr="$VSERVER $vsname exec su - postgres -c \"$PGSQLDUMP $db > 
$backupdir/${db}.sql\""
        else
-           execstr='su - postgres -c \"$PGSQLDUMP $db > $backupdir/${db}.sql\"'
+           execstr="su - postgres -c \"$PGSQLDUMP $db > $backupdir/${db}.sql\""
        fi
        debug "$execstr"
        if [ ! $test ]; then
-           output=`$execstr 2>&1`
+           output=`eval $execstr 2>&1`
            code=$?
            if [ "$code" == "0" ]; then
                debug $output
                                                                                
                                                                                
                                                                                
                                                                                
                


--- End Message ---
--- Begin Message ---
Source: backupninja
Source-Version: 0.9.4-1

We believe that the bug you reported is fixed in the latest version of
backupninja, which is due to be installed in the Debian FTP archive:

backupninja_0.9.4-1.diff.gz
  to pool/main/b/backupninja/backupninja_0.9.4-1.diff.gz
backupninja_0.9.4-1.dsc
  to pool/main/b/backupninja/backupninja_0.9.4-1.dsc
backupninja_0.9.4-1_all.deb
  to pool/main/b/backupninja/backupninja_0.9.4-1_all.deb
backupninja_0.9.4.orig.tar.gz
  to pool/main/b/backupninja/backupninja_0.9.4.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.
Micah Anderson <[EMAIL PROTECTED]> (supplier of updated backupninja 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: SHA1

Format: 1.7
Date: Fri,  6 Oct 2006 13:04:45 -0600
Source: backupninja
Binary: backupninja
Architecture: source all
Version: 0.9.4-1
Distribution: unstable
Urgency: medium
Maintainer: Micah Anderson <[EMAIL PROTECTED]>
Changed-By: Micah Anderson <[EMAIL PROTECTED]>
Description: 
 backupninja - lightweight, extensible meta-backup system
Closes: 363297 370396 370778 382737 382747
Changes: 
 backupninja (0.9.4-1) unstable; urgency=medium
 .
   * New upstream release (0.9.4)
     . admingroup config option (Closes: #370396)
     . stat call fixes (Closes: #382747)
     . sqldump compress in-line (Closes: #370778)
     . fixed shell expansion (Closes: #363297)
     . fixed src set to the trac repo directly (Closes: #382737)
     . many other fixes, new handlers and changes, see upstream Changelog
   * added AUTHORS to debian/docs
   * debian build changes to change with upstream
   * bumped standards version to current (no changes)
Files: 
 6214157489001fb1d28376d3ebfd9d1e 630 admin optional backupninja_0.9.4-1.dsc
 2b9e0a258785093a0f5a773d9e2c2185 134181 admin optional 
backupninja_0.9.4.orig.tar.gz
 23e73d94946750f2b5645ee34fe6f6d9 9674 admin optional 
backupninja_0.9.4-1.diff.gz
 10f87966dec5584eefc3f92574aace55 73136 admin optional 
backupninja_0.9.4-1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFJy+E9n4qXRzy1ioRAg8fAJ9DJQ8eATBUaAfKkEqbhRoXU7lS9ACgq4g6
n+KyvuenLtp+b6ng/mOJIpA=
=LiF9
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to