Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From: Ole Streicher <olebole@debian.org>
Newsgroups: linux.debian.maint.python
Subject: Re: package_data in python package
Date: Mon, 28 Oct 2019 17:20:01 +0100
Message-ID: <yWfUl-45z-1@gated-at.bofh.it>
References: <yWelz-2Sv-7@gated-at.bofh.it> <yWevf-2Wb-5@gated-at.bofh.it> <yWeOB-3is-7@gated-at.bofh.it> <yWeYi-3m0-1@gated-at.bofh.it> <yWf7Y-3pc-11@gated-at.bofh.it>
X-Original-To: debian-python@lists.debian.org
X-Mailbox-Line: From debian-python-request@lists.debian.org  Mon Oct 28 16:15:16 2019
Old-Return-Path: <news@liska.ath.cx>
X-Amavis-Spam-Status: No, score=-6.332 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, HEADER_FROM_DIFFERENT_DOMAINS=0.249, KHOP_HELO_FCRDNS=0.399, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02] autolearn=ham autolearn_force=no
X-Policyd-Weight: using cached result; rate: -5.5
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Lines: 21
X-Mailing-List: <debian-python@lists.debian.org> archive/latest/17524
List-ID: <debian-python.lists.debian.org>
List-URL: <https://lists.debian.org/debian-python/>
List-Archive: https://lists.debian.org/msgid-search/87zhhk980j.fsf@orrococo
Approved: robomod@news.nic.it
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
X-Original-Date: Mon, 28 Oct 2019 16:58:36 +0100
X-Original-Message-ID: <87zhhk980j.fsf@orrococo>
X-Original-References: <20191028142544.zlzgobcvpm3yzbvt@capeo.gueux.org> <2505510.ydTWeorpcb@l5580> <20191028150240.hk5wrdpxhiv43w6g@capeo.gueux.org> <3360581.9UBmNTVxP0@l5580> <20191028152841.j7ycyfnpvoevgboj@capeo.gueux.org>
Xref: csiph.com linux.debian.maint.python:11963

Félix Sipma <felix+debian@gueux.org> writes:
> They just run "python3 setup.py install" (https://github.com/scheibler/khard/issues/231):
> [...]
>
> For my part, I "just" build the debian package with "gbp buildpackage",
> and with "dh $@ --with python3 --buildsystem=pybuild" in debian/rules.
>
> The solutions I say are: I can keep the patch in the package (without
> really understanding the need for it) or try to convince upstream to
> merge it (but they can't reproduce the problem, so why would they do
> that?). In both cases, probably others will encounter the same problem
> in other packages... It would be nice to fix the problem once for all
> (if possible :)).

Just FYI, https://bugs.debian.org/940728 describes a similar problem,
although there the unhandled files are Python source files. pybuild
seems to handle things different from plain setup.py.

Cheers

Ole