[00:18] <balloons> dobey, are you running a window manager inside your vm?
[01:02] <kris_> Hello everybody. I was thinking to join quality team as a tester and contribute little bit. My knowledge about Linux is very limited. This is actually my project for one of my classes at school. Our assignment is to join an open source community, participate and contribute.
[01:03] <wxl> kris_: excellent. welcome! have you seen the wiki pages already? there's a lot of detail there!
[01:04] <kris_> Yes, I have.
[01:04] <wxl> kris_: are there any questions about how the process works or where to get started?
[01:08] <kris_> I have been reading the wiki pages, and I can’t imagine how can I contribute. It is little bit overwhelming. So yes, what would be my first step?
[01:08] <wxl> kris_: so i assume, by testing, that you want to help with testing the installation images, correct?
[01:09] <kris_> Actually Yes, I was looking at the ISO tracker walkthrough.
[01:11] <wxl> ok, so basic first steps:
[01:11] <wxl> 1. make sure you have a launchpad account
[01:11] <wxl> 2. join the ubuntu-quality team on launchpad
[01:11] <wxl> 3. sign up for the mailing list
[01:11] <wxl> 4. hang out here
[01:11] <wxl> once you got that out of the way, then we can move on to the actual work :)
[01:12] <kris_> I have setup a Launchpad account already. So let me join the quality team and mailing list.
[01:13] <wxl> let me know when you're done
[01:17] <wxl> kris_: i'm out of here in 10 minutes so i'm going to break it down for you:
[01:18] <wxl> when it comes to ISO testing, we have sort of three different ISOs that may get tested at any particular time (tho not necessarily all of them):
[01:18] <wxl> 1. daily images
[01:18] <wxl> 2. milestone images
[01:18] <wxl> 3. LTS point release images which are milestones, technically, but good to point out as they're on their own cycle
[01:19] <wxl> so daily images represent the current state of development. both LTS and non-LTS versions have them (so right now, there's a vivid daily and a trusty daily)
[01:20] <wxl> milestone images are release images though not necessarily just the final release. there's alpha 1 & 2, beta 1 & 2, and ultimately the final release
[01:20] <wxl> LTS images have several point releases that collect updates and include support for newer hardware. like i said, they're a sort of milestone
[01:21] <wxl> if you look at the release schedule, the milestones always come out on thursday. the testing on those images come out the tuesday before. right now, there's nothing going on, though the 2nd point release of 14.04 (trusty) will come out next thursday.
[01:21] <wxl> that being said, i would focus your effort right now on daily images (specifically vivid daily)
[01:22] <wxl> i would suggest doing your tests on a virtual machine
[01:22] <wxl> you can do it on real hardware, but ultimately, it will wipe everything out, so it will need to be a spare machine
[01:22] <wxl> i would suggest virtualbox for this pupose
[01:22] <wxl> so you'll want to install that
[01:23] <wxl> then go to the ISO tracker, then vivid daily, then pick an image. if you're only interested in ubuntu, go to ubuntu desktop. if you want to help out with other flavors like kubuntu, lubuntu, xubuntu, etc., tehy're there too
[01:23] <wxl> make sure you choose the image that reflects your machine's architecture
[01:23] <wxl> as a general rule, i386 will work no matter what
[01:23] <wxl> when you click on it, there will be a link to download info
[01:23] <wxl> download it
[01:24] <wxl> then make a new ubuntu/linux virtual machine (default settings should be fine) and in the storage tab of the settings on that machine, add the iso to the empty ide drive
[01:24] <wxl> then boot the image
[01:24] <wxl> at that point you follow the test cases
[01:25] <wxl> if you find a bug in your testcase, file it with `ubuntu-bug <package>`
[01:25] <wxl> then include the number of the bug in your report
[01:25] <wxl> at the end, if the test case succeeds, then mark it a success. otherwise it's a failure.
[01:25] <wxl> then do some more images
[01:25] <wxl> and then do the same thing the next day and so on
[01:25] <wxl> eventually you run out of work. at that point you can help with bug triage :)
[01:26] <wxl> ok, i'm out
[01:26] <wxl> good luck kris :)
[01:26] <kris_> thank you
[01:26] <kris_> I have joined the group and mailing list.
[01:27] <kris_> If I run into any problem, I'll come back here, thanks again.
[01:40] <balloons> awesome kris_. Basically https://wiki.ubuntu.com/QATeam/Roles/Tester is everything you need to know :-)
[01:42] <kris_>  Yes, I'm reading it right now. Lots of information, very helpful.
[14:07] <paulliu> alesage: hi. So did you review my branch?
[14:07] <paulliu> alesage: Just want to make sure that it is good enough to be used in the power indicator testings.
[14:18] <dobey> balloons: i think the ubuntu-touch-session setup script for adt-run doesn't start one
[14:42] <elopio> good morning.
[14:45] <dobey> morning elopio
[14:46] <elopio> hello dobey. Last I read is that your problem is only with one button, right?
[14:46] <dobey> elopio: yes
[14:49] <balloons> dobey, I find running a window manager is required in order for some things to work correctly. Not sure if this is a case of it or not, just tossing it out
[14:50] <dobey> balloons: i'll try making it start unity8 then
[14:50] <balloons> you are running under mir?
[14:51] <dobey> no
[14:54] <elopio> dobey: have you pushed to your branch with the instructions to create the qemu?
[14:54] <elopio> I need to copy somethings you have to the webapps tests. I might as well give it a try and see if I can find something related to the button problem.
[14:55] <dobey> elopio: no, i don't remember how i created the images
[14:55] <balloons> dobey, if not, I use something like ratpoison then
[14:56] <dobey> elopio: i think maybe it was adt-buildvm-ubuntu-cloud
[14:56] <balloons> basically something that autofocuses the app on launch
[14:57] <dobey> balloons: having no wm means whatever is on top of the stack has focus. and focus is surely not the issue as other things in the window can be clicked
[14:57] <dobey> "adt-buildvm-ubuntu-cloud -r vivid" i think is how i built the vivid image
[14:59] <balloons> dobey, just passing along that I had issues in the past.. my issues where with clock app actually, and noticing a qml property was never set unless run under some sort of wm
[15:02] <dobey> sure, i don't know what your specific issue was, but it sounds different
[15:03] <balloons> definitely was.. just trying to empty the brain of all the quirks I've ever experienced and pass them along ;)
[15:05] <dobey> hmm, i guess i can't start unity8
[15:06] <dobey> will try unity7 then
[15:16] <dobey> hrmm, unity7 won't start, probably due to video of course
[15:22] <alesage> paulliu, sidetracked by other stuff last evening, will look at asap
[15:24] <dobey> whee and sometimes i don't even get a screenshot or such with the 'failure'
[15:31] <elopio> alexabreu: ping. I have three things to talk to you about your branch.
[15:31] <alexabreu> elopio, sure
[15:32] <elopio> alexabreu: first, we need it to be python3. So on your dpkt-architecture call, you will need to add the argument universal_newlines=True.
[15:32] <elopio> to make it return a string.
[15:32] <elopio> also, that means we need the PPA thomi started, fgimenez is giving it the last touches.
[15:32] <alexabreu> elopio, yes (for python3) but I made it python2 bc of selenium, which was python2 afaik
[15:34] <alexabreu> elopio, ah no my mistake, there is a python3 version, so I'll fix that for sure
[15:35] <elopio> alexabreu: second thing, the only way I got it to work when using launch_click_package was to use initctl set-env for dev tools host and port. So I think that we need different ways to set the env vars depending on how we launch the package.
[15:38] <elopio> alexabreu: and last thing we need to discuss is how to get this tests running. If we put them in a debian package, we can tell ci to configure it for us using the selenium ppa.
[15:38] <fgimenez> elopio: alexabreu a first version of the ppa is ready for testing at https://launchpad.net/~canonical-platform-qa/+archive/ubuntu/selenium
[15:39] <elopio> alexabreu: another nice alternative is to split the tests, one per click package. On the manifest we specify the tests to run, and then they are runnable with adt-run using qemu as a testbed.
[15:40] <elopio> according to dobey's recent adventures, it's likely that if we go the adt-run way, we'll hit some problems because it's mostly unexplored.
[15:41] <elopio> fgimenez: thank yyou. I will give it a try.
[15:42] <balloons> experimental selenium packages? elopio fgimenez what do you have up your sleeves?
[15:42] <elopio> thanks for the info in the crd fgimenez. That quilt push -a was the command I missed.
[15:43] <dobey> elopio: maybe you should just have the EnvironmentVariable fixture set the variable in the upstart and dbus sessions
[15:43] <alexabreu> elopio, could we control when the tests are being run? or do they have to be run manually?
[15:44] <alexabreu> elopio, regarding the envvars, any suggestion?
[15:45] <elopio> alexabreu: if we go the adt way, it's going to be manual because ci is not yet ready to run those tests. But there are some good points for this: it's the future and ci is going to get it working for merge proposals soon, and by documenting how you create the qemu, you will have an environment that really easy to reproduce, so everybody should always get the same results.
[15:45] <fgimenez> elopio: it's the quick solution, probably it would be better to change the source format and have the patches automanaged
[15:46] <fgimenez> elopio: but that means more changes to the package itself
[15:46] <elopio> alexabreu: about the env vars, my suggestion is to try to always launch the click package and set the initctl env vars, but that would mean to either install the click package or to make a test desktop file to launch it.
[15:47] <elopio> if we go the qemu way, adt-run takes care of installing it.
[15:47] <elopio> for the test desktop, I need to give it a try. I'm not sure if it'll work. I'll be playing with your branch today.
[15:48] <alexabreu> elopio, ok, feel free to MR something
[15:49] <elopio> fgimenez: I understand that. I would love if we could update the package in debian, so the patch won't be needed. But that's something to discuss for the next sprint, it might take us too far from our goal. For now, your quick solution is perfect.
[15:49] <elopio> I'll give it a try after walking the dog. bbs.
[15:58] <dobey> well
[15:58] <dobey> i got metacity working and qmlscene can actually do maximized now, but the click still fails
[16:12] <dobey> ok, so i changed the resolution of the xvfb to 540x960, and hav metacity running, and the qml is maximized, and it still times out
[16:19] <dobey> anyway, i guess i should go get lunch.
[17:10] <dobey> hrmm
[17:10]  * dobey wonders who else to bug about this problem
[17:11] <dobey> or if i should just try to land my branch with skipTest added to these tests that fail in this way
[17:46] <elfy> balloons: I'm working now on updating the manual testcase wiki page - I will add a note about not adding possible test numbers to mp's
[17:48] <balloons> elfy, always seems to confuse folks :-)
[17:48] <elfy> yea - it shouldn't in future :)
[17:49] <elfy> I remember doing exactly the same thing :p
[17:57] <elfy> balloons knome - https://wiki.ubuntu.com/QATeam/DevelopmentToolsUsage
[17:58] <elfy> this page has 'bit's of bzr in it - there are other bits, like adding and commit messages at https://wiki.ubuntu.com/QATeam/ContributingTestcases/Manual/Writing
[17:59] <elfy> which I'm looking at now - should I add add & commit to the tools usage page and remove from the writing one?
[18:00] <knome> elfy, probably so because that page can be reused
[18:01] <knome> (without having looked at the pages just right now)
[18:01] <knome> :)
[18:06] <elfy> ok - and yea - I can just clean up the write page and add thing to usage now
[18:10] <balloons> knome, what's the ticket for https://bugs.launchpad.net/ubuntu-qa-website/+bug/1416893?
[18:10] <knome> i don't remember from the top of my head
[18:11] <balloons> apparently it's still an issue; I didn't realize
[18:12] <elfy> bug 1416893
[18:12] <elfy> I hope
[18:12] <elfy> yay
[18:12] <knome> it's still an issue if the SSO account doesn't have a username associated with it, eg. it's not linked with LP
[18:12] <knome> elfy, ticket meaning the canonical IS one
[18:13] <elfy> oh sorry
[18:18] <knome> can't find the ticket now
[18:18] <knome> maybe pleia2 knows
[18:20] <balloons> interesting.. so people with sso accounts, but never signed up for launchpad?
[18:20] <pleia2> yeah, there's a forever ticket, sec
[18:20] <balloons> so if they sign up for launchpad, does it fix the issue or no?
[18:21] <pleia2> #24297
[18:21] <balloons> also, dkessel did you see pleia2's feedback?
[18:21] <knome> balloons, fixes
[18:21] <pleia2> filed in April of 2014, last response I got was in May of 2014 (no fix), I followed up on January 4th again
[18:22] <knome> only last year? :)
[18:22] <balloons> knome, so is it a matter of a better error message then?
[18:22] <dkessel> good evening
[18:22] <knome> balloons, that would be a start
[18:22] <pleia2> the transition from lp to Ubuntu SSO was a serious disaster with no communication with the community, so we have problems all over the place :(
[18:22] <dkessel> balloons: yes. i read the part about the list of known bug, and about the hardware URL box
[18:23] <knome> balloons, but ultimately, it should just allow doing whatever is needed to log in on the fly
[18:23] <pleia2> help wiki, loco.ubuntu.com, iso&package tracker are the ones I know of
[18:23] <knome> might affect other sites too
[18:23] <knome> what about pad? forum?
[18:26] <balloons> dkessel, yes.. I'm thinking about the hardware link especially.. I know you have a nice idea for the bugs
[18:28] <dkessel> balloons: honestly, i don't know if anyone ever used those URLs. I would not have any problems with dropping it ;)
[18:29] <dkessel> but i am not part of the target group of that information ;)
[18:31] <balloons> dkessel, I was thinking to do the same
[18:32] <balloons> that is, dropping the field completely. Originally we envisioned a hwdb, but that never really came to pass
[18:35] <dkessel> elfy, what do you think? ^
[18:35] <wxl> infinity: the metapackage issue is not affecting vivid daily is it?
[18:38] <elopio> brendand: should we also skip the wizard test if the sim is not inserted?
[18:41] <elfy> re hardware info - never use it - never ask people to use it :)
[18:42] <elfy> I've set up a xubuntu place for that information for if *we* ever need it
[18:43] <wxl> oops
[18:48] <brendand> elopio, why?
[18:48] <balloons> given Liz's feedback and knowing I've been asked about it before it seems to be mainly a point of confusion. I too, do not use it
[18:50] <elopio> brendand: I'm getting:
[18:50] <elopio>   File "/tmp/adt-run.ePQNOn/build.FOM/real-tree/ubuntu_sanity_tests/tests/test_settings_wizard.py", line 120, in test_complete_settings_wizard
[18:50] <elopio>     self.assertEqual(sim_inserted, self.is_sim_inserted)
[18:50] <elopio> um, but that shouldn't happen. That's weird
[18:54] <dkessel> pleia2: i updated bug 1017207 to note the hardware URL input box should be removed
[18:54] <pleia2> dkessel: hooray :)
[18:54] <elopio> dobey: how are you running your tests? I still get the launching error.
[18:54] <elopio> I'm using adt-run --click-source . --click build/com.canonical.payui_15.01.last_amd64.click -U --apt-pocket proposed --setup-commands ubuntu-touch-session --- qemu /media/elopio/vms/images/adt-vivid-amd64-cloud.img
[18:56] <brendand> elopio, shouldn't that just match the fact of whether the sim inserted screen is shown with the sim status?
[18:56] <elopio> brendand: yes, I'm waiting for the screenshot. Maybe the wrong screen was opened.
[18:58] <brendand> elopio, is_sim_inserted will be true if a sim is inserted in any slot
[18:59] <elopio> it comes with no screenshot, how convenient :/
[18:59] <elopio> brendand: I'm not able to reproduce your uninstall errors.
[18:59] <brendand> elopio, i'm not able to not reproduce them :)
[19:00] <brendand> elopio, i will try and figure out what's happening
[19:01] <elopio> brendand: I left comments on the branch. In theory, I have code to make sure they don't happen. So if you see it again, please paste traceback and screensthot.
[19:05] <dobey> elopio: what revision of the branch do you have?
[19:06] <dobey> elopio: i've added skips for the tests which fail due to the buyButton click failing. and i just pushed a new revision which updates the HACKING file
[19:07] <elopio> dobey: I'll follow the instructions from there.
[19:10] <elopio> dobey: is this expected? http://paste.ubuntu.com/10176933/
[19:12] <dobey> elopio: yes. add --maint-mode and it should "do the right thing" there. i left --maint-mode out of the HACKING file so it would show up for people who might need to care about that
[19:12] <dobey> i don't think having the one extra package installed will matter for them though
[19:13] <elopio> dobey: got it.
[19:13] <brendand> elopio, alesage - could one of you give this a second review? https://code.launchpad.net/~canonical-platform-qa/ubuntu-sanity-tests/print_using_argparse_conf/+merge/249304
[19:14] <elopio> dobey: I don't have the right chroot. http://paste.ubuntu.com/10176950/ A step with the command to create it would be useful
[19:14] <elopio> brendand: sure, one second.
[19:15] <dobey> elopio: hmmm
[19:17] <dobey> ah ok
[19:19] <dobey> elopio: done
[19:20] <dobey> elopio: i've finally made an MP for it too: https://code.launchpad.net/~dobey/pay-ui/adt-run-ap/+merge/249387
[19:41] <brendand> elopio, to confirm - the thing you would like to be fixed is passing the artifacts_directory instead of the config stack?
[19:49] <brendand> elopio, someone accidentally set https://code.launchpad.net/~canonical-platform-qa/ubuntu-sanity-tests/print_using_argparse_conf/+merge/249304 to top-approved
[19:51] <brendand> elopio, if you want i can make another proposal to implement your suggestion
[19:58] <elopio> brendand: well, that's related to the mail I sent to vila with copy to the mailing list. I think I would prefer to unpack the values from the config and pass them as arguments if they are just a few.
[19:59] <brendand> oh what the hell?
[19:59] <elopio> so get artifact directory before calling the methods, and pass the directory as argument. If you like the idea, yes, a branch for it would be nice.
[19:59] <elopio> it will change your tests a little too.
[19:59] <brendand> elopio, i pushed and it went to trunk...
[19:59] <brendand> elopio, bzr did something dumb
[19:59] <brendand> elopio, i'll fix it
[20:00] <elopio> brendand: :) not a big deal, as your branch is actually fixing the issue.
[20:00] <elopio> about the test suggestion, I will try to make an MP so we discuss it there.
[20:03] <brendand> elopio, ok. i just checked i didn't introduce any flake8 issues too
[20:05] <Letozaf_> balloons, hi
[20:06] <brendand> elopio, looks like we are broken again:
[20:06] <brendand> elopio, http://pastebin.ubuntu.com/10177521/
[20:10] <elopio> brendand: coudl it be that your image is too old?
[20:10] <elopio> if there is a new one, you should flash it.
[20:11] <elopio> veebers: looking at all the prints for finger movement we are now getting in the log, I think that autopilot's -v should only print info messages.
[20:11] <elopio> -vv should print debug.
[20:12] <veebers> elopio: Sounds reasonable, I totally agree about the prints for finger movement
[20:14] <veebers> elopio: can you file a bug against ap stating that?
[20:15] <elopio> veebers: yes, give me a second.
[20:15] <elopio> and that means that we need to print more info in our tests, which is good.
[20:15] <veebers> no pressure, just when you can. I can't fix it right now anyway ;-)
[20:16] <elopio> dobey: http://paste.ubuntu.com/10177617/
[20:16] <elopio> you missed the 'create'
[20:16] <elopio> veebers: the only pressure is that I will forget if I don't do it now :)
[20:21] <elopio> https://bugs.launchpad.net/autopilot/+bug/1420949
[20:23] <brendand> elopio, i just updated that's why i'm saying we got broken :)
[20:24] <elopio> brendand: I don't get how the apt list in a newly flashed image can point to non-existing packages. I will reflash.
[20:25] <dobey> elopio: oh, oops indeed
[20:40] <elopio> brendand: agh, same problem here.
[20:41] <brendand> elopio, might be a small window between image builds where we get hit by this
[20:41] <elopio> so it seems we are with no good solution here. If we add the update, we might get unity upgrade. If we don't, we might get 404
[20:41] <elopio> brendand: we will be hitting this until a new image is made, unless we update.
[20:43] <elopio> for now, and to let us keep working, I suppose adding the -u option for the update is the way to go
[20:43] <elopio> I have no idea what an image tester should do in this case.
[20:46] <elfy> balloons: ok - redone https://wiki.ubuntu.com/QATeam/ContributingTestcases/Manual/Writing and added stuff tohttps://wiki.ubuntu.com/QATeam/DevelopmentToolsUsage
[20:58] <elfy> wxl: you going to get that gnome monitor one merged - or I can I'm wandering about in the tracker atm
[20:59] <wxl> elfy: oh yeah i guess i can do my first merge :)
[21:00] <elfy> don't forget to do the tracker first so you get the number and can rename the testcase :)
[21:00] <wxl> help me out with that, elfy ?
[21:01] <elfy> http://packages.qa.ubuntu.com/qatracker
[21:01] <elfy> then the admin option on the left
[21:03] <wxl> jeez weird that you have to copy/paste everything
[21:03] <elfy> :)
[21:03] <elfy> then new testcase - don't give a number - that's automatic
[21:04] <elfy> once you've got that - you can add the number and merge it
[21:04] <elfy> balloons has a tool in the branch but I can never make it work
[21:11] <Letozaf_> balloons, you're about ?
[21:15] <elfy> he was - he's probably hiding from me again Letozaf_ :)
[21:16] <knome> or me
[21:17] <elfy> if we're both here - he's definitely going to hide :p
[21:21] <wxl> elfy: done, but had to make another commit with the pass/fail bit corrected
[21:21] <Letozaf_> elfy, LOL
[21:21] <wxl> noticed that after the fact
[21:21] <wxl> maybe i should have done a merge request but naaaah :)
[21:21] <Letozaf_> elfy, good evening to you :)
[21:21] <elfy> wxl: ok - thanks :)
[21:22] <elfy> Letozaf_: and you too :)
[21:22] <Letozaf_> :)
[21:22] <elfy> Letozaf_: did you get a phone?
[21:23] <Letozaf_> elfy, yes
[21:24] <Letozaf_> elfy, a white one, it's really cool ?
[21:25] <elfy> nice :)
[21:25] <Letozaf_> elfy, did you try to get one on bq site ?
[21:26] <elfy> nah - first of all I've no cash, secondly I'm one of those people who's phone contract is for hardly anything as I text and talk to people
[21:27] <Letozaf_> elfy, :)
[21:34] <balloons> sorry, missed her
[21:34] <elfy> balloons: seems that it's no longer easy to see how to report testcase bugs from tracker
[21:34] <elfy> bug 1420980
[21:35] <elfy> balloons: not sure she's deliberately left right now
[21:38] <balloons> elfy, nice catch actually
[21:41] <elfy> someone I am talking to in #xubuntu-devel brought it to my attention :)
[21:41] <elfy> xubuntu ftw :D
[21:43] <balloons> elfy, btw the new page looks lovely!
[21:43] <elfy> wiki ones?
[21:43] <balloons> elfy, are you going to go ahead and move the script into the branch also? https://wiki.ubuntu.com/QATeam/ContributingTestcases/ManualStyleGuide/test_case_format_script
[21:45] <elfy> balloons: I was looking at that a short while ago - I assume just more or less the same as the existing tool?
[21:46] <balloons> elfy, not sure what you mean, but we could certainly grab the code and place it inside the branch itself
[21:46] <balloons> it would also be helpful to have a nice README inside the branch; even if you just point people to the wiki to avoid duplicating info
[21:46] <elfy> that's what I meant - wget it then - make it a file with readme things ?
[21:46] <balloons> elfy, yep :-0
[21:47] <knome> please remove the instructions from the wiki :P
[21:47] <elfy> ok - I'll make that next balloons
[21:47] <knome> or at least don't make people go there to read the readme..
[21:47] <balloons> I usually just run it locally rather than copying to /usr/bin as wekk
[21:47] <elfy> knome: I'd not do that :D
[21:47] <balloons> knome, lol, don't like the idea of linking to the wiki?
[21:47] <knome> balloons, i don't like to force people to use the wiki if they already download the tool from a branch
[21:48] <balloons> knome, :p I know. The instructions are really simple. Run it and pass your file as the argument
[21:49] <knome> yes, that too
[22:24] <wxl> elfy: i think i'm going to copy what xfce did and make a lxde folder in the testcases. i can do that without affecting anything else, right?
[22:24] <elfy> yea
[22:24] <wxl> i don't need to make a merge request, right? :/
[22:25] <dobey> hmm
[22:26] <elfy> well - probably better to do something - I can approve it as soon as I see it
[22:26] <elfy> wxl: ^^
[22:27] <wxl> k thx elfy
[22:35] <alesage> elopio, veebers, paulliu asked me to review http://code.launchpad.net/~paulliu/unity8/notification_helper/+merge/249211 , he could probably use your feedback too
[22:39] <wxl> elfy: your turn :)
[22:41] <wxl> not sure why all those bugs are linked grr
[22:41] <veebers> alesage: ack, will push it on the stak
[22:41] <veebers> stack
[22:42] <elfy> wxl: propose it for merging so I can approve
[22:42] <wxl> elfy: https://code.launchpad.net/~ubuntu-testcase/ubuntu-manual-tests/trunk/+merge/249427
[22:42] <elfy> what's with all the bugs linked?
[22:42] <wxl> i have no idea
[22:42] <wxl> wait a minute
[22:43] <wxl> something is messed up here me thinks
[22:43] <wxl> i'm going to do this over
[22:43] <elfy> ok
[22:43] <elfy> I might have crashed before I see it again - put my name as reviewer and I'll do that as soon as
[22:45] <wxl> elfy: ok NOW it's right
[22:45] <wxl> i did my merge backwards XD
[22:47] <elfy> all done
[22:47] <wxl> thank you sir
[22:48] <elfy> welcome :)
[22:49] <elfy> what *we* did was only have things in xfce which were just us, so things like abiword which could have been used by anyone were in the main
[22:49] <wxl> right right
[22:49] <wxl> so i copied
[22:49] <wxl> made sense to me
[22:50] <wxl> i've used lxterminal on other flavors ;)
[22:50] <elfy> so for instance - gnome system monitor would be where it is now
[22:50] <wxl> yep
[22:52] <wxl> elfy: you might want to move Xubuntu GTK3 Indicators and Power in there, no?
[22:52] <wxl> or Xfce4 Assistive Technologies?
[22:52] <elfy> I might once
[22:53] <elfy> we don't actually do it anymore :p
[22:53] <wxl> ah
[22:53] <wxl> should prolly rm then
[22:53] <elfy> wut?
[22:53] <wxl> if you don't do it anymore, the testcase can be removed?
[22:54] <elfy> no we use them :)
[22:54] <wxl> oh
[22:54] <wxl> then move them in Xfce/ ?
[22:54] <elfy> ormight
[22:55] <elfy> no - xfce was JUST xfce - xubuntu was kept out - it's from the way we used to do our testcases
[22:56] <wxl> well
[22:56] <wxl> there's something xubuntu specific in there
[22:56] <wxl> settings of some kind
[22:56] <elfy> anyway - the long and short of is - we're not looking to fiddle about currently :)
[22:56] <wxl> hahhaa ok
[22:57] <elfy> :)
[22:57] <knome> theoretically the tracker "should" have a tagging system which allowed anything to appear under anything
[22:57] <elfy> if I was ever likely to do anything it would be empty xfce on the branch
[22:57] <knome> but practically it's just much more useful to group them to this kind of groups
[22:58] <knome> "stuff that mostly xubuntu users use"
[22:58] <wxl> yeah
[22:58] <wxl> well
[22:58] <wxl> merge requests welcomed, knome :)
[22:58] <knome> of course you can put a rhino on an elephant
[22:58] <wxl> hahahahahah
[22:58] <knome> i mean i'm happy the way we have it now...
[22:59] <elfy> wxl: when knome and I first worked out how we wanted to set it up - this was the easiest and most logical way
[22:59] <elfy> we now don't test in quite the same way
[22:59] <wxl> ah
[22:59] <elfy> so it's less of an issue
[22:59] <wxl> well i kind of like the separation
[22:59] <wxl> it will make it easier for lubuntu folks to know where to help out
[22:59] <elfy> and of course the tracker admin and branch are 2 seperate things
[22:59] <wxl> or rather where to put their stuff
[22:59] <knome> it's better than a list of all testcases..
[22:59] <elfy> there is that
[23:00] <wxl> elfy: which, to me, is really silly
[23:00] <wxl> but again, merge requests welcomed XD
[23:00] <elfy> wxl: yep - but these are the tools we have :)
[23:00] <wxl> yuuup
[23:01] <elfy> it's just nice to have someone else watching what goes on in the manual testing code tbh
[23:05] <elfy> night wxl - have fun wondering what to do with the branch :)
[23:07] <wxl> hahah
[23:07] <wxl> night elfy
[23:08] <alesage> balloons, do you know if there's a better remedy for the adt-run 404 errors you mention in your orange notebook post?
[23:09] <alesage> I'm on the latest and greatest but getting some 404s
[23:09] <alesage> :(
[23:24] <elopio> alesage: we need to do the apt-get update, again.
[23:25] <alesage> elopio, is writable-mode necessary for that?  and if so how to undo?
[23:25] <elopio> I've made a card for it. I'll implement it now, unless you want to take it.
[23:25] <elopio> alesage: writable is necessary, temporarily.
[23:26] <elopio> umount to undo it. But there's a script that will take care of it for us.
[23:30] <alesage> elopio, umount what?
[23:30] <elopio> alesage: http://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=a51f26f61c376