Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod From: Carles Pina i Estany Newsgroups: linux.debian.maint.python Subject: Re: dh_python3: file in /usr/lib/python3.12/dist-packages ? Date: Mon, 26 Feb 2024 01:10:01 +0100 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Feb 26 00:01:15 2024 Old-Return-Path: X-Amavis-Spam-Status: No, score=-12.21 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, LDO_WHITELIST=-5, PGPSIGNATURE=-5, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -4.6 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="NyR7JGSjHZ/7Yjob" Content-Disposition: inline X-Mailing-List: archive/latest/21471 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/ZdvUsHkxKRClMM4M@pina.cat Approved: robomod@news.nic.it Lines: 149 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Mon, 26 Feb 2024 00:00:48 +0000 X-Original-Message-ID: X-Original-References: <20240225013541.t7cpd3vojm4vdciw@satie.tumbleweed.org.za> Xref: csiph.com linux.debian.maint.python:15494 --NyR7JGSjHZ/7Yjob Content-Type: text/plain; protected-headers=v1; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Date: Mon, 26 Feb 2024 00:00:48 +0000 From: Carles Pina i Estany To: debian-python@lists.debian.org Subject: Re: dh_python3: file in /usr/lib/python3.12/dist-packages ? Hi, During the "gbp buildpackage" (or "dpkg-buildpackage") I see in Salsa: python3.11 -m build --skip-dependency-check --no-isolation --wheel --outdir /builds/python-team/packages/python-ping3/debian/output/source_dir= /.pybuild/cpython3_3.11 [...] python3.12 -m build --skip-dependency-check --no-isolation --wheel --outdir= /builds/python-team/packages/python-ping3/debian/output/source_dir/.pybuil= d/cpython3_3.12 The first one includes, in top_level.txt: debian ping3 And the second one: build debian ping3 Where "ping3" is the expected module. "debian" is there because of the debian/ directory (I'm super sure, and AFAIK should not be there!) and "build" is there on the second time since, I guess, it exists at that time. So, even in the package in testing, it contains "debian" which is wrong: $ cat ./dist-packages/ping3-4.0.4.dist-info/top_level.txt debian ping3 And in salsa it contains the difference, making it more obvious. The file top_level.txt generated by "python3 -m build" in upstream checkout does not contain "debian". In my system, I see[1] more packages that might have the same problem. So now, I guess that the question is: a) How to make "python3 -m build" to not include "debian" or "build"? b) What would be the best way to address this (if possible, via d/rules changes). I mean, besides post-processing the generated file which I guess that is possible, but not the best idea. [1]: Via carles@pinux:/usr/lib/python3$ find . -iname "top_level.txt" -exec= grep -l ^debian$ {} \; On 25 Feb 2024 at 23:32:09, Carles Pina i Estany wrote: >=20 > Hi, >=20 > On 25 Feb 2024 at 01:35:41, stefanor@debian.org wrote: > > Hi Carles (2024.02.25_00:14:46_+0000) > > > It generates a .deb file with a directory: > > >=20 > > > /usr/lib/python3.12/dist-packages/ping3-4.0.4.dist-info/ > > >=20 > > > With two files there: > > > -INSTALLER > > > -top_level.txt > >=20 > > If there are files in /usr/lib/python3.*/dist-packages/ after running > > dh_python3, it means they differed between python 3.x versions. >=20 > yes... >=20 > > So to investigate, diff the files against the ones in > > /usr/lib/python3/dist-packages/ and see if you can spot why they are not > > matching. >=20 > $ ls python3.12/dist-packages/ping3-4.0.4.dist-info/ > INSTALLER top_level.txt >=20 > $ ls python3/dist-packages/ping3-4.0.4.dist-info/ > entry_points.txt INSTALLER METADATA top_level.txt WHEEL >=20 > The file INSTALLER is the same: >=20 > $ diff -u python3.12/dist-packages/ping3-4.0.4.dist-info/INSTALLER python= 3/dist-packages/ping3-4.0.4.dist-info/INSTALLER >=20 > The file top_level.txt is different: >=20 > $ diff -u python3.12/dist-packages/ping3-4.0.4.dist-info/top_level.txt py= thon3/dist-packages/ping3-4.0.4.dist-info/top_level.txt=20 > --- python3.12/dist-packages/ping3-4.0.4.dist-info/top_level.txt 2023-11-= 06 22:53:00.000000000 +0000 > +++ python3/dist-packages/ping3-4.0.4.dist-info/top_level.txt 2023-11-06 = 22:53:00.000000000 +0000 > @@ -1,2 +1,3 @@ > +build > debian > ping3 >=20 > > It's probably something non-reproducible in the package's build system. >=20 > Will investigate and if relevant share the problem here. This is in > salsa using the standard pipeline. Last time that I run the pipeline I > didn't have this problem. It was months ago. >=20 > If you have any ideas let me know, of course! >=20 > Thanks! >=20 > --=20 > Carles Pina i Estany > https://carles.pina.cat --=20 Carles Pina i Estany https://carles.pina.cat --NyR7JGSjHZ/7Yjob Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEth6/Zob9uGYomaJ+qAKIT2ClX4EFAmXb1LAACgkQqAKIT2Cl X4Fk3Q//dozRnCTRVKwkAZM5ZapA5AvYj1Gr7TZoA+xeKC8Hd2ZTUCMYvCcy38P/ 0gkwTOM9Pl9QUZRb5ggKotMj4hIj7ldnjhE/Hqq/lpq58hKrST5OH0I6pScUvZxq 62Iv8RZRjjuZsbkTYXOX2SfLNNsMuh1aiSp0NsMiTpDk5pNjT8jZiWsa+un64Jxq jQs+6Bu/r2DUBNLOxGvGpMlGVa3aKaCd5Zhyf02cLKa3+q5SiolGIRnTqobOAPs7 Sj29wOhuJPeHbRuGs3RwHqb1RG3L8dkIuyIOwAWZz47940+E9d6V0qw9dEsUkADE +nUYAnbI3Bn/hIMM5hPJr1LbTjMpIE6bGy8Q3JdWxyOO6Bt5XlMxf+MzfSsXJqgR wv5x0amHVUwRY2znBVjm/M5F5lsZoWaZaXueTRXBtNLqf/FownPo3jJdfSpZvT/Q kK+TbgGMblfM5tF/evFl6JkqB2QfZfirR2GUF7qNArkYwqaD/L9WLB0oSmatDNh/ zeo3VdUzlUHD03eUdTJX2XnnPavbNQQYaoxIQrBAGIWzJQlCr7EoQFcROtrz6eqa jmwwFcCkFqGY8hf/DTVW/ASNQiTbYSvnml5QnGD7YyKCTqcsJF8CFGHnnIk2PWtZ fKUxoj4oHhbZK38RCd5t1nCx1y+iGNIECJPBc+gZCWBrN+zDxHs= =6Hsv -----END PGP SIGNATURE----- --NyR7JGSjHZ/7Yjob--