Mailman 3 September 2024 - Bit-dev

Does someone manage (un)mounting via user-callback scripts?
by c.buhtz＠posteo.jp Sept. 24, 2024

Sept. 24, 2024

Hello, Does someone of you manage mounting and unmouting via user-callback scripts and provide this as an example? Or can someone imagine a possible use case where it would make sense do manage mounting via user-callback script? But without root rights. Thanks Christian

2 1

User-callback example scripts: Where to store them?
by c.buhtz＠posteo.jp Sept. 23, 2024

Sept. 23, 2024

Hello, I would like to integrate the "user-callback" repo into the "backintime" repo. There are some example scripts in that repo. The question is where they should be stored in the "backintime" repo. Currently there is the folder "doc/manual" containing the user manual. That manual will also include a section about user-callback. So it might be a good idea to store the example scripts inside it; e.g. "doc/manual/user-callback-examples". Or another location? We also do have an open Debian bug report asking for that scripts to being installed somewhere. Where should they go on a Debian system? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985257 What do you think? Thank you for your opinions and input. Christian

2 1

Error '"com.ubuntu.DeviceDriver.PermissionDeniedByPolicy: net.launchpad.backintime.UdevRuleSave"
by yctct＠yctct.com Sept. 22, 2024

Sept. 22, 2024

Hi Bit maintainers, In Backintime GUI, when I click on the folder icon under 'Where to save snapshots' in the 'General' of Main Profile[3], an error message pop ups in small window: com.ubuntu.DeviceDriver.PermissionDeniedByPolicy: net.launchpad.backintime.UdevRuleSave I saw the error was already reported by a user on the repository[1]. Also, aryoda wrote: > It would also be helpful to post this log output here (for other users > with the same problem to find this issue and because I am curious ;-) Here is the output of journalctl: $ journalctl --since "30 minute ago" | grep -i backintime [...] Sep 22 10:29:35 redacted python3[2345]: backintime-qt (redacted/1): ERROR: Failed to get crontab lines: 1, no crontab for redacted Sep 22 10:29:35 redacted python3[2345]: backintime-qt (redacted/1): ERROR: com.ubuntu.DeviceDriver.PermissionDeniedByPolicy: net.launchpad.backintime.UdevRuleSave [...] I also reported the error to Trisquel GNU/Linux maitainers. I use Trisquel. https://trisquel.info/en/forum/backintime-error-when-i-try-update-snapshot-… $ backintime -v backintime 1.2.1 $ uname -a Linux x220 5.15.0-121-generic #131+11.0trisquel30 SMP Sun Sep 15 21:38:45 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux Let me know if more information would be useful to you. Roman https://github.com/bit-team/backintime/issues/1719

2 1

Migrating to Codeberg?
by Mark Johnno Sept. 19, 2024

Sept. 19, 2024

Hello bit maintainers & contributors, would migrating to Codeberg from Github be a possibility? I was a bit reluctant to ask this question because I am not a maintainer, and this decision belongs to the maintainers, that said, I have reported some bugs and feedback via Github's issue in the past - and I am really appreciated the responses and questions from maintainers. I no longer can do so because I deleted my Github account. I am no longer confortable using Github (i.e. a proprietary software running on the servers of a privately owned company). I would be confortable again to report (small) hiccups I see (BiT works really well overall) if the repository was hosted on the server of non-profit, for example Codeberg e.V., running a copyleft-licensed software, e.g. Forgejo. If you are wondering what the migration takes, this https://docs.codeberg.org/advanced/migrating-repos/ documents how to migrate from Github to Codeberg (or any other Gitea/Forgejo instances). There is a feature to migrate Issues ("the migration tool can not only migrate your repository data, but also metadata like issues, labels, wiki, releases, milestones, etc"). Again, I imagine the decision belongs to maintainers. Please take this email as an input to the conversation on whether BiT should migrate away from Github.

2 2

"Cannot render with an inactive painter" ?
by c.buhtz＠posteo.jp Sept. 17, 2024

Sept. 17, 2024

Hello, Does someone still experience the error "Cannot render with an inactive painter" in Back In Time version 1.3.4 or higher? The question is in relation to that issue. https://github.com/bit-team/backintime/issues/1404 Issue can be closed if the error is gone. Best, Christian

1 0

Request to review PR "Reset cached SSH password when changed" (#1859)
by c.buhtz＠posteo.jp Sept. 15, 2024

Sept. 15, 2024

Hello Folks, There is an open but read to merge pull request I would like to have reviewed by someone else. David Wales improved the behavior around cached SSH passwords. Because I am not much into that topic I would be glad if someone else could have a look on it before I am merging it. The PR https://github.com/bit-team/backintime/pull/1859 Related Issue https://github.com/bit-team/backintime/issues/1852 Thanks in advance, Christian Buhtz

1 0

New user manual
by c.buhtz＠posteo.jp Sept. 12, 2024

Sept. 12, 2024

Hello Folks, with a lot of help from Kosta Vukicevic (stcksmsh) I am in the middle of migrating our user manual from "Sphinx" to "MkDocs" build system. Please see this (test) URL for the new manual: https://backintime-buhtz.readthedocs.io And in comparison this current (old) one: https://backintime.readthedocs.io The content has not changed yet, just the layout and the build system. The advantage is that MkDocs is easier to handle from the perspective as an author (markdown based, live preview via local webserver) and maintainer. It is also an opportunity to move the manual repository "bit-team/doc" into the main repository "bit-team/backintime". The new manual instance is currently build from "buhtz/backintime" repo's branch "RTDmkdocs". When the setup is final we can start to integrate new content in the manual. Let me know what you think about it? Best, Christian Buhtz

2 1

Why is host/user/profile in the snapshot path?
by c.buhtz＠posteo.jp Sept. 10, 2024

Sept. 10, 2024

Hello, the values "host", "user" and "profile" are not fixed in the settings/manage profiles dialog, but they are always used in the snapshot path. Does someone has an idea why it is that way? Is there a technical reason we this needs to be done? Would it hurt, if this fields would just disappear? Ignore backwards compatibility for this question. Related issues: "Allow customisation of the backup location path" <https://github.com/bit-team/backintime/issues/1795> "Allow disabling of Host/User/Profile etc nesting" <https://github.com/bit-team/backintime/issues/1304> Best, Christian Buhtz

3 3