| 00:10.06 | *** join/#maemo jonwil (~jonwil@27-33-80-219.tpgi.com.au) |
| 00:14.33 | jonwil | hi |
| 00:25.17 | *** join/#maemo Smily (~SmilzOrg@ip5f5aea67.dynamic.kabel-deutschland.de) |
| 00:25.18 | *** join/#maemo dafox (~dafox@2a02:a448:c25a:1:7061:3b2a:37df:ded3) |
| 01:22.39 | *** join/#maemo chainsawbike (~chainsawb@unaffiliated/chainsawbike) |
| 02:49.28 | *** join/#maemo pagurus (~user@p4FDC376A.dip0.t-ipconnect.de) |
| 02:53.09 | *** join/#maemo Mike_a320 (d31f1b25@gateway/web/freenode/ip.211.31.27.37) |
| 04:01.21 | *** join/#maemo lxp1 (~lxp@unaffiliated/lxp) |
| 04:10.32 | DocScrutinizer05 | ~memory |
| 04:10.32 | infobot | The memory smacks of usage!, or vulnerable, see http://abcnews.go.com/Technology/story?id=98195&page=1 |
| 04:32.43 | *** join/#maemo povbot (~supybot@office.pov.lt) |
| 05:38.04 | Juesto | hmm |
| 05:38.33 | *** join/#maemo DocScrutinizer06 (~saturn@openmoko/engineers/joerg) |
| 08:12.47 | *** join/#maemo NeKit (~nekit@188.162.203.89) |
| 08:28.23 | *** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian) |
| 08:29.01 | *** join/#maemo shentey (~shentey@p4FF0FE7B.dip0.t-ipconnect.de) |
| 08:31.52 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 09:21.37 | *** join/#maemo Michael_a320 (d31f1b25@gateway/web/freenode/ip.211.31.27.37) |
| 09:35.44 | *** join/#maemo chainsawbike (~chainsawb@unaffiliated/chainsawbike) |
| 09:55.51 | *** join/#maemo NeKit (~nekit@85-95-187-85.saransk.ru) |
| 09:58.47 | *** join/#maemo xorly (~xorly@ip-89-176-102-19.net.upcbroadband.cz) |
| 10:27.56 | *** join/#maemo cyphase_eviltwin (~cyphase@unaffiliated/cyphase) |
| 10:28.37 | *** join/#maemo kerio (kerio@bad.memes.vs.dank.ninja) |
| 10:29.05 | *** join/#maemo deepy (deepy@wrongplanet/deepa) |
| 10:37.59 | freemangordon | Pali: ping |
| 10:48.39 | Pali | freemangordon: pong |
| 10:50.27 | freemangordon | Pali: check your mail. in short - hildon-status-manu crashing is because of your changes to HAM |
| 10:50.34 | Pali | saw |
| 10:50.46 | Pali | about https://github.com/community-ssu/hildon-application-manager/commit/3edbb49dc6c2ee66917c8f165f6a52ee10df1984 |
| 10:50.53 | Pali | provider is stored in provider |
| 10:51.10 | Pali | this one should be OK |
| 10:51.11 | Pali | problem is probably in commit 03ed723f3b2439764d3224ef051c6853fd2ebd85 |
| 10:51.20 | freemangordon | see my latest mail |
| 10:52.31 | Pali | yes, double free |
| 10:52.53 | Pali | those commits bring support for "New update" notification |
| 10:53.14 | Pali | on repository.maemo.org should be already present file about new CSSU update |
| 10:53.31 | Pali | ham needs to be configured to use that file instead on downloads.maemo.nokia.com |
| 10:53.39 | freemangordon | aah, I see |
| 10:53.43 | Pali | and it checks it once per day, even apt-get is not running |
| 10:53.52 | freemangordon | ok, got it now |
| 10:53.54 | Pali | so user get information about new SSU update |
| 10:54.23 | freemangordon | Pali: also, see my note re killing h-d on update |
| 10:54.32 | Pali | yes looking on iy |
| 10:54.40 | freemangordon | I think this should be reverted, at least partially |
| 10:55.18 | Pali | killing h-d is not a problem |
| 10:55.23 | freemangordon | an hour ago, when installing testing-testing, I got a dialog asking me about whether to flash cssu-kernel |
| 10:55.34 | Pali | it is already done by HAM |
| 10:55.37 | Pali | via dsme |
| 10:55.43 | freemangordon | but, it was like on 2/3 of the screen, in the upper-left corner |
| 10:55.55 | Pali | I just added another kill_all to make sure even if dsme fails |
| 10:55.55 | freemangordon | hmm, another problem then |
| 10:56.15 | Pali | in some cases dsme can fail |
| 10:56.18 | Pali | this is fallback |
| 10:56.48 | Pali | I just added kill_all for every process which is stopped by dsme (look at that code) |
| 10:56.58 | freemangordon | what is the problem if dsme fails? device cannot be rebooted? |
| 10:57.11 | Pali | dsme stop can fail |
| 10:57.27 | Pali | that is to ensure that all needed processes are stopped |
| 10:57.31 | freemangordon | ok |
| 10:57.37 | Pali | because in the process of upgrade they do not work |
| 10:57.47 | Pali | as libraries in system are changing |
| 10:58.14 | Pali | e.g. hildon-status-menu can reload plugins if they appear in VFS |
| 10:58.26 | freemangordon | ah, I see |
| 10:58.27 | Pali | and so it must be not runinng when doing update |
| 10:58.34 | freemangordon | ok, this is clear now |
| 10:58.39 | Pali | and I saw some situation when dsme did not stopped hildon-status-menu |
| 10:58.51 | Pali | even dsme though hildon-status-menu is already stopped |
| 10:59.12 | Pali | ideally fix that double free |
| 10:59.23 | Pali | and I will try to find where is URL for that SSU notify |
| 10:59.29 | Pali | seems we do not have it in HAM yet :-( |
| 10:59.32 | freemangordon | still, I wonder why I got that ugly dialog. looks like a bug in that piece of SW that shows the dialog |
| 10:59.49 | Pali | new URL should be in next CSSU release |
| 11:00.03 | freemangordon | Pali: so, HAM should not be included in the new -testing, right? |
| 11:00.22 | Pali | should be, but with fix for double free |
| 11:00.39 | freemangordon | (12,59,25) Pali: seems we do not have it in HAM yet :-( |
| 11:00.44 | freemangordon | ^^^ ? |
| 11:00.52 | Pali | we do not have new URL in HAM |
| 11:01.03 | Pali | so still is using old downloads.maemo.... |
| 11:01.09 | Pali | like all versions before |
| 11:01.39 | freemangordon | then why include it if the functionality is the same as before those changes? |
| 11:02.06 | freemangordon | because of killing of the processes? |
| 11:02.36 | Pali | there are other changes too |
| 11:02.42 | freemangordon | ok, going to fix that double-free |
| 11:02.50 | Pali | e.g. include PR1.3 HAM in CSSU |
| 11:02.56 | freemangordon | Pali: unless you want to do it? |
| 11:03.10 | Pali | I'm going to find that URL... |
| 11:03.13 | freemangordon | ok |
| 11:05.14 | Pali | ok, got it |
| 11:05.18 | Pali | old was: http://tableteer.nokia.com/application-notices/notice-${HARDWARE}-fremantle |
| 11:05.26 | Pali | new is: http://repository.maemo.org/application-notices/notice-${HARDWARE}-fremantle.html |
| 11:09.20 | freemangordon | Pali: you're going to change something? |
| 11:09.28 | Pali | yes, just Makefile.am |
| 11:09.35 | freemangordon | ok |
| 11:13.55 | freemangordon | Pali: done |
| 11:14.41 | freemangordon | Pali: please, add entries in changelog as well, so the package to be ready for ilew to build and push it |
| 11:14.51 | Pali | ok |
| 11:39.32 | *** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian) |
| 11:57.57 | Pali | freemangordon: done package is in cssu-devel |
| 11:58.05 | Pali | and also in git on github |
| 12:01.12 | Pali | freemangordon: do you have access to that notice-${HARDWARE}-fremantle.html file? |
| 12:01.29 | Michael_a320 | thanks for all your work. :-) |
| 12:02.15 | Pali | it should be updated every time when new CSSU stable is released |
| 12:08.12 | *** join/#maemo cyphase (~cyphase@unaffiliated/cyphase) |
| 12:21.42 | *** join/#maemo cyphase (~cyphase@unaffiliated/cyphase) |
| 12:28.19 | Sicelo | am in the only one having problem with supl.nokia.com? |
| 12:31.26 | Sicelo | openssl connects to it, but Ovi Maps doesn't seem to succeed getting A-GPS info |
| 12:33.03 | *** join/#maemo trx (ns-team@devbin/founder/trx) |
| 12:35.02 | Sicelo | https://talk.maemo.org/showpost.php?p=1522819&postcount=228 |
| 12:39.06 | *** join/#maemo xorly (~xorly@ip-89-176-102-19.net.upcbroadband.cz) |
| 12:43.26 | DocScrutinizer05 | ~supl |
| 12:43.26 | infobot | supl.nokia.com known to be broken, use alternatives like supl.google.com! Adjusting this detail is via settings screen |
| 12:52.26 | DocScrutinizer05 | but maybe it's just slow |
| 12:52.30 | *** join/#maemo dafox (~dafox@2a02:a448:c25a:1:7061:3b2a:37df:ded3) |
| 12:52.57 | DocScrutinizer05 | or your device missing the cert patch once published and afaik included to CSSU |
| 12:55.18 | DocScrutinizer05 | http://paste.opensuse.org/97725536 |
| 13:02.31 | *** join/#maemo cyphase (~cyphase@unaffiliated/cyphase) |
| 13:03.08 | *** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian) |
| 13:03.42 | *** join/#maemo agomez{M} (~agomeziga@fanzine.igalia.com) |
| 13:04.04 | *** join/#maemo platicus (~matrixirc@fanzine.igalia.com) |
| 13:06.52 | *** join/#maemo ubizzy (~ubizzy@178.58.63.94.rev.vodafone.pt) |
| 13:19.22 | freemangordon | Pali: on which server, r.m.o? |
| 13:19.34 | Pali | http://repository.maemo.org/application-notices/notice-${HARDWARE}-fremantle.html |
| 13:19.45 | freemangordon | I guess yes, lemme check |
| 13:21.02 | freemangordon | Pali: yes, I have access |
| 13:21.06 | Pali | ok |
| 13:21.19 | freemangordon | Pali: wait, what kind of access? |
| 13:21.22 | freemangordon | ssh? |
| 13:21.26 | Pali | edit that file |
| 13:21.59 | freemangordon | Pali: who put it there? |
| 13:22.11 | Pali | do not remember |
| 13:23.06 | freemangordon | what to edit? |
| 13:23.41 | freemangordon | Pali: ^^^ |
| 13:23.45 | Pali | chanlog told me that xes! |
| 13:24.01 | freemangordon | maybe it is better to ask him then |
| 13:24.15 | freemangordon | or it is CSSU that "owns" that file |
| 13:24.18 | freemangordon | ? |
| 13:24.31 | Pali | yes, CSSU stable should own that file |
| 13:24.45 | freemangordon | ok |
| 13:24.51 | Pali | every time when new CSSU stable is released, that file content should be updated |
| 13:25.02 | freemangordon | so, what needs to be edited? |
| 13:25.14 | freemangordon | updated how? |
| 13:25.15 | Pali | so ideally include version number or something |
| 13:25.27 | Pali | content of file needs to be changed |
| 13:25.37 | Pali | to that will trig HAM to show update |
| 13:26.29 | freemangordon | Pali: http://pastebin.com/FsBvYe18 |
| 13:27.01 | freemangordon | Pali: but, this is for -stable, right? |
| 13:27.21 | Pali | when content of that file is changed then HAM show update |
| 13:27.27 | Pali | yes that points to stable |
| 13:27.31 | freemangordon | and updated HAM is not in -stable |
| 13:27.55 | freemangordon | Pali: what about changing <text>Includes latest fixes for Maemo 5 system by Maemo Community</text> to: |
| 13:28.08 | freemangordon | <text>Includes latest fixes for Maemo 5 system by Maemo Community - $VERSION</text>? |
| 13:28.14 | Pali | it can be changed as you wish |
| 13:28.20 | Pali | just content needs to be changed |
| 13:28.29 | Pali | text is shown in that ham notifier |
| 13:28.36 | freemangordon | Pali: ok, but should I do it now? |
| 13:28.43 | Pali | no need |
| 13:28.45 | freemangordon | there is no new CSSU afaik |
| 13:28.48 | freemangordon | ah, ok |
| 13:28.57 | Pali | after HAM will be in cssu-stable |
| 13:29.04 | Pali | and after new cssu-stable will be released |
| 13:29.18 | freemangordon | I guess it is merlin1991 who is supposed to do it, right? |
| 13:29.41 | *** join/#maemo cyphase (~cyphase@unaffiliated/cyphase) |
| 13:29.51 | Pali | yes |
| 13:30.58 | freemangordon | Pali: ok, if after issuing new -stable merlin1991 is not willing to edit that file, I will do it :) |
| 13:31.15 | freemangordon | but lets first make him issue a new -stable |
| 13:51.58 | *** join/#maemo M4rtinK (~M4rtinK@ip-78-45-144-165.net.upcbroadband.cz) |
| 14:01.03 | *** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian) |
| 14:46.58 | *** join/#maemo mp107 (~mp107@PC-109-125-232-42.wegrow.domtel.com.pl) |
| 14:51.49 | *** join/#maemo Vajb (~Vajb@85-76-18-133-nat.elisa-mobile.fi) |
| 14:58.05 | *** join/#maemo MetalGearSolid (~MetalGear@unaffiliated/metalgearsolid) |
| 15:53.08 | sixwheeledbeast | I thought supl server issues where fixed? It was a cert IIRC not an issue with supl.nokia.com. Is your system time correct? |
| 16:55.58 | freemangordon | sixwheeledbeast: at least here it works fine. And yes, there were certificate issues fixed in CSSU |
| 16:59.24 | sixwheeledbeast | :nod: Sicelo? |
| 17:06.29 | *** join/#maemo geaaru (~geaaru@host67-212-dynamic.5-87-r.retail.telecomitalia.it) |
| 17:10.58 | *** join/#maemo eMHa_ (~mh@p200300738E56D200267703FFFE6CC360.dip0.t-ipconnect.de) |
| 17:12.37 | *** join/#maemo shentey (~shentey@p4FF0E6E4.dip0.t-ipconnect.de) |
| 17:15.40 | *** join/#maemo kerio (kerio@bad.memes.vs.dank.ninja) |
| 17:16.07 | *** join/#maemo deepy (deepy@wrongplanet/deepa) |
| 17:24.37 | *** join/#maemo eMHa__ (~mh@p200300738E56D200267703FFFE6CC360.dip0.t-ipconnect.de) |
| 17:55.00 | Vajb | supl.nokia.com working here also |
| 17:56.01 | *** join/#maemo eMHa__ (~mh@p54B0F308.dip0.t-ipconnect.de) |
| 18:21.02 | DocScrutinizer05 | <text>Includes latest fixes for Maemo 5 system by Maemo Community - $VERSION $(date +%Y-%m-%d)</text> |
| 18:25.21 | Sicelo | sixwheeledbeast: yes, all is well with my time and cert (i'm on cssu-thumb) |
| 18:41.30 | Sicelo | both location-test-gui and ovi maps seem to make a request to h-slp.mnc002.mcc655.pub.3gppnetwork.org .. which doesn't resolve |
| 18:41.42 | Sicelo | no idea where it gets that from |
| 18:43.00 | Sicelo | 655-02 would be my network operator of course, but i don't know how N900 gets to know about this hostname |
| 18:43.22 | KotCzarny | you've got a virus |
| 18:44.48 | Sicelo | :p |
| 18:44.56 | Sicelo | stop being dramatic :) |
| 18:51.22 | DocScrutinizer05 | sounds like ~gsm-agps |
| 18:53.19 | DocScrutinizer05 | aka RRLP |
| 18:54.26 | Sicelo | yes that's what i think .. but i'm specifying AGNSS in location-test-gui |
| 18:55.00 | Sicelo | log of an A-GPS session: https://talk.maemo.org/showpost.php?p=1522819&postcount=228 |
| 18:57.35 | Sicelo | wow .. my 2nd N900 got A-GPS fix in just 3s |
| 18:58.11 | Sicelo | never contacted anything else besides supl.nokia.com |
| 19:04.57 | LjL | that still works? |
| 19:07.28 | Sicelo | yes, always worked |
| 19:08.07 | freemangordon | Sicelo: that should get resolved by your MNO afaik. do you have SIm card in that device? |
| 19:08.40 | Sicelo | yes, i do |
| 19:08.44 | Sicelo | KotCzarny: https://forum.xda-developers.com/showpost.php?p=9533067&postcount=10 |
| 19:09.32 | DocScrutinizer05 | yes, 3s is RRLP, standard on 3G nowadays |
| 19:10.05 | DocScrutinizer05 | ~gsm-agps |
| 19:10.05 | infobot | rumour has it, rrlp is the Radio Resource LCS (Location Service) Protocol as specified first in GSM TS 04.31, or http://security.osmocom.org/trac/wiki/RRLP |
| 19:11.03 | Sicelo | DocScrutinizer05: my main N900 is the one coming up with this address, and no fix. the 2nd N900 is the one with quicker fix, and no attempt to contact this address. 2nd N900 has different operator's SIM though |
| 19:11.03 | DocScrutinizer05 | since GPS is integral component of BB5 modem, it's totally opaque to userland *how* the fix got established |
| 19:11.36 | DocScrutinizer05 | Sicelo: do I realy need to suggest the onvious? ;-) |
| 19:11.44 | DocScrutinizer05 | obvious* |
| 19:11.53 | DocScrutinizer05 | swap SIMs |
| 19:12.29 | DocScrutinizer05 | use airplane mode. (though now you got ephem/alm in cache, so it's pointless anyway) |
| 19:12.36 | Sicelo | i'm going to do that of course |
| 19:13.48 | DocScrutinizer05 | I did similar tests a maybe 6 years ago, and it turned out: 3G *and* correct system time allow a TTFF<5s |
| 19:30.33 | Sicelo | tested 3 SIM cards now .. the 1st N900 always considers the 3gppnetwork.org address, of course with the corresponding MCC/MNC in the hostname. no fix |
| 19:42.58 | Sicelo | 2nd N900 .. with any of the SIM cards .. quick fix. no 3gpp address looked up at all |
| 19:43.34 | Sicelo | i'll reinstall location-proxy on 1st N900 .. no idea if it will help |
| 19:48.52 | Sicelo | i'll add that 2nd N900 has not been used for GPS in a very long time .. so has the least 'knowledge' about my location compared to 1st |
| 19:59.59 | *** join/#maemo dafox (~dafox@ip3e8380c8.speed.planet.nl) |
| 20:03.19 | *** join/#maemo DrGrov (~deathstar@unaffiliated/drgrov) |
| 20:03.34 | DocScrutinizer05 | you know http://repository.maemo.org/pool/maemo5.0/non-free/l/location-test-gui/ I'm sure |
| 20:05.05 | DrGrov | DocScrutinizer05: Hi Doc, are you active on the 05 or 51 nickname? |
| 20:05.39 | DocScrutinizer05 | none, I'm inactive on IRC, and my flu is active on me |
| 20:06.08 | DrGrov | DocScrutinizer05: Oh, that is a shame. Did you read my quickly sent direct message? |
| 20:06.27 | DrGrov | DocScrutinizer05: I hope that you'll get rid of that nasty flu |
| 20:06.46 | DrGrov | I will send you a quick question if you do not mind? |
| 20:06.55 | DocScrutinizer05 | go ahead |
| 20:07.50 | Sicelo | DocScrutinizer05: 20:55 < Sicelo> yes that's what i think .. but i'm specifying AGNSS in | location-test-gui |
| 20:15.35 | *** join/#maemo Roth (~quassel@73.114.35.109) |
| 20:17.24 | *** join/#maemo Roth_ (~quassel@73.114.35.109) |
| 20:21.11 | *** part/#maemo DrGrov (~deathstar@unaffiliated/drgrov) |
| 20:22.50 | *** join/#maemo Roth (~quassel@73.114.35.109) |
| 20:30.51 | DocScrutinizer05 | idly muses how much a N900 would cost and weigh when built with technology of 1980 |
| 20:31.42 | *** part/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net) |
| 20:33.45 | DocScrutinizer05 | in 1980 |
| 20:34.24 | DocScrutinizer05 | prolly needs two dozen Z80, a 50 to 100 bucks each? just to start with |
| 20:41.40 | warfare | Or a few m68ks |
| 20:42.06 | KotCzarny | or a bunch of sticks and stones |
| 20:59.37 | *** join/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net) |
| 21:10.10 | *** join/#maemo M4rtinK (~M4rtinK@ip-78-45-144-165.net.upcbroadband.cz) |
| 21:13.07 | *** join/#maemo shentey (~shentey@p4FF0FF20.dip0.t-ipconnect.de) |
| 21:19.21 | kerio | but the n900 is basically 80s technology ð¤ |
| 21:20.16 | buZz | <3 n900 |
| 21:27.10 | Juesto | lol 80s |
| 21:46.31 | ravelo | hehe |
| 21:50.12 | LjL | 70s technology at best |
| 21:50.17 | LjL | i'm sure i've spotted some valves in it |
| 21:51.20 | *** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 21:56.09 | Juesto | ;o |
| 22:42.39 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 23:08.58 | Sicelo | freemangordon, DocScrutinizer05 ... 'solved' the problem with AGPS - *maemosec* packages from devel have problem of some sort. will report on devel thread |
| 23:12.36 | freemangordon | hmm |
| 23:12.47 | freemangordon | some certificate problem again I guess |
| 23:13.42 | Sicelo | possibly, but 2nd N900 using CSSU-T (no devel) worked perfectly the whole time. no idea what's up with the devel ones |
| 23:14.45 | freemangordon | Sicelo: https://github.com/community-ssu/maemo-security-certman/commits/master |
| 23:15.02 | freemangordon | we should wait fo jonwil to appear |
| 23:15.19 | freemangordon | but yeah, report the problem on cssu-devel thread |
| 23:15.58 | Sicelo | i've done, https://talk.maemo.org/showpost.php?p=1522850&postcount=510 :-) |
| 23:19.21 | freemangordon | Sicelo: could you try to connect with openssl instead of cmcli? |
| 23:20.24 | freemangordon | ah, you already did it |
| 23:20.27 | Sicelo | i did both |
| 23:20.29 | Sicelo | yeah |
| 23:21.12 | Sicelo | weird thing is .. exactly the same output for both devices for cmcli and openssl |
| 23:21.29 | freemangordon | mhm |
| 23:21.57 | freemangordon | I wonder why cmcli gives self-signed error |
| 23:24.16 | freemangordon | Sicelo: are you sure you did cmcli on both devices? |
| 23:24.26 | freemangordon | as it does not fail on mine |
| 23:24.52 | freemangordon | "Verified OK" |
| 23:24.58 | freemangordon | for the same command as yours |
| 23:25.11 | Sicelo | yes, yes |
| 23:25.40 | Sicelo | but now that i've downgraded maemosec-certman-tools one the one to 0.2.3, it verifies ok |
| 23:26.11 | freemangordon | Sicelo: what is the version on your second device? |
| 23:26.22 | Sicelo | the 2nd N900 (which has had consisted quick fixes), has 0.2.4 .. didn't downgraded, and that ones still 'sees' self-signed |
| 23:26.30 | freemangordon | weird |
| 23:26.55 | Sicelo | 0.2.4 doesn't seem to be in any repo now though :-/ |
| 23:27.05 | Sicelo | what version do you have? |
| 23:27.24 | freemangordon | 0.2.3 |
| 23:34.17 | freemangordon | Sicelo: what is the output from dpkg -L maemosec-certman-common-ca | grep 00d85a4c25c122e58b31ef6dbaf3cc5f29f10d61 |
| 23:34.27 | freemangordon | on that device with 0.2.4 |
| 23:37.31 | Sicelo | /etc/certs/common-ca/00d85a4c25c122e58b31ef6dbaf3cc5f29f10d61-1.pem |
| 23:37.31 | Sicelo | /etc/certs/common-ca/00d85a4c25c122e58b31ef6dbaf3cc5f29f10d61.pem |
| 23:37.43 | Sicelo | problem is the duplicate? |
| 23:37.57 | freemangordon | no, most probably it is in the order |
| 23:38.18 | Sicelo | yes .. by the way the 0.2.4 device is 'fine' :) |
| 23:38.37 | freemangordon | what do you mean? |
| 23:38.50 | freemangordon | if cmcli fails to verify, it is not fine |
| 23:39.09 | freemangordon | see https://github.com/community-ssu/maemo-security-certman/commit/2cbd96e89d7529e1ce25801824fb76f39b05b836 |
| 23:39.14 | Sicelo | ah yes .. meant from the POV of A-GPS |
| 23:39.18 | freemangordon | I suspect same/similar problem |
| 23:39.45 | Sicelo | i remember those fixes back then |
| 23:39.45 | freemangordon | Sicelo: but then, why cmcli fails? |
| 23:40.25 | Sicelo | i really have no idea about that |
| 23:40.39 | Sicelo | maybe jonwil will have idea, but |
| 23:41.21 | Sicelo | not sure if this is related .. https://talk.maemo.org/showthread.php?t=96433 .. seems to be the only place 0.2.4 is mentioned |
| 23:41.56 | freemangordon | yep, lets wait for him to appear. If not, tomorrow I'll install the latest from -devel and will check |
| 23:42.07 | Sicelo | the thread seems to have ended without anything specific |
| 23:42.24 | freemangordon | goes afk |
| 23:42.27 | freemangordon | night |
| 23:42.28 | Sicelo | sure .. at least you'll probably be able to understand it better than I |
| 23:42.33 | Sicelo | night |
| 23:50.19 | *** join/#maemo NeKit (~nekit@85-95-187-85.saransk.ru) |