Bug#887490: O: backuppc -- high-performance, enterprise-grade system for backing up PCs

[Tobias Frost]

Package: wnpp
Followup-For: Bug #887490
Control: retitle -1 ITA: backuppc -- high-performance, enterprise-grade system 
for backing up PCs
Control: owner -1 team+pkg-backu...@tracker.debian.org

Dear all,

We're intending to adopt this package for collaborative packaging of
BackupPC. For that we've created a packging team, you can find the team page
at: https://tracker.debian.org/teams/pkg-backuppc/
(just add yourself to the team if you want to get involved in
maintaining BackupPC.)

Cheers,
tobi

Bug#887490: O: backuppc -- high-performance, enterprise-grade system for backing up PCs

[Ludo]

Hi !
Good to see that you'll take care of BackupPC ;) 
Do not forget that I have some wip stuff here that might help: 
https://github.com/ldrolez

Regards,
Ludovic 

Le 3 septembre 2018 10:45:15 GMT+02:00, Axel Beckert  a écrit :
>Hi Raoul,
>
>Raoul Bhatia wrote:
>> I've tried to keep some up2date packages in my Github repositories,
>> see
>> https://github.com/backuppc/backuppc/wiki/Build-Your-Own-Packages ,
>> specifically
>> 
>> * https://github.com/raoulbhatia/rsync-bpc/tree/3.0.9.12-DEBIAN
>> * https://github.com/raoulbhatia/backuppc/tree/DEBIAN
>> * https://github.com/raoulbhatia/backuppc-xs/tree/DEBIAN
>
>Thanks for these!
>
>> Would this help to get things back in shape?
>
>I'm sure it will. I haven't looked at them, but since the hint to your
>packages in
>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873075#35 my plan is
>to look at them and try to do a Debian QA upload based on them.
>
>I though don't have my Debian Testing based BackupPC server in shape
>yet, so I can't test it currently.
>
>Once I managed to do this, I intent to look into making a QA upload of
>BackupPC to at least get it back in shape. Or maybe first a simple 3.x
>upload to unstable to get a few things fixed and then upload 4.x to
>experimental first. (JFTR: This should though not keep anyone from
>doing this before I get to it! I do not claim this bug.)
>
>It's though not my top priority at the moment, so I don't want make
>any promises I may not be able to keep.
>
>> Especially, I am no Debian expert and also have basic requirements
>> for BackupPC only, so I will not be able to do this properly all by
>> myself.
>
>I'd join and help if anyone wants to form a BackupPC team in Debian.
>I'm though not keen on taking the lead.
>
>   Regards, Axel
>-- 
>,''`.  |  Axel Beckert ,
>https://people.debian.org/~abe/
>: :' :  |  Debian Developer, ftp.ch.debian.org Admin
>`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
>  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

-- 
Envoyé de mon téléphone Android avec K-9 Mail. Excusez la brièveté.
-- 
Envoyé de mon téléphone Android avec K-9 Mail. Excusez la brièveté.

Bug#887490: O: backuppc -- high-performance, enterprise-grade system for backing up PCs

[Axel Beckert]

Hi Raoul,

Raoul Bhatia wrote:
> I've tried to keep some up2date packages in my Github repositories,
> see
> https://github.com/backuppc/backuppc/wiki/Build-Your-Own-Packages ,
> specifically
> 
> * https://github.com/raoulbhatia/rsync-bpc/tree/3.0.9.12-DEBIAN
> * https://github.com/raoulbhatia/backuppc/tree/DEBIAN
> * https://github.com/raoulbhatia/backuppc-xs/tree/DEBIAN

Thanks for these!

> Would this help to get things back in shape?

I'm sure it will. I haven't looked at them, but since the hint to your
packages in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873075#35 my plan is
to look at them and try to do a Debian QA upload based on them.

I though don't have my Debian Testing based BackupPC server in shape
yet, so I can't test it currently.

Once I managed to do this, I intent to look into making a QA upload of
BackupPC to at least get it back in shape. Or maybe first a simple 3.x
upload to unstable to get a few things fixed and then upload 4.x to
experimental first. (JFTR: This should though not keep anyone from
doing this before I get to it! I do not claim this bug.)

It's though not my top priority at the moment, so I don't want make
any promises I may not be able to keep.

> Especially, I am no Debian expert and also have basic requirements
> for BackupPC only, so I will not be able to do this properly all by
> myself.

I'd join and help if anyone wants to form a BackupPC team in Debian.
I'm though not keen on taking the lead.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#887490: O: backuppc -- high-performance, enterprise-grade system for backing up PCs

[Raoul Bhatia]

Hi!

I've tried to keep some up2date packages in my Github repositories, see 
https://github.com/backuppc/backuppc/wiki/Build-Your-Own-Packages , 
specifically


* https://github.com/raoulbhatia/rsync-bpc/tree/3.0.9.12-DEBIAN
* https://github.com/raoulbhatia/backuppc/tree/DEBIAN
* https://github.com/raoulbhatia/backuppc-xs/tree/DEBIAN

Would this help to get things back in shape?  Especially, I am no Debian 
expert and also have basic requirements for BackupPC only, so I will not 
be able to do this properly all by myself.


Raoul

