Right, these condition are specific to debian packaging. borgmatic is install system wide and run as root. The convention is to ship config in /etc, hence the condition on `/etc/borgmatic{.d/*.ya…
I rebased the branch on latest changes from main to control and it still looks fine (I did not pushed rebased code though).
These change are good to merge now.
We discussed it already :)
[These files are in the source distribution. The MANIFEST.in is declaring it and setuptools includes them by default, no need to explicitly declare ](https://projects.…
Then I think pycqa config could be gathered within tox.ini conf file when pyproject.toml is not supported.
I'm not familar with PyCQA. What is its config? It looks like [Tox does…
It's done automatically indeed.
And the resulting tar ball does not contain any test files.
But to make…
Right, it can still be ported to pyproject.toml with an extra conf :
[tool.setuptools]
obsoletes = ['atticmatic']
These files (systemd units and schema) are declared in MANIFEST.in and by default, [include-package-data is true in pyproject.toml](https://setuptools.pypa.io/en/latest/userguide/datafiles.html…
I believe there are two different issues here. One regarding tox and another one concerning the release script.
My understanding of recent python packaging is that build module is…
Package discovery was broken indeed and somehow my test failed to raise the issue (some leftovers interfered I guess). Anyway I fixed this in d5afdeebda.
I'm hoping to have more time next week…
I'm not sure how PyCQA is handled within borgmatic project. The doc suggest tox is the main entrypoint.
Then I…