Mailman 3 July 2025 - Bit-dev

Back In Time 1.3.3-4 -> which *-keyring?
by sawbona＠gmx.net Aug. 11, 2025

Aug. 11, 2025

Hello: My Linux box runs BiT 1.3.3-4, the latest version available in the repositories. [code] $ apt list | grep installed | grep backintime --- snip --- backintime-common/stable,stable,now 1.3.3-4 all [installed] backintime-qt/stable,stable,now 1.3.3-4 all [installed,automatic] $ [/code] Have used it for the longest time, saved my files more than once. Thanks to all those involved for that. That said, I have something to which I need some insight into: 1. I understand that BiT will use whatever available keyring it finds. 2. For reasons, it turns out that my system has more than one keyring available: [code] $ apt list | grep installed | grep keyring --- snip --- debian-archive-keyring/stable,stable,now 2023.3+deb12u2 all [installed] devuan-keyring/stable,stable,now 2023.05.28 all [installed] gnome-keyring/stable,now 42.1-1+b2 amd64 [installed] python3-keyring/stable,stable,now 23.9.3-2 all [installed,automatic] python3-keyrings.alt/stable,stable,now 4.2.0-1 all [installed,automatic] $ [/code] I'm not a fan of gnome 'anything' and as a result I only have one gnome application installed: gnome-disk-utility, which is actually quite handy. Recently, wondering if gnome-keyring was used by gnome-disk-utility, I asked aptitude ... [code] $ aptitude why gnome-keyring i backintime-common Depends python3-keyring i A python3-keyring Depends python3-secretstorage (>= 3.2) i A python3-secretstorage Recommends gnome-keyring | libkf5wallet-bin (>= 5.97) | keepassxc $ [/code] ... only to find out that it is (indirectly) used by backintime-common. ie: backintime-common >depends> python3-keyring >depends> python3-secretstorage >recommends gnome-keyring |or| libkf5wallet-bin (>= 5.97) |or| keepassxc As libkf5wallet-bin seems to be a transitional package which can be removed (if it were installed), the only options for BiT would be gnome-keyring or keepassxc. But it happens that if I purge gnome-keyring, BiT won't work and keepassxs is not installed. Q1: why are gnome-keyring and keepassxc 'recommended' packages and not dependencies? Just asking, seems odd. Q2: how could I safely (and not breaking anything) switch from gnome-keyring to keepassxc? The less gnome I have, the better. Thanks in advance. Best, JHM

3 8

Opinion about restore config dialog
by c.buhtz＠posteo.jp July 26, 2025

July 26, 2025

Hello Folks, I am interested in your opinions. Maybe I simplify this topic to much and miss something. A fresh installed and not configured BIT will ask if you want to restore an existing configuration (from a backup somewhere else). The dialog [1] [2] to select backup folder containing the config that should be restored is the topic here. The dialog shows a directory tree to encourage the user to select the folder containing the config file. I wonder if this dir tree widget is even useful in this context. The dialog runs an extra thread in background search the file system for config files. That thread updates the related tree entries, so that the QLabel below that tree widget can display information of profiles found [1] or if nothing was found [2]. So why not throw away that tree widget and just present the search result of the thread running in the background? The user just need to wait some seconds in the beginning until the search for config files is finished. Maybe add an extra button with a DirSelectDialog behind. It would simplify the code. It would remove the threading logic and tree-model-filterproxy-logic of the tree widget. Any suggestions and thoughts about it? Regards, Christian [1] -- <https://translate.codeberg.org/media/screenshots/bit_dlg_import_config_foun…> [2] -- <https://translate.codeberg.org/media/screenshots/bit_dlg_import_config.png>

3 3

Disabled - Source Code docu at Read The Docs
by c.buhtz＠posteo.jp July 12, 2025

July 12, 2025

Hi, I want to inform and ask for opinions and vetos. On Read The Docs I disabled the automatic build (via Sphinx) of the source code docu [1]. My self I don't use it, not even on my local machine. I am surfing through the original code files. To my knowledge there is also no other developer using it. BIT is an end user application and not a library or package where you need to check how to use the API. Every build of that docu is wasting resources, energy and CO2. Beside the green-thinking, there is also the organization behind Read The Docs. They offer the service for free. As always I am open for opinions and arguments. Best, Christian Buhtz [1] -- <https://backintime-dev.readthedocs.org/>

1 0

Back In Time 1.6.0 is near
by c.buhtz＠posteo.jp July 6, 2025

July 6, 2025

Dear all, The upcoming version 1.6.0 is getting close. All issues, planned for this milestone, have been closed, only a few RPs are pending [1]. One last feature is in the works: support for gocryptfs as a replacement for EncFS. What changed since latest stable release 1.5.5? The major highlight of 1.6.0 will be gocryptfs support, replacing EncFS, which is known to have security flaws [2]. Other major changes: - The command-line interface has been completely reworked. Most commands and switches are now deprecated and replaced. - Terminology changed: what used to be called a "snapshot" is now a "backup". - Minimum required Python version increased to 3.11. - Many other features and fixes are listed in the CHANGELOG [3]. Under the hood A lot of code was refactored and cleaned up. Extensive testing is necessary and required before release. I encourage you to test the latest dev branch and would highly appreciate any feedback or bug reports. Some git metrics, comparing latest "dev" with latest release "v1.5.5": - 106 commits - 175 files changed - 55.086 insertions, 45.169 deletions Thank you to all persons contributing feedback, ideas, bug reports and solutions. Best regards, Christian Buhtz [1] -- <https://github.com/bit-team/backintime/milestone/34> [2] -- <https://github.com/bit-team/backintime/issues/1734> [3] -- <https://github.com/bit-team/backintime/blob/dev/CHANGES>

1 0