[00:08] <doctormo> Is there anyone interesting is having a look at packaging ktoon? http://www.ktoon.net/portal/node/63 The devs are asking for help and art users are asking why ktoon doesn't work for ubuntu.
[00:08] <vorian> hrm
[00:09] <vorian> sure doctormo
[00:10] <vorian> doctormo: I take it it's having trouble on lucid?
[00:11] <vorian> sistpoty was the last to upload it, to debian unstable
[00:11] <doctormo> vorian: Seems to be something of a mystery, some users get it to work if the grab a specific version and compile it, others can't be arsed.
[00:11] <vorian> so are they not using the package in our arhives?
[00:12] <vorian> archives too :P
[00:12] <doctormo> vorian: Looks like two parts, ktoon and kom, 0.9a
[00:12] <vorian> compiling requires every little tasty bit to work right
[00:12] <vorian> i see
[00:13] <vorian> hrm, is the ubuntu/debian version causing trouble, or just the compiled versions?
[00:24] <kklimonda> well, developers are recommending us to provide a weekly builds as the project is in constant development..
[00:26] <vorian> '[['
[00:39] <doctormo> kklimonda, vorian: Isn't that something new in launchpad for the maverik cycle? weekly building?
[00:41] <kklimonda> doctormo: so I've heard but I haven't seen much info about it
[00:41] <doctormo> vorian: The problematic version I think is the repo one in Ubuntu.
[00:42] <doctormo> but then again, I wonder if it should be in the repository at all, considering it's very experimental nature.
[00:42] <kklimonda> *nods*
[00:43] <kklimonda> if developers believe their users should use weekly builds then we should remove it from archive and provide a ppa with builds for lucid and maverick
[00:43] <kklimonda> (well, we can't remove it from lucid anymore but we can probably still remove it from maverick)
[00:44] <doctormo> kklimonda: I wonder how we can start a dialog with Ktoon devs, debian and motu to get it sorted?
[00:54] <kklimonda> doctormo: normally I'd say to just contect the debian dev and ask if he needs help maintaining it (as the 0.9 has been released 3.. months? weeks? ago) but as ktoon devs have voiced their opinion that we should provide weekly builds instead of stable releases I'm not sure. It's hard to expect debian maintainer to provide a weekly releases or create a service to release them automatically.. and
[00:54] <kklimonda> Launchpad can't create debian packages :(
[00:55] <doctormo> kklimonda: Could just make a cron job though, with a simple email if it goes wrong. then he can get to fixing the package when he likes.
[00:57] <kklimonda> there is also a question of how alive the ktoon project itself really is
[00:58]  * kklimonda has just tried to browse ktoon's bugzilla
[01:00] <kklimonda> neither do I see a link to the repository..
[01:06] <kklimonda> doctormo: we should contact Labtoon and help them make ktoon a nice, opensource friendly project. Then, if they are interested in make it more friendly for us to work with, we can start worying about getting weekly builds and collaborating with debian maintainer. Of course we should find some MOTU interested in pushing it forward so we don't end up with a situation where they provide a working
[01:06] <kklimonda> bugtracker, a svn repository and we ignore them..
[01:07] <kklimonda> I can probably help with maintaining it in Ubuntu and working with Debian maintainer from a purely technical side - I'm not an artist myself but images on their homepage made me interested ;)
[01:08] <squarebracket> where can i disable -nolisten tcp for X?
[01:09] <doctormo> kklimonda: I'm more of an artist and non-packaging programmer, so I can only prod people on this. there was actually an interesting discussion we had on ubuntu-artists about ktoon vs synfig.
[01:10] <doctormo> kklimonda: My face on planet ubuntu was made in inkscape and synfig for instance.
[01:12] <kklimonda> the animated one? :)
[01:14] <crimsun_> would a member of ~ubuntu-sponsors please unsub the team from lp#609758?
[01:33] <ajmitch> crimsun_: ok
[01:39] <j3su> hi
[01:53] <doctormo> kklimonda: Yes the animated one.
[01:53] <doctormo> kklimonda: Although I'm willing to ignore a project that uses svn if you are ;-) I'm not a fan.
[03:31] <crimsun_> ajmitch: thanks!
[04:24] <easter_egg> Hi, someone can help me with this question:
[04:24] <easter_egg> https://answers.edge.launchpad.net/ubuntu/+source/blobwars/+question/118967
[04:24] <easter_egg> ?
[04:30] <easter_egg> And.. how can I proceed to report an abandoned package?
[04:32] <ajmitch> most packages are maintained in debian rather than ubuntu, which is most likely the case here
[04:34] <ajmitch> you can get an updated package into ubuntu, but it appears that there's not even an upstream release of blobwars, which makes it a little harder
[04:35] <ajmitch> & looking at the upstream git repository, the author is also the debian maintainer
[04:36] <vorian> thats not good
[04:37] <ajmitch> at least it's still being worked on upstream, but it's probably not ready for a release
[04:46] <vorian> ah, missed that part
[07:07] <dholbach> good morning
[07:53] <Rhonda> easter_egg: Please keep in mind that the version has no sound because the sounds used in there didn't had compatible licensing so they had to get removed.
[07:53] <Rhonda> easter_egg: And there is no concept of "maintainership" in Ubuntu as I understand it. :)
[07:54]  * Rhonda will add an answer instead of continuing here. ;)
[07:55] <easter_egg> Rhonda, all the extra packages that are in debian will be maintained in same conditions in Ubuntu?
[07:56] <Rhonda> Preferably.
[07:57] <Rhonda> There is no ubuntu diff for blobwars, so it's encouraged to do the move within Debian.
[07:57] <Rhonda> As Games Team admin I wasn't though aware about a new upstream release, and the history with licensing of the sounds has shown to be careful with such updates.
[07:58] <micahg> Rhonda: are the sounds non-distributable or just violate DFSG?
[07:58] <Rhonda> micahg: From what I perceived non-distributable because no licensing information at all.
[07:58] <micahg> Rhonda: ah, that's bad...
[07:58] <Rhonda> They were claimed to be "taken from the net" without any information from where and how.
[08:19] <easter_egg> Rhonda, I could send an e-mail to game creators
[08:19] <Rhonda> Why game creators?
[08:20] <Rhonda> Please notice that they did react extremely unhelpful when being addressed last time about these issues.
[08:20] <Rhonda> So I'm not sure what good that would be to ask them.
[08:22] <easter_egg> Rhonda, what them reply?
[08:26] <Rhonda> ajmitch: Hmm, it might though be that the sound files are indeed distributable, only non-commercial and non-modifyable.
[08:27] <Rhonda> hmm, or not
[08:28] <Rhonda> ajmitch: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515541#27
[08:30] <Rhonda> easter_egg: I highly doubt that upstream has replaced the music given the discussion we had with them. So an updated package won't have sound neither, I fear.
[08:33] <easter_egg> Rhonda, I'll put the right package in my PPA for the friends that wants to play
[08:33] <easter_egg> Rhonda, or the sound files has a problem with the launchpad rules too?
[08:37] <Rhonda> They have a problem with everything.
[08:37] <Rhonda> Not knowing wether you are allowed to distribute them is a problem.
[08:37] <Rhonda> So you should rather remove the music sound directory before doing anything with it.
[08:38] <Rhonda> The 1.17 version seems to only have something like a MedalServer code addition, and translation updates/additions.
[08:39] <Rhonda> I'm unsure about what the Medal thing adds to the game, so I'm uncertain what an update really would gain.
[08:41] <easter_egg> Rhonda, ok, thanks for all the informations
[08:41] <ajmitch> Rhonda: ok, I didn't look too closely at it :)
[08:41] <easter_egg> I will close the related bug
[08:46] <Rhonda> I think there were discussions on the debian-games list going on about it in the past. That shouldn't though hinder an update …
[08:49] <Rhonda> easter_egg: Just so that you are aware: I filed a "new upstream version" bugreport in Debian so that it's not lost. Not sure though wether this would be able to get in for maverick.
[08:49] <Rhonda> People are busy these days.
[08:53] <easter_egg> Rhonda, Really thanks. Because thats is not a high priority question is good to know that it's not lost yet.
[08:54] <easter_egg> I will translate some things for maverick now, thanks =]
[08:55] <Rhonda> easter_egg: http://bugs.debian.org/590430 for your convenience.
[08:57] <easter_egg> Rhonda, grateful for the concern
[09:10] <LucidFox> Ooh, got a woman interested in packaging for Ubuntu - not now, though, but when her work rush recedes and she can take a breather
[09:11] <LucidFox> those interviews do inspire!
[09:11] <LucidFox> er
[09:11] <LucidFox> wrong channel
[09:18] <easter_egg> ahahahaha
[09:36] <easter_egg> Rhonda, I received a reply of Gus. Mantainer of blobwars, I commented with the e-mail contents in https://bugs.edge.launchpad.net/ubuntu/+source/blobwars/+bug/561182 if you want to know
[09:36] <easter_egg> I will change the description of bug
[09:36] <easter_egg> with him informations
[09:42] <Rhonda> I was told that Guus is also involved in upstream development, he commits to the sourceforge blobwars git repository.
[09:43] <Rhonda> But then, 1.17 isn't really what would give you sound, it's still the old (unlicensed) stuff in there.
[09:46] <Rhonda> easter_egg: http://blobwars.git.sourceforge.net/git/gitweb.cgi?p=blobwars/blobwars;a=summary
[09:48] <easter_egg> Rhonda, well... at least we have a bug report with good details
[09:48] <Rhonda> And partly misleading ones. :)
[09:50] <bilalakhtar> Rhonda: hey there! did you license a packaging as WTFPL license or something ?
[09:51] <bilalakhtar> Rhonda: see conflicts in this file during a merge http://ubuntuone.com/p/Ad7/
[09:53] <bilalakhtar> Rhonda: is such a license permitted ?
[09:57] <Rhonda> Why shouldn't it be permitted?
[09:59] <Rhonda> Why is the versioned depends on libqt4-opengl-dev needed?
[09:59] <Rhonda> … and on libphonon-dev?
[10:00] <easter_egg> Rhonda, I been changed the description. If you want to review: https://bugs.edge.launchpad.net/ubuntu/+source/blobwars/+bug/561182
[10:00] <Rhonda> I would think that the diff can get dropped from my last upload and simply get synced?
[10:07] <Rhonda> oh gosh, bug #358391
[10:08] <Rhonda> bilalakhtar?
[10:09] <jpds> That bloke plays too many games.
[10:10] <Rhonda> And it's not something that all those games has to tweak, unless there is a clear instruction set like "set wm hint", mind you.
[10:11] <Rhonda> easter_egg: I wouldn't know how that one is "In Progress" when Guus clearly stated "Replacement music has
[10:11] <Rhonda> been found and a version of blobwars that contains it might be released in a
[10:11] <Rhonda> few months, sound is next."
[10:12] <Rhonda> … "in a few months" isn't that much in progress to me. Though, it might still be correct, I was wrong about launchpad status before once. :)
[10:14] <easter_egg> Rhonda, you think that is better change to only "Confirmed"?
[10:14] <lifeless> in progress should be used when someoine *is working on it*
[10:16] <easter_egg> I hope so
[10:17] <Rhonda> Yes, but someone within Ubuntu, not someone external. :)
[10:17] <lifeless> right
[10:17] <Rhonda> This depends on a new upstream release.
[10:18] <easter_egg> well... I will change for only "Confirmed" so.
[10:19] <easter_egg> done!
[11:45] <bilalakhtar> jono: Aloha!
[11:47] <bilalakhtar> Hi there! if a package has Standards-Version upgrade as an Ubuntu change, when merging, should I take the ubuntu s-v or the debian one ?
[11:50] <jono> hey bilalakhtar
[12:09]  * Rhonda nibbles on bilalakhtar …
[12:10] <Rhonda> bilalakhtar: A diff just for the standards-version doesn't make much sense, if it's only in debian/control anyway.
[12:11] <Rhonda> bilalakhtar: You did ask me before about qcake but didn't answer my question to you about it?
[12:14] <bilalakhtar> Rhonda: I went somewhere
[12:15] <bilalakhtar> Rhonda: I have already requested a sync. What did you actually tell me? Should I have requested sync orr ... ? bug #610024 please ack
[12:16]  * bilalakhtar doesn't have a log of what Rhonda told him :(
[12:16] <Rhonda> bilalakhtar: Yes, sync would be proper, I don't think that a diff is warranted here anymore. And I was curious why you think that the WTFPL might not be permitted.
[12:17] <bilalakhtar> Rhonda: because it has the F word on it
[12:17] <Rhonda> So?
[12:17] <bilalakhtar> and I never heard about the license
[12:17] <Rhonda> It's not that uncommon anymore. :)
[12:17] <bilalakhtar> I have heard about all types of FOSS licenses, but this one was a new one for me :)
[12:17] <bilalakhtar> ok
[12:17] <bilalakhtar> Rhonda: Can you ack, please?
[12:17] <Rhonda> If you go to hunt for F words, get the linux kernel removed. ;)
[12:18] <bilalakhtar> Rhonda: why?
[12:18] <Rhonda> Comments in there are known to contain various levels of profanity.
[12:18] <bilalakhtar> Rhonda: So bad!
[12:18] <Rhonda> The WTFPL is a FSF approved free software license. :)
[12:18] <bilalakhtar> But, don't the Linux Foundation people regulate the people in their development team ?
[12:19] <bilalakhtar> ok, enough of the F
[12:19] <bilalakhtar> word
[12:19]  * sebner waves at Rhonda :)
[12:19]  * bilalakhtar hopes Rhonda is free and will ack his sync 
[12:19] <umang> bilalakhtar, I think even some debian changelogs aren't very so nice about language. And at least with DWTFYL, it's in a well meaning way.
[12:20] <bilalakhtar> This was the first time I saw the F word in a package. I have worked on over 50 packages before this, but this was odd
[12:20] <umang> bilalakhtar, http://bugs.debian.org/477454
[12:21] <Rhonda> bilalakhtar: http://sam.zoy.org/wtfpl/ has a FAQ, "Can’t you change the wording? It’s inappropriate / childish / not corporate-compliant."
[12:21]  * bilalakhtar is shocked at the bug umang gave him
[12:21] <Rhonda> Uh yes, the quodlibet bucket issue. Sweet. :)
[12:21]  * Rhonda waves at SEJeff_home
[12:21] <Rhonda> erm, sebner
[12:21] <Rhonda> SEJeff_home: unping, sorry. :)
[12:23]  * bilalakhtar waves at Rhonda sebner and umang 
[12:23] <sebner> bilalakhtar: holaa :)
[12:23] <umang> like I said, when these kind of things happen, you shouldn't at all mind it when a four letter word is used with a (very) good intention
[12:23]  * umang waves back
[12:24] <Rhonda> Hmm.
[12:25] <Rhonda> I really should get added to the sponsors team …  Again in the situation where I can't remove the sponsors team from subscribers. %-)
[12:41] <sebner> Rhonda: unsubscribed sponsors-team for you + set to "Confirmed", don't forget that :P
[12:43] <Rhonda> sebner: Oh, forgot setting Confirmed, right, sorry.
[12:43] <nbolton> Hi all, if I remove a plugins table from my database, isn't `rake db:migrate_plugins` supposed to re-create it?
[12:43] <sebner> Rhonda: np, yw
[12:44] <nbolton> Oops, wrong channel!
[12:44]  * nbolton sighs
[13:04] <vorian> we should not exceed debian on standard versions Rhonda
[13:04] <vorian> just a freindly fyi :)
[13:05] <Rhonda> vorian: Did I suggest that? If it sounded like, I didn't.
[13:07] <Rhonda> vorian: The question was about a package that already has that from what I understood - for whatever reason.
[13:10] <vorian> Rhonda: ah, ok
[13:11] <vorian> it just looked like you said it didn't matter
[13:17] <Rhonda> "A diff just for the standards-version doesn't make much sense, if it's only in debian/control anyway." - doesn't sound in any way encouraging to me. :)
[13:41] <Rhonda> bleah
[14:14] <lfaraone> What's the recommended way to get the most updated version of lintian for use when checking packages? (I take it rebuilding from debian source locally isn't the best idea)
[14:17] <RainCT> lfaraone: install it directly from sid? :P
[14:19] <sebner> hoi RainCT :)
[14:19] <sebner> lfaraone: maverick just got an lintian update
[14:20] <RainCT> hi sebner
[14:20] <RainCT> bbl, getting some lunch
[14:21] <lfaraone> sebner: mk, so I'll just have to arrange a backport then.
[14:27] <Rhonda> Aren't there ubuntu specific patches to linitan that are relevant?
[14:28] <Rhonda> So pulling it from maverick should rather be the proper answer, not unstable. :)
[14:28] <lfaraone> Rhonda: yeah, one, related to CDBS symlinks.
[14:34] <lfaraone> sebner, Rhonda, if you're interested in a lucid backport, see bug 610082.
[14:36] <sebner> lfaraone: so you want me to testbuild and install that thing? :P
[14:36] <Rhonda> lfaraone: Not really - I use Debian's lintian and do my packaging in Debian, too. :)
[14:37] <sebner> Rhonda: I hope you at least testbuild with a ubuntu chroot :P
[14:38] <Rhonda> sebner: You mean with respect to the wesnoth-1.8 backports that I requested? Sure thing.
[14:38] <Rhonda> And I just noticed that I don't have a maverick chroot yet.
[14:38] <sebner> Rhonda: pfffff :P
[14:39]  * Rhonda . o O ( sudo cp -a /var/cache/pbuilder/cow/lucid /var/cache/pbuilder/cow/maverick; sudo sed -i -e 's/lucid/maverick/g' /var/cache/pbuilder/cow/maverick/etc/apt/sources.list; sudo cowbuilder --update --basepath /var/cache/pbuilder/cow/maverick )
[14:39] <Rhonda> What pffff?
[14:40] <lfaraone> sebner: I testbuilded it.
[14:40] <lfaraone> sebner: feel free to install it :)
[14:40] <sebner> lfaraone: Making a deeeeeeep backport test means building and installing on my own :P
[14:40] <Rhonda> lfaraone: testbuilt, btwl. It's a irregular verb. Even if it's nitpicking it's meant helpful. :)
[14:41] <lfaraone> Rhonda: meant to be helpful* :P
[14:41] <Rhonda> meant in a helpful way? :)
[14:42] <lfaraone> "meant well" is the idiom, I think.
[14:43] <Rhonda> Thanks. :)
[14:43] <lfaraone> Rhonda: do you ever get "Help me Rhonda" jokes?
[14:44] <Rhonda> What do you think? There's always someone to be found to consider it extremely funny, yes.
[14:45]  * lfaraone doesn't find it funny, just was curious. 
[14:45] <Rhonda> Even though when thinking about it they would have to realize that it's the least original thing they could come up with.
[14:45] <lfaraone> Rhonda: almost less original than "Luke, I am your father."
[14:46]  * lfaraone points to the L in lfaraone.
[14:46] <Rhonda> I like the Beachboys, but I started to grow a hatered for that song. On the other hand, it's just understandable because I am known as a helpful person and people often seek my advice, so …
[14:46] <jpds> lfaraone: I thought that was a 1.
[14:46]  * lfaraone stabs jpds, hard. 
[14:46] <jpds> ;-)
[14:46] <Rhonda> And jpds is shorthand for jeopardys?
[14:47] <jpds> Rhonda: Potentially.
[14:47] <sebner> lfaraone: commented on the bug + improved descriptions stuff ;)
[14:48] <lfaraone> sebner: much appreciated.
[14:48] <sebner> yw
[15:24] <proppy> lifeless: ping
[15:25] <lifeless> hi?
[15:25] <proppy> Hi, I just found out about your patch to add xrandr support to xvfb
[15:25] <proppy> http://bugs.freedesktop.org/show_bug.cgi?id=26391
[15:25] <lifeless> \o/
[15:25] <proppy> I forwarded them to debian bts
[15:25] <proppy> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590468
[15:25] <lifeless> nice
[15:26] <proppy> it seems a proper submittion to xorg-devel need to be done in order for it to be applied upstream
[15:26] <proppy> did you follow ? http://www.x.org/wiki/Development/Documentation/SubmittingPatches
[15:29] <proppy> see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590468#10
[15:32] <Rhonda> Hmm. cowbuilder --update from lucid to maverick doesn't seem to work. :(
[15:36] <proppy> lifeless: I would be happy to help thought
[15:36] <proppy> since I'm also interested in getting this patch pushed upstream
[15:38] <lifeless> i have to fly nowish
[15:39] <lifeless> will talk in a few days
[15:43] <proppy> lifeless: thanks
[15:49] <Rhonda> Alright, great notify-send blog entry - now I wonder how to tweak the look of the notifications.  %-)
[16:15] <nigelb> LucidFox: re: interviews we should make a list :)
[16:16] <LucidFox> Make a list?
[16:16] <LucidFox> Oh right
[16:16] <LucidFox> the Behind MOTU ones
[17:28] <statik> micahg, thanks for forwarding the couchdb1.0 request upstream to debian. i've done that work upstream in pkg-erlang team in debian already, it's just stalled waiting for review and so i went ahead and uploaded to ubuntu so we get it in before the freeze
[17:29] <micahg> statik: awesome, I didn't know, so wanted to imply less urgency upstream, thanks, were there any problems with xulrunner and couchdb?
[17:30] <statik> micahg: it's a hassle that we don't have libmozjs in ubuntu but debian still has it, thats one of the only remaining deltas that we have to carry in ubuntu. I've pushed everything else upstream.
[17:30] <micahg> statik: ok, does it still have issues when a new xulrunner is uploaded?
[17:31] <statik> micahg: i think so, couchdb wants to compile against and load libmozjs.so in order for the javascript view engine to be able to execute.
[17:31] <micahg> statik: k, can we add a wrapper around the daemon so it can find mozjs dynamically?
[17:32] <micahg> statik: congrats on MOTU BTW :)
[17:33] <statik> micahg, thanks! so it looks like right now we call xulrunner-1.9.2 --gre-version at build time in order to set the LD_LIBRARY_PATH, it seems quite possible to set that up so it's done at run time instead
[17:34] <micahg> statik: ok, that's what we've done with gxine and edbrowse and will be doing for mediatomb
[17:34] <statik> micahg, unfortunately i don't have time to work on that personally this week, but i will file a bug and see if someone on the desktopcouch team can write a patch for it
[17:34] <statik> thanks for the suggestion and pointers to the other packages that have solved it
[17:35] <micahg> statik: ok, if I can help let me know, I can try to do it a little later in the cycle if it falls through the cracks.  The only issue I can think of is what happens when xulrunner is upgraded and coundb is running
[17:36] <statik> hmm yeah, could be tricky if couchdb itself keeps running but reloads the child process that links against libmozjs.so
[17:36] <statik> i think we have that problem already though
[17:37] <j3su> hi
[17:37] <j3su> i search a french motu team
[17:37] <james_w> j3su: you can find francophones in #ubuntu-fr-devel I believe
[17:38] <micahg> statik: maybe we can trigger a restart during xul upgrades?
[17:40] <statik> micahg, ooh, that just might work. I'll write all this into the same bug report
[18:06] <Muscovy> What's the correct way to version a non-maintainer upload?
[18:08] <micahg> Muscovy: we don't have maintainers
[18:09] <micahg> Muscovy: what's the current version?
[18:09] <Muscovy> 0.9.14/
[18:09] <micahg> Muscovy: dch -i usually does the right thing except for SRUs
[18:09] <micahg> Muscovy: which release, which package?
[18:10] <Muscovy> lLcid, I'm backporting opengtl-0.9.14
[18:10] <micahg> Muscovy: it's done already
[18:10] <Muscovy> Oh? I couldn't find that package in lucid.
[18:10] <micahg> Muscovy: did you enable -backports?
[18:11] <Muscovy> ...no, I don't think I did.
[18:11] <micahg> Muscovy: you can check versions available with rmadison in devscripts
[18:12] <Muscovy> Ok, thanks.
[19:46] <fabrice_sp> micahg, got five minutes? It's about mediatomb
[19:47] <micahg> fabrice_sp: well, I can answer a few questions
[19:47] <fabrice_sp> I'm blocked  because of Bug #465811
[19:48] <fabrice_sp> is it something you're familiar with?
[19:49] <micahg> hmmm, the file is there in the includ dir
[19:49] <micahg> but there's no unstableanymroe dir
[19:49] <micahg> fabrice_sp: how are you trying to include it?
[19:50] <fabrice_sp> yeah: xulrunner also contains expat.h, and don't define XML_Char
[19:51] <fabrice_sp> micahg, http://paste.ubuntu.com/469474/
[19:51] <fabrice_sp> I had to do that, because otherwise, configure fails
[19:53] <micahg> fabrice_sp: that looks goodf
[19:53] <micahg> fabrice_sp: expat_config.h defines XML_Char
[19:53] <fabrice_sp> my guess is that xulrunner is not compatible with libexpat
[19:53] <fabrice_sp> hmm, let me check
[19:53] <fabrice_sp> I missed that, I think
[19:54] <micahg> fabrice_sp: that could be
[19:55] <micahg> fabrice_sp: there's not much difference between the 2
[19:56] <fabrice_sp> the message is different now: missing nspr.h
[19:56] <fabrice_sp> so I have to check the includes. Thanks!
[19:57] <micahg> fabrice_sp: k, let me know if I can do anything else
[19:57] <fabrice_sp> I hope I'll be able to fix it ;-)
[19:57] <fabrice_sp> thanks for your help
[19:58] <micahg> fabrice_sp: np
[20:05] <chilicuil> good afternoon, how can I know what changes went from 1 version to another? e.g. I can see $ rmadison qamulator output 2 different versions from lucid to maverick
[20:05] <chilicuil> I'd like to know to see if X bug is still there
[20:07] <highvoltage> chilicuil: I guess you could check the software name under /usr/share/doc, there are usually changelog files in there
[20:07] <chilicuil> highvoltage: ok, but then how do I download the maverick version if I'm in lucid?, do u have any clue?
[20:10] <highvoltage> chilicuil: there are quite a few ways, packages.ubuntu.com should provide for maverick one of these days then you could look at package versions and changelogs from there
[20:11] <highvoltage> I guess the easiest would just be to change your sources.list file to use maverick, install what you need and then change the sources back to lucid. (note that you can't downgrade the package again though)
[20:13] <chilicuil> ok, I think I'll use the packages.ubuntu.com url, thx highvoltage , btw I've seen the behing motus site, thx for develop Ubuntu :)
[20:13] <zooko> iulian: did you see my upgrade-tahoe-lafs ticket?
[20:14] <highvoltage> chilicuil: I do very very little but thanks anyway :)
[20:30] <fabrice_sp> hmm, anyone knows what's happening there: "error: corrupted profile info: profile data is not flow-consistent
[20:30] <fabrice_sp> "
[20:30] <fabrice_sp> ( http://launchpadlibrarian.net/52551431/buildlog_ubuntu-maverick-i386.stockfish_1.8.0-4_FAILEDTOBUILD.txt.gz )
[20:31] <micahg> fabrice_sp: do you have time to sponsor something for me?
[20:31] <fabrice_sp> sure
[20:31] <micahg> fabrice_sp: bug 608940, thanks
[20:31] <fabrice_sp> an easy one :-)
[20:31] <micahg> yep
[20:35] <BlackZ> hey fabrice_sp
[20:40] <fabrice_sp> hey BlackZ ;.)
[20:55] <fabrice_sp> micahg, uploaded
[20:55] <micahg> fabrice_sp: thanks
[20:55] <fabrice_sp> (sorry for the delay: I had to rebuild my lucid sbuild)
[20:55] <fabrice_sp> yw :-)
[21:15] <Rhonda> About the UbuntuOne iPhone client and the GPL issue, good news for all these things: http://www.nytimes.com/aponline/2010/07/26/technology/AP-US-TEC-Digital-Copyright.html
[22:32] <ari-tczew> I see in some patches a files /.pc/ what is it?
[22:33] <Laney> quilt applied patches directory
[22:34] <Laney> reminds me to write that lintian check
[22:34]  * Laney checks out
[23:05] <ari-tczew> does maverick support armel and sparc?
[23:07] <zooko> Folks: if someone could look at this before the imminent freeze for Maverick I would appreciate it:
[23:07] <zooko> https://bugs.launchpad.net/ubuntu/+source/tahoe-lafs/+bug/609755
[23:08] <micahg> ari-tczew: armel yes, sparc ATM, but most likely will be dropped
[23:21] <ari-tczew> hi and thanks micahg