=== JoeSett is now known as JoeMaverickSett
=== JoeSett is now known as JoeMaverickSett
=== bilalakhtar_ is now known as cdbs
[15:14] <bcurtiswx> nigelb, so why the dislike towards SVN? :P
[15:14] <nigelb> bcurtiswx: I like git :D
[15:14] <nigelb> bcurtiswx: and generally, dvcs
[15:14] <bcurtiswx> nigelb, ah i guess i've used all before and have gotten used to the differences for the most part
[15:15] <nigelb> bcurtiswx: yeah, I've used all of them at some point
[15:15] <nigelb> bcurtiswx: oh btw, want to talk about upstreaming bugs at UDW?
[15:15]  * nigelb is in recruitment mode
[15:16] <bcurtiswx> what day
[15:16] <nigelb> bcurtiswx: pick an empty slot https://wiki.ubuntu.com/UbuntuDeveloperWeek/Timetable#preview
[15:31] <nigelb> bcurtiswx: final decision? :)
[15:32] <bcurtiswx> nigelb, i'm thinkin :)
[15:33] <nigelb> hehe
[15:33] <nigelb> bcurtiswx: feel free to team up with pedro or hggdh or charlie-tca :D
[15:34] <hggdh> heh
[15:35] <nigelb> the very subtle form of recruitment ;)
[15:35] <bcurtiswx> any of you want to do a session on "Bugs: Head to Dead.
[15:35] <bcurtiswx> "
[15:35] <bcurtiswx> maybe two sessions worth
[15:36] <bcurtiswx> OK, maybe that was a bad play on words
[15:37] <bcurtiswx> Where we triage a couple bugs live, from NEW to Triaged
[15:39] <bcurtiswx> hggdh gets the interest with the obvious public attraction, and i just get to stamp my name on it. how about it :P
[15:39] <charlie-tca> Do you really want to start at "New" if you are talking to developers?
[15:40] <bcurtiswx> charlie-tca, good point.
[15:40] <bcurtiswx> but how well do devs understand our triaging techniques?
[15:41] <charlie-tca> bcurtiswx: valid point, too. Some do, perhaps most do not?
[15:43] <bcurtiswx> charlie-tca, i don't know.
[15:45] <bcurtiswx> hggdh, charlie-tca, bdmurray: Would a "Bug Triage: NEW to TRIAGED" really benefit dev's in your own opinions
[15:48] <bdmurray> bcurtiswx: that seems more appropriate for open week
[15:48] <charlie-tca> A developer working his bugs doesn't really care what our steps are. If they can fix the bug, it could jump from New to Fixed in one step
[15:50] <bcurtiswx> nigelb, i think that best sums up that.  Sorry :)
[15:50] <nigelb> bcurtiswx: well, you could always talk about upstreams and their importance ;)
[15:51] <bdmurray> One thing I've talked about in the past is how to get better quality bug reports
[15:51] <bdmurray> by writing apport hooks for example
[15:52] <nigelb> oh, apport hooks would be a fun session
[15:52] <nigelb> when I wrot them, I kept looking at your sessions bdmurray :)
[15:52] <charlie-tca> That would be good, but I know nothing about that...
[15:53] <bcurtiswx> nigelb, you have your own session to run then ;)
[15:54] <nigelb> oh no
[15:54] <nigelb> how did I fall into that trap
[15:54] <nigelb> :-P
[15:54] <nigelb> bdmurray: can you help me if I'm willing to take an apport session? :)
[15:55] <bdmurray> nigelb: sure when is it?
[15:55] <nigelb> 1600 4th March?
[15:57] <bdmurray> okay that's a fair bit of time
[15:58] <nigelb> \o/
[15:58] <nigelb> session added
[16:23] <Gartral> hello, I see a fix was posted for Gobi2k 3g radios in Kernel, (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/554099?comments=all) but I can't use that Kernel due to a TPM-locked Kernel architecture.. and I was hoping the needed driver was available as a Module.. my other problem is I can't compile the module myself as until i fix 3g in ubuntu, my computer won't have internet.
[16:23] <ubot4> Launchpad bug 554099 in linux-backports-modules-2.6.32 (Ubuntu Maverick) (and 9 other projects) "Qualcomm Gobi 2000 3G (gobi_loader/qcserial) broken (affects: 73) (dups: 4) (heat: 424)" [Undecided,Invalid]
[16:24] <Gartral> yes ubot4 that's the package and bug.
[16:41] <gondoi> I'm a little confused on the SRU instructions...
[16:41] <gondoi> I want to submit an SRU for this bug
[16:41] <gondoi> https://bugs.launchpad.net/ubuntu/+source/munin/+bug/699967
[16:41] <ubot4> Launchpad bug 699967 in munin (Debian) (and 2 other projects) "Empty list of plugins/services with hostname containing uppercase letters (affects: 2) (dups: 1) (heat: 20)" [Unknown,Confirmed]
[16:41] <gondoi> but I'm not sure whether to submit it in that bug or start a new one
[16:42] <gondoi> can anyone help me?
[16:42] <charlie-tca> a little patience is appreciated. We are all volunteers, not sitting looking at the monitor waiting for questions.
[16:42] <gondoi> same here
[16:43] <gondoi> just throwing it out there and waiting for a reply
[16:43] <charlie-tca> and expecting an answer within a minute?
[16:44] <Gartral> hello, I see a fix was posted for Gobi2k 3g radios in Kernel, (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/554099?comments=all) but I can't use that Kernel due to a TPM-locked Kernel architecture.. and I was hoping the needed driver was available as a Module.. my other problem is I can't compile the module myself as until i fix 3g in ubuntu, my computer won't have internet.
[16:44] <ubot4> Launchpad bug 554099 in linux-backports-modules-2.6.32 (Ubuntu Maverick) (and 9 other projects) "Qualcomm Gobi 2000 3G (gobi_loader/qcserial) broken (affects: 73) (dups: 4) (heat: 424)" [Undecided,Invalid]
[16:44] <charlie-tca> gondoi: Use the same bug, nominate for series "maverick"
[16:44] <gondoi> dude, it wasn't intended as a bump... just asking for assistance
[16:44] <gondoi> thank you charlie-tca
[16:44] <charlie-tca> You are welcome
[16:44] <Gartral> (if waiting 20 minutes between posts aint long enough, sorry, trying too compensate for joins which i turned off...
[16:45] <charlie-tca> Gartral: I would suggest asking in #ubuntu-kernel, also, for that issue. They might have a workaround you can use.
[16:46] <shankhs> hi
[16:47] <Gartral> charlie-tca: maybe, maybe not, keep in mind im forced too use a kernel that I don't even have headers for... so compiling my own module isn't an option
[17:04]  * micahg wonders if we're having a meeting
[17:04] <micahg> hggdh: charlie-tca: yofel: bdmurray ^^^
[17:05] <Gartral> ?/?
[17:05] <shankhs> Hi i am very much eager to participate in bug day (10 feb ) but I have never done any bug-fixing for ubuntu before . Also I have never saw the code of OpenOffice or LibreOffice. How do I get started with this? I have signed the ubuntu code of conduct and read the Triage guide. Thanks a lot for the help
[17:05]  * yofel totally forgot about it, thanks for the ping
[17:06] <micahg> shankhs: can you stick around another hour, we're supposed to have a meeting now, but it might not happen
[17:06] <shankhs> micahg: sure!
[17:07]  * micahg doesn't see pedro
[17:09] <bdmurray> micahg: pedro is on holiday
[17:09] <micahg> bdmurray: ah, good for him :)
[17:09] <micahg> bdmurray: well, should we have a meeting or defer 1 week?
[17:10] <bdmurray> micahg: looking at the agenda it needs some cleanup and no announcement was sent so I'd pefer to wait
[17:10] <bolster> Hey all, I'm new to the bugsquad (and haven't exactly contributed yet, but exams finished this week so I should be a productive human being tomorrow). Have read most / all of the knowledgebase so hopefully can hit the ground running as soon as I can block off some time for it :D
[17:11] <micahg> bdmurray: ok, makes sense
[17:11] <yofel> +1
[17:14] <bdmurray> okay, I'll take care of the agena, email and channel topic
[17:15] <micahg> bdmurray: thanks,
[17:16] <micahg> shankhs: so, it's just a matter of installing LIbreOffice and seeing if you can reproduce the OpenOffice bugs, if so, add a bug task for LibreOffice
[17:16] <micahg> I think
[17:16] <bdmurray> right you don't need to know the code to help out triaging bug reports
[17:17] <micahg> bdmurray: are we adding tasks for LibreOffice or moving the bugs? (not everyone might know if something's SRU worthy or not)
[17:18] <shankhs> micahg bdmurray : thanks any more pointers
[17:18] <bdmurray> micahg: adding seems the easiest to me
[17:19] <micahg> bdmurray: ok, thanks
[17:20] <vish> bdmurray: hi.. when you get some time, could you have a look at Bug #659947 ? thanks! :)
[17:20] <ubot4> Launchpad bug 659947 in launchpad "Users, unfamiliar with bug-triage, often confuse 'Triaged' and 'Confirmed' status (affects: 2) (heat: 10)" [Low,Triaged] https://launchpad.net/bugs/659947
[17:34] <bdmurray> vish: what are you looking for with that bug?
[17:35] <vish> bdmurray: some solution to prevent redoing the confirmed -> triaged work..
[17:36] <vish> ie, not revisiting the triaged bugs again..
[17:37] <vish> bdmurray: it is a follow up bug, to the earlier one where i suggested locking down the permissions as to who changes those, but their feedabck was a better solution was to looking at reducing the number of statuses
[17:38] <vish>  to merge triaged and confirmed
[17:38] <Gartral> hello, I see a fix was posted for Gobi2k 3g radios in Kernel, (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/554099?comments=all) but I can't use that Kernel due to a TPM-locked Kernel architecture.. and I was hoping the needed driver was available as a Module.. my other problem is I can't compile the module myself as until i fix 3g in ubuntu, my computer won't have internet.
[17:38] <ubot4> Launchpad bug 554099 in linux-backports-modules-2.6.32 (Ubuntu Maverick) (and 9 other projects) "Qualcomm Gobi 2000 3G (gobi_loader/qcserial) broken (affects: 73) (dups: 4) (heat: 424)" [Undecided,Invalid]
[17:38] <bdmurray> vish: okay
[17:39] <micahg> vish: I think that's a bad idea, confirmed means there's a real bug, but not enough information to work on it, triaged means there's enough information to work on it
[17:40] <vish> micahg: yea.. thats how i thought so too.. but sinzui and mpt suggestion seemed OK.. but i'll take whatever fixes the current situation ;)
[17:42] <micahg> Gartral: you might want to ask in #ubuntu-kernel about that
[17:53] <ddecator> assuming my calendar is correct, there is a bugsquad meeting starting in a few minutes, right?
[17:55] <micahg> ddecator: calendar is wrong :)
[17:56] <ddecator> micahg: what the, i swear i copied it from the fridge calendar..
[17:57] <ddecator> micahg: ...from your calendar
[17:57] <micahg> ddecator: yeah, I saw that, idk why it was set for 18:00, meeting was 17:00 I thought, but in any case, no announcement and an old agenda postponed the meeting
[17:57] <ddecator> micahg: ah, gotcha. when is it now?
[17:58] <micahg> ddecator: TBA
[17:58] <ddecator> micahg: alright, thanks
=== zyga is now known as zyga-afk
[19:33] <Rcart> hello, there are logs available for the talk that took place today?
[19:34] <ddecator> Rcart: the meeting? it's being rescheduled
[19:36] <Rcart> ddecator: Oh, great. 10 February right?
[19:36] <ddecator> Rcart: i don't think a new time has been determined yet
[19:37] <charlie-tca> It should change in the topic here when it is decided
[19:37] <Rcart> ddecator: Thanks, I was confusing it with the Hug Day date ^^
[19:38] <hjd> Hi. I'm tagging some bugs 'upgrade-software-version' and wondered what (if anything) I should do with bugs tagged 'upgrade'. Should I replace the tag with usv, add it in addition or leave them alone?
[19:39] <Rcart> charlie-tca: I'll be waiting for the update then :). Thanks.
[19:40] <bdmurray> micahg: what did we decide about upgrade vs upgrade-software-version?  I'd say keep the old one
[19:41] <micahg> bdmurray: hmm, I've been using the new one?  either way is fine, there are only about 15 wtih the new tag
[19:42] <charlie-tca> seems like it would depend on the actual bug, if they used upgrade in place of upgrade-software-version or to report a bug that happened during an upgrade
[19:42] <micahg> charlie-tca: upgrade bugs are supposed to be specified by their releases (i.e. lucid2maverick)
[19:42] <charlie-tca> I know, but that doesn't mean the reporter did not add "upgrade".
[19:42] <bdmurray> micahg: if the bug is already tagged upgrade I'd say keep that tag
[19:43] <micahg> bdmurray: ok, I've just been adding, not changing
[19:43] <bdmurray> hjd: so add usv inaddition to upgrade
[19:44] <bdmurray> hjd: thanks for asking
[19:45] <hjd> ok. I've left them alone so far, just thought I'd check.
[19:51] <hjd> For some requests for newer versions, I've found similar bug reports in debian as well. However, the Ubuntu bug and Debian bugs mention different versions. Should I add a bugwatch to these or not? As a new release might fix one of the bugs, but not the other. (I can probably find an example)
[19:55] <hjd> for instance bug 451947 vs http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599617. (Perhaps a bad example, as the difference i version numbers are pretty small)
[19:55] <ubot4> Debian bug 599617 in php-codesniffer "php-codesniffer: New upstream version available" [Wishlist,Open]
[19:55] <ubot4> Launchpad bug 451947 in php-codesniffer (Ubuntu) "Version bump request (1.2.0) (affects: 2) (heat: 7)" [Undecided,New] https://launchpad.net/bugs/451947
[20:05] <bdmurray> hjd: I think making the ubuntu one less version specific and linking to the debian bug is a good idea
[20:19] <hjd> bdmurray: something like this (bug 451947)?
[20:19] <ubot4> Launchpad bug 451947 in php-codesniffer (Debian) (and 1 other project) "Version bump request (affects: 2) (heat: 12)" [Unknown,Unknown] https://launchpad.net/bugs/451947
[20:20] <bdmurray> hjd: yes - you could also confirm since you know ubuntu is behind
[20:23] <hjd> bdmurray: confirmed as well. Wasn't aware I should do taht.
[20:23] <hjd> *that
=== bdmurray changed the topic of #ubuntu-bugs to: Ubuntu BugSquad - next meeting 2/15/11 | http://wiki.ubuntu.com/BugSquad | Documentation: http://wiki.ubuntu.com/HelpingWithBugs | If you have been triaging bugs for a while, please apply to https://launchpad.net/~ubuntu-bugcontrol/ | Want to report a bug? Read https://help.ubuntu.com/community/ReportingBugs | User support (not related to triage) is in #ubuntu