Path: csiph.com!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod From: PICCA Frederic-Emmanuel Newsgroups: linux.debian.maint.python Subject: Re: dpkg-buildpackage vs sbuild with python packaging Date: Wed, 11 Jun 2025 17:30:02 +0200 Message-ID: References: X-Original-To: Santiago Vila X-Mailbox-Line: From debian-python-request@lists.debian.org Wed Jun 11 15:27:11 2025 Old-Return-Path: X-Amavis-Spam-Status: No, score=-2.896 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001] autolearn=no autolearn_force=no X-Policyd-Weight: using cached result; rate: -5.5 Dkim-Filter: OpenDKIM Filter v2.10.3 zmtaout05.partage.renater.fr D05FBA0105 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Mailer: Zimbra 8.8.15_GA_4652 (ZimbraWebClient - FF128 (Linux)/8.8.15_GA_4652) Thread-Topic: dpkg-buildpackage vs sbuild with python packaging Thread-Index: 8uAjkBBpN4AoXFM+4il0qHYyG0eqdg== X-Virus-Status: Clean X-Renater-Ptge-Spamstate: clean X-Renater-Ptge-Spamscore: -100 X-Renater-Ptge-Spamcause: gggruggvucftvghtrhhoucdtuddrgeeffedrtddugdduvdehudcutefuodetggdotefrodftvfcurfhrohhfihhlvgemucftgffptefvgfftnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpeffhffvvefkjghfufggtgfgofhtsehtjegttdiitdejnecuhfhrohhmpefrkfevveetucfhrhgvuggvrhhitgdqgfhmmhgrnhhuvghluceofhhrvgguvghrihgtqdgvmhhmrghnuhgvlhdrphhitggtrgesshihnhgthhhrohhtrhhonhdqshholhgvihhlrdhfrheqnecuggftrfgrthhtvghrnhepleefkeeujefgjeeigefgffffudegheefgfeffeethfetkedtiedvhfeijeeifefgnecukfhppedutddrvdehgedrvdegtddrudegheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepihhnvghtpedutddrvdehgedrvdegtddrudeghedphhgvlhhopeiishhtohhrvgdqsgefqddtuddvrdhprghrthgrghgvrdhrvghnrghtvghrrdhfrhdpmhgrihhlfhhrohhmpehfrhgvuggvrhhitgdqvghmmhgrnhhuvghlrdhpihgttggrsehshihntghhrhhothhrohhnqdhsohhlvghilhdrfhhrpdhnsggprhgtphhtthhopedvpdhrtghpthhtohepshgrnhhvihhlrgesuggvsghirghnrdhorhhgpdhrtghpthhtohepuggvsghirghnqdhphihthhhonheslhhishhtshdruggvsghirghnrdhorhhg X-Mailing-List: archive/latest/23032 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/895197705.132125083.1749654653778.JavaMail.zimbra@synchrotron-soleil.fr Approved: robomod@news.nic.it Lines: 12 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python X-Original-Date: Wed, 11 Jun 2025 17:10:53 +0200 (CEST) X-Original-Message-ID: <895197705.132125083.1749654653778.JavaMail.zimbra@synchrotron-soleil.fr> X-Original-References: <1779402678.132016719.1749649153102.JavaMail.zimbra@synchrotron-soleil.fr> Xref: csiph.com linux.debian.maint.python:16901 It seems that this is due to setuptools-scm which provide the list of the data during the dpkg-buildpackage. taken from the doc of setuptools-scm --- Additionally setuptools-scm provides setuptools with a list of files that are managed by the SCM (i.e. it automatically adds all the SCM-managed files to the sdist). Unwanted files must be excluded via MANIFEST.in or configuring Git archive. --- And indded via sbuild there is no .git directory so setuptools-scm do not provide the list. Do we know how to deal with this at the pacakging level. the upstream is using the code from the git repository, so it is not affected by this issue... Fred