• Is there a point to retaining src:pth?

    From =?utf-8?B?0L3QsNCx?=@21:1/5 to All on Sun Nov 17 03:30:01 2024
    Hi!

    src:pth has been gone from testing since August.
    There are no rdeps and no rbuilddeps,
    and only FTBFS bugs since like 2012.
    I can hardly imagine a point to Pth at all in 2024
    (or any time after ubiquitous pthread support),
    so it reads to me like an easy QA removal.

    But, this seems incongruent with the
    inst~15000 + vote~15 popcon
    (admittedly, with a peak of 50k, that may just be latent).

    What am I missing here? Is there any reason for any one
    to install libpth{20,-dev} at any time any more?

    Best,

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

    iQIzBAABCgAdFiEEfWlHToQCjFzAxEFjvP0LAY0mWPEFAmc5U00ACgkQvP0LAY0m WPFqAQ/+Ps4NIREzIa15bAUufvu48fYVheeUNLHN0w1VBp1u0SIgfeznYNbgUB43 deiCxijuw3gd41EhxymxIOGVcFb5nSNOwk+e7qEqBJEoCumnX+fNFE3eo2vz2cz7 NlQzwIGfjCeptJQelS8y9NMIjyC7GpaZXB7Tcy5chD6+U9KVAQMnD89ALHfyic17 iaWwIoE9fM+zPFZm51ZFxLrmQWnwV5MG0QBQtf0QUtygM1gzmkyCQKiyJyNbvTjE RJTJMUrFMpTYUiUC83+DXlSudm02LAyD1z0k4B8M4POmJPMHqRDgLTh1F/0zkAF+ yGSKgU/0sl6NZX6bJU+GhkCBlTVp+FETRb0KPOdSfhs/cOtX8tmYDAzbLWcI82b6 APoWz7QUNKZhyW8XRbofDAACU8bU+xECMMRK853HUHY01X+KDJk/9M/wMWplCUHp TyuVIZQmgpx1YGyBGvaQKY5qjgeYzEM2f/St7MFOXv+KYvwnDeb3G0cHVrVzuIZv grHSnSHJwNkaOPn5i/+o67351OuF7fj3jtHVbePGplsPq62w+Y+P2EPQMV3icUgY sLBKhlEn6/3imuXDlmRjUItf3lAy1NqeAeQ//B3Xyaui7kA0zjbEPqI45ZanBwwV 7iuMPf1gI0ZWR60QBtTbCxsnLd2pQxAi4XOr1SnxbaxmS9a74qs=
    =u5w3
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ben Hutchings@21:1/5 to All on Sun Nov 17 11:30:01 2024
    On Sun, 2024-11-17 at 03:22 +0100, наб wrote:
    Hi!

    src:pth has been gone from testing since August.
    There are no rdeps and no rbuilddeps,
    and only FTBFS bugs since like 2012.
    I can hardly imagine a point to Pth at all in 2024
    (or any time after ubiquitous pthread support),
    so it reads to me like an easy QA removal.

    But, this seems incongruent with the
    inst~15000 + vote~15 popcon
    (admittedly, with a peak of 50k, that may just be latent).

    I'm not seeing those numbers. Maybe because pth had an ABI bump for
    time64 and libpth20 is no longer on the graph.

    What am I missing here? Is there any reason for any one
    to install libpth{20,-dev} at any time any more?

    GnuPG once used pth, but switched to npth over a decade ago. As
    recently as bullseye, pth still had some significant reverse- (build-)dependencies:

    $ grep-dctrl -FBuild-Depends -sPackage libpth-dev /var/lib/apt/lists/deb.debian.org_debian_dists_bullseye_main_source_Sources
    Package: gcc-9
    Package: libdap
    Package: pianobar
    Package: unicon
    Package: zhcon
    $ grep-dctrl -FDepends -sPackage libpth20 /var/lib/apt/lists/deb.debian.org_debian_dists_bullseye_main_binary-amd64_Packages
    Package: libgm2-0
    Package: genometools-common
    Package: libpth-dev
    Package: zhcon

    but it does seem like it can be dropped now.

    Ben.

    --
    Ben Hutchings
    If more than one person is responsible for a bug, no one is at fault.


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

    iQIzBAABCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAmc5w4wACgkQ57/I7JWG EQkRKhAAtGEh80lng87ZrqVPoYhIrMLTW/nt6JXkLuHAnATE7nAiUyQ2jKxgYeFt RzFAQfw99eVewgTvC0hkhVuB9O7nd195bgq2qGxtH07llaR87YuNBO3shsLwFo2C mfHH2B6BN2wOoA0Xt/vNfhupqf7JjeX4AFMISj9qFuMyyHMAc4WLwRH2AEoCHcMS vjLie2pYggiBOHYjHJc3yKTQPB4rizDgfD4NFnbMNcvOMa1V9x1DONqZlWcRAqoy YAOHv58FD7Es0TDHVDDnOBYlP5h4yyPmuRk8SxI3wwous3qKmdVM7I7JXKhGIMac yzkNJ2as61q8b6eS7yoNAFFAKF42Jw+nNJ0L2ursCdPC+zvfuK2A42UuvCj6eJD5 Hg7xKGImRoTiFtYQazD+1crf4eeUAGMXRSNWxmbMDnprwZJu5YxNkkGlO2Mi6ADL iHo0pOBwnmfKNVb2Kst9ikcHss0g6RG7fgMMedKji7UbsPofSbyKRwBDNHVYl0p2 p+NGs0VwWO1eLFfanm0jUmQ0fT4EVonVFGlYqleugsuE6ZaKUiY67EFK87m22x6r xFz4gvU9WSOxNEUNqb2niaUaui+sgaY1BdAFTPmAEmWgfUiGPLqKIEuga2in9D2K uA8KASfoYewSzqro9fOKHr3/bH4jr1VQC4Px+d3DGcLPZFqWY14=
    =MS44
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?utf-8?B?0L3QsNCx?=@21:1/5 to Ben Hutchings on Sun Nov 17 15:40:01 2024
    On Sun, Nov 17, 2024 at 11:21:00AM +0100, Ben Hutchings wrote:
    On Sun, 2024-11-17 at 03:22 +0100, наб wrote:
    src:pth has been gone from testing since August.
    There are no rdeps and no rbuilddeps,
    and only FTBFS bugs since like 2012.
    I can hardly imagine a point to Pth at all in 2024
    (or any time after ubiquitous pthread support),
    so it reads to me like an easy QA removal.

    But, this seems incongruent with the
    inst~15000 + vote~15 popcon
    (admittedly, with a peak of 50k, that may just be latent).
    I'm not seeing those numbers. Maybe because pth had an ABI bump for
    time64 and libpth20 is no longer on the graph.
    Had to dig these out of the graph manually:
    https://qa.debian.org/popcon-graph.php?packages=libpth20t64+libpth20+libpth-dev&show_vote=on&show_old=on&want_legend=on&want_ticks=on&from_date=&to_date=&hlght_date=&date_fmt=%25Y-%25m&beenhere=1
    https://qa.debian.org/popcon-graph.php?packages=libpth20t64+libpth20+libpth-dev&show_vote=on&show_old=on&want_legend=on&want_ticks=on&from_date=2020-01-01&to_date=&hlght_date=&date_fmt=%25Y-%25m&beenhere=1

    What am I missing here? Is there any reason for any one
    to install libpth{20,-dev} at any time any more?
    GnuPG once used pth, but switched to npth over a decade ago.
    That historical context was what I was missing,
    and certainly matches the peak and cliff.

    As recently as bullseye, pth still had some significant reverse-(build-)dependencies:
    This looked like a scary prospect,
    $ grep-dctrl -FBuild-Depends -sPackage libpth-dev /var/lib/apt/lists/deb.debian.org_debian_dists_bullseye_main_source_Sources
    Package: gcc-9
    Package: libdap
    Package: pianobar
    Package: unicon
    Package: zhcon
    $ grep-dctrl -FDepends -sPackage libpth20 /var/lib/apt/lists/deb.debian.org_debian_dists_bullseye_main_binary-amd64_Packages
    Package: libgm2-0
    Package: genometools-common
    Package: libpth-dev
    Package: zhcon
    but from the changelogs and relevant bugs,
    it looks like all of these specced that by accident as a left-over.

    So it was deeply vestigial even in bullseye,
    and the maintainer trimmed it off most of the way.

    but it does seem like it can be dropped now.
    https://bugs.debian.org/1087708

    Thanks,

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

    iQIzBAABCgAdFiEEfWlHToQCjFzAxEFjvP0LAY0mWPEFAmc5/v0ACgkQvP0LAY0m WPG2bQ//elIxqpoSoE+sV6XsWfBJJITlp/LUPJrnJ3pr+qWOmQYXT/hdhsMNDVB6 4Lp8/jLuGfU8h8TCp3EowBT+hkg1fZZS+nU8CO5meQhAkEmgImH7e5zawlcTQBEa PhcYcRG1TcrNqm6Pq8VP0lJLU0PPV88RNf3QOC6eXYI+3iw3IBdA0H28HPL1K57L 6VkRqz+DUn+/RuWGPOp8eCRSCI/Cw7tbTrX2dPccXsirPVB0v3BsrmtGy4VS4MNW pEvzl5HrGjMA52/LybgLqAdyJvGx2q5NPqrdxesSSWRUI61V9dR/LS/1sOCC/0xN tV596E5/EAqwU6Pt4Yya0Oh9aixfCtAmw6A3YpB/nv/lvn8H3cgMTeaKdffYtrms 31z9X7JViD3pJLl4Acla/OTEGJfvD4BlWWNezzpvuGeWM7tdIo19MRO3/NzSurl4 6+RxBmZ/9sTv7NpCecW3df/oAQuMNKIaYPfW4Eb1IpEnKRdSiceQBkSQAgJrZbKc qUVWMDakjYTGnZ3piLh7RiuT0EGy0ZUYFDH8zZ29cFmT4h2cf5LxHFTfliHZJg5T D172e4aUPr3DXGqAVTXTBz15McwKNZl7vp6y5fXSf0hD40egMkIGpX1SlVcXgbHW Oys4HgjWpe3u0KUIqaeLTnt0qVQw6FnpbG0gPxSLTneWjW5eNRg=
    =ue4Y
    -----END PGP SIGNATURE-----

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