On Thu, 18 Jan 2018 21:12:43 +0100 Axel Beckert  wrote:

Hi,

Ludovic Drolez wrote:
> Due to lack of time, I intend to orphan the backuppc package.


Thanks for recognizing such issues yourself and for doing the
orphaning yourself!


> Maintaining this package requires time and skills. Please only adopt this
> package if you will have enough time and attention to work on it.

I agree here and that's why I won't adopt it alone.

I'm nevertheless very interested in getting the package back in shape
and would join a team of people interested in team-maintaining
backuppc (and probably libbackuppc-xs-perl, too, see
https://bugs.debian.org/887491).

So if nobody else shows up soon-ish for joining a potential team, I
might start fixing issues doing a QA upload, getting the packaging up
to current standards, fixing long-standing trivial issues like e.g.
https://bugs.debian.org/488098 and creating a packaging git repository
under https://salsa.debian.org/debian i.e. the collab-maint successor
on Salsa. (Packaging 4.x.y versions is very likely not included in
such a first step.)

JFTR: I'm a BackupPC user and admin for more than 15 years now (in
personal as well as professional surroundings), it's in most cases my
primary backup system, and I'm even brave enough to run one soon-to-be
production instance on Debian Testing. :-)

Regards, Axel
--
 ,''`.  |  Axel Beckert , 
https://people.debian.org/~abe/

: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

--
DI (FH) Raoul Bhatia M.Sc.
E-Mail. ra...@bhatia.at
Tel. +43 699 10132530

Bug#887490: O: backuppc -- high-performance, enterprise-grade system for backing up PCs

[Ludovic Drolez]

On Thu, Jan 18, 2018 at 09:12:43PM +0100, Axel Beckert wrote:
> > Maintaining this package requires time and skills. Please only adopt this
> > package if you will have enough time and attention to work on it.
> 
> I agree here and that's why I won't adopt it alone.

Hi !

Yes, I was on the way to upload backuppc v4, but it was too much work
for me... 
I've packaged backuppc-rsync, which is a modified rsync for backuppc v4,
and uploaded it but it was rejected because of copyright issues.
I may try to upload it again before orphaning it...
The source for it is here: https://github.com/ldrolez/backuppc-rsync

Some of the Debian bugs are in fact fixed in v4, that's why I was
working on it.

There's still lots of problem caused by latest samba packages, and
I think that they can only be fixed with patches in smbclient.

Best regards,

-- 
Ludovic Drolez.

https://www.aopensource.com - The Android Open Source Portal
https://www.drolez.com - Personal site - Linux and Free Software
https://chezsandro.com - A cool place in Cape Verde :)

Bug#887491: Bug#887490: O: backuppc -- high-performance, enterprise-grade system for backing up PCs

[Axel Beckert]

Hi,

Ludovic Drolez wrote:
> Due to lack of time, I intend to orphan the backuppc package.


Thanks for recognizing such issues yourself and for doing the
orphaning yourself!


> Maintaining this package requires time and skills. Please only adopt this
> package if you will have enough time and attention to work on it.

I agree here and that's why I won't adopt it alone.

I'm nevertheless very interested in getting the package back in shape
and would join a team of people interested in team-maintaining
backuppc (and probably libbackuppc-xs-perl, too, see
https://bugs.debian.org/887491).

So if nobody else shows up soon-ish for joining a potential team, I
might start fixing issues doing a QA upload, getting the packaging up
to current standards, fixing long-standing trivial issues like e.g.
https://bugs.debian.org/488098 and creating a packaging git repository
under https://salsa.debian.org/debian i.e. the collab-maint successor
on Salsa. (Packaging 4.x.y versions is very likely not included in
such a first step.)

JFTR: I'm a BackupPC user and admin for more than 15 years now (in
personal as well as professional surroundings), it's in most cases my
primary backup system, and I'm even brave enough to run one soon-to-be
production instance on Debian Testing. :-)

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#887490: O: backuppc -- high-performance, enterprise-grade system for backing up PCs

[Ludovic Drolez]

Package: wnpp
Severity: normal

Due to lack of time, I intend to orphan the backuppc package.
Maintaining this package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

Ludovic


The package description is:
 BackupPC is disk based and not tape based. This particularity allows
 features not found in any other backup solution:
  * Clever pooling scheme minimizes disk storage and disk I/O.
Identical files across multiple backups of the same or different PC are
stored only once resulting in substantial savings in disk storage and disk
writes. Also known as "data deduplication".
  * Optional compression provides additional reductions in storage.
CPU impact of compression is low since only new files (those not already
in the pool) need to be compressed.
  * A powerful http/cgi user interface allows administrators to view log files,
configuration, current status and allows users to initiate and cancel
backups and browse and restore files from backups very quickly.
  * No client-side software is needed. On WinXX the smb protocol is used.
On Linux or Unix clients, rsync or tar (over ssh/rsh/nfs) can be used
  * Flexible restore options. Single files can be downloaded from any backup
directly from the CGI interface. Zip or Tar archives for selected files
or directories can also be downloaded from the CGI interface.
  * BackupPC supports mobile environments where laptops are only intermittently
connected to the network and have dynamic IP addresses (DHCP).
  * Flexible configuration parameters allow multiple backups to be performed
in parallel.
  * and more to discover in the manual...