IRC log for #maemo-ssu on 20121110

00:01.08*** join/#maemo-ssu Senicius (~alexander@ironlegend.student.ipv6.utwente.nl)
00:07.42*** join/#maemo-ssu Senicius (~alexander@ironlegend.student.ipv6.utwente.nl)
00:10.13*** join/#maemo-ssu Senicius (~alexander@ironlegend.student.ipv6.utwente.nl)
00:17.31merlin1991Pali: pong
00:18.31Palimerlin1991, can you also add symlinks for community, extras and rtcomm to oldmaemo?
00:19.52merlin1991sure, pm me with the paths though please
00:23.28*** join/#maemo-ssu Senicius (~alexander@ironlegend.student.ipv6.utwente.nl)
00:42.45DocScrutinizer05merlin1991: wtf is going on on my IroN900? I just got notified about orrery update, and now I have ~984387 updateable pkgs, like libqtm-12-versit installed:1:1.2.0-tp1-0fn-fremantle13  available:1:1.2.0+git20111104-0nd-fremantle3
00:44.26*** join/#maemo-ssu Senicius (~alexander@ironlegend.student.ipv6.utwente.nl)
00:44.35DocScrutinizer05or sp-rich-core, or python2.5-sip4
00:45.31DocScrutinizer05python-hildon, python, python-osso... pulseaudio-utils (WAAAAH!)
00:45.54DocScrutinizer05libshiboken1.0
00:46.15DocScrutinizer05even camera-ui
00:47.18DocScrutinizer05are all the cssu pkgs < maemo-stock same pkg, and only the mp-community-fremantle-pr lifted them on my device?
00:48.27DocScrutinizer05well, for camera-ui it's the other way round
00:49.14DocScrutinizer05I downgraded to stock camera and it wants to update to 1.1.29.2+0cssu13 now
00:51.38DocScrutinizer05hildon-initscripts, intsalled: 1.26-1+0m5, avail: 1.26-1+dp1
00:51.46DocScrutinizer05WTF is dp1?
00:52.37DocScrutinizer05stops bitching and fires up apt-cache
00:53.40DocScrutinizer05<PROTECTED>
00:53.42DocScrutinizer05<PROTECTED>
00:53.43DocScrutinizer05:-o
00:54.18ShadowJKwhat
00:55.12DocScrutinizer05tools repo activated
00:55.23DocScrutinizer05<--- fool
00:57.39DocScrutinizer05meh!
00:58.40DocScrutinizer05disabled tool catalog, no change (except for hildon-initscripts now gone in list of updatable pkgs)
01:00.43DocScrutinizer05maemo-launcher:  Installed: 0.35-7+0m5  Candidate: 0.35-7+0m5                     Version table:     0.35-7+0m5 0        500 https://downloads.maemo.nokia.com ./ Packages                *** 0.35-7+0m5 0        100 /var/lib/dpkg/status
01:01.14DocScrutinizer05now wtf?!
01:03.51DocScrutinizer05grrrrrr
01:04.23Skry:o
01:04.24merlin1991well that is no update :D
01:05.07DocScrutinizer05groff-base:
01:05.08DocScrutinizer05<PROTECTED>
01:05.10DocScrutinizer05<PROTECTED>
01:05.31merlin1991and what does policy tell you?
01:05.45DocScrutinizer05<PROTECTED>
01:05.46DocScrutinizer05<PROTECTED>
01:05.48DocScrutinizer05<PROTECTED>
01:05.49DocScrutinizer05<PROTECTED>
01:05.51DocScrutinizer05<PROTECTED>
01:06.09merlin1991also please pastebin your /etc/apt/sources.list and /etc/apt/sources.list.d/*.list
01:06.23DocScrutinizer05k
01:07.15DocScrutinizer05IroN900:~# cat /etc/apt/sources.list
01:07.17DocScrutinizer05IroN900:~# cat /etc/apt/sources.list.d/*.list
01:07.18DocScrutinizer05deb http://repository.maemo.org/community-testing/ fremantle free non-free
01:07.20DocScrutinizer05deb https://downloads.maemo.nokia.com/fremantle/ssu/apps/ ./
01:07.21DocScrutinizer05deb https://downloads.maemo.nokia.com/fremantle/ssu/mr0 ./
01:07.23DocScrutinizer05deb http://repository.maemo.org/extras/ fremantle-1.3 free non-free
01:08.16merlin1991hm that looks perfectly fine
01:08.38DocScrutinizer05merlin1991: I installed procps and stock camera-ui, and one of those nuked MP
01:09.05DocScrutinizer05if that's any relevant or yields a clue
01:10.17DocScrutinizer05wtf groff-base 1.18.1.1-11osso3 ?
01:10.47DocScrutinizer05or 1.18.1.1-21 0
01:12.05DocScrutinizer05either we got 21.0 in latest cssu-t then where from my device got this other version that's allegedly installed? or cssu-t has 11osso3 then wtf is 21 from
01:12.08merlin1991hm atm I have no n900 on me so I can't crosscheck what should be there
01:12.28merlin1991I don't remember anything called groff-base in cssu
01:13.19DocScrutinizer05anybody could run apt-cache policy groff-base on his device, and share installed version together with his OS flavor?
01:13.19merlin1991groff-base 21 0 is in extras
01:13.23merlin1991sdk has the osso3
01:13.32merlin1991see http://maemo.org/packages/view/groff-base/
01:13.44merlin1991try to disable extras see what happens
01:13.55DocScrutinizer05np, wilco
01:14.56*** join/#maemo-ssu Senicius_ (Senicius@ironlegend.student.ipv6.utwente.nl)
01:15.16DocScrutinizer05W*T*F*F?? can't edit catalogs
01:15.45PaliDocScrutinizer05, do you have HAM from CSSU ?
01:16.03DocScrutinizer05planned to rename "maemo.org" catalog to "maemo.org extras" - no way
01:16.13DocScrutinizer05I guess so, Pali
01:16.31Palirename of system calatogues is not possible
01:16.36Palionly disable
01:16.42DocScrutinizer05>:-(
01:17.07DocScrutinizer05how sane that mameo-extras is named mameo.org
01:17.19Paliname comes from  nokia
01:17.30DocScrutinizer05s/mameo/maemo/g
01:17.32Paliand that name can be translated into more languages
01:17.51Palisame as ssu name
01:18.12Palirenaming is possible in file in /usr/share/hildon-application-manager/
01:18.31DocScrutinizer05I feel assraped
01:18.34DocScrutinizer05by HAM
01:19.12Palisecurtiy reason - you cannot modify system catalogues as user
01:19.32Paliit is like aegis--
01:19.33DocScrutinizer05# of pkgs down to 3: camera-ui (ok'ish), maemo-auncher (?????), pulseaudio-utils ( GRRR )
01:20.42merlin1991well no idea why there is an update for the later 2 but at least camera-ui is reasonable
01:20.42DocScrutinizer05I can't modify da fuckin NAME, for security reasons?
01:21.12merlin1991you cna#t modify anything on the cataloge for security reasons ;)
01:21.33DocScrutinizer05no idea why there was an update for 89820987 when extras been enabled
01:21.59DocScrutinizer05I'll teach fsckng HAM about security!
01:22.24merlin1991maybe the expired keys of the ssu repos had something todo with that?
01:22.33DocScrutinizer05bullshit rationale. Worse though to adopt it in cssu
01:22.59DocScrutinizer05(security)
01:24.16DocScrutinizer05btw now orrery is gone as well :-/
01:24.23DocScrutinizer05for upgrade
01:24.37DocScrutinizer05of course
01:24.59DocScrutinizer05I wouldn't want to permanently disable maemo-extras repo!
01:25.50merlin1991my bet is, that the domain policy for the ssu repos within ham was valid as long as the keys were not expired and now all the libs and whatnot that have been pushed to extras can be replaced as if there is no priority to repos anymore
01:27.43DocScrutinizer05pulseaudio-utils:  Installed: 0.9.15-1maemo38+0m5  Candidate: 0.9.15-1maemo43+0m5  Version table:     0.9.15-1maemo43+0m5 0        500 https://downloads.maemo.nokia.com ./ Packages *** 0.9.15-1maemo38+0m5 0        100 /var/lib/dpkg/status
01:28.46DocScrutinizer05last update installed crap from tools?
01:29.12merlin1991yep that looks like
01:29.28merlin1991the installed version is in no avaiable repo so I guess tools
01:29.37DocScrutinizer05then that could be the culprit
01:30.53DocScrutinizer05probably since I already had MP nuked when I did last update (?), it "updated" a lot of shit to tools revision level
01:31.14Palilast version of pulseaudio from nokia is 0.9.15-1maemo43+0m5
01:31.34DocScrutinizer05this is a cssu-t system though
01:31.43DocScrutinizer05aah
01:31.59Palidownloads.maemo.nokia.com/fremantle/ssu/mr0/pulseaudio-utils_0.9.15-1maemo43+0m5_armel.deb
01:32.20DocScrutinizer05well, I got a third version I omitted in above paste:
01:32.24DocScrutinizer05<PROTECTED>
01:32.25DocScrutinizer05<PROTECTED>
01:33.11Palithis is too old version
01:33.18Palido you have PR1.2 installed?
01:33.22DocScrutinizer05aah old version in same repo
01:33.39Palino in nokia repo is only last version
01:33.46DocScrutinizer05nfc
01:33.47Palimaybe in SDK is older too
01:34.00DocScrutinizer05<PROTECTED>
01:34.51DocScrutinizer05hell here's the fuill spam of paste:
01:34.57DocScrutinizer05IroN900:~# apt-cache policy pulseaudio-utils
01:34.58DocScrutinizer05pulseaudio-utils:
01:35.00DocScrutinizer05<PROTECTED>
01:35.01DocScrutinizer05<PROTECTED>
01:35.03DocScrutinizer05<PROTECTED>
01:35.04DocScrutinizer05<PROTECTED>
01:35.06DocScrutinizer05<PROTECTED>
01:35.08DocScrutinizer05<PROTECTED>
01:35.09DocScrutinizer05<PROTECTED>
01:35.10DocScrutinizer05<PROTECTED>
01:35.12DocScrutinizer05<PROTECTED>
01:35.38Paliseems like you had disabled SSU repo
01:35.44Paliand now you enabled it
01:36.03DocScrutinizer05nope, I disabled tools repo
01:36.15DocScrutinizer05and now I disabled extras repo
01:36.17Paliaaa, now I see problem
01:36.35PaliDocScrutinizer05, you have in your system enabled PR1.2 nokia repo
01:36.49DocScrutinizer05o.O
01:36.49Palior PR1.1
01:36.54PaliPR1.1 is downloads.maemo.nokia.com/fremantle/mr0/
01:37.06Paliand PR1.3 is downloads.maemo.nokia.com/fremantle/ssu/mr0
01:37.25PaliI looked into PR1.1 and there is pulseaudio 27
01:37.31DocScrutinizer05[2012-11-10 02:07:14] <DocScrutinizer05> deb https://downloads.maemo.nokia.com/fremantle/ssu/mr0 ./
01:37.33Paliand in PR1.3 is 43
01:37.56Palido apt-get update
01:38.37DocScrutinizer05no change
01:39.13Palidid you downgraded pulseaudio package?
01:39.20DocScrutinizer05nevar
01:39.32DocScrutinizer05why should I do that
01:39.49Palithis looks like bad upgrade to PR.13
01:40.21Palior some stupid extras package want to downgrade pulseaudio
01:40.25Pali(no idea why)
01:40.32Paliand HAM did it
01:41.17DocScrutinizer05and what about the other 986487 pkg that show up when I enable maemo-extras?
01:42.06Palior, maybe you have corrupted /var/lib/dpkg/something
01:42.26Palithere is one file on debian where is stored version of each installed package
01:42.54DocScrutinizer05/usr/bin/apt-get install libmissioncontrol-utils ;# Mo.,  9. Jul. 2012 11:51:05 CEST
01:42.55DocScrutinizer05/usr/bin/apt-get install procps ;# Fr., 17. Aug. 2012 20:30:11 CEST
01:42.56DocScrutinizer05/usr/bin/apt-get install sp-oops-extract ;# So., 26. Aug. 2012 18:37:46 CEST
01:42.58DocScrutinizer05/usr/bin/apt-get install openntpd ;# Di., 11. Sep. 2012 21:36:04 CEST
01:43.00DocScrutinizer05/usr/bin/apt-get install procps ;# Sa., 15. Sep. 2012 20:10:57 CEST
01:43.01DocScrutinizer05/usr/bin/apt-get install camera-ui=1.1.29.1+0m5 ;# So.,  7. Okt. 2012 16:17:11 CEST
01:44.06DocScrutinizer05no way I did any weird things via HAM
01:44.42Palicall: sudo hildon-application-manager-config update
01:44.54Paliand then upload your sources.lists
01:45.21DocScrutinizer05I'm root
01:46.31DocScrutinizer05IroN900:~# cat /etc/apt/sources.list
01:46.32DocScrutinizer05IroN900:~# cat /etc/apt/sources.list.d/*.list
01:46.34DocScrutinizer05deb http://repository.maemo.org/community-testing/ fremantle free non-free
01:46.35DocScrutinizer05deb https://downloads.maemo.nokia.com/fremantle/ssu/apps/ ./
01:46.36DocScrutinizer05deb https://downloads.maemo.nokia.com/fremantle/ssu/mr0 ./
01:47.01DocScrutinizer05http://mg.pov.lt/maemo-ssu-irclog/latest.log.html#t2012-11-10T03:07:15
01:48.25DocScrutinizer05I guess merlin1991 was on a trace to something
01:48.31Paliok
01:48.36Paliwhat is problem?
01:49.34DocScrutinizer05[2012-11-10 02:25:50] <merlin1991> my bet is, that the domain policy for the ssu repos within ham was valid as long as the keys were not expired and now all the libs and whatnot that have been pushed to extras can be replaced as if there is no priority to repos anymore
01:50.39Paliyes, this is true
01:50.54Palibecause packages from bad domain are ignored
01:51.18Paliand bad domain is when gpg key is not valid
01:51.30Palior when gpg key does not match to stored in HAM
01:52.15DocScrutinizer05how to fix that now?
01:52.32DocScrutinizer05I mean, I wanna enable extras again
01:52.44Paliask nokia to increase life of gpg key
01:52.47merlin1991rehost ssu repo and put the key you use to sign it into the trusted zone
01:52.50DocScrutinizer05and forget PA-utils for now
01:53.33DocScrutinizer05I'm not hosting ssu
01:55.03merlin1991well you could use apt-pinning to give the ssu repo a higher priority
01:55.10Paliis there anybody in nokia who can change gpg key expiration?
01:55.12merlin1991you basically have to give it a prio over 100
01:55.20merlin1991err over 1000
01:55.25merlin1991Pali:  X-Fade could
01:55.27merlin1991...
01:56.00DocScrutinizer05dang, aren't *we* hosting ssu?
01:56.03Paliand how expiration of gpg keys working?
01:56.17merlin1991*we* are hosting a subset of ssu that works as long as regular ssu works
01:56.36merlin1991Pali: when you create a key you either specifiy an expiration date or "valid forever"
01:56.57merlin1991so nokia would have to resign repos with a new key and push an ssu update containing the fingerprint
01:57.04Paliyes, but I think that there is option to change expiration date of existing key
01:57.40DocScrutinizer05so, wait a minute! what's the actual situation now? Is it just me who hosed his device, or do we face a major desaster?
01:57.41merlin1991DocScrutinizer05:  http://wiki.maemo.org/Extras-devel#Limiting_the_damage you'll have to pin nokia ssu and cssu at a higher level than extras
01:57.56merlin1991DocScrutinizer05: gotta check on my device but possibly everyone
01:58.12merlin1991if my guess is correct about the source of your problem
01:59.17DocScrutinizer05I noticed several maemo keys being expired on http last few days
01:59.54merlin1991yeah (almost) all sll certs around maemo.org have expired aswell
02:05.50DocScrutinizer05merlin1991: I fail to clearly figure how to tell this pinning voodoo about the repo to pin/priorize
02:06.02DocScrutinizer05l=?
02:06.39merlin1991uh I don't know either, gotta read the docs, but I think you can pin based on "suite" which is in the release file on the repo
02:07.05DocScrutinizer05gibberish to me, sorry
02:07.35DocScrutinizer05Package: *
02:07.36DocScrutinizer05Pin: release l=Extras
02:07.38DocScrutinizer05Pin-Priority: 1001
02:07.54DocScrutinizer05is suppesed to do what? prio of maemo-extras to 1001?
02:08.15DocScrutinizer05so my guess been I have to swap Extras by ssu/cssu
02:08.29merlin1991yeah pin ssu and cssu
02:08.38merlin1991and look into the release files ie there's l (label
02:08.40merlin1991arf
02:08.42merlin1991paste fale
02:08.45merlin1991ie http://repository.maemo.org/extras/dists/fremantle-1.3/Release
02:09.15merlin1991Suite can be matched with a=string, label with l=string
02:09.49DocScrutinizer05I'm too tired to get what you're trying to tell me
02:10.04DocScrutinizer05nfc about apt and pinning
02:10.17DocScrutinizer05neither about suite
02:15.13DocScrutinizer05and God damn me if I know what to look up in http://repository.maemo.org/extras/dists/fremantle-1.3/Release
02:17.39DocScrutinizer05shouldn't I maybe lookup "Label: XXXXX" in CSSU repo Release file?
02:18.00merlin1991yep
02:18.35merlin1991cssu has a label of community-testing
02:18.51merlin1991so you can match that with Pin: release l=community-testing
02:19.33DocScrutinizer05so I prepare a file with.. ? TWO sections like
02:19.36DocScrutinizer05Package: *
02:19.37DocScrutinizer05Pin: release l=Extras
02:19.39DocScrutinizer05Pin-Priority: 1001
02:19.48merlin1991extras has to have no prio
02:20.17merlin1991you need to pin ssu and cssu at the same prio (or cssu higher than ssu) and leave extras alone
02:20.19DocScrutinizer05yes, but do I need TWO sections for cssu-testing and nokia-ssu or whatever the name?
02:20.27merlin1991yep you need 2 sections
02:20.36merlin1991and the file is in /etc/apt/preferences
02:20.42merlin1991or actually is exactly that path
02:21.04DocScrutinizer05now just about the friggin label of nokia ssu
02:21.41DocScrutinizer05ssu/mr0 ?
02:21.53DocScrutinizer05or maybe ssu/apps?
02:22.55DocScrutinizer05meh, nm.  https://downloads.maemo.nokia.com/fremantle/ssu/mr0 is 404 or sth
02:23.55DocScrutinizer05so nfc again where to find the Release file there
02:24.25DocScrutinizer05to look up "Label: nokia-ssu"
02:25.08DocScrutinizer05or "Label: MR0" or whatever it might be
02:25.51merlin1991yeah the friggin ssu repo requires user and pass :/
02:26.01DocScrutinizer05:nod:
02:26.12merlin1991and ofc the proper path
02:26.30merlin1991hm should be https://downloads.maemo.nokia.com/fremantle/ssu/mr0/dists/Release
02:26.46DocScrutinizer05Access Denied though
02:27.06DocScrutinizer05wait, wasn't that a question of right device to run browser on?
02:28.04DocScrutinizer05meh, N900 microb also shows "Access Denied"
02:34.30DocScrutinizer05ok, that nokia ssu repo isn't pin-able
02:34.34DocScrutinizer05so what now?
02:35.22merlin1991well either wait for nokia, or add some hugeass mp to cssu that pins everything ssu related
02:35.33merlin1991hides
02:35.49DocScrutinizer05should I try to install my MP again, for a first shot?
02:36.29merlin1991well in order to have cssu you can't use the ssu mp, and the cssu mp doesn't pin anything that we didn't update
02:37.09DocScrutinizer05who knows, maybe all those 897498 pkgs were just those that cssu updated?
02:37.48merlin1991wonders with which key cssu is signed
02:37.49DocScrutinizer05actually it were maybe 100
02:38.03DocScrutinizer05good question
02:38.16DocScrutinizer05I thought you have that, but on second thought...
02:38.27DocScrutinizer05probably x-fade created one for us?
02:38.51DocScrutinizer05apt-get install mp-fremantle-community-pr ?
02:38.57merlin1991yep
02:39.00DocScrutinizer05k
02:39.04merlin1991but it's probably not going to help
02:39.10merlin1991and obviously brings back camera-ui
02:39.12DocScrutinizer05yoh
02:40.33DocScrutinizer05The following extra packages will be installed:  busybox-symlinks-procps camera-ui The following packages will be REMOVED:  procps The following NEW packages will be installed:  busybox-symlinks-procps mp-fremantle-community-pr The following packages will be upgraded:  camera-ui
02:40.39DocScrutinizer05yoh yoh yoh
02:42.58DocScrutinizer05now would I dare to do a `apt-get -s upgrade` instead of starting HAM?
02:45.08DocScrutinizer05nm, need to activate extras anyway
02:45.50DocScrutinizer05meh
02:45.54DocScrutinizer05takes minutes
02:46.01DocScrutinizer05so I guess...
02:46.44DocScrutinizer05yep, 94984270982 pkgs to update
02:47.47DocScrutinizer05this is pretty symptomatic:
02:47.51DocScrutinizer05IroN900:~# apt-cache policy maemo-launcher
02:47.56DocScrutinizer05maemo-launcher:
02:47.58DocScrutinizer05<PROTECTED>
02:47.58DocScrutinizer05<PROTECTED>
02:47.58DocScrutinizer05<PROTECTED>
02:48.00DocScrutinizer05<PROTECTED>
02:48.02DocScrutinizer05<PROTECTED>
02:48.02DocScrutinizer05<PROTECTED>
02:48.04DocScrutinizer05<PROTECTED>
02:48.12merlin1991ham trolls you ;)
02:50.22DocScrutinizer05installed: some unknown (or deprecated or whatnot) version "from var/lib/dpkg/status"; Candidate: a supposedly more trusted higher prio identical version from extras
02:50.40DocScrutinizer05or rather from Nokia ssu?
02:51.04DocScrutinizer05err nope, https://downloads.maemo.nokia.com ./ Packages  should be extras aiui
02:51.41DocScrutinizer05or not? I should stop this, as long as my beloved N900 is still alive
02:52.46DocScrutinizer05deb http://repository.maemo.org/extras/ fremantle-1.3 free non-free   is extras
02:53.31DocScrutinizer05seems we should get a hold of X-Fade as SOON AS POSSIBLE
02:54.29DocScrutinizer05X-Fade: ping! merlin1991found out that our cssu cert expired. We need a fixed one urgently
02:54.32merlin1991/lib/dpkg/status is the currently installed pacakge
02:54.40DocScrutinizer05:nod:
02:54.45DocScrutinizer05gathered as much
02:55.07merlin1991actually the nokia ssu cert expired ;)
02:55.16merlin1991about the cssu cert I'm not 100% sure
02:55.24merlin1991gotta check that myself
02:55.59DocScrutinizer05yeah, might still be me and my friggin tools repo
02:58.06merlin1991and ofc I have to check on my device it it is going similar foobar
02:58.14merlin1991btw it might actually be even funkier
02:58.24merlin1991extras
02:58.28merlin1991is a trusted repo too
02:58.31merlin1991it came in pr1.2
02:58.40merlin1991maybe that cert is valid and the nokia ssu isn't anymore
02:59.02merlin1991I didn't run into the problem because I only have extras-devel enabled, but I'll do some testing when I get home
02:59.12merlin1991btw do you see the bazillion updates in apt or in ham?
02:59.34merlin1991(or both)
03:01.52merlin1991DocScrutinizer05: ^^
03:01.58DocScrutinizer05in HAM
03:02.04DocScrutinizer05haven't checked apt
03:02.31DocScrutinizer05[2012-11-10 03:42:56] <DocScrutinizer05> now would I dare to do a `apt-get -s upgrade` instead of starting HAM?
03:03.32DocScrutinizer05merlin1991: in fact I wouldn't exactly know what to do in apt to simulate the HAM "update" display
03:05.03DocScrutinizer05Reading package lists... Done
03:05.05DocScrutinizer05W: GPG error: https://downloads.maemo.nokia.com ./ Release: The following signatures were invalid: KEYEXPIRED 1349249546 KEYEXPIRED 1349249546 KEYEXPIRED 1349249546
03:05.06DocScrutinizer05W: GPG error: https://downloads.maemo.nokia.com ./ Release: The following signatures were invalid: KEYEXPIRED 1349249546 KEYEXPIRED 1349249546 KEYEXPIRED 1349249546
03:05.08DocScrutinizer05W: You may want to run apt-get update to correct these problems
03:05.39DocScrutinizer05merlin1991: ^^^
03:06.38DocScrutinizer05on apt-get update
03:08.02DocScrutinizer05it's a Warning though
03:08.37DocScrutinizer05I wonder if that might be related to new HAM version
03:11.43DocScrutinizer05merlin1991: http://pastebin.com/QrqdWWWj
03:19.04DocScrutinizer05ooh, and just for the shits'n'giggles:  http://pastebin.com/A7J3h5kh
03:35.36*** join/#maemo-ssu infobot_ (~infobot@rikers.org)
03:35.36*** 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): 21.2011.38-1Tmaemo5.1; (stable): 21.2011.38-1Smaemo4.1
03:35.37*** mode/#maemo-ssu [+v infobot_] by ChanServ
03:36.03*** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn)
03:42.07DocScrutinizer05yep
03:42.29DocScrutinizer05err WUT??? infobot_  ??
03:42.50DocScrutinizer05~+uptime
03:45.17*** join/#maemo-ssu infobot (~infobot@rikers.org)
03:45.17*** 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): 21.2011.38-1Tmaemo5.1; (stable): 21.2011.38-1Smaemo4.1
03:45.17*** mode/#maemo-ssu [+v infobot] by ChanServ
03:45.33DocScrutinizer05seen my pastebins?
03:45.59merlin1991yep
03:47.49*** join/#maemo-ssu Milhouse (~irc_milho@Maemo/community/contributor/Milhouse)
03:48.35DocScrutinizer05just remembered the Z900 (N900-thombie), and noticed it has a [!] and says "maemo5-thumb update available"
03:58.18merlin1991and apt-worker is running :D
04:00.53*** join/#maemo-ssu DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg)
04:02.17merlin1991aaaand ham troll me
04:02.18merlin1991nice
04:02.23merlin1991s/troll/trolls/
04:02.30DocScrutinizer05not really
04:03.00DocScrutinizer05I want my plastic medal now for digging this up first
04:03.13DocScrutinizer05shit
04:03.31merlin1991so far I didn't see a bazillion of packges to upgrade
04:03.44DocScrutinizer05hmm?
04:04.03DocScrutinizer05what now?
04:04.09merlin1991I currently have extras, ssu, and cssu enabled and see no avaiable updates
04:05.05merlin1991in my case it would only upgrade gstreamer0.10-ffmpeg
04:05.16DocScrutinizer05well, what does apt-get update tell you?
04:05.29merlin1991the ususal with the 2 key expired warnings
04:05.39DocScrutinizer05ummm
04:06.20merlin1991tries what happens if he removes the mp
04:07.33DocScrutinizer05rather isntall procps
04:07.44merlin1991ah yeah
04:08.29merlin1991I need the tool repo right?
04:08.47DocScrutinizer05possibly
04:08.57DocScrutinizer05tough policy is again cryptic to me
04:09.10DocScrutinizer05500 http://repository.maemo.org fremantle-1.3/free Packages
04:09.31DocScrutinizer05Candidate: 1:3.2.7-11maemo1+0m5
04:09.45merlin1991ah seems to be in extras
04:10.30merlin1991still only gstreamer
04:10.30DocScrutinizer05I still suspect the enabled tools repo been the culprit
04:11.04merlin1991you must have somehow f00bared your device with the tools repo, becuase I really can't reproduce the problem here
04:11.45DocScrutinizer05I'm pretty sure enabling tools and then installing sth while MP is gone will cause this mess
04:14.55DocScrutinizer05though, would something like >> Inst python-osso [0.4-0maemo4] (0.4-0maemo5 Extras:2.0/fremantle-1.3) << be related to tools?
04:15.51DocScrutinizer05I pasted last few months of apt-get install logs way up
04:16.05merlin1991well for starters I don't even have python-osso installed here
04:16.16merlin1991and extras seems to ship the maemo5 version
04:16.20DocScrutinizer05and I for sure didn't any fapman or HAM stuff that's more insane than enabling a catalog
04:17.23DocScrutinizer05here's another one: Inst python2.5-qt4-maemo5 [4.7.3-maemo5] (4.7.5-maemo2 Extras:2.0/fremantle-1.3) []
04:17.28*** join/#maemo-ssu sicelo^ (sicelo@unaffiliated/sicelo)
04:17.35DocScrutinizer05well, you got them all in my pastebin
04:18.21DocScrutinizer05the weird stuff is why I had to reinstall procps several times
04:19.10DocScrutinizer05I guess my apt-get log is missing the --reinstall calls
04:20.26merlin1991btw is that paste with or without extras enabled?
04:20.44DocScrutinizer05errr with
04:20.52DocScrutinizer05without there's not that much
04:21.07DocScrutinizer05only those 3 pkgs
04:21.18merlin1991hm well the only idea i have is, that you installed something without having extras enabled, otherwise why would you have so many old pkgs?
04:21.47DocScrutinizer05hmmm
04:24.02DocScrutinizer05so you think I should allow an upgrade all?
04:24.33merlin1991at least that list looks safe
04:25.06DocScrutinizer05I wonder how the F* this list could show up *now* while before it never did
04:25.47DocScrutinizer05whatever, HAM GO GO GOOOOO
04:29.49DocScrutinizer05this seems to take a while
04:35.02merlin1991the python stuff takes some time, it optifies on install or something similar weird
04:38.34DocScrutinizer05python-pyside-qtcore(1.0.5-1maemo1) conflicts with python-pyside-qtgui(1.0.0-1maemo1) :-/
04:41.17merlin1991hm but there should be an equally new python-pyside-qtgui
04:41.49DocScrutinizer05python-pyside-qtgui(1.0.5-1maemo1) installing
04:42.08DocScrutinizer05HAM bastard
04:44.59DocScrutinizer05pythin2.5-qt4-common(4.7.5-maemo2) and python2.5-sip4(4.11-maemo0) in python-2.5-qt4-common conflict with python2.5-qt4-core(4.7.3-maemo5)
04:45.25DocScrutinizer05dafaq
04:47.09DocScrutinizer05python2.5-qt4-core conflicts with python2.5-qt4-gui(4.7.3-maemo5) dafaqfaqfaqfaq
04:47.10merlin1991well you need to update all python qt packages in one go
04:47.25merlin1991they need exact versions
04:47.31DocScrutinizer05this is HAM!!
04:47.51merlin1991you need to find the single package that depends on all the others then :D
04:48.02DocScrutinizer05hahahaha
04:49.00DocScrutinizer05I'll run it a second time
04:49.10merlin1991which would be python-pyside
04:49.10DocScrutinizer05and then a third time if necessary
04:50.07DocScrutinizer05:shrug:
04:50.18DocScrutinizer05no more available updates
04:50.45DocScrutinizer05apt-worker busy like hell
04:52.38DocScrutinizer05The following packages have been kept back:
04:52.39DocScrutinizer05<PROTECTED>
04:52.40DocScrutinizer050 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
04:52.55DocScrutinizer05NFC who installed the failing pkgs now, and when
04:54.10DocScrutinizer05IroN900:~# apt-cache policy python2.5-qt4-core
04:54.12DocScrutinizer05python2.5-qt4-core:
04:54.13DocScrutinizer05<PROTECTED>
04:54.15DocScrutinizer05<PROTECTED>
04:54.49DocScrutinizer05merlin1991: thanks anyway
05:02.15DocScrutinizer05psproc and camera-ui in place again, everything fine
05:02.22DocScrutinizer05fsck tools repo
05:04.01DocScrutinizer05idly wonders if apt could update pkgs from their original repos *only*
05:04.54DocScrutinizer05n8
06:11.50*** join/#maemo-ssu l4m3rx (~l4m3rx@darknet.escom.bg)
06:46.18*** join/#maemo-ssu _xnt14 (~xnt14@xceleo.us)
07:28.06*** join/#maemo-ssu dhbiker (~dhbiker@193.2.218.150)
07:59.54kerioDocScrutinizer05: yep
07:59.58kerioit's kinda doable
08:00.20kerioi think, at least
08:00.36keriopin that package/repo combination at 600
08:12.29*** join/#maemo-ssu _xnt14 (~xnt14@xceleo.us)
08:12.29*** join/#maemo-ssu dhbiker (~dhbiker@193.2.218.150)
08:12.29*** join/#maemo-ssu _shadowx (~l4m3rx@darknet.escom.bg)
08:12.29*** join/#maemo-ssu sicelo^ (sicelo@unaffiliated/sicelo)
08:12.29*** join/#maemo-ssu DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg)
08:12.29*** join/#maemo-ssu Milhouse (~irc_milho@Maemo/community/contributor/Milhouse)
08:12.29*** join/#maemo-ssu amiconn (amiconn@rockbox/developer/amiconn)
08:12.29*** join/#maemo-ssu Senicius (Senicius@ironlegend.student.ipv6.utwente.nl)
08:12.29*** join/#maemo-ssu myuu_- (~miku@pool-108-27-88-90.nycmny.east.verizon.net)
08:12.29*** join/#maemo-ssu merlin1991 (~merlin@Maemo/community/cssu/merlin1991)
08:12.29*** join/#maemo-ssu Sc0rpius (~naikel@190.79.197.57)
08:12.29*** join/#maemo-ssu jon_y (~enforcer@124.82.62.227)
08:12.29*** join/#maemo-ssu wmarone (~wmarone@c-67-174-151-253.hsd1.ca.comcast.net)
08:12.29*** join/#maemo-ssu chainsawbike (~chainsawb@unaffiliated/chainsawbike)
08:12.29*** join/#maemo-ssu freemangordon (~freemango@130-204-50-168.2074221835.ddns.cablebg.net)
08:12.29*** join/#maemo-ssu RST38h (marat@wsip-184-180-40-182.ri.ri.cox.net)
08:12.29*** join/#maemo-ssu Jaded (~jade@unaffiliated/jade)
08:12.29*** join/#maemo-ssu KrayonWork (~krayon@pdpc/supporter/28for7/krayon)
08:12.29*** join/#maemo-ssu Lava_Croft (lcd@satgnu.net)
08:12.29*** join/#maemo-ssu krayon (~fallen@pdpc/supporter/28for7/krayon)
08:12.29*** join/#maemo-ssu X-Fade (~xfade@d5152FFD8.static.telenet.be)
08:12.29*** join/#maemo-ssu ruskie (ruskie@sourcemage/mage/ruskie)
08:12.29*** join/#maemo-ssu Skry (~skry@81-175-241-67.bb.dnainternet.fi)
08:12.29*** join/#maemo-ssu tadzik (tjs@feather.perl6.nl)
08:12.29*** join/#maemo-ssu gregoa (~gregoa@chello212186052066.410.14.vie.surfer.at)
08:12.29*** join/#maemo-ssu Woody14619a (~Woody@Maemo/Community/council/Woody14619)
08:12.29*** join/#maemo-ssu povbot (~supybot@office.pov.lt)
08:12.30*** join/#maemo-ssu guly (~why@shivaya.guly.org)
08:12.30*** join/#maemo-ssu andre__ (~andre@wikimedia/aklapper)
08:12.30*** join/#maemo-ssu ShadowJK (jk@terminus.enivax.net)
08:12.30*** join/#maemo-ssu FireFly (~firefly@oftn/member/FireFly)
08:12.30*** join/#maemo-ssu raccoon_ (r@ghs/raccoon)
08:12.30*** join/#maemo-ssu ekze (~nyan@bakaekze.ru)
08:12.30*** join/#maemo-ssu peetah (~peetah@cha92-9-82-236-202-86.fbx.proxad.net)
08:12.30*** join/#maemo-ssu trumee (~parul@93-97-89-157.zone5.bethere.co.uk)
08:12.30*** join/#maemo-ssu Raimu-Z (~raimu@kameli.net)
08:12.30*** join/#maemo-ssu Sicelo (~sicelo@unaffiliated/sicelo)
08:12.30*** join/#maemo-ssu Raimu (rmaunula@tuomi.oulu.fi)
08:12.30*** join/#maemo-ssu DocScrutinizer51 (~lagrange@openmoko/engineers/joerg)
08:12.30*** join/#maemo-ssu tg (~tg@irc.tgbit.net)
08:12.30*** join/#maemo-ssu chem|st (~chemist@svn.unix-ag.uni-kl.de)
08:12.30*** join/#maemo-ssu jon-kha (~jon-kha@hoasnet-fe32dd00-87.dhcp.inet.fi)
08:12.30*** join/#maemo-ssu kerio (kerio@unaffiliated/kerio)
08:12.30*** join/#maemo-ssu macmaN (~chezburge@138.167.190.90.dyn.estpak.ee)
08:12.30*** join/#maemo-ssu ChanServ (ChanServ@services.)
08:12.30*** mode/#maemo-ssu [+vo povbot ChanServ] by verne.freenode.net
08:16.58DocScrutinizer05~+uptime
08:56.22*** join/#maemo-ssu dhbiker (~dhbiker@193.2.218.150)
09:06.11*** join/#maemo-ssu luf (~luf@ip-89-103-223-164.net.upcbroadband.cz)
09:34.34*** join/#maemo-ssu Pali (~pali@unaffiliated/pali)
09:45.37*** join/#maemo-ssu _rd (~rd@p57B48B7F.dip0.t-ipconnect.de)
09:58.37*** join/#maemo-ssu tg (~tg@irc.tgbit.net)
10:03.13*** join/#maemo-ssu _rd (~rd@p57B48B7F.dip0.t-ipconnect.de)
10:10.24*** join/#maemo-ssu NIN101 (~NIN@p5DD286D7.dip0.t-ipconnect.de)
10:19.42Pali~seen X-Fade
10:19.45infobotx-fade is currently on #maemo (2h 6m 9s) #harmattan (2h 6m 9s) #meego (2h 6m 9s) #maemo-ssu (2h 6m 9s), last said: 'ZogG_laptop: ?'.
10:23.52*** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu)
10:34.58*** join/#maemo-ssu kolp (~quassel@212.255.22.174)
10:45.40*** join/#maemo-ssu NIN101 (~NIN@p5DD286D7.dip0.t-ipconnect.de)
11:04.20Paliping freemangordon
11:12.58*** join/#maemo-ssu Senicius_ (Senicius@ironlegend.student.ipv6.utwente.nl)
11:32.07freemangordonPali: pong
11:33.06Palifreemangordon, check your time(zone) for git, in systemui alarm repo is good anomaly :D
11:34.10freemangordonPali: I am using virtual machine, it could be that time zone is not setup correctly
11:34.33Paliok
11:34.43freemangordonhmm, settings look ok
11:34.51freemangordontime zone is correct
11:35.03Palianyway I pushed new patch for debian/control
11:35.28Pali(commit time about 30 minutes ago)
11:35.51freemangordonPali: good. And I pushed some fixes, alarmui should be working ok now
11:36.00Paliok :-)
11:36.11freemangordonok as in stock :)
11:36.29freemangordonI am going to remove all of the global variables dhit
11:36.42freemangordoncan't believe it is written in that way :(
11:37.02freemangordondid yoiu look at the code?
11:37.05freemangordon*you
11:39.02Paliyes
11:39.15Palibtw, why are you marking that c source file as executable?
11:39.31freemangordonI am using QtCreator under windows to edit it
11:39.49freemangordonchmod 777
11:40.08Palichmod 666 or chmod 644
11:40.13*** join/#maemo-ssu _rd (~rd@p57B48B7F.dip0.t-ipconnect.de)
11:40.31freemangordonok, ok, I know, no particular reason for 777
11:40.55jon_yC file doubles as a shell script to compile itself :)
11:41.33Palijon_y, not possible because header #!/ is not comment in C
11:46.06*** join/#maemo-ssu freemangordon (~freemango@130-204-50-168.2074221835.ddns.cablebg.net)
11:46.56*** join/#maemo-ssu Woody14619a (~Woody@2620:4:4000:1:c95a:a95d:2340:5acd)
11:46.56*** join/#maemo-ssu Woody14619a (~Woody@Maemo/Community/council/Woody14619)
11:47.28freemangordonhmm, power outage :(
11:57.19*** join/#maemo-ssu _rd (~rd@p57B48B7F.dip0.t-ipconnect.de)
12:04.03jon_yPali: it calls sed to output and stream itself to gcc?
12:04.23jon_yyeah, probably more complicated than required
12:04.28Palijon_y, stupid, because that source is plugin, not executable
12:04.57Palijon_y, but tcc can be used as #!/usr/bin/tcc -run :-)
12:05.04Palitcc is tiny c compiler
12:05.10jon_yyeah, I forgot about tcc
12:06.11jon_ytcc should implement repl-like functionality :)
12:06.28jon_yso C can run as fast as interpreted script code :)
12:10.37keriojon_y: there's CINT for that
12:10.42kerioor picoc
12:10.58jon_ydoes it run as fast as interpreted code? :)
12:11.05kerioidk
12:11.14jon_yit's a feature to emulate that part as well
12:11.45keriojust write the interpreter in python :D
12:12.31jon_yoh, I have pypy to do that, infinite recursions
12:12.52jon_ymay run out of stack running helloworld tests
12:21.00*** join/#maemo-ssu toxaris (~toxaris@s83-180-246-172.cust.tele2.se)
12:33.37*** join/#maemo-ssu iDont (~iDont@j138215.upc-j.chello.nl)
12:37.26*** join/#maemo-ssu dhbiker (~dhbiker@193.2.218.150)
13:10.53kerio:3
13:11.53*** join/#maemo-ssu _rd (~rd@p57B48B7F.dip0.t-ipconnect.de)
13:17.51keriojon_y: pypy works by black magic, though
13:18.11jon_yI guess jython it is
13:19.15keriojython sucks :(
13:19.26kerioPali: i want moar features in your battery applet!
13:19.42jon_ykerio: only doing a subset of python?
13:19.54Palikerio, patches are welcome :-)
13:20.04keriojon_y: nah, i think it does pretty much everything cpython does, except for the c bindings thing
13:20.14kerioPali: no, i don't actually want to do things
13:20.21kerio>:D
13:20.21jon_yI do JNI for that :)
13:20.25jon_yor JNA
13:20.32keriojon_y: jython runs in the jvm
13:20.34kerioit's evil
13:20.53jon_yeven if it is the GNU classpath? :)
13:21.04jon_yhas no idea how good the gnu jvm thing is
13:22.17keriomaybe kaffe is better?
13:22.37*** join/#maemo-ssu dafox (~dafox@ip51cc571d.speed.planet.nl)
13:23.16jon_ykerio: kaffe?
13:23.27keriooh, it does use gnu classpath
13:24.08jon_ydoes it go up to Java 1.7 standards?
13:24.34kerioi doubt it
13:24.39keriothe last stable release was 4 years ago
13:25.14jon_youch
13:26.03kerioopenjdk+icedtea is neat
13:26.59kerioPali: btw, what does the battery applet uses right now?
13:27.11jon_yicedtea is the jvm?
13:28.22keriojon_y: idk
13:28.54kerioit's basically openjdk with replacements for the binary parts
13:28.59jon_yok, it's a build system for openjdk
13:29.04tadzikPali: speaking of battery widget, the estimated time seems completely nonsensical, what kind of value this is? Estimated runtime at warp 9?
13:29.10jon_yI want that on windows too :(
13:29.19tadzik(no irony, I'm seriously curious)
13:29.49Palikerio, it is written in C using GTK+Hildon
13:29.58Palitadzik, data from BME
13:30.12Palior data from BME replacement drivers
13:30.13tadzikI see
13:30.48tadzikSo it doesn't calculate stuff on its own?
13:31.34keriotadzik: ofc not
13:32.38keriotadzik: /sys/class/power_supply/bq27200-0/time_to_empty_now
13:32.47keriotadzik: or /sys/class/power_supply/bq27200-0/time_to_empty_avg
13:32.54kerionot sure *how* the data gets there though
13:37.47*** join/#maemo-ssu Jade (~jade@unaffiliated/jade)
13:49.30tadzikkerio: I don't seem to have /sys/class/power_supply at all
13:49.54keriotadzik: it's not my fault your kernel sucks
13:50.21tadzikwell, shame on KP then
13:52.46*** join/#maemo-ssu dhbiker (~dhbiker@193.2.218.150)
14:09.36Palitadzik, replacement bq modules are by default blacklisted
14:09.47Palibecause are incompatible with BME
14:10.08Palithat kernel modules are replacement for BME
14:11.15*** join/#maemo-ssu MrPingu (~MrPingute@86.92.226.97)
14:18.53kerioPali: where's the blacklist?
14:18.56kerioand what loads them?
14:19.26Paliwhich blacklist?
14:19.43keriothe module blacklist
14:20.22Pali/etc/modprobe.d/
14:20.34kerioi see
14:20.50keriowhat's mousedev?
14:24.56PaliMouse (ExplorerPS/2) device interfaces
14:26.00Paliit is disabled since v34 by titan
14:45.11keriowhy?
14:46.11freemangordonwonders how to properly test the changes in alarm UI
14:46.58kerioPali: how can i convince you to give absolute priority to bq27200 data over rx51-battery data?
14:47.25freemangordonkerio: which data, voltage?
14:47.35keriofreemangordon: total capacity, percentage
14:47.50Palibq27x00_battery cannot report total capsacity
14:48.08freemangordonkerio: bq27000 needs a  calibration to have proper values
14:48.09kerioPali: it reports the full charge
14:48.12freemangordonthis one too
14:48.27keriofreemangordon: which is better than the silly value reported by rx51-battery
14:48.29Palithere is no full charge
14:48.31kerio(where does that come from?)
14:48.36Palionly some last value
14:48.53kerioPali: /sys/class/power_supply/bq27200-0/charge_full
14:48.59Palivalue that consider chip as last used
14:49.05keriothat's not the last value, that's the last calibration value
14:49.11kerioaged "appropriately"
14:49.12freemangordonkerio: this is not design capacity
14:49.16Palikerio, it is last
14:49.22keriofreemangordon: why should we use design capacity?
14:49.30kerioPali: it's the last if you followed the proper calibration procedure
14:49.34kerio...which makes it accurate
14:49.51freemangordon"proper calibration procedure"
14:49.54freemangordonthis
14:50.44Palirx51_battery reporting full capacity
14:51.10keriofreemangordon: yeah but bq27200 doesn't save the full charge unless you reach VDQ and then go down to EDV1
14:51.10Palibq27x00_battery reporting last or design=2048mAh
14:51.28kerioPali: it's because you haven't calibrated it
14:51.35keriothe design is silly, yes, but we don't really need that
14:51.59kerioDocScrutinizer05: is there a way to figure out if bq27k has been calibrated?
14:52.15Palikerio, what is the problem??
14:52.19kerio...oh, of course there is, CI
14:52.23PaliI do not understand...
14:52.48kerioPali: using battery design is silly, and becomes sillier as the battery becomes older
14:53.24Paliand what?
14:53.26keriothe most accurate thing to measure battery data is bq27200, when properly calibrated
14:54.28kerioPali: maybe it's just me, but 75% to me means that the battery has 75% of the charge that it can hold as of now, not 75% of the charge that it could hold when it was manufactured
15:03.30kerioPali: btw, there's no "done charging" apparently
15:13.45lufIs here someone who has stock kernel + stock bluez? I want to see if there is err log "Can't create GN bridge" when you enable network plugin in bluez :)
15:14.01*** join/#maemo-ssu _rd (~rd@p57B48B7F.dip0.t-ipconnect.de)
15:28.13DocScrutinizer05kerio: bq27200 is reporting percent-of-current-capacity for charge-level
15:30.59DocScrutinizer05freemangordon: I don't know if we'd need design-capacity *anywhere* for battery-statusbar-applet etc
15:31.11DocScrutinizer05it's irrelevant and often incorrect too
15:32.23freemangordondeffinitely we need it for genuine(or not) batteries
15:32.30DocScrutinizer05the charge values reported on a 'normal' lshal are ratiomentric to the actual max charge that battery currently can hold, not to design capacity
15:32.57kerioDocScrutinizer05: maybe as a measure for weird values caused by lack of calibration?
15:33.09DocScrutinizer05this is particularly true when deducing charge level from voltage
15:33.21freemangordonof course, but it is good to be able to compare reported capacity agains what is written on the label
15:33.43DocScrutinizer05not done in statusapplet-battery
15:34.55DocScrutinizer05you *might* need design-capacity when bq27200 is CI, and you want to deduce available charge in mAh from voltage
15:35.46DocScrutinizer05available charge in % from voltage is a formula with one variable: voltage
15:36.16DocScrutinizer05available charge in mAh is with 2 variables: voltage and design capacity
15:36.43DocScrutinizer05unless you got better values from bq27200 since CI=0
15:37.09freemangordonPali: https://gitorious.org/community-ssu/osso-systemui-alarm/commit/5209126ea32c19013a3435b6740a66df0e432632
15:37.11freemangordon:)
15:37.26freemangordonGuys I need volunteers to test the alarm UI
15:37.41freemangordonso far clock alarm should be ok
15:37.59freemangordonbut IDK how to test calendar alarm
15:38.33freemangordonnew UI allows alarms with 1 minute interval ;)
15:38.52freemangordonauto-snooze should work too with multiple alarms
15:39.33Paliworking it in portrait mode?
15:39.56freemangordonPali: hmm, never tested it :D
15:40.13Paliok
15:40.18freemangordonbut that will be the cherry on the top when *FUNCTIONALITY* is ok :P
15:40.39Palinext question, difference between nokia and your version
15:40.57freemangordonBTW portrait works with forced rotation, so I think we only need to add appropriate flag
15:41.06*** join/#maemo-ssu NIN101 (~NIN@p5DD286D7.dip0.t-ipconnect.de)
15:41.06Paliok
15:41.12freemangordonPali: see the commits. Or rephrase
15:41.31freemangordonMy changes are on top of "stock"
15:41.39freemangordonI don;t reinvent alarm UI
15:42.34Paliwhat bugs are in nokia version?
15:42.37freemangordonBTW I really wonder what kind of QA (if any) has  passed this piece of crap
15:42.49freemangordonPali: most of the data is global
15:43.05freemangordonso you just can't have simultanios alarm events
15:43.17freemangordonand all the stuff like that
15:43.23freemangordonmemory leaks
15:43.51Palinow you know reason, why nokia did not opensourced it :D
15:44.09freemangordonyeah :(
15:44.23DocScrutinizer05usual reason, actually
15:44.27DocScrutinizer05no kidding
15:44.49freemangordonbut I didn't tested calendar and power-on code paths
15:45.00freemangordonthat is why I need volunteers :D
15:45.17DocScrutinizer05power-on is rather tricky
15:45.28freemangordonI know
15:45.37DocScrutinizer05dunno how much gets gandled by alarmd
15:45.43DocScrutinizer05handled*
15:45.54freemangordonit sends the events
15:45.56keriofreemangordon: does it work fine with the replacement for worldclock?
15:46.04freemangordonkerio: those are unrelated
15:46.19freemangordonboth are frontends to alarmd
15:46.38kerioare you sure? because it does some weird stuff with alarms for specific days
15:46.44freemangordon"it"?
15:46.55keriothe open worldclock
15:47.02DocScrutinizer05WTF?!
15:47.04keriothe UI to set up alarms is different
15:47.15freemangordonwell, could be, I don't use it
15:47.44freemangordonkerio: if you think there is a bug, report it to ade
15:48.05kerioit's not a bug, but i'm afraid that it won't work properly with your UI change :(
15:49.06freemangordonkerio: there is no change to UI
15:49.33freemangordonthe changed part is how the alarm events are handeled
15:49.37DocScrutinizer05wait, so what *is* it you're working on?
15:49.52freemangordonthe logic behind the UI
15:50.00DocScrutinizer05Ui of what?
15:50.04freemangordonalarm
15:50.17freemangordonosso-systemui-alarm
15:50.24DocScrutinizer05so I'd see it when I type `alarm` to xterm?
15:50.31DocScrutinizer05osso-systemui-alarm
15:50.33DocScrutinizer05?
15:50.52freemangordonthe one with STOP/SNOOZE buttons on it
15:51.19Paliosso-systemui-alarm is plugin for systemui
15:51.30Palisystemui is daemon which do some magic with plugins
15:51.44Paliand one plugin is alarm which show alarms
15:52.07DocScrutinizer05aha
15:52.09Palialarms are: events from calendar or alarm clock, ...
15:52.11freemangordon:nod:
15:52.18DocScrutinizer05Pali: thanks
15:52.31*** join/#maemo-ssu dhbiker (~dhbiker@193.2.218.150)
15:52.54freemangordonand it is decoupled to worldclock
15:53.44DocScrutinizer05sneezes and snivels a few times
15:54.23DocScrutinizer05I gather it gets invoked whenever there's an alarm from alarmd firing
15:54.35freemangordonyep
15:54.44DocScrutinizer05maybe a certain class of alarmd alarm
15:54.51Palisystemui daemon has 27144B and about 1800 lines arm instructions
15:55.48DocScrutinizer05and I gather it's closed (sys-ui)
15:55.52freemangordonye
15:55.54freemangordonyep
15:56.05DocScrutinizer05lart nokia
15:56.11Pali(without @plt and data sections)
15:56.19keriowhat deals with alarms when the n900 is turned off, btw?
15:56.31DocScrutinizer05the RTC?
15:56.44keriohow does it turn on, i mean?
15:57.07DocScrutinizer05you mean, what handles wakeup alarms during bootup?
15:57.31DocScrutinizer05since device is turned on by RTC
15:57.34DocScrutinizer05obviously
15:57.35keriooh, neat
15:57.42freemangordont is RTC that wakes the device on. In ACTDEAD mode
15:58.21DocScrutinizer05LOLWUT, RTC wake reason results in act_dead?
15:58.31DocScrutinizer05how reasonable
15:58.54Palinot in alarm mode?
15:59.00freemangordonit seems so, as there is a code in alarm UI which checks for ACTDEAD
15:59.07Palithere is some rtc mode
15:59.24Paliyes, getbootstate convert rtc mode to actdead
15:59.30Paliso you are right
15:59.50Paligetbootstate report user, actdead or malf
15:59.52DocScrutinizer05now hwat wheed did those engineers smoke?
16:00.21Palithis getboostate was not touched since 770
16:00.37Palinew rewritten getboostate is in harmattan (open source)
16:01.10DocScrutinizer05device coming up from RTC IRQ should enter user runlevel, not act_dead runlevel, for all I could think of
16:01.59DocScrutinizer05anyway we won't touch that for a while I guess, since it seems to work
16:02.01Pali<PROTECTED>
16:02.01Pali<PROTECTED>
16:02.01Pali<PROTECTED>
16:02.01Pali<PROTECTED>
16:02.11DocScrutinizer05no matter how screwed the design
16:02.50Palithis is in harmattan getbootstate ^^^^^^
16:02.56DocScrutinizer05yeah
16:03.04Paliand seems that this is in fremantle
16:03.14DocScrutinizer05toldya bootup-alarm handling is rather tricky
16:03.39DocScrutinizer05there might be reasons why it has to come up in act_dead
16:03.57DocScrutinizer05after all you can tell alarm-ui to shut down again
16:04.25DocScrutinizer05or you tell it to boot up completely, when it asks you for lockcode etc
16:04.49Paligetbootstate return: FLASH, LOCAL, TEST, MALF, SHUTDOWN, ACT_DEAD, USER
16:04.50DocScrutinizer05iirc
16:05.04DocScrutinizer05(last tested it ~3 years ago)
16:05.26DocScrutinizer05(since after all, *who* whould *shut down* his N900?? ;-P)
16:06.18Paliwhen you connect charger to powered off device it boot into actdead, if you press power button it full reboot and bootreason will change to sw_rst which getboostate translate to user or malf
16:06.24DocScrutinizer05alarm-ui has to handle all those niche cases
16:06.26*** join/#maemo-ssu NIN101 (~NIN@p5DD286D7.dip0.t-ipconnect.de)
16:06.30DocScrutinizer05aiui
16:07.01Paliso why I need to reboot my phone??
16:07.37freemangordonDocScrutinizer05: well, stock one does not handle anything but ACTDEAT
16:08.16PaliSHUTDOWN is handled by /sbin/preinit and it immediately turn off device
16:08.32PaliMALF is also handled by /sbin/preinit and it show stupid message
16:08.34DocScrutinizer05nfc, it handles wakeup from power-down, wake-up from act_dead, and alarms during screen-locked as well as alarms during interactive
16:08.53DocScrutinizer05Pali: irrelevant for alarm-ui
16:09.06freemangordonwake-up from power down because of RTC is act-dead
16:09.23DocScrutinizer05I don't give a shit about what 'it is'
16:09.46DocScrutinizer05it gets handled correctly by stock alarm-ui
16:09.56freemangordonbut?
16:10.19DocScrutinizer05nothing but
16:10.46DocScrutinizer05rather make sure this doesn't change for the worse
16:10.57freemangordonORLY?
16:11.02DocScrutinizer05hehehe
16:11.46DocScrutinizer05[2012-11-10 17:03:39] <DocScrutinizer05> there might be reasons why it has to come up in act_dead
16:11.48DocScrutinizer05[2012-11-10 17:03:57] <DocScrutinizer05> after all you can tell alarm-ui to shut down again
16:12.16freemangordonno, once woken, it stais there
16:12.21freemangordonAIUI
16:12.34DocScrutinizer05nope
16:12.37freemangordonbooted in actdead
16:13.13freemangordonthough I might be wrong, didn't checked that part of the code
16:14.01DocScrutinizer05you didn't even check the function in real life
16:14.21freemangordonDocScrutinizer05: what's wring with you man?
16:14.24freemangordon*wrong
16:14.34DocScrutinizer05???
16:14.40freemangordonwhy don;t you check the commit dates, ok?
16:14.47freemangordonhours even
16:14.51DocScrutinizer05???
16:15.07freemangordon<DocScrutinizer05> you didn't even check the function in real life
16:15.12DocScrutinizer05???
16:15.17freemangordonwhen I was supposed to do that?
16:15.38DocScrutinizer05before you start to develop patches for that very function?
16:15.58freemangordonthe source code is REed
16:16.00DocScrutinizer05to see what original component is doing in that situation?
16:16.15freemangordonok, ok.
16:17.30DocScrutinizer05set an alarm, power down device, watch alarm firing, look what the alarm-ui does in that particular case
16:18.16DocScrutinizer05as mentioned above *I* tested that some 3 years ago, so I can't help with 100% accurate info - you're on your own
16:21.26*** join/#maemo-ssu Woody14619a (~Woody@2620:4:4000:1:c95a:a95d:2340:5acd)
16:21.26*** join/#maemo-ssu Woody14619a (~Woody@Maemo/Community/council/Woody14619)
16:22.55DocScrutinizer05It comes up, asking "snooze" "stop alarm". Then when I stop alarm, it asks "start up device?" "shut down again?"
16:23.20DocScrutinizer05alas it shuts down during the time I typed this if I don't answer last question
16:24.01DocScrutinizer05(this is most actual recent info now, for your convenience)
16:26.58DocScrutinizer05(all of the above tested with no charger plugged in)
16:28.16DocScrutinizer05when I answer "power up device", it goes thru a complete reboot cycle, incl blue-on-white NOKIA screen and vibrator kicking and all
16:29.00DocScrutinizer05(btw powerkernl still does that also on powerdown - quite a bit puzzling)
16:29.15keriodafuq?
16:29.16kerionot here
16:30.44DocScrutinizer05I tested on Z900-thumbified and it does exactly that on shutdown:black, screen, .... bwahahaha this time of course it doesn't
16:31.01kerioNOTABUG could not reproduce
16:31.02keriomwahaha
16:32.28*** join/#maemo-ssu ron0062000 (~ron006200@cpe-72-181-242-49.tx.res.rr.com)
16:34.26*** join/#maemo-ssu _ade_ (~arno@52481E0B.cm-4-1a.dynamic.ziggo.nl)
16:35.52_ade_kerio: whats that "because it does some weird stuff with alarms for specific days"
16:36.17kerio_ade_: ohai
16:36.26keriofor instance, it supports alarms for specific dates :)
16:36.28_ade_hai
16:36.35_ade_so?
16:36.50kerioso it's something that the stock worldclock doesn't do
16:37.17_ade_okay, I thought we where talking about a bug...
16:37.24freemangordonkerio: if stock alarm UI handles that, there will be no problem with replacement
16:38.01kerioi think that it's an alarmd thing, so there shouldn't be a problem
16:38.05DocScrutinizer05dafaq, it did 3 times irregular behaviour on shutdown now, in a row, and now 3 time shutdown behaviour as expected
16:38.30kerioDocScrutinizer05: i never encountered that behaviour
16:40.39DocScrutinizer05haha, I know what it did! It changed alarmd time to (real-alarm-time - 1min), and thus on shutdown it already thought "duh, I need to enter act_dead mode now, so I'll be able to kick off due alarm in 90sec"
16:40.54_ade_kerio: for alarms on a specific date, I just fill the timestamp, just like the calendar app does for example.
16:41.13kerioDocScrutinizer05: hahaha
16:41.24kerio_ade_: yep, that's what i figured
16:45.51_ade_freemangordon: when adding an alarm to alarmd, you can provide a custom alarms sound (per alarm). But that does not work. Is that functionality a part of alarm-ui?
16:47.03DocScrutinizer05Pali: freemangordon: it's obviously like that: alarmd sets RTC to a time some minutes _before_ real alarm is scheduled, to allow system to boot up to act_dead. Alarmd is active in act_dead. Then at real alarm-time as scheduled by used, alarmd emits the according events/signals to start up alarm-ui
16:48.40DocScrutinizer05alarm-ui in turn, when detecting "current-state == act_dead" shows a requester "boot up device?" / "shut down again?" and initiates according runlevel transition
16:49.27DocScrutinizer05HTH
16:54.25DocScrutinizer05btw system on boot-up needs to check if bootreason been RTC-alarm and if so, stays in act_dead for above scheme to work
16:55.51keriocouldn't've they just said to people to keep the phone on to make alarms work? :s
16:56.04DocScrutinizer05you can watch all this if you set an alarm 5+ minutes to the future, and then shut down system. Watch it boot up to act_dead ~1min before your scheduled alarm
16:58.09*** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172)
17:00.48DocScrutinizer05kerio: how would you keep device on for as long as alarm set to 2012-12-24,19:30 on the N900 gift for your nephew
17:01.17keriowhy would i give my nephew a N900 as a gift instead of keeping it for myself?
17:01.44kerio"the n900 is a dead platform - here, have this galaxy s3"
17:01.50DocScrutinizer05tell him "here's your xmas gift package, it has a hole here you should plug an usb-charger to until you inpack on xmas eve"?
17:02.24DocScrutinizer05meh
17:02.29kerioDocScrutinizer05: somehow i think he'll remember that 24/12 is christmas' eve
17:02.32kerioeven without the alarm :)
17:03.06DocScrutinizer05you're a quite uninspired person, aren't you?
17:03.42kerioi'm old enough to open gifts when i receive them :D
17:03.54DocScrutinizer05I think it's a nice surprise if xmas gift package starts off an alarm under the tree, while kids are still singing holy-shit
17:04.21keriohehe
17:04.23kerio"BEWARE, I LIVE"
17:04.24keriohttp://www.youtube.com/watch?v=S-XEINagmaU
17:04.25merlin1991rofl @ "holy-shit"
17:05.24*** join/#maemo-ssu ron0062000 (~ron006200@cpe-72-181-242-49.tx.res.rr.com)
17:57.41*** part/#maemo-ssu _ade_ (~arno@52481E0B.cm-4-1a.dynamic.ziggo.nl)
17:59.02*** join/#maemo-ssu ron0062000 (~ron006200@cpe-72-181-242-49.tx.res.rr.com)
18:33.54*** join/#maemo-ssu _rd (~rd@p57B48B7F.dip0.t-ipconnect.de)
18:48.06*** join/#maemo-ssu ron0062000 (~ron006200@cpe-72-181-242-49.tx.res.rr.com)
19:01.31*** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172)
19:17.25*** join/#maemo-ssu _rd (~rd@p57B48B7F.dip0.t-ipconnect.de)
19:35.20*** join/#maemo-ssu dafox (~dafox@ip3e8380c8.speed.planet.nl)
20:06.50*** join/#maemo-ssu MrPingu (~MrPingute@86.92.226.97)
20:12.46*** join/#maemo-ssu nox- (noident@freebsd/developer/nox)
20:33.19*** join/#maemo-ssu MrPingu (~MrPingute@86.92.226.97)
20:43.43lufkerio: I also understood how to use dbus + bluez to connect to the remote PAN server ;)
20:58.00*** join/#maemo-ssu arcean (~arcean@aacr221.neoplus.adsl.tpnet.pl)
21:04.11*** join/#maemo-ssu dafox (~dafox@ip3e8380c8.speed.planet.nl)
21:05.24*** join/#maemo-ssu MrPingu (~MrPingute@86.92.226.97)
21:49.48*** join/#maemo-ssu int_ua (~int_ua@ip-602f.proline.net.ua)
21:53.39*** join/#maemo-ssu ron0062000_ (~ron006200@cpe-72-181-242-49.tx.res.rr.com)
22:33.57*** join/#maemo-ssu MrPingu (~MrPingute@86.92.226.97)
23:00.57*** join/#maemo-ssu Skry (~skry@81-175-241-67.bb.dnainternet.fi)
23:06.35int_uafreemangordon: ping

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