pyproject.toml | 4 2 2 - 0 !
1 file changed, 2 insertions( ), 2 deletions(-)

 adjust poetry build system in pyproject.toml.
 The upstream pyproject.toml relies on a dynamic versioning plugin to determine
 the version at build time, based on the Git tag.  This plugin is not available
 in Debian.  However, it doesn't really matter, since the correct version is
 set into the pyproject.toml file when the sdist is published.  We can just
 reset the build system back to the default Poetry implementation and
 everything works as expected.

src/CedarBackup3/customize.py | 4 2 2 - 0 !
1 file changed, 2 insertions( ), 2 deletions(-)

 convert source to use debian platform customizations.
 Upstream includes an easy way to switch the platform from "standard" (i.e.
 cdrecord and mkisofs) to "Debian-specific" (i.e. wodim and genisoimage).
 This patch flips the PLATFORM constant so that we get Debian customizations.

docs/conf.py | 3 2 1 - 0 !
docs/index.rst | 21 0 21 - 0 !
2 files changed, 2 insertions( ), 22 deletions(-)

 change config for sphinx alabaster theme to fix lintian warnings.
 The standard Alabaster theme includes both a GitHub banner ("Fork me on
 GitHub!") and some buttons to star and fork the upstream GitHub project, etc.
 Debian policy considers the resulting images to be a privacy breach, so for
 the Debian version of this documentation, I just disable those features.
 The various badges on the homepage (test suite passing, PyPI versions, etc.)
 have a similar problem.  These changes resolve the Lintian privacy-breach-logo
 and privacy-breach-generic warnings. 

docs/conf.py | 1 0 1 - 0 !
1 file changed, 1 deletion(-)

 disable sphinx autoapi documentation.
 Various Sphinx-related packages are out-of-date in Debian, and that has
 started to cause problems.  I have pinned the dependencies in pyproject.toml
 to match what's available in Debian.  However, the most recent python3-astroid
 package in Debian unstable is now 3.x, and that version breaks autoapi document
 generation with the older Sphinx packages.  The simplest thing for now is to
 just disable the autoapi docs. These days, the user-facing documentation is
 more important than the developer documentation.