Your message dated Mon, 14 Feb 2011 14:23:24 +0100
with message-id <[email protected]>
and subject line Fixed in 0.10-1
has caused the Debian Bug report #607796,
regarding Should include "lvs=/sbin/lvs" option in default /etc/mylvmbackup.conf
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.)
--
607796: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607796
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mylvmbackup
Version: 0.9-1
Severity: normal
Tags: patch
Option "lvs=" is not included in default /etc/mylvmbackup.conf
If you launch backupfrom a root shell, it makes no difference, because /sbin
is in root's path. But if you launch it from a cron job, it fails with te
following error:
't exec "lvs": No existe el fichero o el directorio at /usr/bin/mylvmbackup
line 734 (#1)
(W exec) A system(), exec(), or piped open call could not execute the
named program for the indicated reason. Typical reasons include: the
permissions were wrong on the file, the file wasn't found in
$ENV{PATH}, the executable in question was compiled for another
architecture, or the #! line in a script points to an interpreter that
can't be run for similar reasons. (Or maybe your system doesn't support
#! at all.)
Use of uninitialized value $lv in substitution (s///) at
/usr/bin/mylvmbackup
line 736 (#1)
(W uninitialized) An undefined value was used as if it were already
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.
To suppress this warning assign a defined value to your variables.
To help you figure out what was undefined, perl will try to tell you the
name of the variable (if any) that was undefined. In some cases it
cannot
do this, so it also tells you what operation you used the undefined
value
in. Note, however, that perl optimizes your program and the operation
displayed in the warning may not necessarily appear literally in your
program. For example, "that $foo" is usually optimized into "that "
. $foo, and the warning will refer to the concatenation (.) operator,
even though there is no . in your program.
Use of uninitialized value $lv in substitution (s///) at
/usr/bin/mylvmbackup
line 737 (#1)
This option will be the same for nearly all Debian users and cases, so it
should be put by default in configuration file.
-- System Information:
Debian Release: 5.0.7
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages mylvmbackup depends on:
ii libconfig-inifiles-perl 2.39-5 Read .ini-style configuration file
ii libdbd-mysql-perl 4.007-1+lenny1 A Perl5 database interface to the
ii libtimedate-perl 1.1600-9 Time and date functions for Perl
ii lvm2 2.02.39-8 The Linux Logical Volume Manager
mylvmbackup recommends no packages.
Versions of packages mylvmbackup suggests:
ii mysql-server 5.0.51a-24+lenny4 MySQL database server (metapackage
ii mysql-server-5.0 [mysq 5.0.51a-24+lenny4 MySQL database server binaries
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.10-1
This issue was fixed upstream in 0.10.
--- End Message ---
