[00:00] <ScottK> http://ubuntu-releases.cs.umn.edu/hardy/ as an example.
[01:52] <sparr__> this is a bug, no?  /usr/sbin/invoke-rc.d: 274: /sbin/runlevel: not found
[02:41] <LaserJock> man, I wish these earthquakes would stop :/
[02:50] <ajmitch> LaserJock: move to NZ, we never have earthquakes here...
[02:51] <LaserJock> but you have ... new zealanders ;-)
[03:02] <RAOF> You could come to .au - we don't have earthquakes either, and a lower concentration of new zealander's than NZ :)
[03:02] <PMantis> Australia?
[03:03] <ajmitch> RAOF: depends on which suburb you're in :)
[03:11] <LaserJock> RAOF: sorry, you may not have many new zealanders, but your australian concentration is a bit high ;p
[04:46] <jdong> ia64 build of iscsitarget 0.4.15-5ubuntu2 in ubuntu intrepid RELEASE
[04:47] <jdong> oh my god oh my god oh my god!!!1
[04:47] <jdong> IT SAYS INTREPID!!!!
[04:47] <nixternal> haha
[04:47] <nixternal> all of my packages have been coming back with FTBFS for lpia
[04:47] <jdong> nixternal: that's a bug in the hardware then ;-)
[04:48] <nixternal> heh, rsibreak-kde4 FTBFS ia64 :)
[04:48] <nixternal> jeesh, I am getting a bunch of Intrepid emails tonight
[04:49] <gnomefreak> do one of you remember the command to automagicly add the next build to changelog (something like dch -i debian/changelog?
[04:49] <emgent> :D
[04:49] <calc> intrepid has been open for a couple days now
[04:50] <calc> well in the archive, its still frozen aiui
[04:50] <calc> doko has been uploading toolchain stuf for a while now
[04:51] <calc> zul: http://archive.ubuntu.com/ubuntu/dists/intrepid/
[04:51] <zul> calc: I know I was kidding
[04:51] <calc> zul: ok :-P
[04:53] <calc> hmm gta iv released today
[04:55] <ajmitch> ah, an important release
[04:55] <ajmitch> but will it run on ubuntu?
[04:57] <calc> isn't it for consoles? :)
[04:57] <calc> best solution to get rid of windows, get a console for games :)
[04:59] <calc> i don't actually like gta just noticed it made the news with a poll asking should violent games be sold
[05:00]  * ajmitch doesn't tend to play many games
[05:01] <ajmitch> world of warcraft a bit, but cutting back on that for sanity's sake
[05:10] <zul> i still like pong
[05:48] <RoAkSoAx> hi there, anyone around?
[05:54] <CrippledCanary> jdong: I just subscribed -sponsors on bug #224241
[06:41] <dholbach> good morning
[06:52] <LaserJock> morning dholbach
[06:54] <dholbach> hiya LaserJock
[06:54] <LaserJock> I guess this means I should be going to be
[06:54] <LaserJock> ;-)
[06:55]  * dholbach hugs LaserJock
[06:55] <ajmitch> hello dholbach, goodbye LaserJock
[06:55] <dholbach> hi ajmitch
[07:06] <PMantis> HI guys, I have my own repo setup... and I'm using "gpg -abs -o Release.gpg Release" to secure it. However, I get this on apt-get update unless I delete the .gpg file: "Failed to fetch http://domain.com/apt-repo/binary/Release"
[08:46] <secretlondon> can someone sanity check my bug with a .pc file before I send it to debian?
[08:46] <secretlondon> https://bugs.edge.launchpad.net/ubuntu/+source/soundtouch/+bug/214929
[08:46] <secretlondon> This is half the cause of an audacity bug
[09:00] <YokoZar> dholbach: did you catch the confusion regarding SRU process yesterday?
[09:01] <dholbach> YokoZar: no, not really - what was it about?
[09:02]  * dholbach rushes out to walk the dog for a bit - brb
[09:09] <\sh> YokoZar, what was it?
[09:57] <YokoZar> dholbach: \sh: Basically I followed the process on the SRU wiki page and ended up uploading without an ack since it wasn't clear I was supposed to wait for one between step 3 and 4
[09:57] <YokoZar> I assumed that uploading to -proposed was how the SRU team reviewed proposed updates
[09:58] <\sh> YokoZar, hmm...
[09:58] <dholbach> YokoZar: best to ask members of https://launchpad.net/~motu-sru/+members if they can clarify the docs
[09:59] <laga> i wonder if someone from motu-sru can take a look at bug #220087 and ACK it. it fixes an upgrade problem
[10:01] <YokoZar> Also I guess it's worth pointing out that I'm not sure what to do now.
[10:01] <YokoZar> \sh: you've seen the bug right?  Very minimal patch, fortunately.  Also I've tested it to work.
[10:01] <\sh> YokoZar, tbh, I think there needs to be a review of the docs for SRUs...because I wonder if any member of motu-sru does know everything about special packages...
[10:02] <\sh> YokoZar, yes...nothing which can break existing wine installations
[10:05] <coolbhavi> Hello  Can you please point out the errors: http://paste.ubuntu.com/8868/
[10:07] <\sh> coolbhavi, you still have diff fragments in your control file
[10:07] <\sh> e.g. <<<<<<< mon-0.99.2-11ubuntu1 (ubuntu)
[10:07] <\sh> and [10:07] <\sh> and other stuff
[10:07] <coolbhavi> How to overcome?
[10:08] <\sh> coolbhavi, remove it in the right way?
[10:08] <\sh> following merging documentations :)
[10:11]  * \sh fights more with bacula
[10:11] <coolbhavi> means removing lines 9 10 and 11?
[10:12] <\sh> coolbhavi, dunno...it depends if the package is a merge or not.
[10:13] <\sh> coolbhavi, if there is an ubuntu change, so it's a merge, you need to follow the DebianMaintainerField guidelines for ubuntu (which you can find on the wiki)
[10:14] <coolbhavi> I have got the major part of merging into my head but the conflicts part I m not understanding at the moment...:(
[10:14] <Hobbsee> coolbhavi: differences between ubuntu and debian.  you have to merge them, and keep the bits you want.
[10:18] <coolbhavi> Hobbsee : I understood that but how to edit control files? I m up with it for past hour but I keep getting same error... :(
[10:18] <Hobbsee> coolbhavi: ...with a text editor.
[10:19] <\sh> grmpf
[10:20] <\sh> bacula is missing somehow the drop tables script in /usr/share/bacula-director
[10:20] <coolbhavi> Hobbsee : yes I know but can you give an example please of a sample control file before changes and after changes in merging?
[10:20] <Hobbsee> coolbhavi: wouldn't that depend on the changes to the control file?
[10:20] <Hobbsee> the non-merged is what you have now.
[10:21] <Hobbsee> the merged looks more like a standard control file, which you'll find in the packaging guide.
[10:22] <coolbhavi> OK thanks I ll come come back if any doubts are there.. Please bear my questions....
[10:28] <coolbhavi> OK is this a standard control file? http://paste.ubuntu.com/8874/
[10:29] <Hobbsee> yes
[10:30] <coolbhavi> Ok thanks
[10:39] <coolbhavi> Now is my control file correct? http://paste.ubuntu.com/8878/
[10:40] <\sh> grmpf...
[10:40] <Hobbsee> coolbhavi: yes, style-wise, it's correc.t
[10:40] <Hobbsee> i've no way of knowing whether you picked the right bits to merge.
[10:41] <coolbhavi> I m following yesterdays session on merging at the Open week...:)
[10:43] <pochu> so does anyone have a needs-packaging wishlist for a Python application/module?
[10:44]  * \sh needs to recreate his whole build infrastructure...can somebody do me a favour and fix bacula? :)
[11:36] <Kopfgeldjaeger> hi
[11:39] <Kopfgeldjaeger> i have a package that patches the configure file. it adds launchpad-integration to lines like <error: Package requirements: libegnome-something \n>. should i add those lines to all messages like that?
[11:44] <Kopfgeldjaeger> yes, i should. ok.
[11:49] <fargiolas> jdong: ping?
[12:22] <Sveinung> does anyone know when all the packages from Debian will be auto synced to Intrepid?
[12:25] <mrpouet> hi
[12:25] <StevenK> Sveinung: Sometime after the toolchain is sorted out
[12:26] <Sveinung> StevenK: thank you. About how long time do you belive that will take? (days, weeks or months?)
[12:27] <dholbach> a very few days
[12:27] <Sveinung> thanks
[12:28] <sebner> dholbach: heya. any news/progress about the new "contributors" group?
[12:28] <dholbach> sebner: as far as I can see no blockers, now that the name is sorted out
[12:30] <james_w> dholbach: have you spoken to sistpoty about co-ordinating the revu-uploaders name change? Or is that decision not final yet?
[12:31] <sebner> dholbach: kk, just want to join ASAP to start the new development cycle with a new mail adress for the changelogs ^^  Btw do you know where to send the application?
[12:31] <dholbach> sebner: motu-council@lists.u.c
[12:31] <dholbach> james_w: no, I didn't talk to him about it yet - it'd be nice if that was sorted out too
[12:32] <sebner> dholbach: great. thx :)
[12:32] <dholbach> ROCK :)
[12:32] <james_w> sebner: https://lists.ubuntu.com/archives/motu-council/2008-April/001035.html is an example
[12:32] <dholbach> make sure you CC your sponsors :)
[12:32] <sebner> dholbach: kk. I have testimonials on my wiki page ^^ xD xD XD
[12:32] <sebner> james_w: thx :)
[12:33] <sebner> dholbach: a good laugh ;) https://wiki.ubuntu.com/StefanEbner
[12:33] <james_w> dholbach: I can speak to him today if he is on. Is the decision at the meeting final? There were no responses to the minutes.
[12:34] <persia> Lack of objection to the minutes is what makes a decision "final".  Note that such a "final" decision is subject to change from new agenda in a future MOTU Meeting.
[12:34] <james_w> persia: cool, thanks.
[12:35] <persia> james_w: Please note that in general, building consensus is preferred to any formal process.  The "formal rules" tend to based on precedent from previous cases where there was confusion or disagreement.
[12:36] <persia> Wherever possible, it's best to proceed on your best understanding, and engage in discussion if this doesn't match your perception of another's understanding.
[12:36] <james_w> ok
[12:38] <persia> For wide-ranging changes that affect a lot of people, I like to have final discussion at a MOTU Meeting, just because that way everyone has time to prepare, and can share their thoughts.  On the other hand, the decision (new for gutsy) to use massive task lists to handle transition bugs was taken without a MOTU Meeting.  It really depends on the subject, and whether there is any controversy or confusion.
[12:49] <\sh> grmpf...
[12:49]  * \sh needs a hp tape library somehow
[12:53]  * ScottK doesn't think the team rename should be done until after someone has a REVU patch to change it to work with the new name.
[12:58] <james_w> ScottK: that's exactly why I was going to talk to sistpoty
[12:58] <RainCT> ScottK: dunno what you were talking about but if you want to change the team name I can update REVU if necessary (changing the group name seems like a pretty trivial change)
[12:59] <ScottK> RainCT: I'm not saying it's easy or hard, just that it needs to be done in a coordinated way (unlike last time where MC broke REVU keyring syncs without even knowing they'd done it).
[13:01] <pochu> nxvl: I think I'm going to 'repackage' terminator for the Python Packaging session ;)
[13:01] <pochu> nxvl: it's the perfect candidate as it's simple and uses distutils :)
[13:02] <RainCT> actually, I think I'm going to move this to REVU's config file..
[13:05] <pochu> nxvl: do you know where can I find some terminator screenshots online? the link at lp.net/terminator doesn't load...
[13:06] <CrippledCanary> ScottK and RainCT: I manage to sort out the bug for #224221 :)  .....
[13:07] <CrippledCanary> had to study some debconf :)
[13:07] <ScottK> Kewl.
[13:08] <CrippledCanary> now just waiting for a sponsor upload
[13:10] <sebner> persia: sended my application :) Awaiting for moderators approval. I have you take that not too serious because my applications is somehow a little bit sloppy ^^
[13:11] <sebner> *hope
[13:53] <ScottK> jdong: First Hardy backport from Intrepid is done: https://launchpad.net/ubuntu/hardy/+source/devscripts/2.10.26ubuntu3~hardy1
[13:54] <ScottK> FYI: Devscripts that (among other things) has intrepid as the default is backported to hardy-backports and will be available there once it
[13:54] <ScottK> is built/published
[13:54] <jdong> ScottK: nice
[13:55] <ScottK> ... intrepid as default for dch ...
[13:56] <ScottK> Or not.  It's not depwait.  Built in my pbuilder.  Urgh.
[13:56] <jdong> haha
[13:57] <ScottK> jdong: It's libterm-size-perl and the whole main/universe thing again.
[13:57]  * ScottK gives up on backporting anything in Main until it's fixed.
[13:57] <jdong> ScottK: grumble, the bug is "fixed" in lp development
[13:57] <jdong> hopefully it'll be really fixed in the upcoming upgrade
[13:58] <ScottK> Would you please beat on them and make sure.
[13:58]  * jdong nods
[13:58] <ScottK> I guess once that fix gets release it'll un-depwait automatically anyway.
[14:08] <Mez> \sh, ping
[14:09] <\sh> Mez, pong
[14:09] <sistpoty|work> hi folks
[14:09] <Mez> \sh, the new xdebug package is in the NEW queue for debian. Do you want me to build a 0ubuntu1 for intrepid ?
[14:10] <\sh> Mez, if it's in debian, we can sync it later.
[14:10] <sebner> heya sistpoty|work
[14:10] <sistpoty|work> hi sebner
[14:10] <\sh> intrepid is still frozen for toolchain
[14:11] <\sh> Mez, but we should watch out for indirect bugs, like php-xdebug + zend-platform == crash ;)
[14:11] <\sh> or better the other way around
[14:11] <Mez> \sh ah yes, we have a while yet - I forgot. Though it might be fun as It uses 'xdebug' as the source package
[14:12] <\sh> Mez, this we can resolve with pitti in a clean way imho
[14:13] <Mez> \sh, I'm sure it can - but it means more work for SOMEONE
[14:13] <Mez> by the way do you/the guy who made the ubuntu package have alioth accounts?
[14:13] <\sh> Mez, I have yes..
[14:13] <Mez> \sh, what's your alioth account ?
[14:14] <Mez> (as we're using that + collab-maint for xdebug)
[14:14] <\sh> Mez, oh damn..wrong question ;) wait .. i'll have to check
[14:14] <Mez> sh-guest ? :P
[14:15] <Mez> \sh shermann-guest
[14:16] <\sh> Mez, yes
[14:16] <\sh> Mez, but the -guest part I never wanted...
[14:16] <\sh> but alioth is forcing me to use this :(
[14:17] <Mez> \sh, yeah - it does unless you're a DD
[14:17] <\sh> well, imho this will never happen ,-)
[14:18] <Mez> \sh, why not?
[14:20] <james_w> hi sistpoty|work
[14:21] <james_w> sistpoty|work: for the renaming of u-u-c to go ahead do you just require a patch to the source and then co-ordination of the time to rename, or is there something else involved?
[14:21] <\sh> Mez, I disagree with some of debians ways
[14:21] <Mez> \sh, care to explain?
[14:23] <\sh> Mez, wrong place, wrong time
[14:23] <Mez> \sh, no problem
[14:28] <sistpoty|work> james_w: it's just patching the code and renaming the team afaik... siretart wanted to take care for that (and iirc split off the keyring handling from revu to a different project when doing so)
[14:28] <james_w> sistpoty|work: ok, thanks, I'll talk to him about it.
[14:29] <siretart> ah, right
[14:29] <siretart> that was as well on my list
[14:29] <james_w> hi siretart
[14:29] <siretart> hey james_w
[14:32] <siretart> sistpoty|work: I notice that the daily keyring sync script has been disabled from revu1's cronjob. do you know if we have another place where the keyring sync is done from?
[14:32] <siretart> I don't remember disabling it
[14:32] <sistpoty|work> siretart: nothing on spooky at least
[14:32] <siretart> ok
[14:34] <james_w> sistpoty|work: do I remember right that you also requested that the ownership of revu-uploaders be transferred to revu admins?
[14:35] <sistpoty|work> james_w: yes, either /me or siretart did that... but it's not really a problem if that doesn't happen imo
[14:36] <siretart> james_w: yes, I requested ownership to be transferred to revu-admins
[14:37] <siretart> james_w: I requested that because I thought only the owner of a team can rename it. it seems that every administrator (revu-admins is) can do that
[14:37] <siretart> james_w: so my request isn't that urgent. still, I think that revu-admins is a more appropriate owner than motu-council, but YMMV
[14:38] <\sh> revu is completely separated from motu, I thought
[14:41] <siretart> \sh: sort of. revu is a service offered by ubuntuwire for ubuntu developers.
[14:41] <siretart> sistpoty|work: james_w: team renamed, keyring sync started. seems to work
[14:41] <sistpoty|work> siretart: woohoo, thanks a lot :)
[14:42] <james_w> siretart: fantastic, thanks.
[14:42] <persia> I'd agree that "revu-uploaders" belongs to revu-admins, rather than motu-council.  motu-council may be responsible for a different open team, but that's another issue, for another day.
[14:44] <siretart> wiki page updated
[14:44] <siretart> if you find any missing references to ubuntu-universe-contributors, please fix them to mention revu-uploaders!
[14:46] <sistpoty|work> siretart: did you also update revu trunk?
[14:46] <siretart> sistpoty|work: sorry?
[14:46] <siretart> sistpoty|work: no, I didn't commit the change yet
[14:46] <sistpoty|work> siretart: ah... then I don't need to wonder why I'm not getting a mail *g*
[14:48] <persia> Should old specs also be updated to reflect the team name change?
[14:49] <siretart> sistpoty|work: production branch updated
[14:49] <sistpoty|work> thanks a lot, siretart!
[14:50] <sistpoty|work> persia: might make some sense, I guess
[14:50] <sistpoty|work> persia: do you mean the revu2 spec? iirc it's referred to from elsewhere
[14:50] <sistpoty|work> (so it makes sense to update it)
[14:50] <persia> OK.  I'm just updating the results from a full text search of the wiki then, excepting meeting logs and personal pages.
[14:52] <sistpoty|work> thanks persia
[14:57] <james_w> Thanks persia, you beat me to it.
[14:57] <persia> I'm unsure about https://wiki.ubuntu.com/KubuntuTutorialsDay/GetYourWorkIntoKubuntu  Anyone have an opinion?
[14:58] <james_w> persia: I just added a note at the point where it is mentioned to explain it, do you think that is correct?
[14:59] <ScottK> What's your question about it?
[14:59] <sistpoty|work> looks good james_w
[14:59] <persia> Well, I'm not sure about editing an IRC log.  it feels like editing an old changelog entry.  I think it'd be better to extract the useful content from the log, and put it into a HOWTO somewhere, if that hasn't been done already.
[15:00] <persia> ScottK: I'm not sure I should s/ubuntu-universe-contributors/revu-uploaders/
[15:00] <ScottK> Maybe add a footnote at the bottom.
[15:29] <Hobbsee> bug 8896
[15:35] <broonie> DktrKranz2: I've actually had one of teh SCons developers offer as well.
[15:47] <DktrKranz2> broonie: no problem then :)
[15:47] <DktrKranz2> they know better than me, thanks ;)
[15:48] <broonie> DktrKranz2: Well, he knows nothing about packaging.
[15:49] <broonie> DktrKranz2: I'm thinking team maintinance might be best.
[15:49] <DktrKranz2> sounds good
[15:49] <broonie> How about I look at uploading your package tonight and put you guys in touch with each other?
[15:50] <broonie> I do want to give up the package since I'm not enjoying maintaining it at all any more.
[15:50] <DktrKranz2> broonie: great! I'll be mostly offline due to adsl failure these days, I found a old modem and I can connect from time to time
[15:51] <DktrKranz2> hope to be back in action soon
[15:51] <DktrKranz2> can I/we poke you for sponsorship?
[15:52] <broonie> Yes, of course.
[15:52] <DktrKranz2> good :)
[15:54] <DktrKranz2> broonie: I noticed link I gave you is incorrect, do you want the good one?
[15:54] <broonie> Please.
[15:54] <DktrKranz2> dsc is here: http://mentors.debian.net/debian/pool/main/s/scons/scons_0.98.3-1.dsc
[15:54] <broonie> Could you e-mail it, please?
[15:55] <DktrKranz2> sure, just a second
[15:55] <broonie> I'll not look at it until this evening.
[15:56] <DktrKranz2> done
[15:57] <\sh> hey jono
[15:58] <Hobbsee> uh oh, i'ts jono!
[15:58]  * Hobbsee runs and hides
[15:59] <jono> hey
[15:59] <jono> :)
[15:59] <DktrKranz2> broonie: in case of troubles,  just drop me a line by mail or in IRC and I'll catch it when back online
[15:59] <\sh> jono, will you attend LT this year after UDS? :)
[16:13] <jdstrand> hi ScottK
[16:13] <jdstrand> ScottK: I finally looked at bug 217256 and added a comment recommended moving forward with SRU for dapper
[16:14] <jdstrand> ScottK: sorry it took so long-- got *really* busy with hardy release
[16:23] <jdstrand> leonel: hi! I was just looking at bug #213500
[16:23] <jdstrand> leonel: can you update your dapper debdiff to update 00list and retest?
[16:26] <leonel> jdstrand: PLOP  sorry ..   I'll redo de debdiff
[16:27] <emgent> heya people
[16:27] <jdstrand> leonel: thanks!
[16:27] <jdstrand> hi emgent
[16:27] <emgent> hey jdstrand :)
[16:30] <leonel> jdstrand: also i'm cooking  another debdiff for bug #217256  for feisty and  gutsy
[16:33] <jdstrand> leonel: ok. ping me when ready
[16:33] <leonel> jdstrand: will do
[16:38] <sebner> geser: around?
[16:55]  * \sh heads home
[16:57] <geser> sebner: yes
[16:58] <sebner> geser: :). I suppose you attended the MC meeting today? I read the minutes. What does that means now?
[17:00] <geser> sebner: if we don't reschedule the meeting for sometime later this week, the next meeting will be next wednesday
[17:01] <sebner> geser: that also means until then *nothing* will be done?
[17:02] <geser> very likely, perhaps only the team rename
[17:03] <jdong> [  144.547466] wifi0: FAILED verification of AR5K_PHY_AGCCOARSE_HI default value [found=0x6e (-18) expected=0x6e (-18)].
[17:03] <jdong> heh.
[17:04] <geser> sebner: but open applications aren't only processed during the meeting. during the meeting we only look which ones are still open.
[17:04] <jdong> I don't know what that means, but it sure doesn't speak too highly of madwifi...
[17:04] <sistpoty|work> well, there's a difference between 0x6e and 0x6e... probably a very subtle one *g*
[17:05] <jdong> :)
[17:05] <sebner> geser: ok. thanks
[17:14] <geser> sebner: as your application is on the MC radar, we won't ignore you for to long :)
[17:14] <sebner> geser: ah. you already noticed ^^
[17:54]  * sistpoty|work heads home
[17:54] <sistpoty|work> cya
[18:09] <leonel> jdstrand: done the debdiff for  bug 213500
[18:26] <jdstrand> leonel: thanks-- and you tested it too? (the bug just said the debdiff was updated)
[18:35] <leonel> jdstrand: there's a build error  fixing it
[18:37] <bddebian> Heya gang
[18:53] <geser> Hi bddebian
[18:53] <bddebian> Heya geser
[19:06] <wasabi> So... probably a simple problem on my part; genchanges is saying it cannot read the files list file: No such file or directory.  Probably just a missing file I didn't create, but I can't figure out which one.
[19:06] <wasabi> Basic packaging help. ^
[19:08] <LaserJock> sebner: are you subscribed to motu-council?
[19:17] <ScottK> jdstrand: I'm back now.
[19:17] <ScottK> jdstrand and leonel: My preferred solution for Dapper is to copy clamav from dapper-backports to dapper-updates/-security.  That'll be one less variant we have to make patches for in the future.
[19:21] <jdstrand> ScottK: understood, and I expressed my opinion on that in the bug
[19:21] <ScottK> So I guess I need to harass an archive admin then?
[19:21] <jdstrand> ScottK: looking at the code, IMO it will need full SRU, but at least it'll be the last time
[19:21]  * jdstrand nods
[19:21] <ScottK> OK.
[19:22] <jdstrand> ScottK: but I didn't do the testing
[19:22] <ScottK> Right.
[19:22] <ScottK> Testing is mostly use it and see it not break.
[19:22] <ScottK> The security hole is known fixed in 0.92.1, so that's not at issue.
[19:24] <leonel> ScottK: jdstrand  not to be lazy from me  but   agree with ScottK's  solution
[19:24] <jdstrand> leonel: I agree too
[19:24] <jdstrand> it just isn't in there *yet*
[19:25] <ScottK> leonel: In the scheme of things, I'd suggest focus your patching on feisty/gutsy if you have to pick.
[19:26] <ScottK> pitti did the last clamav pocket shuffling, so I'll ask him on Friday.
[19:34] <leileilol> think there's a chance for libmodplug to be updated to the latest working version?
[19:34] <leileilol> the current one in the repositories is a bit old and doesn't sound as good as the latest
[19:34] <leileilol> although xmms is depreciated, there is one game I know of that uses libmodplug
[19:34] <leileilol> (nexuiz)
[19:35] <ScottK> leileilol: For Intrepid, yes.  After that maybe a Hardy backport.
[19:39] <leonel> ScottK: working on
[19:41] <ScottK> K
[19:53] <leileilol> the libmodplug in ubuntu has a problem with patterns in audacious, like makes the first pattern plays twice
[19:53] <leileilol> and then ends the song abruptly
[20:27] <mysterycool> Hello.
[20:31] <mysterycool> I am interested in requesting a mentor to guide me through in order to become a MOTU. I will write an email in a bit and im wondering if u could plz tell me when i'll most probably get a response from a mentor.
[20:34] <james_w> mysterycool: there are a few people waiting for mentors at the moment, so you will probably join a queue of people I'm afraid.
[20:34] <james_w> you can start working without one though, so don't let it stop you
[20:34] <mysterycool> hmm, k, then I think ill get working around with packaging stuff and maybe request one in a while or so =]
[20:35] <james_w> and any contributions you can make beforehand will probably make you more appealing to invest time iin as your commitment will be more clear.
[20:35] <RoAkSoAx> hi there, to start merging (for this new development cycle) i should be in intrepid right??
[20:40] <cyberix> Does Ubuntu Wine team have an irc channel?
[20:40] <james_w> RoAkSoAx: you mean running intrepid?
[20:41] <ogra> hehe
[20:41] <ogra> RoAkSoAx, not even hardcore devs would do that in the next four weeks :)
[20:41] <ogra> as soon as the merging starts intrepid will eat your children
[20:41] <james_w> cyberix: I don't think so, they just discuss things here.
[20:41] <RoAkSoAx> james_w, yes... to do merges... or can i create a pbuilder enviroment for intrepid un my Hardy installation?
[20:42] <ogra> there ill be a debootstrap in hardy-updates that will support building chroots/pbuilder for intrepid on hardy
[20:42] <james_w> RoAkSoAx: yup, you can. That's the way most people will do it for a while
[20:43] <james_w> pbuilder/debootstrap/vm etc. at least
[20:43] <RoAkSoAx> james_w, so do i just to this?: sudo pbuilder create --distribution intrepid --othermirror "deb http://archive.ubuntu.com/ubuntu intrepid universe multiverse"
[20:43] <ogra> but give it still some days, the toolchan is just being built
[20:44] <james_w> RoAkSoAx: yep, I think that's right, but as ogra says give it a few days.
[20:45] <RoAkSoAx> ok, because after doing that i have this error: http://pastebin.ubuntu.com/9012/
[20:45] <ogra> you cant do that yet
[20:45] <ogra> there is no intrepid
[20:46] <ogra> only if the toolcain has built and someone pushed a new debootstrap to hardy-updates
[20:46] <ogra> dont bother to try before
[20:46] <RoAkSoAx> oh ok, thanks ;)
[20:47] <ogra> someone will surely yell in #ubuntu-devel or put it in the channel topic if you can
[20:49] <ffm> How do I get a debdiff I made accepted?
[20:52] <james_w> ffm: you should subscribe the sponsors team, then someone will review it and upload if it is ready
[20:53] <ffm> james_w: Ok. Should I put that I fixed a bug in the changelog of the debdiff? (and if so, can I just edit the diff file instead of going through the process all over again?
[20:53] <james_w> ffm: yes and possibly, though editing a diff can make it not apply properly
[20:54] <james_w> if you simply edit a line you are safe, but adding a new line means you need to tweak the numbers at the top of the hunk
[20:55] <ffm> james_w: Thanks.
[21:02] <Son26> hi ;)
[21:02] <james_w> hi
[21:03] <Son26> what this?
[21:04] <james_w> Son26: you can find out more about what we do at https://wiki.ubuntu.com/MOTU
[21:05] <Son26> what this? page?
[21:11] <Son26> hw?
[21:19] <Son26> james_w: No!
[21:20] <laga> ?
[21:20] <Kopfgeldjaeger> can i unsubscribe someone else from a bug?
[21:25] <slangasek> Kopfgeldjaeger: no, you need a launchpad admin for that
[21:26] <Kopfgeldjaeger> ok. if i upload a new package, should i upload *.dsc, *.diff.gz and *.orig.tar.gz? or link to the orig file? or create a get-orig-source rule?
[21:39] <Mez> wow, this rules file is fun
[21:39] <Mez> mkdir  etc/etc/etc/etc/etc
[21:39] <Mez> cp etc etc/etc/etc/et
[21:39] <Mez> over and over again
[21:48] <slangasek> Mez: bwuh?
[21:48] <Mez> slangasek, the package I'm making
[21:49] <Mez> It basically just copies files to the right paths for the respective packages
[21:53] <RainCT> Mez: why don't you just use dh_install?
[21:53] <Mez> RainCT, I might... dunno yet
[21:53] <slangasek> Mez: so you don't mean "etc/etc/etc/etc/etc" literally...? :)
[21:53] <Mez> slangasek, nope
[21:53] <Mez> lol
[21:54] <slangasek> ok, that's what was frightening me
[22:05] <norsetto> LaserJock: can you pls. check bug 221399 and eventually ack it?
[22:07] <LaserJock> norsetto: k
[22:07] <norsetto> LaserJock: thx
[22:25] <Jazzva> Should I subscribe motu-sru and prepare sru bug report for bug 219303 in order to include this fix in 8.04.1?
[22:42] <norsetto> Jazzva: since you need sponsoring, and u-u-s is already subscribed, you may as well wait for it
[22:43] <norsetto> Jazzva: your sponsor should help you with the sru too
[22:43] <Jazzva> norsetto: Thanks...
[22:44] <Jazzva> Just wanted to check if everything is ok. I would like if this fix could be included :).
[22:44] <norsetto> jazzva: couldn't keep you away from ubuntu too long eh ;-)
[22:45] <Jazzva> norsetto: Naah :). I think I managed to do both Ubuntu and school work...
[22:46] <norsetto> jazzva: when you say "Re-apply changes from 0.2-0ubuntu2" is that because of an incorrect sync/merge?
[22:47] <norsetto> jazzva: ops, its 0.2-0ubuntu2, so, this cannot be
[22:47] <norsetto> jazzva: so, do you know why these changes were removed?
[22:49] <Jazzva> norsetto: Right ... Some of the changes were lost between 0ubuntu3 and 0ubuntu5 (I think). I don't know why they were removed, but it wasn't documented. It might be due to the bad build system. The build system deletes some of the needed files on the dist-clean, that needs to be fixed upstream.
[22:50] <norsetto> jazzva: ah, so there is no patch system being used ... good
[22:50] <Jazzva> Some of the build files were changed before, but those changes were lost somewhere between ubuntu3 and 5.
[22:51] <Jazzva> norsetto: No patch system for now. I'm planning to set up one, when we include 0.3. Most of the changes were made to the build system.
[22:51]  * norsetto curses against people not using a patch system
[22:51]  * Jazzva hides
[22:52] <norsetto> jazzva: ok, so, do you know why was that automake change made in the first place?
[22:54] <Jazzva> norsetto: Yes. It deleted gnome-doc-utils.make file in dist-clean, which is needed in the build process.
[22:55] <norsetto> jazzva: that would be the DISTCLEANFILES change, not the addition of the automake call?
[22:55] <Jazzva> norsetto: automake call was removed. It might be the source of this, too...
[22:56] <norsetto> jazzva: ah, you only change the in/am, why not changing directly the Makefile then
[22:56] <LaserJock> norsetto: do you have any idea wbout these lockups in rkward?
[22:56] <norsetto> jazzva: just automake on another tree with the DISTCLEANFILES change and diff it to the Makefile
[22:56] <norsetto> LaserJock: no idea
[22:57] <norsetto> LaserJock: but the change is relatively heavy
[22:58] <norsetto> LaserJock: its an upstream change, I have seen no refs in ubuntu nor debian bts
[22:58] <LaserJock> norsetto: I think the version should be maybe 0.4.9-2build1
[22:59] <norsetto> LaserJock: for an sru!?
[22:59] <LaserJock> or 0.4.9-2ubuntu0.1
[22:59] <LaserJock> I don't think a build1 is going to be a problem
[22:59] <norsetto> LaserJock: I'm ok with it, I'll change before uploading
[22:59] <Jazzva> norsetto: Hmm, Makefile is made in the build process, and then removed in the cleaning process...
[23:00] <norsetto> jazzva: ah
[23:00] <Jazzva> (just checked)
[23:00] <norsetto> jazzva: you got an upstream with a serious case of cleansing frenzy :-)
[23:01] <norsetto> jazzva: so, you do need to automake anyway
[23:01] <LaserJock> norsetto: it looks to me that according to https://wiki.ubuntu.com/SecurityUpdateProcedures#Prepare it should be 0.4.9-2ubuntu0.1
[23:01] <norsetto> jazzva: no wait, that could also be done during the configure step
[23:01] <norsetto> LaserJock: checking
[23:02] <LaserJock> although they don't specifically mention rebuilds, my guess is that we should treat them as any other upload
[23:02] <Jazzva> norsetto: yep. automake would produce Makefile.in, which was provided by the upstream.
[23:02] <norsetto> LaserJock: ok, will go for 0.4.9-2ubuntu0.1
[23:02] <Jazzva> norsetto: Anyway, I'm hoping this will be fixed for 0.3, so all of this dirty fixes can be forgotten :).
[23:03] <norsetto> jazzva: yes, I hope too :-)
[23:04] <norsetto> jazzva: anyway, I don't get why the automake change was made, you say there is no ftbfs now, correct?
[23:05] <Jazzva> norsetto: You mean the removal of automake call from configure?
[23:05] <norsetto> jazzva: from rules
[23:05] <Jazzva> right.
[23:07] <LaserJock> norsetto: ok ack'd and I also added a bug watch for the Debian bug so we remember to make sure we get this fixed in Intrepid
[23:08] <norsetto> LaserJock: err, we will sync and then build with R 2.7.0
[23:08] <Jazzva> norsetto: afaik, this would produce new Makefile.in, which then produces an unusable applet. It builds, but it fails to start. I think that was the problem.
[23:09] <RainCT> good night
[23:10] <norsetto> night rainct
[23:11] <LaserJock> norsetto: we *assume* we'll sync ;-)
[23:13] <norsetto> LaserJock: its an autosync
[23:14] <azeem> persia: are you running pidgin?
[23:14] <LaserJock> norsetto: I know, I just don't trust it until I see it :-)
[23:14] <persia> azeem: Yes, why?
[23:15] <norsetto> laserjock: ok ... thx for your swift help btw
[23:15] <azeem> persia: you changed the /topic last, and it has a weird UTF8 char at the beginning
[23:15] <azeem> persia: looks like a pidgin feature/bug to me, I saw it with other pidgin people in other chans
[23:17] <persia> azeem: It's a 0-byte space, not shown in pidgin.  Comes from oddities in copy/paste.  Depending on various factors, there can be a few oddities transmitted.
[23:18] <persia> If you don't mind, please clean the topic :)
[23:18] <Jazzva> norsetto: Right, automake call doesn't produce any wrong change. It did before, since it made .am from unpatched .in. Anyway, it's not needed, as the .am file is provided by the upstream.
[23:18] <azeem> easier said than done, it freaks out my irssi/screen/terminal combination :)
[23:18] <laga> azeem: interesting. works fine for me (ubuntu dapper)
[23:19] <azeem> persia: well, it's just a matter of time till the next pidgin user changes it again
[23:20] <persia> azeem: Maybe.  On the other hand, last fall I did >80% of the topic changes, and didn't hit it.  It depends on how the copy & paste is done.  I'll check in a less robust display environment next time I change it.
[23:20] <norsetto> jazzva: ok, can you please mention this in the changelog? Also, the version number should be changed for an sru and it should be hardy-proposed not hardy
[23:21] <sebner> good night folks :)
[23:22] <Jazzva> norsetto: Sure thing. SRU version is XubuntuY.1?
[23:22] <norsetto> jazzva: yes
[23:29] <Kopfgeldjaeger> n8
[23:29] <Jazzva> norsetto: Done. Thanks for your help :).
[23:30] <norsetto> jazzva: de nada
[23:30] <norsetto> jazzva: glad to see you back ;-)
[23:30] <Jazzva> norsetto: glad to be back :)
[23:30] <Jazzva> *good
[23:36]  * norsetto goes to bed