Mailman 3 September 2022 - Bit-dev

Quick setup of VMs (virtual machines) for issue testing
by J. A. 18 Sep '22

18 Sep '22

Can someone recommend a quick and secure (= reliable image sources) way of downloading and running ready-to-use VM images to test issues reported on different Linux distros and version? I am currently using Gnome Boxes on Ubuntu 20.04 which must be installed via snap (the apt version is to old and has many broken download links to no longer existing VM Images)...

5 28

Automatically validate docstrings incl. Sphinx python domain directives and roles ("markup language")
by J. A. 16 Sep '22

16 Sep '22

During my development of https://github.com/bit-team/backintime/pull/1295 I had to modify a docstring and include references to other functions which can be done by via Sphinx roles, eg.: Args: cfg: A config created via :py:func:`config.Config()` or :py:func:`getConfig()` If would be great to validate these cross references automatically via TravisCI, a new make target or somehow else since generating the Sphinx doc and viewing the formatted doc manually is time consuming (and boring ;-) Could we add this to the TODO list + collect solution proposals?

2 3

Changelog
by Michael Büker 11 Sep '22

11 Sep '22

Hey all, I've been committing some of your fine fixes, and at some point in the future, we will hopefully make new releases. Which got me thinking: Should I pay closer attention to keeping a changelog? Surely, when it's time for a new release Somday Soon™, I can just look back through the commit history and use GitHub to compare the current codebase to the 1.3.2 release label, right? Is that enough, or should we be taking notes on the side or something? Cheers :) Michael

7 17

Discussion on whole-system backups with BiT
by Michael Büker 11 Sep '22

11 Sep '22

Hi everyone, there's a question that seems to come up in GitHub Issues rather frequently: Can BackInTime be used to make a whole-system backup, including /dev, boot code, tmpfs mountpoints etc.? In my opinion, that's out of scope for backintime, and it would be a neverending game of catch-up with distributions to try and support this functionality (not to mention a nightmare for testing). I've discussed this in a recently close Issue (https://github.com/bit-team/backintime/issues/1211), and though I'd share my arguments here, because this is a recurring topic: > The main goals/unique benefits of backintime (as I understand them) > are: > > 1. to make the most of the powers of `rsync` in order to create > incremental > backups, > 2. to provide a convenient and powerful graphical interface for > browsing past snapshots and restoring from them, > 3. and to store the backed up files in their original form and > directory > structure in a sane and easy-to-navigate set of folders, making it > possible to > restore from backup even without the backintime software itself. > > This is a whole other game from complete-system backups, which need to > deal > with special mountpoints, device files, boot code etc. Take a look at > [TimeShift](https://github.com/linuxmint/timeshift), though, it may be > just > what you're looking for, and from what I understand, it can even be > used > sensibly in combination with backintime. Cheers, Michael

4 4

Sphinx: Missing doc for test_*.py
by c.buhtz＠posteo.jp 11 Sep '22

11 Sep '22

Hello, as Hakan explained I generate the API reference docu via cd common/doc-dev && make html It seems to me that the py-files in common/test/* are ignored. But I can't find an ignore directive in the conf.py (IMHO the central Sphinx config file). Can someone help here? Another tiny wish: Can we add Graphviz based inheritance diagrams in that docu? Kind Christian

3 3

Rfc: Introduce OS labels for issues
by J. A. 10 Sep '22

10 Sep '22

How about introducing operating system labels for issues so that I could easier find other issues that I could test and possibly fix on virtual machine that I have set up? The label should contain the OS major version IMHO since this is typically important to reproduce issues...

3 2

Local unittests with lot of fails/warnings
by c.buhtz＠posteo.jp 09 Sep '22

09 Sep '22

Hello, I tried to run pytest (via "./configure && make test") on my local repo. 148 failed, 155 passed, 53 skipped, 21 warnings Ok, some tests are skipped maye because of a missing SSH setup. But this doesn't explain everything. Some questions to that. Two questions about that? 1. Is someone able (except "Travis") to get all tests passed on a local repo? 2. Can I setup the make-pytest-thing in a way that the hugh output is logged into a file?

2 9

Setup Travis in my fork
by c.buhtz＠posteo.jp 08 Sep '22

08 Sep '22

Hello, I tried to setup Travis for my forked "backintime". I created a "free" account at travis, clicked on the activation link in the email. I can see "buhtzz/backintime" and "bit-team/backintime". I can not trigger a build for "buhtzz/backintime"; not on the Travis dashboard and not via creating a PR against my own repo. The message on the Travis dashboard is "We are unable to start your build at this time. You exceeded the number of users allowed for your plan. Please review your plan details and follow the steps to resolution." Any idea what this could be about? Kind Christian

2 2

Why DBus?
by c.buhtz＠posteo.jp 08 Sep '22

08 Sep '22

Hello, that Issue (https://github.com/bit-team/backintime/issues/931) is an opportunity for me to learn about DBus. It is far beyond my knowledge. The problem is something in the context of crontab and DBus. I know what crontab is and why BiT need it. I have heard about DBus and have an idea about what it is. But I don't understand why BiT need it and how it fits into the context of crontab. DBus is about interproces communication. But the piece of code IMHO relevant to the linked issue just try to manipulate the crontab. This is a simple job on a file. Which whom tries BiT communicate here? ;) Kind Christian

2 1

git: remote add upstream
by c.buhtz＠posteo.jp 08 Sep '22

08 Sep '22

Hello, I need some help with my local git config. Of course I forked "backintime" via the GitHub web-frontend. And after that I cloned my fork to my local machine. No I try to configure the "remotes". for "upstream" I used the URL that is offered by the web-frontend. But it seems to doesn't work. I also tried the http-url instead of the git@. git remote -v origin git@github.com:buhtzz/backintime.git (fetch) origin git@github.com:buhtzz/backintime.git (push) upsream git@github.com:bit-team/backintime.git (fetch) upsream git@github.com:bit-team/backintime.git (push) upsream2 https://github.com/bit-team/backintime.git (fetch) upsream2 https://github.com/bit-team/backintime.git (push) But this doesn't succeed: git pull upstream fatal: 'upstream' does not appear to be a git repository fatal: Konnte nicht vom Remote-Repository lesen. Bitte stellen Sie sicher, dass die korrekten Zugriffsberechtigungen bestehen und das Repository existiert. And I also only see the "remote" branches but not "upstream" or "upstream2". git branch -a * master remotes/origin/HEAD -> origin/master remotes/origin/gocrypt remotes/origin/incorp-bit-search remotes/origin/master remotes/origin/patch-1 remotes/origin/patch-2 remotes/origin/series1.0 remotes/origin/series1.1 remotes/origin/series1.2 remotes/origin/traack_fix_snapshot_test remotes/origin/traack_fixup_devnull remotes/origin/traack_gui_test Any idea how to fix this? Kind and good night. Christian

2 2