> Tar complained unless I added the 'c' but it's still erroring out for me.
> Were you thinking something like this?
>
> tar c --strip-components=4 /home/backup/my_web_server_backups/todays_backup/
>
> There has got to be an easier way to import local data into a backup pool for
> a specific hos
Johan Ehnberg wrote:
To do it directly from directories, you could try changing 'zcat' to
'tar --strip-components=X' and point it at the directory. Set X to match
the number of path components that should not be included for the
archive to make the structure equal to that of the actual host to b
Hi,
Glad to hear!
To do it directly from directories, you could try changing 'zcat' to
'tar --strip-components=X' and point it at the directory. Set X to match
the number of path components that should not be included for the
archive to make the structure equal to that of the actual host to be
On Tue, May 17, 2016 at 11:05 AM, Juergen Harms wrote:
> On 05/17/2016 01:33 PM, Alexander Moisseev wrote:
>> Did you upgrade backuppc from sources or some distribution packages?
>
> From the Mageia distro - there may be an explanation in that. But at
> that time I had been maintainer for BackupP
It worked! Thanks so much for spelling it out for me!
My previous backups are not tar'd so I'm having to first compress them into a
tar.gz to make it work. Is it possible to import them directly from the
(uncompressed) source? Could I change the entry for TarClientCmd from 'zcat' to
'cat'? If s
On 18/05/2016 02:05, Juergen Harms wrote:
> On 05/17/2016 01:33 PM, Alexander Moisseev wrote:
>> Did you upgrade backuppc from sources or some distribution packages?
> From the Mageia distro - there may be an explanation in that. But at
> that time I had been maintainer for BackupPC in Mageia -
On 05/17/2016 01:33 PM, Alexander Moisseev wrote:
> Did you upgrade backuppc from sources or some distribution packages?
From the Mageia distro - there may be an explanation in that. But at
that time I had been maintainer for BackupPC in Mageia - the distro
package was essentially the wrapped o
Thanks Stephen,
comments below.
Il 17/05/2016 16:24, Stephen Joyce ha scritto:
> I'm glad to see the recent energy going into the discussion and planning
> for BackupPC's future. It's great that there's an interest in making sure
> the project stays alive.
The interest is surely here.
> It sound
I'm glad to see the recent energy going into the discussion and planning
for BackupPC's future. It's great that there's an interest in making sure
the project stays alive.
It sounds like there are lots of opinions about how to proceed long-term,
including who the core players will be who have t
Hi Juerghen,
comments below.
Il 17/05/2016 13:15, Juergen Harms ha scritto:
> On 05/17/2016 12:41 PM, Mauro Condarelli wrote:
>> Who should that be? Lars? Juergen?
> Not Juergen - that is against my mid-range "retiring-from-retirement"
> strategy (where BackupPC has already made me add a sawtooth
On 17.05.16 13:59, Juergen Harms wrote:
> On 05/17/2016 12:03 PM, Alexander Moisseev wrote:
>> I believe the current configure.pl implementation updates config.pl
>> automatically. What would you suggest?
>
> I have doubts - but have not looked into it. But I remember that I
> normally had some -
On 05/17/2016 12:41 PM, Mauro Condarelli wrote:
> Who should that be? Lars? Juergen?
Not Juergen - that is against my mid-range "retiring-from-retirement"
strategy (where BackupPC has already made me add a sawtooth function).
Re IRC: once it works, can you suggest a period of time where - normal
On 05/17/2016 12:03 PM, Alexander Moisseev wrote:
> I believe the current configure.pl implementation updates config.pl
> automatically. What would you suggest?
I have doubts - but have not looked into it. But I remember that I
normally had some - very few - lines to change (fewer as backuppc
p
On 05/17/2016 11:35 AM, Alexander Moisseev wrote:
> https://github.com/backuppc/backuppc/compare/v4.0.0
> Does it help?
It does - both for digging into backuppc internals, and for watching git
at work - many thanks!
--
I tried contacting the owner of #backuppc on freenode.
It turns out he does not have a working account anymore, so the channel is
officially orphaned.
Normal procedure should be request transfer of ownership to a new "Founder"
(they stated it should be a single person).
Unless I hear some othe
Hi Juergen,
comments below.
Il 17/05/2016 11:29, Juergen Harms ha scritto:
> On 05/16/2016 08:37 PM, Alexander Moisseev wrote:
>> As FreeBSD sysutils/backuppc port maintainer I can say one of the first
>> thing that should be done is to split up configure.pl in two parts:
>> installation scrip
On 17.05.16 12:29, Juergen Harms wrote:
> I agree that this is a very important issue. Can you also take the
> aspect on board to facilitate the users work when he adapts his
> customization to a new release? I have always found it extremely painful
> to wade through more than 2000 lines of config.
On 17.05.16 12:21, Juergen Harms wrote:
> I will - and I am starting to overcommit. But I start realising that
> this immediate work on creating an efficient platform for the
> contributors to efficiently and sustainably "live" in is top priority
> rather than small fry for later - I will shift the
On 05/16/2016 08:37 PM, Alexander Moisseev wrote:
> As FreeBSD sysutils/backuppc port maintainer I can say one of the first thing
> that should be done is to split up configure.pl in two parts: installation
> script and configuration/update script.
> It's practically impossible to create pre-buil
On 05/17/2016 10:35 AM, Mauro Condarelli wrote:
> Can You take the burden to move to wiki whatever useful from ML? (TiA!)
I will - and I am starting to overcommit. But I start realising that
this immediate work on creating an efficient platform for the
contributors to efficiently and sustainably
Hi Juergen,
comments inline.
Il 17/05/2016 09:33, Juergen Harms ha scritto:
> Mauro and Lars - can you aim at summing up what is emerging to be
> "software management procedures and policies" into a short summary paper?
This is a very good idea.
Lars, please share Your proposal.
> That summary wi
On 16.05.16 22:40, Mauro Condarelli wrote:
> Can You create an issue on github, please?
Done.
> Should we ask for debian maintainer input and/or support?
I believe we should invite debian backuppc package maintainer Ludovic Drolez
not only to discussion on this particular issue, but to the backup
Mauro and Lars - can you aim at summing up what is emerging to be
"software management procedures and policies" into a short summary paper?
That summary will probably end up as a wiki page, but the wiki is not
yet on the list of things to be immediately done. Meanwhile, there must
be an interim
23 matches
Mail list logo
