[03:21] <twb> lilstevie: my btrfs netbook decided to become corrupt with warning this morning, so I think I will be fast-tracking my TF101 now :-P
[03:29] <lilstevie> lol
[03:33] <twb> At least the notes were copied to another box
[03:54] <GrueMaster> Grrr.  Looks like hunspell-en-us has clobbered all arm desktop images.
[04:47] <Xase> lilstevie: oh @ evdev, rollup.
[04:55] <twb> lilstevie: what's the URL for your latest tarball of stuff?
[04:55] <twb> IIRC you changed its name and suchlike
[05:01] <twb> Ah, "OLiFE"
[09:46] <ogra_> hmm, where does that second omap4 armhf image build come from
[09:48] <ogra_> infinity, was that you ?
[09:48]  * ogra_ definitely didnt trigger a second build 
[11:01] <infinity> ogra_: Eh?  What second build?
[11:02] <infinity> ogra_: Oh, cdimage?  I've been asleep.  So, not me.
[11:02] <ogra_> k
[11:02] <ogra_> i'll add the SUDO_USER stuff today then :P
[11:03] <ogra_> but first i would love to know why ubiquity is broken :(
[11:03] <infinity> The build, you mean?
[11:03]  * ogra_ sees no valid reason for it not finding flash-kernel-installer
[11:03] <infinity> I was going to look at that today.
[11:03] <infinity> After I get this mklibs hackery committed for netboot.
[11:03] <ogra_> it complains about f-k-i missing in its source tree
[11:03] <infinity> Yeah, I saw that.  Made little sense.
[11:04] <infinity> Ooo, my bootstrap build of ghc finished.
[11:04] <ogra_> but f-k-i definitely built for hf and the last ubiquity upload calims it pulled it in in the changelog
[11:04] <infinity> Time to get the archive building it.
[11:05] <ogra_> hmm, though it claims it can not create the target in the build log
[11:05] <ogra_> not that the source file isnt there
[11:05] <ogra_> i wonder if there is just a mkdir missing
[11:06] <ogra_> (or -d for the install command)
[11:06] <infinity> But it works on armel.
[11:06] <infinity> Should be the same code.
[11:06] <ogra_> yes
[11:06] <infinity> Looking, though.
[11:07] <ogra_> well, colin claims in the changelog that he adapted links for hf or some such
[11:07]  * ogra_ checks for the exacrt wording
[11:07] <ogra_> hmm, no, that was d-i
[11:07] <ogra_> ubiquity only has * Add armhf support.
[11:08]  * ogra_ doesnt really get it 
[11:09] <infinity> lrwxrwxrwx 1 adconrad adconrad  15 2011-12-08 04:06 armhf -> d-i/lists/armel
[11:09] <infinity> That could be the problem.
[11:09] <ogra_> hmm
[11:09] <infinity> That should be a link to the same directory.
[11:10] <ogra_> geez, unpacking the xz takes my ac100 close to a halt
[11:10] <ogra_> still running
[11:11] <ogra_> fun
[11:12] <ogra_> infinity, to the same file you mean
[11:14] <infinity> Well, to the file in the same directory, yes.
[11:14] <ogra_> yup
[11:14] <infinity> Same problem in debian/
[11:15] <ogra_> you mean the .install file ? yeah
[11:15] <infinity> And that's probably your missing target.
[11:15] <ogra_> and .dirs as well it seems
[11:15]  * infinity is also curious why ./d-i/source/base-installer/kernel/armhf.sh is different from ./d-i/source/base-installer/kernel/armel.sh
[11:16] <infinity> But I'm also not entirely convinced that's used.
[11:17] <ogra_> i doubt it, but it will surely caquse d-i issues since it originates there i think
[11:20] <infinity> Well, let's see if fixing those symlinks makes ubiquity happy.
[11:20] <infinity> To test build or not to test build...
[11:20] <ogra_> pfft
[11:20] <ogra_> just upload
[11:21] <ogra_> will just waste 1h of your day to do a testbuilt, if it fails we can upload again
[11:21] <ogra_> *testbuild
[11:22] <ogra_> testbuilds are for freezes :P
[11:24]  * ogra_ wonders why gcc-4.5 is in the core seed
[11:25] <ogra_> arent we using 4.6 since a while ?
[11:25] <infinity> 4.4 is still in main too.
[11:26] <ogra_> main, sure
[11:26] <ogra_> but core ?
[11:26] <infinity> Eh?
[11:26] <infinity> "core" is just an upload packageset.
[11:26] <infinity> I don't ever want any version of GCC living outside core, do you?
[11:26] <ogra_> i want the default one in core ...
[11:26] <infinity> Packagesets != Seeds.
[11:26] <ogra_> why would i want the fallback there
[11:27] <infinity> You want MOTU updating every compiler other than the primary one?
[11:27] <infinity> Possibly accidentally dropping vital patches and breaking them? :)
[11:27] <ogra_> well, -snapshot is in universe as well
[11:27] <infinity> Yeah, because we don't build packages with snapshot.
[11:27] <ogra_> afaik at least
[11:28] <infinity> Sometimes we fall back to building packages with older versions of gcc.
[11:28] <infinity> (MySQL is built with 4.5, for instance)
[11:28] <ogra_> ah, k
[11:28] <ogra_> i thought we fobid that a while ago
[11:28] <ogra_> *forbid
[11:28] <infinity> We can't, really.
[11:28] <infinity> If a new compiler is broken for some chunk of code, what do we do?
[11:28] <ogra_> fix it :)
[11:28] <infinity> Just say "well, we can't ship MySQL unless the compiler is fixed"?
[11:29] <ogra_> scream and shout to linaro ...
[11:29] <infinity> That sort of thing doesn't work well with time-based releases. :P
[11:29] <ogra_> heh
[13:07] <doko> infinity, hmm, what is wrong with https://buildd.debian.org/status/package.php?p=gcc-4.4&suite=sid ?
[13:07] <doko> armel
[13:09] <infinity> doko: You forget to backport your -mfloat-abi=softfp change from 4.6 to earlier versions?
[13:09] <infinity> doko: (The one where you explicitly set that for the Debian/armel build)
[13:09] <infinity> s/forget/forgot/
[13:11] <infinity>   else
[13:11] <infinity>     # Debian armel
[13:11] <infinity>     CONFARGS += --with-arch=armv4t --with-float=$(float_abi)
[13:11] <infinity>   endif
[13:11] <infinity> doko: ^-- That?
[13:14] <doko> infinity, it's the default anyway, and 4.4 doesn't know about hard-float yet. it's just 4.4 linaro. so I assume I just back out this change for debian
[13:15] <infinity> doko: Eh?  softfp wasn't the default, that's why you had to add it to 4.6...
[13:16] <infinity> (Or, rather, the switch wasn't SET by default)
[13:18] <infinity> doko: --with-float=$(float_abi) only happens in the ifeq Ubuntu block, so no float bits set for debian/armel.
[13:18] <doko> infinity, Debian armel is soft, not softfp
[13:19] <infinity> Well, whatever it was. :P
[13:19] <infinity> I was just copying your else..endif from 4.6 up there.
[13:19] <infinity> Anyhow.  You could just revert and not build on armhf at all.
[13:19] <infinity> Or just make rules2's arm* block match 4.6
[13:21] <infinity> 4.5 is in the same boat, I imagine.
[13:45] <doko> infinity, ahh, no -mfloat-abi= parameter passed at all, which breaks the patch :-/
[13:46] <doko> I know I dislike this default stuffing of config parameters
[13:47] <infinity> I'm sure we can work up a more elegant patch later.  But this "works".
[13:49] <infinity> doko: ghc is building on the buildds now, BTW.
[13:50] <infinity> Local build took forever.  Silly haskell.
[14:12] <ogra_> hmm
[14:12] <ogra_> what i wonder is why did ubiquity 2.9.5 build flawless on armhf ... it shuld have had the same issues as .9.6
[14:12]  * ogra_ just noticed there is a binary
[14:43] <IamTrying> I was using Ubuntu-ARM in my Eee pad transformer, now i get this: http://i.imgur.com/6lY5H.png  . How can i restore to Android using OLiFE.sh ? 1. Backup 2. Flash 3. Inject
[14:45]  * ogra_ would suggest to ask that in a transformer channel ... i doubt anyone here knows OLiFE.sh (apart from lilstevie probably)
[14:52] <IamTrying> Fixed, with OLiFE.sh > Menu update > 1. Android kernel
[14:52] <IamTrying> But i want to go back to Ubuntu again and see what caused it?
[14:54] <lilstevie> IamTrying: sec
[14:55] <lilstevie> wow
[14:55] <lilstevie> wtf did you do
[14:55] <lilstevie> 0.o
[14:55] <IamTrying> Yea i was also thinking what i did. I actually Ubuntu-ARM but it does not auto boot
[14:56] <IamTrying> So i needed to press always Vol+ to boot
[14:56] <lilstevie> yeah, but that framebuffer connection is... just not normal
[14:56] <IamTrying> Then i decided to re-install Ubuntu-ARM again so that auto it boots
[14:56] <lilstevie> and yeah, that is normal if android is set as default boot
[14:56] <lilstevie> ok, still doesn't really answer the question
[14:56] <lilstevie> if you try running it as the recovery boot does it do the same
[14:58] <ogra_> probably the antenna is just mis-adjusted :P
[14:58] <IamTrying> I used this OLiFE.sh script to restore to Android ( https://gist.github.com/1447187 ) and it caused this > http://i.imgur.com/6lY5H.png
[14:58] <lilstevie> that isn't what I asked
[14:59] <lilstevie> ogra_: lol
[14:59] <lilstevie> ogra_: that is like total fb corruption; I don't understand it in the slightest
[14:59] <ogra_> bootloader probably
[15:00] <lilstevie> ogra_: shouldn't be, bootloader goes with the OLiFE scripts
[15:00] <lilstevie> purposely done so I don't have to deal with bootloader issues
[15:00] <ogra_> isnt the frambuffer initialized by the bootloader on the transformer ?
[15:00] <ogra_> like on the ac100
[15:00] <lilstevie> yeah, but corruption like that would be kernel level
[15:01] <lilstevie> or above
[15:01] <IamTrying> Let me freshly install the Ubunt-ARM using OLiFE.sh. But it does not boot auto.
[15:01] <lilstevie> maybe something done to xorg
[15:01] <ogra_> on ac100 we dont re-initialize the fb ... so such a thing cant happen here
[15:01] <IamTrying> I did always need to press vol+ to boot. and finally today it was failing to boot.
[15:01] <ogra_> do you re-init it in the transformer kernel =
[15:01] <ogra_> ?
[15:01] <lilstevie> no, which is why I don't understand
[15:01] <ogra_> yeah, weird
[15:02] <lilstevie> also IamTrying yes, that means you set ubuntu to be secondary boot
[15:02] <IamTrying> I did those steps and it fixed it now and i am back to Android PRime
[15:02] <IamTrying> https://gist.github.com/1447187
[15:02] <lilstevie> AKA; it is meant to do that
[15:02] <lilstevie> as I said last time we had this little conversation
[15:04] <IamTrying> Yes, when i try to setup for option 2, its very odd, it shows a loop of ASUS Screen and Linux unless i press manually down and then up button.  1. Turn device on or 2. Hold vol-down then press vol-up
[15:12] <lilstevie> IamTrying: all I can really suggest is post in the QandA thread on XDA developers, maybe someone has come across your condition before and can help
[15:13] <IamTrying> lilstevie, Yes sure, OLiFE.sh is excellent its genius, its working actually, saved my Android device. I just want to install the Ubuntu-Arm as power-on default boot, but optionally if requires i want to go back like now i did.
[15:14] <lilstevie> default boot can be a little flakey tbh
[15:14] <lilstevie> the mem carveout is not nice
[15:15] <IamTrying> Ok, still fine, but There was a strange crash today. I pressed vol-down, i got the choice then i press vol-up to boot in my Ubuntu-Arm, but it shows lots of error and then nothing just happened. So then i decided to go back to Android.
[15:41] <IamTrying> I just re-installed Ubuntu-Arm using OLiFE.sh just like Day 1. And i have the same crash everytime when i boot e.g: http://i.imgur.com/AGSzH.png
[15:41] <IamTrying> Any idea?
[15:53] <infinity> doko_: I'll fix qtmobility right after my next meeting.