Mailman 3 January 2023 - Bit-dev

Re: FYI Renaming default branch from "master" to "main"
by c.buhtz＠posteo.jp Jan. 23, 2023

Jan. 23, 2023

In-Reply-To=<e5d8cb0e8110f79c8fe0cfb9a508c4b6%40posteo.de> Hello, renaming is done. Be aware to update your local repositories or re-clone them; also your forks on GitHub. Beside the new "main" branch I created the "dev" branch. In the past I used the name "develop" but found out it is unusual and a bit to long. I think "dev" is easier (for some of us). :D Hope this is OK. I also updated the target branch in all existing and open Pull Requests. I created a new Pull Request updating version numbers, changelog and mention the "dev" branch in the README.md. @Jürgen: I know you work on some FAQ and maybe README. Maybe this will cause a merge conflict. But some md-files are a secure learning case I think. ;) I assume your upcoming docu changes should go into "main" too? I suggest to merging it into "dev" and then picking the changes form there into "master". I would do that via "git checkout my.file dev". I never used git's cherry pick before. This is one exception of the only-release-commits-in-main because "main" do produce the landing page via its README.md. Kind Christian

2 4

"make uninstall"?
by c.buhtz＠posteo.jp Jan. 21, 2023

Jan. 21, 2023

Hello, haven't I asked this before somehow? ;) We can install BIT from source repo via "make install". But it seems there is not "make uninstall". How can I uninstall? Kind Christian

2 2

Request for review of a bug report on debian (#985260 cron jobs error not mailed to user)
by c.buhtz＠posteo.jp Jan. 21, 2023

Jan. 21, 2023

Hey folks, can someone please who knows good about cron have a look at this bug report. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985260 The users expect that he would got a mail if there is a syntax error in one of his user-callback scripts running by cron. I'm not sure if this should be the default behaviour and which component is responsible for sending mails. For the letter I assume cron should do this. So I assume this bug is not related to Back In Time. Am I wrong? Kind Christian

3 3

How diagnose logs?
by c.buhtz＠posteo.jp Jan. 21, 2023

Jan. 21, 2023

Hey Folks, there is a fresh bug on launchpad [1] which brings up the opportunity for me to learn something. In short about the bug: I assume the LOCK file is somewhere. But I don't know where BIT stores it. Maybe one of you can jump in and help. And I didn't found the LOCK-file topic in our FAQ. Would be great to add this there, too. Back to the main topic of that mail. It is an often experience situation for me when dealing with log files and debug output. In relation to that specific issue let me ask some questions please. - The reporter use "systemctl status cron" to show us cron output. But BIT isn't a systemd unit. How can I ask the system for BIT releated syslog output? Next time I can answer the user with "Please execute 'xyz' in the shell and post me the output.". - Where does BIT store its LOCK files? It seems to me this information is not present in debug output. But I'm not sure. Kind Christian [1] -- <https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/2003326>

3 2

Latest Back In Time release (1.3.3) merged into Debian
by c.buhtz＠posteo.jp Jan. 20, 2023

Jan. 20, 2023

Hello, I like to announce that our latest release joined the Debian "unstable" branch. https://tracker.debian.org/pkg/backintime Based on my humble understanding I would say that BIT 1.3.3 would make it into the next stable Debian release (Version 12 namely Bookworm). Kind Christian

2 1

FYI Renaming default branch from "master" to "main"
by c.buhtz＠posteo.jp Jan. 13, 2023

Jan. 13, 2023

Hello together, I just want to inform you that in the next days we will rename the branch "master" into "main" and make that the new default branch on Microsoft GitHub. There is no need for a warning or countdown. ;) I tested it with my own fork and found out it is much easier then I thought. When you have your own fork from bit-team/backintime on GitHub they keep connected no matter how the default branches are named. If possible and if it doesn't interrupt any task you currently work on it must be the easiest to delete your fork and fork again. But I assume there will be no problem if you keep your fork. It is up to you. If you cloned from the upstream repo bit-team/backintime into your own machine and you want to keep that clone you should do a bit git magic like this: git branch -m master main git fetch origin git branch -u origin/main main git remote set-head origin -a That is how GitHub itself "told" me. It renames your local branch and "reconnect" it to the remote branch. I don't understand the 4th command. ;) Greetings Christian

1 0

Where to store picture files for FAQ and README in the "backintime" repo?
by BiT dev Jan. 13, 2023

Jan. 13, 2023

I am working on a FAQ issue and intend to add some screen shots to our FAQ which is now under version control in the same repo as our source code: https://github.com/bit-team/backintime/issues/1394 https://github.com/bit-team/backintime/blob/master/FAQ.md#how-to-use-synolo… We currently do not reference any picture file, neither in the README.md nor in the FAQ.md. Where shall we store these picture files (mainly screen shots I guess)? I suggest creating a sub folder "doc" in the "backintime" repo root. This would correspond to my upcoming PR with developer documentation the sub folder "doc-dev". Proposals welcome :-)

2 1

ANN: Back In Time 1.3.3 released
by c.buhtz＠posteo.jp Jan. 12, 2023

Jan. 12, 2023

Hello, on behalf of the maintaining team I'm happy to announce the Back In Time release version 1.3.3 [1]. Germar also made that release available on Launchpad [2] via the testing-PPA ("ppa:bit-team/testing"). The Debian release is also on its way [3]. I hope it can happen before Debians Freeze phase starting on 23th January. Thanks to the Team, to Germar, all Contributors and Users. Kind Christian Buhtz [1] -- <https://github.com/bit-team/backintime/releases/tag/v1.3.3> [2] -- <https://launchpad.net/backintime/1.3/1.3.3> [3] -- <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027823>

3 6