[02:08] <micahg> JontheEchidna: thanks for the packaging tips
[02:09] <JontheEchidna> micahg: thanks for the FTBFS fix ;)
[02:33] <zachtib> hey, q about the eclipse-cdt package in Karmic: it's version 3.1.2, which is a (very) older version than the version of eclipse in karmic, 3.5.1. The version of cdt that corresponds to that eclipse release is 6.0.1, so I'm worried that someone installing eclipse and eclipse-cdt on Karmic is going to wind up with a broken eclipse...
[02:36] <zachtib> I'm guessing it's way too late to bump the cdt version that much, so it seems to me the best thing would to be pull it (I think a few other packages are in a similar state) and let users install addons via eclipse's built in manager until newer packages can be built...
[02:36] <zachtib> (I came here b/c the eclipse-cdt package is maintained by MOTU)
[02:37] <micahg> zachtib: have you looked at that bug that was mentioned in the eclipse fix bug?
[02:37] <zachtib> i did a quick search on launchpad, but I don't think I've seen the one you're referring to
[02:38] <micahg> bug 163739
[02:38] <zachtib> ah,that's the one I saw
[02:38] <zachtib> though even 4.x is pretty old
[02:39] <micahg> zachtib: you might want to update the upgrade bug
[02:39] <micahg> have you tried eclipse-cdt and eclispe together?
[02:39] <zachtib> on it
[02:39] <micahg> is there indeed a problem, or is it just lacking features
[02:39] <zachtib> not yet, I just noticed it
[02:40] <zachtib> i'll know shortly... I mentioned it to my mother, who is an eclipse developer that works w/ cdt a lot, and she said it was probably asking for trouble
[02:40] <zachtib> lemme fire up my VM
[02:40] <micahg> ok, if there's a conflict, then please file a separate bug saying that there is a conflict
[02:41] <micahg> although, idk
[02:41] <micahg> maybe someone else can weigh in here
[02:42] <micahg> just requiring version 3.2 doesn't seem like a good solution as that's not in the repo
[02:43] <zachtib> ideally, I'd like to see cdt 6.0.1 in there, but it's probably a little late for that
[02:43] <zachtib> for Karmic at least
[02:43] <micahg> zachtib: not necessarily
[02:46] <ScottK> zachtib: If the current one won't work, as long as someone can package the new version and test it, it shouldn't be a problem.
[02:46] <zachtib> micahg: ScottK: just tried, eclipse 3.5.1 flat out doesn't see eclipse-cdt 3.1.2
[02:47] <ScottK> OK.  That's step on.
[02:47] <ScottK> Step two is someone packages the new version (Debian has the same one we do).
[02:47] <micahg> ok, so update bug 163739 to the version it should be
[02:47] <micahg> and find someone to package it like ScottK said :)
[02:48] <zachtib> can I edit that bug?
[02:48] <micahg> lool: lubuntu-meta still didn't build amd64
[02:48] <micahg> zachtib: if you're registered with launchpaf
[02:48] <micahg> *launchpad
[02:48] <zachtib> i am, I just don't see what to click
[02:49] <zachtib> ah
[02:49] <micahg> are yo ulogged in?
[02:49] <zachtib> yes
[02:49] <micahg> you should see a foot in the title
[02:49] <zachtib> got it
[02:49] <ScottK> Unless you are using one of the many browsers that doesn't work with
[02:51] <zachtib> nope, it works
[02:52] <micahg> dyfet: lubuntu-desktop still does not have amd64
[02:57] <ScottK> micahg: I'm fixing it.
[02:57] <micahg> ScottK: which thing?
[02:58] <ScottK> micahg: lubuntu
[02:58] <micahg> ok
[03:02] <zachtib> micahg: I sent an email to a guy that had some up-to-date eclipse packages in his PPA, so maybe he'll be able to provide some updated packages...
[03:03] <ScottK> micahg: The lubuntu fix is uploaded.
[03:03] <micahg> ok, thanks ScottK
[03:08] <ScottK> micahg: https://launchpad.net/ubuntu/+source/lubuntu-meta/0.7.1/+build/1281343
[03:11] <micahg> thanks ScottK
[03:26] <cyberix_> What happens when a user installs a package which depens on something that is implemented by multiple alternative packages?
[03:27] <ScottK> First one on the list gets installed if none are already installed, but if any of them are installed nothing extra gets installed.
[03:28] <cyberix_> I mean
[03:28] <cyberix_> we used to have totem-xine and totem-gstreamer
[03:28] <dhillon-v10> hi all, I just got done installing pbuilder (sudo apt-get install pbuilder) and I have a then I had to test a package if it runs on karmic or not so I did sudo pbuilder update --distribution karmic --override-config it started downloading lot of packages and I am running karmic, I didn't break anything on jaunty did I
[03:28] <cyberix_> both of which would provide totem
[03:28] <cyberix_> now, if I'd have none installed
[03:29] <cyberix_> and something would simply depend on "totem"
[03:29] <cyberix_> there would be no list
[03:29] <dhillon-v10> * I am running jaunty
[03:29] <cyberix_> to chechk which one comes first
[03:30] <ScottK> cyberix_: In the case of a virtual provides it's random.
[03:30] <cyberix_> ok
[03:30] <cyberix_> But the user is not bothered?
[03:30] <cyberix_> the system picks one
[03:30] <ScottK> that's why you should always depend on realpackage|virtualpackage so you get deterministic behavior
[03:30] <cyberix_> ok
[03:34] <ScottK> The user is not bothered
[03:34] <cyberix_> thank you
[03:35] <ScottK> No problem.
[03:35] <cyberix_> I never knew how far I'm from understanding how this stuff works, until I started reading how multiarch works :-)
[03:35]  * ScottK shudders
[03:36] <cyberix_> lol
[03:36] <cyberix_> I'm starting to get it.
[04:05] <ScottK> https://launchpad.net/ubuntu/+source/kazehakase/0.5.4-2.1ubuntu3.0xul191/+build/1152529 would be a nice target for FTBFS fixing by someone that knows a bit of gtk.
[04:16] <ScottK> sistpoty|work: You might want to take a shot at fixing https://launchpad.net/ubuntu/+source/bayonne/2.3.2-3build1/+build/1161099/+files/buildlog_ubuntu-karmic-i386.bayonne_2.3.2-3build1_FAILEDTOBUILD.txt.gz - in addition to FTBFS fix, it also clears up some NBS.
[06:52] <porthose> fabrice_sp, Thx for the upload.  Forwarding it to Debian :)
[06:55] <kklimonda> siretart: can you take a look at bug 446040 when you are online?
[07:08] <fabrice_sp> porthose, thanks for the debdiff ;-)
[07:42] <dholbach> good morning
[07:51] <mohanohi> hi pwnguin
[07:51] <pwnguin> h
[07:52] <mohanohi> compiling ctl..
[07:52] <pwnguin> why?
[07:52] <mohanohi> its giving error while doing make..
[07:52] <mohanohi> to install the missing library..
[07:53] <pwnguin> ah
[07:53] <pwnguin> thats what you meant by color transform
[07:53] <mohanohi> http://pastebin.ca/1603475
[07:54] <mohanohi> can you tell me why the error is occuring pls?
[07:55] <pwnguin> maybe
[07:55] <pwnguin> you did ./configure?
[07:56] <mohanohi> yeah..
[07:56] <pwnguin> well, it means that a standard function wasn't properly scoped
[07:57] <mohanohi> hmm??
[07:57] <pwnguin> the question is, is it because your compiler is too new, or too old?
[07:57] <mohanohi> ah..
[07:57] <mohanohi> what should i do now?
[07:59] <mohanohi> how to check if my compiler version?
[07:59] <pwnguin> gcc --version
[08:00] <mohanohi> gcc (Ubuntu 4.3.3-5ubuntu4) 4.3.3
[08:02] <pwnguin> you might ask the developer how he did it
[08:02] <mohanohi> pwnguin: oh...
[08:02] <pwnguin> http://ramenhdr.blogspot.com/2009/09/color-transformation-language.html
[08:03] <mohanohi> pwnguin: yeah.. i read it..
[08:03] <pwnguin> i wonder if CtlLex.cpp is actually c++
[08:03] <mohanohi> pwnguin: hmm.. no programming idea... :(
[08:04] <mohanohi> pwnguin: i am just an artist
[08:05] <pwnguin> well, ramenhdr is super new
[08:06] <pwnguin> and it's dependencies aren't yet packaged
[08:06] <pwnguin> which is a bad sign
[08:09] <pwnguin> mohanohi: im guessing strtol was depricated or moved and ctl hasn't changed to fix it
[08:10] <pwnguin> it looks like the developer uses osx
[08:11] <mohanohi> pwnguin:oh...
[08:12] <pwnguin> honestly, even the gentoo people have trouble building according to the forum
[08:13] <mohanohi> pwnguin:oh... ok.. then i will mail the developer.. sorry for wasting your time :)
[08:13] <pwnguin> not a problem
[08:13] <mohanohi> pwnguin: thanx :)
[08:14] <pwnguin> ive actually been collecting references to nodal editors like that
[08:14] <pwnguin> hadn't seen that one
[08:15] <pwnguin> but i think he's going a bit nuts on the dependencies without considering their long term viability
[08:16] <pwnguin> Academy of Motion Picture Arts and Sciences might not be a very responsive upstream
[08:25] <mohanohi> pwnguin: oh...
[08:25] <mohanohi> pwnguin: anyhow.. linux seriously needs a Opensource compositing program..
[08:25] <pwnguin> have you seen blender?
[08:25] <mohanohi> pwnguin: Blender is our productions major package..
[08:26] <mohanohi> pwnguin: but it isn't really sufficient as an compositing programme..
[08:26] <mohanohi> pwnguin: lacks rotoscope, tracker, animatable nodes, good masking..
[09:07] <jetienne> q. what is the name of the tool which convert a ./configure installation in a .deb ?
[09:23] <randomaction> checkinstall
[09:25] <jetienne> randomaction: thanks
[09:25] <jetienne> q. where can i get information on how to set my own repository
[09:26] <_ruben> google, as there's tons of methods, each with their pros and cons
[09:30] <jetienne> _ruben: on widely accepted good practice ?
[09:35] <_ruben> jetienne: depends on your needs/wishes/etc .. i use debmirror to mirror the official repos and mini-dinstall for our inhouse packages
[09:36] <jetienne> _ruben: this is a for small repo with only our packages, like 10 packages top
[09:36] <jetienne> easy to install would be good
[09:36] <_ruben> mini-dinstall will probably suffice for that
[09:37] <jetienne> _ruben: cool thanks
[09:41] <sistpoty|work> ScottK: will take a look later... (hm, didn't close kvirc when I left work yesterday *g*)
[11:26] <Daviey> Could a motu please confirm Bug #446038 ?
[11:28] <Laney> superm1 is a MOTU
[11:28] <Laney> superm1: why didn't you confirm it?
[11:31] <ScottK> sistpoty|work: Thanks.
[11:31] <Daviey> Laney: superm1 reported it, i would suggest it's bad form for a reporter to confirm their own bug :)
[11:31] <Laney> Daviey: not for process bugs like this
[11:32] <Daviey> ok
[11:32] <Laney> you're just asking an archive admin to perform an action you can't do yourself
[11:32] <Laney> I did it anyway
[11:32] <Daviey> thanks Laney, i'll pester an AA now.
[11:32] <Laney> one just spoke in this very channel ;)
[11:35] <ScottK> Not one that can do removals, however.  That takes shell access.
[11:35] <Laney> oh :(
[11:35] <Laney> Is that Canonical staff only?
[11:35] <directhex> there are different degrees of AAness?
[11:35] <directhex> i thought they all sat atop mount olympus, with a glowy blue aura :(
[11:36] <ScottK> Laney: Yes.
[11:36] <ScottK> For non-Canonical AA, we can only do what the LP U/I allows.
[11:37] <Laney> is that basically NEWing?
[12:32] <AnAnt> Hello, could someone review http://revu.ubuntuwire.com/details.py?package=sabily-xsplash-artwork ?
[12:35] <AnAnt> ^ it closes LP 440153, which is FFe approved
[14:42] <mok0> Man it looks dumb when that Kpackagekit window resizes for every package it installs...
[14:47] <bddebian> Heya gang
[14:47] <sistpoty|work> hi bddebian
[14:47] <bddebian> Heya sistpoty|work
[14:49] <lfaraone> If a package was pulled in from debian with a python-multithreading dep, does it make sense to remove that dep in Ubuntu? Is it worth fixing at this time?
[14:54] <AnAnt> bddebian: Hello
[14:54] <bddebian> Hi AnAnt
[14:56] <AnAnt> could someone review http://revu.ubuntuwire.com/details.py?package=sabily-xsplash-artwork ?
[14:56] <AnAnt> ^ it closes LP 440153, which is FFe approved
[15:15] <sistpoty|work> ScottK: patch at bug #412933, it's really ugly though, and I haven't tested yet if it works (well, I'm at work...)
[15:40] <RoAkSoAx> heya guys should -doc pcakages Depend on ${misc:Depends} if lintian says so?
[15:41] <james_w> there's no harm in it
[15:41] <james_w> and there's often no harm in not doing it either
[15:43] <RoAkSoAx> james_w, ok thanks :)
[15:43] <james_w> it's only needed if debhelper automatically adds a dependency
[15:43] <james_w> if it won't do that for your package then you don't need it, but it's better to have it
[15:43] <james_w> just not worth adding to a package that we get from Debian unless it is known to cause a bug
[15:46] <RoAkSoAx> ok awesome! thanks :)
[16:05] <ari-tczew> james_w: could you review this bug #431080 ?
[17:43] <irixpgmr> I am learning about buffer overflows.  I am working in a virtual environment.  How do it turn of the Ubuntu 9.04 protections?
[17:49] <av`> ScottK, about Bug #431979, do you think is sane enough to package it for karmic? or should we ask to have it synced from debian at some point?
[18:04] <soc> hi
[18:04] <soc> i'm just changing something in the glade files of synaptic, but somehow the change never appears after i compiled the app, what am i doing wrong?
[18:11] <joaopinto> you are not installing the files into the proper place ?
[18:11] <soc> hoe would i do it?
[18:11] <soc> there is a makefile in this dir and it gets executed afaics
[18:12] <soc> s/hoe/how
[18:41] <fabrice_sp> funkyHat, ping
[19:49] <funkyHat> fabrice_sp: pong?
[19:50] <funkyHat> fabrice_sp: just got in, taking at look at that patch now.
[19:52] <funkyHat> I already made a patch to submit to upstream, so I'm just reading how to put that into dpatch
[19:53] <funkyHat> Is there some more help about dpatch than https://wiki.ubuntu.com/PackagingGuide/Complete#dpatch ?
[19:57] <wrapster> i was building jkaudio pkg and this is what i got as an error... http://pastie.org/647309
[19:58] <wrapster> i needed help on resolving it.. and its a little urgent.. can anyone look into it pls
[20:04] <ScottK> av`: For amule we pretty much always want the latest crack, so I'd be in favor at long as there's a halfway sane package.
[20:04] <av`> ScottK, gonna update the package and upload it
[20:05] <av`> myself :)
[20:05] <joaopinto> wrapster, what don't you understand about that error ?
[20:06] <wrapster> joaopinto: well what i wanted to post was something different.. sorry about that.. the issue is actually about a complain on missing header sys/audio.h and sys/mixer.h
[20:08] <joaopinto> pastebin it please, and I hope you are not again asking us about opensolaris specific stuff :P
[20:08] <av`> ScottK, please comment into the bug and say it's ok for the update
[20:08] <av`> ScottK, plus approve the task
[20:09] <wrapster> joaopinto: no not this time
[20:09] <wrapster> :)
[20:10] <fabrice_sp> funkyHat, man dpatch?
[20:10]  * funkyHat feels silly now
[20:10] <fabrice_sp> lol
[20:11] <ScottK> av`: Done
[20:11] <av`> ScottK, thanks
[20:11] <ScottK> No problem.  Thank you for working on it.
[20:13] <funkyHat> fabrice_sp: still not really getting it, I don't want to just try it as I'm worried I'd mess up my package and have to start again
[20:13] <av`> ScottK, np :)
[20:13] <funkyHat> I suppose I'd be able to just use my debdiff though
[20:13] <fabrice_sp> funkyHat, an easy is to use dpatch-edit-patch
[20:14] <fabrice_sp> and apply then your patch to it
[20:14] <funkyHat> Ah got it
[20:15] <funkyHat> So I need to reset it to the unmodified package anyway. should I do dpatch and then dch -i?
[20:15] <funkyHat> Or just unpatch the file I changed and then do dpatch-edit-patch?
[20:17] <ScottK> I'm a fan of dpatch-edit-patch
[20:17] <funkyHat> Do you know the answer to my question then? :)
[20:17] <fabrice_sp> unpatch the file and then run dpatch-edit-patch
[20:18] <fabrice_sp> do somebody know what would be the watch file to download the source from there: http://plugins.guifications.org/trac/downloads ?
[20:22] <funkyHat> I just did dpatch-edit-patch and patched then exited, but my patch isn't in 00list...
[20:22] <ScottK> funkyHat: You have to add it to 00list by hand, but the patch should exist now.
[20:23] <funkyHat> Oh ok. So I will add a number to the beginning of the file, as I didn't realise I should
[20:24] <micahg> ScottK: about the kvpnc thing, shouldI file a bug about the packaging, upstream?
[20:25] <ScottK> micahg: Yes.  About a missing version requirement for pkg-kde-tools
[20:25] <micahg> ok
[20:26] <ScottK> micahg: Where upstream means Debian.
[20:26] <micahg> yes
[20:36] <ylatuya> Hi! I'm trying to package Chronojump for Ubuntu and I'm looking for an Advocate (https://bugs.launchpad.net/ubuntu/+bug/445207). The package is already in revu. Is it the right place to ask help?
[20:36] <ScottK> ylatuya: We are very close to a release, so not taking new packages right now.  We'll be back in the new package business next month.
[20:37] <ylatuya> Ok. I'll come back in a month :)
[20:42] <funkyHat> fabrice_sp: just uploaded the new patch :)
[20:43] <fabrice_sp> cool :-)
[20:43] <fabrice_sp> did you take care of the merge?
[20:43] <ScottK> ylatuya: You're welcome to hang around and help us fix bugs in the meantime.
[20:43] <fabrice_sp> Or I should perform it by myself?
[20:43] <funkyHat> fabrice_sp: the merge?
[20:44] <fabrice_sp> yes: Debian has a newer version that should be merged as it fixes several bugs
[20:44] <funkyHat> Oh, sorry, you mentioned that and I forgot about it
[20:45] <fabrice_sp> np :-)
[20:45] <fabrice_sp> will take it?
[20:46] <funkyHat> I've not done a merge before, but I could give it ago
[20:46] <funkyHat> *a go
[20:47] <fabrice_sp> from what I remember, this one is easy
[20:47] <ylatuya> ScottK:I'm the maintainer of LongoMatch and filled to asking to update the version that currently is in karmic because I'm not maintaining the 0.14.x anymore (https://bugs.launchpad.net/ubuntu/+source/longomatch/+bug/420107). The current upstream version is at 0.15.3
[20:47]  * ScottK looks
[20:49] <fabrice_sp> funkyHat, have a look and if you feel like it's too much for you, just tell me, and I will take care of it
[20:49] <sebner> ScottK: ylatuya : Hoi, I planned to do the packaging on the weekend (Debian ->Ubuntu) but if necessary I could work on getting it directly into Ubuntu first
[20:49] <ylatuya> sebner: Hi!
[20:50] <sebner> ylatuya: hi ;)
[20:50] <ari-tczew> hello all
[20:51] <ylatuya> sebner: I let everything in your hands :) Thanks again for your help
[20:52] <ScottK> ylatuya and sebner: It needs two motu-release acks for FFe.  I just gave one.
[20:52] <funkyHat> grab-merge just told me "You almost certainly don't want to continue without investigating." < what should I investigate?
[20:53] <sebner> ScottK: I know, just wanted to ask what's the consens right now
[20:53] <ScottK> Since the current package seems broken in Karmic, not broken > broken.
[20:54] <ari-tczew> who can accept bug #431080 ? I need info for follow work
[20:54] <fabrice_sp> funkyHat, why does it say that to you?
[20:55] <funkyHat> fabrice_sp: it says "it looks like this package is maintained in revision control:" then lists some git urls
[20:55] <fabrice_sp> funkyHat, you can perform the merge
[20:56] <fabrice_sp> without investigation, I mean
[20:56] <ylatuya> ScottK:sebner: The package itself is not broken. Are all the Mono packages broken due to #420385
[20:56] <ScottK> Ah
[20:56] <ScottK> ylatuya: Are you subscribed to bugs in Launchpad for the package?
[20:56] <sebner> ScottK: to be honest the current package wouldn't have entered Debian/Ubuntu since there was also a source file license issue.
[20:56] <funkyHat> Also the package number that grab-merge has downloaded is confusing, there's a gpaint_0.3.3-3ubuntu1.src.tar.gz but that's the same debian version as the debian version it downloaded??
[20:56] <ScottK> sebner: Is that fixed in the new version?
[20:57] <funkyHat> Is that the point?
[20:57] <sebner> ScottK: yep
[20:57] <ylatuya> ylatuya: yes
[20:57] <ScottK> sebner: More reason to update
[20:57] <funkyHat> fabrice_sp: ok :)
[20:57] <ScottK> So licensing fixes and upstream support are good reasons to update
[20:57] <ylatuya> ylatuya: 0.14.x is not maintained anymore
[20:57] <sebner> ScottK: yeah, wasn't sure because we are that late in the archive cycle.  I'll get active tomorrow :)
[20:58] <fabrice_sp> funkyHat, gpaint_0.3.3-3ubuntu1.src.tar.gz has been created by MoM. It's better to begin with a fresh debian directory, and incorporate the changes
[20:59] <fabrice_sp> s/debian/debian package/
[20:59] <fabrice_sp> this way, you control better what changes you are doing
[20:59] <funkyHat> Oh, so that tarball is just 0.3.3-3 with an ubuntu version bump tacked on?
[20:59] <funkyHat> no actual changes
[21:00] <funkyHat> Or an automated merge attempt?
[21:00] <fabrice_sp> an automate merge attempt
[21:00] <fabrice_sp> better to unpack 0.3.3-3, and manually do the merge
[21:01] <funkyHat> Ok, so I should ignore that and work straight from the debian package
[21:01] <funkyHat> Right
[21:01] <jdong>  
[21:02] <fabrice_sp> so nobody can help me with the trac based download url for a watch file?
[21:03] <ari-tczew> fabrice_sp: what's the program?
[21:03] <fabrice_sp> purple plugins pack (http://plugins.guifications.org/trac/downloads)
[21:03] <fabrice_sp> trying to get the watch file fixed
[21:04] <ari-tczew> what's the program in ubuntu?
[21:04] <fabrice_sp> purple-plugin-pack
[21:04] <fabrice_sp> :-D
[21:05] <ari-tczew> You have searched for packages that names contain purple-plugin-pack in all suites, all sections, and all architectures.
[21:05] <ari-tczew> Sorry, your search gave no results
[21:05] <fabrice_sp> https://bugs.launchpad.net/ubuntu/+source/purple-plugin-pack
[21:06] <ari-tczew> give me a moment for that
[21:06] <fabrice_sp> I'm trying to fix the watch file of this package
[21:06] <fabrice_sp> ok
[21:09] <fabrice_sp> have to go now. Will have a look tomorrow morning. bye!
[21:10] <ari-tczew> cya
[21:11] <funkyHat> wooo vimdiff is shiny
[21:16] <ari-tczew> http://plugins.guifications.org/trac/downloads/purple-plugin_pack-2.6.0.tar.gz
[21:16] <ari-tczew> this link shoud be works, but doesn't accepted by uscan
[21:17] <ari-tczew> if someone is boring, feel free to play with it
[21:19] <funkyHat> Is there a command to unpack an original tarball and apply a debian source diff to it?
[21:20] <ari-tczew> are you mean about .diff.gz?
[21:20] <funkyHat> Yeah
[21:20] <debfx> funkyHat: if you have the .dsc file: dpkg-source -x
[21:21] <funkyHat> ah :) thanks
[21:22] <debfx> if you want to download+unpack a source package you can use dget
[21:22] <funkyHat> debfx: I already had  the source because  I'd used grab-merge
[21:24] <ari-tczew> who is reviewing bugs refers to fix security bugs?
[21:25] <ScottK> ari-tczew: For Karmic or earlier releases?
[21:31] <ari-tczew> ScottK: both
[21:31] <ari-tczew> karmic, jaunty, intrepid, hardy
[21:32] <kees> ari-tczew: when you've got patches and you've tested them, please attach them to the bug and set the bug to "In Progress".  from there, the security team will sponsor the uploads.
[21:32] <kees> ari-tczew: (for the stable releases)
[21:32] <ScottK> ari-tczew: And regular sponsorship process for Karmic.
[21:36] <ari-tczew> ouh, so I need to hack drupal ;-D (for testing)
[21:40] <ari-tczew> kees: if I'll done packages for test, could you test these?
[21:41] <kees> ari-tczew: I'm sure I could figure it out, but it would be much easier if someone familiar with it (and the changes) did the testing.
[21:43] <funkyHat> Ok, I'm trying to merge gpaint, and add a patch I've created to fix #444750
[21:43] <funkyHat> bug 444750
[21:44] <funkyHat> And I'm not sure what to do about debian/changelog
[21:45] <funkyHat> I'm basically just keeping one change from Ubuntu (adding ${misc:Depends) to depends) and my patch, should I just keep debian's changelog and add what I'm changing?
[21:45] <ari-tczew> I'm not a hax0r so I can don't know how test it. :P
[21:47] <ScottK> ari-tczew: You might ask for testing help in #ubuntu-server.
[21:51] <ari-tczew> OK
[21:52] <funkyHat> Can anyone tell me if I'm doing the right thing with this merge? :(
[21:54] <ari-tczew> funkyHat: if you have done, upload to ppa :P
[21:55] <funkyHat> ari-tczew: no I haven't yet, I'm not sure what to do about debian/changelog ^
[21:55] <funkyHat> I'm guessing I should just keep the new one from debian and put the changes I made on top
[21:56] <Darxus> funkyHat: You should use dch -i to update the changelog.
[21:56] <Darxus> That'll add something like -1ubuntu1 to the version.
[21:56] <Darxus> Which is what you should do if you're merging from debian.
[21:57] <funkyHat> Darxus: well I'm not sure if I've done a proper merge, I've just re-applied the relevant Ubuntu changes to the new debian package
[21:57] <Darxus> funkyHat: Open a bug if there isn't one (requesting the merge) and attach a debdiff.
[21:58] <Darxus> Did you check to see if there are any ubuntu specific changes in, say, debian/control?  For example, in hugin, a depends is added.
[21:58] <Darxus> funkyHat: Do you know about MoM?  What's the package?
[21:59] <funkyHat> Darxus: Darxus gpaint, see about 20 lines above
[21:59] <Darxus> Do you know about MoM?
[22:00] <ari-tczew> funkyHat: I suggest to you - read wiki.ubuntu.com
[22:00] <Darxus> Hah.
[22:00] <Darxus> funkyHat: Are you matt Wheeler?
[22:01] <funkyHat> Darxus: I grabbed the package from there using grab-merge but I was advised by fabrice_sp to unpack 0.3.3-3 and do the merge manually
[22:01] <funkyHat> Darxus: yes
[22:03] <Darxus> He recommended the same to me.
[22:03] <Darxus> But you should check MoM to make sure there's nothing else, like changes in debian/control, that need to be updated as well.
[22:05] <funkyHat> Darxus: I did that, see above
[22:05] <Darxus> Then what are you unsure about?
[22:05] <funkyHat> Which debian/changelog I should keep, or should I merge them?
[22:06] <funkyHat> My guess is I should just have debian's and make a note again at the top of the changes I've re-added for Ubuntu, but I wasn't sure
[22:06] <Darxus> funkyHat: Oh, just use the debian one.
[22:06] <Darxus> With your addition.
[22:06] <funkyHat> Ok :)
[22:07] <Darxus> The docs for mom give a specific format for a merge changelog entry.
[22:07] <Darxus> -Depends: ${shlibs:Depends}
[22:07] <Darxus> +Depends: ${shlibs:Depends}, ${misc:Depends}
[22:07] <Darxus> You got that?
[22:08] <funkyHat> yeah
[22:08] <Darxus> Cool.
[22:08] <funkyHat> Adding it to the changelog too
[22:09] <Darxus> So you merged from debian and added key bindings?
[22:09] <funkyHat> Yeah
[22:09] <Darxus> Cool.
[22:10] <funkyHat> Should I file a separate bug for the merge?
[22:11] <Darxus> I don't know.
[22:11] <funkyHat> Before I build the package, so I can add the magic to debian/changelog for the bug fix :)
[22:11] <Darxus> I think you should be fine doing both in one.
[22:12] <funkyHat> Ok
[22:41] <funkyHat> I'm using reportbug to report this bug upstream, does it matter that it's including a whole bunch of stuff about how I'm running ubuntu in the report?
[23:01] <Darxus> funkyHat: No.
[23:04] <Darxus> Wow, I'm surprised more packages FTBFS on i386 than amd64.
[23:04] <ScottK> Darxus: arch all packages are only built on i386, so it has a lot more packages.
[23:04] <Darxus> Ah.  Seems like they should be built on all architectures.
[23:05] <Darxus> Are packages build tested continuously throughout the release cycle, or just at the end?
[23:07] <ScottK> It varies.
[23:07] <ScottK> We're a bit into a new process this cycle so we only managed it once.
[23:07] <ScottK> It is supposed to be done two or three times.
[23:08] <Darxus> It seems like it should be done continuously.
[23:08] <ScottK> Given unlimited resourced, certainly.
[23:08] <Darxus> Heh, okay.
[23:08] <ScottK> resourced/resources
[23:09] <Darxus> Unlimited resources would be nice.
[23:10] <Darxus> I wonder if the SABDFL would be interested in throwing more machines at build testing.
[23:11] <joaopinto> It would be cheaper to have a distributed build test farm
[23:11] <ScottK> I think we should have a better plan for it the next cycle.
[23:12] <av`> ScottK, what happened to the mentoring offers into LP?
[23:13] <ScottK> av`: Not sure, but I vaguely recall the removed the feature because it was almost unused.
[23:13] <av`> ScottK, yes, looks like it's now removed...but the wiki pages into help.l.n should be removed IMO
[23:13] <av`> there are documents about it that refers to nothing
[23:13] <ScottK> av`: You should take that up on #launchpad
[23:14] <av`> yep, true
[23:14] <av`> ScottK, amule is ready, gonna test it a bit again tomorrow, and then it should be ready for the upload
[23:15] <av`> tomorrow morning should be in I guess :)
[23:17] <Amaranth> Does anyone know if there is a MC meeting in 9 hours? According to the wiki there should be but the next meeting time says a day that doesn't exist :)
[23:18] <av`> Amaranth, I see 24th of october
[23:19] <Amaranth> av`: And the last meeting was the 24th of September, thus the confusion
[23:19] <Amaranth> av`: It doesn't match the schedule so I'm assuming it's a typo
[23:19] <av`> Amaranth, tomorrow (friday 10) should be the second friday of the month
[23:20] <Darxus> LP's build system doesn't prioritize by wheither or not you're a motu, or canonical employee?
[23:20] <av`> Amaranth, but I dunno if the plans will be respected : /
[23:20] <Amaranth> Right, 9 hours from now matches the schedule
[23:20] <av`> yep
[23:21] <av`> Darxus, https://help.launchpad.net/Packaging/BuildScores
[23:22] <av`> Amaranth, but I really don't know if there will be one tomorrow (7 utc)
[23:22] <av`> Amaranth, you should ping any motu-council member around
[23:23] <ScottK> Actually is was sistpoty that was coordinating the meeting.  He doesn't seem to be around now.
[23:24] <av`> Amaranth, just be there at 7 utc to be sure :)
[23:24] <Darxus> vadi2: I read that, which is why I thought user status wasn't included in the priority.  Which seems weird.
[23:25] <ScottK> Darxus: They aren't
[23:25] <Darxus> Weird.
[23:25] <Darxus> They should be, to encourage me to become an motu :P
[23:26]  * funkyHat is already encouraged to become a motu, don't need no silly build status for that
[23:26] <av`> Darxus, what's the difference between having a build done today or tomorrow?
[23:26] <funkyHat> :P
[23:26] <av`> Darxus, simply nothing
[23:26] <av`> it's not the day that makes the difference
[23:26] <av`> if the delay is 1-2-3 days it's fine
[23:27] <vadi2> Darxus: huh?