/srv/irclogs.ubuntu.com/2013/05/07/#ubuntu-release.txt

=== mmrazik is now known as mmrazik|afk
=== doko_ is now known as doko
=== mmrazik|afk is now known as mmrazik
ogra_slangasek, there is not much you could help with i fear ... the tarball we have coming out of cadejo is usable, for turning it into a zip we currently need a binary install tool included that needs to be cross built with a bionic toolchain ... i worked out a workaround script in  my home on nusakan for the moment that does the zip production, just need to couple it with my phablet-sync tool for publishing somehow06:47
StevenKbionic toolchain?06:50
StevenKYou need a Borg drone?06:51
ogra_haha06:51
ogra_StevenK, i need an infinity/doko coproduction :)06:52
ogra_we need to package up the android parts of the touch image ...06:53
ogra_cjwatson, did the behavior of the default-arches command when called manually change or did my last change mess up etc/default-arches ?08:15
ogra_it always returns  "amd64 amd64+mac i386 powerpc" no matter what args i use08:16
ogra_i.e.08:16
ogra_cdimage@nusakan:~$ default-arches lubuntu daily-preinstalled saucy08:16
ogra_amd64 amd64+mac i386 powerpc08:16
ogra_that should only return armhf+ac10008:17
ogra_(it did once at least)08:17
cjwatsonThat's not the correct calling sequence08:18
cjwatsondefault-arches takes no arguments08:19
ogra_well, it used to work with args in the past08:19
cjwatson*shrug*08:19
cjwatsonI feel no obligation to preserve that interface08:19
cjwatson$ PROJECT=lubuntu DIST=saucy IMAGE_TYPE=daily-preinstalled default-arches08:20
cjwatsonarmhf+ac10008:20
ogra_ok08:20
ogra_http://irclogs.ubuntu.com/2013/02/26/%23ubuntu-release.txt ...08:20
ogra_cdimage@nusakan:~$ PROJECT=ubuntu-touch DIST=saucy IMAGE_TYPE=daily-preinstalled default-arches08:21
ogra_armhf08:21
ogra_right08:21
cjwatsonI changed it in r106908:22
ogra_now i wonder about the ubuntu-touch builds from last night ...08:22
cjwatsonIt was unnecessarily difficult to preserve the old (irregular) interface while also adding reliable support for SUBPROJECT and UBUNTU_DEFAULTS_LOCALE08:22
cjwatsonThose were manually triggered, yes?08:23
ogra_yeah, fine with me, i just never called it that way08:23
cjwatsonHow did you trigger those builds?08:23
ogra_it doesnt look like SUDO_USER was set, no08:23
ogra_i didnt08:23
ogra_thats the fun part08:23
cjwatsonBut then why multiple builds ...08:23
ogra_i stopped working rather early yesterday08:23
cjwatsonThey were eight minutes apart08:24
ogra_the mails i have are from ~1:30 here08:24
cjwatsonI guess perhaps that was slangasek; he was asking questions about that on IRC at around the same time08:24
ogra_yes, saw that08:24
ogra_it shouldnt build these arches at all08:24
cjwatsonSo I'm going to disregard those failures until he appears and says what he was doing :)08:25
ogra_and if he ran it manually thatr should be in the mail subject08:25
cjwatsonNo08:25
cjwatsonOnly livefs build failures do that right now08:25
ogra_was that dropped ?08:25
ogra_oh, ok08:25
cjwatsonIt was never there for non-livefs builds, AFAIK08:25
cjwatsonThere's certainly some code unification possible08:26
ogra_well, the first set of mails are livefs failures actually08:26
cjwatsonI've deleted the mails now so can't check08:26
infinitySUDO_USER isn't always set either.08:27
cjwatsonDo you mean that the subject starts with "LiveFS"?08:27
ogra_http://people.canonical.com/~ubuntu-archive/livefs-build-logs/saucy/ubuntu-touch/20130506/08:27
ogra_yes08:28
ogra_infinity, apparently08:29
cjwatsonI've adjusted image build failure mails to mention SUDO_USER if it's set, too08:29
cjwatsonbut as infinity says ...08:29
ogra_yup08:29
ogra_i still dont get why it tried all these arches though ... but slangasek might be ablle to tell08:30
ogra_(the 06 and 06.1 armhf builds were mine from around noon btw)08:32
ogra_i wonder if the buildds were just busy for 12h and they were queued up08:35
cjwatsonogra_: I expect because slangasek used cron.daily-live rather than cron.daily-preinstalled08:48
ogra_ah08:48
ogra_hmm, i fear BOOTAPEND_LIVE wont gain us much in the ubuntu-touch images08:50
=== smartboyhw_ is now known as smartboyhw
=== greyback is now known as greyback|lunch
=== greyback|lunch is now known as greyback
slangasekogra_: yeah, those failed builds were mine.  So why does building a .zip require such special tooling?14:03
ogra_slangasek, we dont have the needed binary built in the archive yet14:03
slangasekogra_: what tool do you need that isn't "zip"?14:04
ogra_slangasek, http://bazaar.launchpad.net/~phablet-team/touch-preview-images/phablet-build-scripts/files/head:/META-INF/com/google/android/14:05
ogra_the update-binary binary14:05
ogra_lives inside the adnroid metadata dir14:05
ogra_*android14:05
ogra_will be easy to build it once we have a cross bionic ... until then, not so much ... we could ship it in restricted i guess but that fellt to uglt14:06
cjwatsonApplication-level code is specifically per policy (and Mark) excluded from restricted14:06
slangasekogra_: ok, but what is this tool supposed to *do*?  Creating a .zip file is not hard and doesn't require building binaries for bionic14:06
cjwatsonfwiw, since people seem to keep bringing that up as a possibility ...14:06
ogra_slangasek, its not *creating* the zip, thats stuff android uses during verificastiion when installing it14:07
cjwatsonhttp://stackoverflow.com/questions/15608292/meta-inf-com-google-android-update-binary-source-code has some stuff about this program14:07
ogra_it is used during unpack14:07
slangasekogra_: ok14:08
ogra_we have the source living on phablet.u.c ... its just that we dont have a package atm14:08
stokachuis it more appropriate to ask for sru approval in this channel or -devel?14:08
ogra_if you look in my home on nusakan, the whole zipping code is there14:08
ogra_(in the utouch-android dir14:09
ogra_)14:09
slangasekogra_: ok, but why does this need to be a *bionic* binary at all?14:12
ogra_it is executed in the android recovery mode14:12
slangasekah14:12
infinityIt's statically linked.14:12
ogra_during unpacking/installling14:12
infinitySo, the bionic bit is somewhat of a red herring.14:13
ogra_well, we need it built from source and in a package14:13
infinityBut it needs to be statically linked against some libc that it doesn't hate. :P14:13
slangasekright, so we could just as well statically link an eglibc binary?14:13
infinityIt looks like some sick cross between busybox and every decompression method EVAR.14:13
infinityAt least, from a quick scan with strings(1).  I imagine the source would be more enlightening. :P14:14
cjwatsonLooks like its own mini-language thing14:14
ogra_sergiusens should know ehere the source is  on phablet.u.c14:15
ogra_*where14:15
slangasekogra_: I don't see any source in ~ogra/utouch-android14:15
ogra_there is none14:15
infinityIt can't just be this edify thing.14:15
ogra_slangasek, its my script to roll a zip from the tarball ... essentially what will go into livecd-rootfs modulo the binary14:16
slangaseksergiusens: hi, can you help me find the source to the 'update-binary' program needed for the root .zip?14:16
ogra_i think in a checked our tree it lives under ./bootable/recovery/updater/14:21
ogra_http://phablet.ubuntu.com/gitweb?p=CyanogenMod/android_bootable_recovery.git;a=tree14:21
ogra_that should be the right tree14:21
ogra_yeah ... #include "edify/expr.h"14:22
ogra_http://phablet.ubuntu.com/gitweb?p=CyanogenMod/android_bootable_recovery.git;a=blob;f=updater/updater.c;h=5f1580870d54c3ef8058ffc6230103aa728c40e2;hb=HEAD14:22
ogra_that must be it14:22
* sergiusens reads14:27
* sergiusens is late14:28
ogra_no prob :)14:29
ogra_it made me look at git ... thats a good thing ... i have to get used to it :)14:29
sergiusensogra_: slangasek we can probably add that to the recovery image and remove it from the zip... if that would speed things up, I'll see to it14:30
ogra_if the zip still works  then, that would likely help ... but we need a cross bionic anyway14:31
ogra_and in the end we should have it packaged14:32
ogra_especially in the light that not everyone uses our recovery image14:32
ogra_we would pertty much exclude everyone using a plain CWm recovery for installation14:33
sergiusensogra_: yeah, that would be the case... I thought that long term the recovery image would be rewritten anyways, right?14:38
ogra_would be fine for our own devices ... not so sure about ports14:38
ogra_i guess that would need broader discussion14:38
sergiusensogra_: also, next time you can't find something easily look in .repo/manifest.xml, you'' have the directory<->git_repo translation14:39
ogra_oh14:39
sergiusensogra_: yup, seems like two conflicting objectives14:39
ogra_thanks !14:39
sergiusensnp14:40
ogra_cjwatson, hmm, regarding that image build failure that just hit my inbox ... should cron.daily not exit 0 if there are no default arches at all ? (i dropped ubuntu daily-preinstalled from default-arches but left the cronjob in place assuming it would just not do anything)14:47
cjwatsonI'd rather there were some incentive to clear up clutter14:48
ogra_yeah, i will dissable the cronjob too ... but it looks to me like it shouldnt just fall back to defaults14:48
ogra_-s14:49
cjwatsonIt's doing what it's told *shrug*14:50
cjwatsonThe format's clear, I think14:50
ogra_indeed14:50
cjwatsonThere's a "* * *" wildcard, which covers everything14:51
ogra_oh, right ... the top line14:51
cjwatsonBottom14:51
ogra_oh, right, top is source14:52
ogra_(and i386 only)14:52
cjwatsonWell, insofar as the arch is any more than a cheat there14:53
ogra_cjwatson, gtw, by the looks of it there are no plans for user creation etc on fist boot of the touch images14:54
ogra_would using live-debconf ig be appropriate if we need to create it during build ?14:54
ogra_(vs the hackish scripts the images use now)14:55
cjwatsonNo idea what live-debconf is14:56
ogra_(xnox indicated that there wont be anything like oem-config at all)14:56
ogra_live-debconfig ...  seems to be a new part in live-build14:57
cjwatsonrun away14:57
ogra_http://live.debian.net/manpages/current/en/txt/live-debconfig-set-selections.1.txt14:57
ogra_heh14:57
cjwatsonI don't really see the point in "reusing" that given that it isn't used by us anywhere else14:58
ogra_well, i think using something other thna a ton of adduser calls  from a live-build hook script might still be better14:58
ogra_did i say re ?14:58
cjwatsonWell, no, but the only reason to use it would be if it were reuse14:59
ogra_i only just discovered it in universe searching for a saner way to replace the hooks14:59
ogra_(and wanted an opinion ... run away sounds pretty clear :) )15:00
cjwatsonlive-build is allergic to stable interfaces; I would be very cautious about using it15:00
cjwatsonfor this kind of thing15:00
ogra_k15:00
cjwatsonYeah, that seems very very specific to a particular view of the world in live-build15:01
cjwatsonI don't think it will actually make your life easier in more than the very short term15:01
ogra_well, i'd obviously like a sane solution15:01
cjwatsonWhy's there more than one adduser call and a few fixups?15:02
cjwatsonI realise it's suboptimal to have to duplicate this stuff, but I'm not sure why it's a ton of stuff15:02
ogra_its like 20 groups with fixed numbers ... setting up sudoers etc15:02
cjwatsonWhy not imitate what casper does?15:03
ogra_during install ?15:03
cjwatsonIt preseeds some stuff and calls user-setup-apply15:03
cjwatsonNo, casper, not install-time15:03
ogra_ah15:03
cjwatsonscripts/casper-bottom/25adduser15:03
ogra_yeah, i know casper15:03
ogra_we have something similar in the hooks in livecd-rootfs15:04
ogra_just using direct adduser calls though15:04
cjwatsoncasper's scheme would involve less code duplication if you can make it work15:05
ogra_so you would propose to keep the hook system but use more of a casper like script15:05
ogra_k15:05
infinitystgraber: Is queubot having a sad again?15:05
stgraberinfinity: possibly, let me kick it15:05
infinitystgraber: Give it a rexec command with a simple hostmask ACL (if you fear abuse), and we can all kick it. :P15:06
cjwatsonogra_: Or something.  I don't mean the general format of casper's scripts, I just mean the way it handles that particular case15:07
ogra_cjwatson, yeah15:14
ogra_cjwatson, actually i'll register a spec for UDS, i think we should define that properly (assuming tablet images will want something like oem-config while phones dont and need the GIDs for android etc etc)15:15
ogra_so that sounds like a divergent think in the converged world :)15:16
ogra_*thing15:16
cjwatsonogra_: I thought we already had some design-led work for that15:17
ogra_cjwatson, me too, until xnox told me it wont do user creation or use any debconf in the backend15:17
ogra_i think there is a big gap still15:18
cjwatsonThere's a "personalisation" slot in it, but it's not clear to me that it's worth the overhead of using oem-config15:18
cjwatsonWe already know we'd have to put a lot of work into performance to make that workable15:18
ogra_well i dont care what we use, but it should be consistent15:19
ogra_and it doesnt look like any techincal design has happened there15:19
slangasekogra_: based on the actual requirements for the OOBE on the phone, there doesn't seem to be much reason to reuse oem-config.  We certainly aren't going to be prompting the user to configure a username, so I don't see any reason to do this at install time instead of at image build time15:38
ogra_slangasek, well, i would expect us to ask for a real name15:39
ogra_so that we have some GECOS changes at least15:39
slangasekwe may or may not do; but even if we store that in GECOS, that doesn't involve adding the user to groups at install time15:39
ogra_as well as timezone and language (unless we produce one img per lang)15:40
ogra_what about tablets with multiuser option ?15:40
slangasekout of scope for 13.1015:40
ogra_will they just use oem-config ?15:40
slangasektimezone/language> I don't know what the plan is there; but this needs to be confirmed with design before we commit ourselves to any technical implementation15:41
ogra_well, might be out of scope for 13.10 ... but we are laying a foundation here for the convergence15:41
ogra_and at least a raw idea should be defined15:41
ogra_imho15:41
slangasekogra_: IMHO, laying the foundation for convergence means that, *when* we need to do work for the phone, we think about how it applies to other form factors.  For OOBE, that means we need to first get an agreed design, then figure out what's needed to support that design in the larger ecosystem15:43
ogra_so we wait for the UI ?15:43
slangasekbut we shouldn't insist on using oem-config before we know it's needed/wanted15:43
ogra_i didnt insist using oem-config15:43
slangasekogra_: I wouldn't say "wait".  The language prompting is a good point, I don't remember this in the OOBE presentation last week - I'm checking now15:44
ogra_but if i write something it would be good if it could be used on the tablet too15:44
cjwatsonalso worth remembering that oem-config is a very old design and not necessarily worth hanging onto as the number of reused items decreases15:44
ogra_i just want to replace:15:45
ogra_ogra@chromebook:~/branches/livecd-rootfs-2.132$ ls live-build/ubuntu-touch/hooks/15:45
ogra_01-setup_user.chroot  02-add_user_to_groups.chroot  45-add-adming-group-nm.chroot  48-setup-env.chroot  49-setup-demo-assets.chroot  99-remove-documentation.chroot15:46
ogra_but if i invest work it would be good to do it based on a design we can re-use later15:46
ogra_like cjwatson said above, using caspers user setup etc15:46
slangaseksure15:48
ogra_(and it sadly needs to take all these android groups into account)15:49
slangasekfwiw, here's the current design for OOBE: https://docs.google.com/a/canonical.com/document/d/1JHFd_6mYdUTd0RpR-Sm7-WnX-06rY8r58K3Cz32mhJg/edit#15:49
slangasekandroid groups> doubtful, in the long term?15:50
ogra_as long as we use the android kernel and blobs i fear we have to15:50
slangasekkernels and blobs certainly shouldn't care about userspace groups15:51
infinityOne would hope not.15:51
ogra_it hardcodes  some GIDs that have access to certain services in the kernel iirc15:51
slangasekoh dear God15:51
ogra_its android :)15:51
slangasekyes15:51
slangasekI expect a minimum level of sanity from Android15:52
slangasekit's not a very high bar15:52
ogra_it definitely does it for the paranoid network stuff .... and i suspect there is a lot more15:52
ogra_(we switch off paranoid network, but thats the only modification in that  area)15:52
ogra_(.. other services, sensors etc will expect certain GIDs too)15:53
* ogra_ points at live-build/ubuntu-touch/hooks/02-add_user_to_groups.chroot ... in the livecd-rootfs source15:55
ogra_groupadd -g 1015 sdcard_rw15:55
ogra_....15:55
ogra_groupadd -g 1004 android_input15:56
ogra_...15:56
ogra_etc15:56
slangasekogra_: anyway, there's definitely a language selection step in the OOBE (see google doc).  You may or may not get to set a username.16:12
ogra_well, at least in the U1 config step you will get one16:13
ogra_yay16:15
ogra_dropping the hardcoded packagelist worked16:15
=== mmrazik is now known as mmrazik|afk
ogra_cjwatson, does http://paste.ubuntu.com/5642091/ look ok to you ?17:06
cjwatsonogra_: Should be fine.  A test for at least the first part would be nice (there's one you can copy and paste)17:10
ogra_cjwatson, like that http://paste.ubuntu.com/5642150/ ?17:21
ogra_(i'll need to switch that to zips once we can build them though ... )17:21
cjwatsonogra_: yep17:25
* ogra_ commits ... lets see if i now get non-empty output dirs :)17:25
=== Ursinha-afk is now known as Ursinha
antarusroyal rainbow!19:49
=== apachelogger is now known as Phonon
slangasekhmm, still an ubuntu zh_CN build for saucy?22:50

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!