[00:00] <nhandler> So the source of the bug was never discovered?
[00:01] <drguildo> yeah
[00:02] <nhandler> Then it should be invalid. See http://tinyurl.com/5uubpe
[00:03] <drguildo> ok, thanks.
[00:04] <nhandler> You're welcome drguildo
[00:37] <lfaraone> Hi, I'm getting an error "104" when submitting bugs via 5aday...
[00:37] <lfaraone> Any idea how I can fix this?
[00:44] <drguildo> anybody fancy trying to reproduce a rhythmbox bug?
[03:11] <bucket529> I'm trying to create my first patch for bug 117984 using the wiki. The fix changes one line in an XML file in evolution-data-server, plus the ChangeLog addition. But e-d-s doesn't have a debian/ directory, so debuild fails. The wiki only covers debuild -> deb file -> defdiff to create the patch. Any clever workaround or alternate method?
[03:14] <RAOF> bucket529: You're starting from what package?  If you want to fix this _in Ubuntu_ you start with the relevant source package, make a patch, and apply it; in that case, you're guaranteed to have a debian/ directory.
[03:16] <RAOF> bucket529: "aptitude search evolution" suggests the package you're after is evolution-data-server.
[03:16] <bucket529> RAOF: I started with 'apt-get source evolution-data-server'. It downloaded the source beautifully. Everything was there...except a debian/ folder.
[03:17] <bucket529> RAOF: AS a check, I also pulled the source from the link at packages.ubuntu.com. Same ultimate result.
[03:18] <persia> bucket529, Did it downlod a tar.gz and a diff.gz an report an error about dplg-source failing?
[03:18] <RAOF> Uuur, really?
[03:18] <bucket529> persia: Yes, .tar.gz. Yes, diff.gz. No error.
[03:18] <persia> RAOF, Common if devscripts isn't there.  Try it in a chroot.
[03:19] <persia> bucket.  Try dpkg-source -x $(whatever).dsc.  This ought get you unpacked source with a debian/ directory.
[03:19] <RAOF> persia: Aaah.
[03:19] <persia> Or at least produce a useful error.
[03:19] <bucket529> persia: Will do. Thanks.
[03:20] <persia> bucket529, Thanks for helping with a patch :)
[03:20] <persia> bucket529, If that doesn't work, apt-get install devscripts and try again.
[03:35] <bucket529> persia, RAOF: Success. Got a debian/ this time. Thanks.
[04:00] <bucket529> Attached a patch (cross fingers - first try) for bug 117984. Tried patching my own, and it seemed to work. hggdh wanted to see it - I'll ping him tomorrow about it. I'll pause a couple days for feedback/corrections before sending it upstream to Gnome.
[04:20] <hggdh|away> bucket529, I will have a look at it, and will ping upstream about it (happened to come to my office to get a printout)
[04:23] <hggdh|away> bucket529, did you create the diff from a clean apt-get source?
[04:24] <bucket529> hggdh: Er, clean?
[04:26] <hggdh|away> bucket529, if you look at the diff there is a lot of changed lines
[04:26] <hggdh|away> er, is this s debdiff?
[04:26] <bucket529> hggdh: The wiki instructions were for a debdiff.
[04:28] <hggdh|away> then seems OK
[04:28] <bucket529> hggdh: If a different format is better, can do...just let me know
[04:29] <hggdh|away> bucket529, a debdiff is good for us; for upstream we will just provide them witha diff
[04:29] <bucket529> hggdh: Ah...I will start learning that tomorrow.
[04:31] <bucket529> hggdh: I'll attach a diff to the bug once I get there...perhaps tomorrow.
[04:31] <hggdh|away> bucket529, thank you ( and a diff is simpler ;-)
[04:32] <hggdh|away> bucket529, the reason is upstream does not package at all, they provide the source and a bauild process to make the binaries, but no packaging
[04:33] <bucket529> hggdh: Good to know. As I wade in the deeper water, the swimming lessons begin to make more sense.
[04:37] <hggdh|away> :-)
[04:38] <hggdh|away> beware of crocodiles
[05:35] <rrittenhouse> I'm trying to assign some bugs to their packages. Would this one go to network-manager-applet? https://bugs.launchpad.net/ubuntu/+bug/297909
[05:36] <Hobbsee> rrittenhouse: n-m-a doesn't exist?
[05:36] <Hobbsee> network-manager is the source package though
[05:36] <Hobbsee> (and yes, it should go there)
[05:37] <rrittenhouse> Oh ok. I'm trying to get my head wrapped around triaging. I have a lot of time that can be donated to this once I learn what to do :P
[05:38] <rrittenhouse> Hobbsee: I just did a search for the package in LP and I thought that network-manager-applet would have been the right one..
[05:39] <Hobbsee> rrittenhouse: bugs go by source packages, not binary packages, to start with
[05:39] <rrittenhouse> hmm ok
[05:39] <Hobbsee> i'd guess you found network-manager-gnome?
[05:40] <Hobbsee> oh, wait, yes it is
[05:40] <Hobbsee> i can't spell.
[05:40] <Hobbsee> network-manager-applet | 0.7~~svn20081020t000444-0ubuntu1 | http://archive.ubuntu.com intrepid/main Sources
[05:40] <rrittenhouse> hmm
[05:41] <Hobbsee> rrittenhouse: so, that would either go to the applet, or network-manager itself.  I have a suspicion that network-manager itself should get the card to refresh the available networks after a suspend, so i'd send it to network-manager
[05:41] <Hobbsee> (because that should happen no matter which frontend gets used)
[05:42] <rrittenhouse> true. :)
[05:45] <rrittenhouse> Hobbsee: Thank you. I'm sure i'll have a lot more questions if thats ok :D
[05:46] <Hobbsee> rrittenhouse: you're welcome.  I'm heading out to work, but i'm sure others will be happy to answer
[05:46] <rrittenhouse> thanks again
[05:50] <rrittenhouse> Assigning packages to bugs; Does that count for 5-a-day? :P
[05:50] <Hobbsee> yes
[05:52] <rrittenhouse> I thought it read that way on the wiki. Neat. That'll be a good start. I felt that trying to duplicate the bugs or asking for certain info for every little problem was an overwhelming place to jump in.
[06:13] <dholbach> good morning
[07:38] <thekorn> good morning
[11:50] <Laibsch> Is there a kind soul to push https://bugs.launchpad.net/ubuntu/+source/mailgraph/+bug/221010 into -proposed?
[11:50] <Laibsch> The fix is obvious and I think 0 regression potential
[12:57] <reic> hi, I just started to help with bugs and now i could use some kind of mentor with: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/295414  -  things are getting a little confused, I'm not quite shure whether the bug is filed under the right package and whether the duplicate linked there is really related to "our" bug...
[13:07] <charlie-tca> reic: I believe that bug 297022 is back to the WPA failing, while 295414 is driver failing. That would
[13:08] <charlie-tca> make 297022 not a duplicate.
[13:09] <charlie-tca> Per comment #12, your bug can be reproduced without network manager, making it probably driver.
[13:09] <reic> thx charlie-tca, i thought so too, but wasn't quite sure...
[13:11] <charlie-tca> If Tobias and Diabolo have the same issues, you might want to make it against the kernel, for that is
[13:11] <charlie-tca> where the drivers are, normally, now
[13:12] <reic> so back to package linux, right? is there anything else i can do now, or will someone from bugcontrol set it to triaged and we'll just have to wait?
[13:13] <charlie-tca> Yea, unless the driver is in it´s own package. I´ll triage it if you have all the logs,etc
[13:15] <reic> i first put it under linux, so i think the logs should yet be attached. thanks a lot! :)
[13:19] <charlie-tca> np, some of these are really hard to keep straight. Keep trying, it comes with time
[13:19] <reic> thx, I will :)
[13:19] <charlie-tca> That dup was a good catch!
[13:24] <charlie-tca> reic: done
[13:25] <reic> thanks a lot! I'll check in here later... cya!
[14:53] <chadwik> can someone have a look at bug 295311 for me pls, i'm not sure whether to set it as confirmed by the 2nd commenter as the hardware appears to be very similar, or set it to triaged and leave it to the kernel team to decide if its confirmed?
[14:59] <toobaz1> Hello. Bug 257797, opened since August renders a package (drgeo, ~700 installs on popcon) totally unusable. But unfortunately its Importance is still "Undecided". Since this is slightly frustrating, is there something I can do to solve the problem? Now a patch was provided, but I'm afraid it's veeeeery low on the sponsorship queue, since of its low importance.
[15:00] <angusthefuzz> chadwik: i would ask the second commenter to file a new bug, as many times these things are very hardware specific.  I would still confirm the bug, as you have followed the kernel debug procedures and all the files are collected.
[15:04] <chadwik> angusthefuzz: thanks, it should be set to confirmed rather than triaged even with the hardware being different?
[15:06] <angusthefuzz> chadwik: i think your decision to set it to either triaged or confirmed should ignore the second commenter, because as you said, the hardware is different
[15:07] <angusthefuzz> chadwik: if you have enough experience and think that it is a genuine bug with enough detail for a fix, then set it to triaged, otherwise it should be confirmed.
[15:07] <chadwik> angusthefuzz: ahh ok i see, i'll set it to confimed. thanks again
[15:08] <angusthefuzz> chadwik: if the second commenter makes a new bug, and it happens to be the same root cause, we can duplicate it easy enough
[15:08] <angusthefuzz> chadwik: thank you for helping
[15:53] <AnAnt> Hello, can someone have a look at: bug 292738
[17:55] <hggdh> all: I eeebotu (#ubuntu-bugs-announce) will stop for 5 minutes for a system restart due to package upgrades
[17:57] <bddebian> Boo
[18:06] <bucket529> hggdh: Upstream patch (diff) attached to bug 117984
[18:07] <hggdh> bucket529, will look at it, thanks
[18:19] <hggdh> bucket529, let's have a private chat
[18:50] <bucket529> hggdh: Thanks for your help
[18:54] <chrisccoulson> just looking at bug 298140
[18:55] <chrisccoulson> it seems like a feature request
[18:55] <chrisccoulson> but shouldn't bug reports be raised against whatever daemons are spamming logs?
[18:55] <chrisccoulson> i know there is effort in the kernel to not fill up log files excessively
[19:03] <krychek> wow the number of new bugs is going down
[19:20] <pwnguin> krychek: is it people giving up or software getting better?
[19:23] <krychek> pwnguin: i guess old "new" bugs are being set to incomplete if theyre still an issue
[19:24] <pwnguin> lets say i were really insane -- is it possible to run and test jaunty yet?
[19:24] <chrisccoulson> of course
[19:24] <chrisccoulson> ;)
[19:24] <chrisccoulson> i'm running it at the moment
[19:24] <pwnguin> ok
[19:24] <chrisccoulson> but only in a virtual machine
[19:24] <pwnguin> i guess i'll put that on my todo for tonihgt
[19:24] <krychek> im not gonna upgrade before release anymore
[19:25] <chrisccoulson> i would run unstable all the time but my girlfriend would not approve of it
[19:25] <pwnguin> i have a dual boot system
[19:25] <chrisccoulson> krychek - why?
[19:25] <pwnguin> when things break, i've still got a stable ubuntu install
[19:25] <krychek> too many problems.. i still have 3-4 big problems with intrepid
[19:25] <pwnguin> but no point in trying if the archive hasn't been rebuilt etc
[19:26] <chrisccoulson> you can definately upgrade to jaunty if you're brave enough, but bare in mind that the repositories are in a state of major flux at the moment
[19:26] <pwnguin> krychek: i hear that there's a targetted goal to reduce the number of bugs in jaunty (over say new features)
[19:27] <krychek> that sounds good
[19:27] <pwnguin> chrisccoulson: i'm fine with that, as long as there's a consistant set out there. there's some bugs fixed in gnome upstream i'd like to test again
[19:28] <pwnguin> chrisccoulson: ive been running ubuntu+1 on my laptop since like edgy
[22:49] <mikes80> Hey guys, I'm trying to learn how to assign bug packages. I've read some stuff on the wiki and watched the screencast. But am still a little confused about how to figure what the right package is. Would I be correct in saying it is the source package that the bug needs to be assigned to?
[22:51] <angusthefuzz> mikes80: that is correct, you always assign to the source package
[22:51] <angusthefuzz> mikes80: what is the bugnumber
[22:52] <mikes80> Thanks. 298177
[22:53] <angusthefuzz> bug 298177
[22:54] <mikes80> Yeah that's the one. How do I figure it out. https://launchpad.net/ubuntu/+source?
[22:54] <calc> source would be 'openoffice.org'
[22:55] <angusthefuzz> calc: doesnt it sound like it might be past openoffice, like nautilus perhaps?  since the save dialog allows the user to select the share, but the credentials are handled later?
[22:56] <calc> oh its almost certainly openoffice, of course the user didn't actually give enough data to be useful, they shoul dhave used apport "Help->Report a bug"
[22:56] <calc> since i can't tell which version they are actually using
[22:56] <angusthefuzz> okay calc
[22:56] <calc> the used some weird OOo build number, not even sure where that shows up
[22:57] <calc> they also didn't mention whether they were using gnome or kde, etc
[22:58] <mikes80> Guess I picked a bad bug for my first one :/
[22:58] <calc> and the OOo 3.0 packages (that i created anyway) haven't been changed in several weeks (or a month maybe) so the fact that it used to work but now doesn't sounds like they may be using some other packages entirely
[22:58] <calc> mikes80: hehe :)
[22:58] <calc> mikes80: well it still goes to openoffice.org package but the user didn't really give enough information to determine what is going on
[22:59] <angusthefuzz> mikes80: you could also set status to incomplete and ask for the info we were discussing :-)
[23:00] <mikes80> Okay. How do i request more info. In the comments section?
[23:01] <angusthefuzz> mikes80: yes, your you can click the down arrow next to the word New
[23:01] <angusthefuzz> *or
[23:06] <angusthefuzz> mikes80: were you able to find what I was referring to?
[23:08] <mikes80> Yeah sorry. Thanks for the help. :) Hope i've done it right.
[23:08] <mikes80> So the incomplete status, is for bugs that don't have enough info?
[23:08] <angusthefuzz> looks like you have, thanks for helping mikes80
[23:09] <angusthefuzz> mikes80: you might find this useful, https://wiki.ubuntu.com/Bugs/Status
[23:09] <angusthefuzz> mikes80: but yes, if you have to ask a question, the bug is incomplete
[23:10] <calc> mikes80: well exact ubuntu version would have been more precise but what you said should be enough to get him to hopefully respond with the correct information :)
[23:10] <mikes80> Great thanks guys.