Your message dated Fri, 13 Oct 2006 17:32:15 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#392525: fixed in backupninja 0.9.4-3
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.4-1
Severity: serious

[EMAIL PROTECTED]:/etc/backup.d>backupninja --now        
Configuration files must not be world writable/readable! Dying on file 
/etc/backup.d

It seems to be confusing the directory with a config file. chmod 770
/etc/backup.d is a workaround.

The backup.d mode has always been 775, and dpkg preserves directory
modes on upgrade, so this breaks upgrades from older versions of
backupninja. Fix would be chmodding the directory on upgrade in the
postinst.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

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

backupninja recommends no packages.

-- no debconf information

-- 
see shy jo

Attachment: signature.asc
Description: Digital signature


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

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-3.diff.gz
  to pool/main/b/backupninja/backupninja_0.9.4-3.diff.gz
backupninja_0.9.4-3.dsc
  to pool/main/b/backupninja/backupninja_0.9.4-3.dsc
backupninja_0.9.4-3_all.deb
  to pool/main/b/backupninja/backupninja_0.9.4-3_all.deb



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: Sat,  7 Oct 2006 19:14:32 -0600
Source: backupninja
Binary: backupninja
Architecture: source all
Version: 0.9.4-3
Distribution: unstable
Urgency: medium
Maintainer: Micah Anderson <[EMAIL PROTECTED]>
Changed-By: Micah Anderson <[EMAIL PROTECTED]>
Description: 
 backupninja - lightweight, extensible meta-backup system
Closes: 392525
Changes: 
 backupninja (0.9.4-3) unstable; urgency=medium
 .
   * Added postinst to fix perms on /etc/backup.d (Closes: #392525)
   * Added fix from upstream to make rub handler work
Files: 
 fff217644e5df4471cb42c5b15cfcc42 631 admin optional backupninja_0.9.4-3.dsc
 2afb0d83f6aa65f27005fd58f0e9de88 10565 admin optional 
backupninja_0.9.4-3.diff.gz
 11a016f93af5b8edf59fb9afa2ef24de 73514 admin optional 
backupninja_0.9.4-3_all.deb

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

iD8DBQFFMDBW9n4qXRzy1ioRAir1AKCJTOqbz5DIVwCsMN6uM6L/Y/ZN+ACgkU+m
lQwUgkf+BoFqnaI1EPHYfdA=
=QpZw
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to