@adisbladis ?

Hello, I'm a bot and I thank you in the name of the community for your contributions.

Nixpkgs is a busy repository, and unfortunately sometimes PRs get left behind for too long. Nevertheless, we'd like to help committers reach the PRs that are still important. This PR has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human.

If this is still important to you and you'd like to remove the stale label, we ask that you leave a comment. Your comment can be as simple as "still important to me". But there's a bit more you can do:

If you received an approval by an unpriviledged maintainer and you are just waiting for a merge, you can @ mention someone with merge permissions and ask them to help. You might be able to find someone relevant by using Git blame on the relevant files, or via GitHub's web interface. You can see if someone's a member of the nixpkgs-committers team, by hovering with the mouse over their username on the web interface, or by searching them directly on the list.

If your PR wasn't reviewed at all, it might help to find someone who's perhaps a user of the package or module you are changing, or alternatively, ask once more for a review by the maintainer of the package/module this is about. If you don't know any, you can use Git blame on the relevant files, or GitHub's web interface to find someone who touched the relevant files in the past.

If your PR has had reviews and nevertheless got stale, make sure you've responded to all of the reviewer's requests / questions. Usually when PR authors show responsibility and dedication, reviewers (privileged or not) show dedication as well. If you've pushed a change, it's possible the reviewer wasn't notified about your push via email, so you can always officially request them for a review, or just @ mention them and say you've addressed their comments.

Lastly, you can always ask for help at our Discourse Forum, or more specifically, at this thread or at #nixos' IRC channel.

@cab404 I've essentially rewritten most of your original expression:

• Changed the upstream. Guix had also changed it so I went with what they did.
• I try to be compatible with MacOS, but I don't have a MacOS machine so I can't test this.
• I made it multi-output
• Fixed a couple of things it tries to dlopen by adding relevant paths to the rpath
• Added meta
• Added version
• No longer using clangStdev

I still can't get it to work mind you, but I feel that this is in a better shape than before.

@cab404 Could you take a look?

I still can't get it to work mind you, but I feel that this is in a better shape than before.

@cab404 Could you take a look?

I've tried doing a test call and telega-server crashed.

#0  0x00007f551fa0633a in raise () from /nix/store/3wa1xwnfv8ada1za1r8m4vmsiz1jifqq-glibc-2.32-35/lib/libc.so.6
#1  0x00007f551f9f0523 in abort () from /nix/store/3wa1xwnfv8ada1za1r8m4vmsiz1jifqq-glibc-2.32-35/lib/libc.so.6
#2  0x00007f551f9f041f in __assert_fail_base.cold.0 () from /nix/store/3wa1xwnfv8ada1za1r8m4vmsiz1jifqq-glibc-2.32-35/lib/libc.so.6
#3  0x00007f551f9fed92 in __assert_fail () from /nix/store/3wa1xwnfv8ada1za1r8m4vmsiz1jifqq-glibc-2.32-35/lib/libc.so.6
#4  0x0000000000408251 in telega_voip_cmd(char const*) ()
#5  0x00000000004041e3 in stdin_loop(void*) ()
#6  0x0000000000403a55 in main ()

environment:

NIX_PATH=nixpkgs=. nix-shell -p 'emacsWithPackages(s: [s.telega])' --run "emacs -q --execute '((lambda() (load-library \"telega\") (telega)))'"

is this what you meant by 'can't get it to work'?

It builds with libtgvoip already present in nixpkgs, but yields same results in the call test. Either both libraries are broken, or telega can't use them properly.

Next stop would be trying to build libtgvoip from tdesktop/Telegram/ThirdParty/libtgvoip, but it is built with automake now, and I have any more time today to spend.

@adisbladis can you please try to build tdesktop's libtgvoip?

I marked this as stale due to inactivity. → More info