dequis / bitlbee-old Goto Github PK
View Code? Open in Web Editor NEWOld personal fork, use https://github.com/bitlbee/bitlbee instead
Old personal fork, use https://github.com/bitlbee/bitlbee instead
seirl is doing this
adding tickets to track stuff i want to get done before the next release
this would be loosely based on the changes the carbons patch does.
It crashes the damn thing. Their bug but also our bug.
Trac: http://bugs.bitlbee.org/bitlbee/ticket/917#comment:6
This Robert had a backtrace but it got lost in an expired pastebin. It was something along the lines of account_on adding contacts right away and dereferencing some null pointer in the whatever structs of whatever whatsapp-purple things. That.
References #19
Fuck yeah coverity
from @jgeboski's suggestions - split to individual tickets as needed.
General:
Specific:
g_strcmp0()
(glib 2.16)GHashTableIter
(glib 2.16)GResolver
(glib 2.22)g_unix_signal_add()
(glib 2.30)g_slist_free_full()
(glib 2.28)Rejected:
adding tickets to track stuff i want to get done before the next release
i mean why the hell not
Importing bugs I care about from trac.
incorrect-fsf-address /usr/include/bitlbee/events.h
incorrect-fsf-address /usr/include/bitlbee/proxy.h
incorrect-fsf-address /usr/share/doc/bitlbee-3.2.2/COPYING
incorrect-fsf-address /usr/src/debug/bitlbee-eeb82256c627b807d2a2cf657158d32b52bf17bd/lib/proxy.c
incorrect-fsf-address /usr/src/debug/bitlbee-eeb82256c627b807d2a2cf657158d32b52bf17bd/protocols/oscar/oscar.c
incorrect-fsf-address /usr/src/debug/bitlbee-eeb82256c627b807d2a2cf657158d32b52bf17bd/protocols/yahoo/yahoo2_callbacks.h
incorrect-fsf-address /usr/src/debug/bitlbee-eeb82256c627b807d2a2cf657158d32b52bf17bd/protocols/yahoo/yahoo2.h
incorrect-fsf-address /usr/src/debug/bitlbee-eeb82256c627b807d2a2cf657158d32b52bf17bd/protocols/yahoo/yahoo2_types.h
incorrect-fsf-address /usr/src/debug/bitlbee-eeb82256c627b807d2a2cf657158d32b52bf17bd/protocols/yahoo/yahoo.c
incorrect-fsf-address /usr/src/debug/bitlbee-eeb82256c627b807d2a2cf657158d32b52bf17bd/protocols/yahoo/yahoo_debug.h
incorrect-fsf-address /usr/src/debug/bitlbee-eeb82256c627b807d2a2cf657158d32b52bf17bd/protocols/yahoo/yahoo_httplib.c
incorrect-fsf-address /usr/src/debug/bitlbee-eeb82256c627b807d2a2cf657158d32b52bf17bd/protocols/yahoo/yahoo_httplib.h
incorrect-fsf-address /usr/src/debug/bitlbee-eeb82256c627b807d2a2cf657158d32b52bf17bd/protocols/yahoo/yahoo_list.h
incorrect-fsf-address /usr/src/debug/bitlbee-eeb82256c627b807d2a2cf657158d32b52bf17bd/protocols/yahoo/yahoo_util.c
incorrect-fsf-address /usr/src/debug/bitlbee-eeb82256c627b807d2a2cf657158d32b52bf17bd/protocols/yahoo/yahoo_util.h
76c85b4#diff-b6da343f1913e438b4650d5b04bfcfcaR388
new = new->next
, new becomes new->next, old becomes forgotten, new is returned
Channels that show debug.
for-wilmer-19-jan
wip/md5
feat/hip-cat
(welp)patch/twitter-filter
(jgeboski)patch/mode-special
(jgeboski)wip/jabber-subprotocols
patch/headers
patch/use-dev-urandom-properly
flexo/python
WPettersson:twitter_format_strings
WPettersson:rawreply
WPettersson:threads
(he will take care)patch/carbons
Importing bugs I care about from trac.
Importing bugs I care about from trac.
This one is for @jcopenha, who cares about the portability of his resolv patch much more than i do.
So we have this:
if detect_resolv_dynamic || detect_resolv_static; then
echo '#define HAVE_RESOLV_A' >> config.h
if detect_resolv_ns_dynamic || detect_resolv_ns_static; then
echo '#define HAVE_RESOLV_A_WITH_NS' >> config.h
fi
else
And this debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=291609
Which causes the detect_resolv_ns_dynamic check to fail with:
/tmp/ccyZuKqf.o: In function `main':
:(.text+0x18): undefined reference to `__ns_initparse'
:(.text+0x31): undefined reference to `__ns_parserr'
collect2: ld returned 1 exit status
And pretty much the same thing at the end of the build:
lib/lib.o: In function `srv_lookup':
ns_parse.c:(.text+0x4e44): undefined reference to `__ns_initparse'
ns_parse.c:(.text+0x4f60): undefined reference to `__ns_parserr'
In this particular failing case (with emoji because why not)
detect_resolv_dynamic
succeedsdetect_resolv_static
isn't checkeddetect_resolv_ns_dynamic
fails (debian bug)detect_resolv_ns_static
succeedsSince detect_resolv_dynamic
/ detect_resolv_static
are in charge of adding themselves to EFLAGS, this ends up trying to link against the libresolv.so
, while needing libresolv.a
for resolv_ns.
Soooo, wtf do we do?
Our test suite is not great but the github integration is so sweet~
this is going to hurt
http://bugs.bitlbee.org/bitlbee/ticket/1114
srsly dude
the plan is to send IDs coded with a timestamp in them, and if the error has a valid timestamp, show formatted time in the ui error message.
Trac: http://bugs.bitlbee.org/bitlbee/ticket/1044
Half a patch written for this one. Should spend more than 5 minutes on it.
DO SOMETHING
Old "patch": http://bugs.bitlbee.org/bitlbee/ticket/971
Arch's version of tmpfiles: https://projects.archlinux.org/svntogit/packages.git/tree/trunk/bitlbee.tmpfiles?h=packages/bitlbee
Don't think we can predict the location that needs to be cleared:
pidfile='/var/run/bitlbee.pid'
ipcsocket=''
Also the ipc socket gets disabled with this, can't be re-enabled in runtime
Trac:
Patch ticket: http://bugs.bitlbee.org/bitlbee/ticket/1098
OpenBSD ticket: http://bugs.bitlbee.org/bitlbee/ticket/1003
Trac: http://bugs.bitlbee.org/bitlbee/ticket/1085
Don't remember what was missing to apply this one...
BASH PROGRAMMING TOO COMPLEX
GET HYPE
< jgeboski> dx: another thing that should be done if the API is going to break... fix the damn pkgconfig include dir
< jgeboski> to be bitlbe/*.h
< jgeboski> for instance, global includes for url.h, it's just #include <url.h>
< jgeboski> not bitlbee-url.h
< jgeboski> or bitlbee/url.h
< jgeboski> it's very uncleanly
< jgeboski> and could very likely lead to header conflicts< jgeboski> you can see a ton of things that are ambiguously named
< jgeboski> and having them in a global include path could be severely problematic
< jgeboski> the only reason this has not been an issue as of yet is because there are not many plugins, and most other libraries do things correctly in this department< dx> so this is just removing -I/usr/include/bitlbee from bitlbee.pc and changing includes to #include <bitlbee/url.h>?
< jgeboski> yes
< jgeboski> it might require some changes in the configure/makefiles for bitlbee, but all of those changes should be trivial as well
< dx> neat
I've followed this wiki page: http://wiki.bitlbee.org/HowtoHipchat
But I get Unknown protocol
when trying to
account add hipchat [email protected] <password>
Is there a step missing in the wiki page? Do I need to change some settings in configure
when making bitlbee?
The fix for the missing arpa/nameser.h types on OpenBSD broke the cygwin build. The detect_nameser_ns_types code is not called and does not correctly compile on other platforms causing redundant type definitions.
Trac: http://bugs.bitlbee.org/bitlbee/ticket/785
There's a patch in there, but it's not correct.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.