=== smartboyhw is now known as Guest59018
=== smartboyhw_ is now known as smartboyhw
=== sagaci_ is now known as sagaci
=== mmrazik is now known as mmrazik|lunch
=== yofel_ is now known as yofel
=== mmrazik|lunch is now known as mmrazik
=== _salem is now known as salem_
[13:56] <mvo> jibel: hello, can you give me a hint on this jenkins error: "sh: 0: Can't open /tmp/tmp.1kRfnWr0Ov/dsc0-build/software-center-5.3.10/debian/tests/run-tests" ? from the latest upload. I guess the real issue is "-su: line 0: cd: /tmp/tmp.1kRfnWr0Ov/dsc0-build/software-center-5.3.10: Permission denied" - but why?
[14:04] <jibel> mvo, I'm on it. autopkgtest set TMPDIR and set it to 0700
[14:04] <jibel> mvo, I'll apply the same /fix/ pitti uses for his tests
[14:05] <mvo> jibel: if you tell me what the fix is I will merge it :)
[14:05] <pitti> agreed; setting this private $TMPDIR leads to nothing but trouble in a lot of tests :(
[14:05] <pitti> just run the tests under env -u TMPDIR, or "unset TMPDIR" in debian/tests/*
[14:15] <mvo> pitti: cool, thanks, trying this now
[14:16] <xnox> bug 1043853 filed against ubiquity, when a person runs a command in a terminal.....
[14:16] <ubot5> Launchpad bug 1043853 in apt (Ubuntu) "Apt ignored few packages on executing 'sudo apt-get update'" [Undecided,Incomplete] https://launchpad.net/bugs/1043853
[14:16]  * xnox refiled it....
[14:23] <jibel> xnox, he seems to be using ubiquity for everything e.g bug 1043860
[14:23] <ubot5> Launchpad bug 1043860 in ubiquity (Ubuntu) "Manual setting of time and date has no effect on the clock present on the desktop " [Undecided,New] https://launchpad.net/bugs/1043860
[14:24] <xnox> jibel: My theory is that iso tracking website, on the bug reporting page suggests to file bugs against ubiquity
[14:24] <xnox> jibel: maybe they should be changed more urgently to a "link to bugsquad wiki page" or a paragraph "select an appropriate package, if all fails then use ubiquity package"
[14:24] <xnox> launchpad has an excellent package search facility =)
[14:27] <jibel> the tracker should refer to https://wiki.ubuntu.com/Testing/ISO/Procedures#Bugs
[14:30] <jibel> balloons, could we replace the content of http://iso.qa.ubuntu.com/qatracker/milestones/219/builds/22117/buginstructions with the section https://wiki.ubuntu.com/Testing/ISO/Procedures#Bugs
[14:30] <jibel> balloons, what do you think ?
[14:32] <smartboyhw> jibel: Let
[14:32] <smartboyhw> 's wait for balloons to wake up:)
[14:33] <smartboyhw> ping balloons
[14:36]  * balloons is reading
[14:36] <smartboyhw> balloons: Who shall be the chairs for September QA meetings?
[14:38] <balloons> jibel, I think xnox's summary for how to report bugs is pretty good
[14:38] <balloons> basically changing the instructions and of course, adding the bug wiki pages you mentioned as required reading will help out
[14:39] <balloons> this looks interesting; https://wiki.ubuntu.com/DebuggingProcedures
[14:41] <smartboyhw> ...
[14:42] <balloons> anyways, let me try and update the instructions and see what everyone thingks
[14:43] <smartboyhw> OK
[14:43] <mvo> jibel, pitti: do you have a example I can look at? I just can't figure it out :/ keeps failing in my adt test VM
[14:44] <pitti> mvo: gvfs and apport
[14:44] <pitti> one does "unset TMPDIR"
[14:44] <pitti> the other "env -u TMPDIR /usr/share/apport/testsuite/run 2>&1"
[14:45] <mvo> ta!
[14:59] <balloons> jibel, xnox http://iso.qa.ubuntu.com/qatracker/milestones/219/builds/22117/buginstructions
[14:59] <balloons> need to fix the formatting a bit, but thoughts?
[15:00] <smartboyhw> balloons: I saw it and it's good.
[15:01] <xnox> balloons: yeah, add jquery AJAX UI to make it a flowcharts with yes/no questions like in magazines with Text-to-Speech automated announcements "Press 1 if yes, Press 2 if no, Press 3 to repeat" and it will be grand =)
[15:02] <xnox> balloons: but honestly. Yes it is good =)
[15:02] <balloons> heh.. :-)
[15:02] <balloons> that would be nice
[15:02] <smartboyhw> ;_)
[15:02] <balloons> alright, so i'll clean up the formatting a little and then replace the instructions on the rest
[15:08] <xnox> balloons: it should be one line
[15:08] <xnox> balloons: e.g. table with three columns
[15:08] <balloons> not sure I can do a true table
[15:08] <balloons> but yes, keep describing
[15:13] <xnox> balloons: http://paste.ubuntu.com/1176073/
[15:13] <xnox> it is actually fixed-size in the terminal
[15:13] <balloons> ahh, I see it
[15:14] <xnox> i should not scroll the window
[15:14] <balloons> yes.. it's way to olong
[15:14] <xnox> it's a short paragraph not a manual =)
[15:15] <balloons> heh.. the trouble is those pre tags
[15:15] <balloons> maybe I'll bold instead
[15:26] <balloons> xnox, http://iso.qa.ubuntu.com/qatracker/milestones/219/builds/22117/buginstructions
[16:12] <bdmurray> xnox, balloons: that buginstructions page misses plymouth as a posibility and I don't think it should have the 'if unknown' line.  Actually, I don't think 'ubuntu-bug ubuntu' would work at all
[16:13] <mvo> jibel, pitti: https://code.launchpad.net/~mvo/software-center/adt-you-make-my-life-hard/+merge/122100 as the tree is alreaady created as root :/ feedback welcome, then it should be in reasonable state (fingers crossed)
[16:14] <balloons> bdmurray, alright we can keep iterating on it
[16:14] <balloons> the goal is to get more bugs in the proper location
[16:14] <balloons> that will help everyone :-)
[16:15] <bdmurray> right I understand and appreciate the work
[16:15] <xnox> bdmurray: true, hard to separate grub2/xorg/plymouth/linux though, as I myself rarely know where the difference lies.
[16:15] <jibel> mvo, heh, I did exactly the same :)
[16:15] <balloons> your right.. ubuntu-bug ubuntu doesn't work.. I was supposed to find something for that
[16:15] <balloons> whoops
[16:15] <xnox> "package ubuntu does not exist"
[16:15] <bdmurray> well plymouth is 'graphics before login' and xorg is graphics 'during and after login'
[16:15] <jibel> mvo, I not sure it really make sense that adt creates averything as root and the top directory permission set to 0700
[16:16] <xnox> bdmurray: unless it's compiz or lightdm problem
[16:16] <xnox> ;-)
[16:18] <bdmurray> well yes but I think xorg and plymouth are better starting points than just xorg
[16:19] <xnox> bdmurray: sure. you know better to be honest =) i was stabbing the darkness trying to stop the flood of ubiquity bugs about $random_packages =))))
[16:20] <bdmurray> oh also all those +filebug links will only work if you are in ubuntu bug control
[16:20] <balloons> yea, adding another data point isn't inhernetly bad.. I don't want to overload people, but we can keep the instructions simple, it will help
[16:21] <balloons> bdmurray, they seem to work fine for me: https://launchpad.net/~nskaggs/+participation
[16:21] <balloons> unless I'm somehow special..
[16:21] <bdmurray> balloons: indeed you are special as a member of ubuntu bug control
[16:22] <bdmurray> oh
[16:23] <bdmurray> for you it is probably being in ubuntu-drivers then
[16:25] <balloons> bdmurray, ahh.. well, I think you've got the problem now
[16:25] <balloons> how can we achieve the goal?
[16:26] <balloons> I didn't realize the +fileabug was special :-)
[16:26] <bdmurray> in my mind the goal is to get high quality bug reports and the way to do that is to have people report them using apport
[16:27] <bdmurray> so there should be no OR
[16:31] <bdmurray> I realize this is a rather hard line stance and there are cases where people's system won't boot etc but we just get so many low quality bug reports with +filebug being open
[16:32] <balloons> bdmurray, yes I understand that
[16:33] <balloons> so +filebug is closed to most folks?
[16:33] <balloons> I also use that for general testing purposes.. like from a ppa
[16:33] <balloons> or is it only closed for some packages?
[16:34] <bdmurray> balloons: yes, it redirects people to the how to file a bug documentation on help.ubuntu.com
[16:35] <balloons> ok, so the links as they are now are re-directs on how to file a bug for most people
[16:35] <bdmurray> yes, which seems odd to me as the chart will have
[16:36] <bdmurray> 'ubuntu-bug xorg' or a link to a web page that says 'ubuntu-bug xorg'
[16:36] <balloons> ok, we need to provide something for folks that have unbootable systems..
[16:37] <balloons> so what's the best way to do that if the system won't boot?
[16:37] <bdmurray> ask somebody for help
[16:37] <balloons> we just need proper recommendations for all scenarios
[16:38] <balloons> bdmurray, in some cases it's not booting because of a bug.. I mean, we could ask them to boot an older livecd.. maybe that's just a fringe case to indvidually deal with
[16:38] <bdmurray> yes an older live cd or a previous release if it used to boot
[16:39] <bdmurray> or read documentation about how to boot without splash and kernel options....
[16:40] <bdmurray> https://wiki.ubuntu.com/DebuggingKernelBoot
[17:57] <balloons> bdmurray, ok, so we'll remove the file-bug links
[17:58] <balloons> and in general force folks to use ubuntu-bug to report.. what if the package is unknown to them? Again should we just remove ubuntu (no package) as an option for reporting?
[18:07] <bdmurray> balloons: then the find the right package documentation may help
[18:08] <balloons> right.. ok, so I made all those changes
[18:08] <bdmurray> balloons: or that documentation might be in the reportingbugs page
[18:08] <bdmurray> balloons: great, thanks!
[18:08] <balloons> they can always (and they do) ask for help
[18:08] <balloons> that might be better than the generic filing
[18:11] <balloons> thank you bdmurray :-)
=== salem_ is now known as _salem
[22:28] <phillw> balloons: ping
[22:36] <leadsled> is reporting a bug for util-linux package the same as for any other package?
[22:37] <phillw> leadsled: it should be?
[22:37] <leadsled> ok thanks
[22:39] <phillw> too late.. he's gone :/
[23:53] <leadsled> when does the pre-beta testing in quantal officially end?