Arch Linux

riveravaldez

Member

Registered: 2016-11-18

Posts: 29

How to keep using qTox (for a while)?

Hi everybody, sorry to bother, as mentioned here: Why qtox removed from extra repo?, qTox seems to have been removed from repose because right now it's unmaintained.
I still have it installed in my system, and while looking for a suitable replacement I would like to keep using it.
This is what I got when trying to run it:

$ qtox 
qtox: error while loading shared libraries: libavcodec.so.60: cannot open shared object file: No such file or directory

Could anybody give me some idea about what can I do to make it work?
I've looked around but couldn't find nothing clear until now...
Thanks a lot in advance for any help you can give me.
Kind regards!

d_fajardo

Member

Registered: 2017-07-28

Posts: 1,656

Re: How to keep using qTox (for a while)?

Have you tried rebuilding the package?

riveravaldez

Member

Registered: 2016-11-18

Posts: 29

Re: How to keep using qTox (for a while)?

Have you tried rebuilding the package?

Hi, d_fajardo, thanks for answering.

Not really, I'm not experienced with that, at least not with packages this complex (I'm guessing you mean rebuild qtox).

My first idea was looking for some way to put libavcodec.so.60 back in the place qtox is looking for...

I'm pretty open to suggestions, of course.

Kind regards.

Last edited by riveravaldez (2024-09-24 08:24:49)

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 30,330

Website

Re: How to keep using qTox (for a while)?

Apparently the last working PKGBUILD was not dropped to the AUR.  There is an old PKGBUILD there from nearly 10 years ago which has a lot of issues and it'd probably be better to start from scratch.

Retrieving the PKGBUILD last used for the official package would be best, though I don't know how to retrieve that after it's been removed from the repos and not dropped to the AUR.  Presumably it is in the gitlab history.

EDIT: here it is.  Though it does need patching: upstream has abandoned it due to API breaking changes in dependencies that they don't know how to fix - so it may take some work.

I suspect finding the old .so file would be a losing battle as you'd get one lib file and you'd find another was then needed, then another, etc.  Downgrading your whole system could work for the moment - but then you'd be running an outdated system.

Last edited by Trilby (2024-09-24 17:48:08)

---

"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman