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

  • [Help] New package python-loky build time test times out

    From Andreas Tille@21:1/5 to All on Wed Dec 25 18:50:01 2024
    Hi,

    the new version of python-cogent needs python-loky[1] which I tried to
    package. Unfortunately there is some issue with the build-time test
    which times out[2]. Any help is welcome.

    Kind regards
    Andreas.


    [1] https://salsa.debian.org/python-team/packages/python-loky
    [2] https://salsa.debian.org/python-team/packages/python-loky/-/jobs/6775017

    --
    https://fam-tille.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrey Rakhmatullin@21:1/5 to Andreas Tille on Wed Dec 25 19:00:02 2024
    On Wed, Dec 25, 2024 at 06:47:01PM +0100, Andreas Tille wrote:
    Hi,

    the new version of python-cogent needs python-loky[1] which I tried to package. Unfortunately there is some issue with the build-time test
    which times out[2]. Any help is welcome.

    Why do you think it's the build-time test?


    Kind regards
    Andreas.


    [1] https://salsa.debian.org/python-team/packages/python-loky
    [2] https://salsa.debian.org/python-team/packages/python-loky/-/jobs/6775017


    --
    WBR, wRAR

    -----BEGIN PGP SIGNATURE-----

    iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmdsRo8tFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh CJ8P/3XUYbWxlFpal8mwUxQe38G9i6BwFSNChh1DzWDkRVuvU1lj9KJCcjI0aRJG cb1oJzmRjxEGtaibEVKr0YPpIijJ2y698/x60Y4jse3JqICCS2abq8+OLncQ+CxQ hQ+zn5PMw4AKhY4khm1g1190r4pf0D4rB/DyxN9kh6azxu6j1bue7Wp9n6ubPyNR DU3LS8zgHoyY8I4hNvlM66okwut9ZFKUnlGiBEBVsLPvDR51h/AZL3rYq9yaeLAS KIED0ZZO4Uw3Nt4EEgQUZU9KpkBZiowVRjdvYIG667mxmQ9+XofQXxFsh26XyWKI 1d5YuizcxkiBW98+NhtCXcn+e4ciqGEDbxXSvbyinf6HixKiWyEeljKSCxQ9sErh su9z3Wg1rwbXEq7Macgrk+vsS06iY7MtRiuAH0Z2Q3I0kR85peajlcH9LwVNSzKD ED2NaNFH1Z5yhXXO6L+hhNDY0AhPfc2HtGz69Z531p6lLVDyGxsE9QTv31u6Tppi in7PpewwkhzbNNaNowbkPPS4BAtyLmOBu3bR4G3zFrTgDhfFS9QlfStcVR7vA6pU OTMR3CXkvVSAVeGzD6suCmxnOJn+QGFWmCgAdTDABKWL1UTWyf9UYqh0KmBbVJN8 jCUZkCytbS29JrfEinJNxjB64k3T2hfNCTb13CZx3W46JXZs
    =mZTw
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From [email protected]@21:1/5 to All on Wed Dec 25 20:40:01 2024
    Hello,

    I am a Python developer and upstream maintainer.
    I am not much experience when it comes to distro packaging.
    This is just an example of a case I often do observe. And I always ask
    myself why this happens.

    Am 25.12.2024 18:47 schrieb Andreas Tille:
    the new version of python-cogent needs python-loky[1]

    I checked both package and do not understand why python-loky exist. It
    is a mini package with less benefit. Why does Debian burn resources in packaging things like this. I would ask python-cogent to remove that
    dependency instead of create a package for it. As upstream maintainer I
    would not dare to have dependencies like this in my project and bother
    distro maintainers with it.

    I am assuming this package will be orphaned in the near future.

    I am asking the upstream maintainer for a justification about this
    dependency:
    <https://github.com/cogent3/cogent3/issues/2187>

    Regards,
    Christian

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrey Rakhmatullin@21:1/5 to [email protected] on Wed Dec 25 21:00:02 2024
    On Wed, Dec 25, 2024 at 07:37:51PM +0000, [email protected] wrote:
    Hello,

    I am a Python developer and upstream maintainer.
    I am not much experience when it comes to distro packaging.
    This is just an example of a case I often do observe. And I always ask
    myself why this happens.

    Am 25.12.2024 18:47 schrieb Andreas Tille:
    the new version of python-cogent needs python-loky[1]

    I checked both package and do not understand why python-loky exist. It is a mini package with less benefit. Why does Debian burn resources in packaging things like this. I would ask python-cogent to remove that dependency
    instead of create a package for it. As upstream maintainer I would not dare to have dependencies like this in my project and bother distro maintainers with it.

    I am assuming this package will be orphaned in the near future.

    I am asking the upstream maintainer for a justification about this dependency:
    <https://github.com/cogent3/cogent3/issues/2187>

    https://github.com/search?q=repo%3Acogent3%2Fcogent3%20loky&type=code

    --
    WBR, wRAR

    -----BEGIN PGP SIGNATURE-----

    iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmdsY2UtFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh lJAQAJzqmGM/x8EIy/dJuWKhUWuKMF3h8DXt94532gvA89ZC2klY8OK479Pats7m LDgqtvoPHsavNAt2nrsG+0n6LTRSl1qAqcegE2xmemjOAGwE1BD9SDw6rw3evPnG 11XCiLooViUZN/bsWQydm/0gV1l/KULW50qJVIhHt4rJNjRHjZXfnw0P7WzYT6Se DK/Ggix35d1e3UBxjyzvk95Xvw74mpZwRsIVG7gGdEXfM03EekeQfmU+UFfZklWl WxCpcyIlOv9kQUrpN7A9crYNuywImdjTvczey9bl1hZOp0iMizbIxL5zoED6uMcX 832N9GbiW0z/AMdygUHCfEKZH0pWli5Uqz078hCND1up9fWYsXgtxqLEqBF11muk fRVEllsiT0bFJoxZakOJGXLW1H4zCaOaHglE3QF9oPYFZYvvUbIlGJeeGXixcX2C SLQXaz5ke2GW6amxvA9wnt7dBrrXX/UiQlJ9O+Fr0C10JxYJs5iGBot6Tfk01GKD 0ZecVEtCBVyeQ8K0HfyzX4Ohrq1AmLFjuXJiASg6QKHqMhm3UdO68wggrSXLDSg2 zrBQY5Y1eUlsGAgXWNQqNYlgF7xgSMbzPw4AUYXHUqHSSUg+Pb4HOSaw1g7W+1wV r8xAUVU/EDcQigq32UlHzeFk7L5d0g+wkMJwTUcVDhvFmHzS
    =4VTO
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andreas Tille@21:1/5 to All on Wed Dec 25 22:30:01 2024
    Am Wed, Dec 25, 2024 at 09:43:02PM +0100 schrieb Gregor Riepl:
    Why do you think it's the build-time test?

    The build output looks quite strange to me.

    It almost seems like it gets stuck in the middle of a copy job - the last log line is cut off, but this could be a log buffering issue.

    The build log is not complete - sorry, forgot to add this information.

    @Andreas Did you test the build process (as it's done by Salsa) in a local chroot or build container?

    I asked for help since it does not finish in my local pbuilder chroot.

    Does it get stuck there as well, do you see more output, or perhaps excessive memory usage / CPU load?

    It might make sense if someone tries to reproduce with sbuild or
    something else.

    Kind regards
    Andreas.

    --
    https://fam-tille.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From [email protected]@21:1/5 to All on Thu Dec 26 09:50:01 2024
    Dear Andrey,

    Am 25.12.2024 20:56 schrieb Andrey Rakhmatullin:
    https://github.com/search?q=repo%3Acogent3%2Fcogent3%20loky&type=code

    Sending URLs only is quit annoying to all other list members and not an
    answer.

    I know the details and that there are reasons why this package depend on
    the other. But IMHO the reasons are not heavy enough to burn resources
    of Debian packagers.
    As upstream I would just integrate that codebase into my own, or open a
    ticket at Jupyter to get rid of that restriction causing that
    dependency.

    I think of Debian GNU/Linux as a big project and I am worried about its resources. That's all.

    Regards,
    Christian

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrey Rakhmatullin@21:1/5 to [email protected] on Thu Dec 26 11:00:02 2024
    On Thu, Dec 26, 2024 at 08:48:54AM +0000, [email protected] wrote:
    https://github.com/search?q=repo%3Acogent3%2Fcogent3%20loky&type=code

    Sending URLs only is quit annoying to all other list members and not an answer.

    *shrug*

    I know the details and that there are reasons why this package depend on the other.

    But IMHO the reasons are not heavy enough to burn resources of Debian packagers.
    As upstream I would just integrate that codebase into my own,

    As an upstream I would never "integrate" a several thousands SLoC package, properly written, tested and maintained one, into my own project just to
    have 1 less dependency. This sounds very wrong to me.
    And I wouldn't do that "not to burn resources of Debian packagers", in
    any case. Saying this as a DD. Having to package dependencies is normal.

    or open a
    ticket at Jupyter to get rid of that restriction causing that dependency.

    Assuming it's possible, it could be done in parallel.

    --
    WBR, wRAR

    -----BEGIN PGP SIGNATURE-----

    iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmdtKOUtFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh cHEP/2sr45h2zIrkI6DOuC9PFJRXndMU0oPBa3Td6xl8MbwtiUM6ukYdsuUq/ZWN 2524DQv4RTWti3qB1P13JfpteyqktfbxIwn1T3kvMp/FLNofi3iSEXl1aF7GFvr9 n6VovqKaXYLZxpkbiI0sAFAt1mdIgW1QpwvaNlU9fFeiC66xnlW2sl3vgSfFJ2kg 18w6N5EzILMZhj/IsgiN+wtu7BAnLHM3z6/dHGO3P5FqRm2+qH+0N6fcMjHjbS1Z Xnearm77zJf6iRlJSJY40KFvM8y249LhFZhuONcZ5WhrIyTm0X2/IAxUd1Ggls/P 1GU0XVxIgyEgNmqsjzAXoNQpiv3Z8jD+SNsKQ2/vWvd2TW5F39qiCzTG3pvQlBFj 6ZMB+z/HgzJgwYT+uFhs7d0xnGmCmoeKMhNffTvDqCGreSxeYQh8SOSmlqrOOIBP z8LCV1+Tq4TgVqSApYwtXWY7qx9peK//2wRJRvXYL007NvR+2CEjqtmId9qFq1zv ihiXg1Suh+QFf1CqFDofpW5t/LIMsjbj5woMIxPYDb8lXvH4E1/yNqJIizHjKIIJ WXkExB0Wu/7ySteVmgdl1b8fN6pXMhVUxO/g94nubeurusEKzXE7OjkXG2+qEmft Jf499jvKJ1UWR9ZfbyJZIKvfUHZc1IEjfTDvclhdo4UzSJHg
    =kTkM
    -----END PGP SIGNATURE-----

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