1. Forum
  2. Usenet
  3. LINUX.DEBIAN.MAINT.PYTHON

  • Multi-Arch: same and WHEEL files

    From Soren Stoutner@21:1/5 to Debian Python on Wed Jan 8 13:03:32 2025
    Python3-hid was marked `Multi-Arch: same` by a previous maintainer. Recently, tracker.debian.org warned that there is an issue because the WHEEL file is different in each package.

    https://tracker.debian.org/pkg/python-hidapi

    The differences are in the `tag` field in the WHEEL file. For example, amd64 has:

    Tag: cp312-cp312-linux_x86_64

    While arm64 has:

    Tag: cp312-cp312-linux_aarch64

    What is the recommended way to deal with this?\

    1. Should the package not be marked `Multi-Arch: same`?

    2. Should I prevent the binary package from shipping the WHEEL file?

    3. Is there some other recommendation?

    --
    Soren Stoutner
    soren@debian.org
    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmd+2hQACgkQwufLJ66w tgP2NQ/+OBvfPL/he/k0JiXkNC8QSnsIuyUbQ9Xea/dC7OCgkc7MmlEXs5dQIp4+ Dk9C3N5psfPUUphQ1uEWpMIbsCVkoc/OKOAKnRN0DEZ5gmWaLgS6SV5ue2VtnCzS NoUo8HnPtDwn3472t0huH4TrmYLShrLXKw6p2PrwtPkrWoSVuPyzm3I3Y5UaNduP 2SkGYPwRjbkpeU5ihFCSvVLaKL4n6mknR7ixCGZX5EmSkLoOGZR+XRbKKYZmrAvZ AGUhdMBwFOKc2S13HYDkJmnJO8sLgM/iaKEXTp++cBhsyHNoXqrNi3AQbbTLsOkT bVu6dLDIIFYCBXojTQbeedlR0nZ0XvB7QSs9VSFt/vf7qDmjhuNy6sAQaR2hMi/6 vKLD2Nl9aOkc/zado8WNSu5HTIBwYJYRNewGw/0+ARkBOFq2ViBVDHGV1SAbf9VE vFPc+MLPxSRZoYkOOt+jihfGSmPNik6AMQVzTGKjJaVhg+KuuLi3wyG8meZ+VhRU tORyX6J7JeJw+eEdW9bbj6ufg7zOumSscVFkwUb51u81UOOwli708vL4bAOr2/a0 JPkTyL/e/s3b5XuXxxATlp+zjeq+n7tILHJCr84kPBs46neqcKbR/YWENIUYwUIS i2r1nkuX79p5SIJipe/axSn3fVLWUAbeqcGX0x5/aUW3vve+/lE=
    =zr34
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Scott Talbert@21:1/5 to Soren Stoutner on Wed Jan 8 21:50:01 2025
    On Wed, 8 Jan 2025, Soren Stoutner wrote:

    Python3-hid was marked `Multi-Arch: same` by a previous maintainer. Recently,
    tracker.debian.org warned that there is an issue because the WHEEL file is different in each package.

    https://tracker.debian.org/pkg/python-hidapi

    The differences are in the `tag` field in the WHEEL file. For example, amd64 has:

    Tag: cp312-cp312-linux_x86_64

    While arm64 has:

    Tag: cp312-cp312-linux_aarch64

    What is the recommended way to deal with this?\

    1. Should the package not be marked `Multi-Arch: same`?

    2. Should I prevent the binary package from shipping the WHEEL file?

    3. Is there some other recommendation?

    It seems like this package probably should just not be marked Multi-Arch:
    same. The WHEEL file is likely important metadata.

    Scott

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Scott Talbert@21:1/5 to Matthias Klose on Wed Jan 8 22:10:01 2025
    This message is in MIME format. The first part should be readable text,
    while the remaining parts are likely unreadable without MIME-aware tools.

    On Wed, 8 Jan 2025, Matthias Klose wrote:

    On 08.01.25 21:36, Scott Talbert wrote:
    On Wed, 8 Jan 2025, Soren Stoutner wrote:

    Python3-hid was marked `Multi-Arch: same` by a previous maintainer.
    Recently,
    tracker.debian.org warned that there is an issue because the WHEEL file is >>> different in each package.

    https://tracker.debian.org/pkg/python-hidapi

    The differences are in the `tag` field in the WHEEL file.  For example, >>> amd64
    has:

    Tag: cp312-cp312-linux_x86_64

    While arm64 has:

    Tag: cp312-cp312-linux_aarch64

    What is the recommended way to deal with this?\

    1.  Should the package not be marked `Multi-Arch: same`?

    2.  Should I prevent the binary package from shipping the WHEEL file?

    3.  Is there some other recommendation?

    It seems like this package probably should just not be marked Multi- Arch: >> same.  The WHEEL file is likely important metadata.

    but why would we ship wheel files in the first place?

    In this case Soren's talking about the WHEEL file in the dist-info
    directory, not a .whl file.

    Scott

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Soren Stoutner@21:1/5 to Debian Python on Wed Jan 8 15:45:07 2025
    On Wednesday, January 8, 2025 1:36:18 PM MST Scott Talbert wrote:
    On Wed, 8 Jan 2025, Soren Stoutner wrote:
    Python3-hid was marked `Multi-Arch: same` by a previous maintainer. Recently, tracker.debian.org warned that there is an issue because the WHEEL file is different in each package.

    https://tracker.debian.org/pkg/python-hidapi

    The differences are in the `tag` field in the WHEEL file. For example, amd64
    has:

    Tag: cp312-cp312-linux_x86_64

    While arm64 has:

    Tag: cp312-cp312-linux_aarch64

    What is the recommended way to deal with this?\

    1. Should the package not be marked `Multi-Arch: same`?

    2. Should I prevent the binary package from shipping the WHEEL file?

    3. Is there some other recommendation?

    It seems like this package probably should just not be marked Multi-Arch: same. The WHEEL file is likely important metadata.

    Thank you for the advice. I have done so.

    --
    Soren Stoutner
    soren@debian.org
    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmd+//MACgkQwufLJ66w tgOq8RAAkRMZyClAqC8PJayGmtbeC3eff+JDoyE2VowD5fNapPVzYwfCKNkM5n/W hHXMUeaZMYaVvg0p1DUYqjW3ImhRJPigGdC9AWNWTbbkOQ+LkDf1jfbdikMyPB3e Jb6IQZFg11GUttWnPY6J2oaznI/OyzDK2SuIDuQBDGCYActR4IMSGaLuYDBmShMD /fWO5fePwihVlPVmAtTfRnPUF6b5P3myJjYgTRBKP6mJEWC25JpwflLsQL+YKpuZ 07XgVTP6UG5xlK8i6y5uhJTTW3quFp2jussDnbFqCq0Vx6AwuzRbMqk+1BCbHmIa sD/sPlnj1wgttjBeVp2xgK2nzFyBxl2I6niwoW62c1RAUuKywRA5RB1AsADQxKf/ cui/ZBsl20yNlwyuQqpuP0lRDvlgJiVqZQccDvqWJRFjnCU89PnaxeO6x/fGw3j5 qsG3wlHP4iOOBEbw3yenCuV8qPuzmo3+Tl6jDYYWTlfb+2Tl8NGd3AMEXZVBhU0g vp7XqjlLXirCrDMye39Kc5ThT7199TPlACsjWM5RdMc5IM/9w7ZO8JNxh/Dyw5yR FoZDZl7oAOGe/Gs8gDJ9/DsoskLC5FmbkZcnU5ao/PkU68YLZzqkmn6pi+vlnu6/ uVIiqLVjGgEhN4x4DVDJeyDDehOd223P8pr9dk/50BsfxTHiVBI=
    =0uxo
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)