Arch Linux User Repository

If you're getting error like this on login:

Login error: Authentication error: code 400 (API_ID_PUBLISHED_FLOOD)

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.

Can you change tdlib from depend to makedepend? The plugin is using the static C++ interface.

Got around to add the patch and test the thing with it - works fine here as well, with current tdlib 1.8.2+ from git.

patch --dry-run -tNp1 -R ... || patch -tNp1 ... should hopefully match the applied PR in the future too, instead of breaking the build after that.

Thanks for pointing it out.

@mk-fg yes it does make it compatible. I can confirm it works, and I'm building on top of that PR instead of sticking to tdlib 1.7.9 as a solution. Hopefully it gets merged.

Presumably it makes tdlib-purple compatible with current tdlib?

Probably a good idea to add if it fixes that tdlib version annoyance, at least until they eff-it-up again.

Though it seems like a bad idea for -git package in general, as it'll probably either get merged or broken soon enough, and this shouldn't be my own fork of the thing.

@mk-fg what about integrating this PR as patch meanwhile:

• https://github.com/ars3niy/tdlib-purple/pull/154

Hi. Will add conflicts/provides, thanks for the suggestion.

if there is a version restriction to the dependency telegram-tdlib, then I suggest you add it to the depends array, like depends=('telegram-tdlib>=0.7.9' 'telegram-tdlib<0.7.10'), and poke the maintainer of telegram-tdlib-git to add =${pkgver} to the telegram-tdlib entry in the provides array.

Yeah, that's the problem with adding such dependency:

• Has to also be in telegram-tdlib-git
• Have to be manually updated whenever it changes in telegram-tdlib-purple

Since this is a -git package, upstream telegram-tdlib-purple can change anytime, and I don't monitor changes there and only build it myself something like once a year, second thing would be a hassle, especially since upstream telegram-tdlib seem to be breaking API in minor versions on a whim (which is far from the strangest thing about it).

And since I won't bother tracking these versions in PKGBUILD, there seem to be no need to bother with telegram-tdlib-git tweaks either or make its ad-hoc copy for specific telegram-tdlib-purple commit ranges.

I think the latter task would fit a proper non-git telegram-tdlib-purple much better, so if you want to maintain more reliable package like that, I'd suggest creating it, and bumping both release version and dependencies there manually to track those in upstream, unlike this generic git pkgbuild.

Dear maintainer,

when this package needs telegram-tdlib version >=0.7.9 but <0.7.10, and that package is not available, I suggest to create a package telegram-tdlib-0.7.9 that specifically provides that version and upload it to the URL.

Dear maintainer,

if there is a version restriction to the dependency telegram-tdlib, then I suggest you add it to the depends array, like
depends=('telegram-tdlib>=0.7.9' 'telegram-tdlib<0.7.10'),
and poke the maintainer of telegram-tdlib-git to add =${pkgver} to the telegram-tdlib entry in the provides array.

That seems to be the clean way for dependencies that are version specific.

Can you please add provides=("telegram-tdlib-purple=${pkgver}"), conflicts=('telegram-tdlib-purple')?

Thanks for maintaining!

I'm getting a bunch of linking errors. A small sample:

Probably incompatible tdlib version - see pinned msg above.

EDIT: I'd also suggest doing "rm -rf src" to repeat the build from scratch, if you maybe had stuff from previous build cached there, but otherwise no idea.