IRC log for #maemo-ssu on 20130125

00:08.02*** join/#maemo-ssu jonwil (~jonwil@27-33-137-199.static.tpgi.com.au)
00:16.50*** join/#maemo-ssu jaded (~jade@Jade.broker.freenet6.net)
00:16.50*** join/#maemo-ssu jaded (~jade@unaffiliated/jade)
00:37.15*** join/#maemo-ssu jade (~jade@unaffiliated/jade)
00:48.00*** join/#maemo-ssu jaded (~jade@2001:5c0:1000:b::b41b)
00:48.00*** join/#maemo-ssu jaded (~jade@unaffiliated/jade)
00:55.55*** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu)
00:59.09*** join/#maemo-ssu jade (~jade@2001:5c0:1000:b::b41b)
00:59.09*** join/#maemo-ssu jade (~jade@unaffiliated/jade)
01:00.45*** join/#maemo-ssu kolp (~quassel@212.255.234.217)
02:01.23*** join/#maemo-ssu Mihanizat0r (~Miranda@83.149.35.45)
02:51.11*** join/#maemo-ssu ShadowX (~l4m3rx@darknet.escom.bg)
03:25.53*** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn)
04:03.34*** join/#maemo-ssu DocScrutinizer06 (~HaleBopp@openmoko/engineers/joerg)
06:41.46*** join/#maemo-ssu LaoLang_cool (~LaoLang_c@120.85.133.181)
07:44.50*** join/#maemo-ssu ivgalvez (~ivgalvez@89.140.113.138.static.user.ono.com)
07:51.37*** join/#maemo-ssu futpib (~futpib@89.106.197.109)
08:29.30freemangordonaapo: zeq faced that locales problem when he was trying to build glibc(stock) with gcc 4.7.2. So I guess it is some kind of a toolchain problem
08:39.02*** join/#maemo-ssu xes (~xes@host22-224-dynamic.5-87-r.retail.telecomitalia.it)
08:39.02*** join/#maemo-ssu xes (~xes@unaffiliated/xes)
08:45.51freemangordonaapo: I guess some additional flag passed to the compiler is neede
08:45.54freemangordond
08:53.23*** join/#maemo-ssu jade (~jade@Jade.broker.freenet6.net)
08:53.23*** join/#maemo-ssu jade (~jade@unaffiliated/jade)
08:54.24freemangordon~mirrors
08:54.24infobotwell, mirror is http://maemo-archive.wedrop.it/ http://maemo.merlin1991.at/apt-mirror/   http://talk.maemo.org/showthread.php?p=1315143#post1315143
09:07.41*** join/#maemo-ssu lartza_ (~lartza@IP-62-216-127-116.telemail.fi)
09:22.22*** join/#maemo-ssu lartza_ (~lartza@IP-62-216-127-116.telemail.fi)
09:28.40*** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu)
10:03.56*** join/#maemo-ssu Martix_ (~martix@ip-62-245-106-78.net.upcbroadband.cz)
10:21.34*** join/#maemo-ssu Estel_ (~Estel@d56-215.icpnet.pl)
10:21.34*** join/#maemo-ssu Estel_ (~Estel@Maemo/community/contributor/Estel-)
10:29.19*** join/#maemo-ssu lizardo (lizardo@nat/indt/x-mzvspclfindfdogz)
10:34.34*** join/#maemo-ssu BCMM (~BCMM@unaffiliated/bcmm)
10:58.08*** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali)
11:03.04kerioPali: fix your battery applet
11:03.11kerioit's not normal that i'm getting 110% capacity
11:03.18kerioi have to rmmod rx51_battery
11:03.43Palikerio, are you using bme replacement and/or my battery applet
11:03.47kerioyep
11:03.48kerioto both
11:03.53kerioand i just changed battery
11:03.57Paliok, then you need to run my debug version
11:04.00PaliI need logs
11:04.00keriothis one is ~1400
11:04.09kerioPali: it's a problem of rx51_battery
11:04.20kerioor, rather, it's a problem of your battery applet not displaying the data from bq27200
11:04.20PaliI think that I fixed all > 100% bugs
11:05.53Palihttp://atrey.karlin.mff.cuni.cz/~pali/hald-addon-bme
11:06.25keriohm, i'll have to reboot for that, right?
11:06.35kerioor somehow restart hal without rebooting, but i doubt it's possible
11:06.36Palihttp://atrey.karlin.mff.cuni.cz/~pali/status-area-applet-battery.so
11:06.42Paliupdate both and reboot
11:06.50Palithen log from hal is in /tmp/
11:06.54Paliand from widget in syslog
11:06.56kerioPali: i'll finish this calibration first, though
11:07.01Paliok
11:07.18keriothis battery is surprisingly good
11:07.40kerioit's not the 1700mAh advertised, and not the 1600mAh that vi_ said that his battery had
11:07.47keriobut it's still 1420
11:08.06kerioso ~150 more than the original bl-5j
11:09.17kerioPali: does your bq24k module have a way to charge a bit more aggressively?
11:09.49Paliyou can do anything with bq2415x_charger
11:10.03Paliyou have exported all settings via sysfs
11:10.15Palialso you have access to bq registers
11:10.19keriowho decides how much to charge for each voltage?
11:10.37PaliI do not remember sysfs entires, look at datasheet
11:10.43kerioi see
11:11.00keriobtw, i almost never get to see the solid green led
11:11.14kerioand i realize that bme's "charge finished" is a lie, but it was a comforting lie
11:12.01Paliso wait
11:12.16Palior change termination current sense to 100 or 150
11:12.37kerioit's already at 150
11:22.57Palichange it to 100
11:23.16PaliI think I changed it to 100 in last kp52 build
11:25.18*** join/#maemo-ssu Akuma (c064782a@gateway/web/freenode/ip.192.100.120.42)
11:28.19kerio:O
11:28.25keriothere's a new kp52 build and you don't tell me
11:28.30kerioyou monster
11:32.53*** join/#maemo-ssu arcean (~arcean@aaep122.neoplus.adsl.tpnet.pl)
11:34.56Akumahello all. :)
11:35.02kerio'lo
11:35.50Akumai'm on n900 ssu repo/gpg key business regarding expired keys. :)
11:35.54kerioPali, freemangordon: would kernel-power compile with gcc4.7-linaro?
11:36.10Palino idea
11:36.53kerioAkuma: ohai
11:36.59keriowe were kinda waiting for you
11:37.07kerioDocScrutinizer06: *poke*
11:37.35Akumakerio: thank you for your patience. :)
11:37.50Akumahopefully finnish timezone didn't mess my arrival time up. :)
11:38.10kerioAkuma: we did some tests, HAM will only accept system updates from a repository that uses a valid key in a certain list
11:38.25freemangordonkerio: probably it will, with some tweaks
11:38.35Akumame i'm trying to locate the "MaemoSW Admin" key. it's not in the key ring we use for SSU business.
11:38.35kerioand for the key to be considered valid, it has to be not expired, and stored in the apt-secure keychain
11:38.47keriooh, you already know, sorry
11:39.16Akumawe got a verbose mail from pali (thank you), which shed light on the "fifth key" thing
11:39.43kerioAkuma: it's something related to maemo.research.nokia.com (whatever that is), according to the description of the maemointernal-keyring package
11:40.22kerio(the package that installs that key)
11:40.38Akumamm-hmm. that's our frontend server allright.
11:40.42Akumalooking around it a bit.
11:41.19Akuma(it probably just reroutes traffic somewhere else)
11:41.22kerioperhaps it's the key used to sign some testing or old repos
11:43.59Akumayeah. we haven't done fremantle stuff at all during our time, just harmattan. if it was up to me, i'd just hand over the relevant packages to the community. :)
11:44.17PaliAkuma, hi, do you know if you can release new pr1.3.2 firmware if maemosw admin key could not be found?
11:44.29kerioPali: as a flashable image? ugh :s
11:44.37Palivia pc-suite updater
11:44.44keriodouble ugh :s :s
11:44.49freemangordonPali: iirc pc-suite is windows-only
11:45.05Paliyes, but this is official way for updating images
11:45.13Paliwe can of course flash image via maemo flasher
11:45.46kerioby the way, what happened to tablets-dev?
11:46.00Akumapali: that is highly improbable due to the fact that it's now maintenance mode over here and most of the original crew is no longer around.
11:46.09freemangordonPali: "we" can, but that won't work for an "ordinary" user. Esp if he is a non-windows user
11:47.02keriofreemangordon: the only problem would be with the osx non-"power" users
11:47.09keriobut those have iphones anyway :P
11:47.12freemangordonhehe
11:48.18PaliAkuma, how long will be downloads.maemo.nokia.com working?
11:49.02Akumapali: my estimate is that at least as long as harmattan maintenance is around
11:49.13Palitablets-dev.nokia.com where was all flashable firmwares and flasher tool is not down
11:49.18Pali*now
11:49.25Akumaas they're pretty intertwined.
11:50.39freemangordonAkuma: so, now your focus is to find the private "Maemo SW Admin" key?
11:50.50Akuma@pali: so at least an year, hopefully two.
11:51.50Akuma@freemangordon: yeah. however, that particular key is not where our signing keys usually reside. maemo.research.nokia.com is just a little frontend can that forwards traffic inside the system.
11:52.47freemangordonAkuma: I see.
11:53.10PaliAkuma, ok. but what happen then? It is possible to move ssu repositories to community servers (when nokia ssu will be down)?
11:53.21kerioprobably legal stuff then
11:53.29freemangordon:nod:
11:53.35Akumathere is this so called "ssu" server which has four gpg keys, the "The Nokia repository signing key <1-4>v1".
11:53.55freemangordonwith all of them expired :)
11:53.59kerioand of course if we lose the control of the "downloads.maemo.nokia.com" domain, we won't have a working OTA update for vanilla devices
11:54.14Palithere are also public nokia keys "<1-4>v2" which expired too
11:54.28Akumafreemangordon: we have extended the expiry of the first key, but we fear that uploading it to repos will break the trust chain in Akamai and nobody gets anything d/l'd after that. :)
11:54.36Akumaso we can't do that until we're sure that wont happen
11:55.10Akuma@pali: I'd say a public petition to Nokia would be the best way to accomplish that. Other than that, I have no idea where fremantle code will end up. I have N900 myself, and I sure hope community could take over it's maintenance.
11:56.04keriowell, we already kinda have :)
11:56.15Akumapali: it's odd, but we can't see those "v2" keys over here.
11:56.22Akumaso there must be another gpg cache somewhere around here.
11:56.41Paliv2 keys are exipired too, so are useless too
11:57.13kerioAkuma: does nokia keep backups?
11:57.30Akumakerio: of course. it's a legitimacy thing.
11:57.58PaliAkuma, I wrote in mail that extending key on server (+ upload it to public gpg keyserver) is not enught. It is needed to update that key also to each n900 device. And I really do not have idea how to do that (without releasing new FW)... So belive that maemosw admin key will be found
11:58.21keriowell, there's a kludgy, kludgy way to do that
11:58.31Akumapali: yeah, we've gone through a lot of options here, and we pretty much agree with what you said
11:58.41jonwilI just wish the "maemo license change requests" (on bugs.maemo.org) had actually lead to some code being opened up but it never did :(
11:58.59freemangordonPali: if swadmin key cannot be found, n900 users are more or less screwed
11:59.01kerioAkuma: n900-fmtx-enabler is in extras, and preinstalled in quite a number of n900s
11:59.23kerionot all of them though, i think that it's missing in... uk and japan?
11:59.28keriofmrx, sorry
11:59.33freemangordonkerio: but it have to be pushed via extras, not by nokia server
11:59.48kerioyeah, yeah
11:59.49Akumai just probably have to go through most of the servers looking for any clues for gpg keyrings.
11:59.50freemangordonAnd I still have doubts this will work
11:59.55kerioand it's also a massive kludge :)
12:00.38Akumathat admin key would probably help a lot, if we can find it. we have like ~100 servers here.
12:00.49freemangordonAkuma: OMG :)
12:01.14keriofor serv in `cat servlist`; do ssh $serv find / -iname *.gpg ; done
12:01.17kerioeasy
12:01.23freemangordonhehe
12:01.29Akumayeah, and i could drive that through clusterssh or something.
12:01.34freemangordonkerio: what about the access?
12:01.35Akumanice idea. :)
12:01.37kerioand in only a couple of years, we'll find our key
12:01.50kerioooh, even better solution
12:01.56keriouse those 100 servers to bruteforce the secret key
12:02.04kerio100 is a lot!
12:02.09Akumaha ha. :)
12:02.19Akumai'll get some coffee and start from the first server.
12:03.16freemangordonAkuma: any chance to contact someone from the ex-crew? I know they don't have reasons to be polite and helpful, but still
12:05.25Akuma@freemangordon: most if not all of them are working in Jolla (sailfish) nowadays. i doubt they will want to assist us. :(
12:05.35keriobut it's for the n900!
12:05.45freemangordonkerio: even worse ;)
12:05.56kerionobody who ever used a n900 dislikes it
12:06.04freemangordonkerio: you are the past, don;t you get it?
12:06.11freemangordon:P
12:06.47kerio~kerio
12:06.47infobothmm... kerio is <DocScrutinizer05> kerio is right
12:07.09kerioinfobot: no, kerio is <DocScrutinizer05> kerio is right  <freemangordon> kerio: you are the past
12:07.09infobotcannot alter locked factoids, kerio
12:07.16keriooh ffs, i locked it
12:07.22freemangordonchange that to "kerio is the past"
12:07.30kerionope
12:07.40kerioanyway, noise
12:07.45freemangordonyep
12:07.56*** join/#maemo-ssu kolp (~quassel@212.255.237.18)
12:10.14jonwilOne of these days I will buy (or otherwise obtain) that copy of ARM Hex-Rays I need then I can REALLY bust this phone wide open... :)
12:11.06freemangordonhehe, count me in :P
12:12.04jonwilOnly problem is that I dont have a couple thousand spare to buy it :)
12:12.47freemangordonjonwil: and unfortunately russian hackers are slow this time :D:D:D
12:12.47kerioask them nicely :3
12:13.14freemangordonkerio: won't work :(
12:13.20keriois the arm version a particular one?
12:13.23keriobecause hex-rays can be... found
12:13.29freemangordononly x86
12:13.59freemangordonat least I am not aware of ARM hexrays being available on PB
12:15.13freemangordonjonwil: do you have any idea why locales don;t work when glibc is compiled with gcc 4.7.2?
12:15.20jonwilThat I dont know
12:15.28jonwilI know nothing about glibc or locales
12:15.35freemangordonI see :)
12:15.46jonwilYou could always pull out GDB and debug it :P
12:15.59kerioholy shit, there's a 105.49GB bounty for hex-rays arm on w.cd
12:16.15freemangordonand for some reason dgb symbols give me:0x40054360 in dcgettext () from /lib/libc.so.6
12:16.17freemangordon0x40054360 <dcgettext+28>:      add     sp, sp, #12     ; 0xc
12:16.20freemangordon(gdb)
12:16.22kerioit's fair to assume that it's not on the internet
12:16.22freemangordonSingle stepping until exit from function dcgettext,
12:16.24freemangordonwhich has no line number information.
12:16.59freemangordonkerio: yep, wanted dead or alive :)
12:17.55kerioare you the one that put that request in? :o
12:18.04freemangordonno
12:22.30Akumajonwil: btw, one of the biggest problems for nokia in releasing it's fremantle code in the open relates mostly to brand name.
12:23.02kerioreally wants to say "it's ok, it's already gone down the shitter" but decides against doing so
12:23.05keriooh crap
12:23.16Akumaif community would do the maintenance, i guess it would look too much that's it's actually nokia doing it
12:23.32Akumaso a smart way would have to be thought up to circumvent that in order to make it happen
12:23.43kerioAkuma: well, every update is clearly marked "Community SSU"
12:23.53jonwilyeah CSSU is exactly that
12:24.04jonwilIts 100% clear that anything is community and not Nokia
12:24.31Akumayeah, i agree and to me and my colleagues it would be clear - but from that point it's still a long way in convincing the lead.
12:24.34freemangordonguys, I guess Akuma is aware of that. Not sure about the decision-makers :)
12:25.00Akumamaybe found a new brand name... like... jolla ;)
12:25.10freemangordonhehe
12:26.18jonwilWhats wrong with a press statement making it 100% clear that Nokia has nothing whatsoever to do with the N900 anymore and that the community has taken over maintanence of the device. And then direct any queries related to the N900, its software and its supporting servers to HiFo or whoever it is.
12:26.36jonwilOr maybe I have been watching too much "West Wing" to think that such tactics can work in the real world :P
12:27.37jonwiloh and wiki.maemo.org is down again :(
12:27.48freemangordonjonwil: AIUI The best we can do and hope is to somehow "sneak" some information to the n900 users that CSSU exists and to leave them decide
12:28.22jonwilI was talking about it in the context of "nokia is concerned that community updates look like nokia updates"
12:28.27freemangordonjonwil: look from Nokia's POV - who TF are freemangordon, Pali, merlin1991, jonwil, etc
12:28.42jonwili.e. Nokia can avoid that by saying in public that they are not Nokia updates and that Nokia has nothing to do with them or endorse them
12:28.46freemangordonwhy should they trust us?
12:28.46keriofreemangordon: hildon foundation is a NFP
12:29.16freemangordonkerio: FMG is in no way related to HiFo ;)
12:29.29freemangordonlegally speaking
12:30.06keriothat's why the inclusion of community-thumb and community-devel in the repos is wrong, imo
12:34.50jonwilI dont think we would get anywhere near the full codebase for the N900 even if there weren't these issues and Nokia was willing to open up more code. Too much of the code is encumbered in various ways (3rd party IP, regulatory concerns e.g. FCC etc, liability concerns)
12:35.31Akumai reckon that creating a small shoestring budget company with a new brand name to handle it would go a long way in convincing nokia lead, but it might still not be enough and nokia might still ask for an astronomical price for the whole sheebang as it's now stepped over to commercial side..
12:39.05*** join/#maemo-ssu phr3akDom (~phr3ak@ip-213-220-198-105.net.upcbroadband.cz)
12:39.19PaliAkuma, are you still trying to find lost gpg key?
12:40.42[Akuma]pali: good and bad news regarding that: good news is that i found the key. bad news is that it's a BIFH (our build and integration system) related key.
12:41.23Paliwhy it is bad?
12:42.25[Akuma]BIFH is a critical part our infrastructure and we are not aware to the full extent of what this key will permit.
12:44.59jonwilAssuming Nokia doesn't distribute the private half of this key and assuming the repositories that get signed with this key do not get changed form the current state other than the re-signing, I dont know of anything that this key would permit that wouldn't already be possible if the other SSU keys weren't expired.
12:45.07jonwilBut then again I dont work for Nokia :)
12:46.21kerio[Akuma]: you're going to *use* the key, not give it to us
12:46.22freemangordon[Akuma]: resigning the repo with it would permit nothing but a working repo AIUI
12:46.30freemangordon:nod:
12:46.37kerioi mean, the public key is in every device, anyway
12:46.46kerioreleasing a signature won't really help with bruteforcing it :)
12:47.04freemangordonkerio: the signature is on the devices too
12:47.23keriofreemangordon: i mean the signature of the Release file
12:47.29freemangordonaah, yes
12:47.46[Akuma]yeah, i agree.
12:47.59kerioof course you agree, you actually understand what's going on :)
12:48.07freemangordon:)
12:48.15keriowill /they/ agree?
12:48.19jonwilsuspects there are several layers of PHB-style management that actually have to approve this
12:48.36kerioit's literally a command to run on the downloads.maemo.nokia.com web server
12:48.38[Akuma]kerio: exactly. i could use a nice mail which describes the process in its entirety to the mail chain that's been going under the desk.
12:48.52freemangordons/approve/grok/
12:48.59freemangordonjonwil: fixed for you :P
12:50.09freemangordon[Akuma]: well, our biggest fear was that the private was lost :)
12:50.30keriofreemangordon: talk for yourself
12:50.39freemangordonok, mine biggest fear
12:50.45freemangordonkerio: better?
12:50.46jonwilin any case I would be willing to do everything in my power to aid any efforts in the area of code release (if it should happen at some point in the future) if it meant there was any possibility of being able to see (and modify/reuse/redistribute) the source code to the N900 connectivity UI widgets and network connectivity bits
12:50.52kerioi always stated "if nokia still has the private key and is willing to use it"
12:52.15jonwilBut as that will probably never happen, I am resigned to staring at ARM ASM all day hoping I can figure out one more function in a shared library or one more data structure or one more piece of code
12:52.54freemangordonkerio: i don't think there is any other feasible option but to use it. given the "maintaince mode" n900 is in. i.e. forget about new firmware or something
12:53.43[Akuma]yeah, maintenance mode means all devs and testers out, only a small fraction of IT remains behind
12:54.11[Akuma]to wrap it up, so to speak
12:55.10[Akuma]creating a new PR would mean a lot of work anyway - branching, somebody had to do new enablers for SSU testing, they would probably want bugfixes in, etc.
12:55.33jonwilI think all we need is to show Nokia Management that re-signing these files wont allow someone to do anything dangerous
12:56.23[Akuma]yup, if such a document / mail would be present, it would help
12:57.09jonwilI think kerio is probably the best person to write such a document
12:57.14keriowat
12:57.24jonwilnot me anyway
12:57.30kerionot me
12:57.35jonwilok
12:57.37jonwilwho then?
12:57.50kerio*then who?
12:58.02jonwilHiFo?
12:58.04freemangordon[Akuma]: speaking of PR.. How do you think, is it possible Nokia to release a small PR, with a package informing n900 users of CSSU existence?
12:58.18keriojonwil: http://en.wikipedia.org/wiki/Who_Stole_the_Cookie_from_the_Cookie_Jar%3F
12:58.21jonwilfreemangordon: Highly unlikely to happen
12:58.29freemangordonjonwil: I know, but still
12:58.49keriofreemangordon: hell, at this point we might as well ask for a straight move to cssu-stable
12:58.56freemangordonI guess asking on #maemo-ssu is still allowed :P
12:58.58freemangordonkerio: no
12:59.07*** join/#maemo-ssu kolp (~quassel@212.255.237.18)
12:59.07freemangordonit should be the user to make the choice
12:59.29keriothey'll still get a choice, to update or not
12:59.40jonwilAny move by Nokia to even admit CSSU exists is potentially brand-diluting (per what Akuma said before)
12:59.40[Akuma]freemangordon: imagine the option of making a new PR in a situation when you have "would it be just easier to throw the towel in the ring" for the whole product as an option in the other scale dish...
12:59.54freemangordon[Akuma]: I see
13:00.14[Akuma]but that's just my personal view.
13:00.18kerio[Akuma]: think of it as "we can drop the hot potato on those guys over *there*"
13:00.33jonwilI don't think we should be even thinking about going to Nokia mgmt with anything other than the repo signing at this point
13:00.35[Akuma]yeah, i'd sure like to see community taking it over.
13:00.39kerioexcept that it's more like a cold, dried-out potato
13:00.51freemangordonkerio: hot? well...
13:00.56freemangordonjonwil: for sure
13:01.02keriofreemangordon: there's still plan b to give users a notification of the existance of cssu :)
13:01.11freemangordonkerio: ORLY?
13:01.24freemangordon:P
13:01.28jonwilFYI I would much rather have more code access than any kind of official push for CSSU but thats me (as a programmer) speaking :)
13:01.32[Akuma]anyway, i think i have to go buy some stereo jacks from the electrics store before it closes up. i like this channel, i'll pop back here to idle on monday. :)
13:01.38kerioyay
13:01.43[Akuma]thank you guys, youve been of great help and source of advice.
13:01.53freemangordon[Akuma]: thank you too
13:01.59kerioin the mean time, please ask whoever it is that could give you the authorization to change the signing key
13:02.09kerioif you can figure out who to ask
13:02.25jonwilNow we just need to find out who from community can draw up mail to Nokia mgmt in support of getting repos fixed
13:02.25[Akuma]i sent mail to pali and guys to describe the master sw key promises & peril in more elaborate detail
13:02.31[Akuma]so as to alleviate fears
13:02.34keriohas no idea of how big corporations are organized
13:02.50keriojonwil: i'd say it should be someone speaking as an official representative of HiFo
13:03.00freemangordonkerio: you don;t want to know :)
13:03.02[Akuma]anyway, have a nice weekend all, catch you again monday.
13:03.10keriocya [Akuma], thanks for your help!
13:03.15freemangordonbb
13:03.33freemangordonkerio: as doc explained it is the council, not hifo
13:03.44keriook, someone speaking as an official representative of the maemo council
13:03.47jonwilwell I did a 6 month student internship for Motorola as part of my university degree (back when the original RAZR was considered "high-tech") so I have some idea of how these kinds of companies work
13:05.52jonwilI have also had experience in the past with trying to get a big company to share source code (in this case it was for a PC game title and not a phone and it was for limited private use by the community and not full open-sourcing) so I have a little understanding of the sorts of things big companies tend to want to do
13:06.07jonwiland what sorts of things they might be worried about when sharing code outside of their company
13:06.30jonwilThat said Nokia is probably different to both Motorola and Electronic Arts
13:06.36jonwiland would have different processes for all this :)
13:07.14jonwilbut if anyone knows of anything I can do that might in some small way help get more code released, I will do whatever it takes :P
13:07.25jonwilwill go back to staring at ARM ASM now
13:09.36jonwilor I would if http://wiki.maemo.org/Fremantle_closed_packages worked and I could use it to figure out which target to fiddle with next
13:10.07kerioanyway, akuma is imba
13:10.25kerioat least, in sf3 third strike
13:12.10merlin1991hm I don't get the reference
13:12.42keriohey, where were you?
13:13.00keriohttp://streetfighter.wikia.com/wiki/Akuma
13:13.15merlin1991metalab, then sleep since around 6 am :D
13:13.23kerioi keep reading that as methlab
13:13.45merlin1991I bet someone at some point will do or has done some meth in there :D
13:18.38Skry*cough*
13:33.28kerio...hold on, why are we trying to get the nokia repo back to working again?
13:33.33keriojust for pr1.3.1?
13:42.14*** join/#maemo-ssu phr3akDom (~phr3ak@ip-213-220-198-105.net.upcbroadband.cz)
13:49.21jonwilPlenty of reasons to get the Nokia repos to work again. For example if I am messing with a replacement for some package and I want to reinstall the original for some reason, I need a working repo to do that :)
13:51.48keriojonwil: apt-get won't complain
13:51.52kerioand neither will HAM, once we fix it
13:52.02kerioor if you disable the checks in redpill mode
14:05.41kerioPali: is the new kp52 build still in the same place?
14:05.59Paliyes
14:06.25Palimy on hdd is jan 18 17:49
14:07.31Palikerio, I have new sudo and rootsh packages
14:07.37Paliwhich using /bin/su -
14:07.48Palifor spawning root shell
14:08.03Paliif you want you can try to use them :-)
14:12.03keriotrying to overwrite `/opt/boot/zImage-2.6.28.10-power52', which is the diverted version of `/boot/zImage-2.6.28.10-power52'
14:12.04keriogoddammit
14:12.06keriowhat's wrong with that?
14:12.07keriostupid dpkg
14:12.22kerio/opt/boot has the correct permissions
14:14.14kerio...oh
14:14.18kerioyou removed the diversion
14:14.21kerioyou sneaky Pali you
14:14.25kerioer, i mean
14:14.30kerioyou put it in /opt/boot already
14:14.44Paliyes
14:14.47kerio<3
14:14.55keriobut what about multiboot users?
14:47.07kerioPali: anyway, /sys/class/power_supply/rx51-battery/charge_full_design is 1257719, /sys/class/power_supply/bq27200-0/charge_full is 1411399
14:47.10kerioone of them is lying
14:47.34freemangordonkerio: why so?
14:47.56freemangordonrx51 get that from the battery
14:48.59kerioso the battery was designed to hold 1257mAh, but instead holds 1411
14:49.01keriook
14:49.05kerioi'm cool with that
14:49.22keriowhat i'm not cool with, is the battery applet showing what the battery is designed to hold instead of what the battery holds
14:49.29freemangordonwell, at least it reports itself as 1260
14:49.36freemangordonkerio: that's better :)
14:50.13kerioa calibrated bq27k should trump any other source of information
14:50.30freemangordon:nod:
15:08.53*** join/#maemo-ssu MrPingu (~MrPingute@86.92.226.97)
15:18.30Palikerio, but bq27x calibration does not have to be done by one cycle
15:18.57kerioso?
15:19.00Paliby sone bq cycle it can change charge_full only by some %
15:19.20keriodo you think it's magically going to drop?
15:19.27Paliso if you change big battery with some with small desing capacity, one cycle is not enought
15:19.49Paliso then charge_full will not be correct after CI flag
15:20.04kerioi've already done two cycles
15:20.16kerioand charge_full went *up* with the last one
15:20.25Palibut I cannot read how many cycles you done in applet
15:21.01kerioso you just display a value that's wildly wrong?
15:28.34Palirx51_battery reports value which is not wrong as value from bq27x
15:29.05kerio/sys/class/power_supply/rx51-battery/charge_full_design is 1257719
15:29.10keriothat value is oh so very wrong
15:30.12Palikerio, run bq27200.sh script for full discharge and full charge
15:30.20Palito see if there are no big steps
15:30.35keriowhere does rx51 take the values from, anyway?
15:31.50Palifrom battery
15:32.11keriohow?
15:32.14Palirx51_battery show values which reporting your battery
15:32.26Palipins on your battery
15:32.31*** join/#maemo-ssu jonwil_ (~jonwil@27-33-137-199.static.tpgi.com.au)
15:32.50kerioyeah, that's really trustworthy
15:35.37Palikerio, if you have problems with > 100% send me logs
15:35.53Pali110% is really bug
15:37.18kerioanyway, it's no big deal, i just have to remember to unload rx51_battery on every boot
15:38.10Lava_CroftI personally don't get all the interesting in the battery of the n900
15:38.13Lava_Croftor it's readings
15:38.22Lava_Croftall the interest*
15:45.57ShadowJKI had batterylife anxiety because the stock meter was so random. Accurate readins and instant consumption readings make it easy to manage use to last a day
15:46.43ShadowJKDon't have to guess whether I can have streaming music the last 3 hours of work without running out of batt
15:51.56chem|stcan someone put light on him?! http://talk.maemo.org/showthread.php?p=1317736#post1317736 CSSU during migration
16:00.57kerioDocScrutinizer05: here?
16:01.14DocScrutinizer05no
16:07.04*** join/#maemo-ssu infobot (~infobot@rikers.org)
16:07.04*** topic/#maemo-ssu is Maemo Community Seamless Software Update "CSSU" channel, http://wiki.maemo.org/Community_SSU | Known bugs: http://j.mp/communityssu-bugs | Channel logs: http://mg.pov.lt/maemo-ssu-irclog/ | Sources: http://gitorious.org/community-ssu/ | Latest version: Testing(2013-01-07): 21.2011.38-1Tmaemo7.2; Stable(2013-01-10): 21.2011.38-1Smaemo6
16:07.04*** mode/#maemo-ssu [+v infobot] by ChanServ
16:36.28*** join/#maemo-ssu toxaris (~toxaris@s83-180-246-172.cust.tele2.se)
16:42.57*** join/#maemo-ssu NIN101 (~NIN@p5DD2954E.dip0.t-ipconnect.de)
16:43.11*** join/#maemo-ssu arcean_ (~arcean@aaep122.neoplus.adsl.tpnet.pl)
16:49.00*** join/#maemo-ssu arcean__ (~arcean@aaep122.neoplus.adsl.tpnet.pl)
16:55.22*** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali)
17:01.50*** join/#maemo-ssu arcean (~arcean@aaep122.neoplus.adsl.tpnet.pl)
17:10.59*** join/#maemo-ssu arcean (~arcean@aaep122.neoplus.adsl.tpnet.pl)
17:19.16kerioPali: do you think you could make fiasco-image-update-ask usable with the terminal too?
17:20.00Palisorry I hate ncurses
17:20.01kerio^C is caught by softupd, and then dpkg complains because the postinst script of $whatever exited with an error
17:20.07keriono, i meant something much simpler
17:20.19Palikerio, provide patch
17:20.25PaliI can look at it if is ok
17:20.32kerioi don't know what, though
17:20.38kerio^c to exit without flashing, maybe
17:20.48keriobut then there's no way to accept
17:21.19PaliWTF http://maemo.org/packages/ is down :-(
17:21.25PaliService Temporarily Unavailable
17:21.30PaliThe server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
17:36.36*** join/#maemo-ssu luf (~luf@ip-89-102-208-114.net.upcbroadband.cz)
17:59.27*** join/#maemo-ssu arcean (~arcean@aaep122.neoplus.adsl.tpnet.pl)
18:00.59*** join/#maemo-ssu Timmo_ (~mirggi@46.115.49.23)
18:09.11*** join/#maemo-ssu Timmo_ (~mirggi@46.115.49.23)
18:20.58*** join/#maemo-ssu arcean_ (~arcean@aafq116.neoplus.adsl.tpnet.pl)
18:53.34*** join/#maemo-ssu Estel_ (~Estel@d56-215.icpnet.pl)
18:53.34*** join/#maemo-ssu Estel_ (~Estel@Maemo/community/contributor/Estel-)
19:18.12*** join/#maemo-ssu WizardNumberNext (~marek@2001:470:1f08:178b:92e6:baff:fe50:bed4)
19:35.32*** join/#maemo-ssu futpib_ (~futpib@89.106.197.109)
19:49.47*** join/#maemo-ssu wumpwoast (~jcassidy@63.251.248.156)
20:25.16*** join/#maemo-ssu Estel_ (~Estel@d56-215.icpnet.pl)
20:25.16*** join/#maemo-ssu Estel_ (~Estel@Maemo/community/contributor/Estel-)
20:29.45*** join/#maemo-ssu jade (~jade@Jade.broker.freenet6.net)
20:29.45*** join/#maemo-ssu jade (~jade@unaffiliated/jade)
20:43.36Palimerlin1991, can you create sudo git repository on cssu?
20:43.47PaliI have patch which fix sudo gainroot
20:44.00Pali(gainroot script is part of sudo package)
20:47.11kerioPali: "fix" what? and how?
20:48.38Palikerio, look at gainroot script
20:48.46Palirun sudo gainroot
20:48.51Paliand then show your $HOME
20:48.59Palior something else
20:49.12Pali"sudo sh" is *bad* usage
20:49.25Pali"sudo su -" is better
20:49.31keriouser@kerio900:~$ sudo gainroot
20:49.32kerioEnable RD mode if you want to break your device
20:49.32Palior "sudo -i"
20:49.36kerioworks fine for me
20:49.48Palikerio, you do not have enabled R&D mode
20:50.18keriono i don't
20:50.20kerioit's intended
20:54.41*** join/#maemo-ssu brkn (~brkn@HSI-KBW-134-3-171-252.hsi14.kabel-badenwuerttemberg.de)
21:01.37*** join/#maemo-ssu warfare (~falk@kilbeggan.fourecks.de)
21:02.06keriowarfare: community-testing from repository.maemo.org doesn't work, at the moment
21:02.30keriowarfare: http://community-testing.merlin1991.at/community-testing-light.install
21:02.42kerioit'll install a better mirror, and it'll actually work properly with HAM
21:03.37warfareI've got http://maemo.merlin1991.at/apt-mirror/community/ and -testing enabled.
21:03.47keriohm
21:03.51kerioit's just HAM being stupid then
21:03.59kerio(disable the community repo, you won't need it)
21:04.42kerioput "red-pill-mode 1" "red-pill-mode-permanent 1" in ~/.osso/hildon-application-manager
21:05.22kerioit'll enable a SEEEEEEEEEEEEEEEECRET menu in HAM
21:06.14warfareSo I don't have to create the matrix repo everytime? ;)
21:06.30kerionope
21:06.36keriodoes it work on PR1.3? :o
21:06.39kerioi thought it was disabled
21:07.06kerioanyway, due to repo mismatch, you need to disable "ignore wrong domains" in there
21:07.10keriokeep it disabled, it's just a hassle
21:07.47kerioit's basically an extra verification for each package, HAM will refuse to upgrade a package from a "domain" with a certain "trust" value to a "domain" with a lower one
21:08.27kerioke-recv is in the nokia repos, trust 600, and you need to upgrade it to the cssu version, but it's not the correct repo so it has trust 0
21:09.41warfareso HAM is way more than plain apt/aptitude.
21:10.24kerioyeah, it's a lot more
21:10.27keriomore annoying, more slow
21:12.21*** part/#maemo-ssu brkn (~brkn@HSI-KBW-134-3-171-252.hsi14.kabel-badenwuerttemberg.de)
21:15.28keriothe only good thing that it does is that if you're updating a system package, it'll put the phone in some sort of lockdown and reboot afterwards
21:25.01keriowarfare: is it going? is it gone?
21:25.11keriodid your phone blow up? i heard it happens, sometimes
21:26.59warfareStill full cpu load with HAM.
21:28.50keriooh right, more cpu usage
21:30.52keriowarfare: do you have extras-devel enabled? it brings HAM to a full 12 *minutes* of wall clock time halt on every catalogue refresh
21:32.57warfarekerio: no.
21:33.36warfareapt-worker is doing something.
21:33.57kerioyeah, apt-worker is what HAM actually uses to do stuff as root
21:36.11*** join/#maemo-ssu _rd (~rd@p57B492D1.dip0.t-ipconnect.de)
21:36.25warfareoh, I have. Now trying to disable it.
21:40.19kerioheh
21:40.36warfaretry, try, try, try again ;)
21:40.40kerioeventually, i advise you to not use HAM except when doing system updates
21:41.01warfareI was using FAM most of the time.
21:41.55kerioalso
21:41.58kerio~fapman
21:41.58infobotrumour has it, fapman is Faster Application Manager, a bad package manager that causes problems, don't use it, ever
21:42.18kerioit keeps its own apt lists, for crying out loud
21:42.27kerioit's against any guideline on apt interfaces
21:42.33warfareoO
21:43.03warfareSo just plain apt then?
21:45.15keriosure, why not
21:45.29kerioi'm going to assume that you can operate a terminal ;)
21:45.38warfare;)
21:47.39*** join/#maemo-ssu Estel_ (~Estel@d56-215.icpnet.pl)
21:47.39*** join/#maemo-ssu Estel_ (~Estel@Maemo/community/contributor/Estel-)
21:49.27*** join/#maemo-ssu arcean_ (~arcean@aafq116.neoplus.adsl.tpnet.pl)
21:50.50warfareStill missing packages: upstart, system-services, status-menu-applet-profiles, osso-systemui-powerkeymenu... (most with a cssu in the version number)
21:54.16keriohm
21:54.21keriowhich repositories have you enabled?
21:54.42kerioalso, is the "system upgrade" version 21.2011.38-1Tmaemo7.2+thumb0 ?
21:55.07keriowarfare: are you sure you *disabled* "ignore packages from wrong domains"?
21:55.20kerioyou don't want to ignore them, they're good
21:55.53warfarekerio: Yes. but "osso-systemui-powerkeymenu" is nowhere in the community "free/binary-armel/Package" files.
21:56.10warfares/community/&-cssu/
21:56.14keriowarfare: you need to disable community and enable merlin1991's community-testing
21:56.29keriocssu-thumb is built on top of cssu-testing
21:57.01warfareSo, disable community & community-testing?
21:57.24warfareBut yes, the version matches.
21:59.01keriorepository.maemo.org is offline at the moment
21:59.23keriocssu-thumb is on merlin1991's server, and so is that awesome mirror that supports pdiffs and only has the latest versions of each package
21:59.31keriothere's a light mirror of extras-devel too
21:59.42kerioit turns 9MB updates into handful-of-kB ones
21:59.57warfareI installed cssu-testing from merlin1991's server.
22:01.29kerioand you're sure that you disabled the domain check in HAM's settings?
22:01.38warfareOk, now I only enabled cssu-thumb and extras.
22:01.44keriono, you need cssu-testing too
22:01.48kerioi swear
22:01.57kerio(and you don't need extras)
22:02.11kerio(so perhaps you could disable it so that HAM is a bit faster because it won't have to wait for the RMO timeout)
22:02.37warfareI already disabled all rmo repos and added the mirrors.
22:02.50keriok
22:03.02keriohm, there's a Log in HAM
22:03.04kerioin the menu
22:03.11keriocan you pastebin it?
22:05.24*** join/#maemo-ssu toxaris (~toxaris@s83-180-246-172.cust.tele2.se)
22:06.12warfarejust a moment.
22:11.28warfarehttp://pastebin.com/esGDmJej
22:12.02warfareI changed cssu-testing repos (from merlin1991's mirror to skeiron.org) and now I'm only missing libidn11
22:14.04keriowarfare: instead of that repo, use http://community-testing.merlin1991.at/ fremantle free non-free
22:18.59warfare.oO( every non-hacker person would have thrown the device out of the window by now ;)
22:19.24kerionon-hackers won't buy a n900
22:19.31RaimuPretty much that.
22:19.32warfareAlso that.
22:19.38kerionon-hackers won't install cssu-thumb now
22:19.39keriothey'll wait
22:19.46kerionon-hackers won't install cssu-thumb
22:20.37kerionon-hackers should READ THE fine MANUAL
22:21.17warfareThats what hackers read after they broke something. At least I do.
22:21.21RaimuAlthough to be honest I consider myself less a hacker and more an enlightened power user.
22:22.31warfareYou were willing to spend $$$ on a phone with a complete unix environment. Thats no longer power user ;)
22:23.55chem|stwarfare: people pay $$$ for iphones... they arent even worth the word user
22:25.10kerioi spent $$$ on it
22:25.16kerioand then it broke
22:25.20kerioand then i spent $ for another one
22:25.26warfare;)
22:25.31kerio(and yes, that's in scale)
22:27.12warfarechem|st: depends, I like my iPhone in so far as it just works (most of the time) and I can live with the limitations. Same goes for my MacBook. But most other devices here are running linux (including the htpc and the dvr in the basement)
22:28.57chem|stwarfare: I cannot live with it so everything is running *x system... my coffeemachine my TV my desktop my tablet my two phones my landline-phone my netbook...
22:29.30warfareI'd like to see the coffeemachine, please ;)
22:29.34chem|stcollegue asking, oh is it android or windows... neither nor...
22:29.58chem|stwarfare: it is an old saeco
22:30.51chem|stall coffeemachines I know run some linux based firmware, even my 10 year old sony has a linux kernel
22:30.56keriowarfare: well, hopefully now that you have a n900 you'll realize how wrong you were
22:31.04keriois not smug at all
22:31.45warfarekerio: I still have my n810 ;)
22:33.54warfare*grah* libidn11 is hiding in extras-devel
22:36.46warfareSo, extras-devel is required for cssu-thumb.
22:38.51keriohuh
22:38.56keriofreemangordon: did you know about this?
22:39.04keriowarfare: my, do we have a repository for YOU sir
22:39.13keriowarfare: http://extras-devel.merlin1991.at/ fremantle free non-free
22:39.14warfare;)
22:39.24freemangordonkerio: yes, and it comes with -testing i guess
22:39.27warfareAlready enabled that.
22:39.31kerioyay
22:39.45freemangordoni suspect libcurl, but not sure
22:39.46keriothe hostname ones are different from the apt-mirror ones
22:39.50keriothey're better, in fact :)
22:40.02warfarefreemangordon: yep, its libcurl and friends.
22:40.24freemangordonwill pester luf when he appears :)
22:40.49keriowarfare: just be a man and keep extras-devel enabled
22:40.55keriothe light version is lighter on HAM too
22:43.13warfareand still has a 14M Packages file ;)
22:43.52keriowat
22:43.54keriono way
22:43.58warfareOk, regular extras-devel has 25.6M
22:44.05warfareunpacked.
22:44.05kerio...oh, you have no bzip2 installed, right
22:44.17keriomerlin1991: please also add Packages.gz
22:44.21keriofor our stocky friends
22:44.31warfare.gz's are there.
22:44.45keriohm?
22:45.20kerioi see
22:45.53keriothe "light" repos are due to the fact that repository.maemo.org is stupid, and keeps every version of every package ever built
22:47.48kerioand have no pdiffs
22:52.45warfarelooks like it is installing \o/
22:55.23kerio\o/
23:02.27*** join/#maemo-ssu nox- (noident@freebsd/developer/nox)
23:02.46*** join/#maemo-ssu futpib__ (~futpib@89.106.198.175)
23:10.51warfareupdate successful, device booted normally after the update. all is good.
23:10.59warfarekerio: thanks for your time!
23:18.14*** join/#maemo-ssu GNUtoo-m4a785t-m (~GNUtoo@host3-118-dynamic.54-79-r.retail.telecomitalia.it)
23:18.21*** part/#maemo-ssu GNUtoo-m4a785t-m (~GNUtoo@host3-118-dynamic.54-79-r.retail.telecomitalia.it)
23:23.48*** join/#maemo-ssu Estel_ (~Estel@d56-215.icpnet.pl)
23:23.48*** join/#maemo-ssu Estel_ (~Estel@Maemo/community/contributor/Estel-)
23:59.49*** join/#maemo-ssu jonwil (~jonwil@27-33-137-199.static.tpgi.com.au)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.