Added -DCMAKE_POLICY_VERSION_MINIMUM=3.5 as a workaround as cmake suggests. Build seem to work, so probably good enough for now.
Thanks for reporting.
Git Clone URL: | https://aur.archlinux.org/telegram-tdlib-purple-git.git (read-only, click to copy) |
---|---|
Package Base: | telegram-tdlib-purple-git |
Description: | libpurple/pidgin Telegram plugin implemented using official tdlib client library |
Upstream URL: | https://github.com/BenWiederhake/tdlib-purple/ |
Keywords: | bitlbee libpurple pidgin tdlib telegram |
Licenses: | GPL2, LGPL2.1, custom:FTL, custom:PIX, custom:RPD, custom:SKIA, custom:STB |
Conflicts: | telegram-tdlib-purple |
Provides: | telegram-tdlib-purple |
Submitter: | mk-fg |
Maintainer: | mk-fg |
Last Packager: | mk-fg |
Votes: | 10 |
Popularity: | 0.014798 |
First Submitted: | 2020-06-27 20:23 (UTC) |
Last Updated: | 2025-05-30 21:14 (UTC) |
Added -DCMAKE_POLICY_VERSION_MINIMUM=3.5 as a workaround as cmake suggests. Build seem to work, so probably good enough for now.
Thanks for reporting.
Looks like this package has been snagged with Arch's CMake updates, which have removed support for CMake behavior pre-3.5:
~/.cache/yay/telegram-tdlib-purple-git/src/td ~/.cache/yay/telegram-tdlib-purple-git/src/telegram-tdlib-purple-git
HEAD is now at 3870c29b1 Update version to 1.8.21.
~/.cache/yay/telegram-tdlib-purple-git/src/td/build ~/.cache/yay/telegram-tdlib-purple-git/src/td ~/.cache/yay/telegram-tdlib-purple-git/src/telegram-tdlib-purple-git
CMake Error at CMakeLists.txt:1 (cmake_minimum_required):
Compatibility with CMake < 3.5 has been removed from CMake.
Update the VERSION argument <min> value. Or, use the <min>...<max> syntax
to tell CMake that the project requires at least <min> but has been updated
to work with policies introduced by <max> or earlier.
Or, add -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to try configuring anyway.
This should be a simple patch to change cmake_minimum_required()
unless upstream explicitly relies on some old behavior. I tried a couple of clean builds to remove stale sources and it's still present, so until upstream updates their CMakeLists a workaround for building for now would be to patch where possible.
Thanks for this package. Voted :)
The latest iteration of the packagebuildfile works like a charm :)
Updated PKGBUILD as mentioned, it seem to build with newer tdlib and works for me, but dunno if it will for new users - please report if it doesn't, I'll probably mark this as outdated/abandoned if that's the case.
Source isn't updated. Same thing have also been reported in purple-dev telegram group, so it's likely not a fluke. This doesn't seem to happen when I reconnect, so maybe only happens for first-time app authorizations.
There seem to be a fork updated to build with more up-to-date tdlib here:
https://github.com/savoptik/tdlib-purple/
(also mentioned here - https://github.com/BenWiederhake/tdlib-purple/pull/6 )
I'll try switching to that repo and pinning build to a specific commit from there - might resolve the issue, if it builds with more recent tdlib.
Authentication error: code 406 (UPDATE_APP_TO_LOGIN)
Seems like this package is out of date, or the source isn't updated?
I think it's not required in a sense that its on/off status is auto-detected at build time (unless you use -DNoVoip=True), and don't think that's what optional dependencies are for - they are for stuff not required at runtime, so it'd seem to be a wrong and misleading thing to do.
There is a minimal version of this PKGBUILD here: https://aur.archlinux.org/packages/telegram-tdlib-purple-minimal-git
Which maybe you can use, it has -DNoWebp=True -DNoLottie=True -DNoVoip=True
and no corresponding dependencies.
Otherwise I think it'd have to be a separate PKGBUILD like that -minimal
one (-novoip
maybe), and idk if adding that on AUR with such packages is a better idea than maybe you removing that from depends=() in PKGBUILD or making some AUR-build-tool do that automatically (they probably have hooks for that).
Can the libtgvoip dependency be made optional? It doesn't seem to be required (it's just for voice calls) and it's currently broken.
You seem to be reporting an issue against wrong package - there are no such files here.
Pinned Comments
mk-fg commented on 2021-12-07 14:44 (UTC) (edited on 2023-09-23 21:26 (UTC) by mk-fg)
If you're getting error like this on login:
Check https://core.telegram.org/api/obtaining_api_id URL, for generating your own api_id/api_hash values (only a couple clicks), and specify those in the plugin parameters.