[00:01] <Woody86> Hello everybody :D
[00:01] <csilk> Hello
[00:55] <coppro> this makes no sense
[00:55] <coppro> my intrepid chroot has no upgrades in 4 months?
[01:04] <crimsun> coppro: ensure that it actually has intrepid for apt's configuration.
[01:04] <coppro> thx
[01:59] <cody-somerville> ScottK, ping
[02:42] <philsf> how can I recompile evince with libpoppler3, instead of libpoppler2, assuming I already have all -dev deps installed? what do I need to change in evince's /debian/* to make it use the newer libs?
[02:43] <RAOF_> philsf: Nothing.
[02:44] <nixternal> ya, libpoppler-dev == libpoppler3
[02:44] <StevenK> philsf: It already does, in Intrepid
[02:44] <ScottK> cody-somerville: Pong
[02:45] <cody-somerville> Incase StevenK gets too busy, can you upload https://bugs.edge.launchpad.net/ubuntu/+source/abiword/+bug/284857 ?
[02:46] <StevenK> cody-somerville: Nearly done
[02:46] <StevenK> As in dput'ing now
[02:46] <cody-somerville> StevenK, \o/
[02:46] <StevenK> cody-somerville: Looking
[02:46] <ScottK> Ah.  So I'm not needed.
[02:47] <philsf> StevenK: I want to do this in hardy, I should have said that
[02:47] <philsf> I already backported libpoppler from intrepid
[02:47] <StevenK> Eek
[04:10]  * ScottK notes that Universe is still open for bug fixes.
[04:12] <mneptok> ScottK: that's why i still attend church.
[04:14] <philsf> about version number: is the string "ubuntu1.0" considered greater than "ubuntu1"?
[04:14] <philsf> make that ubuntu1.0~philsf
[04:15] <ScottK> Yes.
[04:15] <Hobbsee> sarah@neptune:~% dpkg --compare-versions ubuntu1.0 gt ubuntu1 && echo true
[04:15] <Hobbsee> true
[04:15] <philsf> I just noted to my shame that ubuntu1~philsf is actually *less* than ubuntu1. what should I use if I want to keep the package installed, and be able to upgrade if a new version comes out?
[04:16] <philsf> 1.0~philsf is enough?
[04:16] <Hobbsee> sarah@neptune:~% dpkg --compare-versions ubuntu1.0~philsf lt ubuntu1 && echo true                                     2:16PM
[04:16] <Hobbsee> sarah@neptune:~%
[04:16] <Hobbsee> so, ubuntu1.0~philsf is greater than ubuntu1
[04:17] <philsf> thanks, Hobbsee and ScottK
[04:19] <philsf> dpkg-buildpackage wants to make clean, how can I keep the compilation and just rebuild the package? is it a one-liner?
[04:20] <philsf> just to change the version, that is
[04:34] <RAOF> philsf: "man dpkg-buildpackage" will help you; the particular switch you're looking for is '-nc'
[04:34] <StevenK> RAOF: I had a Do question
[04:35] <StevenK> RAOF: Is there a "I don't like this match, give me the next one" button?
[04:42] <ScottK> I don't have time to investigate in detail, but it looks like the twiki update in Bug 261962 is one we'd want for the release.  Can someone bend it into shape and upload it?
[04:46] <RAOF> StevenK: Yes.  "Down".
[04:46] <RAOF> StevenK: That'll bring up the results list.  Does this mean I should be setting "always show results list" by default?
[04:47] <StevenK> RAOF: Hmmm. I don't mind no results list, but it'd be nice to be able to tell Do, "No, you guessed wrong."
[04:47] <RAOF> No, I mean the fact that you need to ask the question.
[04:48] <StevenK> Oh, I found down by myself, I was curious if there was a better way
[04:48] <StevenK> RAOF: I wonder if the Firefox plugin can deal with bookmarks that contain '%s'
[04:48] <RAOF> Another button that does the same thing as 'down'?
[04:49] <StevenK> RAOF: No, a button that skips to the second item on the results list
[04:49] <StevenK> s/second/next/
[04:49] <RAOF> Ah.  Without bringing up the results list?
[04:49] <StevenK> Right
[04:49] <RAOF> No, I don't think so.  I'm not totally sold on such a button being a good idea, either.
[04:50] <RAOF> And I don't know about the firefox plugin; possibly?
[04:52] <StevenK> Hmph. The launchpad plugin needs hooks for Package bugs and Package overview
[04:53] <RAOF> Correct.
[04:53] <RAOF> Mmm.  With the launchpad API release, it might also be nice to add some bugs to Do's universe.
[04:54] <StevenK> Is there any API bindings to C# ?
[04:56] <RAOF> Probably not.  Is there a C api?
[04:56] <RAOF> It's only python as of now, isn't it.
[05:01] <RAOF> Hm.  Seems like writing C# bindings wouldn't be unassailably hard.
[05:01] <ajmitch> certainly nto
[05:02] <ajmitch> it should only take you a few hours, I'm sure :)
[05:11] <ScottK> persia: I think some java'ish person should look into merging kaffe.
[05:31]  * Woody86 is away: I'll brb, PM me or say my name
[05:31]  * Woody86 is back (gone 00:00:23)
[06:46] <didrocks> morning
[06:53] <iulian> G'morning.
[10:32] <POX> sebner: Patryk replied to #268692, he also asked other upstream developers to add a comment
[10:33] <sebner> POX: I see. thx for your help. I'll talk to ScottK and then we decide if I'll prepare a FFe or not =)
[10:35] <DktrKranz> sebner: prepare, just to spend some time :)
[10:36] <sebner> DktrKranz: lol xD
[10:39] <sebner> DktrKranz: no time now, soon I gonna cut my hair xD xD xD
[10:40] <DktrKranz> sebner: are you a grunge guitarist?
[10:40] <DktrKranz> or jono's fan?
[10:41] <sebner> DktrKranz: of course the second
[10:41] <dholbach> take "before" and "after" pictures
[10:41] <dholbach> you're going to cut it yourself? ;-)
[10:41] <sebner> dholbach: Not even if I'm drunken xD
[10:41]  * DktrKranz is scared about sebner's "before"
[10:41] <dholbach> hehe
[10:41] <sebner> But it's a pleasure to see how folks are interested in my hair xD xD xD
[10:42] <sebner> DktrKranz: !?!?!
[10:42] <DktrKranz> sebner: being a jono fan, your hair should be looooong
[10:42] <sebner> DktrKranz: jono fan != metal fan
[10:43] <DktrKranz> ah
[10:43] <sebner> dholbach: btw, nearly forgot to tell you that your newest motu vid is great *as usual*  ^^
[10:43] <dholbach> gracias :-)
[10:43] <DktrKranz> newest motu vid? I missed it
[10:43] <sebner> DktrKranz: bah, damn you :P
[10:44]  * DktrKranz hides
[10:44]  * DktrKranz is planning two mass-hugs against dholbach next UDS
[10:44] <dholbach> hehe :)
[10:44] <sebner> DktrKranz: finally you will participate?
[10:45] <DktrKranz> sebner: I'm planning, I'm not doing it ;)
[10:45] <sebner> DktrKranz: tz tz tz
[10:45] <DktrKranz> but I'll be virtually there
[10:45] <sebner> ^^
[10:45] <DktrKranz> sebner: it you convince my belgian boss to leave me for a week, I could partecipate
[10:45] <DktrKranz> but I guess you'll fail in that
[10:46] <sebner> DktrKranz: you have a right for holidays
[10:46] <sebner> but I forgot
[10:46] <sebner> Italy is different :P
[10:46] <sebner> however
[10:46] <sebner> off
[10:46] <sebner> HAIR cutting :D
[10:46] <DktrKranz> no... my company is different ;(
[11:03]  * pochu should cut his hair too...
[11:03] <pochu> sebner: know what? we can start a MEME!! ;-)
[11:06] <DktrKranz> pochu: I plan to cut it tomorrow! :)
[11:06] <pochu> DktrKranz: great, so we are now three! :)
[11:06] <DktrKranz> heh
[11:07] <pochu> DktrKranz: we can create a launchpad team too :P
[11:08] <DktrKranz> ~haircutters
[11:08] <sebner> pochu: rofl
[11:09] <sebner> what a shit. Also a sebner needs a appointment :\
[11:09] <sebner> !ohmy | sebner
[11:09] <sebner> :)
[11:09] <DktrKranz> sebner: auto-oh,ty
[11:10] <sebner>  ^ ^
[11:19] <bobbo> dholbach: ping
[11:19] <dholbach> bobbo: pong
[11:20] <bobbo> dholbach: hey, could you add me to the 5-a-day team on Launchpad? It says only admins can do it
[11:20] <dholbach> bobbo: admins can do what?
[11:20] <bobbo> dholbach: ah doesnt matter, just read your blog post, sorry for bothering you :)
[11:20] <dholbach> :)
[11:20] <dholbach> no worries
[11:21] <DktrKranz> bobbo: hi, I didn't find time to review your debomatic branch yet :(
[11:21] <DktrKranz> after the release, probably I'll have time
[11:22] <bobbo> DktrKranz: ah no problem, i think there are still a couple of bugs i need to iron out, but I'll have another look later
[11:23] <dholbach> debomatic?
[11:23] <DktrKranz> dholbach: my project to create a simple build machine for debian packages, similar to PPA (but not so complex). It's in the archives.
[11:24] <dholbach> ah ok
[11:25] <DktrKranz> If REVU wants some build infrastructure, and PPA is not feasible, I'll propose it
[11:25] <persia> DktrKranz, Problem with build infrastructure for REVU is more about processing power than PPA.
[11:26] <persia> Especially considering how many first draft packages have odd bits in them that could break a buildd.
[11:28] <DktrKranz> good point.
[11:29] <DktrKranz> REVU isn't something to replace PPA
[12:20] <directhex> hang on, superm1 works at dell?
[12:21] <crimsun> yes
[12:21] <laga> yes
[12:21] <directhex> i never knew that O_o
[12:21] <Hobbsee> canonical and dellhavehired all the cool people by now.
[12:21] <Hobbsee> most of the people here seem to work for one or the other,except a few misfits.
[12:22]  * crimsun <-- misfit
[12:22]  * Hobbsee is also a misfit.
[12:22]  * directhex is more of a freak than a misfit
[12:28] <sistpoty|work> hi folks
[12:28] <sebner> sistpoty|work: ahoi =)
[12:29] <sistpoty|work> hi sebner
[12:29] <iulian> Hello sistpoty
[12:29] <sistpoty|work> hi iulian
[12:56] <Laibsch> Hi, can somebody please archive http://revu.ubuntuwire.com/details.py?package=gourmet ?
[12:56] <Laibsch> Thanks
[12:57] <persia> Laibsch, archiving
[12:57] <Laibsch> Thanks
[12:58] <persia> I'm about to start an RCbugs chase.  kaffe was mentioned previously.  Anything else anyone things I'm interested in?
[13:25] <DktrKranz> any free sponsor willing to review bug 268692? FFe have been just approved, might be a good candidate for the last sync round.
[15:14] <RainCT> uhmm.. /me is confused about bug #261935. Wrong triaging?
[15:21] <sistpoty|work> RainCT: looks like it... I've marked it as fixed, since the new version is already in
[15:21] <RainCT> sistpoty|work: I just did the same :P
[15:21] <sistpoty|work> heh
[15:22] <RainCT> if it was just a random guy it wouldn't wonder me, but seeing that Bruce is a MOTU and Canonical employee.. he must have been multitasking :P
[15:23] <StevenK> Bruce? Bryce?
[15:23] <RainCT> erm.. right, I have already closed the report and wrote what I remembered :P
[15:23] <sistpoty|work> RainCT: most probably (wasn't there a new xorg-server today? *g*)
[15:25]  * RainCT full-upgrades.. yep, there's a new one out
[15:30] <iulian> Ohh, right. Forgot to run the upgrade here.
[15:30]  * iulian presses the upgrade button now.
[15:30] <sistpoty|work> hi bddebian
[15:31] <iulian> 177 upgraded, 0 newly installed, 0 to remove and 16 not upgraded.
[15:31] <iulian> Yikes
[15:31] <iulian> Hello bddebian.
[15:32] <bddebian> Heya gang
[15:32] <bddebian> Hi sistpoty|work, iulian
[15:33]  * iulian fetched 155MB in just 43s.
[15:34] <iulian> Not bad.
[15:34] <persia> Is that a proper network connection, or just precaching?
[15:34] <RainCT> iulian: bah, I still have to wait for over 1 hour XD
[15:39] <iulian> persia: It's a proper one.
[15:40] <persia> iulian, Nice!
[15:43]  * ScottK notes that the buildd's are mostly idle waiting for your last minute bug fixes.
[15:43]  * persia needs a faster local build farm
[15:43] <persia> I'm also waiting on the rumoured kernel upload to rebuild the -rt kernel :(
[15:47] <iulian> RainCT: Just a couple of minutes more and I'm all done here :-)
[15:47]  * iulian -> shopping
[16:18] <ScottK> dfiloni: You can go ahead and upload your wxwidgets2.8 fix to intrepid-proposed.  It'll sit there until release.
[16:19] <dfiloni> ScottK: the version number as a normal SRU, right?
[16:19] <ScottK> dfiloni: Yes.
[16:19] <dfiloni> ok
[16:20] <dfiloni> ScottK: thanks
[16:43] <slytherin> persia: Do you have any docbook file containing SVG image lying around? I have not yet found time to verify fop fix as I promised geser yesterday.
[16:44] <persia> slytherin, I don't.  Sorry.  I do have the fop bug open for tracking, in case you found time whilst geser was alseep.
[16:45] <slytherin> persia: I guess I will find some time tonight. Once done I will probably ping geser
[16:46] <persia> OK.
[16:46] <persia> slytherin, Also, did Koon already talk to you about OpenWeek?
[16:46] <slytherin> persia: No. I haven't been on IRC much in last few days. I will talk to him on weekend.
[16:47] <persia> slytherin, Cool.  Thanks.
[16:47] <slytherin> persia: It is in November first week right?
[16:47] <persia> I think so.
[17:02] <slytherin> superm1: in case you haven't already checked it, there was a bug about missing netlink plugin in bluez.
[17:17] <csilk> If a developer only has copyright in a small number of files in a new packagee would I list this person in the same section as th emain copyright holder or would I do it in another section in the COPYRIGHT file?
[17:18] <RainCT> csilk: if those files are part of the main program, then in the same section
[17:18] <csilk> Thanks
[17:18] <RainCT> csilk: if it's a bundled library/file/whatever then in a separate one
[17:18] <persia> Well, it depends
[17:18] <RainCT> yw
[17:19] <csilk> persia,  the secondary person has joint copyright (with main (C) holder) on 5 .c files
[17:19] <csilk> RainCT, ^
[17:19] <persia> If the files are included in the main program, but logically distinct, http://lists.debian.org/debian-devel-announce/2006/03/msg00023.html seems to recommend a separate section.
[17:20] <persia> Oh, if it's joint copyright, and the same license, just put them in the main section.
[17:21] <RainCT> persia: do you have some example of "logically distinct" (beside bundled stuff)?
[17:21] <csilk> Ok, thanks for the link aswell, I'll save that as a reference
[17:22] <persia> RainCT, "logically distinct" could be bundled stuff, plugins, the result of a fork, an alternate UI added, or any of a number of other things.  Basically, some separable chunk of stuff that someone contributed independently of working on the main tree.
[17:24] <csilk> persia, gerping the dirs I just found a library written by a 3rd party
[17:25] <csilk> I guess that would go in a seperate section
[17:25] <csilk> it's doesnt specifiy a license, it justs (public domain, use whatever license you like) ?
[17:25] <csilk> *greping
[17:26] <persia> csilk, That's an example of something that gets it's own section.
[17:26] <csilk> Would I just note that i's under the "public domain" license or what?
[17:27] <csilk> Technically public domain isn't alicense
[17:28] <persia> You'd report that it was "in the public domain".
[17:29] <persia> Citing the PD grant and author is probably useful, as in some places authors can't grant stuff to the public, but some of those places recognise intent.
[17:29] <csilk> PD grant?
[17:29] <persia> *Don't* write "Copyright $(author)" anywhere, as it's not, if there was a public domain grant (except in jurisdictions where there is no public domain, or where authors cannot grant to the public domain).
[17:30] <csilk> Ok
[17:31] <csilk> I'll just list the authors and note that the code is in the public domain but I won't attribute copyright
[17:31] <persia> wikipedia has a reasonably good article, although my browser just crashed, eating the URL I wanted to paste.
[17:32]  * sistpoty|work calls it a day... cya
[17:32] <sebner> sistpoty|work: ciao
[17:32] <persia> Nothing in the public domain is copyrighted : that's the point.  Copyright either isn't claimed initially, isn't valid, is expired, or was explicity discarded.
[17:34] <csilk> Thanks for the help persia, just one further question, this app also contains the XMMS media player (integrated) the author of the app modifed xmms slightly so it would integrate with his code better, after listing the upstream authors of xmms should I put something like *Modified by AUTHOR * ?
[17:36] <persia> Yes, but we don't like to accept packages like that, because it's code duplication, and hurts security.  In the special case of xmms also please try to avoid linking against GTK+1.2.  Given the modifications, and that xmms has been dropped from the repo, it might not be as much of a concern.
[17:36] <persia> Note that you probably want to make sure upstream is maintaining *all* of the xmms fork, as upstream xmms is inactive, so there could be all sorts of bugs,.
[17:40] <csilk> persia, upstream isn't maintaining xmms other than making slight intergration modifications. also, when you say linking against GTK+1.2 what exactly do you mean?
[17:42] <persia> The xmms interface was GTK+ version 1.  Most of the GTK apps in Ubuntu now use GTK+ version 2.  Version 1 doesn't support niceties such as UTF-8, or current themes.  We'd like to drop it from the archive, but it's stuck by a couple things.
[17:42] <persia> Anything new that uses it is likely to be at risk.
[17:43] <csilk> I'll check it's gtk dependencies
[17:43]  * slytherin quickly searches for rdepends on gtk 1.2
[17:43] <Buiss> I am interested in Linux development and use ubuntu since 7.04. how can i find a mentor..
[17:43] <persia> Buiss, What do you seek to do?
[17:44] <Buiss> Kernel Module programming and device drivers
[17:44] <Buiss> especially
[17:45] <persia> Have you worked with kernel code before?
[17:45] <Buiss> i have written certain modules for my education purposes. Not much. I want to learn more on device drivers also
[17:46] <Buiss> I have studied DD basics
[17:46] <csilk> persia,  looks like it doesnt use the xmms UI it just takes some of the core codebase. This app required gtk-2.6 +
[17:46] <csilk> *requires
[17:46] <persia> csilk, Excellent news.  Just be careful with copyright.
[17:47] <csilk> persia,  yeah will do.   Looks like the only barrier to entry will be the fact that upstream aren't actively maintaining the xmms codebase other than (as mentioned) integration based modifications
[17:47] <persia> Buiss, Hmm.  I'm not sure.  You might do well to ask in #ubuntu-kernel, but peobably next week : this week the team is *very* busy chasing final issues with 8.10, and may not have time to help you find resources to help them.
[17:48] <persia> csilk, Yeah : that's unmaintained code that was previously dropped.  Perhaps upstream could adjust to make an audacious plugin for the integration?
[17:48] <Buiss> It is ok.. I really thank  your patience persia, I am waiting for Intrepid..
[17:49] <csilk> persia, the project owner is pretty set in his ways, I can't see him making that kind of madification just so his app will be in the ubuntu repo
[17:49] <csilk> *modification
[17:50] <csilk> persia,  if that is deffinatly a barrier to entry I'll not bother submitting to revu, I'll just stick it in my ppa and link to it on the bug tarckers feature request explaining why it can't go in the repo. The people that wanted the app would still get it in the end
[17:50] <csilk> via my ppa
[17:51] <persia> csilk, It's not definitely a barrier : it's a negative point.  That said, it would take a code review to determine how much of the code is unmaintained.
[17:52] <slytherin> persia: shouldn't you assign the bluetooth pairing bug to superm1?
[17:52] <csilk> persia, as far as I can see it's only one c source file
[17:52] <persia> slytherin, No.  I'm not him, I'm not his boss, and he hasn't asked me to assign him : therefore I won't assign him.
[17:53] <slytherin> persia: The reason I asked is he has done recent uploads and the bug seems to be important from functionality point of view.
[17:53] <persia> slytherin, Generally, unless one of those conditions apply, never assign a bug to someone : bug assignment is used to define work queues, and it's annoying to be assigned stuff that one won't do
[17:54] <slytherin> hmm, will keep that in mind.
[17:54] <persia> slytherin, If you think "Medium" is incorrect, escalate it.  That he uploaded it recently doesn't commit him to fixing all the rest of the bugs, although if someone persistently uploads things that break things and doesn't chase them, the rest of us get annoyed.
[17:55] <slytherin> I haven't had time to check it so I won't comment on the importance.
[17:55] <RainCT> csilk: you could also exclude that xmms stuff from the binary packages, then there shouldn't be any problem about that code not being maintained
[17:56] <csilk> RainCT, wouldn't that be removing core functionality from the app?
[17:56] <persia> csilk, Or if it's just one file, promise to maintain it yourself.
[17:57] <RainCT> csilk: Perhaps, I don't know what application it is. But if the xmms stuff is just an extra then removing it may be worth considering.
[17:57] <persia> If it's not extra, better to find another solution.
[17:58] <csilk> Starting to regret ever responding to this pakacge-request ;)
[17:58] <csilk> *package
[18:01] <persia> csilk, Each package is it's own adventure :)
[18:01] <csilk> That's becoming apparent haha
[18:01]  * slytherin remembers his days of fixing lucene2 and batik :-)
[18:04]  * persia gets annoyed that both MoM is out of date and DaD crashes the browser on every load
[18:05] <woody86> does anyone know if there's a way to remove a comment from LP?
[18:05] <persia> woody86, Yes, I know.  No, there isn't.
[18:06] <persia> Well, if it's spam or porn or something like that, you can ask a question on answers.launchpad.net/malone to have an admi remove it, but not for normal comments.
[18:07] <woody86> persia- well I kind of made a silly mistake, I had 2 bugs open in tabs next to eachother, and I minimized them for a little bit while I was looking some info up, and I accidentally left the comment on the wrong bug :P
[18:08] <slytherin> woody86: that is not a crime. :-)
[18:09] <woody86> yeah, but I'm going to feel bad if the guy goes through getting all these files and terminal outputs for no reason :P
[18:26] <ScottK> woody86: Then make a comment saying not to do it.
[18:41] <Adri2000> persia: DaD crashes your browser? :o
[18:42] <persia> Adri2000, Not the front page, but the universe page.
[18:42] <Adri2000> what's your browser?
[18:42] <Adri2000> I've no problem with firefox on intrepid
[18:42] <persia> epiphany 0.7.0-2
[18:43] <persia> Perhaps.  I stopped trusting firefox after it started to eat my sessions, and I discovered that the sort of bugs I was experiencing weren't considered bugs upstream, and so couldn't be fixed.
[18:44] <persia> (this was back in gutsy)
[18:45] <Adri2000> strange that it crashes, because that page doesn't have anything special embedded such as flash or java
[18:45] <Adri2000> only a ~350 lines table
[18:45] <persia> Since both firefox and epiphany use xulrunner-1.9 they shouldn't be that different
[18:45] <Adri2000> I'll try to reproduce
[18:45] <Adri2000> does main.php also crash?
[18:45] <persia> Oh, and ignore the version.  I actually have epiphany-gecko 2.24.1-0ubuntu1
[18:46] <persia> Oddly no.  Just universe (I tried 5 times)
[18:47] <Adri2000> doesn't crash here
[18:48] <persia> I'm on amd64, if that is different.
[18:48] <Adri2000> maybe
[18:49] <Adri2000> if you're looking for the merge candidate of a specific package, you can use dad.d.n/package/
[18:49] <Adri2000> but unfortunately a lot of merges are broken (at least partly due to snapshot.debian.net)
[18:50] <persia> Yeah.  I'd just pull from snapshot if it were reliable : I was more looking for a list of things that changed.  I'll use mdt.
[18:51] <persia> Mind you, what I'd like is to finish the updates to MoM to use the ideas from DaD, and keep MoM *always* running, but that never seems to work.
[18:51] <persia> Main reason being that the MoM backend seems to do a better job of pulling stuff than the snapshot.debian.net backend.
[18:52] <Lutin> persia: MoM mirrors the debian archive, afaik
[18:52] <RainCT> persia: I use Epiphany too and it doesn't crash here
[18:52] <persia> RainCT, which arch?
[18:52] <Adri2000> persia: well, I recently signed some copyright assignement thing to allow the patches to be included in MoM, so hopefully that will happen soon, but it's on Keybuk's side
[18:53] <persia> Lutin, I think it pulls from a mirror of the archive, and keeps a full history or something, but yes.
[18:53] <RainCT> persia: i386
[18:53] <persia> RainCT, Yeah.  I think it's an amd64 issue.  amd64 seems not to be as good in intrepid as it has been for some previous releases.
[18:54] <RainCT> Adri2000: o.O
[18:57] <Adri2000> RainCT: ?
[18:57] <Adri2000> copyright assignement?
[19:15] <RainCT> Adri2000: yep
[19:38] <Adri2000> RainCT: I had to give my copyright to canonical for the patches to be accepted
[19:40] <Adri2000> RainCT: I signed http://upstart.ubuntu.com/wiki/CopyrightAssignment with s/upstart/MoM/
[19:41] <laga> haha
[19:41] <laga> yay for dual licensing
[19:45] <RainCT> Adri2000: ah, but with clause 5 it isn't that bad
[19:49] <persia> clause 7 could have viral stickiness
[21:06] <persia> I made a mistake in ordering.  Could someone from MOTU Release ACK bug #287999, or ask for rejection from unapproved?
[21:08] <iron> hi
[21:10] <iron> just a question which knowledge is needed to be a kernel-hacker
[21:11] <iron> it is enough to be a bachelor of science or should i be a bachelor of engi.
[21:12] <RainCT> iron: Well, I have no idea about kernel hacking but I'd say you don't need any bachelor at all, but time and a desire to learn :)
[21:14] <RainCT> iron: and knowledge of C wouldn't do any bad neither. But best ask at #ubuntu-kernel or directly on some kernel place
[21:16] <iron> RainCT: right, but im studying  already therefore am asking. i have knowlegde of c . ok thx i will join #ubuntu-kernel
[21:16] <iron> RainCT: thx for your answere
[21:16] <RainCT> yw
[21:17] <iron> yw?
[21:17] <RainCT> iron: you're welcome :)
[21:18] <iron> RainCT: thx
[21:19] <iron> if i find a way to devl. i will give a peace of my knowledge into community
[21:20] <iron> s/peace/piece
[21:22] <kirkland> who can "accept" a minor upload for a universe package?
[21:23] <ScottK> kirkland: MOTU Release needs to approve it and then Ubuntu Release or and archive admin can actually accept it.
[21:23] <ScottK> kirkland: What's up?
[21:23] <ScottK> kirkland: musica?
[21:26] <kirkland> ScottK: yeah, fixes a couple of minor work-out-of-the-box issues
[21:26] <ScottK> Looks fine.
[21:27] <kirkland> ScottK: could live without it, but it sure would be nice to have, not on any install media, etc. etc.
[21:28] <ScottK> I've asked for it.
[21:30] <kirkland> ScottK: awesome, thanks
[22:22] <tbielawa> Can anyone give some advice for things to consider if I was to start packaging something for jaunty? Or is it to early to consider that?
[22:31] <RainCT> tbielawa: you could check the needs-packaging bugs on LP, perhaps you like some of the applications suggested there
[22:33] <tbielawa> RainCT, I mean to inquire into technical things to consider. New standards to package against, such as policy or compiler versions. If you can't think of any, then awesome :-)
[22:34] <RainCT> tbielawa: Oh, OK. Sorry. Well, no, just the usual stuff.. Check the wiki, there should be plenty of information
[22:35] <tbielawa> RainCT, exactly what I was looking for. Thanks
[22:41] <ScottK> persia: It'd be nice if the Ubuntu Studio release delegate would make some kind of statement about your ubuntustudio-menu upload.
[22:42] <persia> ScottK, The release delegate currently has extremely limited access to the network, which is why I asked for someone from MOTU Release to ACK.  The release delegate will ACK as soon as next on the network.
[22:42] <persia> (unless someone else ACKs first).
[22:42] <ScottK> OK.
[22:43] <persia> I'm sorry to have uploaded before getting the ACK.  That was a mistake.
[22:43] <ScottK> persia: It doesn't particularly matter since Ubuntu Release isn't accepting stuff unless we tell them to.
[22:43] <ScottK> persia: You're confident this is a good fix?
[22:44] <persia> I tested it before/after and it fixed it for me.  I'd have to regenerate a CD image for a proper test, but would rather spend my CPU cycles running builds against the RCbugs list.
[22:44] <persia> Although it's my debdiff and my upload, the author of the patch is the primary author of ubuntustudio-menus
[22:46] <ScottK> persia: OK.  I'll go with that.
[22:46] <persia> Thanks.
[22:47] <persia> zul, Are we affected by Debian bug #499282 ?
[22:48] <ScottK> persia: Ack'ed to Ubuntu Release.
[23:33]  * persia shouldn't have put off the RCbugs investigation.  The remaining ones are all sticky and unpleasant.
[23:40] <sistpoty> hm... anyone knows how long we've got until final, final freeze (as in no more uploads)?
[23:42] <ScottK> sistpoty: Glad you're here.  I don't know, but you can ask slangasek in #ubuntu-release.  I'll be out this evening and so I think you're the duty dude for motu-release.
[23:42] <slangasek> Monday-ish
[23:42] <sistpoty> ScottK: damn, wanted to go to bed in an hour or so
[23:43] <sistpoty> slangasek: ok, so up to sunday we can still make uploads? If so, maybe we should announce that date on u-d-a?
[23:43] <slangasek> announcing Sunday?  that would be fine
[23:43] <sistpoty> ok, I'll put up a draft and ask for a review then ;)
[23:44] <ScottK> sistpoty: IIRC Monday 0600 UTC was the cutoff for Hardy.
[23:44]  * ScottK heads out.
[23:44] <sistpoty> cya ScottK
[23:44] <persia> sistpoty, I was advised "Sunday" during the release meeting.
[23:45] <ScottK> As long as it's still Sunday at slangasek's house, I think it's OK.
[23:46] <slangasek> I'm working London hours next week, so 0600 UTC isn't far off
[23:46] <persia> Could someone from MOTU Release please make a push/SRU call for bug #288938
[23:49] <superm1> slangasek, if it's mondayish would you (or someone else on ubuntu-release) mind making a call on the hal & bluez bug i've subscribed ubuntu-release to by sometime tomorrowish so i'd be able to upload it prior to mondayish or defer it to intrepid-updates otherwise?
[23:49] <slangasek> superm1: yes
[23:50] <slangasek> (ish)
[23:50] <superm1> thanks
[23:50] <tbielawa> I just want to say: debtree + dot = awesome for producing dependency graphs :)
[23:54] <sistpoty> persia: if the debdiff boils down to the patch in the debian bug, please go ahead with xmoto
[23:55] <sistpoty> (and feel free to quite this irc message *g*)
[23:55] <persia> sistpoty, quoting and subscribing the archive admins.  I'll upload if nobody pushes, but I don't like to upload things that could be syncs.
[23:56] <persia> And thanks for the reminder.  I'll stuff debdiffs in them
[23:56] <sistpoty> persia: well, go ahead == do the right thing to get it in ;)