Thanks everybody for the continued consideration of this question. It's
encouraging that there seems to be some interest and appetite for a
slightly more demonstrably maintained version of BackupPC that might
provide releases in response to fixes for published CVEs in its
dependencies etc.
Since we are new to this community, we'll leave it to others to
determine the best direction of travel for enabling new releases to be
issued. But if something can be put in place we would be interested to
participate further with some minor developments (UI tweaks etc.) that
we've been considering. But in the first instance a new release, just
so that we can point to a 2025 version, would certainly help!
On 01/06/2025 02:07, backu...@kosowsky.org wrote:
[You don't often get email from backu...@kosowsky.org. Learn why this is
important at https://aka.ms/LearnAboutSenderIdentification ]
Caution: This sender is from outside of Quintessa. Do not click links or open
attachments unless you recognise the sender and know the content is safe.
Indeed.
I think the most urgent need for a "maintainer" now would be to
validate and merge in existing patches as well as to potentially
update the source relying on rsync (even though technically not
necessary as pointed out by G.W. Haywood).
[It's pretty easy to do as I have in the past pulled in new versions
for my own private builds though one would of course need to test it
again for each version to make sure nothing breaks]
Beyond that I don't think much regular maintenance activity is
required as the program is otherwise rock-solid.
Having an ongoing maintainer would also at least serve as a point of
reference and approval for any future patches -- whether they be
updates, bug fixes, or code extensions.
Mr. Haywood -- it is certainly very generous of you to step up and
agree to maintain a "fork".
Has anyone heard from Craig over the past couple of years because if
he is around, it would be good to get his blessing. Even better if in
lieu of Craig maintaining active ownership, he would invite
G.W. Haywood plus minus/others to serve as co-maintainers of the
existing branch rather than "forcing" a fork.
Kenneth Porter wrote at about 16:27:57 -0700 on Friday, May 30, 2025:
> --On Friday, May 30, 2025 7:04 PM +0100 "G.W. Haywood"
> <bac...@jubileegroup.co.uk> wrote:
>
> > Maybe the best I could offer would be to fork the project on Github and
> > undertake to maintain the fork. Could that help you?
>
> It might be worthwhile to bring in the people who package BackupPC for
> various distros to create a "packaging" fork that merges all the patches
> that they bave to do anyway.
>
>
>
> _______________________________________________
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki: https://github.com/backuppc/backuppc/wiki
> Project: https://backuppc.github.io/backuppc/
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
--
Dr Steven J Benbow BSc MSc PhD CMath MIMA
Quintessa Ltd, The Hub, 14 Station Road, Henley-on-Thames, Oxfordshire, RG9
1AY, UK
Tel: 01491 636246 DD: 01491 630051 Web: http://www.quintessa.org
Quintessa Limited is an employee-owned company registered in England, Number
3716623.
Registered office: Quintessa Ltd, The Hub, 14 Station Road, Henley-on-Thames,
Oxfordshire, RG9 1AY, UK
If you have received this e-mail in error, please notify priv...@quintessa.org
and delete it from your systems. Our privacy and other policies are available
from https://www.quintessa.org/about-us/policies
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
