From: 
Subject: Debian changes

The Debian packaging of zwave-js-server-python is maintained in git, using a workflow
similar to the one described in dgit-maint-merge(7).
The Debian delta is represented by this one combined patch; there isn't a
patch queue that can be represented as a quilt series.

A detailed breakdown of the changes is available from their canonical
representation -- git commits in the packaging repository.
For example, to see the changes made by the Debian maintainer in the first
upload of upstream version 1.2.3, you could use:

    % git clone https://git.dgit.debian.org/zwave-js-server-python
    % cd zwave-js-server-python
    % git log --oneline 1.2.3..debian/1.2.3-1 -- . ':!debian'

(If you have dgit, use `dgit clone zwave-js-server-python`, rather than plain `git clone`.)

We don't use debian/source/options single-debian-patch because it has bugs.
Therefore, NMUs etc. may nevertheless have made additional patches.

---

diff --git a/pyproject.toml b/pyproject.toml
index 08b6710..d64f7fd 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -37,6 +37,7 @@ zwave-js-server-python = "zwave_js_server.__main__:main"
 version = { attr = "zwave_js_server.const.__version__" }
 
 [tool.setuptools.packages.find]
+include = ["zwave_js_server", "zwave_js_server.*"]
 exclude = ["test", "test.*", "scripts"]
 
 [tool.setuptools.package-data]
