apt VS Duplicacy

And if that's not enough, you yourself seem to have been responsible that exactly this change was added to apt. If I may refresh your memory: https://github.com/pop-os/apt/pull/1 It even links to upstream Debian work mentioning exactly this method: https://salsa.debian.org/apt-team/apt/-/merge_requests/196

And no matter how hard it is, if it's possible to break it, someone will find their way to completely breaking the system. Look at what Linus had to do to break his Pop!_OS install - go to the terminal (which already renders it far out of reach for the average user), run sudo apt install steam, and ignore a giant error. And that wouldn't work anymore anyway, because Pop now uses a version of APT that completely forbids breaking the system unless specifically configured to allow it - so there is now an extra step in there, telling APT not to preserve pop-desktop.

This isn't locking it down. This is about providing sensible defaults like I mentioned before. For power users, the control is still there. It's easy enough to create the `/etc/apt/break-my-system` file so that you can shoot yourself in the foot if you wanted to. This is not similar to what ChromeOS or Android is doing at all.

ah, I thought you mean https://github.com/pop-os/apt/pull/1

- Improve the GUI package manager error message: https://github.com/pop-os/shop/pull/302 - Make the apt message more explicit and make the bypass much harder: https://github.com/pop-os/apt/pull/1

https://github.com/pop-os/apt/pull/1/files Here is the code change. Note line 311.

They have already committed a fix that improves things dramatically.

And they already issued a "fix" to prevent people to easily "break" it.

And their fix for the issue Linus had is downstream only. Not a word said about working with Debian on this.

I have been having great luck with incremental backups with the very similar named Duplicacy https://duplicacy.com/

Pro: No need for a special index database. The chunks are placed in the file system. This explains it in greater detail. Seems to place great emphasis on reliability, which is important for me. Versioning is also supported.

Having all your data in one place isn't wise though, so I am planning on storing encrypted backups on Dropbox and Backblaze B2 using Duplicity so that I am following the 3-2-1 backup rule.

I tried a bunch of different ways but ultimately settled on Duplicacy [0].

It runs inside a Docker container and backs up both my data as well as configurations like my docker compose file and smb.conf.

Off site storage was Backblaze B2, but I moved to Hetzner. Likely will move back just because B2 is cheaper and a bit faster for my region.

Another layer of backup I do is use Duplicacy to backup to a portable hard drive occasionally that I keep off site.

[0] https://duplicacy.com/

Duplicacy

I use Kopia and works well. Have also used this https://duplicacy.com