libera/#maemo-leste/ Thursday, 2021-10-28

uvosWizzup: so about sphone-store10:47
uvosWizzup: i want to drop everything except the call and sms logging.10:48
uvosWizzup: here is what the new tables looks like: https://github.com/maemo-leste/sphone/blob/c325a8aa7c1c76a39f10c07a00837ed912c3072c/src/utils/store.c#L10710:49
uvosvs https://github.com/maemo-leste/sphone/blob/e19fb96bf6f0ef95b76811b349a748daa18933bb/src/utils/store.c#L14010:49
uvosand adding events10:50
uvoshttps://github.com/maemo-leste/sphone/blob/c325a8aa7c1c76a39f10c07a00837ed912c3072c/src/utils/store.c#L23210:50
uvosvs https://github.com/maemo-leste/sphone/blob/e19fb96bf6f0ef95b76811b349a748daa18933bb/src/utils/store.c#L30310:51
uvosthats all fine10:51
uvosbut then https://github.com/maemo-leste/sphone/blob/store/src/utils/sphone-store-tree-model.c needs to select on those tables via its filters10:51
uvosand it more or less looses me there due to lack of sql knowlage10:51
uvosreally we would only need SPHONE_STORE_TREE_MODEL_FILTER_SMS_ALL, SPHONE_STORE_TREE_MODEL_FILTER_CALLS_ALL to work10:54
Wizzuprandom idea I do want to pitch, what about using the rtcom database structure? http://maemo.org/api_refs/5.0/5.0-final/eventlogger/10:55
uvosand SPHONE_STORE_TREE_MODEL_FILTER_SMS_MATCH_DIAL_ID SPHONE_STORE_TREE_MODEL_FILTER_SMS_MATCH_CONTACT_ID with something that matches on line_identifier and backend10:55
uvos*replace10:55
WizzupI don't know what dependencies the rtcom libraries have, but it might be entirely without hildon10:59
uvosWizzup: sure that might be ok10:59
Wizzupseems to be just glib and sqlite310:59
Wizzupand dbus10:59
Wizzup(not sure what for)10:59
Wizzuprtcom-eventlogger-plugins has rtcom-el-plugin-call and rtcom-el-plugin-sms11:00
uvosidealy id like to replace sphone-store-tree-model with something that just ingests a vector of CallProperties or MessageProperties to create the GtkTreeModel11:00
uvoshttps://github.com/maemo-leste/sphone/blob/store/src/modapi/types.h11:00
Wizzuphttps://github.com/maemo-leste/rtcom-eventlogger-plugins/tree/master/src11:01
uvosand then some store backend provides functions to translate whatever backend format into those11:01
Wizzupright11:02
uvossince rn its also very gtk specific, something none of the rest of non ui sphone is anymore11:02
Wizzupright11:02
Wizzuphttps://github.com/maemo-leste/rtcom-eventlogger-ui/blob/master/example/example.c11:04
Wizzupto be clear I have not looked rtcom eventlogger in detail at all yet11:04
Wizzupbut finding some interesting things11:04
Wizzuplooks like there is some code there to populate a gtk tree view and such from the events as well11:05
Wizzupso I think rtcom-eventlogger-ui is mostly testing stuff, not things we'd need, and then rtcom-eventlogger and rtcom-eventlogger-plugins are ui and hildon agnostic11:07
Wizzupthe rtcom-eventlogger-ui seems to do abook stuff as well11:07
Wizzupfrom a quick glance11:07
Wizzupuvos: so do you want me to look at the specific sql question you had now or do you want to investigate a more abstract model and/or rtcom-el?11:08
uvosim fine with either11:08
uvosrtcom looks ok to depend on i think11:08
uvos"please figure out how to make this work while not forceing sphone ui to be gtk and preferably just provide the ui with an array of sphone call/message structs"11:10
Wizzupok so the rtcom dbus dependency is only for timezone changes11:11
uvosdepending on dbus isent a big issue11:11
uvossphone dose too11:11
Wizzupyeah, just wanted to make sure there wasn't some other service11:11
uvosfor uinque11:11
uvos(and some of its modules also depend)11:12
Wizzupso my plan is to finish the news post by tonight or tomorrow at latest11:12
uvosok11:12
uvosneat11:12
Wizzupand then work on audio (hopefully just a few days) and then this/rtcom/conversations11:12
uvosi would enjoy if you flip the last 2 things11:12
Wizzupok11:12
Wizzupcould probably do that11:13
uvosalso gives me some time to look into plug detection again11:13
uvosok need to run ttyl11:13
Wizzupttyl11:14
Wizzupfreemangordon: https://www.phoronix.com/scan.php?page=news_item&px=X.Org-Server-21.111:57
lelparazyd created a repository: https://github.com/maemo-leste-upstream-forks/wireguard-tools13:24
freemangordonWizzup: :)13:35
freemangordonhmm, I think I found our pvr_dri source code14:32
Wizzupah?14:32
freemangordonhttps://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/72f54d8ee166e26ff110f7bc12bd62ec037dae09/media-libs/mesa-img/files/0000-Add-pvr-dri-driver-to-the-Mesa-build.patch14:32
freemangordonso far I have 100% match while REing14:32
freemangordonbasically, it seems out '1.17' is 1.6 or something like14:33
Wizzuphm14:33
uvosWizzup: i presume he means he found the code from pvr_dri in ti blobs14:33
Wizzupyeah14:34
freemangordonyeah14:34
freemangordon'or' == TI blobs14:34
freemangordon*our14:34
uvosyeah14:34
freemangordonit does not match what 'your' mesa has14:34
freemangordonbut I am working on it14:35
Wizzupit froze my firefox hehe14:35
freemangordonit is lengthy, yeah14:35
uvosalso ff-93 has been pretty terrible on my end...14:36
freemangordonff66 here, have no issues with it :)14:37
lelparazyd edited a repository: https://github.com/maemo-leste-upstream-forks/wireguard-tools14:42
freemangordonhmm, those blobs are very, very, old version of the driver15:02
freemangordonthe ones TI provided15:02
freemangordonbut, it is what it is15:03
uvosimgtek proububly dropped sgx at some point and ti releases are based on some legacy maintinace branch.15:09
freemangordonbut where chromeos gets their drivers then?15:09
uvoschomeos pvr is aimed at rouge and later after all15:09
uvos*rogue15:09
freemangordonah15:09
freemangordonyeah, ok15:09
freemangordonthat makes sense15:10
Wizzupuvos: were you suggesting before to skip sphone updates for now in the news post?16:21
uvos?16:23
uvosi dont remember mentioning sutch a thing16:23
uvosInput device name: "Mapphone Audio Headphones"16:23
uvosEvent code 2 (SW_HEADPHONE_INSERT) state 016:24
uvos:)16:24
uvosEvent: time 1635431030.607635, type 5 (EV_SW), code 2 (SW_HEADPHONE_INSERT), value 116:24
uvosbut pulse dosent do anythin :\16:24
Wizzupuvos: ok, so then I'll cover sphone a bit in the news post16:25
Wizzupuvos: nice @ plug detection16:25
Wizzupregarding pulse acting on it, recently I looked up what exactly it acts on / read, but I don't remember anymore16:26
WizzupI don't think pulse necessarily acts on that16:26
parazydWizzup: I think we should conflict with resolvconf package if we want to keep our DHCP functionality for multiple interfaces.16:26
parazyd(i.e. all nameservers for wlan + gprs + etc...)16:27
parazydWe can do so from hildon-connectivity-base16:27
Wizzupwe need resolvconf for wireguard though16:27
parazydDo we?16:27
Wizzupcan't we just make edit dnsmasq config ?16:27
parazydIt's just a recommended pkg16:27
parazydNot a hard dep16:27
Wizzupwell, something must write the wireguard dns addrs16:27
parazydah right16:28
Wizzupit seemed to solve a real problem within wg-quick, also something must *restore* the dns entris16:28
parazydmhm then we must make dnsmasq ignore it.16:28
parazydI have to test how all this works together.16:28
Wizzupafaik the dnsmasq config just points to some files16:28
parazydYes16:28
Wizzupwell you can already have dnsmasq ignore it with a single flag, as I mentioned in the issue report16:28
parazydWe have 00leste_dns in /etc/dnsmasq.df16:28
Wizzupbut I was wondering we could maybe have them properly interoperate16:29
Wizzupbut IDK why we even have per-interface dns entries in leste16:29
uvospacmd16:29
uvosNo PulseAudio daemon running, or not running as session daemon.16:29
uvosgreat16:29
uvosi dont get to inspect pa via its shell16:29
Wizzupuvos: there is a workaround for that somewhere16:29
parazydWizzup: Because you can be connected to both gprs and wifi, then both nameservers can be used16:29
Wizzupuvos: try pactl btw16:29
uvospactl dosent provide what i need16:29
parazydI'm not sure how to work properly with resolvconf tooling16:29
Wizzupuvos: https://pulseaudio-bugs.freedesktop.narkive.com/RyQTiLPL/222-pacmd-doesn-t-work-with-pulseaudio-running-as-a-system-wide-daemon16:29
Wizzupuvos: maybe grep logs in this channel for pacmd, I solved it for myself a whileago16:30
Wizzupparazyd: me neither, but the current maemo setup felt like a hack for me16:31
uvosWizzup: grep pacmd in the logs dosent bring anything up16:31
Wizzupuvos: sec16:31
uvosexcept clort complaining about the same problem16:31
Wizzupok16:32
Wizzupuvos: found it in my notes16:33
WizzupMaking pacmd work16:33
Wizzup=================16:33
WizzupAdd this line to /etc/pulse/system.pa:16:33
Wizzupload-module module-cli-protocol-unix16:33
WizzupThen run as::16:33
WizzupPULSE_RUNTIME_PATH=/var/run/pulse pacmd16:33
uvosside note16:34
uvos /etc/init.d/pulseaudio restart is broken16:34
uvosit starts pulse to soon (before the old instance exits)16:35
uvosWizzup: yeah that works16:35
parazydMaybe that can be exported in /etc/profile?16:37
uvoswhy dont we just start pulse as a session deamon...16:37
parazydWizzup: Should I port our DNS setup to resolvconf?16:37
parazydI think I know how to do it16:37
parazydWizzup: But I'll need some help since I don't have a SIM ready so can't test both connections at the same time.16:38
WizzupI think it's worth trying, yes16:38
parazydok16:38
WizzupI don't think we can have both connections at the same time16:38
Wizzupwhat makes you think we can do that?16:38
uvosbtw16:38
parazydWizzup: Oh, we can't?16:38
uvosi hate whoever decided to name a popular sound server jack16:38
Wizzupparazyd: I don't know any way to do it with the UI for sure16:38
parazydWizzup: It's possible on linux in general, so I thought so16:38
Wizzupuvos: poettering started pulse16:38
parazydBut true, icd doesn't allow this16:38
uvosi cant google jack about pulse and jacks without jack geing in the way16:38
Wizzupoh16:39
Wizzupyou mean JACK16:39
uvosyeah16:39
parazydWizzup: So, without changes, our current DNS setup works with resolvconf as well. It still seems to respect the 00leste_dns17:18
parazydWizzup: Can you tell me how you trigger the breakage?17:18
tmlindnice :)17:19
tmlindfor the event code i mean17:19
Wizzupparazyd: when I start something in wg, and disable wg again, I have no working dns17:19
Wizzupall resolves fail17:19
Wizzupand this is because of dnsmasq trying to load servers from a non existent file17:20
parazydMy current /etc/resolv.conf is generated by resolvconf. Removing /var/run/resolv.conf.wlan0, and kill -SIGHUP `pidof dnsmasq` makes DNS not resolve. Reconnecting wifi brings back the wlan0 file and DNS continues working.17:20
parazydOk, I will try now with wireguard.17:20
Wizzupit should not try to load the wlan0 file ever since resolvconf exists17:20
Wizzupper the config/init script of dnsmasq17:20
parazydWizzup: It loads it, that's /etc/dnsmasq.d17:20
WizzupI'll redo my research and explain, just a second17:21
parazydWe never change /etc/dnsmasq.conf17:21
uvospa works :)17:22
Wizzupso in /etc/init.d/dnsmasq:17:22
Wizzupif [ ! "$RESOLV_CONF" ] &&17:22
Wizzup   [ "$IGNORE_RESOLVCONF" != "yes" ] &&17:22
Wizzup   [ -x /sbin/resolvconf ]17:22
Wizzupthen17:22
Wizzup        RESOLV_CONF=/run/dnsmasq/resolv.conf17:22
Wizzupfi17:22
uvosi have fully working plug deteion on my d4 :)17:22
Wizzupand then it starts with:17:22
Wizzup                ${RESOLV_CONF:+ -r $RESOLV_CONF} \17:22
uvoswell except that the device dosent know if its booted with hp plugged or not17:22
Wizzupparazyd: so the command line args tell it to ignore other stuff and only read the ones from that file afaict17:22
Wizzupuvos: sweet, what else did you change17:22
uvosi was reporting the jack on the wrong dpms pin17:23
uvos(ie was kernel problem)17:23
Wizzupparazyd: this is worked around in /etc/default/dnsmasq by setting IGNORE_RESOLVCONF17:23
uvosand i had to add load-module module-switch-on-port-available17:23
Wizzupparazyd: this was the only way I was able to get dns17:23
uvosto system.pa17:23
Wizzupuvos: ok, in other settings ohm might do this17:23
parazydWizzup: Have you looked at /run/dnsmasq/resolv.conf ?17:24
parazydFor me it points to 127.0.0.1, and then dnsmasq continues with our .$interface resolv files.17:24
parazyd(This is a new image, with only resolvconf installed)17:24
Wizzupthat file is empty for me17:24
parazydok17:25
Wizzuproot@maindroid:~# wc -c /run/dnsmasq/resolv.conf17:25
Wizzup0 /run/dnsmasq/resolv.conf17:25
parazydI'll try now with wg and see what happens.17:25
WizzupI do have the ignore option set, but I recall that file was empty before I set that option as well17:25
Wizzupwhich is why I disabled the resolvconf integration17:25
WizzupIt's not clear to me what writes that file17:25
Wizzupthanks for chasing this down17:25
parazydWizzup: Is wireguard-maemo the package that'll pull everything?17:26
parazyd(I forgot, sry)17:26
WizzupI don't know, I'd do it through the application manager17:27
Wizzup(just to see what else might break/complain)17:27
parazydWizzup: Mind if I remove wireguard-dkms dep from libicd-wireguard?17:27
WizzupI think we should remove it17:28
Wizzupso please do17:28
parazyd*nod*17:28
Wizzup(since we ship it in our kernels)17:28
parazydExactly17:28
Wizzupuvos: that's great though, does it also switch the UCM profile(s)?17:31
Wizzup(I suppose it shouldn't)17:31
uvosofc it dose17:33
uvoswell not profiles17:33
uvosit switches the profile outputs17:33
uvosas defined in ucm17:33
Wizzupok17:34
uvossphone swtiches profiles17:34
uvosfor ringing and for volice call17:34
uvosits route-pulseaudio module dose this17:35
uvosyou can unload it ofc17:35
Wizzupok17:35
Wizzupwell you asked me to postpone ohm stuff until some rtcom stuff, so I'm just going to try not to think about it too much since my head is full :p17:36
Wizzupthat's really great though17:36
parazydWizzup:17:37
parazydSetting up libicd-network-wireguard:armhf (0.1.2+2m7.3) ...17:37
parazydbash: icd2-manage-modules: command not found17:37
parazydThat's a bug17:37
Wizzuphm let me see17:37
Wizzupwhat is this command a part of again :)17:38
parazydI think the script you wrote to edit gconf arrays17:38
Wizzupyeah17:38
parazydmaemo-system-services17:38
Wizzupisn't that installed already?17:38
Wizzupor was it not pulled in as upgraded package?17:39
parazydLet me see17:39
parazydI think the latter indeed, I have about 75 devel updates17:39
uvoswe should downmerge into stable too17:41
uvosfor this newspost17:41
uvos(imo)17:41
uvosat least some safe stuff17:41
Wizzupyes17:42
Wizzupthat's the plan17:42
parazydWizzup: After that:17:52
parazydSetting up libicd-network-wireguard:armhf (0.1.2+2m7.3) ...17:52
parazydERROR: requested network_type GPRS does not exist in /system/osso/connectivity/network_type (['WLAN_ADHOC', 'WLAN_INFRA'])17:52
parazydWizzup: It shouldn't fail on this17:53
parazyd(Can also continue in private if you prefer and this is too noisy)17:53
Wizzupparazyd: this is also fixed, did you fully update?17:53
Wizzupoh, I see17:53
parazydYes just got the latest maemo-system-services-dev17:54
WizzupI see, that's a problem17:54
WizzupI guess one of the tricky parts here is that if we ignore the error, and if you then install gprs network modules after, the gprs module will not contain the proper entries17:54
Wizzupunless there is some trigger to re-run the script(s)17:55
parazydYes, but for example we can also run the scripts on hildon-connectivity-* metapackage (un)installs17:56
parazydMaybe that's a good way to keep gconf up to date17:56
Wizzupwhat if someone installs gprs pkgs manually?17:56
WizzupI don't know how triggers work, but they might be better here imho17:56
Wizzupas in, we can change many things without bumping the meta pkg17:57
parazydAn example hook we have is /etc/apt/apt.conf.d/142updatehildonmenu17:57
parazydThat's the only way I know to always trigger some binary on apt17:57
Wizzuprun, and it runs every time17:58
parazydYep17:58
WizzupI don't know what a good solution is here tbh17:58
WizzupI can make the error non fatal for starters17:58
parazydMe neither17:59
Wizzupbut more needs to happen to make it not painful later on17:59
parazydThat'd be good, thanks17:59
Wizzuppushed to master on maemo-system-services18:00
parazydty18:02
parazydWizzup: Install goes through now, thanks. Note that it'd fail both on GPRS and DUMMY.18:24
parazydWizzup: So we probably want some general trigger for icd modules.18:24
Wizzupright18:36
parazydWizzup, uvos: Ping20:14
parazydDo you have a wireguard applet setup already?20:14
Wizzuppong20:24
parazydHey20:37
parazydCould you try reenabling resolvconf in /etc/default20:38
parazydAnd then connect and disconnect wireguard20:38
parazydSee if DNS breaks then20:38
parazydIf so, then `touch /var/run/resolv.conf.*`. See if DNS is fixed.20:38
parazydIf not, `kill -SIGHUP `pidof dnsmasq``20:38
parazydSee if you can do DNS then.20:39
sicelotouch /var/run/resolv.conf.* will create that file. is that what you really want?20:40
parazydNo, but it'll work20:49
parazydThere should be a wlan0 or some20:49
Wizzupparazyd: yeah ok let me test21:04
Wizzupparazyd: so when I uncommented the line in /etc/default/dnsmasq, and restarted dnsmasq, I immediately have dns problems21:05
WizzupI didn't even enable wireguard21:05
Wizzupdo you want me to try the touch now?21:05
Wizzup(I was on gprs)21:05
Wizzuprestarting dns on wifi also causes the error(s)21:07
Wizzupas in, try to connect over wifi, and then issue /etc/init.d/dnsmasq restart21:07
parazydReconnect icd21:08
Wizzupparazyd: as a workaround, or what?21:09
parazydReconnecting icd should make dns work21:09
parazydAnd then try wireguard21:09
Wizzupcan we make it so that restarting dnsmasq while connected to an AP doesn't make it fail?21:10
Wizzupthe touch works for me21:10
parazydI have to check @ restart21:11
parazydBut nothing should be restarting dnsmasq anyway21:11
parazydIn any case21:13
parazydWe then need to touch the files after wg-quick down21:13
parazydYou didn't have to sighup dnsmasq?21:14
Wizzupno21:15
Wizzupis there no more robust way?21:15
Wizzupas in, why does this even happen exactly?21:16
parazydok, great21:17
Wizzupso what's the real difference, why does this happen?21:18
parazydThis happens because resolvconf and wg-quick change the configuration upon enabling. So when after wg-quick down it returns, the files have to be triggered for dnsmasq to pick up the change.21:18
Wizzupthere must be a way to make dnsmasq not that stupid21:18
parazydThis ia because our setup is watching those multiple resolv.conf.interface files21:18
parazydI don't know another way21:19
parazydAnd touching the files doesn't really seem bad tbh21:19
WizzupI think it is pretty darn bad21:20
sicelomaybe we don't need dnsmasq anymore? the main reason it was there in fremantle was to help with caching, and not having to muck with /etc/resolv.conf for each connection21:20
Wizzupparazyd: so what file does wg-quick create21:20
siceloif we are using resolvconf, i guess that negates its need21:20
Wizzupparazyd: shouldn't dnsmasq.conf have interface=lo ? I don't think we want it to be lo,wlan021:21
parazydWe aren't changing dnsmasq.conf21:22
Wizzupsame question :)21:22
parazydI dunno, there's a dnsmasq.lo file21:23
parazydAnd it points to localhost21:23
Wizzupyes, but the service is exposed over wireless21:23
Wizzupas I discovered a few weeks ago21:23
parazydBut our icd ipv4 setup makes the other files21:23
parazydSo if someone wants to change that setup, they're more than welcome21:24
parazydI'm just trying to solve this with our current setup, and this is the solution I'm offering.21:24
Wizzupso the solution is to add C code  to libicd-wireguard to touch a glob of files upon disconnect?21:25
parazydI suppose21:26
Wizzupnot going to happen21:26
Wizzupso why do you think the problem is gone when -r /run/dnsmasq/resolv.conf is not passed?21:27
Wizzupis it just an mtime thing?21:27
parazydI think so, dnsmasq seems to watch those files we set in /etc/dnsmasq.d21:28
Wizzupas far as I can tell the problem is that /run/dnsmasq/resolv.conf is empty and it tries to use that21:28
parazydThat's not the problem, it can remain empty21:28
Wizzupif resolvconv would manage our iface addrs it should be fine, too21:28
Wizzupthen it would never be empty21:29
Wizzupbut that requires use to change our icd scripts to use resolvconf21:29
parazydActually I think it's empty even when wg-quick up21:29
parazydNeed to check21:29
Wizzupit's not21:30
Wizzupthat was in my bug report iirc21:30
parazydIt should be possible to add a script in /etc/maemo-dhcp21:30
Wizzupso with wireguard on it contains 'nameserver 8.8.8.8'21:30
parazydTo so some kind of resolvconf setup21:30
parazydaha21:30
parazydThen maybe we can move the dns setup from the current script and split it into another21:31
parazydAnd use resolvconf21:31
Wizzupyeah, and only use the resolvconf file in dnsmasq21:31
parazydYes21:31
WizzupI wonder if it is also because we use udhcpcd21:32
Wizzupthere seems to be a dhclient hook available21:32
Wizzup( /etc/dhcp/dhclient-enter-hooks.d/resolvconf )21:34
WizzupI don't know how to tell resolvconf what to load though21:35
Wizzupso it looks like we either make our own resolvconf scripts21:36
Wizzupor we use dhclient which has the hooks avail in debian21:36
parazydI'd first try with our own21:37
parazydAt least to learn how it works21:38
parazydBetter than changing two components at once21:38
Wizzupdo you want to do it?21:41
Wizzupotherwise I think I will probably opt for dhclient since then I don't need to know how resolvconf works ;)21:41
Wizzupand it's the debian way(tm)21:42
Wizzuphttps://lists.debian.org/debian-devel/2003/07/msg00438.html21:43
parazydWhatever you prefer21:43
Wizzuplooks like it's basically just this:21:44
Wizzupecho "nameserver $DNS1" | resolvconf -a $IFACE21:44
Wizzupand -d $IFACE to remove it21:44
Wizzupsorry for being a pain here btw, I just don't want to add the touch calls :P21:45
WizzupI'm fine with keeping udhcpc or going dhclient way, but I think either way we agree that we ought to go the resolvconf way?21:46
Wizzupso we'd get rid of the fremnatle hacks with a file per interface and let resolvconf take it over21:46
Wizzupso basically what sicelo said21:46
Wizzupfreemangordon: ^^ opinions?21:46
WizzupI wonder if this will also get us ipv6 for free, or if this will actually cause headaches ;)21:47
parazydYeah let's use resolvconf21:47
parazydIt could be worth it21:47
Wizzupwe could move our dbus-send to /etc/dhcp/dhclient-enter-hooks.d/50_maemo_ipv421:48
Wizzupfrom /etc/maemo-dhcp/50_ipv4_network_setup21:48
parazydThere's however also 'domain', and 'search', not just 'nameserver'21:48
Wizzupright, I wasn't suggesting to actually use the echo command21:48
Wizzupit probably just takes whatever file (via <)21:48
parazydmhm21:49
parazydBut if we pick dhclient, I guess this happens magically21:49
Wizzupyes21:49
WizzupI think I'd prefer to move to dhclient, I can try to modify libicd-network-ipv4 for this purpose21:49
parazydAlright, sounds good.21:49
parazydThanks21:49
parazydThen also remove 00leste_dns21:50
Wizzupyes21:50
Wizzuphttps://github.com/maemo-leste/bugtracker/issues/583#issuecomment-95415238721:52
freemangordonno opinion, sorry22:56
Wizzupok22:59

Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!