[11:15] <TheMuso> c
[11:43] <Le-Chuck_ITA> hi all
[11:43] <Le-Chuck_ITA> suppose I want to work on a bug
[11:43] <Le-Chuck_ITA> suppose I want it to be fixed in edgy
[11:44] <Le-Chuck_ITA> since I want to avoid an embarassed explanation to people
[11:44] <Le-Chuck_ITA> about what they should not do with their fresh ubuntu
[11:44] <Le-Chuck_ITA> even if it looks like they can do it
[11:44] <Le-Chuck_ITA> well
[11:44] <Le-Chuck_ITA> where will I go?
[11:44] <Le-Chuck_ITA> I already reported many bugs
[11:44] <Le-Chuck_ITA> I can fix one of them
[11:44] <Le-Chuck_ITA> it's better than 0
[11:44] <Adri2000> Le-Chuck_ITA: bug number?
[11:45] <Seveas> attach your patch to the bugreport
[11:45] <Le-Chuck_ITA> https://launchpad.net/distros/ubuntu/+source/beagle/+bug/67778
[11:45] <Ubugtu> Malone bug 67778 in beagle "Search don't work with beagle" [Low,Confirmed] 
[11:45] <Le-Chuck_ITA> great :)
[11:45] <Le-Chuck_ITA> yes
[11:45] <Le-Chuck_ITA> the patch is stupid
[11:45] <Le-Chuck_ITA> since I don't understand why "set -e"
[11:45] <Le-Chuck_ITA> makes bash exit where it should not according to the manual
[11:45] <Le-Chuck_ITA> however that is a workaround, removing "set -e"
[11:46] <Adri2000> hey, bug 63416
[11:46] <Ubugtu> Malone bug 63416 in beagle "Problem with /etc/cron.daily/beagle-crawl-system" [Undecided,Confirmed]  http://launchpad.net/bugs/63416
[11:46] <Le-Chuck_ITA> and the bug effects are a disaster: just install beagle and you won't have search in yelp anymore
[11:46] <Le-Chuck_ITA> and what should I reply when people installs ubuntu and asks "hey what's the google desktop alternative here?"
[11:46] <Le-Chuck_ITA> "there's beagle but don't use it" :)
[11:46] <Le-Chuck_ITA> it's not an answer
[11:47] <Adri2000> Le-Chuck_ITA: do you receive an email every day from cron saying that the script failed?
[11:47] <Le-Chuck_ITA> I meant "google desktop search"
[11:47] <Le-Chuck_ITA> no
[11:47] <Le-Chuck_ITA> ehm
[11:47] <Le-Chuck_ITA> do I receive mails from cron at all?
[11:47] <Le-Chuck_ITA> is it by default in ubuntu?
[11:47] <Adri2000> "mail" in the terminal
[11:48] <Le-Chuck_ITA> wait a moment
[11:48] <Le-Chuck_ITA> "mail command not found" but...
[11:48] <Le-Chuck_ITA> sudo apt-get install mailx :)
[11:48] <Adri2000> command not found?!
[11:48] <Le-Chuck_ITA> no I never received any e-mail
[11:48] <Adri2000> "mail" without the quotes of course
[11:48] <Le-Chuck_ITA> I received three e-mails from cron
[11:48] <Le-Chuck_ITA> yes yes I know
[11:49] <Le-Chuck_ITA> I've been using debian for years
[11:49] <Le-Chuck_ITA> mailx is not installed by default
[11:49] <Le-Chuck_ITA> and root mail is not sent to any user by default
[11:49] <Le-Chuck_ITA> oh yes
[11:49] <Le-Chuck_ITA> it is sent
[11:49] <Le-Chuck_ITA> sorry
[11:49] <Le-Chuck_ITA> however I have three e-mails from cron
[11:50] <Le-Chuck_ITA> and none of them has to do with the above bug
[11:51] <Adri2000> ok, but anyway bug 67778 and bug 63416 have the same fix, remove "set -e"
[11:51] <Ubugtu> Malone bug 67778 in beagle "Search don't work with beagle" [Low,Confirmed]  http://launchpad.net/bugs/67778
[11:51] <Ubugtu> Malone bug 63416 in beagle "Problem with /etc/cron.daily/beagle-crawl-system" [Undecided,Confirmed]  http://launchpad.net/bugs/63416
[11:52] <Le-Chuck_ITA> ok I see
[11:52] <Le-Chuck_ITA> now
[11:52] <Le-Chuck_ITA> what are the steps to drive a fix into everybody's update system? I mean to drive a fix into an update in edgy-updates?
[11:52] <Le-Chuck_ITA> can I do something different than wait?
[11:52] <Adri2000> SRU :)
[11:53] <Le-Chuck_ITA> Sometimes Root is Useful???
[11:53] <Le-Chuck_ITA> :)
[11:53] <Le-Chuck_ITA> what does SRU mean
[11:53] <Adri2000> Stable Release Updates
[11:53] <Le-Chuck_ITA> when do they happen (sorry if I waste your time)
[11:55] <Adri2000> so, someone have to create a debdiff with the fix, then be approved by the sru team to go to edgy-proposed, the package should stay there for one week, be tested (and it must be confirmed by some people that the fix works and doesn't cause any regression), then it can go in edgy-updates
[11:55] <Adri2000> the process is something like that, but I believe that it is still in discussion
[11:56] <Le-Chuck_ITA> well I see that ubuntu is the most responsive distribution
[11:56] <Le-Chuck_ITA> but we need a way to quickly fix stuff for people
[11:57] <Le-Chuck_ITA> however: if I create a debdiff where do I go
[11:58] <Adri2000> attach it to the bug report
[11:58] <Le-Chuck_ITA> and... is there a page about debdiff? ah ok
[11:58] <Le-Chuck_ITA> I found "man debdiff" but I suppose it's not it
[11:58] <Adri2000> do you know about debian packaging?
[11:59] <Le-Chuck_ITA> very little but can learn
[11:59] <Le-Chuck_ITA> I am taking seriously this "make ubuntu conquer the world" thing
[11:59] <Adri2000> debdiff is the diff between the current package and your new package with the fix
[12:00] <Adri2000> but, you can wait for someone to do it, maybe I will find some time to take care of it
[12:00] <Le-Chuck_ITA> is it the diff between the two source directories? I am looking at one here: http://librarian.launchpad.net/4942734/xorg_7.1.1ubuntu6.1.debdiff
[12:00] <Adri2000> debdiff between two .dsc
[12:01] <Adri2000> and debdiff creates a diff between the whole source directory yes
[12:01] <Le-Chuck_ITA> Adri2000, you're very kind but I have opened some 20 bugs and subscribed the same number
[12:01] <Le-Chuck_ITA> I really want to do something about those
[12:01] <Adri2000> sources directories*
[12:01] <Le-Chuck_ITA> ok
[12:02] <Le-Chuck_ITA> so I apt-get source the current file
[12:02] <Le-Chuck_ITA> copy the source
[12:02] <Le-Chuck_ITA> modify it
[12:02] <Le-Chuck_ITA> then run debdiff
[12:02] <Adri2000> no
[12:02] <Le-Chuck_ITA> Ok :)
[12:02] <Adri2000> don't directly modify the source: patch
[12:02] <Adri2000> then changelog also
[12:03] <Le-Chuck_ITA> ?
[12:03] <Le-Chuck_ITA> to obtain a patch I am used to modify something then run "diff"
[12:03] <Adri2000> depends on the patch system used by the beagle package
[12:04] <Adri2000> I'm looking at it
[12:04] <Adri2000> it uses dpatch
[12:04] <Adri2000> haha, the "set -e" is added by an ubuntu patch
[12:05] <Le-Chuck_ITA> so the task is easier ...
[12:05] <Le-Chuck_ITA> hope I am not going to add an additional patch to that :)
[12:05] <Adri2000> but the patch adds also a few more linux
[12:05] <Adri2000> s/linux/lines/
[12:06] <Adri2000> I don't know if they can be removed also
[12:07] <palski> Le-Chuck_ITA: I think this a good tutorial howto create debdiffs http://wiki.debian.org/BSP/BeginnersHOWTO
[12:08] <Le-Chuck_ITA> great
[12:08] <palski> somebody else should confirm this is a valid way also in ubuntu
[12:08] <Adri2000> non maintainer upload doesn't exist in ubuntu
[12:10] <Le-Chuck_ITA> by the way
[12:10] <palski> Adri2000: ok, so those are valid, but do not add "* Non-maintainer upload" to changlog?
[12:11] <Le-Chuck_ITA> well nothing (adding "configure evolution to handle the local mail by default" in my ubuntu todo list)
[12:12] <Le-Chuck_ITA> Tag the bug as "patch available" by sending an email to  control@bugs.debian.org
[12:12] <Le-Chuck_ITA> what's the ubuntu equivalent?
[12:12] <Adri2000> attach the debdiff to the bug report
[12:13] <Le-Chuck_ITA> there's the "this attachment is a patch" checkbox, yes I remember now
[12:13] <Le-Chuck_ITA> but, finally
[12:13] <Le-Chuck_ITA> in this case
[12:14] <Le-Chuck_ITA> should one really create a new patch to remove just the "set -e" line?
[12:14] <Le-Chuck_ITA> or can one edit the previous patch?
[12:15] <Adri2000> you can edit the previous patch (using dpatch-edit-patch), but if all the patch can be removed (check that), it's easier to just drop the patch
[12:15] <Le-Chuck_ITA> yes I see
[12:16] <Le-Chuck_ITA> hope that I won't make a mess however I keep this for myself
[12:16] <Le-Chuck_ITA> this bug, I mean
[12:16] <Le-Chuck_ITA> for a couple of days so I will learn how to do a debdiff
[12:16] <Le-Chuck_ITA> make
[12:16] <Le-Chuck_ITA> a debdiff... my english is going worse every day
[12:21] <Le-Chuck_ITA> "To ensure that you get the latest source for the package check  http://incoming.debian.org and  http://packages.qa.debian.org. Go to the directory where you want to edit the source and get all the required files with   "
[12:21] <Le-Chuck_ITA> is there an "incoming" in ubuntu?
[12:23] <Adri2000> ftp://upload.ubuntu.com I think, but there are not a lot of new packages every day in a stable release
[12:23] <Adri2000> so you can apt-get source beagle
[12:25] <Le-Chuck_ITA> ok, thank you
[12:26] <Le-Chuck_ITA> got to stop here now, will continue in the evening
[12:26] <Le-Chuck_ITA> bye and thanks again
[12:27] <Adri2000> bye
[02:47] <Seveas> grmbl
[02:48] <Seveas> and AGAIN ubugtu no longer gets mail from the ubuntu-bugs mailinglist
[02:48] <Seveas> I'm SO fed upwith that
[02:49] <Seveas> sfllaw, in case you're wondering why ubugtu no longer reports new bugs ---^
[03:45] <bddebian> Boo
[04:04] <sfllaw> Seveas: Thanks.
[04:07] <Seveas> sfllaw, if you poke a random canonical sysadmin, he can probabl fi it. I won't do it this time, it's not my fault that mailman fails
[04:12] <sfllaw> Seveas: What's ubugtu's e-mail address?
[04:14] <Seveas> bugbot AT danielveldkamp.nl
[05:34] <[Utah] tristanbob> If you use wireless in Ubuntu, does the pull-down menu show the available wireless networks?
[05:34] <[Utah] tristanbob> this worked for me in Dapper, but after upgrading to Edgy it never shows the networks (using same wireless card)
[05:59] <seb128> zakame: was the duplicate Build-Depends the only change for the dia-newcanvas sync you did?
[06:42] <zakame> seb128: yes, why? the second B-D was hard-coded,
[06:46] <zakame> seb128: it was a nice candidate for  a requestsync, but I don't think its right to have a second B-D there, especially against a lower version
[06:56] <seb128> zakame: because having extra merges just because it's "cleaner" doesn't seem to be a good idea
[06:56] <seb128> zakame: dup B-D is just fine
[06:56] <seb128> that package should be sync
[06:58] <zakame> seb128: wait, it wasn't a duplicate B-D, it was a duplicate Depends
[06:59] <zakame> seb128: so you mean that, with the dup depends, then there's no way for apt to get confused by it right?
[07:46] <seb128> zakame: dup Depends is no issue, it'll just use the most restrictive one
[09:53] <Kaleo> hi everyone
[11:33] <sfllaw> Seveas: It got set to No Mail mode.
[11:33] <Seveas> why?
[11:33] <sfllaw> Seveas: Apparently, you can login to the user interface and turn that off.
[11:33] <sfllaw> We're looking into the cause now.
[11:35] <Ubugtu> New bug: #72019 in bum (universe) "UVF exeption request" [Undecided,Unconfirmed]  http://launchpad.net/bugs/72019
[11:36] <nixternal> so we shall have mr. bugy back
[11:36] <nixternal> yay!!
[11:36] <Seveas> apparently now
[11:36] <Seveas> with the whole kit'n;caboodle of backlog as well
[11:36] <Seveas> so he'll be spammy for a while
[11:36] <nixternal> hehe
[11:37] <Seveas> sfllaw, if mailman sets a user in no-mail-mode after n undeliverable mails, make sure n is huge for -bugs
[11:37] <nixternal> Seveas: cruddy about your CDs..but did you get them yet, or are they running you in circles some more?
[11:37] <ajmitch> we're *way* out of time for that :)
[11:37] <Seveas> nixternal, they'll send them tomorrow, or I'll be making more angry phone calls. I now have the location of the package + the phone number of that depot
[11:38] <Seveas> nixternal, and I'm serious about filing a theft report as well -- it's illegally at their place for 2 weks tomorrow
[11:38] <nixternal> that is crazy
[11:38] <Seveas> it is
[11:38] <nixternal> hopefully you will get them tomorrow then
[11:38] <sfllaw> Seveas: Ng is going to check it out.
[11:38] <Seveas> not hopefully. I will.
[11:39] <nixternal> if not, open up the gates of hell, and fire down on them the wrath of Seveas (if that still works)
[11:39] <sfllaw> Seveas: But can you put Ubugtu on a reliable MX?
[11:39] <nixternal> Seveas: just remember that @lart won't work with them ;)
[11:39] <Seveas> sfllaw, he is on a reliable mx, but 3 rather expensive routers at the colo failed
[11:40] <Seveas> soh was off for a while
[11:40] <Seveas> s/soh/so he/
[11:40] <Ubugtu> New bug: #71867 in libnet-server-perl (universe) "Net::Server::MultiType does not pass forward arguments" [Undecided,Fix released]  http://launchpad.net/bugs/71867
[11:41] <nixternal> heh
[11:41] <sfllaw> Seveas: What about a backup MX?
[11:41] <nixternal> this is gonna get fun really quick
[11:41] <nixternal> it has all the way up to 72097 to go
[11:41] <Seveas> sfllaw, I don't have abackup server right now
[11:42] <sfllaw> Seveas: OK.  We'll see what we can do.
[11:43] <Seveas> plus, mailman should not be bouncing off users after only hours of not being reachable
[11:43] <sfllaw> Seveas: It does it after a set number of bounced messages.
[11:43] <sfllaw> Which, for ubuntu-bugs@, probably happens in a number of minutes.
[11:44] <Seveas> I wouldn't be surprised, hence my previous rem\ark about that
[11:48] <Seveas> Oh no, 2 ivoks-es
[11:49] <pygi> Seveas: :P
[11:49] <Seveas> heh, one of them got scared
[11:49] <pygi> Seveas: lol, by you :)
[11:53] <sfllaw> Seveas: Is there some way you could parse the e-mail that gets sent when you bounce a lot of mail?
[11:54] <sfllaw> And then get Ubugtu to renable his own account?
[11:54] <sfllaw> Seveas: Although that does sound pretty dodgy, doesn't it?
[11:54] <Seveas> sfllaw, ubugtu doesn't get that mail as well
[11:55] <pygi> Seveas: o right, forgot you are here :)
[11:55] <pygi> Seveas: could I please get Ubuntu in #ubuntu-burning?
[11:55] <sfllaw> Bleh.
[11:55] <Seveas> sure, http://releases.ubuntu.com
[11:57] <Seveas> pygi, in cas that reply looked weird, search for the typo in your question 
[11:57] <pygi> Seveas: I got it ^_^
[11:57] <pygi> Seveas: ok, could I please get Ubugtu in #ubuntu-burning? :)
[11:58] <pygi> Seveas: the notification of new bugs to packages assigned to team, and that I can write "bug #134" and it prints me the bug desc, etc
[11:58] <Ubugtu> Malone bug 134 in baz "undo doesn't undo a conflict" [Medium,Unconfirmed]  http://launchpad.net/bugs/134
[11:58] <pygi> Seveas: I think that's about all I need unless you know something else ^_^
[11:58] <Seveas> @join #ubuntu-burning
[11:59] <Seveas> pygi, new-bug notifications will need to wait
[11:59] <pygi> Seveas: ok, thank you
[11:59] <pygi> Seveas: it's not urgent anyway
[12:00] <Seveas> first fix mail setup at new server, then move mailaccounts to my own domain (which does have a backup MX :))