[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


[02:43] <cjohnston> dutchie: does that mean its confirmed?
[08:50] <godbyk> Hey, thorwil.  Want to continue some design work?
[09:08] <godbyk> Hey, komsas.  Did you get the manual to compile okay under TL2009?
[09:13] <komsas> hi godbyk, yes, but some lithuanian letters are squares.
[09:13] <godbyk> We just settled on a new typeface.  Let me upload the latest code and see if those letters appear in this font.
[09:13] <godbyk> (If not, we'll find a font that supports all the Lithuanian glyphs.)
[09:14] <komsas> ok, I will pull
[09:14] <godbyk> give me a sec to push it first
[09:16] <godbyk> komsas: Okay, I've pushed it.
[09:17]  * komsas pulling
[09:19] <komsas> godbyk: "! LaTeX Error: Missing \begin{document}." ?
[09:19] <godbyk> Are you running 'make ubuntu-manual-lt.pdf"?
[09:19] <komsas> yes
[09:20] <godbyk> Run 'make clean' and 'rm ubuntu-manual-lt.*' and then try it again.
[09:21] <komsas> it didn't help
[09:21] <komsas> same error
[09:22] <godbyk> Run 'make ubuntu-manual-lt.tex'
[09:22] <godbyk> then open the ubuntu-manual-lt.tex file.
[09:22] <godbyk> does it have a \begin{document} line in it?
[09:23] <godbyk> (should be around line 5)
[09:23] <komsas> it have, strange.
[09:25] <godbyk> can you send me your ubuntu-manual-lt.log file?  (pastbin or email to<EMAIL_ADDRESS>[09:25] <komsas> ok
[09:25] <godbyk> Do you have local edits to the po/lt.po file, or is it the same that's in the bzr repository?
[09:26] <komsas> http://paste.ubuntu.com/379621/
[09:27] <godbyk> In the meantime, here's my compiled copy: http://kevin.godby.org/private/ubuntu-manual/ubuntu-manual-lt.pdf
[09:27] <godbyk> See if there are letters missing still.
[09:27] <komsas> same like in bzr repo
[09:28] <komsas> godbyk: now all letters showing. :)
[09:28] <godbyk> did the paste get cut off?
[09:28] <godbyk> awesome. :)
[09:31] <komsas> no, it is all text
[09:31] <godbyk> looks like it's been cut off at the bottom.
[09:31] <godbyk> \sl@tab@pred isn't a full line
[09:31] <thorwil> hi godbyk
[09:32] <godbyk> should be \si@tab@predim=\dimen###
[09:32] <komsas> http://paste.ubuntu.com/379624/
[09:32] <godbyk> hey, thorwil .
[09:32] <godbyk> I pushed our font changes.
[09:32] <godbyk> Haven't got back to the headings yet.
[09:32] <godbyk> trying to sort on the running heads.. the small caps are failing in the translations for some odd reason.
[09:32] <godbyk> komsas: better
[09:33] <godbyk> looks like some of your stuff got merged
[09:33] <godbyk> or didn't, as the case may be.
[09:33] <godbyk> there are <<<< TREE lines that are mucking things up.
[09:33] <godbyk> komsas: run 'bzr status' and see what it says
[09:35] <thorwil> godbyk: well, any open design issues on your side? it seems like you are busy enough :)
[09:36] <godbyk> thorwil: heh.. I have a pile of TODOs.
[09:36] <komsas> some conflicts with ubuntu-manual.cls, I did some changes, commented some unnecessary fonts.
[09:36] <godbyk> I may have to put most of them off until I get done putting together slides and whatnot for this Lernid session I'm signed up for.
[09:36] <godbyk> komsas: aha.  Just run 'bzr revert ubuntu-manual.cls' and try it all again.
[09:37] <godbyk> I restructured the code a bit, so you shouldn't need all the fonts now -- just the ones required to compile the translation you're interested in.
[09:38] <thorwil> heh, the 48hour thing will at least succeed in causing stress
[09:39] <godbyk> thorwil: yeah, namely because I'm not quite sure what I'm to cover.
[09:39] <godbyk> At this stage, I think most of the writing is done and now we're left with editing and translating, right?
[09:40] <thorwil> i have no clue on the state of writing. i try to not care about that :)
[09:40] <godbyk> I haven't been paying attention either.
[09:40] <godbyk> I've been trying to get the document design down and working on getting all the translations to compile.
[09:40] <godbyk> Btw, do you know what the status is of all that icon talk?
[09:41] <godbyk> komsas: Did the bzr revert let you compile okay or are you still having problems?
[09:42] <komsas> I pulled new branch, now I'm getting error "po4a::tex: Can't read from file without having a filename"
[09:43] <godbyk> what is the po4a-translate command line look like?
[09:43] <komsas> "at /usr/bin/po4a-translate line 227"
[09:44] <komsas> godbyk: "po4a-translate --master-charset=utf8 -f latex -m main.tex -p po/lt.po -l ubuntu-manual-lt.tex -k 0"
[09:44] <godbyk> that looks right.
[09:44] <godbyk> does 'make ubuntu-manual-lt.tex' work?
[09:45] <komsas> nop, same error
[09:46] <godbyk> Does the size of ubuntu-manual.cls equal 24438 bytes?
[09:46] <godbyk> (also, does 'make' work by itself?)
[09:46] <ubuntujenkins> no make doen't work I just pulled a new branch
[09:47] <komsas> yes, same size.
[09:47] <godbyk> what's it say when you run 'make' (with no arguments)?
[09:47] <komsas> make works godbyk
[09:48] <ubuntujenkins> http://paste.ubuntu.com/379632/
[09:51] <ubuntujenkins> I have to go to a lecture be back in a bit
[09:51] <godbyk> ubuntujenkins: you may have to install TeX Live 2009.
[09:52] <godbyk> thorwil: does the latest revision compile for you?  (or am I the only one?)
[09:53] <komsas> godbyk: now I did get that error, after I did make. I have new "! Font \zf@basefont="Linux Libertine O" at 10.0pt not loadable: Metric (TFM) fi
[09:53] <komsas> le or installed font not found.
[09:53] <komsas> "
[09:53] <komsas> didn't *
[09:54] <godbyk> Ah, komsas, make sure you have done a 'sudo apt-get install ttf-linux-libertine'.
[09:56] <komsas> godbyk: thank u ! all works perfect. :)
[09:57] <godbyk> komsas: Awesome!
[09:57] <godbyk> Both the regular 'make' and the 'make ubuntu-manual-lt.pdf' work?
[09:57] <komsas> yes
[09:57] <thorwil> godbyk: the status regarding icons is that i have to do it and havn't really started
[09:57] <godbyk> thorwil: Gotcha.  Just curious.
[09:58] <komsas> but make ubuntu-manual-lt.pdf began work only after I did make.
[09:58] <godbyk> Do you know what you're going to do for icons and just have to draw them?  Or you haven't started thinking about it yet?
[09:58] <godbyk> (More specifically, I'm curious as to what I'll need to do to help out.)
[09:58] <thorwil> godbyk: first i will deal with those for the title page
[09:59] <thorwil> godbyk: i'm not even sure about their number there
[10:01] <godbyk> Are we doing icons per chapter?
[10:01] <thorwil> maybe
[10:02] <thorwil> Ben wants them, but i will not do it if i don't see sane options for each chapter
[10:03] <godbyk> Right, I agree.
[10:04] <thorwil> ! LaTeX Error: File `siunitx.sty' not found.
[10:07] <godbyk> thorwil: Are you running TeX Live 2009?
[10:07] <thorwil> install-pkgs.sh doesn't help
[10:07] <godbyk> Yeah, I think it doesn't exist in 2007.
[10:07] <godbyk> Time for everyone to upgrade anyway. :)
[10:08] <thorwil> godbyk: so should i uninstall the package and get it from the projects site?
[10:09] <godbyk> thorwil: Yeah, uninstall all the texlive-* packages, then you can follow the install instructions in that email I posted eons ago.
[10:10] <thorwil> found it
[10:10] <thorwil> wow: After this operation, 527MB disk space will be freed.
[10:12] <godbyk> thorwil: To be replaced by a nice 2.5 GB download (if you have install absolutely everything).
[10:12] <thorwil> good that you say that. i don't have that space
[10:14] <godbyk> You can install less than everything, but I don't know what kind of space it requires.
[10:14] <godbyk> At a minimu
[10:14] <godbyk> Blah
[10:14] <godbyk> You could do a minimal install, and then just install each individual package that we require.
[10:14] <godbyk> Make sure you install xelatex.
[10:14] <godbyk> you don't need any docs
[10:15] <godbyk> and you'll want the language packs for any translations you want to compile.
[10:52] <thorwil> still installing
[10:54] <godbyk> thorwil: how much space will it take?
[10:54] <thorwil> godbyk: i think it said something around 1500 MB
[10:55] <thorwil> no docs, only english and german
[10:55] <godbyk> nice
[10:55] <godbyk> there are a TON of packages for latex.
[10:56] <thorwil> makes me wonder what current MS Word takes
[10:57] <godbyk> I'm not sure.  But it doesn't seem to do a lot of things that LaTeX does.
[10:57]  * godbyk loves TeX
[11:00]  * thorwil misses baseline grid support
[11:02] <godbyk> If you try hard, you can get it to work in LaTeX.  I think that ConTeXt has grid support.
[11:02] <godbyk> LaTeX3 is supposed to have grid support, if they ever finish writing it.
[11:03] <godbyk> TeX was written specifically to typeset mathematics really well.
[11:03] <godbyk> And math doesn't like to be set on a grid. :-/
[11:04] <godbyk> So by default, the document styles in LaTeX use stretchable spaces.
[11:04] <godbyk> For instance, the space above a section heading might be 14pt +2 or -3.
[11:04] <godbyk> So it'll nominally be 14 pt.
[11:05] <godbyk> But if LaTeX needs to adjust it to fill the page better, it can stretch it up to 16 pt and shrink it to 11 pt.
[11:05] <godbyk> You can remove the stretchy bits and say, 'I want this to be 14 pt, no more, no less.'
[11:05] <godbyk> And LaTeX will do that.
[11:06] <godbyk> But there are a lot of bits of glue sprinkled through, so you have to track them all down.
[11:06] <godbyk> (There was a package written a while ago that found most of 'em.  I've been meaning to try it out, but haven't taken the time yet.)
[11:07] <godbyk> I'm willing to give it a go, if you'd like to help. :)
[11:10] <thorwil> i have to stay focused
[11:11] <godbyk> On what?
[11:12] <thorwil> the title page
[11:12] <godbyk> Ah, fair enough.
[11:13] <godbyk> If we know what text is to be on there, we should get it to the translators so they can have at it.  Then once the design is done, we can get the translations wrapped up and put the whole title page thing behind us.
[11:13] <thorwil> i might sound like a broken record, but no good will come out of me taking on additional pieces of the cake
[11:14] <godbyk> No worries, I understand completely.
[11:14] <godbyk> I'm juggling a bunch of things right now and my brain is fried.
[11:15] <godbyk> I'm trying to get this document design finalized, get all the translations to compile, handle design differences for some of the languages, and I still need to toss together a presentation for this 48-hours thing.
[11:15] <thorwil> :)
[11:16] <thorwil> seen wolter lately?
[11:16] <godbyk> I haven't seen him for a while.
[11:17] <godbyk> With that, I think I'll go read a bit before going to sleep.
[11:17] <godbyk> As always, if anyone needs anything, ping me and I'll take a look when I'm awake again. :)
[11:17] <thorwil> ok, cya
[13:00] <dutchie> cjohnston: confirmed as in?
[15:00] <ubuntujenkins> is anyone running lucid able to compile the manual?
[15:01] <ubuntujenkins> Lucid has texlive 2009
[15:02] <dutchie> haven't tried recently
[15:03] <dutchie> wfm
[15:03] <dutchie> can't do localised versions though
[15:04] <ubuntujenkins> I can't do the main version localised is hard to do
[15:04] <ubuntujenkins> I have a new branch as well
[15:05] <ubuntujenkins> I think I will download texlive from the internet. where is the best place to install it>
[15:40] <dutchie> ubuntujenkins: /usr/locl
[15:40] <dutchie> +a
[15:41] <ubuntujenkins> cheers
[15:58]  * dutchie gets it to build in german
[16:12]  * dutchie pokes godbyk with a glossary shaped stick
[18:56]  * ubuntujenkins still can't compile the manual in any form. Considers clean installing ubuntu
[18:57] <dutchie> what errors are you getting?
[19:00] <ubuntujenkins> http://paste.ubuntu.com/379913/
[19:01] <ubuntujenkins> I have done three completly removes in synaptic and reinstalled the packages, I have installed as per god bk e-mail.
[19:03] <dutchie> do you have fonts installed?
[19:04] <ubuntujenkins> in every possible language I have the whole of texlive-full
[19:05] <ubuntujenkins> I like looking at the stuff as I write it to see if the formating is write, I also like to check if I have caused any compiling errors in my work
[19:05] <ubuntujenkins> *right
[19:06] <dutchie> fonts live in ttf-*, not texlive-full
[19:10] <ubuntujenkins> I am installing as many as I can find
[19:39] <ubuntujenkins> well with every possible ttf-* installed I get the exact same error
[19:40] <dutchie> hmm
[19:40] <dutchie> have to ask godbyk when he's around
[19:40] <ubuntujenkins> will do
[19:41] <ubuntujenkins> thanks
[20:02] <dutchie> ubuntujenkins: fwiw, http://pastebin.com/f3cddede5 is the ttf-* packages I have installed
[20:02] <ubuntujenkins> thanks dutchie I shall have a compare
[20:53]  * ubuntujenkins has no luck
[21:17] <godbyk> I'm back.
[21:18] <ubuntujenkins> dutchie can you do a pull and check that the manual still compiles ok?
[21:18] <godbyk> ubuntujenkins: It's using your TeX Live 2007 install.  Have you upgraded to 2009 yet?
[21:18] <godbyk> dutchie: The glossary stuff may wait until just after the 48-hours thing.
[21:19] <godbyk> It'll involve everyone upgrading to 2009 (which they should be doing at this point anyway).
[21:19] <godbyk> I have to whip up some slides and whatever for my session.  (Haven't started yet.)
[21:19] <ubuntujenkins> godbyk I did an install as per your e-mail. Also I am using lucid which has the 2009 packages but no such luck
[21:20] <godbyk> ubuntujenkins: Are you using the Lucid packages or the instructions from my email?
[21:20] <godbyk> If you followed the instructions from my email, you should uninstall all the texlive-* packages using synaptic.
[21:20] <godbyk> And make sure you do *not* run the install-pkgs.sh script.
[21:21] <ubuntujenkins> I will try again from the start
[21:21] <dutchie> it's stopped compiling now :)
[21:21] <dutchie> ! Misplaced alignment tab character &.
[21:21] <godbyk> dutchie: put a backslash in front of the ampersand.
[21:22] <godbyk> & has special meaning, so use \& to get a printed ampersand.
[21:22]  * dutchie curses whoever changed it and didn't test the build
[21:26] <ubuntujenkins> my bad dutchie I think that might be my fault as you know I can't test it
[21:27] <dutchie> ubuntujenkins: no worries then
[21:27] <ubuntujenkins> I do normaly test
[21:27] <dutchie> \textfeild is an easy mistake to make
[21:27] <ubuntujenkins> I try and think about lots of things at once so thats why I usualy check it
[21:29] <ubuntujenkins> and make mistakes
[21:30] <godbyk> brb, I'm going to reheat some leftovers.
[21:30]  * ubuntujenkins starts compiling textlive again
[21:30] <ubuntujenkins> thanks for checking dutchie
[21:31] <godbyk> ubuntujenkins: I hope you're just installing it, not compiling it. :)
[21:32] <ubuntujenkins> I ment installing :)
[21:37] <godbyk> back now.
[21:57] <godbyk> Hey, komsas, did we get you up and running last time or were there still problems? (I can't recall where we left off.)
[22:00] <komsas> godbyk: hehe, we are good !
[22:00] <godbyk> cool.  just checking!
[22:03] <komsas> we celabrate my birthday :)))
[22:07] <komsas> http://img26.imageshack.us/my.php?image=20100220000601.jpg
[22:09]  * humphreybc is back
[22:09]  * humphreybc has 62 emails
[22:09] <dutchie> \o/
[22:10]  * dutchie has broken his computer
[22:10] <humphreybc> lol
[22:11] <humphreybc> i managed to get some work done
[22:11] <humphreybc> i did some heavy editing on the prologue, chapters 1, 2, 5, 7 and 8
[22:11] <humphreybc> hopefully it's not going to destroy the branch if I merge them...
[22:15] <godbyk> humphreybc: Oh, figures.  I edited some of your stuff while you were out.
[22:15] <godbyk> But my edits were global find/replace stuff, so feel free to just overwrite them completely for now.
[22:15] <humphreybc> godbyk: yeah i just got a conflict with prologue and installation
[22:15] <humphreybc> okay cool
[22:15] <humphreybc> i'm not sure what happens with the conflicts
[22:16] <humphreybc> i'm going to push anyway :|
[22:16] <godbyk> make sure it compiles first
[22:16] <humphreybc> kk
[22:16] <godbyk> and check for "<<<<<" in the source files.. if they exist, then the merge wasn't so good.
[22:17] <dutchie> or run "bzr conflicts"
[22:17] <humphreybc> compiles okay, i've run bzr conflict resolve <file> on the two files
[22:17] <godbyk> ok
[22:17] <humphreybc> I do have a lot of "<<<<<<< TREE" in the source files
[22:18] <dutchie> http://doc.bazaar.canonical.com/bzr.0.92/en/user-guide/conflicts.html
[22:18] <ubuntujenkins> huphreybc is back yey TommyBrunn and I have had some fun with quickshot
[22:18] <humphreybc> should I just remove that stuff?
[22:18] <godbyk> ah, yeah, you'll want to fix those. :)
[22:18] <humphreybc> i kept a backup of my changes, i'll just overwrite the files
[22:18] <godbyk> yeah, just overwrite the files with your changes.
[22:19] <humphreybc> godbyk: what's prologue.aux?
[22:19] <godbyk> if it's problematic, you can pull a completely fresh branch, then put in your changes and push.
[22:19] <godbyk> humphreybc: it's a temp file created by latex.
[22:19] <godbyk> it can safely be ignored.
[22:19] <godbyk> it gets regenerated each time you compile.
[22:19] <humphreybc> oh true
[22:19] <ubuntujenkins> godbyk it has finished installing an it says Most importantly, add /usr/local/texlive/2009/bin/x86_64-linux silly question but add it to where? and how?
[22:20] <godbyk> ubuntujenkins: I think they mean to add that to your PATH environment variable.
[22:20] <dutchie> in your ~/.bashrc, add "export PATH=/usr/local/texlive/2009/bin/x86_64-linux:$PATH"
[22:20] <humphreybc> okay seems to be all good now, i've made a lot of changes to the big chapters
[22:20] <humphreybc> so everyone pull pull pull!
[22:20] <godbyk> if you had the install program create symlinks, then you won't have to add it to your PATH
[22:21] <ubuntujenkins> I did make it do symlinks I thought e looked important
[22:21] <humphreybc> how's the prep going for 48 hours?
[22:21] <godbyk> humphreybc: eh, haven't really started yet.  it's on my TODO list. :-)
[22:21] <godbyk> ubuntujenkins: cool, then you should be okay.
[22:22] <humphreybc> righto, as a team how are we going? times and stuff?
[22:22] <godbyk> humphreybc: no clue, I've had my head in the sand most of this week.
[22:22] <humphreybc> righto
[22:22] <dutchie> humphreybc: see ML
[22:22] <humphreybc> the NOTICE email dutchie?
[22:23] <dutchie> cjohnston is also here to perform some sort of co-ordination with the classroom team
[22:23] <dutchie> humphreybc: I forget
[22:23] <humphreybc> okay.. so jamin and ryan can't do their sessions?
[22:23] <cjohnston> ?
[22:23] <dutchie> https://lists.launchpad.net/ubuntu-manual/msg00713.html
[22:23] <dutchie> cjohnston: just a passing mention, now our project lead is back
[22:23] <cjohnston> gotcha
[22:24] <humphreybc> okay cool dutchie that was the email i read
[22:24] <dutchie> great
[22:24] <dutchie> we could do with someone to fill in jamin's sessions
[22:24] <dutchie> the wiki should be up to date
[22:25]  * ubuntujenkins can see a manual again
[22:30]  * humphreybc pulls the quickshot branch and prepares to be amazed
[22:30] <ubuntujenkins> I also have a quickshot branch bzr branch lp:~ubuntujenkins/quickshot/luke-quickshot
[22:30] <humphreybc> is that for merges?
[22:31] <ubuntujenkins> no its for experiments a I can't do python quite right yet mine does have some detection of if you are in the quickshot user but I can't skip the next button on the first screen.
[22:31] <humphreybc> okay
[22:31] <humphreybc> has Tommy not pushed his new stuff?
[22:31] <humphreybc> oh he just hasn't set up bzr properly :)
[22:32] <humphreybc> TommyBrunn: run bzr whoami
[22:32] <ubuntujenkins> Tommy and I worked together on stuff he coreccted / made better the suff i did and taught me some stuff
[22:33] <humphreybc> bzr whoami "Joe Bloggs<EMAIL_ADDRESS>[22:33] <humphreybc> TommyBrunn: that way you get karma when you push to the branch
[22:34] <ubuntujenkins> When you click the ok button in the password window it is slow as we had to use that button to do some temporary  trickery untill we have a proper program
[22:35] <humphreybc> yup i noticed that
[22:35] <humphreybc> so what's it actually doing?
[22:36] <ubuntujenkins> Well quickshot now launches when you login to the quickshot user but to do that we had to put a copy of the quickshot branch in the quickshot user so that "quickly run" would work
[22:37] <ubuntujenkins> normaly it would be lauched by linking to the quicjshot file in /usr/bin or where ever
[22:40] <humphreybc> LOVE the new fonts
[22:41] <humphreybc> I think we need a different colour for subsections
[22:45] <ubuntujenkins> thoughts on quickshot? I know tommy has been looking into how to take the screen shots.
[22:45] <ubuntujenkins> its not much but some functinality is there
[22:45] <humphreybc> godbyk: how do i increase some line spacing? using \medskip doesn't seem to work best
[22:45] <humphreybc> ubuntujenkins: quickshot is looking good, i'll have a proper look later on
[22:46] <ubuntujenkins> sorry I am just a little excited that was such a fun day working it out and learning
[22:46] <godbyk> humphreybc: Where?
[22:46] <humphreybc> "special thanks" at the end of the credits
[22:47]  * dutchie thinks the credits needs redoing
[22:49] <ubuntujenkins> whats with the fireffox guide do not know the peoples proper names?
[22:49] <ubuntujenkins> bit of the credits
[22:49] <humphreybc> yeah the credits need a re work
[22:50] <godbyk> I agree that the credits need to be redone.
[22:50] <godbyk> Are they even up to date?
[22:51] <godbyk> humphreybc: You can try \bigskip if you want, but I think we should just revamp the credits stuff anyway.
[22:51] <humphreybc> sure
[22:52] <humphreybc> i just added some skips in and pushed anyway, but yeah, revamping the credits at some point is a good idea. no rush now though
[22:52] <godbyk> right
[23:05]  * humphreybc cannot believe the UMP facebook page has 169 fans....
[23:06] <humphreybc> does anyone know how nice android phones play with ubuntu?
[23:06] <humphreybc> i want to get an android touchscreen on a data contract so i can check my emails everywhere.... :O
[23:07] <ubuntujenkins> I think you can sync music an videos but e-mails have to be done via google or similar, At least thats what I have heard. I dodn't own one
[23:07] <humphreybc> i don't even know if you can get them in NZ
[23:08] <ubuntujenkins> I would like them but they are expensive
[23:08] <ubuntujenkins> *one
[23:08] <dutchie> humphreybc: very nice
[23:09]  * dutchie has one
[23:09] <dutchie> they just appear as a mass storage, and sync with Google Mail, Calendar and Contacts
[23:09]  * godbyk has a Nexus One
[23:10] <godbyk> Heh.. thorwil's gonna hate me now. :)
[23:10] <humphreybc> godbyk: why?
[23:10] <godbyk> He keeps bugging me that he doesn't like the square bullets.  I just changed it to the Ubuntu logo (playing around).
[23:10] <godbyk> Don't get too attached!
[23:12] <humphreybc> lol
[23:12] <ubuntujenkins> ubuntu logos :)
[23:14] <humphreybc> do iphones work with ubuntu?
[23:14] <humphreybc> (silly question i know but they have a good deal on them at the moment)
[23:14] <dutchie> no
[23:14] <ubuntujenkins> they don't
[23:15] <humphreybc> why does NZ charge so much for phones
[23:15] <dutchie> you need a better country
[23:15] <humphreybc> haha
[23:16] <godbyk> Also, you can't turn to the dark side and buy an iphone.. c'mon!
[23:16] <dutchie> you do definitely need linux on your phone :)
[23:17]  * dutchie wonders what's going to happen to the n900 now moblin/maemo have merged
[23:17] <godbyk> hey, humphreybc, are you editing your prologue or installation chapters at the moment?  If not, I'm gonna go fiddle with 'em for a sec.
[23:17] <humphreybc> nope
[23:17] <humphreybc> go for it
[23:17] <godbyk> I saw that.  Choosing between an n900 and a nexus one was tough.
[23:17] <humphreybc> http://www.trademe.co.nz/Mobile-phones/2degrees/auction-272572117.htm
[23:17] <godbyk> went with the nexus one 'cause it looked like a better *phone*.
[23:18] <dutchie> I went for an android because I ♥ google
[23:18] <dutchie> it's not even deliberate
[23:20] <humphreybc> haha
[23:20] <humphreybc> what do you think of that thing? it's unbranded but it does have android
[23:20]  * dutchie is quite happy with his pulse
[23:21] <humphreybc> http://www.trademe.co.nz/Mobile-phones/2degrees/auction-272596277.htm
[23:21] <dutchie> isn't the magic the winmo one?
[23:21] <humphreybc> i don't think so
[23:21] <humphreybc> not sure
[23:21] <humphreybc> none of the actual service providers stock them
[23:22] <humphreybc> (android phones)
[23:22] <humphreybc> so i couldn't get an account and get the phone for free
[23:23] <godbyk> humphreybc: I'd buy an unlocked Nexus One. :-)
[23:23] <humphreybc> yeah but they're too pricey
[23:24] <humphreybc> i think i'll just hold out till a carrier launches one with some good pricing
[23:25]  * dutchie got a pulse on pay as you go for £140
[23:25] <humphreybc> nice
[23:26] <humphreybc> right i'm going to go out for some lunch
[23:26] <humphreybc> catch ya'll later
[23:26] <ubuntujenkins> cya
[23:26] <dutchie> time for bed I think
[23:26] <dutchie> night
[23:26] <ubuntujenkins> night
[23:26] <ubuntujenkins> I am off too
[23:27] <dutchie> lots of work done there :)
[23:31] <godbyk> Fine, just leave. All of you!  :-)
[23:32] <ubuntujenkins> still here just thought I would tinkier with changing the language from the command line
[23:33]  * ubuntujenkins firefox in german :)
[23:33] <godbyk> cool


[01:36] <johnc4510> The new issue of the Ubuntu Weekly Newsletter #170 is now available:
[01:36] <johnc4510> https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue170


[06:53] <dholbach> good morning
[07:02] <Rhonda> Can I give access to a PPA to someone else for uploads, too?
[07:06] <rbasak> AFAIK, you have to create a team, then use the team PPA.
[07:06] <Rhonda> Thought so, thanks.
[07:19] <Rhonda> Alright, we already have the pkg-games team and I created the wesnoth-devel there, can I somehow drop a hint in my personal PPA that it's discontinued and people should rather use the other one?
[08:02] <Unit193> dholbach: Thanks for the sync!
[08:04] <rbasak> Rhonda: you can edit the "PPA description"
[08:05] <dholbach> Unit193, anytime
[14:44] <Fantu> hi, someone can sync xserver-xorg-video-qxl 0.1.4-1 from debian please? this probably will solves some bugs (including important) that make qxl unusable in ubuntu in many cases, is still at upstream version 0.1.1 of 2 years ago
[14:58] <Laney> Fantu: probably best to file a request using the 'requestsync' command from ubuntu-dev-tools


[06:30] <dholbach> hey hey
[09:26] <czajkowski> aloha
[09:42] <popey> yo czajkowski
[10:14] <czajkowski> popey: all set for tomorrow
[10:37] <popey> czajkowski: need to find my ticket
[11:58] <sakrecoer> hi, we have a bit of a situation in ubuntu studio, we don't have anyone available with upÃload right. the last member with that priviledge communuvated his retraction impromptu the day before UI freeze.
[11:59] <sakrecoer> do you thinkbo could poke on the community team mailing list if someone could help us?
[11:59] <sakrecoer> (sorry, typing from my phone)
[11:59] <sakrecoer> s/thinkbo/think i
[12:01] <sakrecoer> i've askedin #u-d and #u-motu but they seem busy and irc is a bit ephemereal, email questions echo longer
[12:09] <popey> sakrecoer: heya, that's an unfortunate situation!
[12:10] <popey> sakrecoer: I'd be inclined to ask in ubuntu-devel-discuss or -devel lists tbh
[12:10] <popey> you'll get more real devs on that list than on the community team list
[12:11] <balloons> popey, dpm. Good morning ;-) What are your plans for GCI this year, if any? I've had some students pinging me wanting to mentor or otherwise help out.
[12:21] <knome> i think it's beneficial for the project, but nobody can force canonical employees to be motivated to run the contest, and if they aren't motivated, i'm not sure if we should do it
[12:21] <knome> of course it was unfortunate that the holidays messed up some things last year, but it's really going to happen this year as well... so there needs to be backup people who can run the contest meanwhile
[12:25] <sakrecoer> thank you popey ! i will try those channels :)
[12:29] <dpm> balloons, tbh we've not started looking this time around yet. Do you have the dates?
[12:30] <balloons> dpm, no. Going by last year they will announce it in about a month, and the contest will be mid-Dev through mid-Jan like last time
[12:31] <balloons> knome, I had a lot of fun doing it, though I agree it was crazy at times. Building on last year with more invovlement and returning students / mentors I think will help
[12:43] <knome> balloons, yeah, but it was the org admins that we were lacking during the holiday season
[12:43] <knome> so more students/mentors will just make it worse in that respect...
[12:44] <knome> all i'm saying, there should be an org admin (or two) available every day
[12:44] <knome> by available i don't mean they should use their whole day running the contest... but that they can be reached and a response can be had in a sensible time, like a day or two
[12:45] <knome> AIUI, there aren't many "huge" tasks for the org admins either, it's just some stuff that only they happen to have access to
[12:45] <knome> so first and foremost, i see this as a scheduling issue
[12:45] <knome> don't let all the org admins on holiday at the same time :P
[13:18]  * popey looks at the calendar.
[13:18] <popey> nope
[14:40] <balloons> in theory an org admin should never be needed; they should be a last resort for tasks. So I do think doubling up mentors on tasks allows for more flexible holidays and timezone coverage.
[14:40] <knome> theory...
[14:41] <knome> there's a lot of *administrating* required
[16:02] <dholbach> all right my friends - I call it a day! have a good weekend!
[16:02] <popey> \o/
[16:02] <popey> Me too!
[16:03]  * popey goes to play Rocket League  😃
[16:04] <dholbach> :)
[16:06] <balloons> knome, administrating, cat herding, you pick
[16:10] <knome> balloons, yeah, somebody has to be the herder :P
[17:04] <jose> balloons: whoops, I intended to respond to that email but accidentally skipped it. I'm more than happy to help out this year again


[16:30] <mdeslaur> \o
[16:30] <chrisccoulson> o/
[16:30] <ratliff> #startmeeting
[16:30] <meetingology> Meeting started Mon Oct 31 16:30:57 2016 UTC.  The chair is ratliff. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:30] <meetingology> Available commands: action commands idea info link nick
[16:31] <ratliff> The meeting agenda can be found at:
[16:31] <ratliff> [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting
[16:31] <ratliff> [TOPIC] Announcements
[16:31] <ratliff> Nikita Yerenkov-Scott (arthur-dent) provided debdiffs for trusty-xenial for tracker (LP: #1178402)
[16:31] <ratliff> Scott Kitterman (ScottK) provided a debdiff for trusty for kdepimlibs (LP: #1631237)
[16:31] <ratliff> Simon Quigley (tsimonq2) provided a debdiff for precise for kdepimlibs (LP: #1630700)
[16:32] <ratliff> Nikita Yerenkov-Scott (arthur-dent) provided debdiffs for xenial-yakkety for openjpeg2 (LP: #1630702)
[16:32] <ratliff> Andreas Cadhalpun (andreas-cadhalpun) provided a debdiff for xenial for ffmpeg (LP: #1581156)
[16:32] <ratliff> Thank you for your assistance in keeping Ubuntu users secure! :)
[16:32] <ratliff> [TOPIC] Weekly stand-up report
[16:32] <ratliff> mdeslaur: you're up
[16:32] <mdeslaur> I'm still in the happy place this week
[16:32] <mdeslaur> I have a couple of updates I'm testing
[16:32] <mdeslaur> and I'm working on a couple of embargoed issues
[16:32] <mdeslaur> that's about it for me
[16:32] <mdeslaur> hrm, who's next?
[16:33] <ratliff> chrisccoulson ?
[16:33] <chrisccoulson> hi :)
[16:33] <chrisccoulson> this week, I'll be mostly working on https://blueprints.launchpad.net/oxide/+spec/ubuntu-webview-implementation, which is blocking a bunch of personal-related work we discussed at the sprint
[16:34] <chrisccoulson> I need to publish Oxide (it's all tested already). I don't have any other updates planned
[16:34] <chrisccoulson> that's me done
[16:35] <ratliff> I'll jump in and go next. We have some team members out due to illness, appointments, and vacation.
[16:35] <ratliff> I'm on CVE triage this week.
[16:36] <ratliff> I'm working on a project to review open CVEs for universe packages.
[16:37] <ratliff> for the record, sarnold is on bug triage and tyhicks is on community this week
[16:38] <ratliff> jjohansen: do you want to go next?
[16:38] <jjohansen> sure
[16:40] <jjohansen> I'm trying to finish up some gsettings review and related work, and I have some bugs to look at (and file), there is a memory leak, and lxd related issue with some files being passed into the container. Neither of which have bugs yet
[16:40] <jjohansen> oh and I need to upstream the change_hat() fix
[16:40] <jjohansen> cboltz really needs that one
[16:40] <jjohansen> thats it for me ratliff back to you
[16:40] <ratliff> thank you!
[16:40] <ratliff> [TOPIC] Highlighted packages
[16:41] <ratliff> The Ubuntu Security team will highlight some community-supported packages that might be good candidates for updating and or triaging. If you would like to help Ubuntu and not sure where to start, this is a great way to do so.
[16:41] <ratliff> See https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures for details and if you have any questions, feel free to ask in #ubuntu-security. To find out other ways of helping out, please see https://wiki.ubuntu.com/SecurityTeam/GettingInvolved.
[16:41] <ratliff> http://people.canonical.com/~ubuntu-security/cve/pkg/pykerberos.html
[16:41] <ratliff> http://people.canonical.com/~ubuntu-security/cve/pkg/maven-indexer.html
[16:41] <ratliff> http://people.canonical.com/~ubuntu-security/cve/pkg/revelation.html
[16:41] <ratliff> http://people.canonical.com/~ubuntu-security/cve/pkg/sanlock.html
[16:41] <ratliff> http://people.canonical.com/~ubuntu-security/cve/pkg/lib3ds.html
[16:41] <ratliff> [TOPIC] Miscellaneous and Questions
[16:41] <ratliff> Does anyone have any other questions or items to discuss?
[16:43] <ratliff> mdeslaur, jjohansen, ChrisCoulson: Thanks!
[16:43] <ratliff> #endmeeting
[16:43] <meetingology> Meeting ended Mon Oct 31 16:43:35 2016 UTC.
[16:43] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2016/ubuntu-meeting.2016-10-31-16.30.moin.txt
[16:43] <mdeslaur> thanks ratliff !
[16:46] <jjohansen> thanks ratliff
[20:58] <tsimonq2> ratliff: Thanks for the mention. ;)


[05:41] <Andre_Gondim> there is one string that still showing but all package is translated, this is string is the translator credits, is it normal?
[05:41] <Andre_Gondim> https://translations.launchpad.net/ubuntu/natty/+source/kubuntu-docs/+pots/kubuntu-docs-development/pt_BR/+translate?show=untranslated
[06:35] <arjunaraoc> Hi can some one help on how to locate the package for string Retrieving file X of Y that is displayed during ubuntu install time
[07:34] <dpm> good morning all
[07:45] <andrejz> good morning, you are early today, dpm :)
[07:46] <dpm> hey andrejz, good morning, yeah, lots of stuff to do :)
[07:49] <andrejz> i have an idea and would like your feedback on it. Keeping in mind that more and more teams are approaching 100%
[07:50] <andrejz> it might be a good idea to use popularity contest data to determine which other programs (non default) are used most ofren
[07:50] <andrejz> often
[07:50] <andrejz> to ensure teams with close to 100% of default installation are focusing on the most relavant programs
[07:51] <andrejz> what do you think, dpm? could something like that be done in 11.10 cycle?
[07:53] <dpm> andrejz, it really is a good idea, I like it. I'd like to work on stats next cycle, so perhaps we can include that, or if you know someone that would want to work on it, that'd also be awesome
[07:54] <andrejz> yeah that would be cool. we could either somehow highlight these programs (especially programs, which are translatable in laucnhpad)
[07:55] <andrejz> or even include them in statistics (with a section Ubuntu extra)
[07:55] <andrejz> or extra programs of some sort
[07:56] <andrejz> i am willing to help up in discussing the specfications and such but my programing skills are rather limited, so i cannot help with that
[07:58] <andrejz> maybe we could discuss about this at UDS ?
[07:58] <dpm> yeah, let's talk about this more in the next few days, while we plan the uds sessions
[08:03] <andrejz> another thing, which me as a coordinator of a translation group would be very much pleased with is if we could get somet of the more problematic upstreams in launchpad
[08:05] <dpm> andrejz, which ones were you thinking of?
[08:05] <andrejz> in my experience two of the most criticall (both important and hard to deal with) are compiz and wine
[08:05] <andrejz> lots of people use these two programs
[08:05] <andrejz> compiz has no working translation infrastructure, they couldn't direct me how to translate ccsm on #compiz-dev
[08:06] <andrejz> and wine is also very important and right now i am contact with one of the developers who is super busy and has no time for translations
[08:07] <dpm> andrejz, I know, we've talked about compiz before, they're willing to move to lp, but they're quite busy. I think after the release it should be easier to start this move. As per wine, I don't know much about it. Where is it hosted? Does it use gettext for translations?
[08:07] <andrejz> so  when sending .po files we need to wait for a month and a half for a reply
[08:07] <andrejz> @dpm: they just moved to gettext (po files) in december 2010 or so
[08:08] <andrejz> so theoretically they could move to lp
[08:09] <andrejz> note that it's not really necessary to move to lp (although it would be fantastic to have it). I would be very happy if could just easiyl find a .pot file  withough getting crazy sending email/browsing wiki) and then send the .po file and have it commited in a week or so
[08:10] <dpm> yeah, sounds sensible
[08:12] <andrejz> it's really frustrating when you need to waste so much additional time for a certian project
[08:12] <andrejz> if movement to launchpad is not possible, then we could think of some sort of upstream outreach program to assist
[08:12] <andrejz> with this
[08:13] <andrejz> sorry, i am making short lines due to strange empathy bug in 11.04 (already reported) :)
[19:54] <trijntje> Hi all, clutter suddenly shows new strings for natty in LP, but I've seen no request for a UI-freeze exception on the list
[19:55] <trijntje> is there anybody who knows more about this? Clutter was fully translated to dutch but now shows 38 untranslated strings


[08:16] <klebers> jeremy31, hi! we need a bug report to apply any patch to the stable kernels, could you please file one? If you have the affected hw please run "ubuntu-bug linux" on it, otherwise file a bug on launchpad against the linux package.
[22:24] <jeremy31> klebers: I don't have the hardware and the issue was a Linux Mint user using the Ubuntu 5.11 HWE


[07:00] <dholbach> good morning everyone!
[07:00] <dholbach> who do we have here for the Packaging Training session?
[07:01] <dholbach> … come on, don't be shy :)
[07:03]  * micahg will be in and out
[07:03] <dholbach> hey micahg :)
[07:03] <dholbach> ok, who else do we have here?
[07:03] <chilicuil> o/
[07:04] <sbronsted> +1
[07:04] <dholbach> awesome, seems like not everyone of the 119 folks in here are sleeping :)
[07:05] <dholbach> Ok…
[07:05] <dholbach> I had a quick look into Launchpad and found a few easy to solve bugs and I'll show you how to do it
[07:06] <dholbach> this isn't so much about the exact fix, but the proper way to do it and get it included into Ubuntu
[07:06] <dholbach> (or at least one way to get it in)
[07:06] <dholbach> Do you guys have your SSH keys already set up in Launchpad?
[07:06] <chilicuil> yep
[07:07] <sbronsted> yep
[07:07] <dholbach> awesome
[07:07] <dholbach> for those who read the logs afterwards:
[07:07] <dholbach> check if you have ~/.ssh/id_rsa.pub or ~/.ssh/id_dsa.pub
[07:07] <dholbach> if not, run: ssh-keygen -t rsa
[07:07] <dholbach> (you might need to install openssh-client first)
[07:07] <dholbach> afterwards, head to https://launchpad.net/people/+me/+editsshkeys and add your ssh key there
[07:08] <dholbach> alright… with that out of the way, let the real fun begin
[07:08] <dholbach> please run:
[07:08] <dholbach> sudo apt-get install --no-install-recommends bzr bzr-builddeb pbuilder ubuntu-dev-tools build-essential debhelper
[07:08] <dholbach> this will install a couple of tools we'll need in our endeavours
[07:09] <dholbach> bzr is a distributed version control system that's very well integrated into Launchpad
[07:09] <dholbach> bzr-builddeb is a bzr plugin that helps with building packages from bzr branches
[07:09] <dholbach> pbuilder is a tool with which you can build packages locally, in a sane and clean way (kind of what happens in a PPA, when packages get built there)
[07:10] <dholbach> ubuntu-dev-tools (and devscripts which it pulls in) gives you a set of scripts that are incredibly useful for package maintenance, especially repetitive tasks like updating the changelog, etc. become very pain-free
[07:11] <dholbach> build-essential pulls in make, gcc and other bits for very basic compilation bits
[07:12] <dholbach> and debhelper is used in almost every package as a build-dependency - it's very useful to have it around, it automates lots of things in the actual build process
[07:12] <dholbach> do you have any questions already?
[07:12] <sbronsted> no
[07:12] <chilicuil> nop =)
[07:12] <dholbach> if you do, please ask, or I'll be typing my fingers off and probably bore you to death :)
[07:12] <dholbach> alright, let's crack on then
[07:13] <dholbach> to tell bzr who you are and how things work, I did the following
[07:13] <dholbach> bzr launchpad-login dholbach
[07:13] <dholbach> bzr whoami "Daniel Holbach<EMAIL_ADDRESS>[07:14] <dholbach> launchpad-login is your personal Launchpad ID (if you're unsure, head to https://launchpad.net/people/+me and see where it redirects you, it's the bit after the "~" in the URL)
[07:14] <dholbach> and please use your own email and not mine :-P
[07:14] <micahg> otherwise bzr blame doesn't work right :)
[07:14] <dholbach> haha
[07:15] <dholbach> alright, job done, next we edit ~/.bashrc (if you use another shell, please edit whatever file else you need)
[07:15] <dholbach> and add something like this to the bottom of it:
[07:15] <dholbach> export DEBFULLNAME='Daniel Holbach'
[07:15] <dholbach> export<EMAIL_ADDRESS>[07:16] <dholbach> afterwards, you can just run    source ~/.bashrc   (or restart the session) and you should be sorted out
[07:16] <dholbach> now the packaging tools and the distributed development tools should know who you are and will make use of that information in commits and all the rest of it
[07:16] <dholbach> woohoo
[07:17] <dholbach> next, please edit ~/.pbuilderrc
[07:17] <dholbach> and add this to it
[07:17] <dholbach> COMPONENTS="main universe multiverse restricted"
[07:17] <dholbach> MIRRORSITE=http://archive.ubuntu.com/ubuntu/
[07:17] <dholbach> it will basically make use of all components (instead of just 'main') and default to the standard archive
[07:18] <dholbach> save the file and run
[07:18] <dholbach> sudo pbuilder create
[07:18] <dholbach> … which will take a bit of time
[07:18] <dholbach> it will set up the initial, minimal build environment which will be re-used for all the local test builds that you do
[07:19] <dholbach> --- now we're done with preparations ---
[07:19] <dholbach> just one more word on your development environment
[07:19] <dholbach> you need to run the latest development release, in our case maverick
[07:20] <dholbach> it doesn't need to be your main system
[07:20] <dholbach> you can have it on a spare partition or in a virtual machine or on a separate computer
[07:20] <dholbach> but you need to be able to test all the stuff in the development release that is currently being worked on
[07:20] <dholbach> https://wiki.ubuntu.com/UbuntuDevelopment/UsingDevelopmentReleases has a lot of information about how to do it and stay sane
[07:21] <dholbach> are there any questions up until now?
[07:21] <chilicuil> in the last udw u've told me that I should look at pbuilder-dist if I wanted to create diff chroots, I've done it but it doesnt seem to use the ~/.pbuilderrc, which file should I edit?
[07:21] <dholbach> hum
[07:21] <dholbach> let me find out
[07:22] <dholbach> why doesn't it use ~/.pbuilderrc?
[07:22] <dholbach> or: how did you notice it didn't?
[07:22] <chilicuil> coz I've set some vars there and it doesnt use them , for example the place where it puts the results
[07:23] <dholbach> aha, let me have a quick look at the code
[07:24] <chilicuil> if u want u can help me to find it out after the classroom I dont want to bother all the nice ppl here
[07:25] <dholbach> I suggest you have a chat with Laney or RainCT in #ubuntu-motu - they wrote the tool
[07:25] <dholbach> maybe it's a bug, it's hard for me to tell right now
[07:25] <chilicuil> I'll do
[07:25] <dholbach> awesome
[07:25] <dholbach> any more questions?
[07:26] <dholbach> alright
[07:26] <dholbach> on to bugs :)
[07:27] <dholbach> https://bugs.launchpad.net/ubuntu/+source/phpldapadmin/+bug/609403 is the first one I picked
[07:27] <ubot2> Ubuntu bug 609403 in phpldapadmin (Ubuntu) (and 1 other project) "Call to undefined function spritnf() in /usr/share/phpldapadmin/lib/functions.php on line 2180 (affects: 1) (heat: 565)" [Undecided,New]
[07:27] <dholbach> the analysis of the bug is quite good, so let's see how easy it is to fix
[07:28] <dholbach> let's get the source code first, so please run
[07:28] <dholbach>   bzr branch lp:ubuntu/phpldapadmin
[07:28] <dholbach> lp:ubuntu/<packagename> will always get you the source of the latest development release
[07:28] <dholbach> so at the moment it's identical to
[07:28] <dholbach>   bzr branch lp:ubuntu/maverick/phpldapadmin
[07:29] <dholbach> first we should check and see if the bug still exists
[07:29] <dholbach> I had a quick look and it seems to be still there
[07:29] <dholbach> daniel@miyazaki:~/phpldapadmin$ grep -r spritnf .
[07:29] <dholbach> ./lib/functions.php:				$new_value = spritnf('{SMD5}%s',base64_encode(mhash(MHASH_MD5,$password_clear.$salt).$salt));
[07:29] <dholbach> daniel@miyazaki:~/phpldapadmin$
[07:29] <dholbach> so let's go and edit lib/functions.php
[07:30] <dholbach> just search for spritnf and replace with sprintf
[07:31] <dholbach> depending on what editor you use if will show you visually how it recognises sprintf as a function name (as opposed to spritnf)
[07:31] <dholbach> at least vi did that for me
[07:31] <dholbach> ok, now save the file - bug should be fixed
[07:31] <dholbach> next we should go and document it
[07:31] <dholbach> for that   dch -i   should do the job
[07:32] <dholbach> it'll automatically start the editor with debian/changelog (which is the changelog for the debian/ubuntu releases of the package)
[07:32] <dholbach> and add a boilerplate entry for us
[07:32] <dholbach> ok, let's go through the first line one by one
[07:32] <dholbach> phpldapadmin (<IP_ADDRESS>-1.1ubuntu2) maverick; urgency=low
[07:33] <dholbach> first up is the package name
[07:33] <dholbach> in parentheses we have the version number of the package
[07:33] <dholbach> or in our case of our suggested revision later on
[07:34] <dholbach> <IP_ADDRESS> is the upstream version number, so what the phpldapadmin authors released on their web page
[07:34] <dholbach> the part after the '-' is the package revision
[07:35] <dholbach> if we split up 1.1ubuntu2, '1.1' is the debian revision we inherited from debian and '2' the revision in Ubuntu
[07:35] <dholbach> so: upstream released <IP_ADDRESS>, there was revision 1, then 1.1 in Debian and we introduced 2 changes to it
[07:36] <dholbach> if you review debian/changelog you can see at least the history of what happened in debian and ubuntu regarding the package
[07:36] <dholbach> ok, moving on: maverick is just the name of the release where you want to upload your package to (current development release always is the default)
[07:37] <dholbach> urgency=low is the default and rarely changed
[07:37] <chilicuil> question: can ubuntu revisions have point in between as debian ones?
[07:37] <dholbach> yes
[07:37] <dholbach> I think it's mostly used for stable release updates and security updates
[07:37] <dholbach> normally we just increment by one
[07:38] <dholbach> in Debian I think it's done similarly, also NMUs (non maintainer uploads, which is a concept we don't have) use those
[07:38] <dholbach> pretty safe to ignore for now :)
[07:38] <chilicuil> ok, great =)
[07:38] <dholbach> let's document our changes now
[07:39] <dholbach> I just put something in there like this:
[07:39] <dholbach>  * lib/functions.php: fixed typo: spritnf() → sprintf. (LP: #609403)
[07:39] <dholbach> so first of all I mention which file I changed
[07:39] <dholbach> then I try to explain what I did there
[07:40] <dholbach> that's the most important thing: you really don't want others to have to guess why you made a weird change somewhere
[07:40] <dholbach> or you don't want to have to guess 2 months later yourself :)
[07:40] <dholbach> we maintain all packages as one big team, so that somebody has a look at your changes later on is not unlikely :)
[07:40] <dholbach> in our case it should be pretty obvious though
[07:41] <ansgar> Does Ubuntu introduce patch systems such as quilt in d/rules or switch to source 3.0 (quilt) when they introduce changes to packages that had none before?
[07:41] <dholbach> ansgar: I wouldn't recommend it - I'd use whatever the package itself uses
[07:41] <dholbach> ansgar: but I've seen it happen
[07:42] <dholbach> just to explain: patch systems are used to store patches on top of upstream source code in packages
[07:42] <dholbach> in this case the package doesn't use any
[07:43] <dholbach> ok, with '(LP: #609403)' I document where the discussion of the bug happened
[07:43] <dholbach> or rather discussion of the change
[07:43] <dholbach> in our case it's very obvious and simple
[07:43] <dholbach> but you might have to change something and somebody might question later on where the decision and idea came from - in that case it's good to reference a bug report, an upstream commit or a mailing list discussion
[07:44] <dholbach> also by using the specific format like in '(LP: #609403)' the bug will get closed automatically once it gets uploaded to Ubuntu
[07:44] <dholbach> with that done, most of our work is done :-)
[07:44] <dholbach> can you save the file, run bzr diff and paste the output to paste.ubuntu.com and give the link here?
[07:45] <chilicuil> http://paste.ubuntu.com/473408/
[07:46] <sbronsted> http://paste.ubuntu.com/473409/
[07:47] <dholbach> chilicuil: not sure if "chilicuil<EMAIL_ADDRESS>is what you want in there, I'll leave that to you, maybe you need to edit the values in ~/.bashrc again :)
[07:47] <dholbach> apart from that it looks great
[07:47] <dholbach> sbronsted: seems you added an additional changelog entry (just edit debian/changelog and remove it)
[07:48] <dholbach> also does<EMAIL_ADDRESS>not look like a real email address :)
[07:48] <dholbach> you might want to change it in ~/.bashrc too
[07:48] <dholbach> apart from that: good work!
[07:48] <dholbach> awesome
[07:48] <dholbach> now please run
[07:48] <dholbach>   debcommit
[07:48] <dholbach> this will commit your changes locally
[07:49] <dholbach> using information from the changelog entry we just wrote
[07:49] <dholbach> so it'll automatically pass on info like that it fixes bug#609403, etc
[07:49] <dholbach> next please run
[07:50] <dholbach>   bzr push lp:~<launchpad id>/ubuntu/maverick/phpldapadmin/fix-609403
[07:50] <dholbach> I'd run
[07:50] <ClassBot> There are are 10 minutes remaining in the current session.
[07:50] <dholbach>   bzr push lp:~dholbach/ubuntu/maverick/phpldapadmin/fix-609403
[07:50] <dholbach> '~dholbach' means: use my personal namespace
[07:50] <dholbach> 'ubuntu' is the distro we're working on
[07:51] <dholbach> 'maverick' the development release we're working on
[07:51] <dholbach> 'phpldapadmin' the package in question
[07:51] <dholbach> 'fix-609403' just a name for the branch
[07:51] <dholbach> now we need to test our package
[07:51] <dholbach> please run
[07:51] <dholbach>   bzr bd -- -S -us -uc
[07:52] <dholbach> this will build a source package from your local branch (so the original upstream tarball, plus the debian/ubuntu changes, plus some descriptional file)
[07:52] <dholbach> -us -uc will just avoid signing it, it's not necessary
[07:53] <dholbach> now please run
[07:53] <dholbach>   sudo pbuilder build ../phpldapadmin_<IP_ADDRESS>-1.1ubuntu2.dsc
[07:53] <chilicuil> question: can I run there $ debuild -S -uc -us instaed?
[07:54] <dholbach> chilicuil: the arguments after 'bzr bd --' are passed to debuild
[07:54] <micahg> dholbach: good question ^^ ;)
[07:54] <dholbach> chilicuil: but it will ignore .bzr for example, etc.
[07:54] <dholbach> 'bzr bd --' is a cleaner way to do it
[07:55] <ClassBot> There are are 5 minutes remaining in the current session.
[07:55] <dholbach> alright, for me the build passed
[07:55] <dholbach> now I would try to install the package, make sure it works and all the rest of it, but  we can't cover that here
[07:56] <dholbach> (the resulting package is in /var/cache/pbuilder/result)
[07:56] <dholbach> once you're happy with all your testing, you'd run
[07:56] <dholbach>   bzr lp-lopen
[07:56] <dholbach> in your branch
[07:56] <dholbach> and it will open the branch's Launchpad page and there you can click 'Propose for merging'
[07:57] <dholbach> which will give Ubuntu Reviewers the opportunity to review your code changes and merge them into Ubuntu
[07:57] <dholbach> so to sum up what you need to do to work on a fix is:
[07:57] <dholbach>  - bzr branch lp:ubuntu/<pkg>
[07:57] <dholbach>  - cd <pkg>
[07:57] <dholbach>  # work on the fix
[07:57] <dholbach>  - dch -i        (to document it)
[07:58] <dholbach>  - debcommit      (to commit locally)
[07:58] <dholbach>  - bzr bd -- -S -us -uc    (to build a source package which you can then pass to pbuilder and other tools)
[07:58] <dholbach>  # test-build the package and test it locally
[07:59] <dholbach>  - bzr push lp:<lpid>/ubuntu/<release>/<pkg>/<branchname>
[07:59] <dholbach>  - bzr lp-open
[07:59] <dholbach>  # click 'propose for merging'
[07:59] <dholbach> DONE
[07:59] <dholbach> that's not too bad, is it?
[07:59] <ajmitch> dholbach: thanks :)
[07:59] <sbronsted> dholbach: thanks :)
[08:00] <dholbach> do you have any last questions, before I take the dog for a walk and you can ask even more questions in #ubuntu-motu and #ubuntu-packaging?
[08:00] <dholbach> :-)
[08:00] <ansgar> And remember to forward the patch upstream after this (if relevant to upstream) ;-)
[08:00] <dholbach> ansgar!
[08:00] <dholbach> very important point
[08:00] <chilicuil> awesome, thx dholbach =)
[08:00] <dholbach> https://wiki.ubuntu.com/Bugs/HowToFix has more info on when to send stuff upstream and the like
[08:01] <dholbach> https://wiki.ubuntu.com/MOTU/GettingStarted links to a lot of other important stuff like the packaging guide, ubuntu development procedures and all the rest of it
[08:01] <dholbach> unfortunately we only got one bug done, but we at least covered a bunch of details in there
[08:01] <dholbach> https://bugs.edge.launchpad.net/ubuntu/+source/sbackup/+bug/384334 was the other one I picked earlier today
[08:01] <ubot2> Ubuntu bug 384334 in sbackup (Ubuntu) "Bad grammar in "Backup Now!" tooltip (affects: 1) (heat: 8)" [Undecided,New]
[08:02] <dholbach> if there are no more questions right now, I'll leave you be
[08:02] <dholbach> and thanks a lot for your interest
[08:02] <kermiac> thanks for the great session dholbach :)
[08:02] <dholbach> hope you enjoyed it and will enjoy it even more to make Ubuntu even better :)
[08:02] <sbronsted> dholbach: How often is http://qa.ubuntuwire.org/ftbfs/ updated?
[08:03] <dholbach> sbronsted: maybe wgrant in #ubuntu-motu knows - I'm afraid I don't know
[08:03]  * chilicuil is gonna fix 384334 if nobody stop him
[08:05] <dholbach> alright my friends - thanks again, all further questions can go into one of the other channels
[08:05] <dholbach> I'll put up logs later on
[08:05] <dholbach> byeeeeeeeeeeee
[09:04] <JoeMaverickSett> was there any session earlier?
[09:05] <mpounta> yeap
[09:05] <JoeMaverickSett> where is the log for that?
[09:06] <mpounta> i don't know, first time i attend here. and i was a bit late too. so i am searching for the log too
[09:06] <JoeMaverickSett> oh! okie! i'll also try to find it.
[09:33] <JoeMaverickSett> could someone give me the link of the log for the today's session?
[09:33] <qwebirc32079> http://irclogs.ubuntu.com/2010/08/05/%23ubuntu-classroom.txt
[09:34] <JoeMaverickSett> thank you! qwebirc32079.
[19:44] <kosaidpo> hello people
[19:44] <kosaidpo> is it gmt +1h ight ??
[19:44] <pleia2> @now
[19:44] <pleia2> hmm
[19:45] <pleia2> Thu Aug  5 18:45:07 UTC 2010
[19:45] <pleia2> the next class is on saturday
[19:45] <kosaidpo> ohh
[19:45] <kosaidpo> okies
[19:45] <kosaidpo> good
[19:45] <kosaidpo> pleia2: tnx : )
[19:45] <pleia2> sure thing
[19:45] <kosaidpo> this is my first time : )
[19:46] <kosaidpo> i missed those past clases : (
[19:47] <pleia2> logs are online here: https://wiki.ubuntu.com/Classroom
[19:48] <pleia2> and if we haven't gotten around to updating that page, they're updated every hour at irclogs.ubuntu.com
[20:08] <kosaidpo> uhmm its ;07 minutes over here or my pc is wrong
[20:08] <pleia2> kosaidpo: the only class today was at 06:00 UTC
[20:09] <pleia2> the next one isn't until saturday
[20:10] <kosaidpo> oh oh oh meanin i missed it already ??
[20:10] <kosaidpo> well utc = gmt-1
[20:10] <kosaidpo> ami wong
[20:11] <pleia2> as far as I know, UTC and GMT are the same
[20:11] <pleia2> at the class was at 6AM
[20:11] <pleia2> s/at/and
[20:11] <kosaidpo> ohh
[20:11] <kosaidpo> okies pleia2
[20:11] <kosaidpo> txn
[20:11] <kosaidpo> have fun people
[20:11] <kosaidpo> peace out


[12:20] <lissyx> bandali, can you check with procenv this worker does have 16GB of RAM ?
[21:44] <bandali> lissyx, https://launchpadlibrarian.net/673872688/buildlog_snap_ubuntu_jammy_armhf_firefox-snap-core22-preview_BUILDING.txt.gz
[21:45] <bandali> i don't immediately see the memory in procenv's output, but per 'free -h' it does indeed seem to have 16 GB