[12:16] <ajmitch_> Mez: yes?
[12:16] <Mez> ajmitch_, would you be willing to sponsor ifolder into debian once it's finished being packaged (assuming of course that it's of high enough grade packaging quality)
[12:17] <ajmitch_> maybe
[12:17] <ajmitch_> is this an individual packaging effort, separate from the mono packaging team?
[12:17] <Mez> yes
[12:18] <Mez> though - I will of course be poking a lot of the mono team for advice :D
[12:18] <ajmitch_> oh joy
[12:19] <Mez> well, I've had quite a bit of advice off them already on previous attempts
[12:19] <Mez> so it shouldnt be too bad
[01:10] <crimsun> gah, ENOELMO
[01:10] <ajmitch_> crimsun: he's hiding?
[01:10] <ajmitch_> or he's probably stressing over the move to soyuz
[01:10] <ajmitch_> and drinking his troubles away
[01:11] <crimsun> quite reasonable =)
[01:14] <Lathiat> hah
[02:22] <Kyral> Okay...Its a good thing I found Ubuntu before I found SuSE
[02:22] <raphink> Kyral: sssshhh
[02:23] <Kyral> what?
[02:23] <raphink> :s
[02:23] <raphink> nm
[02:23] <Kyral> Its not like I'm up and leaving Ubuntu
[02:23] <raphink> yeah yeah ;)
[02:23] <raphink> of course not :)
[02:23] <Kyral> I'm just saying Yast is NICE ;P
[02:23] <Amaranth> bored2k did
[02:24] <raphink> what did you use before getting to Ubuntu?
[02:24] <Amaranth> suse doesn't have alacarte ;)
[02:24] <Kyral> Ohh...Slack 10, Gentoo
[02:24] <Amaranth> at least i don't think so
[02:24] <Amaranth> but GNOME 2.16 will :D
[02:24] <Kyral> I don't use the Menu Editor much :P
[02:25] <Amaranth> Kyral: it doesn't have easyubuntu either
[02:25] <Kyral> Amaranth: I don't need EasyUbuntu ;P
[02:25] <Amaranth> or all of us on call to fix things :)
[02:25] <Kyral> okay that you have me :p
[02:25] <Kyral> I'm just saying I wanna help the Yast4Debian project now lol
[02:26] <raphink> Kyral: very nice idea :)
[02:27] <raphink> from what I heard about yast, i'd love to see it in Kubuntu :)
[02:27] <raphink> although i've heard it's so complex a program that it's very hard to port
[02:27] <Kyral> SaX wouldn't hurt either
[02:29] <Kyral> It is a NICE GUI to configure X with
[02:31] <zakame> heya MOTUs :)
[02:31] <Kyral> yo zakame
[02:32] <zakame> yo Kyral :)
[02:36] <raphink> hi zakame
[02:37] <zakame> heya raphink master revu-er :)
[02:37] <raphink> lol
[02:37] <zakame> good job on the motu doc move-around :)
[02:37] <raphink> :)
[02:37] <raphink> thanks
[02:37] <raphink> took me about 10h
[02:37] <raphink> so far no one complained
[02:37] <raphink> I take it it was accepted ;)
[02:38] <zakame> actually it was much-needed :)
[02:38] <raphink> I think so too
[02:38] <raphink> otherwise I wouldn't have done it ;)
[02:38] <zakame> hehe
[02:38] <raphink> now we can see much more clearly what needs to be merged, nuked, and so on
[02:39] <raphink> just have to keep the doc tree up-to-date
[02:39] <raphink> :)
[02:39] <raphink> I got back to REVU today though ;)
[02:39] <raphink> I had enough of the wiki ;)
[02:40] <raphink> did you have a look at the tools I developped today zakame ?
[02:40] <raphink> I just posted a message on ubuntu-motu about them half an hour ago
[02:40] <raphink> oh ok :)
[02:40] <zakame> ooh lemme check then :D
[02:40] <raphink> sure
[02:40] <raphink> :)
[02:44] <zakame> wow, REVU-tools are great :D
[02:45] <raphink> glad you like them :)
[02:45] <zakame> (which also reminds me I should ping siretart about making me an account on tiber for remote REVU ;)
[02:45] <raphink> that's the main thing I did today :)
[02:45] <raphink> yes that's very useful
[02:46] <raphink> I'll ping siretart again tomorrow to get sure he checks my changes to the svn and adds the new revu tools to /usr/local/bin so they can be used by all
[02:46] <raphink> so far I call them with ~/revu-report
[02:46] <raphink> which is not useful for other tiber users
[02:46] <raphink> hehe
[02:47] <zakame> hehe, or package it even ;)
[02:47] <raphink> oh sure I'm thinking of it
[02:47] <raphink> but then it has to be made `distributable`
[02:48] <raphink> i.e. REVU-independent
[02:48] <zakame> ooh right
[02:48] <raphink> so far it depends a bit too much on tiber's settings and scripts
[02:48] <raphink> and I think it can be made independent to run on any box
[02:48] <raphink> even be used by DDs for sponsoring imo ;)
[02:48] <zakame> that would be nice indeed
[02:48] <raphink> if some of them accept these tools ;)
[02:48] <zakame> yeah
[02:49] <raphink> so that's work for the days to come :)
[02:49] <zakame> a lot of rocking on for you then :D
[02:50] <raphink> it's not to find work in Ubuntu ;)
[02:51] <zakame> hehe
[02:51] <raphink> $ ~/revu-report pam-abl_0.2.3-0ubuntu1.dsc pam_abl-0.2.3.tar.gz
[02:51] <raphink> hop :)
[02:52] <raphink> I'd really like to be able to get the upstream tarball automatically
[02:52] <raphink> but I think Debian policy should be changed to be able to do that
[02:52] <zakame> yeah, I think it could also work for doing some auto-merging work
[02:52] <raphink> since there would have to be a place in the package where the url of the upstream tarball would be clearly given
[02:53] <Mithrandir> uhm, you do realise you should review all changes in each upstream version?
[02:54] <Mithrandir> anyway, sleep
[02:54] <zakame> Mithrandir: hmm, that too
[03:04] <raphink> yep, sleep
[03:04] <raphink> dist-upgrading my box and I'm off to bed :)
[03:17] <raphink> gn
[03:22] <zakame> bbl
[04:44] <jsgotangco> heya minghua
[04:44] <minghua> hi jsgotangco
[04:45] <jsgotangco> minghua, i got to talk to sabdfl 2 days ago over lunch and we talked about cjk and scim
[04:46] <jsgotangco> minghua, he's in tokyo at the moment i think but he'll be passing over to korea and china so i guess there will be focus on discussions with such support
[04:47] <minghua> jsgotangco: great to hear about it
[04:48] <minghua> jsgotangco: mako talked about CJK support during last CC meeting too
[04:48] <jsgotangco> oh cool
[04:49] <minghua> there sure is interest, we probably need more people though
[04:58] <jsgotangco> yeah
[05:36] <monzie> i want to contribute to Ubuntu
[05:37] <monzie> i have debian packaging experience
[05:38] <hub> monzie: https://wiki.ubuntu.com/MOTU
[05:39] <hub> monzie: that is the starting point
[05:40] <monzie> thanks, hub
[05:49] <monzie> the docs are a bit confusing hub
[05:50] <monzie> where can i get the list of packages to work on or something like that?
[05:53] <StevenK> From the bug list?
[05:53] <StevenK> It's a litle more complicated than working on Debian, you don't just look after a package or two.
[05:54] <monzie> okay
[05:55] <Amaranth> everyone can touch every package, no one owns a package
[05:55] <Amaranth> makes it easier
[05:55] <StevenK> And harder to find someone to blame. ;-P
[05:55] <Amaranth> no, that's still easy
[05:55] <Amaranth> blame who touched it last
[05:55] <hub> StevenK: changelog is your friend
[05:57] <Amaranth> yeah
[05:57] <Amaranth> btw, never touch firefox
[05:57] <Amaranth> people will try to make you the permanent maintainer :P
[05:58] <StevenK> Heh
[05:59] <StevenK> That's what Diziet is for. :-P
[05:59] <jsgotangco> heh
[05:59] <jsgotangco> seamonkey
[05:59] <StevenK> At my place of work we have a 'the person who touched it last gets to look after it' policy.
[06:00] <StevenK> jsgotangco: The other I've heard is 'iceweasel'
[06:03] <jsgotangco> yeah i think that's the future all in one mozilla suite/components
[06:35] <fubarity> Can someone explain how Ubuntu's package versioning nomenclature works? I have browsed everywhere, only to find very little conclusive. And, moreover, why is it that some packages are <package>-(numbers), while some are <package>-(numbers)-(numbers)ubuntu(numbers)?
-(numbers) means that the package has been synced with debian
[06:36] <crimsun> ok, it's pretty straightforward (you can find this info in the Debian New Maintainer's Guide)
[06:36] <crimsun> packages where the versioning is A.B.C are native Debian or Ubuntu packages
[06:36] <crimsun> those where the versioning is A.B.C-X are Debian-maintained
[06:37] <crimsun> those where the versioning is A.B.C-XubuntuY are Ubuntu-modified from their original Debian counterparts
[06:37] <crimsun> so A.B.C-X, lke Gloubiboulga said, are synced straight from Debian
[06:37] <psusi> -ubuntuN is for packages with ubuntu specific changes that replace the previous version from debian, but the next version from debian will be newer than the -ubuntuN
[06:46] <fubarity> Now, suppose that I am going to Debianize (i.e., make a *.deb) a package for Ubuntu for a package for which no actual Debian package exists. Which nomenclature would I use? And what do the X and Y components surrounding XubuntuY mean?
[06:47] <crimsun> if it doesn't exist in Debian yet, then you'd package it as A.B.C-0ubuntu1
[06:47] <crimsun> that way when it enters Debian, Debian's versioning has higher precedence
[06:47] <crimsun> (A.B.C-1)
[06:48] <fubarity> So, what do the 0 and 1 mean? Could these variables have any other values?
[06:48] <crimsun> they signify packaging revisions (as opposed to "upstream" versions)
[06:49] <crimsun> and no, for the case you describe, X must be 0, and Y must be 1
[06:50] <crimsun> generally, however, yes, X and Y are not tightly coupled
[06:51] <zakame> this nomenclature is to avoid possible clashes when someone from Debian decides to make a NEW package (which could either be based on your Ubuntu package, or created from scratch altogether; see njam for an example ;)
[07:01] <fubarity> I appreciate everyone's help here; it means a lot.
[07:01] <zakame> no prob :)
[08:08] <Kyral> Night MOTU
[09:16] <siretart> good morning soyuz lovers!
[09:16] <siretart> :)
[09:16] <siretart> this is what I call quick response: debian #351280
[09:16] <zakame> good morning siretart ! :D
[09:16] <siretart> hi zakame
[09:17] <siretart> zakame: I have a hilight in my backlog, you wanted some sort of 'remote' access to revu?
[09:17] <siretart> huh?
[09:18] <zakame> yeah, but the gist of that is I want to be able to test build of REVU-ed packages, not necessarily shell access
[09:19] <siretart> currently you need shell access to call revu-build
[09:19] <zakame> ah
[09:34] <zakame> heya Hobbsee
[09:34] <Hobbsee> hey zakame :)
[09:38] <zakame> what's up?
[09:39] <Hobbsee> just got home from work, having trouble building asciiquarium
[09:43] <zakame> oooh
[09:43] <zakame> brb, someone needs to call :/ (dialup)
[09:54] <TheMuso> c
[11:28] <siretart> raphink: I updated /srv/revu to rev 120 (currently HEAD)
[11:29] <raphink> siretart: thanks :)
[11:29] <raphink> siretart: did you make the new links in /usr/local/bin too?
[11:31] <siretart> raphink: done
[11:32] <raphink> thanks :)
[11:32] <raphink> much :)
[11:33] <siretart> no problem
[11:34] <raphink> argh I made a mistake in revu-build though
[11:34] <raphink> siretart: I'll correct it, it's just a small mistake, if you can aprove it fast
[11:34] <raphink> siretart: in revu-build, I've put
[11:34] <raphink> PBUILDEROPTS="--buildresult $(pwd) --logfile ${BASENAME}.buildlog --hookdir /srv/revu1/scripts/pbuilder-hooks/"
[11:35] <raphink> it should be
[11:35] <raphink> PBUILDEROPTS="--buildresult $(pwd) --logfile ${BASENAME}.buildlog --hookdir /srv/revu1/pbuilder-hooks/"
[11:35] <raphink> otherwise it won't work
[11:39] <raphink> siretart: updated the svn with this single change, can you commit it?
[11:45] <siretart> raphink: done
[11:45] <raphink> thanks :)
[11:45] <raphink> I think that's all :)
[11:46] <siretart> raphink: could you please install a .forward file on tiber?
[11:46] <raphink> how do you mean siretart ?
[11:46] <siretart> I'd like to add you to the svn postcommit hook, so that you get svn mails as well
[11:46] <raphink> oh ok
[11:46] <raphink> so what do I need to do?
[11:46] <siretart> raphink: do a 'echo raphink@youremail > ~/.forward'
[11:46] <raphink> ok
[11:46] <siretart> you can also configure procmail, if you wish ;)
[11:47] <raphink> done
[11:47] <raphink> I mean the .forward ;)
[11:47] <siretart> ok
[11:48] <raphink> :)
[02:19] <Gloubiboulga> I have 2 packages on REVU advocated once, could someone have a look at them ?
[02:19] <Gloubiboulga> it's http://revu.tauware.de/details.py?upid=1654 and http://revu.tauware.de/details.py?upid=1650
[03:19] <pabs3> anyone seen Mez? if someone does, can you ping him about his debian ifolder ITP?
[03:21] <Tonio_> hi
[03:59] <apachelogger> is it allowed to patch binary format files into a packge (eg pictures)?
[04:01] <\sh> apachelogger: how are you doing this? you can do it via uuencode/uudecode (sharutils)
[04:01] <apachelogger> made a diff ;-)
[04:01] <apachelogger> so how to do it via uuencode?
[04:03] <\sh> apachelogger: since when is diff doing binary diffs? you can't inject binaries into a source tarball..the only way to do this, is to uuencode the picture (e.g. an icon) move it to debian/dir and uudecode it and install it via debian/rules install target
[04:04] <apachelogger> well, the diff worked somehow ... but wasn't very smart ... I'll take a look at uuencode and uudecode, thx :)
[04:05] <jpatrick> apachelogger: you could try .xpm's
[04:06] <apachelogger> hm
[04:06] <apachelogger> I think kblogger 0.4 will just not have a image, the author might have a reason to not include it
[04:25] <Kyral> Morning MOTUish people
[04:25] <apacheLAGger> morning
[04:26] <jpatrick> Kyral: afternoon
[04:28] <apacheLAGger> so there is still a really anoying problem: http://paste.ubuntu-nl.org/7994
[04:30] <apacheLAGger> any ideas?
[04:31] <\sh> yes
[04:31] <\sh> 1. if this lib is not used by anything else, lintian-override it :)
[04:31] <\sh> 2. if this lib is used by anything else then kblogger, write shlibs file
[04:32] <apacheLAGger> just used by kblogger ...  so I shouldn't care about that error?
[04:33] <\sh> apacheLAGger: lintian-override it :)
[04:33] <apacheLAGger> ok, thx :D
[04:33] <\sh> apacheLAGger: you know how to do it?
[04:34] <apacheLAGger> not really .... but learning buy doing and googling ;-)
[04:37] <\sh> apacheLAGger: lynx file:/usr/share/doc/lintian/lintian.html/index.html :)
[04:37] <apacheLAGger> http://lintian.debian.org/manual/ch2.html#s2.4
[05:24] <apacheLAGger> \sh: http://revu.tauware.de/details.py?upid=1656 :)
[05:26] <dholbach> no need to lintian-override - it's a good reminder to not override it and see the message every time (and split it out once it's needed somewhere)
[05:27] <apacheLAGger> dholbach: but why would it be needed?
[05:28] <dholbach> the lintian-override is surely not needed.
[05:28] <dholbach> Or do you mean the library?
[05:28] <\sh> dholbach: it will never be needed
[05:28] <\sh> dholbach: the library
[05:28] <apacheLAGger> that was my point
[05:28] <dholbach> "never"
[05:29] <\sh> dholbach: it's a typical "local lib of kde apps"
[05:29] <dholbach> You often see that libraries which are splitted out of "applications" are used at some stage.
[05:29] <dholbach> Think of beagle.
[05:29] <dholbach> I don't say "split it out now!"
[05:30] <\sh> I wonder what inside this lib anyways...
[05:31] <\sh> lemme have a look
[05:32] <dholbach> Ask fabbione on his take on this.
[05:32] <Simira> hey! I wanna become a MOTU!
[05:33] <\sh> apacheLAGger: it's only the panel applet of kblogger?
[05:33] <Simira> at least as a start to becoming a dev
[05:33] <ogra> Simira, yay
[05:33] <apacheLAGger> \sh: kblogger is the applet
[05:34] <apacheLAGger> http://kde-apps.org/content/show.php?content=29552
[05:34] <apacheLAGger> the whole app is just an applet
[05:34] <\sh> jesus
[05:34] <apacheLAGger> lol
[05:35] <Simira> ogra: hey, wanna help me make a small application? Tollef rather wants to have a bath...
[05:35] <ogra> Simira, hmm, still particulary busy here ....
[05:36] <Simira> ogra: right. I'll have to wait until tomorrow evening then. Are you still working on the rollout?
[05:39] <ogra> i only work on ltsp ... the LP guys do the rollout ...
[05:39] <ogra> #
[05:40] <\sh> ogra: is elmo with the LP guys?
[05:40] <ogra> yup
[05:44] <\sh> going out for a while...laters
[07:34] <apachelogger> raphink: ping
[07:35] <raphink> hi apachelogger
[07:35] <apachelogger> hey ...I'm the kblogger guy... :)
[07:35] <raphink> ok
[07:35] <raphink> :)
[07:35] <apachelogger> raphink: http://revu.tauware.de/details.py?upid=1657 what does the kblogger 0.3 tarball do in the list?
[07:36] <apachelogger> actually the orig.tar.gz should be exactly the 0.4 from kde-apps, cause I repacked it today
[07:36] <raphink> ooops
[07:36] <raphink> right should be 0.4
[07:36] <apachelogger> ;-)
[07:36] <raphink> ok good sorry
[07:36] <apachelogger> no problem
[07:37] <raphink> give me the url of the 0.4 package please
[07:37] <raphink> and I'll run it again
[07:37] <apachelogger> http://whiletaker.homeip.net/~christian/kblogger-0.4.tar.bz2
[07:38] <raphink> thanks
[07:40] <raphink> apachelogger: waita  min ok?
[07:48] <apacheLAGger> raphink: looks better, doesn't it?
[07:48] <raphink> wait a min
[07:49] <apacheLAGger> yup
[07:49] <raphink> I'm doing lots of thigns
[07:49] <raphink> there's still the debuild test I'm not very happy with apachelogger, have a looka t it please
[08:02] <raphink> apachelogger: ok?
[08:02] <apachelogger> raphink: new verison online
[08:02] <raphink> ok
[08:03] <apachelogger> add a unpatch rule
[08:03] <raphink> I'l lhave a look
[08:03] <apachelogger> s/add/added ;-)
[08:04] <raphink> running the test, let's wait till it builds :)
[08:04] <raphink> I'll brb
[08:09] <raphink> looks good now apachelogger, good job... :)
[08:09] <raphink> I'll look at it after my dinner
[08:09] <apachelogger> thx :)
[08:10] <raphink> apachelogger: do you know of the Reviewing guideon the wiki?
[08:10] <apachelogger> nope
[08:10] <raphink> http://wiki.ubuntu.com/MOTU/Packages/Reviewing
[08:10] <raphink> main points to check in a package
[08:11] <raphink> so you can check it yourself :)
[08:11] <apachelogger> ok :)
[09:57] <phanatic> hi people
[11:06] <sebest__> hello, is the login pass on revu the same as launchpad?
[11:09] <minghua> sebest: no
[11:09] <hub> sebest__: no
[11:10] <sebest__> how to get a login?
[11:12] <hub> https://wiki.ubuntu.com/MOTU/Packages/REVU?action=show
[11:14] <sebest__> thanx
[11:45] <LaserJock> hi Hobbsee
[11:45] <Hobbsee> hey LaserJock
[11:46] <LaserJock> how's it going?
[11:48] <Hobbsee> just finished building koffice for Riddell
[11:49] <LaserJock> sweet
[11:51] <Hobbsee> for dapper
[11:53] <raphink> cool :)
[11:55] <Hobbsee> yeah