=== asac_ is now known as asac
[00:34] <Gralco> bdmurray who should i assign this bug too? https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/243073
[00:34] <ubottu> Launchpad bug 243073 in compiz "[regression] Visual effects stopped working after last compiz+kernel update on fglrx" [Undecided,Confirmed]
[00:35] <bdmurray> Gralco: nobody - people assign bugs to themselves when they are going to work on them for the most part
[00:36] <Gralco> bdmurray then how do i know i triaged the bug correctly?
[00:37] <bdmurray> You could ask somebody here or stay subscribed to the bug
[00:37] <Gralco> oh okay
[00:38] <Gralco> but there are time when i need to assign bugs to a certain team right
[00:38] <bdmurray> Yes, only for kernel bugs.
[00:38] <Gralco> okay, thank you
[00:39] <Gralco> I haven't been able to triage any bugs recently
[02:55] <wgrant> bdmurray: Wow, that's a bit of an importance definition change!
[02:55] <wgrant> I've been wondering why it wasn't like that already.
[03:19] <persia> I like it.  In addition to reducing the requirement to gauge the general impact on the distribution, it aligns Importance with SRU guidelines.
[03:39] <mrooney> me too, I thought that would be a nice way to do it
[03:40]  * greg-g nods
[03:42] <mrooney> it probably makes life for package devs much better
[03:45] <persia> I suspect it makes life easier for everyone: package maintainers, triagers, QA people, developers, QC people, the stable release team, etc.
[03:48] <mrooney> I don't quite get how it makes it easier for people tracking critical bugs in ubuntu
[03:48] <mrooney> they can milestone and such but how do bugs within a milestone have importances relative to the milestone?
[03:49] <persia> Doesn't matter.  If it's milestoned, it ought get done.  If it isn't getting done in time, the release managers have broad powers of persuasion.  If that also fails, it ought be deferred.
[03:51] <mrooney> I see, fair enough
=== thekorn_ is now known as thekorn
=== RAOF_ is now known as RAOF
[11:11] <james_w> Apport session starting now in #ubuntu-classroom if anyone is interested.
[11:17] <\sh> bdmurray: we have to reopen bug #188018 of py-lp-bugs
[11:17] <ubottu> Launchpad bug 188018 in python-launchpad-bugs "Latest changes in edges.launchpad.net breaks py-lp-bugs" [High,Fix released] https://launchpad.net/bugs/188018
[11:18] <\sh> argl...I'll file a new one
[11:35] <\sh> fix for bug #243193 <- new edge , py-lp-bugs crashing
[11:35] <ubottu> Launchpad bug 243193 in python-launchpad-bugs "launchpad edge changed layout, py-lp-bugs is crashing" [Undecided,New] https://launchpad.net/bugs/243193
=== ogra_ is now known as ogra
=== thekorn_ is now known as thekorn
[13:01] <james_w> persia: nice work on bug 243211
[13:01] <ubottu> Launchpad bug 243211 in 2vcard "dvdvsdvgfvbgrnj,.;hjngfbvgbhnjkm,l;.'.,lmjnhbgvfcdxfghjklp;lkjhgfdsfghjkl;';lkjhgfdsasdfgtyhuiop" [Undecided,Invalid] https://launchpad.net/bugs/243211
[13:04] <persia> james_w: Mind you, it could be an encoding issue :)
[13:14] <Igorot> persia: i doubt it's an encoding issue. seems like the reporters' testing out launchpad.
[13:14] <Igorot> or at least trying to submit a test bug report.
[13:17] <persia> Igorot: Very likely.  I just try to avoid assumptions.
[13:34] <safiyyah> is anyone there
[14:19] <pschulz01> Evening.. just joined 5-a-day, and was looking at the untriaged list.
[14:20] <james_w> hi pschulz01
[14:20] <pschulz01> If someone has added a patch (eg. incorrect strings) and it's still in the 'new' state and I can confirm that the patch hasn't been applied yet.. should I cnahe the status to confirmed?
[14:21] <pschulz01> Bug number 65995
[14:21] <techno_freak> bug $65995
[14:21] <techno_freak> bug #65995
[14:21] <ubottu> Launchpad bug 65995 in libvisual "Mistakes in libvisual strings" [Undecided,New] https://launchpad.net/bugs/65995
[14:23] <james_w> pschulz01: that should be confirmed, yes.
[14:23] <pschulz01> Ta
[14:24] <Hobbsee> pschulz01: is that upstream still dead?
[14:24] <pschulz01> Hobbsee: Hobbsee!!
[14:24] <Hobbsee> heya!
[14:24] <pschulz01> Hobbsee: No idea
[14:25] <pschulz01> Hobbsee: I though I'd use the '5-a-day' to get back into the bug busting business.
[14:25] <pschulz01> (This is my first)
[14:25] <Hobbsee> pschulz01: ahh.  i've not been using it, although i've done about 8 today.
[14:26] <Hobbsee> pschulz01: just poked the debian maintainer, he says he'll do it today, and will file a sync request for it (or will poke me to file one)
[14:26] <pschulz01> Hobbsee: heh it works :-)
[14:27] <Hobbsee> it does.
[14:29]  * Hobbsee does another one.
[14:33] <pschulz01> Hobbsee: bug #65304
[14:33] <ubottu> Launchpad bug 65304 in xfsprogs "Mistake in xfsprogs string - 'prefered'" [Undecided,Confirmed] https://launchpad.net/bugs/65304
[14:42] <pschulz01> If I find that a bug can no longer be duplicated, do I mark it as 'Fix Released'?
[14:42] <pschulz01> bug #68914
[14:42] <ubottu> Launchpad bug 68914 in sudo "HOME (wrongly) removed from environment" [Undecided,Fix released] https://launchpad.net/bugs/68914
[14:42] <pschulz01> (I've done that)
[14:55] <persia> pschulz01: Not every bug that cannot be reproduced is Fix Released, although some are.  Just be sure you have a test case (as you do with that bug).
[14:56] <persia> It's also a good idea to try to check with the version the reported used (if reported) to verify that you could reproduce the failure previously
[15:00] <JohnPhys> Will the fix for bug #55273 be released to hardy?
[15:00] <ubottu> Launchpad bug 55273 in inkscape "inkscape generates no latex formula" [Medium,Fix committed] https://launchpad.net/bugs/55273
[15:00] <pschulz01> Does 'Incomplete' mean something like 'More information required'?
[15:00] <pschulz01> persia: This is for another.. bug #70648
[15:00] <pschulz01> persia: bug #70648
[15:01] <ubottu> Launchpad bug 70648 in gimp "GIMP color chooser broken" [Undecided,New] https://launchpad.net/bugs/70648
[15:01] <persia> "Incomplete" means that the bug doesn't contain sufficient informtion to either confirm or reject.  It can be interpreted as "More Information Required", but should not be assumed to mean that directly.
[15:02] <persia> When a bug is set to "Incomplete", it is essential that the person adjusting it identify what information they believe would be required in order to proceed with triage.
[15:03] <pschulz01> persia: I think I've done that. (Thanks)
[16:39] <bdmurray> gnomefreak: ping
[16:43] <gnomefreak> bdmurray: pong
[16:55] <bliZZardz> hello!
[17:05] <bdmurray> asac: is there a process for needs-packaging extension bugs?
[17:07] <asac> bdmurray: yes. add it to the firefox3extensions page .... fill in the information
[17:07] <asac> and add a firefox-extension project task
[17:07] <bdmurray> asac: which page is that?
[17:07] <asac> bdmurray: https://wiki.ubuntu.com/MozillaTeam/Firefox3Extensions
[17:08] <asac> bdmurray: Extensions that need a maintainer (Ubuntu QA contact)
[17:08] <asac> bdmurray: or if not all info is available:
[17:08] <asac> "Suggested extensions missing details"
[17:09] <bdmurray> hmm, this is neat thanks!
[17:16] <jkary> Hello.  Can someone please tell me what this error message means?  E: Could not open file /var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dist_universe_source_Sources - open (2 no such file or directory)
[17:17] <jkary> I am running Hardy
[17:17] <jkary> I am trying to install some source code using apt-src so I can verify a patch
=== Spec[x] is now known as Spec
[17:18] <james_w> jkary: hi, did you just add a "deb-src" line to your sources.list?
[17:19] <james_w> if so did you run "sudo apt-get update" afterwards?
[17:20] <jkary> hmmm.  let me look. one sec.
[17:22] <jkary> I have the follow lines at the top of my sources.list file.
[17:22] <jkary> deb http://ubuntu.media.mit.edu/ubuntu/ hardy main restricted multiverse
[17:22] <jkary> deb-src http://ubuntu.media.mit.edu/ubuntu/ hardy restricted main multiverse universe #Added by software-properties
[17:23] <kenkku> is the source package you are trying to download in that repository?
[17:24] <jkary> aha
[17:24] <jkary> I think I just needed to run apt-get update.
[17:24] <kenkku> yep
[17:24] <kenkku> if you didn't run it, that's what's wrong
[17:24] <jkary> yup.  that was the trick!  Thanks!
[17:42] <thekorn> hello bughunters!
[17:47] <Iulian> G'evening thekorn.
[17:49] <james_w> hey thekorn, Iulian
[17:49] <thekorn> hi Iulian
[17:49] <thekorn> and James
[17:51]  * thekorn wonders why xchat does not show join/part actions anymore
[17:57] <thekorn> james_w, persia : thanks for organizing and presenting the apport-retracer session, I'm reading the log now and it is very informative
[17:58] <bdmurray> thekorn: hello
[17:58] <thekorn> hi bdmurray, thanks for testing py-lp-bugs
[17:58] <persia> thekorn: I'm glad you found it useful.
[18:03] <bdmurray> thekorn: the datereported_test.py script in bug 185357 fails for me with the intrepid.merge branch
[18:04] <thekorn> bdmurray, hmm, looking
[18:05] <ubottu> Launchpad bug 185357 in bughelper "date_reported in python-launchpad-bugs not accessible via bughelper" [Wishlist,In progress] https://launchpad.net/bugs/185357
[18:08] <thekorn> bdmurray, okay, can reproduce it, seems there was an issue with the thounds merges I did,
[18:08] <thekorn> I missed sometthing
[18:15] <thekorn> bdmurray, false alarm, sorry the sript is wrong, it has to use the +text interface for the Bug-object
[18:15] <thekorn> so line 11 has to be Bug = ConnectBug("text")
[18:16] <thekorn> parsing of the date where a task was created was never implemented in the html mode
[18:17] <bdmurray> thekorn: that makes sense, thanks
[18:22] <geser> thekorn: is it possible to unsubscribe someone (e.g. a team) from a bug with py-lp-bugs?
[18:23] <thekorn> geser, yes, only if the team or user is direct subscribed to this bug
[18:23] <thekorn> geser, let me find an example of code
[18:24] <geser> thekorn: thanks, that was exactly my next question :)
[18:24] <thekorn> :)
[18:27] <thekorn> geser, http://paste.ubuntu.com/23161/
[18:27] <thekorn> very same for teams
[18:29] <geser> thekorn: thanks
=== _neversfelde is now known as neversfelde
=== _neversfelde is now known as neversfelde
=== _neversfelde is now known as neversfelde
=== _neversfelde is now known as neversfelde
=== _neversfelde is now known as neversfelde