[02:10] <thornomad> hi - damon here from the mailing list (recent entry), i posted the bug re intel gigabit card at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/309211 ... would anyone be able to confirm it ?  Thanks!
[02:29] <duanedesign> bug #Bug #309146:
[02:29] <duanedesign> This report is public
[02:31] <duanedesign> bug #309146 this bug needs to be set to Wishlist. Thank you in advance
[02:31] <Hobbsee> (done)
[02:38] <duanedesign> Hobbsee: do feature requests normally get forwarded upstream?
[02:38] <Hobbsee> duanedesign: yes
[02:39] <duanedesign> Hobbsee: thank you for your help.
[02:40] <Hobbsee> you're welcome
[03:41] <duanedesign> A feature request that is asking for a different arrow icon depending on whether or not a CD is in the drive.Would the appropriatte package be nautilus or human-theme
[03:43] <maco> if a suitable icon exists in the theme, i think just nautilus. otherwise, probably touches both.
[03:44] <maco> i mean, nautilus would need to know to change the icon
[03:44] <maco> maybe ask in #ubuntu-desktop to see if anyone knows if nautilus is currently capable of changing the icon based on that status?
[03:46] <duanedesign> thank you, that was a huge help
[05:33] <pckchem> Do we support mythbuntu?
[05:36] <persia> pckchem, Yep.
[05:37] <persia> Official flavours are Ubuntu Desktop, Kubuntu Desktop, Edubuntu, Xubuntu Desktop, Ubuntu Studio, Mythbuntu, Ubuntu Server, Ubuntu MID, and Ubuntu UMPC (for intrepid)
[05:59] <pckchem> Thanks persia
[05:59]  * pckchem reopens that bug report...
[07:52] <dholbach> good morning
[09:30] <thekorn> hello #ubuntu-bugs
[09:30] <dholbach> hello thekorn
[09:30] <BUGabundo_work> olleh thekorn
[09:32] <thekorn> heya dholbach and BUGabundo_work!
[10:15] <ara> have you tried today to report bugs with apport? It reports me network errors with the database server
[10:40] <BUGabundo_work> ara refresh the page
[10:40] <BUGabundo_work> know prob with LP server replication
[10:40] <BUGabundo_work> it has been happening to me over the last 2 weeks
[13:47] <MrKanister> Hey. Has somebody the rights to delete the project https://launchpad.net/debcleaner ? I created it but it became unnecessary
[13:48] <Pici> MrKanister: You may want to ask in #launchpad
[13:48] <persia> MrKanister, You'll want to ask a question against launchpad: the crew in #launchpad can help if you get stuck.
[13:48] <MrKanister> Pici and persia: Thank you. I will ask there
[15:08] <bddebian> Boo
[15:10] <BUGabundo_work> BAAAAAAAAAAA
[15:12] <bddebian> :)
[16:02] <xubuntusdi> Ciao a tutti
[16:12] <hggdh> bdmurray, a question: hoe does one set an upstream task as 'fix committed'?
[16:12] <hggdh> s/hoe/how/
[16:13] <bdmurray> hggdh: Is the upstream task a bug watch?
[16:13] <hggdh> yes
[16:13] <hggdh> and yes, I know
[16:13] <bdmurray> If the bug watch is working it should happen automatically.
[16:14] <bdmurray> hggdh: What bug number is it?
[16:15] <hggdh>  bug 303528
[16:15] <hggdh> from the bug status page: For a bug task about an upstream project: the fix is in CVS/SVN/bzr or committed to some place
[16:18] <bdmurray> I seem to recall a LP developer saying not every bug watch is getting updated.  If you wanted you could reflect the upstream status as FC by modifiying the evolution (ubuntu) task to FC.  But that is a hack.
[16:19] <bdmurray> It's interesting that someone in the upstream bug is still having the issue.
[16:19] <hggdh> yes. that is what we usually do for most desktop, but calc ans slangasek are of a different opinion
[16:21] <bdmurray> Okay, what are you really asking then?
[16:21] <hggdh> I do not understand the phrase "For a bug task about an upstream project: the fix is in CVS/SVN/bzr or committed to some place"
[16:21] <bdmurray> That mirrors what the desktop team does.
[16:22] <hggdh> yes. The point is we cannot set an upstream bug watch, so this phrase has not much of a meaning
[16:22] <bdmurray> I guess it might read better as 'For a bug with a bug task about an upstream project'?
[16:23] <hggdh> (BTW, I mean set status on an upstream bug)
[16:24] <hggdh> I am not sure it reads better... is we are not to set FC for patches in SVN/whatever upstream, then we better not even say anything about that
[16:30] <bdmurray> hggdh: I see your point.  I also think the desktop-bugs team has a valid uses case as there are ~50 bugs that they've set FC (because they are Fixed upstream) but the bug watch isn't reflecting that.  If the bug was left as triaged it would still show up in their TODO list so to speak.
[16:31] <hggdh> bdmurray, yes. I can understand the case for local fixes (i.e., in our bzr), but not this
[16:32] <bdmurray> I think removing it makes sense though as it seem to be a corner case
[16:33] <hggdh> yes. I think it confuses more than helps.
[16:36] <hggdh> or -- if this is how it is to be done -- clearly state that FC is *never* dto be used on the Ubuntu task until the fix is available in -proposed
[16:36] <hggdh> s/until/unless/
[16:38] <torkiano> can anyone assign importance to bug 279430 ?
[17:22] <MrKanister> If a package from "main" was fixed in Debian on 15.03.2008, can I mark it as "fix released", because it should already be fixed in the latest Ubuntu release? (bug #225715)
[17:25] <charlie-tca> MrKanister: Since it was included in Intrepid, you should be able to.
[17:26] <MrKanister> charlie-tca: Thank you. I will do so
[17:26] <charlie-tca> no problem.
[17:56] <LaserJock> what's the "rule" for how long a bug can be in Triaged before people give the "it's been a while" and make it Incomplete?
[17:57] <charlie-tca> I did not think there was a limit
[17:57] <hggdh> there is not
[17:57] <LaserJock> just sort of "it looks like it hasn't been touched in a while"?
[17:57] <charlie-tca> If it is triaged, it should not go incomplete by triagers, but developers sometimes do that
[17:58] <hggdh> well, if it is in traged, then it (theoretically) has all that is needed for dev/maintainers to work. Or perhaps, it is missing the upstream
[17:58] <hggdh> but it is not incomplete
[17:58] <LaserJock> ok, how about bug #121447
[17:59] <hggdh> LaserJock, it certainly should not have been put back in incomplete
[18:00] <hggdh> MrKanister, ping
[18:00] <LaserJock> hggdh: ok, I see.
[18:01] <MrKanister> hggdh: ping
[18:01] <hggdh> MrKanister, ^^
[18:01] <hggdh> a bug that is triaged is outside the bugsquad scope
[18:02] <MrKanister> You are talking about bug #121447 ?
[18:02] <hggdh> yes
[18:02] <MrKanister> oh...I didn't know...the bug seemed abandoned
[18:03] <hggdh> MrKanister, np. LaserJock brought it up to our attention, and it is a good point to be made publicly
[18:04] <hggdh> a triaged bug (except if it needs an upstream bugwatch added) is now the responsibility of the maintainers/packagers/developers (like, for example, LaserJock)
[18:04] <MrKanister> So in general: If a bug was set to "triaged" it should no longer be set to something like "incomplete" because of a long period of no comment
[18:04] <hggdh> correct
[18:04] <LaserJock> MrKanister: I'd say "dormant" rather than "abandoned" ;-)
[18:05] <hggdh> the maintainer/developer/packager *can* downgrade it, but bugsquad should not
[18:05] <LaserJock> hard to tell the difference sometimes
[18:05] <MrKanister> ok, dormant seems ok ;)
[18:05] <MrKanister> I#m glad you are telling me
[18:05] <MrKanister> *I'm
[18:08] <MrKanister> but if a bug is "confirmed" it CAN be set back to incomplete because of a question, right?
[18:09] <LaserJock> that would make sense as you're trying to get more info before going to "Triaged"
[18:09] <LaserJock> when a bug hits Triaged that should say "ok, I got all the info that's needed and it's ready for a dev"
[18:09] <LaserJock> so before then it makes sense to set Incomplete on a question
[18:10] <hggdh> correct -- to my understanding
[18:10] <MrKanister> LaserJock: Thanks
[18:50] <pckchem> Is there a workflow for ISO build errors?
[18:51] <pckchem> Maybe not build errors but ISO/Live image errors in general.
[19:46] <MrKanister> Is it reasonable that some bugs are only assigned to a project but not to a package? (For example bug #5586)
[19:48] <hggdh> MrKanister, it looks like it was set to the wrong package -- it should have been on Ubuntu's gnome-panel instead
[19:50] <MrKanister> So it's wrong to just have the project affected?
[19:51] <LaserJock> that's an ...interesting bug
[19:51] <hggdh> not necessarily, but gnome-panel is packaged by us
[19:51] <hggdh> heh. It is, is it not?
[19:52] <hggdh> BTW, this is one of those where I would seriously consider closing invalid after asking for update...
[19:52] <LaserJock> I'd be hard pressed to ask for an update first
[19:52] <LaserJock> :-)
[19:52] <hggdh> :-)
[19:53] <MrKanister> hggdh: ok, I wanted to do that :)
[19:53] <hggdh> welcome, MrKanister
[19:53] <LaserJock> "something happened in the GUI and then some other thing flashed me"
[19:53] <MrKanister> It's a VERY old bug
[19:53] <hggdh> this is what I meant by finding out what was really meant from what was said
[19:54] <LaserJock> hggdh: yeah, I can kinda guess, but it's difficult
[19:54] <hggdh> MrKanister, it is, and probably invalid now. BUT -- we still have to ask
[19:54] <hggdh> agree
[19:55] <hggdh> and the best is it writes ubento$$ubento...
[19:55] <LaserJock> it looks to me like X is dying on their liveCD
[19:55] <LaserJock> considering this bug is older than Dapper
[19:55] <hggdh> yeah. By the timestamps, this is before dapper... so... unsupported. Since the reporter did not state the distro name, though...
[19:56] <calc> where do bugs that request things be packaged belong?
[19:56] <MrKanister> I answered him, but I don't think we will get much response
[19:56] <LaserJock> I wonder if it's even worth asking anything. I wonder if it would be better to just close the bug and give them a nice paragraph explaining the situation
[19:56] <calc> is there a fake package to assign them to?
[19:56] <LaserJock> calc: no
[19:57] <LaserJock> calc: https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages#Requesting%20a%20new%20package%20for%20Ubuntu
[19:57] <MrKanister> LaserJock: Probably...I will have an eye on the bug. In 4 weeks I wil close it if no answer comes
[19:57] <hggdh> LaserJock, I am tempted to just close & explain. But, given feelings around here...
[19:58] <LaserJock> hggdh: considering *I'm* the one that complains about bugs being closed too often ;-p
[19:58] <calc> LaserJock: ok so it should just be package blank eg Ubuntu ?
[19:58] <hggdh> :-D
[19:58] <LaserJock> calc: yep
[19:58] <calc> LaserJock: ok
[19:58] <LaserJock> calc: there's a spec for Jaunty about improving that, but that's the current way of doing it
[20:01] <hggdh> calc, there is also https://wiki.ubuntu.com/Bugs/HowToTriage#Needs%20Packaging%20Bugs
[20:22] <pckchem> Any talks at UDS about getting some anti-spammer tools on LP ?
[20:23] <hggdh> pckchem, why?
[20:23] <pckchem> https://bugs.edge.launchpad.net/~maurizio-live
[20:23] <hggdh> heh. again
[20:23] <pckchem> Yep. Every couple of days now. There are a few other accounts with similar use patterns.
[20:24] <hggdh> until LP puts in the fix to keep a cancelled account cancelled, not much to do
[20:25] <hggdh> I am pretty sure some of those I myself invalidated...
[20:30] <hggdh> pckchem, what other accounts?
[20:33] <Hobbsee> hggdh: surely they rolled that out yesterday?
[20:33] <hggdh> Hi Hobbsee
[20:33] <Hobbsee> greetings!
[20:34] <hggdh> I was thinking so, but was not sure
[20:34] <hggdh> anyway, the newest is from 2 days ago
[20:34] <hggdh> so there is hope
[20:34] <pckchem> hggdh: Let me look, I came across one in particular about a week ago so it may take a second to look.
[20:37] <Hobbsee> the rollout was done yesterday, so it should be
[20:49] <pckchem> hggdh: https://edge.launchpad.net/~maurizioantillon
[20:51] <pckchem> Obviously some sort of connection between the accounts.
[20:55] <hggdh> pckchem, yes, we think it is the same person