=== hggdh_ is now known as hggdh === _salem is now known as salem_ === salem_ is now known as _salem [07:04] good morning [07:37] yep [07:37] Yeah, it [07:37] 's back [07:40] Noskcaj, http://smartboyhw.tk/wordpress_smartboyhw/?p=76 [07:41] i literally just finished reading that [07:41] Noskcaj, LOL [07:42] you spammed my twitter feed. i follow three people who auto-post planet ubuntu, everything on my feed said your name [07:43] Noskcaj, XD. [07:43] That's awesome! XD [07:50] Good Morning :-) [07:52] evening DanChapman [07:56] smartboyhw, one thing to add to out list of testdrive bugs: You can't install edubuntu or studio due to the tiny disk sizes available [09:48] Noskcaj, yeah, the "Other..." selection DOESN"T WORK. [11:16] jibel: FYI, I updated Debian's autopkgtest git to the most recent Debian version, and applied all our patches [11:16] http://anonscm.debian.org/gitweb/?p=autopkgtest/autopkgtest.git [11:17] jibel: I'll upload today, so we can sync tomorrow; that should also fix this nasty "unicode coercion" exception that we've been seeing occasionally (that was the NMU which we didn't merge yet) [11:17] jibel: do you still have anything else for this? [11:22] pitti, ah awesome! I've no additional fix ready. There is this empty 'Depends' for which I never received an answer how it should behave and the traceback on timeout because stdin is undefined, but I couldn't figure out what the right fix is. === forestpiskie is now known as Guest96363 [13:03] DanChapman: congrats to your ubiquity autopilot test! === _salem is now known as salem_ [13:10] pitti, thanks. It's been good fun doing it. :-) [13:11] DanChapman: I landed some improvements upstream today, should hit the distro tomorrow [13:11] DanChapman: if you have anything which felt like a bug and you needed to work around, please file bugs [13:12] DanChapman: in particular, I landed the direct access to GtkBuilder IDs, so that it's much easier to find particular widgets [13:17] pitti, great sounds cool. Brilliant that should make things a bit easier. I did come across a couple of probs on friday but I will go back and test it before i file a bug. as I saw there was an autopilot-gtk update yesterday or i might have been doing it wrong. ;-) [13:21] DanChapman: there was one this morning, but that doesn't have a functional change yet (it just adds a test suite) [13:21] DanChapman: tomorrow's autolanding will have the nice stuff [13:26] pitti, cool will take a look at it tomorrow then :-). On a different point would it be possible to get the properties of the cursor with autopilot. [13:31] pitti, it would be nice to be able to wait on a 'busy' cursor for long/busy processes where the Eventually matcher doesn't quite suit the situation [13:31] DanChapman: that sounds more like autopilot itself, but why doesn't Eventually work? I thought you could specify custom timeouts? === francisco is now known as Guest25330 [14:19] pitti, DanChapman I assume he's wanting to "wait" for something like the install to finish which could be 20 mins :-) That's a LONG timeout [14:19] balloons, hey, check out your interview! [14:21] phillw, ping [14:22] smartboyhw, I spy my famous your, you're issue :-) [14:23] balloons, heh [14:23] smartboyhw, " More or less your “sailing” with a kite" should be " More or less you are “sailing” with a kite" [14:24] pitti, sorry had phone call. My problem is probably specific to ubiquity. I am trying to find a way to travel the wait between clicking 'install now' and the next page loading. If I use the timeout then I need to be sure that it 'should' have created the partitions etc in a specified time. But I can't as its different depending on arch. xnox suggested waiting on the busy cursor, hence my question. :-) [14:24] balloons, updated http://smartboyhw.tk/wordpress_smartboyhw/?p=76 [14:24] balloons, hey :-) [14:24] * balloons waves to DanChapman [14:31] ahhh its been staring me in the face all this time :-) the progress dots on the bottom.... that should do it. [14:34] DanChapman, I thought we mentioned this? It's actually 5 objects..so if you need all 5 to fill to 100% [14:34] if I remember correctly :-) [14:37] balloons, did we? :-) I only remember discussing the final progress bars after the user info page. I may be wrong though ;-) [14:39] DanChapman, hard to say lol.. But it's not a bad idea :-) [14:41] DanChapman, can you please help test Kubuntu amd64 alpha1? [14:42] smartboyhw, as you asked so nicely i will start a vm up now :-) [14:42] DanChapman, heh! [14:46] DanChapman, you want to wait between the steps "partitioning" and "where are you"? Can't you check the state of the button "Continue" and wait until it's enabled? [14:47] IIRC this "forward" button is disabled when the users click on it and re-enabled at the beginning of each step [14:49] jibel, thanks I will give that a go that will probably work better :-) [14:52] DanChapman, maybe that won't work for every step, because for example, the last step requires valid input from the user but you can check the state of the button "back" instead of "forward" === om26er is now known as om26er|away [15:01] jibel, ok great thanks for that :-) , I will include it for each page to check that it has the correct behaviour. [15:15] DanChapman, please do remember to report your test results to the ISO QA Tracker. [15:31] smartboyhw: pong [15:32] phillw, any time to help me review http://people.ubuntu.com/~smartboyhw/Ubuntu_ISO_Testing_CLASSROOM.pdf ? [15:34] can you email it to me, I have also been asked to review noskaj's upcoming. Two hours of testing remain, so I'm just filling in gaps in our tests. [15:34] phillw, email? It's publicly available on that link. [15:35] to remind me! [15:35] phillw, LOL === forestpiskie is now known as Guest46263 === om26er|away is now known as om26er === salem_ is now known as _salem === _salem is now known as salem_ [17:46] balloons, could you run ubiquity test again for me, i've got rid of the long sleep, only one more left to remove. [17:49] DanChapman, :-) give me a little bite and I'll give it a whirl again [17:49] *bit [17:49] cheers mate :-) [17:55] DanChapman: I tend to get rid of long sleeps during testing season, as well :D [17:55] phillw, HAH! [17:56] balloons: the alphas 1's are published for all those taking part :) [17:56] phillw, HaHaHa..... awesome! :-D [17:56] phillw, ohh published published? [17:57] someone going to post an announce? [17:57] If not, I can take care of that :-) [17:57] yup, they're on cdimages.ubuntu.com :) balloons Kate's doing it as we speak :) [17:57] kk. good [17:58] no PPC for lubuntu - both failed :'( [18:00] balloons, I'll be posting the announce [18:01] just waiting for the torrents to be working [18:01] balloons, do you have a testing report you can publish to ubuntu-release to summarize? [18:05] sure [18:06] Thanks! :-) [18:09] skaet, can you mark everything as ready and close the milestone then? [18:11] balloons, ok, doing. [18:19] balloons, have removed all the entries that aren't ready and closed the milestone. [18:19] skaet, i just saw, thanks for that === balloons changed the topic of #ubuntu-quality to: Welcome to Ubuntu Quality | http://wiki.ubuntu.com/QATeam | Alpha 1 (Participating Flavors) Images released | Cadence Week 2 starts June 29th! | Cadence Week Schedule: https://wiki.ubuntu.com/QATeam/Cadence/Saucy [19:59] Hi everyone, I have question about https://wiki.ubuntu.com/Bugs/HowToFix#Documenting_the_fix and daily packages [19:59] I'm fixing a bug in https://launchpad.net/ubuntu-wallpapers/trunk and I noticed that this package is handled by the daily release bot. [19:59] Should I still edit the debian/changelog as documented or is it generated automatically by the bot? [20:01] And, if I should edit it, what about the version number? [20:01] morning [20:02] Malizor, use: ubuntu-bug ubuntu-wallpapers [20:03] Noskcaj: the bug itself was already reported: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1177260 [20:03] Launchpad bug 1177260 in ubuntu-wallpapers (Ubuntu) "ubuntu-wallpapers-karmic slideshow does not work" [Undecided,New] [20:04] Malizor, ok. i recommend you report it on the iso tracker and confirm it affects saucy. [20:04] and add instructions on how to repeat the bug [20:05] Malizor, you might get a better answer in #ubuntu-devel, as this seems to be a packaging question [20:07] balloons: I come from there [20:07] "It sounds like this is a test package. I think it would be better to ask at #ubuntu-quality, since I am not sure of the current process" [20:07] ahh, because it's going into saucy? [20:07] so is it an SRU or something else? [20:08] balloons: The bug is not fixed yet anywhere, so yes, it should go in Saucy first [20:09] Malizor, ahh, ok so this is an SRU [20:09] I just want to know if I need to edit the debian/changelog in this case (daily release), then I will follow the traditionnal process :) [20:09] as far as I can tell anyways [20:09] Malizor, I would edit the changelog file and note the lp bug [20:10] balloons: ok. And what about the version number? [20:10] The current one is "13.04.0daily13.05.30-0ubuntu1" [20:10] Should I just go with "13.04.0daily13.05.30-0ubuntu2" ? [20:10] when you build it should increment the version number [20:11] I don't remember having to change it myself [20:12] It will probably be overwritten by the daily release bot with the actual date of the upload, but I don't want to break anything ;) [20:14] Malizor, hehe.. don't hurt me if an archive admin comes running, but afaik that should be fine [20:15] balloons: ok, I will just go with that and see what happens :) [20:15] Thanks! [20:15] yw, gl! [20:40] phillw: good morning, for tomorroy classroom I prepared some slides, should I add them to the wiki?, http://people.ubuntu.com/~chilicuil/pdf/pbuilder.pdf [20:42] chilicuil: let pleia2 know and she will get them added for you. [20:43] phillw: alright, then I'll let her know 5 minutes before, have a nice day [20:43] chilicuil, slides are awesome! congrats [20:43] phillw, \o [20:43] SergioMeneses: =)! [20:50] chilicuil: let her know a.s.a.p. ! [21:01] chilicuil, ! [21:01] * balloons hugs chilicuil [21:02] SergioMeneses, ! [21:02] * balloons hugs SergioMeneses too! [21:02] so wonderful to see you two [21:03] * chilicuil hugs balloons back, and hugs SergioMeneses too [21:19] balloons, chilicuil jeje you're very friendly today ;) [21:20] how is everything? [21:23] thomi: Hey ! Sorry to bother you, balloons told me that you could help me about autopilot ? I have a question about it and the testability driver [21:23] Oranger: sure thing [21:23] SergioMeneses, everything is well going on right now it seems [21:23] in a word, busy :-) [21:23] Oranger: you should also join #ubuntu-autopilot - there are other autopilot experts in there as well :) [21:24] thomi: Ahah ok thank you :) [21:25] balloons, jeje like all of us [21:29] balloons: ping. About your comment to cast to int while opening the toolbar... [21:30] do you have a scenario where it fails? I am using gu on the test, so I'm not sure how to write a test for this you mention. [21:41] elopio, hmm.. one of the core apps failed until the change happened [21:42] can we really click on .7 of a pixel anyway? [21:46] elopio, I think from a sanity point it makes senses to round the result to the nearest actual pixel === salem_ is now known as _salem [21:51] balloons: I'm looking at autopilotand it divides some coordinates in half, so I think there's no problem there. [21:51] actually, on the move method it casts them to float. [21:52] elopio, lol.. well clearly it's not been an issue in the past. I just wonder why we have floating point pixels [21:52] honestly me typecasting them in the emulator likely doesn't make sense, but [21:52] I think you are right. It would be better to have ints. I'm just trying to find a test that backs the code. [21:52] well I mean on the autopilot end too [21:53] balloons: do you remember what app was failing? Maybe I can copy some qml from there. [21:53] elopio, let me try and find the test that failed [22:09] just read the last messages, you are talking about the problem with the ubuntu sdk emulator not being able to open the toolbar for certain heights of the app? [22:14] netcurli, yes [22:14] that was you who mentioned it right? [22:15] I have an example here: lp:~djfun/+junk/autopilot_toolbar_problem [22:15] elopio is working on getting a revised version merged into the sdk itself so it has a proper home [22:15] elopio, ^^ [22:15] perfect netcurli! that's just what he was looking for [22:15] thanks netcurli. [22:15] * elopio looks. [22:17] I'm calling it a day, see you all tomorrow :-) [22:18] DanChapman, see you tomorrow.. how's the branch btw? [22:18] did you clear the other sleep? [22:18] i'll let you know tomorrow how my test goes tonight with it [22:19] No not yet I cant seem to get the properties of the webkitview. But i can view it in vis. Will investigate it more tomorrow. [22:19] balloons, sweet, its running rather lovely today :-) [22:19] hehe, very nice [22:20] need to get some folks invovled to help with the test runner for it [22:20] so that setup and teardown is automated [22:20] good night mate! [22:20] looking forward to pitti's updates tomorrow aswell [22:20] good night [22:21] netcurli: intersting. Seem like a problem in the drag method. [22:33] elopio, O really? I had problems intially but cleared them all up with the starting a 1 pixl and swiping up only a small amount [22:33] some of the original code was really wonky with opening the toolbar sanely [22:34] balloons: yeah, my biggest problem was that I had to start swiping from outside the MainView, but I found the globalRect property and that seems to work. [22:34] this problem with the non-integer coordinates is because there's a while on autopilot that loops forever. I think I can fix it. [22:38] cool.. glad netcurli could demonstrate the issue so you could delve into it deeper