/srv/irclogs.ubuntu.com/2013/03/29/#ubuntu-unity.txt

=== tvoss|otp is now known as tvoss|easter
didrockshey sil2100 ;) good work! for yesterday08:10
sil2100didrocks: hi! Thanks, wouldn't do it without cyphermox ;)08:36
didrocks:)08:36
=== andyrock is now known as andyrock|out
=== andyrock|out is now known as andyrock
=== mmrazik is now known as mmrazik|lunch
=== mmrazik|lunch is now known as mmrazik
=== alan_g is now known as alan_g|lunch
* mterry is surprised to see that daily builds actually landed last night for the unity stack. Our luck day!13:11
didrocksmterry: I had to work on it :/13:24
didrocksmterry: UTAH failed13:24
mterrydidrocks, ah, well, it was a nice few minutes of thinking things worked13:26
didrocks:)13:26
didrocksmterry: btw, I'm still working on having the 2 releases in parallel13:26
didrocksmterry: so head is still disabled13:26
mterrydidrocks, and it seems that Head correctly didn't run last night?  yup13:26
didrocks(commit counting and so on)13:26
didrocksmterry: it correctly didn't run rather :p13:26
didrocksmterry: also, even if I reenable it, remember that all the branches are disabled ;)13:27
didrocksuntil you https://wiki.ubuntu.com/DailyRelease/MovingNewRelease#Diverging_.22trunk.22_and_a_.22maintenance.22_branch13:27
didrocksin accordance with upstream13:27
kgunn didrocks ...i'm building unity/phablet...hadn't had a problem...but, now when i run setup (for updates) its saying temp failure to resolve 'ports.ubuntu.com'13:40
didrockskgunn: hum, what is setup? :-)13:40
kgunndidrocks: setup is just an option on the build to update dependencies on the device13:41
kgunn(or that is one step anyway)13:41
kgunndidrocks: and i shouldn't say build...its actually run_on_device script13:41
didrockskgunn: do you have the script somewhere? that would help me know what this is trying to do13:43
kgunndidrocks: http://bazaar.launchpad.net/~unity-team/unity/phablet/view/head:/run_on_device13:44
kgunni think its this line exec_with_ssh $SUDO apt-get -y install build-essential rsync bzr ccache13:44
kgunndidrocks: normally i would suspect i did something stupid :)13:45
didrockskgunn: I don't think you are the guilty, ports.ubuntu.com is available here13:45
didrockskgunn: but looking at the script I would do some modifications13:46
didrockslike     exec_with_ssh $SUDO apt-get -y install build-essential rsync bzr ccache13:46
didrocksavec the apt-get update line13:46
didrocksfor instance13:46
didrockskgunn: can you do that and relaunch?13:46
kgunndidrocks: i actually thot maybe it was the script....so i opened shell on the device (ubuntu_chroot shell)13:46
kgunndidrocks: did apt-get update13:47
kgunndidrocks: and it still said "couldn't resolve"13:47
didrocksduring the apt-get update?13:47
kgunndidrocks: right13:47
didrocksdo you have network on your device?13:47
didrockslike if you ping google?13:47
kgunndidrocks: let me check that...13:47
kgunndidrocks: should've done that prior...13:48
kgunn:)13:48
didrocksno worry ;)13:48
didrocksbut yeah, ports.ubuntu.com is working, the archives are accessible13:48
kgunndidrocks: dammit...thing had network a minute ago...sorry13:48
kgunn:)13:48
didrocksno worry at all ;)13:48
kgunndidrocks: couldn't see forest for the trees13:49
didrockskgunn: well, another eye generally help for that! :)13:49
kgunndidrocks: and so much for my overpriced verizon fios router !13:49
kgunnflakey piece of junk13:50
didrockskgunn: sometimes, the "boxes" we have in France are a blessing TBH. No need for another router, pretty reliable… cheap Internet13:50
didrocksat least this thing is positive :)13:50
kgunndidrocks: good ol' americans...figure out how to charge a premium for something that "sort of works" :)13:51
didrockskgunn: how to say without being rude that I'm not surprized? :)13:52
kgunndidrocks: :)13:53
ollididrocks, I wouldn't be worried about _sounding_ rude... seems impossible for French13:55
mterrydidrocks, let's say a package has typical autopilot tests in tests/autopilot.  What do you expect to see in that second-to-last column on that touch spreadsheet13:55
didrocksolli: tsssss, how ironic after the "excuse my French" and other similar expressions I'm hearing ;)13:56
ollinever made sense to me13:57
olli;)13:57
didrocksheh ;)13:57
didrocksmterry: the package name shipping those autopilot tests (so <foo>-autopilot for instance), all the required packages to run it (maybe a manual run on a guest session for ensuring it's working is best) and the command that needs to be run to start them13:57
didrocksmterry: making sense?13:57
didrockssil2100: FYI, everything is now published13:59
didrockssil2100: I just promoted in raring-proposed appmenu-qt5 and dbusmenus-qt5 to main13:59
didrocks(as they are installed by default)13:59
mterrydidrocks, yeah13:59
mmrazikdidrocks: me and fginther are wondering if this is good to go: https://code.launchpad.net/~mrazik/cupstream2distro-config/webcred/+merge/15554114:01
didrocksmmrazik: should check with kenvandine, and upstream if they agree with moving their branches now14:02
=== alan_g|lunch is now known as alan_g
didrocksmmrazik: you have duplicated btw14:02
didrockslike target_branch: lp:libaccounts-qt14:03
didrocksin raring14:03
didrockslibaccounts-qt:14:03
didrocksin head14:03
didrocksoh14:03
didrockssorry, it's in to_transition14:03
didrocksto yeah, excellent, just ensure with kenvandine and upstream that their branches moved :)14:03
mmrazikdidrocks: do we actually need to check something with upstream? Can we just move stuff from to_transition as upstream creats the branches?14:03
kenvandineso upstream needs to create branches for raring right?14:03
didrocksmmrazik: I mean, checking for the /13.04 branches14:04
mmrazikdidrocks: but can't that be done independently? I.e. the current merge proposal should just work or not?14:04
mmrazikand as soon as we have 13_04 we would move stuff out of to_transition14:04
kenvandinedidrocks, but we don't have to have those branches...14:04
didrockslet me rephrase:14:04
didrockstarget_branch: lp:account-plugins/13.0414:04
didrocksfor instance14:04
kenvandineuntil upstream needs them for some reason14:04
didrocksyou need to ensure upstream wants and has a lp:account-plugins/13.0414:04
didrocksright14:04
didrocksthat's what I mean :)14:05
didrocksfginther: mmrazik:  ^14:05
kenvandineok, so we don't need to create those branches for everyone project :)14:05
kenvandinejust as needed14:05
* mmrazik still confused14:05
mmrazikdo I need to do anything?14:05
* kenvandine is too14:05
kenvandinei think14:05
* fginther confused +114:06
mmrazikso my idea with that MP was the following:14:06
kenvandineupstream has created lp:account-plugins/13.0414:06
mmrazik-everything from head/webcred.cfg will be ignored except account-plugins14:06
kenvandinebut not for others yet, because they haven't needed to14:06
mmrazikwe will have autolanding jobs for lp:account-plugins14:06
didrocksso, if upstream has created lp:account-plugins/13.04, fine14:06
didrocksthe MP is good14:06
didrocksthat what just the thing I wanted to ensure ^14:06
kenvandineok14:06
mmrazik- evreything in raring/webcred.cfg will be used to generate autolanding jobs14:07
* kenvandine isn't confused anymore14:07
kenvandine:)14:07
didrocksmmrazik: so yeah, you can go ahead :)14:07
mmrazikfor account-plugins an autolanding job for lp:account-plugins/13.04 will be create14:07
didrocksright :)14:07
mmrazikdidrocks: oh14:07
mmrazikdidrocks: understood14:07
kenvandinewe just won't autoland anything else for raring, since they don't have 13.04 branches14:07
kenvandinetrunk will go to head14:07
didrockskenvandine: the elements have daily_release: False14:07
didrocksso they won't autoland14:07
kenvandineright14:07
kenvandinein this case14:07
kenvandinei was thinking bigger picture :)14:08
mmrazikuh oh14:08
didrocksapart from signon-keyring-extension: of course ;)14:08
mmrazikwe are overloading the "autoland" term14:08
kenvandinemmrazik, yes.... yes we are14:08
didrocksmmrazik: that's part of the issue for quite some months :)14:08
didrockshence I'm talking about14:08
mmrazikshall we talk about about "autoland" and "upstream merge"?14:08
didrocks"upstream merge"14:08
mmrazikack14:08
didrocksand "daily release"14:08
mmrazikok14:08
kenvandinewe need a new term :)14:08
didrockskenvandine: let's avoid the confusing term :-)14:09
mmrazikdidrocks: so I'll top approve that merge proposal and will generate the jobs14:09
kenvandineautomerge and autopackage?14:09
mmrazikfginther: ^^14:09
didrocksmmrazik: perfect ;)14:09
fginthermmrazik, ack14:09
didrockskenvandine: that works too14:09
kenvandineand stop using the term autoland complete14:09
kenvandine+ly14:09
didrocks+114:09
kenvandineso if we here someone use the term, we know they are confused :)14:09
didrockskenvandine: so you don't really need to redeploy, as all the changes are either in to_transition or daily_release = False14:10
didrocks(for autopackage)14:10
mterrydidrocks, libhybris isn't in the touch blueprint.  Are we upstream for that?14:10
kenvandinedidrocks, and what do you mean by redeploy?14:10
kenvandine:)14:10
kenvandinewe need a dictionary of terms here :)14:10
didrocksmterry: it's on that one: https://blueprints.launchpad.net/ubuntu/+spec/client-1303-ubuntu-touch-porting14:10
didrocksmterry: because yeah, we are not upstream for it14:10
didrockskenvandine: did you read my wiki page I pointed the other day? :)14:11
didrocksthere are even links!14:11
=== jono is now known as Guest21379
kenvandineyes14:11
didrockskenvandine: https://wiki.ubuntu.com/DailyRelease/MovingNewRelease#Deploy_both_stacks_you_modified14:11
mterrydidrocks, OK, so I'll just put that in our PPA then14:11
didrocksmterry: yep ;)14:12
sil2100\o/14:17
kenvandinedidrocks, since the platform stack isn't deployed yet, i am just updating the stack in head removing the to_transition, and disabling it in raring until they have a branch for raring14:39
kenvandinedidrocks, does that make sense?14:39
didrockskenvandine: we can still have daily release for it in raring, you think? or it will never happen?14:45
kenvandinemaybe14:45
kenvandinei need to talk to them about maintaining a bug fix branch for raring14:45
didrocksso, keep it like that for now, and let's see once we are sure :)14:45
kenvandinei am sure they are going to want fixes to land in raring14:46
didrockswe can deploy it after the fact14:46
kenvandineok... so keep it for raring and go ahead and deploy?14:46
didrockskenvandine: hum, why do you want to deploy it until it's ready?14:46
kenvandinei am anxious to get it deployed :)14:47
didrocksI don't get it :)14:47
didrocksif it's not ready for daily release14:47
kenvandinei figured letting it release to next would be a good start14:47
kenvandinenot to raring :)14:47
didrocksbut trunk is ready?14:47
didrocksbootstrapped, etc?14:47
kenvandineit just needs the bootstrap commit14:47
didrockswe have integration tests running?14:47
kenvandinewhich i wanted to do today14:47
kenvandineyes14:47
didrocksok, fine by me to go that in head then14:48
didrockskenvandine: so bzr rm it on raring14:48
kenvandineok, i figured better to start with head and not enable daily release on raring14:48
kenvandineok14:48
didrocksto avoid catastrophees ;)14:48
kenvandineindeed14:48
didrocksok14:48
didrocksFYI14:48
didrocks#schedule: 0 3 * * 1-514:48
didrocksit's disabled by default14:48
didrockskenvandine: I'm still working on cupstream2distro to support parallel release14:48
didrocks(in term of commits collect)14:49
didrocksterms*14:49
didrockskenvandine: so you won't have it yet, but soon, I hope to finish on Monday14:49
kenvandineok14:50
=== mmrazik is now known as mmrazik|afk
=== alan_g is now known as alan_g|tea
didrocksmterry: btw, I've fixed and tested a bug (due to multiple manual uploads) that prevented unity-asset-pool to release its last commit. It was a new icon for 100scopes, do as you wish (it's not used, so technically doesn't break UIF)16:08
didrocksmterry: just be prepare if infinity is going to close the archive as he told on the email in 12 hours that the manual review otherwise will reject it :)16:09
=== alan_g|tea is now known as alan_g
mterrydidrocks, awesome.  You mean it will land next time unity stack runs?16:17
didrocksmterry: yep, so either you can do it today, or you can see what they will tell if infinity is going to freeze the archive :)16:18
mterrydidrocks, might as well try today16:18
didrocksgreat ;)16:18
mterrydidrocks, I thought freeze was yesterday though16:18
didrocksmterry: read ubuntu-devel (ML)16:19
mterrydidrocks, I hate reading16:19
didrocksmterry: but but… you read my "read ubuntu-devel (ML)"16:19
didrocksmterry: I'm puzzled, afraid and lost now :p16:19
mterrydidrocks, i actually don't see it16:20
mterrywill check archive16:20
didrocksoh16:21
didrocksit's in ubuntu-release ML16:21
didrocksmterry: sorry ^16:21
didrocks(they just end up in the same folder)16:21
mterrysure16:23
=== mmrazik|afk is now known as mmrazik
=== mmrazik is now known as mmrazik|afk
slangasekhi, can anyone here tell me how I can run the tests in the compiz package?17:59
slangasek(trying to fix a bug I filed a while back, and wanting to do it right with a new test case)17:59
slangasekthe package has a build-dep on libxorg-gtest-dev, but seems to be completely unused... debian/rules overrides the dh_auto_test target, but dh_auto_test doesn't do anything anyway...18:03
bschaeferslangasek, in your build dir for compiz, you should be able to do make test18:03
slangasekbschaefer: hmm; why is this not being done by default in the package build?  Also, there seem to be some bits missing wrt gtest support (-DCOMPIZ_BUILD_TESTING=OFF, google-mock not a build-dependency), is this relevant?18:11
slangasekright, so it seems that after twiddling both of those things, the tests are building18:12
slangasekbut I wonder why that's off by default18:12
bschaeferslangasek, hmm im not sure why its turned off by default, smspillaz or didrocks would be ones that would have a better answer for that :)18:13
slangasekok18:13
=== bschaefer_ is now known as bschaefer

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