Re: [BackupPC-devel] BackupPC 4.1.0 released

Richard, No, as the error message says, you can't run configure.pl directly from git. You need to run makeDist first, which merges some important settings (the list of libraries and binaries, as well as the release version and date) into configure.pl. Once you test it and confirm it works I'll r

Re: [BackupPC-devel] BackupPC 4.1.0 released

On 28.03.2017 16:32, Richard Shaw wrote: > You need to run makeDist first to create a tarball release that includes an > updated configure.pl . After you unpack the tarball, > run configure.pl from > there. It is not possible to apply a source code patc

Re: [BackupPC-devel] BackupPC 4.1.0 released

On Mon, Mar 27, 2017 at 5:29 PM, Craig Barratt < cbarr...@users.sourceforge.net> wrote: > Richard, > > I just pushed several fixes to configure.pl. Now if you specify > --dest-dir, any existing BackupPC installation should be ignored (ie, no > need to specify --config-path '' any longer). > > I a

Re: [BackupPC-devel] BackupPC 4.1.0 released

Richard, I just pushed several fixes to configure.pl. Now if you specify --dest-dir, any existing BackupPC installation should be ignored (ie, no need to specify --config-path '' any longer). I also fixed the PingPath and Ping6Path merging, and noticed a couple of other things that are now fixed

Re: [BackupPC-devel] BackupPC 4.1.0 released

On Mon, Mar 27, 2017 at 2:22 PM, Craig Barratt < cbarr...@users.sourceforge.net> wrote: > Richard, > > If I take that command, and add > > --config-path '' > > then it ignores the current installation and seems to run correctly. > That got it! Thanks Craig Richard --

Re: [BackupPC-devel] BackupPC 4.1.0 released

Richard, If I take that command, and add --config-path '' then it ignores the current installation and seems to run correctly. Craig On Sun, Mar 26, 2017 at 7:20 AM, Richard Shaw wrote: > On Sun, Mar 26, 2017 at 12:19 AM, Craig Barratt < > cbarr...@users.sourceforge.net> wrote: > >> In looki

Re: [BackupPC-devel] BackupPC 4.1.0 released

On 3/26/17 6:30 PM, Richard Shaw wrote: > On Sun, Mar 26, 2017 at 10:08 AM, Alexander Moisseev > wrote: > > But you have specified --config-dir instead of --config-path . > > Probably https://github.com/backuppc/backuppc/pull/79 >

Re: [BackupPC-devel] BackupPC 4.1.0 released

On Sun, Mar 26, 2017 at 10:08 AM, Alexander Moisseev wrote: > > But you have specified --config-dir instead of --config-path . > > Probably https://github.com/backuppc/backuppc/pull/79 would help with > your issue if you have to use --config-dir . > Perhaps... I tried just changing the dir to pa

Re: [BackupPC-devel] BackupPC 4.1.0 released

On 3/26/17 5:20 PM, Richard Shaw wrote: > On Sun, Mar 26, 2017 at 12:19 AM, Craig Barratt > mailto:cbarr...@users.sourceforge.net>> > wrote: > > In looking a the code, if config-path is specified then any current > config file is ignored. > > If you specify dest-dir then all of the out

Re: [BackupPC-devel] BackupPC 4.1.0 released

On Sun, Mar 26, 2017 at 12:19 AM, Craig Barratt < cbarr...@users.sourceforge.net> wrote: > In looking a the code, if config-path is specified then any current config > file is ignored. > > If you specify dest-dir then all of the output files are put below there. > > So if you specify both --config

Re: [BackupPC-devel] BackupPC 4.1.0 released

In looking a the code, if config-path is specified then any current config file is ignored. If you specify dest-dir then all of the output files are put below there. So if you specify both --config-path '' and --dest-dir, I believe any existing install should be ignored. Craig On Sat, Mar 25,

Re: [BackupPC-devel] BackupPC 4.1.0 released

--On Saturday, March 25, 2017 9:58 PM -0700 Craig Barratt wrote: > I'm not sure how you are using configure.pl to build a package. > > In any case, what I meant was you should try adding --config-path '' to > the existing configure.pl arguments. Is that enough to have it ignore any > existing i

Re: [BackupPC-devel] BackupPC 4.1.0 released

Yes, IncrLevel is no longer used in 4.x. But rather than add a bogus setting to config.pl, it would be better to fix the init script so that it doesn't enforce a condition that is no longer true for 4.x. Craig On Sat, Mar 25, 2017 at 7:35 PM, Bill Broadley wrote: > > I upgraded two backuppc se

Re: [BackupPC-devel] BackupPC 4.1.0 released

I'm not sure how you are using configure.pl to build a package. In any case, what I meant was you should try adding --config-path '' to the existing configure.pl arguments. Is that enough to have it ignore any existing installation?w Craig On Sat, Mar 25, 2017 at 7:15 PM, Richard Shaw wrote:

Re: [BackupPC-devel] BackupPC 4.1.0 released

I upgraded two backuppc servers (both ubuntu 14.04) so far with: 1) cpan install BackupPC::XS 2) manual install of rsync-bpc (./configure --prefix=/opt/pkg/rsync- bpc-; make; make install 3) then just ran the backuppc configure script (and mention the path for rsync-bpc) It "just worked", exc

Re: [BackupPC-devel] BackupPC 4.1.0 released

On Sat, Mar 25, 2017 at 8:18 PM, Craig Barratt < cbarr...@users.sourceforge.net> wrote: > Do you mean an option to configure.pl to ignore an existing install? > > Have you tried doing this: > > ./configure.pl --config-path '' > > (that's 2 single quotes to create an empty --config-path). It shoul

Re: [BackupPC-devel] BackupPC 4.1.0 released

Do you mean an option to configure.pl to ignore an existing install? Have you tried doing this: ./configure.pl --config-path '' (that's 2 single quotes to create an empty --config-path). It should prompt for the config.pl path, and just hit enter. Craig On Sat, Mar 25, 2017 at 6:06 AM, Richar

Re: [BackupPC-devel] BackupPC 4.1.0 released

On 3/25/17 4:06 PM, Richard Shaw wrote: > Craig, > > Thanks for the new release! I'm working on updating the Fedora package now. > > One question though... How hard would it be to add a "--ignore-install" > option? > > I've been trying to test my package on my desktop but I also build the > pa

Re: [BackupPC-devel] BackupPC 4.1.0 released

Craig, Thanks for the new release! I'm working on updating the Fedora package now. One question though... How hard would it be to add a "--ignore-install" option? I've been trying to test my package on my desktop but I also build the package on my desktop so I keep having to uninstall the packag