Thanks, committed.
On 2021/03/20 19:30, Eivind Eide wrote:
> Bumping this as I would like to see bitlbee-facebook updated to the
> latest release before 6.9.
> Tested much longer now. Works fine.
>
> tor. 18. feb. 2021 kl. 18:26 skrev Eivind Eide :
> >
> > bitlbee-facebook-1.2.2
> >
> > faceb
Bumping this as I would like to see bitlbee-facebook updated to the
latest release before 6.9.
Tested much longer now. Works fine.
tor. 18. feb. 2021 kl. 18:26 skrev Eivind Eide :
>
> bitlbee-facebook-1.2.2
>
> facebook-api: Fix id assertion in fb_api_cb_publish_mst() (#204)
> Increase syn
bitlbee-facebook-1.2.2
facebook-api: Fix id assertion in fb_api_cb_publish_mst() (#204)
Increase sync_interval from 5 to 1440 ("The action attempted has
been deemed abusive or is otherwise disallowed") (#194)
Bump the FB_ORCA_AGENT version once again (#208)
Simple diff attached. Light
Ping?
Tested longer on amd64 now. No problems.
tor. 22. okt. 2020 kl. 03:36 skrev Eivind Eide :
>
> bitlbee-facebook-1.2.1 (2020-10-20):
> - Fix "Parse error: unexpected identifier 'taNewMessage'"
> - Fix "Failed to read thrift: facebook-api.c:1929 fb_api_cb_publish_pt:
> assertion 'fb_thr
bitlbee-facebook-1.2.1 (2020-10-20):
- Fix "Parse error: unexpected identifier 'taNewMessage'"
- Fix "Failed to read thrift: facebook-api.c:1929 fb_api_cb_publish_pt:
assertion 'fb_thrift_read_stop(thft)' failed"
Tested lightly on amd64.
Simple diff. Attaching as textfile, as gmail mangle
Committed, thanks.
There's been an update of net/bitlebee-facebook around for a while
with some fixes:
https://github.com/bitlbee/bitlbee-facebook/releases
I've been running it on OpenBSD/amd64 for some time with no problem.
The diff is quite simple, but as gmail webmail mangles all text I'll
try to attach the diff a
On Fri, Apr 19, 2019 at 06:41:40PM +0200, Solene Rapenne wrote:
> update bitlbee to 3.6 and uses https
Keeps working for me, OK kn.
> HOMEPAGE=http://bitlbee.org/
Has TLS as well.
Tom Doherty writes:
> maintainer ok
>
>> On 19 Apr 2019, at 17:41, Solene Rapenne wrote:
>>
>> update bitlbee to 3.6 and uses https
>>
>> commit list at the bottom of the mail after the diff.
>>
>> I don't use bitlbee, but the service starts and bitlbee-facebook
>> compiles fine too.
>>
>> I p
maintainer ok
> On 19 Apr 2019, at 17:41, Solene Rapenne wrote:
>
> update bitlbee to 3.6 and uses https
>
> commit list at the bottom of the mail after the diff.
>
> I don't use bitlbee, but the service starts and bitlbee-facebook
> compiles fine too.
>
> I plan to look at bitblee-mastodon a
update bitlbee to 3.6 and uses https
commit list at the bottom of the mail after the diff.
I don't use bitlbee, but the service starts and bitlbee-facebook
compiles fine too.
I plan to look at bitblee-mastodon and though it would be nice to update
bitlbee while there.
Index: Makefile
=
On 00:06:01, 11.10.17, Rafael Sadowski wrote:
> You forgot to remove REVISION.
Thanks, fixed.
Index: net/bitlbee-facebook//Makefile
===
RCS file: /cvs/ports/net/bitlbee-facebook/Makefile,v
retrieving revision 1.2
diff -u -p -r1.2 Mak
On Tue Oct 10, 2017 at 10:10:45AM +, Michal Mazurek wrote:
> The previous version stopped working.
>
> OK?
>
> Index: net/bitlbee-facebook/Makefile
> ===
> RCS file: /cvs/ports/net/bitlbee-facebook/Makefile,v
> retrieving revisio
The previous version stopped working.
OK?
Index: net/bitlbee-facebook/Makefile
===
RCS file: /cvs/ports/net/bitlbee-facebook/Makefile,v
retrieving revision 1.2
diff -u -p -r1.2 Makefile
--- net/bitlbee-facebook/Makefile 28 May
Maintainer ok
> On 28 May 2017, at 21:59, Stuart Henderson wrote:
>
> This adds an rc script to bitlbee (using the -F flag, "Run in ForkDaemon
> mode. This is similar to ordinary daemon mode, but every client gets its
> own process" which seemed the sanest option). Then there doesn't seem
> much
This adds an rc script to bitlbee (using the -F flag, "Run in ForkDaemon
mode. This is similar to ordinary daemon mode, but every client gets its
own process" which seemed the sanest option). Then there doesn't seem
much need to document inetd setup, so remove it from README. Tweak the
other bit of
As Stuart pointed out, add the MODPY_RUNDEP = No setting.
Index: Makefile
===
RCS file: /cvs/ports/net/bitlbee/Makefile,v
retrieving revision 1.58
diff -u -p -r1.58 Makefile
--- Makefile19 Jul 2015 08:22:14 - 1.58
+++ Mak
On Fri, May 26, 2017 at 05:32:08PM +0200, Michal Mazurek wrote:
For what it's worth, my patch[0] in early april has some additional
changes that could be merged.
0: http://marc.info/?l=openbsd-ports&m=149174357820533&w=2
Thanks, fixed version:
Index: Makefile
=
Thanks, fixed version:
Index: Makefile
===
RCS file: /cvs/ports/net/bitlbee/Makefile,v
retrieving revision 1.58
diff -u -p -r1.58 Makefile
--- Makefile19 Jul 2015 08:22:14 - 1.58
+++ Makefile26 May 2017 15:30:26 -
On 2017/05/26 15:27, Michal Mazurek wrote:
> Update to 3.5.1. Changelog for 3.4.1 states:
> Building documentation is now done with a python script (both 2.x/3.x
> work) Asciidoc/xsltproc/xmlto are no longer build dependencies (dx)
>
> Many thanks to fcambus@ for helping me to get this complet
Update to 3.5.1. Changelog for 3.4.1 states:
Building documentation is now done with a python script (both 2.x/3.x
work) Asciidoc/xsltproc/xmlto are no longer build dependencies (dx)
Many thanks to fcambus@ for helping me to get this complete.
Index: net/bitlbee/Makefile
=
See the official changelog[0] for more information. Especially TLS>1.0
support[1] should make it into 6.1 imho.
Documentation does not depend on textproc/xmlto anymore, a single
help.txt is now produced through a python script in BitlBee's build
process.
Even though I'm running the latest snapsh
Committed.
Thanks,
--
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
Hi
I tested with my usual bitlbee-libpurple/pidgin-sipe
Cheers
Tom
Sent from my iPhone
> On 13 May 2015, at 18:43, Henrik Friedrichsen wrote:
>
> Hey!
>
> Oh, I'm afraid I missed the previous submission.
>
>> On Wed, May 13, 2015 at 07:23:22PM +0200, Jérémie Courrèges-Anglas wrote:
>> I can c
Hey!
Oh, I'm afraid I missed the previous submission.
On Wed, May 13, 2015 at 07:23:22PM +0200, Jérémie Courrèges-Anglas wrote:
> I can commit this if I get explicit test reports. Can I have a rough
> idea of which protocols were tested?
I have been using this since I sent it in with the XMPP a
Hi,
Henrik Friedrichsen writes:
> Oops. Looks like the first message did not get to the list.
> Here is the patch one more time..
I see that Tom Doherty (cc'ed) had already sent an update to 3.4,
including a tweak to remove MSN from COMMENT[1].
I can commit this if I get explicit test reports
Oops. Looks like the first message did not get to the list.
Here is the patch one more time..
On Sun, May 10, 2015 at 01:03:52PM +0200, Henrik Friedrichsen wrote:
> ping?
Index: Makefile
===
RCS file: /cvs/ports/net/bitlbee/Makefile,v
ping?
Attached is a patch bumping bitlbee version to 3.4.
Running this on my server with OTR. Seems to work fine.
OK?
Index: Makefile
===
RCS file: /cvs/ports/net/bitlbee/Makefile,v
retrieving revision 1.55
diff -u -p -r1.55 Makefile
--- M
Hi
Here's an update to bitlbee 3.4
Version 3.4:
Main repository migrated from bzr to git
Some API/ABI changes. Recompiling third party plugins is required!
Important bugfixes:
Fix memory leak when calling word_wrap() on groupchat messages (dx)
Fix segfault after a file transfer is complete (dx)
F
Hi
Probably too late to go in now but will bump after unlock
Version 3.2.2 (released 2014-07-05) hilights:
libotr 4.0 compatibility fixes.
Twitter Unicode fixes.
Small other bugfixes.
Cheers
Tom
Index: Makefile
===
RC
Hi
Please find attached an update to bitlbee 3.2.1. OTR patch has been merged
upstream and I have regenerated the others.
Changelog:
Version 3.2.1 (released 2013-11-27) hilights:
- http_client now uses HTTP/1.1, which is required by Twitter since last
week.
- A bunch of o
On v, jan 27, 2013 at 16:13:24 -0500, Okan Demirmen wrote:
> Here's one that makes sure the otr FLAVOR continues to work:
[...]
This also works for me.
Daniel
--
LÉVAI Dániel
PGP key ID = 0x83B63A8F
Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F
Here's one that makes sure the otr FLAVOR continues to work:
Cheers,
Okan
Index: Makefile
===
RCS file: /home/open/anoncvs/cvs/ports/net/bitlbee/Makefile,v
retrieving revision 1.46
diff -u -p -r1.46 Makefile
--- Makefile27 Nov 20
On Sat, Jan 19, 2013 at 02:48:13PM -0500, Okan Demirmen wrote:
> Hi - Missed this thread; however, I see 1 or 2 diff's - is there one
> complete diff? And on what networks/servers has the openssl switch
> been tested? (I don't have have accounts on all networks to test
> myself :))
Re ssl, i've o
Hi - Missed this thread; however, I see 1 or 2 diff's - is there one
complete diff? And on what networks/servers has the openssl switch
been tested? (I don't have have accounts on all networks to test
myself :))
Cheers,
Okan
On Thu, Jan 17, 2013 at 2:26 PM, Tom Doherty wrote:
> I like it a lot.
I like it a lot. Okan? :-)
On Thu, Jan 10, 2013 at 10:02 AM, LEVAI Daniel wrote:
> On sze, jan 09, 2013 at 19:30:17 +0100, Landry Breuil wrote:
> > On Wed, Jan 09, 2013 at 02:34:10PM +0100, LEVAI Daniel wrote:
> > > On sze, jan 09, 2013 at 10:35:00 +, Stuart Henderson wrote:
> > > > On 201
On sze, jan 09, 2013 at 19:30:17 +0100, Landry Breuil wrote:
> On Wed, Jan 09, 2013 at 02:34:10PM +0100, LEVAI Daniel wrote:
> > On sze, jan 09, 2013 at 10:35:00 +, Stuart Henderson wrote:
> > > On 2013/01/09 10:11, LEVAI Daniel wrote:
> > [...]
> > > > I've been meaning to ask if it would be o
On Wed, Jan 09, 2013 at 02:34:10PM +0100, LEVAI Daniel wrote:
> On sze, jan 09, 2013 at 10:35:00 +, Stuart Henderson wrote:
> > On 2013/01/09 10:11, LEVAI Daniel wrote:
> [...]
> > > I've been meaning to ask if it would be okay to drop the gnutls dep.,
> > > and switch bitlbee to OpenSSL. I've
On sze, jan 09, 2013 at 10:35:00 +, Stuart Henderson wrote:
> On 2013/01/09 10:11, LEVAI Daniel wrote:
[...]
> > I've been meaning to ask if it would be okay to drop the gnutls dep.,
> > and switch bitlbee to OpenSSL. I've been using it with it since 3.0 beta
> > times and never had a problem,
On 2013/01/09 10:11, LEVAI Daniel wrote:
> On k, jan 08, 2013 at 21:36:53 +, Tom Doherty wrote:
> > Hi
> > Update net/bitlbee to 3.2:
> [...]
> > Works for me with msn/jabber/oscar/sipe
> [...]
>
> Hi!
>
> It seems that this works here also; only tested
On k, jan 08, 2013 at 21:36:53 +, Tom Doherty wrote:
> Hi
> Update net/bitlbee to 3.2:
[...]
> Works for me with msn/jabber/oscar/sipe
[...]
Hi!
It seems that this works here also; only tested msn, jabber and oscar
protocols with the otr flavor.
I've been meaning to ask if it
Hi
Update net/bitlbee to 3.2:
Version 3.2 (released 2013-01-06) hilights:
Updated Twitter module. Support for Twitter API 1.1, streaming API, direct
messages and some other improvements.
Fixed potential connection issue to Google Talk, OpenFire, possibly other
Jabber services.
A bunch of other
On cs, dec 15, 2011 at 16:54:42 -0500, Okan Demirmen wrote:
> update to 3.0.4.
>
> testing, comments and oks.
>
Working great on i386. I've been using it for a solid week now, with the
otr flavor. Tested with Jabber, MSN, iCQ, and no problem so far.
Daniel
--
LÉVAI Dániel
PGP key ID = 0x83B6
update to 3.0.4.
testing, comments and oks.
cheers,
okan
Index: Makefile
===
RCS file: /home/okan/openbsd/cvs/ports/net/bitlbee/Makefile,v
retrieving revision 1.41
diff -u -p -r1.41 Makefile
--- Makefile3 Oct 2011 14:41:45 -
Andrew Dalgleish [Tue, Apr 11, 2006 at 08:05:04AM +1000] wrote:
>On Mon, Apr 10, 2006 at 07:08:27PM +, Christian Weisgerber wrote:
>> Is there any reason to keep the no_ssl flavor now?
>
>Hmm. I don't think so. That was added because gnutls didn't work on sparc64.
>I've removed that, and added
Andrew Dalgleish <[EMAIL PROTECTED]> wrote:
> PORT: net/bitlbee
>
> COMMENT:
> bitlbee 1.0.2
>
> Tested on
> i386 -current
Actually, this doesn't build for me. The prototypes for
http_{de,en}code() in util.h specify only a single argument.
--
Christian "naddy" Weisgerber
Andrew Dalgleish <[EMAIL PROTECTED]> wrote:
> PORT: net/bitlbee
>
> COMMENT:
> bitlbee 1.0.2
> -LIB_DEPENDS+=gnutls.8::security/gnutls
> -WANTLIB+=gcrypt gpg-error
> +CONFIGURE_ARGS+= --ssl=openssl
> +WANTLIB+=crypto ssl
Is there any reason to keep th
On Monday 06 March 2006 22:19, Andrew Dalgleish wrote:
> As Will Maier pointed out, it doesn't work.
>
> I used 'cvs diff -uwN' instead of 'cvs diff -uN'.
> Faulty finger macros.
>
>
> Regards,
> Andrew Dalgleish
Any particular reason why nothing is happening with this update?
(speaking of, just
i386 current from Feb 19, compiled and upgraded fine, added account for jabber
via ssl, that and MSN connection seem to work.
--
viq
-
Toshiba i FIFA World Cup
Wygraj bilety i notebooki z Intel Centrino Duo Mobile Technology
ht
Seems to be working fine for me, i386-current as of Feb 26th.
Thanks!
Josh
On Tue, Mar 07, 2006 at 08:19:59AM +1100, Andrew Dalgleish wrote:
> I used 'cvs diff -uwN' instead of 'cvs diff -uN'.
> Faulty finger macros.
Patched port upgrades just fine. Jabber, AIM and Yahoo transports
all appear to be working (as is Google Chat); SSL is enabled.
Thanks, Andrew!
# unam
52 matches
Mail list logo
