Package Details: forkgram 4.16-1

Git Clone URL: (read-only, click to copy)
Package Base: forkgram
Description: Fork of Telegram Desktop messaging app.
Upstream URL:
Keywords: forkgram telegram-fork
Licenses: GPL3
Conflicts: forkgram-bin, telegram-desktop
Provides: forkgram-bin
Submitter: ptr1337
Maintainer: ptr1337 (sir_lucjan, SoulHarsh007)
Last Packager: ptr1337
Votes: 3
Popularity: 0.98
First Submitted: 2022-02-05 16:05 (UTC)
Last Updated: 2024-04-03 18:28 (UTC)

Pinned Comments

Latest Comments

1 2 3 Next › Last »

dreieck commented on 2024-04-03 08:07 (UTC)

Conflicts on telegram-desktop needs to be put back. Attempting to install after building in clean chroot:

Maybe it makes sense to rename /usr/share/dbus-1/services/org.telegram.desktop.service to /usr/share/dbus-1/services/org.forkgram.desktop.service and /usr/share/icons/hicolor/symbolic/apps/telegram-symbolic.svg to /usr/share/icons/hicolor/symbolic/apps/forkgram-symbolic.svg, and change the references in the code accordingly?
(After all, the logo is different anyway.)

If not, then it maybe would make sense to make this a drop-in replacement for telegram-desktop, providing a symlink to the same executable name as telegram-desktop and same other services (if any) and shared libraries (if any), and after doing so adding telegram-desktop=${pkgver} to the provides entry?

xiota commented on 2024-01-27 06:19 (UTC) (edited on 2024-03-18 06:12 (UTC) by xiota)

Conflicts on telegram-desktop needs to be put back. Attempting to install after building in clean chroot:

forkgram: /usr/share/dbus-1/services/org.telegram.desktop.service exists in filesystem (owned by telegram-desktop)
forkgram: /usr/share/icons/hicolor/symbolic/apps/telegram-symbolic.svg exists in filesystem (owned by telegram-desktop)

SoulHarsh007 commented on 2024-01-02 14:29 (UTC)

@dreieck Makes sense, I'll remove the conflicts array.

dreieck commented on 2023-12-19 20:54 (UTC)

Why does this conflict with telegram-desktop?

The executable is /usr/bin/Forkgram, not /usr/bin/telegram-desktop.


Umnik commented on 2023-12-01 08:19 (UTC)

Not started

Forkgram: symbol lookup error: Forkgram: undefined symbol: _ZN14QReadWriteLock16destroyRecursiveEP21QReadWriteLockPrivate, version Qt_6_PRIVATE_API

FabioLolix commented on 2023-09-07 10:13 (UTC)

@archkde_combo please use 'flag out of date' instead of commenting for that

archkde_combo commented on 2023-09-07 10:09 (UTC)

Please update

vad commented on 2023-08-19 00:04 (UTC) (edited on 2023-08-19 00:05 (UTC) by vad)

I have caught missing deps:

Program mm-common-get found: NO
Message: Maintainer mode requires the 'mm-common-get' command. If it is not found,
install the 'mm-common' package, version 1.0.0 or higher.
Program mm-common-get found: NO

glibmm-2.77.0/ ERROR: Program 'mm-common-get' not found or not executable


CMake Error at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
  Could NOT find Boost (missing: Boost_INCLUDE_DIR program_options) (Required
  is at least version "1.58")
  1. extra/mm-common
  2. extra/boost
  3. aka extra/fmt
  4. extra/gobject-introspection due to g-ir-scanner - at cmake/external/glib/generate_gir.cmake:8

I can confirm that installing these allows the build process to begin. I'm updating from 4.6.2-2. To cut it short, going forward keep a look at extra/telegram-desktop it seems to have the deps up to date.

Finally the build errors with this (if I read it correctly) ...frk-v4.9-full/Telegram/lib_ui/ui/platform/ui_platform_window_title.cpp:325:27: note: candidate expects 1 argument, 2 provided

figue commented on 2023-08-04 23:30 (UTC)

Checking telegram-desktop-dev package, Giovanni resolved the glibmm "issue":

I've just merged its changes to my own forkgram private repo and it works. I've pushed my PKGBUILD here: