1. Forum
  2. Usenet
  3. LINUX.DEBIAN.DEVEL

  • Can anyone help with telegram-desktop?

    From Salvo Tomaselli@21:1/5 to All on Mon Mar 17 00:03:57 2025
    Hello,

    I am a user of telegram-desktop.

    The maintainer seems MIA.

    The package has 2 RC bugs and is FTBFS.

    Packaging a new version at this point doesn't seem feasible, it depends on
    some things that are not already in debian and I'd like to avoid the NEW
    queue.

    one of the RC bugs happens in a file that gets generated during the compilation and then fails to compile, something about the MPRIS DBUS interface.

    I failed to fix it or even to disable building the feature.

    Is anyone else interested in fixing this and able to help?

    --
    Salvo Tomaselli

    "Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno."
    -- Galileo Galilei

    https://ltworf.codeberg.page/
    -----BEGIN PGP SIGNATURE-----

    iQIyBAABCAAdFiEEQnSLnnbYmXmeH74Us6fPDIAYhs8FAmfXWN4ACgkQs6fPDIAY hs/1hA/44RiSWpnv+2uZnngQBQBdQ9qb0RaGUoDlabHqjcMM+GhoXo3PGJtDy5Iy PBS/97MzjCjWK22pt1aXBndSahWiauFM3uNSqLDFWkMUo7R5/VS8ymSAB97kToHO 7By1RtyGdW0zbPr+3WmjZDb3AEZmPa5md796JqNGRO6l/A8igprnyLzCxfAeCoM/ H6tfLPqeEAMLPTEWV2nlQ07mpTiWpYrUlYZtmuRCf25oYl5VLoCgPp0y1b/vfEB8 5F3QDbJfye6uidkRKme9pEhiSirG26w+KcGOFu9wduipWIWHoOysd2P8pKbj26yu 8F4bokf0654885WZllfw5pIoinCckzULj3fL2fAsFtjVjUX36pW6dbR7qy/zis9z SJNPCWTL2xzGLA1IamRWpymEwS82ykXgvXGLe9oiHH8Dy0zpTGFuuRAnMdHA7i83 ZK/hYxnXnQgy+5H36sHjBKd0Zra5E2v01q3vRc6D80FUNtKR47QESUx4lyMm9Llw IE8W9GDbV+F1KRpPZQfFZxH6Ps5bcSAP0iBahZrhEMq45g9I8Zps2KyRwNG+uGJz dVs3d8AKv/HiAMSB6zH86vOoTQjkJleemKXwtIsdZmON5FjAM51D6dp/fgbidbTt rPKRiZKMYERKcxjB9R8s044uZhAe0xWVe3u70NAKKZ8WlKqXKw==
    =eGSF
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrey Rakhmatullin@21:1/5 to Salvo Tomaselli on Mon Mar 17 07:50:02 2025
    On Mon, Mar 17, 2025 at 12:03:57AM +0100, Salvo Tomaselli wrote:
    Hello,

    I am a user of telegram-desktop.

    The maintainer seems MIA.

    The package has 2 RC bugs and is FTBFS.

    It also depends on cppgir which is RC-buggy.

    I prevented removal of telegram-desktop from testing 4 or 5 times over the course of 2024 (by fixing either it or one of its deps) but after the most recent set of RC bugs I gave up and switched to the flatpak version. I was also curious if somebody cares about it enough to fix those.

    --
    WBR, wRAR

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

    iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmfXxAItFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh XiEP/RVYxwILMFxP6Rdvk1npG6tfLW+8YkepBun/Sj6QI4AKwPpIyVuXoyiDKCWA l+tJFI7nKETHjx0EPl3rxxB8U4Hm/OVgyI1/I+WPD2oasP1H5UJ1DSI6pmGfsL2X P6q3xMK+6O2Ndrj7gs0NaI62Qc+yqlSZFqgOKQhwI06DydAMSzYn1FK4KOPSo0Rw hAruZ5cabu+JUXJGZ43Q/xGzrroQ3iYzSllO6KvX9OC7G3EZJlX70s4g3ylInpJd Nv9u6g5epNqELPO1BGvL2mWwrXH/EkookYUDGI3ftjnIlqe50V1zPf6kdBqrtxnY AEXKw7td9nAesCwFPfpDZs9hwjHoqd46sHZJLHwzGc3XatLUXZKF+cAaj7D1XlQ8 XeZMVyVPZ8c0UmD/lEpNqIm6CR9b//X55Y2iI41c6ufLukwhidN/VP5I3GzcvFwM erk4aoG4PV3d/uXSfXS+KjtUDxCXwwwH37gWELdke2zBo2TZ/uD3YIWWWc5+ogfE wVmWUJ2VAaWhhw/pm+0/5L+zoVoNEGjvrIv40wd57TQBiDjhKbzAUfjsqi5Bk8QH 6+e7sVd3VlFL3YaSjn1j5mUX8N1/HZm/Uj4MtnfMI1eCe0l43saOmgLmb2OgXFFN JCkp9cfP3zFGWIGzMB1iz7ypcxJVDaV9o6ljldnWKPeUkJRG
    =2amo
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Wookey@21:1/5 to Salvo Tomaselli on Mon Mar 17 13:50:01 2025
    On 2025-03-17 00:03 +0100, Salvo Tomaselli wrote:
    Hello,

    I am a user of telegram-desktop.

    Is anyone else interested in fixing this and able to help?

    I'm a weekly user and would very much like it working. I'm a bit short of tuits, but I'll try and take a look and see if I can help.

    Wookey
    --
    Principal hats: Debian, Wookware
    http://wookware.org/

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

    iQIzBAABCgAdFiEER4nvI8Pe/wVWh5yq+4YyUahvnkcFAmfYGjYACgkQ+4YyUahv nkdZVw/+NA5MZGzLVHEzzWLunUq2jxFiBl2SoeCIEs48/dr/LMMtYxdU08zxYbKz GTig37VpggLxEIgyh2tGHc/ohnMUlPwfb95bgXyq+iXXLIoVP4CEauetp9UvphFz 7My3goAcQpbLvCd61NN/PG2pZnPJWyhQtRwAE1P2ZwQEd7BRJR9/aBV3VTXzp3Xd O+zhDwWV/ntpsRLi5QInQOw9ubuxai80uLnIRKiE6IsvZ8i/R6T1aj0s0lSW4PIc aHDMNGF0HEbl18rBI7xJfIKeq39/KlXQd36vpMVOxnLN+HQcA5T1tENsjOhDqxpE OiPx4TCpWs7iVGOC5QgeF4eKrtyY7DibXXmLcPWdhwKaIEt95G5Fv85AKrIF0t3m IUohKEaH3nonVeHFK6AVu/7fu4QwWVvzhZGYs1TyszjqnKyjXKonc/vjyby3zKMP 8KbseZOEVIxH2YUiiUHpjL2M/11MBuLb1P31VssZD6VitcWuMiPhiOf3DxYfdWT4 aLXywFpYmGoNxNgPq2bhYFfDD+d4mMpluEmBKzhXz93N2NTOSY5udUHMQ8Fmh3Ym YwZ4TMoiox5bFi9pK+M/Gpxp7rixIDgxqA8mdK/+yzlybJJv2Gg6Db+qlPPOe53e Js0yJoRqc/cnGo7So/8eURm8svPsVdrLY81knp2zMSlUJb7ZFa0=
    =gpJI
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Salvo Tomaselli@21:1/5 to All on Tue Mar 18 07:23:33 2025
    Copy: wrar@debian.org (Andrey Rakhmatullin)

    I was also curious if somebody cares about it enough to fix those.

    I only found out very recently that it's not in good state, because I was installing debian 13 on a new device and couldn't find the package, so I figured
    it must have been removed.

    I care but the current ftbfs seems to be about some external library that changed API, from what I can see, and the code calling into that is generated at compile time, so it's not a simple matter of patching a file. That's where I got blocked really.


    --
    Salvo Tomaselli

    "Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno."
    -- Galileo Galilei

    https://ltworf.codeberg.page/
    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCAAdFiEEQnSLnnbYmXmeH74Us6fPDIAYhs8FAmfZEWUACgkQs6fPDIAY hs/trhAAtZaLPEI3Mcif6/+n8X+zN5cxb0c9KDmgKyiZv8jUnAq68fNAG0sfN5k8 734r8a/KsgZ8FcPCgRoboKen++gBHKaJT9KnjT8dgKMJEK5bMXaj6PB/U1Xck5Hk zxl2rtEbrCviXnE0stPhZMJ3v3iyCBiBCZTuEQSJjKLUcFBCLg9kCe5xGTydq3xu j84CIxnNrUNKggRXDK3d8O4FZGysE+TCD1CHtXdSqE++xjM5bZseUyRk/QgedqN1 u8DHdDFyEu4Z3Kg+smev+GSPx3WRvVxtYRt7FEpJa3vcByNqcI+cbKvYGjAvBeHz BoNxZYh3rPyY1NTShIcbFEC+GCd7fAmcWEahi8K2y5dZphF68IINDB+dZssdoAgf GiaU8s8F0w4cYz/1a2P2szX26rHcQgWwFaM/bPe1JT+JTkVSbgfE4HHNMIMuha5f snLWbs4kQ/8KkFvOWdEBThsbTbzjkNoGQa4O10quwiqY2YFtsbhApMiVR1ruWxpc WOdZVV+vhc5ltKKkbe+9MVYs0+f5GrUIG9kZV5QLjGYvNKPbuYmQfo884KnRw55N kEFGJXmJb8/CfP9yMly3cuiUyeHQoUFtkgTMV/0eCFCGQkCA2k+Gi38SW4IJGGo7 kBKljjAWPutv7y+JAQemPuteYBDKfoOHootpRzWaHPjnAnSgFok=
    =RhEb
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mattia Rizzolo@21:1/5 to Salvo Tomaselli on Tue Mar 18 11:20:01 2025
    On Tue, Mar 18, 2025 at 07:23:33AM +0100, Salvo Tomaselli wrote:
    I was also curious if somebody cares about it enough to fix those.

    I only found out very recently that it's not in good state, because I was installing debian 13 on a new device and couldn't find the package, so I figured
    it must have been removed.

    For what is worth, I am in contact with the original maintainer, who had
    some health problems last year.

    I contacted him just yesterday, but unfortunately he said that despite
    his interest he is unlikely to start working until mid-April :(

    --
    regards,
    Mattia Rizzolo

    GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
    More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'`
    Debian QA page: https://qa.debian.org/developer.php?login=mattia `-

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrey Rakhmatullin@21:1/5 to Salvo Tomaselli on Tue Mar 18 14:00:01 2025
    On Tue, Mar 18, 2025 at 07:23:33AM +0100, Salvo Tomaselli wrote:
    I was also curious if somebody cares about it enough to fix those.

    I only found out very recently that it's not in good state, because I was >installing debian 13 on a new device and couldn't find the package, so I figured
    it must have been removed.

    I care but the current ftbfs seems to be about some external library that >changed API, from what I can see, and the code calling into that is generated >at compile time, so it's not a simple matter of patching a file. That's where I
    got blocked really.

    There is a chance that the fix can be extracted from the current upstream version. Ideally, of course, the new upstream version should just be
    packaged, but I don't see this happening without the original maintainer unless someone spends a really large amount of time learning the package
    and updating it.
    And there is that problem with ARM symbols, which happens in some
    low-level symbol manipulation script written for the Debian packaging.
    The cppgir problem could be fixed upstrea, and it should at least be
    easier to update that one.

    --
    WBR, wRAR

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

    iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmfZbc4tFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh rf4P/23qlVyZREERLg5WBIvocvbmsjX9i1RBjfqzNGGj3pEni2qKqoM2Ms4imiNv MvAPdlPSEaZLVqE5WF+Y2VSAWun1Y/NELmbJxLIq9NFcidE+xj5nXC9lbw1yP6c5 gUchE5vg7XX5pWHEftZ6hEXSCpWY+XrIFK+zv74j+/KNXVfKjjyLmj3dPoVpewsv DhIle9U/0cxkGr3Q05gQD0U+j1AOkq5giNjacZGNXbnFs0dtVhXpwnig4kdLkrTG 57NtGhX3bfjz41kyWm8gFZwETT+oIKAE3g6wxgb7YQ0UScGeY4YKx/tjYZWfzqMC 4zQJ3IS1MY/8zeC5mWqlPuCRNe0FEdoby1XcF27L9FV27Bt/AyPdIw9PD9pVxPFN xsJYw6rf5isUWC9fLovgnrPWfYWrHyfp8qwLp0ldF6djasQu44R+KoAKVuaTjyuY BlP3dj83VgAo1VI68XHBGXd4+aWXnNs3jnLmGXNKOUuFI73Ug5nVH8l3tuxxcKUp pjcr7gcF/9Y1qCJIrFwBMAbpNdNw7NicvXYE3ZMKDXcfxoQYiogU7o+k/PZ7qp85 lO+A7SX3JIHvRYhiWuYQli0vWdPMKJ2hcZX5BRcht3+W2KTQv/JGkUkkImLouOZQ pJTihaRj2MMrdmtVSttBdEzVswAEAzFfonZlDwWkZcNa5zGB
    =96LJ
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Salvo Tomaselli@21:1/5 to All on Tue Mar 18 21:18:16 2025
    Copy: wrar@debian.org (Andrey Rakhmatullin)

    There is a chance that the fix can be extracted from the current upstream version.

    True, I'll have a look next Sunday I guess if there's something

    Ideally, of course, the new upstream version should just be
    packaged, but I don't see this happening without the original maintainer unless someone spends a really large amount of time learning the package
    and updating it.

    I tried, but other things needs to be packaged as well.

    And there is that problem with ARM symbols, which happens in some

    I've seen failures on 32 bit architectures after the t64 transition. I'm inclined to just drop the architecture if the fix is not trivial. I don't think telegram-desktop has any 32 bit ARM user.

    Best

    --
    Salvo Tomaselli

    "Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno."
    -- Galileo Galilei

    https://ltworf.codeberg.page/
    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCAAdFiEEQnSLnnbYmXmeH74Us6fPDIAYhs8FAmfZ1QgACgkQs6fPDIAY hs/dGg/+IB4pB85BcGsKbZbiKt7XumF/dbYhItcipxqqWX5sACRwEnfuaEjUZh5b vTCGQMyqR3emhWt+ZnVsMKK19jCU6lhEL/CYa0YagL58sd+naJkwqHTi0wgK5oKr klMULJGw/HGuPm9c35ICvK+RyGLeyVIC8VEvCJjHnqZqJWNk8DZP5FcGkb1pZri3 fa1FgyrMC+99KiIscBc3fPUiO640qRHg72DvrM0jqShTw752qtB6MoV3gtDGbhXE Eoh9TKazBhvpX0L+XeobDLCJfySuGjZNZKV7PpA7Vn0Zw6n1GP265H5sDChNHoc8 ifWIrCY1c3b1p1vARvqhIm9mQOtIvnbMa1O+YiNv5/Cify71hN4gisckRmJJM//w zHpq8e+wyg7HTArg7Q0NPeyGTPZrIYt5cV1QFBZrygMehAxs0BZB7ec5w3pGEVCT pBcgGdmAcDLpUHgYT0v/nFHtUiXUnzMj9UCU5uTmB2inkDvtZgg4tdUYmxiuS6ej huKEwHQH+F7KJHbhA1dAsZG19DspPMlvNUAZhObQ6JtiF7EQFI4uwD9BBd+FNQFt Xswkv6UC4swbXqP++O/TrD1y3Wzeu8vM23z83Qoj2mWFHc0HVLbdECTvSIchg2ii 9TSPGb0JB5flB+CCj9032kP5UMGPDxgGa9kuPE3X1dKggbNjLUc=
    =ZVN2
    -----END PGP SIGNATURE-----

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