| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously it relied on AX_PYTHON_DEVEL, which in turn executes
python-config to get the build flags. However this does not work while
cross compiling because we can't execute the python-config build for the
target platform. To circumvent this problem the python build flags are
now queried via pkgconfig, which has the drawback of not having some
extra build flags, but they do not seem to be needed.
I tested this patch with the termux build system and it build without
their existing hack of injecting python after the configure step. I also
tested non cross compile build on Arch Linux and it also still works.
Fixes #851
|
| |
|
|
|
|
| |
And rename a header.
|
| |
|
|\
| |
| | |
Clean up configure.ac
|
| |
| |
| |
| | |
We don't really need this.
|
| |
| |
| |
| |
| |
| |
| | |
If I understand https://www.gnu.org/software/autoconf/manual/autoconf-2.68/html_node/Canonicalizing.html
correctly then we should use target and not host.
Will only matter in case of crosscompiling.
|
| | |
|
| |
| |
| |
| | |
OSX seems to need CPPFLAGS for readline.
|
| |
| |
| |
| | |
All the distributions I checked have libotr 4.1.1 now.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Remove support for libsignal-protocol-c < 2.3.2.
Debian 10 uses 2.3.2, Debian 11 and 12 use 2.3.3.
openSUSE from 15.2 onward uses 2.3.3.
Fedora since 28 uses 2.3.2.
We should be good.
|
| |
| |
| |
| |
| | |
Since cad934b9a069bb2c3c417d4efc64dc25fb9814b7 we only support
libstrophe. libmesode is deprecated.
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
|\
| |
| | |
Update the contributing guide
|
|/
|
|
|
|
|
| |
We need to define some rules to make sure people know what they need to
take care about.
To allow us to later still understand the changes in an optimal way and
make everyones work easier.
|
| |
|
|\
| |
| | |
fix handling of connection errors
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
When a `see-other-host` stream-error is received we try to re-connect to
the other host. Erroneously this also started the `reconnect_timer`.
This lead to the behavior that in cases where e.g. the login failed
we try to reconnect instead of bailing out with an error.
This commit fixes the wrong behavior by not starting the `reconnect_timer`.
Fix 0e58509c161ae8409c9accabb9606e0c7006b880
Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
|
|\
| |
| | |
Fix typo in comment from "the YES" to "to YES"
|
|/ |
|
|
|
|
|
|
|
| |
If I'm understing everything right the member should be removed here.
muc_members_update() seems to have been writen for the same purpose.
Fix https://github.com/profanity-im/profanity/issues/1594
|
|\
| |
| | |
Fix `_split_url()` once more
|
| |
| |
| |
| | |
Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
|
|\|
| |
| | |
Fix `_split_url()`
|
|/
|
|
| |
Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
|
|\
| |
| | |
Fix #1628
|
| |
| |
| |
| | |
Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
|
| |
| |
| |
| |
| |
| | |
Fixes #1628
Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
|
| |
| |
| |
| | |
Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
|
|/
|
|
|
|
| |
`_session_free_saved_details()` remains as it's still required alone
Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
|
| |
|
|
|
|
| |
As per suggestion of @mdosch.
|
|\ |
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Bugfix in mood_autocomplete (wrong parameter)
* Implemented /mood clean
______________________________________
/ Profanity! THE XMPP client with mood \
\ support! /
--------------------------------------
\
\
.--.
|o_o |
|:_/ |
// \ \
(| | )
/'\_ _/`\
\___)=(___/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It shouldn't happen that we get the presence stanza without a resource.
https://datatracker.ietf.org/doc/html/rfc6120
```
Implementation Note: It is the server's responsibility to deliver
only stanzas that are addressed to the client's full JID or the
user's bare JID; thus, there is no need for the client to check
the 'to' address of incoming stanzas. However, if the client does
check the 'to' address then it is suggested to check at most the
bare JID portion (not the full JID), since the 'to' address might
be the user's bare JID, the client's current full JID, or even a
full JID with a different resourcepart (e.g., in the case of so-
called "offline messages" as described in [XEP-0160]).
```
Let's not segfault though.
Close https://github.com/profanity-im/profanity/issues/1630
|
| |
|
|
|
|
|
| |
It's not run anyways.
See https://github.com/profanity-im/profanity/issues/789
|
|
|
|
|
|
|
|
|
| |
```
Cloning into 'stabber'...
fatal: remote error:
The unauthenticated git protocol on port 9418 is no longer supported.
Please see https://github.blog/2021-09-01-improving-git-protocol-security-github/ for more information.
```
|
|\
| |
| | |
database.c: fix inserting messages to chat logs if archive_id is empty
|
|/
|
|
|
|
|
|
|
|
|
| |
The original intention of the code was that in case archive_id is not set, NULL should be inserted. What is
inserted however is an empty string. This causes the condition to not insert messages with non-unique
archive_id insert only one message in total and ignore all further ones (if NULL was there, the condition
would work properly). And this in turn causes chat history not work properly.
This commit makes the SQL condition work properly and therefore fixes chat history.
Fixes #1589.
|
|\
| |
| | |
Upgrade to OpenBSD 7.0 in CI
|
|/ |
|
|\
| |
| | |
use wildcard for man pages in Makefile.am
|
|/ |
|
|
|
|
| |
Closes https://github.com/profanity-im/profanity/issues/1621
|