Mailman 3 March 2023 - Bit-dev

Diagnostics information in debug output
by c.buhtz＠posteo.jp 17 Mar '23

17 Mar '23

Hello Folks, I realized that our nice "--diagnostics" output is not integrated by default in BIT. But my opinion is it should be. But the original JSON output (see at the end of this mail) is a bit to much I would say. But I'm not sure. I'm interested in your opinions. For the "--debug" output I would use the log format like this: DEBUG: [...] Diagnostics - "backintime" name: "Back In Time" version: "1.3.3-dev" .... DEBUG: [...] Diagnostics - "host-setup" platform: ... DEBUG: [...] Diagnostics - "python-setup" python: ... sys-path: "/usr/...", "/usr/..." DEBUG: [...] Diagnostics - "external-programs" rsync: ... I assume this can be realized with less code. Any suggestions about it? Here is an example of diagnostic output in JSON format. { "backintime": { "name": "Back In Time", "version": "1.3.3-dev", "latest-config-version": 6, "local-config-file": "/home/UsernameReplaced/.config/backintime/config", "local-config-file-found": true, "global-config-file": "/etc/backintime/config", "global-config-file-found": false, "started-from": "/usr/share/backintime/common", "running-as-root": false, "user-callback": "/home/UsernameReplaced/.config/backintime/user-callback", "keyring-supported": true }, "host-setup": { "platform": "Linux-5.10.0-21-arm64-aarch64-with-glibc2.31", "system": "Linux #1 SMP Debian 5.10.162-1 (2023-01-21)", "os-release": "Debian GNU/Linux 11 (bullseye)", "display-system": "x11", "locale": "de_DE, UTF-8", "PATH": "/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games", "RSYNC_OLD_ARGS": "(not set)", "RSYNC_PROTECT_ARGS": "(not set)" }, "python-setup": { "python": "3.9.2 default Feb 28 2021 17:03:44 CPython GCC 10.2.1 20210110", "python-executable": "/usr/bin/python3", "python-executable-symlink": true, "python-executable-resolved": "/usr/bin/python3.9", "sys.path": [ "/usr/share/backintime/qt/plugins", "/usr/share/backintime/common/plugins", "/usr/share/backintime/plugins", "/usr/share/backintime/common", "/usr/lib/python39.zip", "/usr/lib/python3.9", "/usr/lib/python3.9/lib-dynload", "/usr/local/lib/python3.9/dist-packages", "/usr/lib/python3/dist-packages", "/usr/lib/python3.9/dist-packages" ], "qt": "PyQt 5.15.2 / Qt 5.15.2" }, "external-programs": { "rsync": "3.2.3", "ssh": "OpenSSH_8.4p1 Debian-5+deb11u1, OpenSSL 1.1.1n 15 Mar 2022", "sshfs": "3.7.1", "encfs": "1.9.5", "shell": "/bin/bash", "shell-version": "GNU bash, Version 5.1.4(1)-release (aarch64-unknown-linux-gnu)" } }

2 2

Milestones and priorities
by c.buhtz＠posteo.jp 16 Mar '23

16 Mar '23

Hello Folks, I have to apologize. I started to use the Milestones feature of Microsoft GitHubs Issue section. I did this because I like the progress bars in the milestones. ;) Then I remembered that we still have priority tags (low, medium, high). This is a bit interfering, I know. So I stopped with the milestones and would like to discuss. My intention was to have nice looking progress bar and to reference the issues to something like a roadmap or timeplan. Time is relative! I created just three broad milestones. 1. One for the next release (1.3.4) within the next 6 to 18 months. 2. One for the release after the next release (6-24 months). 3. One for far away features that might be implemented or maybe never will be implemented (24 months and further). The time and dates are not fix. It is just a number. And I assume that 2 and 3 can be divided into smaller and more granulated milestones as the development progress. Sidenote: There is still an exception coming up. Depending on how Debian reacts on the Issue #1410 (keyring stuff) we might do a new point release (1.3.4) in the next days. That fast it can go. ;) I'm interested in your thoughts. Kind Christian

2 1

Ubuntu 22.04 LTS : Rsync bug
by c.buhtz＠posteo.jp 15 Mar '23

15 Mar '23

Hello Folks, just for your information. The rsync package in Ubuntu 22.04 LTS was updated from 3.2.3 to 3.2.7. This triggers the known and still fixed rsync-incompatibility bug [1] in Back In Time because BIT in Ubuntu 22.04 LTS still is quit old and not able to handle the "new argument protection" introduced with rsync 3.2.4. It seems that rsync itself doesn't follow Semantic Versioning. It was a big change of behavior and should have been a minor update (Version number 3.3 instead of 3.2.4). On the other site the Ubuntu folks should have read the changelog more carefully. At the end currently BIT is "broken" [2] in Ubuntu 22.04. The solution is to use BIT from upstream repo or PPA. Or using the workaround described in the bug [1]. I opened a question about update policy at Ubuntu rsync [3] and also informed the rsync upstream maintainer about the situation. Kind Christian [1] -- <https://github.com/bit-team/backintime/issues/1247> [2] -- <https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2009756> [3] -- <https://answers.launchpad.net/ubuntu/+source/rsync/+question/705772>

2 2