[05:34] <ScottK> lucas_: I was looking at tokyocabinet-ruby.  It needs libtokyocabinet-dev (>= 1.4.37) and we don't have sufficient version.  Should I reject it (it's New for Ubuntu) or will you look into getting libtokyocabinet updated?
[09:09] <lucas_> ScottK: bah. please reject it
[09:11] <Laney> Can someone update the freeze exception in 309528 for 1.5.1.1-1, please? I've tested that it works (with some packaging changes).
[09:59] <alkisg> I'm trying to create a debhelper 7 package by following https://wiki.ubuntu.com/PackagingGuide/Python... did I understand correctly that I need to create a setup.py which essentially duplicates the info that I already have in debian/control and debian/install?
[10:00] <Laney> it expects your application to come with a setup.py file]
[10:01] <alkisg> I'm the author of the application, so... hm... I need to learn how to write a setup.py file. I'm googling for it, but it seems weird to me that I need to put the same info in two places...
[10:03] <alkisg> I mean, I can't automatically create a minimal setup.py from debian/*, right?
[10:04] <wgrant> If your upstream setup.py is correct, you should not need a debian/install.
[10:05] <alkisg> (I'm the upstream author) thanks, so I'll just move what I have in debian/install to setup.py.
[10:47] <Ciemon> Morning all, I've been doing some work on the package predict which is cuurently linked to the same package in Debian. Is there anything written down about who/when/how etc of linking upstream?
[10:48] <Ciemon> that should be not currently linked
[10:49] <Ciemon> I may be able to write that in English if it's not clear enough :)
[10:55] <joaopinto> is there a "regular" case in which /var/lib/dpkg/info/*md5sums are expected to be missing for an installed package ?
[10:58] <Laney> Ciemon: I don't know what you mean by linking upstream. Can you elaborate?
[11:02] <lifeless> joaopinto: yes, if they aren't included
[11:02] <joaopinto> lifeless, I am not aware of such an option when building a package, there is one ?
[11:04] <lifeless> joaopinto: of course, debs can be built many many ways
[11:04] <lifeless> see debbugs 155676
[11:04] <joaopinto> lifeless, aren't all official packages built with dpkg-buildpackage ?
[11:04] <Ciemon> Laney: sure.. we have Predict in Ubuntu, as do Debian. The patches I've been working on applying over the last week should really be passed to Debian too. I want to get the info right so that I can tell the patch author what he should do to get these patches into Debian
[11:04] <lifeless> joaopinto: yes, and ? :)
[11:05] <lifeless> joaopinto: dpkg-buildpackage doesn't do most of the building
[11:05] <joaopinto> hum, isn't dpkg-buildpackage automatically adding the md5sums ?
[11:05] <Laney> Ciemon: Have you spoken to the upstream author about including them in the next release?
[11:05] <joaopinto> or it's a debian/rules task ?
[11:06] <Laney> Ideally you file upstream bugs and also forward your patches to Debian including both bug links (LP + upstream) and the patches themselves
[11:06] <sistpoty> joaopinto: it's a debian/rules task, usually done with dh_md5sums
[11:06] <lifeless> joaopinto: man dh_md5sums
[11:06] <joaopinto> ah ok
[11:07] <joaopinto> that explains the missims md5sums :P
[11:47] <Ciemon> Laney: the author isn't answering mail, which is why I was suggesting pushing to Debian
[11:48] <Laney> Ciemon: That's fine, just give all the info you have in the Debian bugs
[11:49] <Ciemon> Sure, but at https://launchpad.net/ubuntu/+source/predict there seems to be some sort of link available, that's kinda what I was asking about.
[11:50] <Laney> I don't know what that does
[11:50] <Ciemon> :)
[11:51] <Ciemon> Thanks.. I think ;)
[11:51] <Laney> but I'm pretty sure it makes no difference to what you want to do here
[11:51] <Laney> ;)
[11:51] <Ciemon> Gonna talk about this a lot on MOnday when we record the show
[11:51]  * Laney trembles
[11:52] <Ciemon> :)
[11:52] <Laney> general advice about working with Debian is here https://wiki.ubuntu.com/Debian/ForUbuntuDevelopers
[11:59] <RunePhilosof> Where does the source code for evolution-mapi come from? The homepage listed in the package description contain version 0.26.1 while the latest ubuntu package is 0.28.2
[11:59] <Laney> Ciemon: More seriously, if you're finding it difficult to get involved then these are problems which should get fixed, so don't just let them lie
[12:00] <Laney> RunePhilosof: ask whoever did the last update where they got it from
[12:00] <RunePhilosof> of course
[12:01] <Laney> or check the watch file, maybe that's more current
[12:01] <Laney> or... *cough* http://ftp.gnome.org/pub/gnome/sources/evolution-mapi/0.28/
[12:01] <Ciemon> Laney: not finding it hard as such, there's lots of mentors around. Actually I'm off to see Daviey shortly for some guidance
[12:24] <sistpoty> iulian: mind taking a look at bug #559959 (I'm still not 100% sure if the hat build failure is not a bug in hmake, but given that hat has always been troublesome, I think it's not related)
[12:25] <sistpoty> (and hat's build system is ugly at best, as I'm crawling through it atm.)
[12:31] <sistpoty> Laney: huh, ghc6 did make it on armel in just one day, 10 hours :)
[12:32] <Laney> sistpoty: WHAT?!
[12:33] <sistpoty> Laney: https://launchpad.net/ubuntu/+source/ghc6/6.12.1-12/+build/1526050
[12:33] <sistpoty> maybe one of the gcc fixes, or a different kernel of a different buildd helped it :)
[12:33] <Laney> I don't believe it!
[12:34]  * sistpoty neither
[12:34] <Laney> which buildd did it go to
[12:34]  * Laney looks
[12:34] <Laney> hm, not heard of that one
[12:35] <Laney> right, now we urgently need to get all of the builds done
[12:35] <Laney> sistpoty: can you grant the FFe of pandoc 1.5.1.1 too? I'll upload it into depwait
[12:35] <sistpoty> Laney: sure, give me sec
[12:35] <sistpoty> +a
[12:36] <Laney> there's already a bug open for the sync, I'll just repurporse that
[12:36] <Laney> -r
[12:36] <Laney> bug 309528
[12:39] <Laney> sistpoty: http://orangesquash.org.uk/~laney/haskell-installability/armel.png is our target
[12:39] <Laney> this should be solvable with give-backs
[12:39] <sistpoty> Laney: excellent :)
[12:41] <Hew> I've made a darkstat sync request at bug 549351, and have been asked for a lucid build log. How can I get this? Do I use a PPA?
[12:42] <Laney> Hew: pbuilder can save a log with the --logfile (iirc) option
[12:42] <Laney> or a PPA upload will do
[12:42] <Hew> thanks Laney I'll give the PPA upload a go
[12:50] <sistpoty> Laney: pandoc: go for it
[12:50] <Laney> sistpoty: thanks, uploading
[12:51] <Laney> It's a bit of a brutal upload to be honest - I just chopped out the new cdbs bits
[12:51] <Laney> but it works
[12:51] <sistpoty> heh
[13:03] <sistpoty> Laney: just gave back the top row on armel... that was lots of clicking :)
[13:03] <Laney> sistpoty: good work!
[13:03] <Laney> (but in future, there is a buildd script in ubuntu-dev-tools that will save you that)
[13:04]  * sistpoty likes to click that button *g*
[13:04]  * sebner agrees with sistpoty *g*
[13:06] <sistpoty> sebner: haskell-haskeline should need a rebuild, if I can follow the arrows on http://orangesquash.org.uk/~laney/haskell-installability/armel.png correctly... want to click?
[13:07] <Laney> some of the green ones are false positives too
[13:07] <Laney> so you should verify those manually
[13:07] <sebner> sistpoty: only armel?
[13:08] <Laney> yes
[13:08] <sistpoty> sebner: yep, since ghc6 only made it recently on armel
[13:08] <Laney> ia64 is broken so much
[13:08] <sistpoty> Laney: do you agree to remove ghc6 and haskell packages on ia64
[13:08] <sistpoty> ?
[13:08] <Laney> In fact I was thinking about getting those binaries removed
[13:08] <Laney> ha
[13:08] <persia> Does anyone have ia64 hardware these days?
[13:08] <jpds> persia: Yes.
[13:09] <persia> jpds: Are small desktops available, or just big iron?
[13:09] <sebner> sistpoty: done, that's fun :)
[13:09] <sistpoty> last thing I heard was that the ghc6 build failure on ia64 wasn't always reproducible on the debian porter boxes, which makes debugging not exactly easier
[13:09] <Laney> sistpoty: kaol could build it on the porter boxes, but it always fell over on the buildds
[13:09] <Laney> and the ia64 porters couldn't come up with anything
[13:10]  * sebner is afraid of armel.png though
[13:10] <Laney> don't be
[13:10] <sistpoty> it can't break more than not build
[13:10] <persia> Once gh6 works, it's just a matter of following the graph.
[13:10]  * sebner is AFRAID of that graph xD
[13:11] <Laney> for Karmic we had a similar situation with ppc
[13:11] <Laney> that installability was fixed by throwing all of Haskell/ppc against the wall multiple times until it all stuck :)
[13:12] <sebner> hahah
[13:12] <Laney> this approach has a little more finesse than that
[13:12] <Laney> although I'm sure I could modify the script which generates the graph to tell me which packages to give back next
[13:12] <persia> You could probably even modify the script to give back the next set that needs give-backs.
[13:13] <Laney> yes, that's what I meant
[13:13] <Laney> oh, to actually do the give backs. Indeed.
[13:14] <persia> Actually, if you find a way to make it generalisable over the full package set, I'd be happy to run it daily after my mirror sync completes (for all arches).
[13:14] <Laney> it doesn't test buildability
[13:14] <persia> Ah, good point.
[13:14]  * sistpoty doesn't like the idea that a script will get all the pleasure that I have pressing on this button :P
[13:15] <persia> Well then.  Clearly the script needs to have a mail gateway with a list of URLs getting sent to sistpoty then :)
[13:15] <sistpoty> heh :)
[13:16] <persia> But for the script: I'd actually like to have something that lets us build a tree once the base is fixes: fpc needs bootstrapping on armel/powerpc after which there's a heap of stuff that can be built.
[13:17] <Laney> That would be useful indeed. Generally with Haskell transitions we only need to care about installability, so I haven't bothered to do that here
[13:18] <Laney> and the script which powers those graphs isn't particularly general either, sadly
[13:19] <Laney> http://pastebin.com/YRUZCk3i
[13:20] <persia> Such is life.  There's only ~30 pascal packages, and most of them are properly DEPWAIT, so that's perhaps less painful.
[13:20] <persia> Oh, that is very specific :)
[13:21] <Laney> Certainly the tree-building / installability testing could be split out though
[13:23] <think> HI ALL
[13:24] <joaopinto> hi
[14:04] <sistpoty> nhandler: mind taking a look at bug #559959
[14:05] <nhandler> Sure
[14:05] <sistpoty> thanks
[14:06] <nhandler> sistpoty: So it FTBFS due to a hat problem right now?
[14:11] <sistpoty> nhandler: no, it FTBFS since to haskell-utils was removed
[14:12] <sistpoty> nhandler: however hat FTBFS with the new hmake (most probably with the old hmake as well, even if haskell-utils would still be available and working)
[14:14] <nhandler> sistpoty: Can you at least attach a diff for the merge?
[14:14] <sistpoty> nhandler: sure
[14:16] <sistpoty> nhandler: attached (diff based on debian package)
[14:19] <nhandler> sistpoty: Granted
[14:19] <sistpoty> nhandler: thanks!
[14:52] <ScottK> Laney:  libghc6-hsql-mysql-doc is a new bianry package in your upload.  It's empty.  Please fix it and upload again.  Also, when you build the source package for a merge, please use the -v option to include all the new debian/changelog entries in the .changes file.  (do that for your fixed upload too since I'm going to reject this one).
[14:56] <ScottK> lucas_: Thanks.  Rejecting.
[14:59] <ScottK> Laney: Actually, I'm accepting it so the architectures don't get skewed, but it still needs fixint.
[15:17] <evilshadeslayer> Tonio_: ping...
[15:18] <iulian> sistpoty: Hey.  Do you still want me to take a look at that bug?
[15:18] <sistpoty> iulian: no, Nathan already gave me an ack, and I've already uploaded it :)
[15:18] <iulian> Ah.  It has already been acked.
[15:19] <sistpoty> iulian: btw, are you subscribed to ubuntu-release@l.u.c?
[15:19] <iulian> Sorry for the delayed response.  I have just arrived home.
[15:19] <sistpoty> no problem
[15:19] <iulian> sistpoty: I don't think so.
[15:20] <sistpoty> iulian: oh, can you subscribe? (have started a discussion about FinalFreeze for universe, see https://lists.ubuntu.com/archives/ubuntu-release/2010-April/000043.html, and had hope to reach everyone from the release team there *g+)
[15:21] <sistpoty> nhandler: are you subscribed to ubuntu-release@l.u.c? ^^
[15:21] <sistpoty> ScottK: same question to you ^^?
[15:21] <ScottK> sistpoty: I'm not.
[15:21] <ScottK> I probably should.
[15:21] <ScottK> Give me a moment.
[15:21] <sistpoty> ah, so I guess it wasn't the most brilliant idea from me to think I can reach everyone from the release team via ubuntu-release@l.u.c *g+
[15:22] <ScottK> sistpoty: No problem.  Done.  Just need for slangasek to accept my subscription.
[15:23] <ScottK> Now I know why he was talking about your mail.
[15:23] <ScottK> We had a brief discussion about it at the end of yesterday's release meeting.
[15:23] <iulian> sistpoty: OK, done.
[15:23] <sistpoty> ah, yes, have read that... sorry, once again couldn't make it
[15:24] <ScottK> No problem.
[15:24] <ScottK> In any case we agreed to your proposal.
[15:24] <ScottK> He was going to include it in a u-d-a post he was writing.
[15:24] <sistpoty> excellent!
[15:24] <sistpoty> cjwatson: are you subscribed to ubuntu-release@l.u.c?
[15:25] <ScottK> sistpoty: Why don't you just ask slangasek to see if all the release team members are subscribed rather than ask one by one?
[15:25] <sistpoty> ScottK: oh, does mailman allow that? if so, slangasek: ^^ :)
[15:26] <ScottK> Yes.  The list admin can do that.
[15:26] <sistpoty> cool
[15:29] <sistpoty> ScottK | iulian: I'd like to hear a second opinion on bug #523433
[15:32] <ScottK> sistpoty: Since it's wanted for a derivative, I'm inclined to say go ahead as long as they can find an archive admin (I don't have the time to commit to it).
[15:32] <sistpoty> ScottK: I guess I don't like the idea to add it for lucid and then drop it for lucid + 1 again, but I can't really say I'm decided on it (otherwise I hadn't asked *g*)
[15:34] <ScottK> sistpoty: I can see the sense of having both versions available for a transitional period.
[15:34] <ScottK> I'd have n'acked if they wanted to replace the old one.
[15:34] <ScottK> It's not ideal, but life rarely is.
[15:34]  * iulian agrees with ScottK.
[15:35] <sistpoty> ok, then let's ack it under the condition that an archive admin finds time
[15:35] <sistpoty> thanks for looking!
[15:39] <ScottK> Sounds good to me.
[15:41] <sistpoty> ScottK: yet another question: I'm inclined to ack munin (bug #538594), however as it's server related maybe you have some comments?
[15:41] <ScottK> Looking
[15:52] <ScottK> sistpoty: I'd approve it.  Wnat me too.
[15:52] <sistpoty> ScottK: yes, please
[15:54] <ScottK> Done.  Thanks for pointing it out.
[16:01] <sistpoty> porthose: can you follow up on bug #540583 please and do at least minimal testing? thanks!
[16:17] <ari-tczew> is MOTU Council dead? https://wiki.ubuntu.com/MOTU/Council/Meeting is not fresh
[16:17] <sistpoty> ari-tczew: yep
[16:17] <geser> yes, MC is out of business
[16:18] <nigelb> anyone on the D-M-B available for a chat?
[16:19] <geser> yes
[16:19] <nigelb> geser, I was wondering.. is it possible to have ~ubuntu-dev be a member of ~ubuntu-reviews?
[16:20] <asac> anyone running karmic?
[16:20] <asac> does firefox work for you will all the latest updates?
[16:20] <asac> ;)
[16:20] <nigelb> asac, yes
[16:20] <ari-tczew> I think that MOTU/Council/Meeting wiki page should be cleaned up. Just have information about MC is dead.
[16:20] <nigelb> I'm updating... gimme 10 minutes test out
[16:20] <asac> nigelb: do you use firefox?
[16:20] <asac> cool
[16:22] <asac> nigelb: not running the latest nss?
[16:23] <nigelb> asac, nss?
[16:23] <geser> nigelb: what would be the benefit if ~ubuntu-dev is a member of ~ubuntu-reviewers?
[16:24] <nigelb> geser, helps with patch review, since they'd be able to unsubscribe reviewers (i.e. no excuse for not going into it)
[16:24] <asac> nigelb: just upgrade everything ... and let me know if firefox still works after relogging into X etc.
[16:24] <ari-tczew> so who is responsible for MOTU meetings? where can I find meetings calendar - I'm interested to join MOTU
[16:24] <nigelb> ari-tczew, apply to developer membership board
[16:25] <nigelb> ari-tczew, https://wiki.ubuntu.com/DeveloperMembershipBoard
[16:25] <geser> ari-tczew: DMB handles MOTU applications, the next DMB meeting is Tue, April 13th 2010 15:00 UTC
[16:28] <ari-tczew> hm, so I'm poiting to next meeting after April 13th
[16:29] <geser> nigelb: I'm not sure this is a good idea (because of other reasons). As ~ubuntu-reviewers is subscribed to all bugs with patches, ~ubuntu-dev would get notifications for all those bugs (but I'm not sure about this)
[16:29] <nigelb> geser, notifications go into the patch review mailing list
[16:30] <geser> ari-tczew: that would be Tue, April 27th 2010, 15:00 UTC
[16:30] <geser> nigelb: members don't get any bug email if they aren't subscribeed to the ML?
[16:30] <nigelb> geser, I'm yet to get any
[16:31] <nigelb> geser, well, I did subscribe last week and just started getting mails
[16:32] <asac> nigelb: update finished ;)?
[16:32] <nigelb> asac, 8 minutes more to go
[16:32] <asac> oh
[16:32] <asac> big one ;)
[16:32] <nigelb> nah, slow connection
[16:34] <geser> nigelb: ok, I guess it's like with the sponsoring team where ubuntu-dev isn't a member too. If a dev is interested in sponsoring or patch review he should join the team, but I don't have a strong opinion. An explicit membership has the bonus that I can look up which dev is really interested in patch review (as I assume that only a few would join explicitly if they are a member implicitly).
[16:36] <nigelb> geser, ah, that is reasonable too :)  But I was thinking more in the likes of bug control
[16:41] <geser> I guess bug control is a little different as a dev should be able to update status and importance (it's part of their work).
[16:41] <nigelb> hm, It was just an idea :)
[16:41] <geser> although I'd like if more devs care about sponsoring and patch review (don't know how the situation is there).
[16:41] <nigelb> now I have to manually get the review leads into ~ubuntu-reviews
[16:42] <nigelb> the situation here is pretty bad... less than 10 active folks.
[16:42] <nigelb> asac, you want me to log out and log in back?
[16:43] <asac> nigelb: yeah. thats safe
[16:43] <asac> and then try to use firefox with ssl etc.
[16:44] <nigelb> i.e. https://www.somesite.com?
[16:46] <nigelb> brb... logging out
[16:48] <asac> launchpad
[16:48] <asac> ;)
[16:48] <asac> or something
[16:48] <geser> interesting, www.somesite.com has a DNS entry :)
[16:49] <asac> heh
[16:49] <nigelb> asac, just loggged into my netbanking account.  No issues yet
[16:49] <asac> ok
[16:49] <geser> nigelb: your money still there?
[16:49] <asac> let us know if you get ssl issues ;)
[16:49] <ari-tczew> does wiki.ubuntu.com have multilanguage support?
[16:49] <asac> thanks nigelb
[16:49] <nigelb> geser, Oh no! asac stole it! hehe :D
[16:49] <nigelb> asac, no problem :)
[16:51] <nigelb> geser, anyway continuing on what we were talking.  My idea was if some dev did want to help, it should be super easy.  (well, that was the dream anyway)
[16:54] <geser> nigelb: is it currently that hard for a dev to join?
[16:54] <nigelb> geser, apply and accept
[16:54] <geser> that doesn't sound hard
[16:55] <nigelb> but there is also prove that you do review and a +1 from existing member
[16:57] <geser> anyways as this involves joining a team to an other, an admin of ~ubuntu-reviewers IIRC has to initiate it. so you need to talk to them too.
[16:57] <nigelb> geser, I only wanted your take on it :)
[16:57] <nigelb> I was unsure if it was the way to go.  I'm still unsure.
[16:58] <geser> me too
[16:58] <nigelb> I talk to dholbach to hear his take on this.
[16:59] <nigelb> Anyway, I think I'll have to formally approach the dmb for this anyway
[17:00] <nigelb> dmb, I think you might want to change your nickname :D
[17:01] <ari-tczew> would be nice
[17:02] <nigelb> geser, thanks for your time :)
[17:15] <ari-tczew> is word "deprecated" good instead "dead" on wiki.ubuntu.com? context about MC end of life
[17:16] <RainCT> ari-tczew: what's the sentence?
[17:17] <ari-tczew> MOTU Council is dead and handled by [[#DeveloperMembershipBoard|Developer Membership Board]]. For meetings please read [[#https://wiki.ubuntu.com/DeveloperMembershipBoard/Agenda|DMB Agenda]].
[17:26] <sistpoty> ari-tczew: why not write "out of business"? (though I'm not a native speaker as well)
[17:27] <nigelb> or just say replaced by the DMB
[17:29] <ari-tczew> nigelb ^^ +1
[17:30]  * ScottK looks at http://blog.brettalton.com/2010/04/10/installing-openarena-in-ubuntu-and-applying-patches/ and suggests someone update our package.
[17:30] <ScottK> sistpoty is, I'm sure, happy to test before granting FFe.
[17:32] <sistpoty> ScottK: oh, yes... it'd need very severe testing though :P
[17:33] <ScottK> Yes, so  someone please take care of that ....
[17:34] <ari-tczew> what is Next Chair on Agenda?
[17:35] <nigelb> ari-tczew, next person to chair the meeting
[17:35] <ari-tczew> ok
[17:39] <ari-tczew> what is "TBD" on wiki?
[17:39] <nigelb> to be declared
[17:39] <sistpoty> ScottK: updating openarena is a pretty hairy business, due to debian bug 523323 ... I'll try to see if I can catch fuddl at work, and ask him for details
[17:39] <ScottK> sistpoty: Excellent.
[17:49] <ari-tczew> is MOTU going to full move as DMB?
[17:50] <nigelb> no no, only MOTU council is replaced.
[17:56] <ari-tczew> so current "MOTU mettings" should be called "DMB meetings" right?
[17:58] <bjsnider> will there be sun-java6 packages in lucid?
[18:00] <ScottK> ari-tczew: No.  MOTU will still be around, just no MC.
[18:00] <ScottK> bjsnider: In Canonical's partner repo, not formally in Ubuntu.
[18:01] <bjsnider> ScottK, it's not there now. eta?
[18:01] <ScottK> bjsnider: No idea.  I don't work for Canonical.  Partner generally gets populated at or after release.
[18:03] <ari-tczew> what a mess on wiki.ubuntu.com! so what's the different between MOTU meetings and DMB meetings? please show me where are informations about this difference on wiki?
[18:10] <ScottK> ari-tczew: MOTU meetings are a meeting of all the MOTU.  We haven't had one in a long time.  It has nothing to do with membership in stuff.
[18:12]  * hyperair thinks that ubuntu should undergo daemon-cleanup sometime
[18:12] <hyperair> i've got too many processes running >_>
[18:12] <nhandler> sistpoty: I should be subscribed. I'll double check
[18:12] <sistpoty> thanks nhandler
[18:14] <ScottK> sistpoty: I am subscribed now.
[18:14] <sistpoty> :)
[18:15] <ari-tczew> ScottK: with this approach wiki.ubuntu.com is going to /dev/null because will be useless
[18:15] <nhandler> sistpoty: Turns out I wasn't subscribed. I am now
[18:15] <sistpoty> :)
[18:16] <ScottK> ari-tczew: Wiki's need maintenance.  Someone needs to do it.
[18:16] <hyperair> does anyone know why erlang needs so much rubbish running?
[18:16] <hyperair> there's a beam.smp, an ssl_esock, some heart.smp, ....
[18:17] <hyperair> i wouldn't care so much if they're all lightweight, but added together they take over 30MB, and all that is *just* for desktopcouch.
[18:17] <hyperair> and this ridiculous couch thing takes an additional 10MB, not counting all the erlang processes started solely for it.
[18:18] <hyperair> and on top of that, the only thing that uses this useless couch is gwibber.
[18:18] <hyperair> i think i'll just stop using gwibber >_>
[18:20] <ari-tczew> ScottK: I'm going to invite more user for contribute to Ubuntu with new development cycle (maverick). I don't want give them confusing wiki pages. More professionaly please!
[18:20] <ScottK> ari-tczew: It's a wiki.  Go for it.
[18:23] <ari-tczew> ScottK: wiki.ubuntu.com is too messed, so I don't distinguish a lot of terms, concepts etc. Someone from administration and moderation should clean wiki - once and good.
[18:24] <ScottK> It's been done before and not so successfully.
[18:24] <ScottK> For MOTU stuff there is no "administration and moderation" it's just us.
[18:27] <ari-tczew> bordello, nobody for nothing is not responsible. wiki is siking
[18:36] <sistpoty> ScottK: FFe bug #503616 also looks server related ;)
[18:37] <sistpoty> (avoided looking at it yet, due to incompetence in this regard)
[18:39] <ScottK> sistpoty: Commented.
[18:43] <sistpoty> thanks
[19:09] <ScottK> sistpoty: I'll be AFK for several hours.  Ping and I'll read the scrollback when I return.
[19:09] <sistpoty> ScottK: sure, thanks for the notice
[19:10] <sistpoty> ScottK: and *do* get some sleep somewhen ;)
[19:10] <ScottK> sistpoty: Sleep is for the weak.
[19:10] <sistpoty> haha
[19:10] <sebner> ScottK: bash
[19:10] <sistpoty> <- weak
[19:10] <sebner> ScottK: I wanted to write exactly the same! (citat from you of course :D)
[19:10]  * sebner pets sistpoty 
[19:10] <sistpoty> *g*
[19:10] <sebner> sistpoty: you are simply getting old :P
[19:11] <sistpoty> sebner: well, turned 31 very recently (actually yesterday)
[19:11] <crimsun> i used to be old. then i took some pills and now i'm ancient.
[19:11] <sebner> sistpoty: ujj, congratulations then :)
[19:11] <sistpoty> thanks sebner
[19:11] <sebner> crimsun: ¬_¬
[19:44] <lfaraone> I noticed that xulrunner was dropped in Lucid, but I couldn't find a bug explaining the rationale. If upon testing, it builds properly and runs on Lucid, would it be suitable to request it to be synced from Debian? (this is needed to get sugar-0.88 working)
[19:45] <sistpoty> ajmitch: around? Do I recall it correctly that you have good knowledge of the zope stack? (as I'm a little bit clueless about FFe bug #542634)
[19:47] <crimsun> lfaraone: eh? xulrunner-1.9.2 | 1.9.2.3+nobinonly-0ubuntu1 |         lucid | source, amd64, i386
[20:01] <lfaraone> crimsun: aha. there's just no longer an unversioned "xulrunner", it seems. nor is there a python-xpcom (previously provided by "xulrunner")
[20:01] <lfaraone> *built by
[21:01] <sistpoty> DktrKranz: got a sec to look at FFe bug #551526, as I'm totally clueless about what's requested there, and what goes wrong
[21:02] <sebner> sistpoty: I'm not sure if he will be online today again
[21:02] <sistpoty> sebner: oh
[21:03] <sistpoty> well, there's always the option to leave a comment at the bug report in question :)
[21:03]  * sebner ^5 sistpoty :)
[21:03] <sistpoty> :)
[21:24] <sistpoty> menesis: around? can you give some further insights into bug #542634? thanks!
[21:42]  * abogani waves
[21:42] <abogani> I'm looking for sponsors: https://wiki.ubuntu.com/AlessioIgorBogani/linux-rtPPUApplication
[21:42] <abogani> Thanks
[21:43] <sistpoty> ScottK: one for you (main): bug #555235
[22:45] <ari-tczew> !seen av`
[23:45] <sistpoty> ScottK: re bug #545690... do you want the new version in? if so, don't hesitate to acknowledge it ;)
[23:46] <ari-tczew> is phpmyadmin a server package?
[23:47] <sistpoty> ari-tczew: I'd very much say so, yes
[23:48] <ari-tczew> exactly! security team has pointed phpmyadmin as desktop package. ridiculous!
[23:51] <sistpoty> ari-tczew: hm?
[23:51] <ari-tczew> sistpoty: phpmyadmin is ignored for dapper as desktop package. you can look at UCT
[23:52] <ari-tczew> dapper desktop is eol
[23:54] <sistpoty> ari-tczew: aha, it's in universe
[23:55] <sistpoty> ari-tczew: to my knowledge, packages in universe don't enjoy the extended support period that -server has
[23:55] <sistpoty> (but I might be wrong)
[23:56] <ari-tczew> sistpoty: for discussion you can join #ubuntu-hardened, as you are a member of motu-swat anyway
[23:57] <sistpoty> ari-tczew: I'm the laziest member of motu-swat (only being still a member since one late night I had the idea together with nafallo to found a security team for universe)
[23:58] <sistpoty> ari-tczew: just joined