**** BEGIN LOGGING AT Tue Jul 30 02:59:58 2013
Jul 30 05:31:08 <kerio> wait, what
Jul 30 05:31:12 <kerio> supl.google.com stopped working too? :O
Jul 30 05:47:47 <joga> kerio, what, nooo
Jul 30 05:47:56 <kerio> i hope not
Jul 30 06:24:03 * Luke-Jr wonders why there isn't just an official GPS SUPL server
Jul 30 07:38:39 <kerio> so
Jul 30 07:38:51 <kerio> it appears that supl.google.com doesn't quite work ._.
Jul 30 07:40:43 <kerio> waaaait
Jul 30 07:41:00 <kerio> it was set at supl.nokia.com
Jul 30 07:42:11 <kerio> supl.google.com works
Jul 30 07:47:49 <joga> phew
Jul 30 08:04:26 <sardini_> is yesterday last update cssu?
Jul 30 08:21:04 <peterbjornx> does anyone here know anything about the n900 and making alt. batterys?
Jul 30 08:32:46 <psycho_oreos> sardini_, 1) It's best to ask in #maemo-ssu, 2) It probably won't be the last update, there seems to be new patches here and there that are coming through along with some issues with CSSU updates. 3) Depending on which flavour you have, CSSU-S is somewhat far from CSSU-T and bleeding edge is CSSU-D.
Jul 30 08:33:01 <kerio> peterbjornx: alt. batteries?
Jul 30 08:33:16 <kerio> cssu-devel isn't a cssu flavour
Jul 30 08:33:20 <kerio> it's just random packages
Jul 30 08:33:36 <kerio> it's intended as a way for devs to push packages that can't fit in extras-devel
Jul 30 08:33:52 <kerio> hell, cssu-devel doesn't *exist*
Jul 30 08:33:57 <psycho_oreos> Ahh I thought the devel was one of those hidden repositories :)
Jul 30 08:34:02 <kerio> there's a repo for personal use called community-devel
Jul 30 08:34:11 <kerio> it's publicly available, to use at your own peril
Jul 30 08:35:05 <brolin_empey> ~cssu
Jul 30 08:35:08 <infobot> cssu is, like, http://wiki.maemo.org/Community_SSU
Jul 30 08:35:40 <peterbjornx> kerio: i've got a 3.7 v 1.7Ah logitec li-ion battery that i want to use for my n900
Jul 30 08:35:40 <kerio> cssu-thumb is a modified cssu-testing with a lot of recompiled packages
Jul 30 08:35:58 <kerio> peterbjornx: does it fit? :o
Jul 30 08:36:30 <peterbjornx> no but my n900 isnt anywere near stock shape anyway
Jul 30 08:36:37 <kerio> lol
Jul 30 08:36:42 <kerio> does it have a shape?
Jul 30 08:36:48 <psycho_oreos> Supposedly cssu-thumb takes advantage of the processor's capability (once it is unlocked).
Jul 30 08:37:35 <kerio> no, it's just a faster compiler configured to use a slightly more space-efficient instruction set
Jul 30 08:37:53 <kerio> to use that instruction set, however, you need a workaround in the kernel for a silicon errata
Jul 30 08:38:48 * brolin_empey got 2 new Nokia BL-5J batteries for a cash donation of 5 CAD to his local hack(er)space.
Jul 30 08:39:16 <kerio> peterbjornx: well, grab a bl-5j, remove the cap, connect the wires
Jul 30 08:39:52 <psycho_oreos> Yeah the instruction set I don't think was enabled by default (re: thumb) no? At least that's how I read it about cssu-thumb stuff. There were two patches to the kernel that were needed to use thumb mode.
Jul 30 08:40:10 <kerio> a kernel patch and a bugfix in the linker iirc
Jul 30 08:40:26 <kerio> and there's nothing to enable, it's just a matter of using it
Jul 30 08:40:52 * psycho_oreos shrugs.
Jul 30 08:43:07 <brolin_empey> kerio: Is errata singular?  Or is errata the plural form of erratum?
Jul 30 08:43:59 <kerio> not entirely sure
Jul 30 08:45:54 <sardini_> CSSU Package(thumb) . Package missing libvte-common (>= 1:0.16.14-Omh9.m7) libvte4(>=1:0.16.14-0mh9.m7)
Jul 30 08:46:18 <sardini_> seems to be a package issue and maybe not because of usb
Jul 30 08:46:31 <kerio> sardini_: pastebin the output of `apt-cache policy libvte-common`
Jul 30 09:02:08 <brolin_empey> drathir: I had to have Nokia USA replace my first N900 under warranty because I could not find a local place which could fix the USB connector.  That was a hassle because I live in Canada, not the so-called United States of America.
Jul 30 09:03:25 <sardini_> brolin_empey, broken usb connector too, I use 2 battery and an external cherger
Jul 30 09:03:28 <sardini_> charger
Jul 30 09:04:57 <brolin_empey> The N900 was not even released in Canada. :/
Jul 30 09:05:20 <brolin_empey> Even though at least some of its predecessors were.
Jul 30 09:17:21 * brolin_empey has had some negative experiences with crossing the border between Canada and the USA.  Some of the staff at the border crossings seem to mistakenly believe that I am working for them instead of vice versa.
Jul 30 09:28:17 * brolin_empey does not want to live in the USA for various reasons.
Jul 30 09:30:26 <peterbjornx> i hope that liion is gonna be charged anytime soon
Jul 30 09:30:41 <peterbjornx> i gotta get my train to OHM2013 in a hour
Jul 30 10:22:44 <DocScrutinizer05> [notice] tmo down due to xen vif bug
Jul 30 10:54:48 <DocScrutinizer05> [notice] tmo back to normal
Jul 30 11:09:05 <kerio> DocScrutinizer05: that's not a notice at all!
Jul 30 11:10:36 <japa-fi> TMO?
Jul 30 11:10:47 <psycho_oreos> talk.maemo.org
Jul 30 11:11:43 <psycho_oreos> Thanks DocScrutinizer05 for addressing that issue, I was wondering for a brief moment what happened to tmo :D
Jul 30 11:12:45 <DocScrutinizer05> Jul 30 12:04:07 blade-b kernel: vif vif-2-0 vif2.0: Frag is bigger than frame.
Jul 30 11:12:47 <DocScrutinizer05> Jul 30 12:04:07 blade-b kernel: vif vif-2-0 vif2.0: fatal error; disabling device
Jul 30 11:12:48 <DocScrutinizer05> Jul 30 12:04:07 blade-b kernel: xenbr1: port 3(vif2.0) entered disabled state
Jul 30 11:12:59 <kerio> fuckin xen
Jul 30 11:13:21 <kerio> why are we encountering so many problems?
Jul 30 11:13:30 <DocScrutinizer05> the funny xen bug once again, which our brilliant sysops were able to track down and report and even fix to some extent on their own
Jul 30 11:13:30 <kerio> isn't it supposed to be reliable?
Jul 30 11:14:14 <DocScrutinizer05> kerio: nope, this bug hits *all* XEN installations worldwide
Jul 30 11:15:31 <DocScrutinizer05> a simple workaround is via some parameter offload=no, which in theory could reduce VIF performance by a few percent but didn't for us
Jul 30 11:17:36 <DocScrutinizer05> until some months ago, XEN silently discarded such frag>frame packets. Recent releases have a patch that disables the VIF, and without xes' kernel patches, dom0 kernel even threw a OOPS and you had to reboot dom0 to recover VIF
Jul 30 11:19:24 <Wizzup> btw, I replaced a digitizer for someone and he needs to put more pressure on the screen when using his fingers -- probably not a very good digitizer
Jul 30 11:19:35 <Wizzup> Is there a way to set the threshold pressure for the n900?
Jul 30 11:19:45 <Wizzup> more pressure than usual*
Jul 30 11:20:30 <DocScrutinizer05> the really "funny" detail in all this: frag resp framesize is a kernel buildtime parameter, and when the parameters of dom0 and domU kernels don't match, then at arbitrary moments - even after months of flawless operation - this "Frag is bigger than frame." hits. And there's no way to even *check* for compatibility of dom0 and domU kernels, since you obviously can't query frag/frame-size
Jul 30 11:21:08 <kerio> neato
Jul 30 11:21:31 <kerio> does recompiling every kernel to make sure that the parameters match fix it?
Jul 30 11:26:09 <DocScrutinizer05> sure, that would help
Jul 30 11:26:58 <DocScrutinizer05> and HAH, maybe tmo / chem|st did a system update on tmo, introducing a new kernel
Jul 30 11:27:30 <DocScrutinizer05> which might explain why we see that bug now, for first time
Jul 30 11:27:39 <DocScrutinizer05> on tmo
Jul 30 11:30:45 <SmokeyD> hey all. I have an N900, and python running with the python-osso-abook module on it (downloaded from svn). The module works fine, but I don't know what the properties are that i can check on a Contact. Are there any docs on this anywhere?
Jul 30 11:30:49 <SmokeyD> I can't find them
Jul 30 12:20:43 <LjL-Maemo> Hmm, the irc thing that integrates with Conversations, while sleek, seems a bit unsuited to heavy irc use. The other irc clients i've spotted look moderately horrid...
Jul 30 12:22:02 <kerio> xchat? irssi?
Jul 30 12:22:50 <LjL> yeah, i was kinda hoping there would be a properly hildon-looking client. xchat looks basically like its desktop version
Jul 30 12:25:31 <Sc0rpius> freemangordon, ping
Jul 30 12:25:53 <Sc0rpius> autobuilder keeps failing now with a little different error
Jul 30 12:25:59 <Sc0rpius> it's not size mismatch but a 404 Not Found:
Jul 30 12:26:07 <Sc0rpius> Failed to fetch http://stage/extras-devel/pool/fremantle/free/libx/libx11/libx11-data_1.1.99.6+0m5+withxcb_all.deb  404  Not Found
Jul 30 12:26:07 <Sc0rpius> E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
Jul 30 12:26:09 <Sc0rpius> but same package.
Jul 30 12:41:29 <SmokeyD> I figured everything out. This is a nice sample script for use with python python-osso-abook module: http://bpaste.net/show/zB5iEdBA613pD4f08FqS/
Jul 30 12:41:43 <Lava_Croft> http://i.minus.com/ibaDjk7AeIcvxv.gif
Jul 30 12:41:54 <SmokeyD> It exports all contacts modified after a specific date (2011-08-27 in this case)
Jul 30 13:18:53 <LjL-Pidgin1> Hm qutim looks fancy, i had to switch the irc module to libpurple to make it work though
Jul 30 14:22:41 <LjL> my memory is terrible - i think i had installed something, the other day, that facilitated enabling/disabling vibration, not sure if from the status menu or what. by default, unless "General" is with vibration and "Silent" is without or vice versa, to change vibration settings, you'd have to go into the Settings, there's no faster way, right? i don't remember what it might have been that made it easier.
Jul 30 14:56:51 <kerio> LjL: the profile applet in the status menu always let you toggle vibration
Jul 30 14:56:59 <kerio> it's stock
Jul 30 15:11:11 <freemangordon> Sc0rpius: ping
Jul 30 15:12:08 <Pali> ~zImage-fb
Jul 30 15:12:09 <infobot> i guess zimage-fb is on http://mohammadag.xceleo.org/public/maemo/kernels/framebuffer/
Jul 30 15:12:48 <kerio> Pali: hald-addon-bme reports a wrong battery capacity now
Jul 30 15:13:09 <Pali> kerio: design? last max? or current?
Jul 30 15:13:29 <kerio> design isn't reported anywhere in the n900
Jul 30 15:13:35 <kerio> so last max, i guess
Jul 30 15:13:52 <freemangordon> Pali: design
Jul 30 15:14:01 <kerio> actually, last full too
Jul 30 15:14:12 <Pali> ok, I will look at it
Jul 30 15:14:20 * Pali writing note
Jul 30 15:14:31 <kerio> Pali: await pastebin
Jul 30 15:14:55 <Pali> $ hal-device bme
Jul 30 15:14:56 <Pali> and also
Jul 30 15:14:58 <Pali> $ lshal
Jul 30 15:15:50 <kerio> http://pastebin.com/rLWJivTG
Jul 30 15:16:27 <freemangordon> battery.reporting.design = 1267  (0x4f3)  (int)
Jul 30 15:16:29 <freemangordon> looks fine
Jul 30 15:16:35 <kerio> even if you want to keep using the silly design report, last full as provided by bq27k is 1574
Jul 30 15:16:41 <kerio> freemangordon: last full
Jul 30 15:17:13 <freemangordon> battery.reporting.last_full = 1267  (0x4f3)  (int)
Jul 30 15:17:33 <freemangordon> is that BME?
Jul 30 15:17:33 <ecc2g> read third pin resistor = "design capacity"?
Jul 30 15:17:54 <freemangordon> ecc2g: this is what bme replacement does
Jul 30 15:17:58 <kerio> freemangordon: hald-addon-bme
Jul 30 15:18:38 <Pali> kerio: where is problem?
Jul 30 15:18:49 <freemangordon> kerio: do you have rx51battery module loaded?
Jul 30 15:18:49 <Pali> are values different as from /sys/class/power?
Jul 30 15:19:27 <freemangordon> Pali: btw I had the same problem as the guy on tmo
Jul 30 15:19:37 <Pali> ok
Jul 30 15:19:44 <freemangordon> my charge was something about 500mAh
Jul 30 15:19:47 <Pali> I need output from lshal and from /sys/class/power
Jul 30 15:19:54 <freemangordon> the reported capacity was 200 mAh :D
Jul 30 15:19:55 <kerio> Pali: LMD is 1574
Jul 30 15:20:11 <kerio> (taken from /sys/class/power...)
Jul 30 15:20:18 <freemangordon> Pali: sorry, I was at the sea shore by that time and fishing :D
Jul 30 15:20:33 <freemangordon> didn;t take those outputs
Jul 30 15:20:43 <Pali> kerio: do you have loaded rx51_battery modele?
Jul 30 15:20:43 <freemangordon> will check what is going on if it happens again
Jul 30 15:21:08 <Pali> It looks like hald-addon-bme do not allow high value as from design
Jul 30 15:21:23 <Pali> I do not remember how it is working... :-)
Jul 30 15:21:29 <kerio> Pali: acehack.de/~kerio/lshal
Jul 30 15:21:44 <Lava_Croft> now thats proper url posting
Jul 30 15:21:46 <Lava_Croft> good job
Jul 30 15:21:54 <freemangordon> Pali: we had some formula
Jul 30 15:22:09 <kerio> http://acehack.de/~kerio/stfu
Jul 30 15:22:25 <kerio> formula?
Jul 30 15:22:27 <kerio> for what?
Jul 30 15:22:44 <Pali> kerio: you have loaded rx51_battery module
Jul 30 15:22:57 <kerio> you always told me to keep it loaded
Jul 30 15:23:24 <Pali> and hald-addon-bme using last capacity as max(rx51_battery value, last bq27 value)
Jul 30 15:23:51 <Pali> not max, but min
Jul 30 15:23:54 <kerio> that's fucking dumb, bq27k keeps track of LMD
Jul 30 15:24:21 <Pali> I know, need to add some gconf key to disable rx51_battery in hald-addon-bme
Jul 30 15:24:40 <Pali> so this is not bug, but design feature :-)
Jul 30 15:24:42 <kerio> but why does it cap the value, regardless?
Jul 30 15:24:45 <Pali> I will try to change it
Jul 30 15:24:49 <kerio> it makes no sense
Jul 30 15:25:14 <kerio> if bq27k is reporting a higher lmd than rx51's design then it's a lot more likely that the latter is wrong
Jul 30 15:25:18 <kerio> rather than the former
Jul 30 15:26:10 <SAiF> Quick questiion, qill N900 support UHS memory cards?
Jul 30 15:26:17 <SAiF> *will
Jul 30 15:26:34 <kerio> yes, but not at max speed, iirc
Jul 30 15:27:01 <SAiF> what will be max transfer speeds that it can support?
Jul 30 15:30:19 <Sc0rpius> freemangordon, pong
Jul 30 15:30:46 <freemangordon> Sc0rpius: now the autobuilder should work, mind to reupload yappari to test?
Jul 30 15:31:04 <Sc0rpius> ok lemme try
Jul 30 15:45:03 <Sc0rpius> looks like it worked
Jul 30 15:45:19 <Sc0rpius> :)
Jul 30 15:48:05 <freemangordon> hmm, don;t see it in the queue
Jul 30 15:48:20 <freemangordon> maybe I am not looking at the right place
Jul 30 15:51:38 <freemangordon> Sc0rpius: did you increase the version?
Jul 30 15:52:25 <freemangordon> ooh, build succeeded :)
Jul 30 15:52:36 <Sc0rpius> yeah it worked :)
Jul 30 15:52:43 <freemangordon> good
Jul 30 15:53:03 <Sc0rpius> I increased the version because I fixed a couple of bugs in the meantime
Jul 30 15:53:33 <freemangordon> hmm, doesn;t look good http://maemo.org/packages/view/yappari/
Jul 30 15:53:38 <freemangordon> latest version is missing
Jul 30 15:55:36 <freemangordon> maybe it needs some time to be copied
Jul 30 15:57:01 <SmokeyD> !gcalc 1033 USD Iin Euro
Jul 30 15:57:30 <SmokeyD> !gcalc 1033 USD in Euro
Jul 30 15:57:30 <SmokeyD> !gcalc 1033 Dollar in Euro
Jul 30 15:57:30 <Sc0rpius> I wonder if we will ever import packages to extras
Jul 30 15:57:41 <Sc0rpius> the karma system and all that stuff never worked anymore
Jul 30 15:57:47 <Sc0rpius> the votes
Jul 30 15:57:49 <Sc0rpius> etc.
Jul 30 15:58:05 <Sc0rpius> it usually takes a while to that package page to refresh
Jul 30 15:58:28 <freemangordon> Sc0rpius: well, now the autobuilder has I maintainer we'll fix it. hopefully
Jul 30 15:58:33 <Sc0rpius> actually it is not refreshed until the package is imported to extras-devel
Jul 30 15:58:42 <Sc0rpius> and that takes a little while, like an hour
Jul 30 15:58:58 <Sc0rpius> http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/yappari/1.0.37/ 
Jul 30 15:59:09 <Sc0rpius> when the package is imported I can see there the filename, md5sum and size
Jul 30 15:59:17 <freemangordon> yep
Jul 30 15:59:22 <freemangordon> going to check in the repo
Jul 30 15:59:34 <Sc0rpius> it must be a cron process that runs like every hour or so
Jul 30 15:59:40 <freemangordon> yeah
Jul 30 15:59:45 <Sc0rpius> but it works, I just give it a little time :)
Jul 30 16:00:20 <freemangordon> hmm, it is here http://repository.maemo.org/extras-devel/pool/fremantle/free/y/yappari/
Jul 30 16:00:32 <freemangordon> Sc0rpius: however, I know what the problem is
Jul 30 16:00:35 <freemangordon> don;t worry
Jul 30 16:00:44 <Sc0rpius> I didn't even know there was a problem :/
Jul 30 16:00:53 <Sc0rpius> I usually wait an hour and everything gets right 
Jul 30 16:00:54 <freemangordon> sure there is
Jul 30 16:01:49 <Wizzup> If it's in extras-devel, does that mean its foss now?
Jul 30 16:06:01 <Lava_Croft> inb4fossgestapo
Jul 30 16:21:20 <jaska> fosstapo
Jul 30 16:53:45 <shawnjefferson22> ~seen DocScrutinizer05
Jul 30 16:53:51 <infobot> docscrutinizer05 is currently on #maemo #n9 #harmattan #meego #openmoko #maemo-ssu #infobot #openmoko-cdevel. Has said a total of 86 messages. Is idling for 2h 25m 11s, last said: 'yw'.
Jul 30 16:54:28 <freemangordon> shawnjefferson22: here?
Jul 30 16:54:53 <shawnjefferson22> yes, in #maemo anyway
Jul 30 16:56:52 <freemangordon> shawnjefferson22: see private 
Jul 30 17:17:20 <shawnjefferson22> DocScrutinizer05: here?
Jul 30 18:14:06 <Lava_Croft> http://opensignal.com/reports/fragmentation-2013/
Jul 30 23:04:12 <DocScrutinizer05> a short update for those wondering what's going on with all our woes on autobuilder|repo-management|administrative_maintenance:
Jul 30 23:04:20 <DocScrutinizer05> [2013-07-31 00:29:53] <DocScrutinizer05> freemangordon: see /usr/share/php/midcom/lib/midcom/core/querybuilder.php line260 ==>
Jul 30 23:04:22 <DocScrutinizer05> [2013-07-31 00:30:16] <DocScrutinizer05>         /* Force read only mode when in anonymous mode */
Jul 30 23:04:23 <DocScrutinizer05> [2013-07-31 00:30:16] <DocScrutinizer05>         if (!$_MIDCOM->auth->is_valid_user())
Jul 30 23:04:24 <DocScrutinizer05> [2013-07-31 00:30:16] <DocScrutinizer05>         {
Jul 30 23:04:26 <DocScrutinizer05> [2013-07-31 00:30:16] <DocScrutinizer05>             $this->toggle_read_only(true);
Jul 30 23:04:27 <DocScrutinizer05> [2013-07-31 00:30:16] <DocScrutinizer05>         }
Jul 30 23:04:29 <DocScrutinizer05> [2013-07-31 00:30:44] <DocScrutinizer05> comment out dat shite, done!
Jul 30 23:06:22 <bef0rd> won't that allow anonymous users to "write" something?
Jul 30 23:07:12 <DocScrutinizer05> this little "optimization" crept in with some install of midgard packages between Dec 2012 and may of this year, and rendered broken an estimated 50..75% of the cronjobs that do all the updates of karma, planet, news, package-interface, repo, younameit
Jul 30 23:09:01 <DocScrutinizer05> no, since normal authentication still applies
Jul 30 23:11:28 <DocScrutinizer05> this is just an optimization done to db-objects (queries) that are r/o and thus you can't change their properties/values/whatever-the-name. It does NOT control if you can or can not do an update to db
Jul 30 23:12:22 <DocScrutinizer05> it's kind like a "const" statement in c
Jul 30 23:13:31 <DocScrutinizer05> according to midgard devels it's been done to reduce memory consumption
Jul 30 23:14:10 <DocScrutinizer05> see for example /lib/midcom/core/querybuilder.php
Jul 30 23:14:28 <DocScrutinizer05> (disclaimer: I have NFC about PHP)
Jul 30 23:15:10 <bef0rd> ah ok, I see some functions there to check privileges
Jul 30 23:15:27 <DocScrutinizer05> ...and I hope that will _never_ ever have to change. I don't want to touch that stuff with a 15ft pole
Jul 30 23:19:00 <DocScrutinizer05> I've been tackling this since quite some time now
Jul 30 23:19:03 <DocScrutinizer05> [2013-07-10 15:16:56] <mashiara> that warning comes from some legacy code trying to rewrite an ISO datetime to UNIX timestamp directly to an object
Jul 30 23:19:05 <DocScrutinizer05> [2013-07-10 15:17:15] <mashiara> but if there is no used logged in objects are returned as read-only as this will increase performance
Jul 30 23:19:06 <DocScrutinizer05> [2013-07-10 15:17:30] <mashiara> said legacy code is likely in the templates somewhere
Jul 30 23:19:31 <DocScrutinizer05> [2013-07-10 13:01:49] <DocScrutinizer05> mashiara: this is very first line of that kind that shows up in www VM maemo_http_error.log:
Jul 30 23:19:33 <DocScrutinizer05> [2013-07-10 13:01:53] <DocScrutinizer05> [Fri Dec 28 09:31:26 2012] [error] [client 10.0.0.1] PHP Warning:  (pid:20625): Can not write property. Object in read only mode in /usr/share/php/midcom/lib/midcom/core/dbaobject.php
Jul 30 23:21:09 <DocScrutinizer05> [2013-07-10 15:55:02] <mashiara> it's old code trying to do things now forbidden issue
Jul 30 23:21:38 <DocScrutinizer05> [2013-07-10 15:55:33] <mashiara> say we have $object->start property which contains ISO datetime as string
Jul 30 23:21:40 <DocScrutinizer05> [2013-07-10 15:55:51] <mashiara> but we want to format it with date, in a few places
Jul 30 23:21:41 <DocScrutinizer05> [2013-07-10 15:56:12] <mashiara> the clever template coder back in the day did $object->start = strtotime($object->start);
Jul 30 23:22:45 <DocScrutinizer05> this bites us on a multitude of levels
Jul 30 23:23:40 <DocScrutinizer05> commenting out just one line might put maemo.org from - say - 30% working to 98% working
Jul 30 23:24:42 <DocScrutinizer05> I mean, all that stuff worked once, some year plus change ago
Jul 30 23:25:19 <DocScrutinizer05> broke down during migration#1 basically
Jul 30 23:26:30 <DocScrutinizer05> obviously due to some slightly newer midgard version got installed on the interim infra
Jul 30 23:31:12 <DocScrutinizer05> I first time since March see a chance to get maemo.org back to old shape, maybe even til end of this week
Jul 30 23:32:17 <DocScrutinizer05> thanks to freemangordon and his incredible energy investigating this particular issue
Jul 30 23:34:51 <DocScrutinizer05> oooh, on a sidenote, I deleted that rogue x11-data_withxdg package from repo for good, and freemangordon pushed repo-management to rebuild Packages.gz - so as a result this issue got solved today as well
Jul 30 23:35:17 <DocScrutinizer05> autobuilder should work again as much as it did before 19th of this month
Jul 31 01:52:35 <user> are you friggin kidding me
Jul 31 01:52:55 <user> just started up phone
Jul 31 01:53:12 <user> got some issues with some custom made scripts not working
Jul 31 01:53:16 <user> the reason?
Jul 31 01:53:43 <user> ls: cannot access fixdate: Stale NFS file handle
Jul 31 01:53:48 <user> perfect
Jul 31 01:54:19 <user> oh and
Jul 31 01:54:24 <robbiethe1st> stale nfs file handle, at least on mine, means filesystem corruption
Jul 31 01:54:41 <FIQ|n900> yes I know
Jul 31 01:54:46 <FIQ|n900> the thing is
Jul 31 01:55:12 <FIQ|n900> I already recovered the file system from an issue like this
Jul 31 01:55:22 <FIQ|n900> last week
Jul 31 01:56:04 <robbiethe1st> It seems that whenever my N900 crashes, the optfs goes wonky
Jul 31 01:56:06 <FIQ|n900> will reboot and attempt to solve this with BM *again*
Jul 31 01:56:27 <FIQ|n900> hopefully it doesn't ruin the fs this time
Jul 31 01:56:44 <robbiethe1st> Any damage is already done at this point
Jul 31 01:57:01 <FIQ|n900> what do you mean?
Jul 31 01:57:35 <FIQ|n900> also
Jul 31 01:57:48 <robbiethe1st> The fact that it said 'stale nfs handle' means that that file is, more or less, gone
Jul 31 01:57:48 <FIQ|n900> this time it was definitely not caused by a hard reboot
Jul 31 01:57:56 <FIQ|n900> it might have been last time
Jul 31 01:58:06 <robbiethe1st> fdisk can probably fix the rest, but you probably won't get the file back
Jul 31 01:58:07 <FIQ|n900> oh but I have a backup of that file
Jul 31 01:58:13 <robbiethe1st> Yeah, that's the only way
Jul 31 01:58:17 <FIQ|n900> my problem is mainly actually solving it with fsck
Jul 31 01:58:26 <FIQ|n900> last time I fsck-ed optfs
Jul 31 01:58:35 <FIQ|n900> it destroyed the file system somehow
Jul 31 01:58:41 <robbiethe1st> Yeah, happens to me too
Jul 31 01:58:47 <robbiethe1st> Best thing is to back it up, then restore
Jul 31 01:58:54 <FIQ|n900> and e2fs claimed I was being a bonehead for having it mounted (it wasn't)
Jul 31 01:59:01 <robbiethe1st> part of the restore is a complete FS wipe/repartition in BM
Jul 31 01:59:47 <FIQ|n900> you're the author of bm, right?
Jul 31 02:00:09 <robbiethe1st> Yeah
Jul 31 02:00:10 <FIQ|n900> just curious, will creation of optfs backup actually work on a corrupted file system?
Jul 31 02:00:19 <robbiethe1st> It'll try.
Jul 31 02:00:31 <FIQ|n900> otherwise I'll have to tar it manually with tar (that worked last time)
Jul 31 02:00:33 <robbiethe1st> If it's mountable, it'll mount and backup whatever files are there
Jul 31 02:00:46 <robbiethe1st> Considering it does exactly that, it should do as well as you can
Jul 31 02:00:54 <FIQ|n900> mkay
Jul 31 02:00:58 <FIQ|n900> will backup
Jul 31 02:01:01 <FIQ|n900> try to fsck
Jul 31 02:01:08 <FIQ|n900> if fsck fail, restore optfs only
Jul 31 02:01:28 <robbiethe1st> Yeah
Jul 31 02:01:47 <robbiethe1st> Heck, you can restore your old optfs backup, if you haven't installed too many programs since
Jul 31 02:02:05 <FIQ|n900> hm
Jul 31 02:02:08 <FIQ|n900> that's true
Jul 31 02:02:27 <FIQ|n900> but then I have to deal with the application desynchs I had to deal with before
Jul 31 02:02:41 <FIQ|n900> oh well, at least I know *which* broke now
Jul 31 02:02:51 <FIQ|n900> instead of discovering them as I go lol
Jul 31 02:02:54 <FIQ|n900> see you
Jul 31 02:02:58 <robbiethe1st> btw, apt-get install --reinstall helps with that
Jul 31 02:03:05 <FIQ|n900> yeah I know
Jul 31 02:03:33 <robbiethe1st> k
Jul 31 02:03:35 <FIQ|n900> did that a lot last optfs restore (didn't restore rootfs because I lacked rootfs for the right kernel)
Jul 31 02:13:17 <DocScrutinizer05> robbiethe1st: there's a pretty fuzzy naming around BM
Jul 31 02:13:41 <DocScrutinizer05> optfs is not existing
Jul 31 02:14:10 <DocScrutinizer05> I suggest to clearly name either the partition or the mountpoint
Jul 31 02:14:35 <robbiethe1st> Uh... huh?
Jul 31 02:15:28 <DocScrutinizer05> so mmcblk0p2, or /home
Jul 31 02:16:40 <DocScrutinizer05> optfs is no term you can actually find anywhere in an docs, and it suggests that maybe only /opt is saved which probably(!?) is incorrect
Jul 31 02:17:02 <DocScrutinizer05> I don't need to explain that /opt is a bindmount
Jul 31 02:21:33 <DocScrutinizer05> robbiethe1st: you were a bit ambiguous if you'd appreciate a devel device or not. I'd like to make this happen anyway unless you say you do not accept any such support
Jul 31 02:24:15 <robbiethe1st> Oh, I thought I said 'yes'
Jul 31 02:25:04 <robbiethe1st> Let me edit my post slightly
Jul 31 02:26:15 <robbiethe1st> There
Jul 31 02:26:28 <robbiethe1st> Must have been slightly tired
Jul 31 02:26:34 <DocScrutinizer05> :-)
Jul 31 02:26:46 <robbiethe1st> (well, really tired. which is typical)
Jul 31 02:27:49 <DocScrutinizer05> I'm also a bit tired right now, which is completely atypic for me, but maybe related to the percieved great achievement in bugfixing maemo.org today
Jul 31 02:28:17 <DocScrutinizer05> feels good to smash the bug
Jul 31 02:28:56 <DocScrutinizer05> well, right now we got it just sitting in the bucket, smashing happens tomorrow ;-D
Jul 31 02:33:47 <DocScrutinizer05> robbiethe1st: I just checked your edit, and I think it's just more confusing XD
Jul 31 02:34:06 <robbiethe1st> *sigh*
Jul 31 02:34:10 <DocScrutinizer05> maybe get some sleep first ?
Jul 31 02:34:14 <DocScrutinizer05> :-)
Jul 31 02:34:19 <robbiethe1st> How do I say 
Jul 31 02:34:40 <robbiethe1st> "yeah, i'm poor, I'll take it" but be very polite and humble about it
Jul 31 02:34:52 <robbiethe1st> <_<
Jul 31 02:35:14 <DocScrutinizer05> hehehe
Jul 31 02:35:50 <DocScrutinizer05> lemme help you out ;-)
Jul 31 02:36:50 <robbiethe1st> Yeah...
Jul 31 02:37:02 <GeneralAntilles> "HELL YEAH! MINE MINE MINE MINE!!"
Jul 31 02:47:35 <robbiethe1st> GeneralAntilles, might be what I'm thinking, but I'd not say it
Jul 31 02:48:00 <robbiethe1st> Cause, you know, I at least /pretend/ to be humble. Because polite
Jul 31 02:52:03 <GeneralAntilles> Whatever, man.
**** ENDING LOGGING AT Wed Jul 31 02:59:58 2013