How to find latest MD5, KEY and VERSION when using Yowsup - yowsup

I have seen issues where registering with whatsapp server sometimes fails when using yowsup with old_version error (Yowsup - old_version error). I understand this is due to whatsapp upgrading itself, what is a good way to find latest MD5, KEY and VERSION that whatsapp uses so that yowsup can register without an issue.

You can use this site:
https://coderus.openrepos.net/whitesoft/whatsapp_scratch
This site provides the MD5, key and the version.

follow these 3 simple steps:
git remote add jlguardi https://github.com/jlguardi/yowsup.git
git pull jlguardi Android_2.12.440
git merge jlguardi/Android_2.12.440
sudo python setup.py install
This should solve the issue

Related

how to update etherpad-lite properly?

I keep totally failing to update an etherpad-lite server. The problem: Even a Google search for the update procedure brings up hardly any information, only that one should run "git pull origin".
I have now tried this in many different ways. The update usually works, but afterwards one of these errors occurs:
Plugins can no longer be installed
The service can no longer be started (TypeError: log4js.replaceConsole is not a function)
The entire admin panel no longer works.
I tried uninstalling or updating all plug-ins before, but both hardly brought any improvements, only other errors. The update of the plugins in the admin console fails, I tried it via the updatePlugins.sh script. Here a message appears that at least etherpad-lite 1.8,6 must be installed. I am currently at version 1.8.4 and would like to update to the latest version 1.8.12. However, some of the plug-ins are still updated. A very strange behaviour.
I would be happy if someone could tell me how to properly update the etherpad-lite instance step by step. (ubuntu 20)
Thank you!
I have recently updated Etherpad-lite from version 1.8.6 to 1.8.13.
For me, executing git pull origin and then checking out the 1.8.13 release tag, with git checkout 1.8.13, made the work.
It is important, despite having Etherpad configured as a service, to run it for the first time using:
src/bin/run.sh.
Node v12.22.1
npm 6.14.12
Ubuntu 20.04.2
I hope it has been useful to you.

Install Git on CentOS 7 LEMP stack

After about 6+ days and numerous rounds of spin-up/destroy I have FINALLY gotten my Digital Ocean droplet server up and running (ie I can view a live page of content at my ip).
At this point I am trying to install Git, and have installed/removed it 3 times so far as I keep getting 'close' to completion but then run into some error I can't find an answer for. I'm hoping someone can help me figure out what my latest problem is so I can move forward with the actual development of my site rathe than spending over a week on the server build.
I have attempted to install version 2.6.2 of git on my server and have had to compile from source (something I am no where near familiar with). I 'thought' I had it correct this time, but received the following error when I attempted to set my git user name:
gitconfig --global user.name "MyUserName" (<--- last command I made)
bash: gitconfig: command not found (<-- error i received)
I thought it was an issue with being in the wrong directory to run the command, so i ran which git and received the following output:
/usr/local/git/bin/git
This seems to be a binary (?) file and none of the directories listed in that path allow me to use gitconfig command either.
Any ideas what I have done wrong? Do I need to remove (again!) and re-compile. I don't desire to be a server admin, but really had thought (hoped?) spinning my own LEMP server on CentOS 7 would be simple - doing so on CentOS 6.* was.
Thanks for your help/advice.
gitconfig isn't a command.
You'd do:
git config --global user.name "MyUserName"
Also you're really better off installing git via yum, rather than compiling from source unless there's a good reason to compile it yourself.
(Edit - updated answer with tested solution on Centos 7).

centos mongodb package not signed

ok this might be a stupid question and this is because centos is not part of my "strong points list" but i am trying to install mongodb and mongodb-server
i followed the steps found here
a link!
they missed a step ... what happens if after centos downloads the packages ... it tells me that they are not signed
i also tried importing this gpg key (as a last desperate attempt before coming here)
a link!
so how do i get pass this? :(
thanks,
Rares
This is what worked for me to ignore "package not signed" message:
yum install --nogpgcheck <your-package-name>
Changing gpgcheck to 0 in /etc/yum.conf didn't help. Security warning: you should use this option ONLY if you trust the installation sources.
You are correct, the package is not signed. It is planned to be done in the future, and the relevant tracking ticket for the implementation of signing is SERVER-8770 (for watching and voting purposes) but there is no definite timeframe for implementation as of writing this response.
Hence, you must install with gpgcheck=0 for the time being as noted on the page you linked to: Install MongoDB on Redhat/CentOS/Fedora

CouchDB install multiple versions side-by-side

I attempt to install multiple versions of CouchDB databases, say 1.1.0 along side with 0.10.0.
By using build-couchdb I was able to get the latest version up and running with no problems, now I am trying with installing a second version (0.10.0) but with no success so far. Following with the instructions, I've tried:
rake git="git://git.apache.org/couchdb.git tags/0.10.0" install=/full/path/to/couchdb/dir
It does a bunch of installs but fails at the end with "rake aborted!".
Have anyone successfully done this ?
Build CouchDB can be slightly brittle. In production, what I've seen is a lot of complete wipes and complete rebuilds. Since people tend to build only once, the build time is not a huge pain-point.
Next, try to use the Erlang shortcut for installing side-by-side CouchDB builds. (Search for couchdb_build in the README).
rake git="git://git.apache.org/couchdb.git tags/0.10.0" \
install=/full/path/to/couch/dependencies \
couchdb_build=/full/path/to/couch/0.10.0
rake git="git://git.apache.org/couchdb.git tags/1.1.0" \
install=/full/path/to/couch/dependencies \
couchdb_build=/full/path/to/couch/1.1.0
With the install locations identical, Build CouchDB should skip the entire process to build and install dependencies when it builds 1.1.0. This includes:
Erlang
OTP
Javascript
I believe this technique is used more often than the simpler one for side-by-side builds. Therefore it is possible this workaround will fix your error.
If you still have issues, it is probably a bug. Would you please submit a Build CouchDB issue indicating your operating system version and also attach your rake.log file?

Upgrade Mercurial installation to use a different version of Python

I have been banging on this for hours now.
I am trying to push my repo changes to kiln but I get this error:
certificate checking requires Python 2.6
I have already installed a parallel install of Python 2.6 by following the instructions from this link, but the error still persists. The system is ClearOS 5.2 by the way.
My first question is, will installing/upgrading mercurial break my existing install?
I tried to re-install following these intstructions link1 and [i lost the other link], but encountered another error.
Then I found this command debuginstall and here's the result:
[root#system mercurial-1.7.5]# hg debuginstall
Checking encoding (UTF-8)...
Checking installed modules (/usr/lib/python2.4/site-packages/mercurial)...
Checking templates...
Checking patch...
Checking commit editor...
Checking username...
no username supplied (see "hg help config")
(specify a username in your configuration file)
1 problems detected, please check your install!
My another question is, can I just change the existing hg's settings to just use the python26 which is already installed?
Thanks in advance!
Install your own python (of whatever version you need) to a separate directory (e.g.: /usr/local/python-2.7.2/) and then change the invocation of hg from #!/usr/bin/python to #!/usr/local/python-2.7.2/bin/python This way you don't disturb the existing/system installation, but you can use the version you want only where you need it. The only annoying part about this is dealing with two sets of libraries, since this is really maintaining two parallel installations. So if the 'extra' python needs libraries, you must install them manually using the invocation and paths of the extra installation. Sounds complicated, but if you only need it for one program, then you set it up once and it's good to go.

Resources