Hello together,
it seems that BIT does use Sphinx. I can see the reStructuredText in the
codes docstrings.
But I can't find the HTML docu generated from that docstrings.
Not sure what the correct term is here for documentation that was
generated out of docstrings: "Reference"?
Does anyone know if there is such a docu?
If not is anyone able to generate such a docu quick and dirty from the
current main branch and can send it to me or somewhere else? It doesn't
have to go into the official …
[View More]repo yet. It just would help me a lot to
better understand the code and the structure of the project.
I have used Sphinx a bit but I'm not quit familiar with it. And I won't
touch Sphinx. ;)
Btw: I am aware of the separate docu repo:
https://github.com/bit-team/doc
But it seems to me that this only is kind of a "User manual" and does
not reference to the code.
Kind
Christian
[View Less]
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 …
[View More]just try to manipulate the crontab. This is
a simple job on a file. Which whom tries BiT communicate here? ;)
Kind
Christian
[View Less]
Hello,
does anyone of you have experience with the continuous integration
system "Travis" used by GitHub?
If so it would be great if you could modify the configuration and offer
this as an PR.
I assume this is the relevant configuration file for that:
https://github.com/bit-team/backintime/blob/master/.travis.yml
The file seems quit easy but I don't want to mess around with it if
there is someone with a bit more experience.
I would like to remove the "python-nightly" from the tests. It …
[View More]seems
interesting to know how the BiT code works with the next Python version.
But currently we don't have resources for that and problems there are
not urgent. We always should test the code manually when a new release
candidate comes out. This is IMHO enough. Python 3.10 is fresh out and
will stay for some times. Let's concentrate on more urgent problems.
Doing this automatically distracts the users offering PRs and often gets
red travis errors. As an example:
https://github.com/bit-team/backintime/pull/1274/checks?check_run_id=798178…
The problem here is that BiT use the deprecated
`unittest.TestCase.assertEquals()` with an 's' at the end instead of the
without the 's' at the end. No big deal and not relevant for the code
that was changed by the PR. The user invested time do offer us a PR so
we should give him the damn good feeling of green test indicators. ;)
So please someone remove "python-nightly".
Also "python3.9-dev" isn't needed anymore because 3.9 is stable. Current
is 3.9.13 and maybe there will come a 3.9.14 someday but the
modifications shouldn't break our builds. So no need to check a
dev/rc/pre version here.
And why does python 3.6 and 3.10 are happens two times here?
https://github.com/bit-team/backintime/pull/1274/checks?check_run_id=798178…
Is there a good reason for this or can we drop this and reduce resources
(time, energy and CO2) on the GitHub server?
Kind
Christian
[View Less]
Hello,
and another fundamental basic question. ;)
Please correct me if I am wrong but I realized today that that
BackInTime is not one application but two; in the meaning of binaries.
Looking into the git repo there are two entry points in the meaning of
"if __name__ == '__main__'":
/backintime/common/backintime.py
/backintime/qt/app.py
Nice to know.
Of course I will have a closer look myself in the next weeks. But please
let me ask also.
Is the command-line version of backintime …
[View More]capable of working alone? Does
it make sense to install just "backintime-cli"?
I am aware that the cli version can take snapshots.
But do assume it right that the cli version is not able to create a new
backup job because the creating and configuration of a new backup job
can be done only in the GUI, right?
So can we say that backintime-cli as standalone version doesn't make
sense?
The background of my question is the workload of the distro maintainers
who have to deal with two applications.
Kind
Christian
[View Less]
Hello,
this is a newbie question but I really don't get it.
I clone the git repo and want to run/start BiT then. I want to start BiT
without installing it (wie deb/abt or make) or anything else. I just
want to start from the py file directly.
Is that possible? Was anyone able to make it that way?
The only way that works (as a workaround) for me is to use "makedeb.sh"
and then install the deb files.
But I would like to do something like "python3 ./backintime.py" or
something like this.
…
[View More]The standard today would be to use "Development Install" feature of pip:
"pip3 install --editable ."
But the later definitely don't work in because the project folder isn't
prepared for that.
I also tried configure and make. But I didn't get it. I won't bore you
with details here. I assume that I am the problem and not make. But also
make is just a workaround because it builds and installs.
At the end and in the current state using the makedeb-workaround would
do it. I just asked to know if someone else has a better way.
Kind
Christian
[View Less]