**** BEGIN LOGGING AT Wed Apr 27 02:59:58 2016 Apr 27 10:33:01 good to see you all Apr 27 10:33:20 infobot, how are you? Apr 27 10:33:21 zamn900: just great Apr 27 10:33:40 infobot, how is your master? Apr 27 10:33:41 I think you lost me on that one, zamn900 Apr 27 10:34:03 why? Apr 27 10:34:25 what have you done to your creator infobot? Apr 27 10:35:33 infobot, do you know what's about yappari? Apr 27 10:35:33 yes, I know what's about yappari. Apr 27 10:35:58 explain that Apr 27 10:36:47 moin :) Apr 27 10:36:55 infobot, you are still dumb Apr 27 10:36:56 zamn900: what are you talking about? Apr 27 10:37:34 infobot, you are still insufficient Apr 27 10:37:34 I think you lost me on that one, zamn900 Apr 27 10:37:50 like I said Apr 27 10:38:41 infobot, does your creator know that you are that dumb? Apr 27 10:38:43 zamn900: okay Apr 27 10:39:17 well... nothing personal Apr 27 11:49:25 luke-jr: ah, sweet , you're asking the questions i wanted to see answered @ pyra forum ;) Apr 27 11:49:34 or eh , question* Apr 27 11:49:36 :P Apr 27 11:50:24 luke-jr: now if only i cared enough to fix his php ;) Apr 27 12:16:13 infobot, have you been fixed? Apr 27 12:16:56 I suppose yes Apr 27 12:50:19 ~forget does your creator know that you Apr 27 12:50:19 DocScrutinizer05: i forgot does your creator know that you Apr 27 12:55:14 that you are dumb, infobot... yea Apr 27 17:33:27 now libaxoltl is segfaulting Apr 27 17:33:28 :( Apr 27 17:33:50 ): Apr 27 17:35:42 new gcc PogChamp Apr 27 17:36:16 freemangordon: giev packages compiled with gcc 6.1 Apr 27 17:41:36 ceene, sorry for your fails... but all heroes sacrifices and suffer Apr 27 17:44:33 and reception doesn't seem to work either Apr 27 17:44:34 :( Apr 27 17:57:45 ceene you can do that Apr 27 17:57:55 we trust you Apr 27 18:48:18 buZz: which one? :P Apr 27 19:58:51 ceene, I don't know how to do it by myself Apr 27 19:59:22 but if you can please subscribe me at the updates about yappari Apr 27 19:59:40 I can tell my email to you in private Apr 27 20:04:06 ahycka, hello, what's the topic in maemo forum about yappari? Apr 27 20:04:46 how can I subscribe to get updates about the eventually new version of yappari? Apr 27 20:05:09 i dont know, im very happy with my android xD Apr 27 20:05:20 rofl Apr 27 20:06:14 i only give a phone number to ceene, and help him yesterday with yapari Apr 27 20:06:31 yappari Apr 27 20:07:46 yappari (yapari), whatsapp (guasap), its the same xD Apr 27 20:09:31 no waaaaaay Apr 27 20:10:22 i can't subscribe you to anything, zamn900 Apr 27 20:10:36 no waaaaaay Apr 27 20:10:42 you'll have to look the thread Apr 27 20:11:14 i was happier yesterday than tonight, more problems have arisen Apr 27 20:11:19 then that it's what I am talking about Apr 27 20:11:24 the damn thread Apr 27 20:12:01 ahycka: thanks for your help :) Apr 27 20:12:32 so as you will overwrite on the thread I will get notice of the new yappari Apr 27 20:13:10 zamn900: but i don't have control over who receives mail notifications Apr 27 20:13:16 no Sicelo Apr 27 20:13:32 sometimes i hate android -.- Apr 27 20:13:38 I will keep myself updated by the thread Apr 27 20:13:40 np Sicelo :) Apr 27 20:13:49 i don't mean that .. you're helping us lending him your number ;) Apr 27 20:13:59 and providing moral support, i assume :) Apr 27 20:14:03 ceene, or Sicelo which is the thread of yappari Apr 27 20:14:03 :) Apr 27 20:14:10 yay for support! Apr 27 20:14:40 I did som fan part anyway Apr 27 20:14:42 and debugging suggestions Apr 27 20:14:45 not only moral, i help him debugging :) Apr 27 20:14:54 fanning is not moral? Apr 27 20:16:12 see .. that's a lot of help. thanks a mil for that Apr 27 20:18:38 do you confirm this? http://talk.maemo.org/showpost.php?p=1503625&postcount=1397 Apr 27 20:19:36 yep Apr 27 20:20:37 so you will eventually edit that post... or write another one to give notice of the new yappari Apr 27 20:20:49 of course Apr 27 20:20:58 eventually Apr 27 20:21:04 thanks Apr 27 20:21:27 i don't know what's faiing now :( Apr 27 20:21:44 can't receive, can't send messages Apr 27 20:21:51 not so useful right now Apr 27 20:22:11 super se cret salts? Apr 27 20:22:32 no, right now is a bug on libwa or yappari Apr 27 20:22:44 sending messages end up segfaulting Apr 27 20:23:07 write text mode wrapper around the code and debug? Apr 27 20:23:09 and receiving follows an absurd codepath Apr 27 20:24:31 extensive debugging rquired right now... Apr 27 20:42:27 subscribed Apr 27 20:43:07 luke-jr: evildragon's bitpay php issue :P Apr 27 20:43:44 buZz: dunno what that is Apr 27 20:43:51 oh Apr 27 20:43:55 pyra :) Apr 27 20:44:01 * luke-jr reloads the forum Apr 27 20:46:02 buZz: you forgot to like my post :P Apr 27 20:47:02 yeah just made a account ;) Apr 27 23:09:54 kerio: what is giev? Apr 28 00:12:32 Is libotr2 v3.2.0-4 on maemo compromised or not? https://www.helpnetsecurity.com/2016/03/10/critical-bug-libotr-open-users-chatsecure-adium-pidgin-compromise/ Apr 28 00:26:52 Anybody wants to test the glibc-PoC-exploit? http://www.securityweek.com/remote-code-execution-flaw-patched-glibc-library Apr 28 00:34:05 Maemo uses libc6 2.5, correct? And much of the world moved on to libc6 2.7, what the difference? If it's only bug fixes, it may be doable. If it's not backward-compatible, it's annoying Apr 28 00:39:03 telepathy-gabble with OTR support, around 2014: what version of telepathy-gabble? https://git.collabora.com/cgit/user/xclaesse/telepathy-gabble.git/log/?h=otr Apr 28 00:39:20 glibc is backwards compat, it has versioned symbols Apr 28 00:39:22 afaik Apr 28 00:39:59 if you are talking about the dns problem, I think that was fixed. Apr 28 00:40:24 Okay, would there be problems if I tried to install libc6 2.7 on Maemo?.. And was it fixed on Maemo platform? Apr 28 00:41:14 Like, does current-on-Maemo glibc have this vulnerability? Apr 28 00:41:24 cssu has the fix iirc Apr 28 00:41:32 either that or we are not vulnerable Apr 28 00:41:56 wrt installing new version: I don't know. probably (you will run into problems) Apr 28 00:43:29 Why does libc6 2.13 depend on libc-bin when libc6 2.5 does not depend on a libc-bin? Apr 28 00:43:49 * Oksana wishes me could test libc6 2.13 in a maemo virtual machine Apr 28 02:33:12 http://www.tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html Apr 28 02:40:57 >>Usually you can update libraries without concern; if there was an API change, the library creator is supposed to change the soname. That way, multiple libraries can be on a single system, and the right one is selected for each program<< Apr 28 02:43:21 IOW all glibc6.so.2.* are supposed to be API compatible Apr 28 02:44:40 updating to glibc6.so.3.* wouldn't do anything except allow for *new* programs to use the new glibc, *old* programs would need and use glibc6.so.2 still Apr 28 02:49:10 DocScrutinizer05: a recent Gentoo glibc update broke fork() Apr 28 02:49:13 fyi Apr 28 02:49:33 (it got to stable :/) Apr 28 02:50:40 well, it's amazing how little lib devels seem to understand about how libs actually are supposed to work Apr 28 02:51:04 ABI is actually quite complicated :/ Apr 28 02:51:30 *highly* recommended: http://www.tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html Apr 28 02:51:45 >>3.6. Incompatible Libraries<< Apr 28 02:52:35 >>If you can avoid these reasons, you can keep your libraries binary-compatible. Said another way, you can keep your Application Binary Interface (ABI) compatible if you avoid such changes. For example, you might want to add new functions but not delete the old ones.<< Apr 28 02:52:39 2. Exported data items change (exception: adding optional items to the ends of structures is okay, as long as those structures are only allocated within the library). Apr 28 02:52:44 ^ this exception can be wrong! Apr 28 02:53:19 well, it is correct as long as devels don't do bullshit Apr 28 02:53:28 struct inside another struct Apr 28 02:53:47 hmm Apr 28 02:53:48 you end up moving everything in the external struct after it :/ Apr 28 02:53:55 yep Apr 28 02:54:13 * luke-jr has actually goofed this before >_< Apr 28 02:54:26 that's pretty poor coding practice in my book though Apr 28 02:55:14 you shalt not assume about properties of a structure you inherit from inside an opaque source like a lib Apr 28 02:55:44 neither aqbout size nor any other properties, as long as you don't derive such properties from same origina as the object itself Apr 28 02:56:54 thus it's a logical deivative of "as long as those structures are only allocated within the library" Apr 28 02:56:57 well, both structs were in the same lib ;) Apr 28 02:57:19 and the external one only had a pointer to the internal one, so I figured it was safe Apr 28 02:57:29 but it happened to be an array ;) Apr 28 02:58:46 when your larger structure embeds the extended data structure, then the original extendad data structure is ABI compatible but your embedding structure breaks ABI compatibility Apr 28 02:59:32 even when the larger structure that embeds the changed one is from same library **** ENDING LOGGING AT Thu Apr 28 02:59:58 2016