| Commit message (Collapse) | Author | Age | Lines |
... | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
So cygwin requires -no-undefined and it was supposed to be harmless on
platforms other than windows, but mac OS doesn't like it.
Instead of adding platform checks to every plugin, i'm going to revert
the changes that added -no-undefined to them, and just do what I should
have done since the beginning: use the cygwin-specific parts of the
pkg-config file to add -no-undefined right next to -lbitlbee
|
| | |
|
|\| |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In other words, "account jabber set away Message" resulted in away
status being set, but not "Message".
Fixes trac ticket 1291
This was broken by ac68733ad7a5127395d6367b655a2d9de5d911b5 (3.4.2)
That commit added another call of imc_away_state_find() with the fixed
string "away", so purple protocols can become away by setting away to
any string. But by doing so, it wiped the status message because it's
the same as the name of the away state.
|
| |
| |
| |
| | |
`utf8_nicks` should be enabled before handling `nick` fields in <setting> because `nick_strip` uses `IRC_UTF8_NICKS` which is only available after calling `handle_settings`.
|
|\| |
|
| |
| |
| |
| | |
The default was to enable both, which was confusing.
|
| | |
|
| | |
|
|\| |
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
I couldn't find anyplace that actually enables the IPC, but I hand
edited the config.h to enable it, and did see the protocol not supported
failure, so modified this file and it went away.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
For some reason the protocol was being set to PF_UNIX which is
incorrect. According to the man pages and other sources (like Stevens
Unix Network Programming), the protocol should be '0' which will
use the default for the given domain. This appears to actually
work under Linux (which appears to allow 0 or 1 as the protocol without
error), but fails under Mac OSX (which only allows 0).
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
In other words, running $(make V=1) will force a verbose build while
$(make V=0) will force a silent build regardless of the verbose option
set by the configure script.
|
| | |
| | |
| | |
| | | |
Defaults to disabled to maintain the status quo.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
trick supported by stunnel to indicate where the connection originally
came from. Looks a little better on public servers.
|
| |/
| |
| |
| |
| | |
reverse lookup. (Code copied from OpenSSH instead of redoing it
poorly.)
|
| | |
|
|\| |
|
| | |
|
| |
| |
| |
| |
| | |
Followup to 701ab81 (included in 3.5) which was a partial fix which only
improved things for non-libpurple file transfers (that is, just jabber)
|
| |
| |
| |
| |
| | |
actually NMU'd. :-( Now this fix really should work. Third time's the
charm after all, innit.
|
| |
| |
| |
| | |
properly.
|
| |
| |
| |
| |
| | |
Because apparently not having build-arch is now a build failure, even
though lintian only considered it a warning and a "recommended" target
|
| | |
|
| | |
|
| | |
|
|\| |
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
I thought I got the capitalization wrong but the manpage of
dh_installchangelogs says it grabs debian/NEWS and calls it NEWS.Debian.
No one told me this.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Turns out the stuff added by debhelper below enables debconf, which
somehow reads the stuff written to stdout before, and chokes on it.
The error output that is being ignored is something along the lines of
"the user doesn't exist".
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This fixes an issue when upgrading from an initscripts based release
like 3.4.2 to the current version, in which the old daemon is still
running when systemd tries to start it, so it fails to start due to bind
and fails to stop because it doesn't use pidfiles.
To get around this, the preinst script kills the initscripts-started
daemon the first time when upgrading from something old enough, using
the pidfile.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It was broken with the transition to systemd and doesn't seem worth
fixing - it's redundant with bitlbee.conf and not much more than a
source of confusion for users.
This also removes all the debconf stuff and all the translations which
are not used anymore (that looked a bit excessive for something that
just asks for a port number)
|
| | |
| | |
| | |
| | | |
As suggested by lintian's systemd-service-file-refers-to-obsolete-target
|
| | | |
|
| | |
| | |
| | |
| | | |
It was 16 before.
|
|\| | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
That is, flagged with PURPLE_MESSAGE_DELAYED. Those are safe to display.
This is similar to what adium does. Thanks EionRobb for the idea.
|
| |/
| |
| |
| | |
Accidentally broke it in d57484d (from last week)
|
|\| |
|
| |
| |
| |
| |
| |
| |
| | |
This constant is always available and meant to be used with
getnameinfo().
This fixes the build on Debian GNU/kFreeBSD.
|
| |
| |
| |
| | |
Credit for the idea goes to russian XMPP spammers. Thanks!
|