You are not logged in.

#1 2026-08-15 12:48:11

buhtz
Member
Registered: 2022-08-24
Posts: 27
Website

Back In Time 2.0.0 - Release Candidate 1

The first release candidate for Back In Time 2.0.0 is out.

It is the largest update in the project's history: major config refactoring, rewritten mount subsystem, Gocryptfs replacing EncFS, and removal of deprecated features.

Please test it and report results, also when you find no regressions.

⚠️ Use a VM or separate "--config" option. This RC might break your current config.

Back In Time is an rsync based backup GUI for GNU Linux. It is an open source project, without a vendor or company behind.


Member of upstream maintenance Teams of Back In Time

Offline

#2 2026-08-15 13:04:37

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,512

Re: Back In Time 2.0.0 - Release Candidate 1

For clarity : you are the maintainer of back in time ?

Out of curiosity : are there plans to move the project away from github ?


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#3 2026-08-15 13:33:25

buhtz
Member
Registered: 2022-08-24
Posts: 27
Website

Re: Back In Time 2.0.0 - Release Candidate 1

Hello Wolf,
thank you for the question.

Lone_Wolf wrote:

For clarity : you are the maintainer of back in time ?

Yep, I am the maintainer. Currently I am the only one.

Lone_Wolf wrote:

Out of curiosity : are there plans to move the project away from github ?

Absofuckinglutely, yes!

It is a matter of resources and priorities. Maybe after this 2.0.0 release or next year after Debian 14 released.

See also this FAQ entry and our strategy outline about this topic.

Myself I still have some projects at Codeberg.org.

2.0.0 is quit unstable because I refactored or re-wrote more than half of the codebase. I really hope to get some test feedback from the community before bringing it into the wild.

Best,
Christian


Member of upstream maintenance Teams of Back In Time

Offline

#4 2026-09-27 03:31:33

baltic
Member
Registered: 2017-07-17
Posts: 17

Re: Back In Time 2.0.0 - Release Candidate 1

Lone_Wolf wrote:

are there plans to move the project away from github ?


Whats wrong with github?

Offline

#5 2026-09-27 19:07:29

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,512

Re: Back In Time 2.0.0 - Release Candidate 1

Most of my issues with github are not suited for discussion on archlinux forum.

Apart from those it runs on proprietary closed code and overtime has become more and more hostile towards opensource projects (often deleting them outright without due process).


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#6 2026-09-27 19:10:06

baltic
Member
Registered: 2017-07-17
Posts: 17

Re: Back In Time 2.0.0 - Release Candidate 1

Lone_Wolf wrote:

overtime has become more and more hostile towards opensource projects (often deleting them outright without due process).

And what are the alternatives?

Offline

#7 2026-09-27 19:19:23

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,512

Re: Back In Time 2.0.0 - Release Candidate 1

That depends entirely on what one needs from a git hoster.

[1] and [2] should give you some idea what's available . If you want more info please start a separate thread.


[1] https://itsfoss.com/github-alternatives/
[2] https://european-alternatives.eu/alternative-to/github


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#8 2026-09-27 19:35:08

baltic
Member
Registered: 2017-07-17
Posts: 17

Re: Back In Time 2.0.0 - Release Candidate 1

Lone_Wolf wrote:

That depends entirely on what one needs from a git hoster.

Alas, gitlab, for example:
1. Doesn't have docker in its automation. So you can't really automate whatever test release process you want.
2. Is not googlable. Projects there will have really poor discoverability.

I bet if you try using whatever else from the list, you will quickly hit some annoying limitations. So i thought maybe you have some first hand experience with some of them and can recommend from it. But anyway, its off topic already.

Offline

Board footer

Powered by FluxBB