/srv/irclogs.ubuntu.com/2014/04/08/#ubuntu-release.txt

=== fginther|away is now known as fginther
Mirvthe qml naming scheme presented by lisandro is sane, he discussed it on IRC before putting to mailing list04:12
=== fabo_ is now known as fabo
zequenceAnother last minute fix, bug 130421407:07
ubot2Launchpad bug 1304214 in ubuntustudio-lightdm-theme (Ubuntu) "[UIFe] New default wp for ubuntustudio-lightdm-theme" [Undecided,New] https://launchpad.net/bugs/130421407:08
seb128hey there08:59
seb128http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#unity-control-center08:59
seb128can somebody make sense of that?08:59
seb128"unity-control-center/arm64 unsatisfiable Depends: indicator-datetime "08:59
seb128"Not considered "08:59
seb128but that situation is not new...08:59
cjwatsonSomebody removed indicator-datetime from arm64?  Why just that arch I wonder?09:00
seb128it fails to build there09:00
seb128but that's not new09:00
cjwatsonOh, me apparently09:00
cjwatsonWell it is somewhat new, saucy had indicator-datetime/arm6409:00
infinityWhy would it be FTBFS on only arm64?09:00
seb128right, but saucy was not using url-dispatcher09:00
cjwatsonWe could probably get that back with a no-change of indicator-datetime though09:01
seb128infinity, it bubble up to some touch component not being available there09:01
seb128iir09:01
seb128iirc09:01
cjwatsonSince the reason it was removed no longer applies09:01
cjwatsonWonder if I can copy it back09:01
seb128oh, no09:01
infinityseb128: No, it's FTBFS in the testsuite, not a missing build-dep.09:01
seb128build failed on test issue09:01
cjwatsonOh, yeah, OK09:01
seb128infinity, sorry, my memory is probably from < qt5.2 times09:01
seb128should I retry the build?09:02
seb128in case it's a flacky test09:02
infinityCan't hurt, but probably won't help either.09:02
infinityRacey tests don't usually segfault.09:02
cjwatsonseb128: And it *is* new - unity-control-center in -proposed Depends: indicator-datetime, the one in release doesn't.09:02
seb128cjwatson, oh indeed, sorry09:03
seb128I confused that version with the one in unapproved09:03
* Laney tries a test build09:04
seb128cjwatson, infinity: thanks for the help, I guess the easiest way out is to get indicator-datetime to build on arm6409:04
infinityseb128: Certainly the preferred way out anyway.09:04
cjwatsonYeah, unity-control-center has enough rdeps that I'd rather not remove its binary.  The next (icky) fallback would probably be to make that dep arch-specific09:11
infinityOr disable the testsuite on arm64 with a massive XXX FIXME OH GOD LOLZ comment.09:12
infinityBut I'd definitely prefer someone investigating the crash a bit first.09:12
infinityAt least get some backtraces of the segv, it might be something one of us has seen before in other contexts.09:13
seb128infinity, right, I'm going to talk to charles about it later09:17
Laneydpkg-deb: building package `indicator-network' in `../indicator-network_0.5.1+14.04.20140318-0ubuntu1_arm64.deb'.09:17
infinityLaney: If only that was indicator-datetime.09:19
Laneyhaha09:19
LaneyI was shitting myself a bit09:19
LaneyI blame... something that's not me not paying attention09:19
LaneyI'd even done apt-get build-dep on the right package /o\09:24
dholbachcould somebody take another look at https://bugs.launchpad.net/ubuntu/+bug/1302619 https://bugs.launchpad.net/ubuntu/+source/qtcreator/+bug/1302620?09:48
ubot2Launchpad bug 1302619 in Ubuntu "[FFe] New package qtcreator-plugin-remotelinux " [Undecided,New]09:48
ubot2Launchpad bug 1302620 in qtcreator (Ubuntu) "[FFe] Remove remotelinux plugin and its dependencies from the QtC package" [Undecided,Incomplete]09:48
dholbachand bug 1303706 too please :)09:49
ubot2Launchpad bug 1303706 in libxkbcommon (Ubuntu) "FFe: new upstream version 0.4.1" [Undecided,New] https://launchpad.net/bugs/130370609:49
brendandhey, i have a couple of FFEs that i'm sheperding:10:10
brendandhttps://bugs.launchpad.net/ubuntu/+source/checkbox/+bug/130261510:10
ubot2Launchpad bug 1302615 in checkbox (Ubuntu) "[FFe] [UIFe] Checkbox GUI needs to be able to send test results to Launchpad" [Undecided,New]10:10
brendandhttps://bugs.launchpad.net/ubuntu/+source/checkbox/+bug/130384910:10
ubot2Launchpad bug 1303849 in checkbox (Ubuntu) "[FFe] The Checkbox UI needs a way to be customised" [Undecided,New]10:10
brendandis there a big backlog of FFEs?10:10
dholbachbrendand, https://bugs.launchpad.net/~ubuntu-release/ as 150 bugs - not sure if that's the best indication though10:21
brendanddholbach, can we em, 'encourage' someone to look at them?10:23
dholbachbrendand, I could imagine that a lot of people on the release team are very busy people :/10:25
infinityWe could encourage people to stop filing FFes seven months after feature freeze and a week and a half before release.10:26
dholbachinfinity, weeks?10:27
brendandinfinity, i know, it's quite late in the day, but we had to do a lot of groundwork to make this feature possible10:27
apw"if we did this by the book hours would seem like days"10:27
infinitydholbach: No, months, the hyperbole was intentional. :P10:28
dholbachok :)10:28
Laneybrendand: The idea is that if a feature's not ready then it gets in next time10:29
maclininfinity, the re-building  of ubuntu kylin does not take effect again. Could you help to check it ?10:29
infinitymaclin: Looks like it's in progress right now.10:30
brendandLaney, well yeah, but this is the LTS release. The feature in question is the ability for the system testing application (checkbox) to submit data to Launchpad's hardware db10:31
=== Adri2000 is now known as Guest44106
brendandLaney, so if it doesn't make it in, we won't have any of that data for the LTS release10:31
brendandLaney, unless we could get it through the SRU process10:32
infinitySRUing features is worse.10:32
infinitybrendand: I understand why everyone wants all their features polished and good to go for LTSes.  I just wish they'd realize they have almost two years to make that happen, and not leave it to the last two weeks to land them.10:32
maclininfinity, thanks! Is there a way for us to see wether the rebuilding is  right or not?10:32
infinitymaclin: Nope.10:33
maclinthanks, I get it:)10:33
brendandinfinity, i think that's oversimplifying it a bit. but i can totally understand that it's frustrating as a release team member to see everything build up in the last few weeks/days10:35
infinitybrendand: It's not oversimplifying at all.  We have a very well-known and rigid release schedule.  Yes, some things won't occur to you as being a killer feature until it's too late.  And some of those, we'll let in, but the expectation that we'll let all, or even most, of them in is just wrong.10:41
infinitybrendand: So, we'll look at this.  And we may deem it low risk and useful enough to be necessary, but asking people to develop to a schedule and accept that "late" might mean "next release" is just part of the time-based release bag.10:41
seb128infinity, imho there would be some value at accepting feature backports to LTS series through SRUs, for things that have been well tested/validated in newer series10:42
infinitybrendand: There are no unique snowflakes here.  If everyone kept uploading new features into the last week or two of release, we'd never be able to stabilise.10:43
infinityseb128: Sometimes.  And we occasionally do.  But that's a slipperly slope of breaking the promise of what a "stable" release means, too.10:43
infinityseb128: Stable UI, stable ABIs, stable APIs.  New features usually break one or all of those.10:44
seb128infinity, right10:44
brendandinfinity, if it gets looked at, we'll be happy. i'm blowing my own trumpet here, but it is very low risk, overall. the absolute worst that could happen is checkbox not working at all, but without it sending results to launchpad, it has little overall value anyway10:44
infinity(FWIW, I just self-rejected an FFe of my own after some investigation and deciding I was too late to effectively test the change, so I'm practicing what I preach)10:45
infinitybrendand: Point taken on the general uselessness of the package without this feature working, then.  One could probably call that a bugfix. :P10:46
brendandinfinity, then we don't need an FFe! \o/10:47
seb128could somebody review/accept unity-control-center from the queue?10:47
seb128it's a one commit to mark string translatable10:47
LaneyAre all of these https://launchpad.net/ubuntu/+source/checkbox versions of checkbox useless then?10:48
seb128getting it through would let me get a silo back to land the indicator-datetime buildfix10:48
Laneyseb128: looking10:48
seb128Laney, thanks10:48
brendandLaney, all of them? no - the ones before trusty had this feature10:49
brendandLaney, currently in trusty it doesn't10:49
brendandLaney, the thing is we rebuilt checkbox10:49
brendandLaney, rewrote it really10:49
infinitybrendand: Can you attach some debdiffs to these FFes?10:50
Laneyseb128: is this kind of translation normal?10:50
brendandinfinity, debdiffs? sure. the lp:ubuntu/checkbox MR is there though10:51
seb128Laney, "kind of translation"?10:51
Laneydatetime format strings10:51
seb128Laney, that's a backport of https://git.gnome.org/browse/gnome-control-center/commit/panels/user-accounts/um-history-dialog.c?id=aa3af401147c9550bc19d14b5cdaf5588083f7c110:51
LaneyI see10:52
seb128Laney, but yeah, https://developer.gnome.org/glib/stable/glib-I18N.html#C-:CAPS10:52
Laneyyeah I know C_, was just wondering if using it on format strings like that is a done thing10:55
seb128Laney, well, that just returns a string, you could put a strdup() or something there as well10:56
seb128Laney, in any case I'm running that version, works fine (and upstream shipped it in a stable release/didn't do followup commits)10:57
brendandinfinity, looks like there are none: http://paste.ubuntu.com/7221079/10:58
brendandinfinity, i can mention that in the ffe's10:58
infinitybrendand: The source, not the debs.10:58
infinitybrendand: Though I'm actually really curious now, since the UIFe seems to imply there should be some conffiles or something new in the packages. :)10:59
infinityAnyhow, I'm going to back away from the laptop, drug myself, and be back tomorrow.10:59
Laneyseb128: done, doubt anyone will translate that before release but you never know11:04
seb128Laney, I uploaded an updated template to launchpad last week so translators already did some work ;-)11:04
Laneymanually?11:05
seb128yes11:05
seb128run intltool-update in my build tree and uploaded11:05
seb128don't worry, it's a documented workflow and not the first time I use it ;-)11:06
Laneyheh11:09
Laneyis there a problem with extracting from uploads?11:09
seb128Laney, no, it's just that if I had waited for the mp to be review/approved/CI trained/unapproved accepted/landed/imported we would have had the new strings available on launchpad this afternoon11:14
seb128Laney, where my manual update meant translators had an head start on it during the w.e ;-)11:14
LaneyIf only launchpad had a way of making translations available from the VCS :-)11:17
seb128hehe11:18
=== pete-woods is now known as pete-woods-lunch
didrocksubuntu-ui-toolkit uploaded: this is a revert to have gallery-app passing again tests. We want to kick an image soon, can anyone from release team consider it? Thanks ^11:43
Laneyseems queuebot hasn't made it back11:44
didrocksyeah11:45
didrockshe's gone for long ;)11:45
Laneydidrocks: ok, done11:51
didrocksLaney: thanks! there is an unity8 coming as well11:51
didrocksLaney: which was linked to that change11:52
didrocks(same, revert of one commit)11:52
=== kitterma is now known as ScottK
didrocksLaney: unity8 7.85+14.04.20140404.is.7.85+14.04.20140403.1-0ubuntu1 coming to a queue near you :)11:54
xnoxLaney: imho it's a bug fix, but also change in the UI, can you peak at bug #1304363 the proposed diff is "s/1/0/" on left,right & bottom border widths.11:55
ubot2Launchpad bug 1304363 in ubuntu-themes (Ubuntu Trusty) "[UIFe] enable borderless windows under metacity (e.g. for ubiquity)" [High,Confirmed] https://launchpad.net/bugs/130436311:55
xnoxthis would make ubiquity look sexy.11:55
Laneyxnox: Check with docs for screenshots11:55
Laney(didn't load the bug, maybe you did that)11:55
Laney(also going to lunch now :P)11:56
Laneyxnox: And get larsu to review that11:57
* Laney biab11:57
xnoxLaney: but the screenshot is soooo pretty =))))11:57
didrocksactually, unity8 was autoaccepted11:58
didrocksLaney: but we'll need someone to bump the fauxpackage if possible11:58
xnoxLaney: larsu approved =)12:02
jamespageDaviey, fyi just updating ceph to 0.79 for testing prior to upload12:25
jamespageI'll request an ack once I'm happy its OK12:25
sil2100Dear release team! Sorry to poke once again about things related to this, but could we ask for pushing platform-api forward from the UNAPPROVED queue? Thank you!12:45
cjwatsonlooking12:46
cjwatsonlack of queuebot is slowing us down :)12:47
cjwatsonsil2100: done12:48
=== pete-woods-lunch is now known as pete-woods
sil2100cjwatson: thank you o/12:56
sil2100:)12:56
Laneyxnox: did you test metacity itself?13:25
Laneyalso, please inform docs team13:25
Laneyafter that, should be fine13:25
Laneydidrocks: did it get done?13:26
jamespagecould someone from the release team please review bug 129509313:36
ubot2Launchpad bug 1295093 in docker.io (Ubuntu) "[FFe] Sync docker.io 0.9.0 from Debian testing" [High,New] https://launchpad.net/bugs/129509313:36
jamespageits been there for a while with no comment whatsoever13:36
jamespage0.9.1 is now in unstable....13:36
jamespage(I'll look at that now)13:38
didrocksLaney: not sure if you have done anything, but unity8 is a valid candidate now :)14:12
xnoxLaney: hm, not sure i need to inform docs team, as we don't have ubiquity screenshots in docs, we only have them on ubuntu.com website. And i have a task to pass updated screenshots for the release to the website team already.14:19
xnoxwill double check if that has changed.14:19
LaneyUsually it's polite to do so14:20
LaneyI'd just ask them instead of trying to figure it out yourself14:20
LaneyYou can ask GunnarHj14:20
stgraberoh, reminds me I probably should do a last minute ubiquity slideshow upload14:23
stgraber(the usual last minute translation update)14:23
seb128Laney, indicator-datetime in the unapproved queue14:45
Laneysomeone else better review that one :-)14:45
didrocks:p14:45
seb128could somebody review indicator-datetime in the queue?15:02
seb128it's a one liner (init a variable to null) that fixes the arm64 ftbfs15:02
marruslHi all.  Can someone look into nvidia-graphics-drivers-331 for precise ?   It seems like it's stuck in the "New" queue.15:03
cjwatsonseb128: done15:05
seb128cjwatson, thanks15:05
jamespageDaviey, if you have time - https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/129509315:11
ubot2Launchpad bug 1295093 in docker.io (Ubuntu) "[FFe] Merge docker.io 0.9.1 from Debian unstable" [High,New]15:11
jamespageor any other release team members :-)15:11
Davieyjamespage, i dont feel able to look closely at that issue right now.15:26
bdrung_workhi, may i upload the new source package versiontools to fix the build failure of gevent-socketio?15:37
jamespagestgraber, would you have time to review https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1295093 ?16:03
ubot2Launchpad bug 1295093 in docker.io (Ubuntu Trusty) "[FFe] Merge docker.io 0.9.1 from Debian unstable" [High,New]16:03
stgraberjamespage: not at the moment, no16:06
jamespageScottK: I need a review of https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1295093 - its been kicking around for a while16:16
ubot2Launchpad bug 1295093 in docker.io (Ubuntu Trusty) "[FFe] Merge docker.io 0.9.1 from Debian unstable" [High,New]16:16
jamespagewould you have time to review?16:16
jamespageScottK, I spoke with the Debian maintainer and he's preparing an upload including the required apparmor patch so we can just sync it over16:17
zulCan someone accept qemu and libvirt it has a regression that affects virtio devices16:56
=== roadmr is now known as roadmr_afk
cjwatsonzul: done17:08
zulcjwatson:  thanks17:09
tjaaltoncould someone ack https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1303706 so I can upload it. RAOF tested it as reported on mir-devel@17:09
ubot2Launchpad bug 1303706 in libxkbcommon (Ubuntu) "FFe: new upstream version 0.4.1" [Undecided,New]17:09
robrucjwatson, oops, I goofed up the bamf upload. can you accept the 0408 version over the 0407.1 that just got into proposed?17:31
cjwatsonrobru: sure, one sec17:39
robrucjwatson, thanks17:40
cjwatsondone17:40
robrucjwatson, sweeet, thanks again17:43
roaksoaxcan someome please take care of 'maas' which is in the approved queue? It has 3 important fixes! Thank you!17:44
=== Guest44106 is now known as Adri2000
=== roadmr_afk is now known as roadmr
rsalvetislangasek: updated qtbase-opensource-src to make sure all the symbols are up-to-date per arch18:37
rsalvetislangasek: before we actually propose the changes needed for the gl x gles work18:38
rsalvetidoing a bunch of rebuilds now in a ppa to see if what you proposed in that thread is enough (which should be, unless we get some other issues)18:38
marruslHi folks, can someone take a look at nvidia-graphics-drivers-331-updates in the precise New queue?  It's needed for compatibility with the trusty backport kernel.18:42
chrisccoulsonhi, can someone please accept that flash package? ^18:58
jdstrandchrisccoulson: oh, I asked you to come here, but I forgot this was for partner19:06
jdstrandI'll do it19:06
jdstrandchrisccoulson: for some reason I was thinking it was flashplugin-nonfree19:06
chrisccoulsonah, thanks :)19:06
chrisccoulsonjdstrand, just uploading the others now as well19:07
jdstrandchrisccoulson: when you update flashpugin-nonfree for trusty, do ask here though19:07
jdstrandchrisccoulson: ok, I accepted all the partner packages19:16
chrisccoulsonjdstrand, thanks19:16
slangasekrsalveti: great, glad to hear you're making progress on the glesing.  Can you give me a pointer to the ppa, so I can follow along?20:37
chrisccoulsoncould someone please approve that? ^^ :)20:38
rsalvetislangasek: did a few tests with local builds and I'm now starting to push stuff to https://launchpad.net/~canonical-arm-dev/+archive/ppa/+packages, but will ping you back later today with more results20:38
rsalvetislangasek: will test initially with a different src package providing just the packages we care (gui, opengles, etc)20:38
* slangasek nods20:39
rsalvetithat can later be integrated in the same src package, but it needs a bit of rework and too close to the release to work on that now20:39
xnoxLaney: got an ack from docs team. So all good to silo that baby up tomorrow \o/20:56
utlemmingstgraber: we need to add a whole bunch more targets for EC2 testing....can we change HVM to "HVM EBS", with one for each region, and then add "HVM Instance" with one for each region?22:03
stgraberI'm sure we can, lots of manual changes though (and not really worth scripting)...22:06
xnoxslangasek: is it a requirement for newly introduced upstart jobs in trusty to be precise compatible? (those that e.g. replace init.d scripts) the upgrade story is not nice, init.d script is stopped upon upgrade and not started since upstart job is rejected, thus one must reboot.22:08
xnoxi guess the question is, is it support to run precise upstart with trusty userspace =)22:08
xnoxs/support/supported/22:08
xnox?22:08
slangasekxnox: I don't think this question had ever been brought up explicitly; it's certainly a requirement that "upgrades work", but I'm not sure I understand the implications here - are you finding upstart jobs using particular features that aren't precise-compatible?22:09
xnoxslangasek: bug #127278822:09
ubot2Launchpad bug 1272788 in php5 (Ubuntu) "php5-fpm upstart job is not compatible with precise upstart" [High,Triaged] https://launchpad.net/bugs/127278822:09
xnoxslangasek: due to "reload signal USR2", my cunning plan is to ship .override file with "reload signal USR2" -> precise will ignore .override, but trusty will use the .override. Thus compatible with both releases, without compromise on trusty.22:10
slangasekxnox: also, is a versioned dependency on upstart sufficient here?  Since running services in chroots is not a common use case, we generally speaking only have to worry about the running init when installing packages in the "host" environment, and versioned dep is sufficient to get upstart restarted22:11
slangasekoverride> yuck :)22:11
xnoxslangasek: alternatively maintainer scripts should fall back to initd script.22:11
slangasekalso yuck!22:11
slangasekwhy not add a versioned dependency?22:11
xnoxslangasek: versioned dep does not help. so the bug is after upgrade and util reboot.22:12
slangasekxnox: how does it not help?  upstart is upgraded; it re-execs22:12
slangasekand then the new syntax is supported22:12
apwheh22:13
apwerp22:13
xnoxslangasek: i thought precise upstart can't do stateful re-exec and hence it only re-execs on shutdown....22:13
slangasekoh man22:13
slangasekyou could be right22:13
slangasekwas that only two years ago?22:13
xnoxslangasek: it was during my time, and i've joined after precise got released.22:14
slangasekyeah, maintainer script in ge 1.9 || 1.8-ubuntu-full-serialization22:14
slangasekso you're right, versioned dep is no good22:14
xnoxslangasek: at first oakland keybuk was briefing myself and jodh on how to serialise upstart.22:14
slangasekxnox: yes, I believe you - I'm just old, and so my perception of time is lacking ;)22:14
xnoxslangasek: hence the question of how to support this case, if at all....22:15
xnoxslangasek: i guess we should be falling back to init.d script if the job is unknown to upstart (even though it's present on disk)22:16
slangasekxnox: that means we would be falling back to init.d in the case of bugs in the upstart job, too; maybe not desirable22:18
slangasekxnox: you could both 'check if job is known' and 'use init-checkconf on disk to parse the file', and only fall back to the init script if the current upstart on disk likes it but the running upstart doesn't22:19
infinityQuick, backport stateful re-exec to precise?22:19
infinityslangasek: That would be a workable (ish) solution for this one package, but that doesn't really scale if other packages are also precise-incompatible.22:20
xnoxslangasek: but init-checkconf in precise, no-worky without X..... (we fixed that in trusty i believe)22:20
slangasekinfinity: eh, you would put it in invoke-rc.d.22:20
infinityNot that I like the obvious alternative (tell people they must reboot or their services won't be running).22:20
xnoxbecause dbus =022:20
slangasekxnox: but short circuit behavior saves us, no?22:21
xnoxslangasek: what do you mean by "short circuit" ? =)22:21
slangasekxnox: if $job_is_not_known && init-checkconf $myjob; then sysvinit_fallback=true; fi22:22
slangasekxnox: so the only case in which you're even trying to invoke init-checkconf is if the job is unknown in the first place22:22
slangasek*and*, you really care about getting the answer from the *new* init-checkconf anyway, so you'd have a versioned dep on upstart for those packages where it matters22:23
xnoxslangasek: i care about servers only. we are in the state where init-checkconf will not work. init-checkconf might be precise one - in which case it needs dbus-launch/X to work.22:23
xnoxslangasek: init-checkconf from trusty needs trusty pid1 to be able to use user-session to check the job.22:24
slangasekxnox: oh, then scrap the entire idea.  I assumed init-checkconf worked without talking to pid122:24
slangasekif it doesn't, then it doesn't provide any additional info22:24
slangasekin which case, "if $job_is_not_known" isn't perfect, but probably the closest we can get22:25
xnoxwait, when init-checkconf is trusty one, /sbin/init is also trusty so yeah that will tell you that job is fine, if you'd re-execed.22:25
xnoxand how would this "sysvinit_fallback=true" work? given that init.d scripts per policy would bail on us and so would the $ service command.22:26
* xnox goes to check how many jobs are affected22:27
slangasekhah, sigh22:29
slangasekomg, xnox is sending my mail client into a busy loop22:29
xnoxslangasek: so far i see it's just that one php job. I might opt in for e.g. not stopping it on upgrade from precise -> trusty?!22:30
slangasekxnox: or just dropping the use of 'reload'?22:31
* xnox will run full init-checkconf on all jobs from trusty on a precise box.22:31
xnoxslangasek: or that.22:31
JackYuhi release team, who could help to take a look at FFe bug #1293299?23:33
ubot2Launchpad bug 1293299 in Ubuntu Kylin "[FFE]upload ubuntu-kylin-software-center into archive" [High,Confirmed] https://launchpad.net/bugs/129329923:33
slangasekJackYu: hi - it's on my list to look at this afternoon23:48
slangasekJackYu: FYI, FFe bugs should be left in state 'New', not 'Confirmed' so that the release team sees them23:49
JackYuslangasek, sure, thanks:)23:51
slangasekrsalveti: how'd the rebuild go?  FWIW I don't seem to have access to https://launchpad.net/~canonical-arm-dev/+archive/ppa/+packages23:56
slangasekwould be nice to have these builds in a public ppa... :)23:56
rsalvetislangasek: yeah, need to get a public ppa with armhf23:57
rsalvetislangasek: but anyway, will copy them over once the build is done23:57
slangasekok23:57
rsalvetifinishing qtbase, next is qtdeclarative, and building the gles versions in parallel23:57
rsalvetibut it takes time23:57
rsalvetiqtbase takes almost 4 hours to build on armhf23:57

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