Bug#887490: BackupPC 4.x and BackupPC 3.3.2 (was: Re: Offering my help to be part of team)
Hi Tobias,
Tobias Frost wrote:
> Team created:
> https://tracker.debian.org/teams/pkg-backuppc/
Thanks! Joined.
BTW, the repo looks like a git-buildpackage style repo, so I assume
it's safe to use gbp for it.
> I wonder if we want to have a new (e.g backuppc4) src package to have
> the old and new one parallel for some time... What do you think?
Good question. I tent to say yes, but probably only for buster. (It
might be too short to get backuppc4 in shape for buster.)
Next question is if we want separate repositories or just separate
branches. I tend to separate repositories.
I feel well-versed enough in Perl and dynamic web pages to provided
fixes for potential security issues in BackupPC 3.x, so upstream
possibly not providing any support anymore should be ok-ish.
P.S.: There seems to be a last 3.3.2 upstream release from Jan. 2017:
https://github.com/backuppc/backuppc/releases/tag/3.3.2
https://backuppc.github.io/backuppc/BackupPC-3.3.2.html
Seems to mostly fix things we already ship as patches. IMHO we should
at least import that for the generation 3 packages. Won't be able to
do that this evening anymore, though, at least not properly with
testing, etc.
Regards, Axel
--
,''`. | Axel Beckert <abe@debian.org>, 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
Reply to: