Package Details: python-yowsup 3.3.0-4

Git Clone URL: https://aur.archlinux.org/python-yowsup.git (read-only, click to copy)
Package Base: python-yowsup
Description: The open source cross platform Whatsapp library powering Wazapp
Upstream URL: https://github.com/tgalal/yowsup
Licenses: GPL
Conflicts: python-yowsup-git, yowsup-client-git
Submitter: fanningert
Maintainer: None
Last Packager: micwoj92
Votes: 2
Popularity: 0.000000
First Submitted: 2016-07-21 19:31 (UTC)
Last Updated: 2024-06-27 18:08 (UTC)

Latest Comments

« First ‹ Previous 1 2

fordprefect commented on 2017-10-23 11:10 (UTC)

@servimo: Thanks for reporting. To mitigate the conflict error I moved the binary for the python2 version to yowsup-cli2. Bear in mind that you usually dont need both packages though. However, I could not reproduce your version error. Could you describe how you come to that conclusion?

servimo commented on 2017-10-22 15:20 (UTC)

error: failed to commit transaction (conflicting files) / usr / bin / yowsup-cli exists in both "python2-yowsup" and "python-yowsup" /usr/share/yowsup/common/mime.types exists in both "python2-yowsup" and "python-yowsup" Errors occurred, so no packages were updated.

servimo commented on 2017-10-22 14:20 (UTC) (edited on 2017-10-22 14:20 (UTC) by servimo)

compiling only works if I edit deleting in pkgbuild python-yowsup, but keeps version as 2.5.0

je-vv commented on 2016-08-13 04:57 (UTC)

No problem, I didn't know it gets installed if installing python2-yowsup... So it's fine... Perhaps you should have a note NOT to install it directly, :-) I'm glad I can get it...

fanningert commented on 2016-08-11 18:44 (UTC)

@jevv Please look at the PKGBUILD, it has a python2 package build an a python3 package build. But after some tests, it was not possible to create a working python3 package for this package. The python2 build depends is for the package base. But it is correct, I can delete the python-yowsup package. An only the python2-yowsup package would exist.

je-vv commented on 2016-08-11 16:52 (UTC)

Why does a python (not python2) have python2 makedeps, and also python2 deps? What's worse, is that even the non python2 [make]deps still have python2 [make]deps...