[Rebuild] forkgram about packages HOT 7 CLOSED

@xiota indeed they are, somewhat unfortunately. If they'd all have feature parity it wouldn't be such a fragmented mess. I'm guilty of using forks that randomly break and don't always have the best update frequency... but they just work well and feel nice[when they work]. It is a nice convenience to provide them.

from packages.

> forkgram-4.8.1-1.3-x86_64.pkg.tar.zst
> forkgram-4.8.1-1.3-x86_64.pkg.tar.zst.sig

ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().

Might have been a sigkill in the builder, this package is consuming quite a lot of RAM iirc.

from packages.

I'll keep trying to fix them then. But drops may be unavoidable when the methods stop working.

from packages.

Last build: 4.14.3-1 on 2024-01-04.

from packages.

Build failed. No idea why. forkgram.log

ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().

from packages.

@xiota, @dr460nf1r3, this happened again, after qt6 update 6.6.0 -> 6.6.1

[remorin@chuwawa:1 ~]$ Forkgram
Forkgram: symbol lookup error: Forkgram: undefined symbol: _ZN14QReadWriteLock16destroyRecursiveEP21QReadWriteLockPrivate, version Qt_6_PRIVATE_API
[ble: exit 127]

from packages.

There are a lot of telegram forks/clones. They're fragile, resource intensive, and difficult to fix/build. Are they all necessary?

forkgram has been rebuilt:

$ pacman -Si forkgram | grep 'Build Date'
Build Date      : Fri Dec  1 12:34:17 2023

from packages.