[12:02] <ajmitch> libnotify-dev is in main, actually
[12:02] <ajmitch> and you might want to file a bug on it
[12:03] <Des_MM> ajmitch, Yes, I do, but I also wanted to submit a patch with the bug
[12:25] <LaserJock> hi bmonty
[12:25] <bmonty> hey LaserJock
[12:26] <LaserJock> bmonty: how's the little one?
[12:31] <Kyral> Back to work
[12:36] <bmonty> LaserJock: sorry, got distracted....the baby has a cold this week
[12:36] <bmonty> I'm finally getting LDAP/Kerberos single sign on to work on my network :)
[12:36] <LaserJock> bmonty: how old is he?
[12:37] <bmonty> LaserJock: he is almost 3 months old now
[12:38] <LaserJock> bmonty: well, he better get over his cold before UVF ;-)
[12:38] <LaserJock> bmonty: cause he'll start doing bug fixes before you know it
[12:39] <bmonty> heh, yeah I've already showed him dpkg :)
[12:39] <LaserJock> lol
[12:40] <bmonty> unfortunately he was more interested in sucking on his fist, so I don't think he will be up to speed to help out on dapper :(
[12:41] <dholbach> good night everybody.
[12:41] <ajmitch> night dholbach
[12:41] <lfittl> gn8 dholbach
[12:41] <LaserJock> bmonty: hmm, I guess you could have him join in on debian-devel. He should fit in over there (just kidding of course)
[12:41] <dholbach> bye lfittl, ajmitch
[12:41] <LaserJock> cy dholbach
[12:41] <LaserJock> cya I mean
[12:41] <dholbach> bye LaserJock
[12:42] <bmonty> bya dholbach
[12:42] <dholbach> bye bmonty
[12:45] <Kyral> C...ick
[12:45] <Kyral> damn Printf
[12:46] <Kyral> Why people don't use C++ is beyond me...
[12:46] <ajmitch> because c++ is nasty & evil
[12:46] <tseng> damn right
[12:46] <tseng> puts for life
[12:49] <Kyral> No I'm cursing at printf :P
[12:50] <LaserJock> hmm, I find for me the problem is hardly ever in the programming language but the one using it
[12:56] <Kyral> lol
[12:56] <Kyral> I <3 Python
[01:20] <Kyral> Malone 5777
[01:20] <Ubugtu> Malone bug 5777: "gpsim not installable in Dapper" Fix req. for: gpsim (Ubuntu), Severity: Normal, Assigned to: MOTU, Status: Confirmed http://launchpad.net/bugs/5777
[01:20] <Kyral> I can fix it...
[01:21] <ajmitch> then do so..
[01:22] <lfittl> Kyral: I started working on that, but you can do it if you want ;)
[01:23] <Kyral> ajmitch: I'm at a text console lol
[01:24] <Kyral> lfittl: It should be easy as changing a dep
[01:24] <ajmitch> Kyral: so?
[01:24] <Kyral> meh
[01:24] <lfittl> Kyral: sure but there is also a new upstream version :)
[01:24] <Kyral> lfittl: for gpsim?
[01:25] <lfittl> Kyral: yep (http://sourceforge.net/project/showfiles.php?group_id=2341)
[01:31] <Kyral> okay
[01:31] <Kyral> I'll diff it
[01:39] <azion> Hey all, was wondering if there's any help need at the moment?
[01:40] <LaserJock> azion: lol there is always help needed
[01:41] <azion> Sorry the stupid question, just wondering how abouts I go helping with motu
[01:41] <LaserJock> no, it's not a stupid question
[01:41] <LaserJock> it's just right now there is actually a lot going on because we have a deadline tomorrow
[01:41] <sistpoty> hi folks
[01:41] <azion> Ah for what?
[01:42] <azion> Hi sistpoty
[01:42] <LaserJock> upstream version freeze
[01:42] <azion> I see
[01:47] <sistpoty> did anyone request scapy sync yet?
[01:47] <azion> Ye've finished the main branch?
[01:47] <azion> Or is bug fixes?
[01:47] <LaserJock> well, we are trying to get everything merged/synced from Debian unstable
[01:47] <azion> Though job
[01:47] <azion> *Tough job
[01:47] <azion> LaserJock, How can I go about helping with MOTU?
[01:47] <siretart> hey sistpoty
[01:47] <sistpoty> huhu siretart
[01:47] <siretart> sistpoty: how are you? are you feeling better?
[01:47] <LaserJock> azion: well have you seen the MOTU wiki page : wiki.ubuntu.com/MOTU ?
[01:47] <tseng> azion: start by reading the topic
[01:47] <ajmitch> hi siretart, sistpoty, hub, et al :)
[01:47] <sistpoty> siretart: still a little bit ill, but much better already :)
[01:47] <siretart> hi ajmitch
[01:47] <azion> LaserJock, Ya have it infront of me
[01:47] <hub> hi
[01:47] <siretart> sistpoty: I'm happy to hear that :)
[01:47] <sistpoty> hi ajmitch
[01:47] <sistpoty> hi hub
[01:48] <LaserJock> azion: do you have any packaging experience?
[01:48] <siretart> sistpoty: tomorrow 1400?
[01:48] <sistpoty> siretart: I'll be there ;)
[01:48] <siretart> same here :)
[01:48] <azion> LaserJock, Only learning now really
[01:48] <siretart> but I need some sleep now. gn8 folks!
[01:48] <sistpoty> gn8 siretart
[01:48] <lfittl> gn8 siretart
[01:50] <LaserJock> azion: ok, then maybe you could look at MOTUBugFixing and DeveloperResources
[01:51] <azion> LaserJock, Afraid haven't had any bug so far with Ubuntu. lol! Good thing!
[01:52] <LaserJock> azion: well, then start fixing the ones other people have found ;-)
[01:52] <azion> LaserJock, I would be interested in doing Developer Resources
[01:52] <LaserJock> azion: just hanging out here for a while will help
[01:53] <azion> LaserJock, Okay
[01:54] <azion> LaserJock, Cheers
[01:58] <azion> Is Azureus going to be included in Ubuntu?
[01:59] <crimsun> doubtful. Does it run with gcj?
[02:00] <azion> Not sure, have to check it out
[02:06] <whiprush> someone from fedora blogged about how they just got it working with gcj
[02:10] <azion> Must have a looksie
[02:14] <sistpoty> anyone have a clue what's going on with gl/glu header packages? seems the one listed in motuglutransition point to x11-proto-gl
[02:15] <sistpoty> hm... just found libgl1-mesa-swrast-dev which seems to do the trick... strange
[02:19] <sistpoty> nope, fails when linking... I guess s.th. with the gl/glu-stuff is broken atm
[02:23] <azion> The forums down?
[02:24] <ajmitch> they could be, I guess
[02:24] <azion> Can't get in
[02:25] <azion> Could be just busy too I guess
[04:48] <lfittl> hub: New upload: http://revu.tauware.de/details.py?upid=1545
[04:48] <hub> i saw
[04:53] <sistpoty> hi minghua
[04:53] <minghua> hi sistpoty
[04:53] <minghua> are we in UVF already?
[04:53] <ogra> nope, tomorrow
[04:53] <ogra> or rather "in some hours"
[04:54] <sistpoty> hehe
[04:54] <minghua> I remember something like "one week grade period for universe packages that don't require new dependencies", is that true?
[04:55] <minghua> I am thinking what to do with my scim packages
[04:55] <minghua> I have them ready now, but I need to wait for my sponsor
[04:55] <minghua> if there is no grace period, should I try to get them uploaded today?
[04:55] <ogra> i'd say yes
[04:55] <sistpoty> minghua: that would be new to me... I only know of a later date for merges to be finished (that are still on the list)
[04:56] <lfittl> hub: You finished with reviewing? :)
[04:56] <minghua> okay, in that case, I should repackage the source as -0ubuntuX version, right?
[04:56] <hub> nope
[04:56] <ogra> minghua, if they're ready, get them in
[04:56] <hub> sorry I was doing something else
[04:57] <hub> done
[04:57] <minghua> ogra: can you sponsor?  I think I can get the repackaging done in half an hour.
[04:57] <lfittl> hub: thanks :)
[04:58] <ogra> i cant sponsor debian stuff minghua
[04:58] <minghua> ogra: I mean sponsoring ubuntu stuff, I am not MOTU yet
[04:58] <minghua> what is the MOTU term for that... upload?
[04:58] <ogra> minghua, oh, surem but not tonight anymore, send me a mail (ogra@ubuntu.com)
[04:59] <ogra> (its 5am here, my GF kills me if i dont come to bed now)
[04:59] <minghua> any other MOTU willing to upload two universe package for me?  otherwise I'll wait for ogra
[04:59] <minghua> ogra: sure, go to bed, hurry :-)
[05:00] <ogra> minghua, nah, i'll finish my glass of wine :)
[05:00] <sistpoty> minghua: sorry, I should have been in bed for a long time already... (same TZ as ogra)... so I can't promise right now
[05:00] <sistpoty> hehe
[05:00] <lfittl> I'm off to bed now (also 5am here..), gn8 all
[05:01] <sistpoty> gn8 lfittl
[05:01] <minghua> sweet dreams, european MOTUs :-)
[05:01] <lfittl> thanks :)
[05:02] <azion> Ng
[05:02] <azion> Night
[05:02] <sistpoty> gn8 azion
[05:02] <azion> Im not gone yet
[05:03] <sistpoty> oh... sleepiness in my brain already ;)
[05:03] <azion> sistpoty,Do u have MSN or anything
[05:04] <sistpoty> azion: nope... I used to be on icq, but now I almost exclusively use irc
[05:04] <hub> azion: use jabber :-)
[05:04] <azion> sistpoty, Arr ok, whats that?
[05:05] <hub> azion: icq?
[05:05] <azion> sistpoty, Ah IM
[05:05] <sistpoty> yep
[05:05] <azion> sistpoty, You have ICQ?
[05:05] <sistpoty> azion: had... I didn't launch it for half a year now...
[05:06] <hub> azion: what's wrong with IRC?
[05:06] <azion> sistpoty, What time will you be on tomorrow at?
[05:06] <LaserJock> minghua: you around?
[05:06] <minghua> Hmm...
[05:06] <minghua> LaserJock: yeah
[05:06] <LaserJock> minghua: I was just reading your -motu email
[05:06] <marcin> hello guys
[05:06] <azion> Hey
[05:06] <sistpoty> azion: don't know yet, if I'll be on... probably later in the evening (23 utc) or so
[05:06] <azion> sistpoty, What time will you be on tomorrow at
[05:07] <azion> sistpoty, Ah, Im in GMT, got email?
[05:07] <marcin> I want to send signed mail to revu - asking to add me to keyring
[05:07] <minghua> LaserJock: any comments?
[05:07] <LaserJock> minghua: how do we keep in good communication with Debian, I mean we touch a lot of packages so we would have to talk to a lot of DDs
[05:07] <marcin> and howto says that I should send my GNUPg KeyID in this mail...
[05:07] <sistpoty> azion: gmt, yes, but that's just a rough guess... and didn't get email yet
[05:07] <marcin> could someone tell me what is exactly this gnupg KeyID?
[05:08] <azion> sistpoty, So how do I contact you, lol!!!
[05:08] <marcin> real name + comment + mail address?
[05:08] <sistpoty> azion: stay around in -motu... and I'm not the only helpful motu ;)
[05:09] <azion> sistpoty, True, just I need to be spoon fed this stuff
[05:09] <ogra> minghua, as i said above, i disagee, if we have introduced a package,m why should we ask the debian maintainer before putting new stuff up ?
[05:10] <psusi> anyone know of a debian-installer guru?  I'm trying to udebify the dmraid package and integrate it into the setup cd
[05:10] <marcin> hello guys - can someone help me with this gpg stuff?
[05:10] <minghua> LaserJock: I personally would (1) let the Debian maintainer know that we are modifying his/her package (2) let him/her know if we have non-ubuntu-specific changes
[05:10] <ogra> minghua, i'm upstream for ltsp and ltspfs as well as ltspfsd for debian ... i wont ask them if i adopt new stuff from upstream
[05:10] <sistpoty> marcin: maybe that'll explain what gnupg is better than I can: http://www.gnupg.org/(en)/documentation/faqs.html
[05:11] <marcin> sistpoty: got this manual in another window
[05:11] <minghua> ogra: are you talking about packages already in debian or packages that get into ubuntu first then merged into debian?
[05:11] <marcin> sistpoty: but I'm just not sure what KeyID should I send to REVU
[05:11] <ogra> minghua, i talk  about packages where ubuntu is upstream
[05:11] <sistpoty> marcin: the one with which you sign emails
[05:12] <marcin> sistpoty: because it can be just few letters and numbers I get after gpg --list-keys
[05:12] <ogra> minghua, and imho debian should accept us as such
[05:12] <minghua> ogra: then of course you don't need to :-)
[05:12] <azion> Ok, guys, I'm off. Thanks for all your help, talk to ye tomorrow
[05:12] <marcin> sistpoty: or it can be name+comment+mail
[05:12] <ogra> minghua, and imho that applies to all 0ubun tu1 packages
[05:12] <sistpoty> marcin: basically you don't explicitely need to state the gpg-id, just sign the message with it
[05:12] <minghua> ogra: in that case I think it's the debian maintainer's responsibility to keep the communication
[05:12] <marcin> sistpoty: ok thanks - sending
[05:13] <minghua> ogra: I disagree (the apply to all 0ubuntuX part)
[05:13] <ogra> minghua, we communicate very well .... but it think its important that debian also accepts that there are packages where *we* are upstream
[05:13] <ogra> minghua, why ?
[05:13] <minghua> ogra: I don't want to make a big fuss about it, but when I wrote the mail I was thinking of my own debian packages
[05:14] <minghua> my scim packages got uploaded as -0ubuntu1 in dapper twice, neither of them has a prior notice to me
[05:14] <ogra> minghua, sure, but 0ubuntuX packages *are* not in debian ... why shouldnt *we* be upstream for *them* ?
[05:14] <minghua> I didn't even know the ubuntu uploader was planning to do that
[05:15] <minghua> and I actaully explicitly expressed that I "will try to take care of the packages in ubuntu" on ubuntu-devel
[05:15] <ogra> yes, thats bad ... in case a package exists in debian, debian is indeed the upstream
[05:15] <minghua> and in the second case, there should be some documentation change/warning when packaging the new upstream version
[05:16] <minghua> ogra: yeah, then we more or less agree
[05:16] <ogra> but for 0ubuntuX packages that really deserve that versioning, i see no reason why we shouldnt be upstream
[05:16] <ogra> for ltsp debian accepted that so this far, that they put a XdebianX version up ;)
[05:17] <minghua> ogra: my point was that, as MOTU we shouldn't upload a new upstream version without a wishlist bug in debian just because the debian maintainer hasn't get to it yet
[05:17] <minghua> unless we are quite confident about the packaging ourselves
[05:17] <ogra> for existing packages i totally agree
[05:17] <ogra> for new packages i dont ...
[05:17] <minghua> in my case, if the ubuntu upload had asked, I can at least give him a patch that fix an important typo
[05:18] <ogra> simply because i expext to be respected as a distro from debian
[05:18] <ogra> *expect
[05:18] <minghua> ogra: I haven't thought about new packages carefully yet, but my mail mainly refer to packages already in debian (in your words, MOTU being downstream)
[05:18] <ogra> yup
[05:19] <ogra> as i said, there i totally agree
[05:19] <minghua> great to clear all these up :-)
[05:19] <ogra> :)
[05:19] <minghua> I'll probably follow up in list for more clarification
[05:21] <sistpoty> minghua: take in account that ubuntu development goes a little bit other than debian. In the early phase usually the repo get's broken pretty hard, so I guess at that time waiting for response from DD wouldn't need to be necessary
[05:21] <minghua> sistpoty: my personal opinion is "we should at least try"
[05:21] <sistpoty> minghua: however the DD should be notified in all cases... that's at least what I think ;)
[05:22] <minghua> sistpoty: a mail to the debian maintainer definitely won't hurt
[05:22] <minghua> sistpoty: exactly, if the DD won't reply our notification mail, it's him/her not willing to communicate, not us :-)
[05:23] <sistpoty> :)
[05:23] <minghua> and I think Lucas's point on the "new upstream" wishlist bug is quite good
[05:23] <sistpoty> yes, it is
[05:27] <minghua> can I ask for sync from incoming?
[05:27] <minghua> my scim package just got uploaded by my sponsor :-)
[05:28] <LaserJock> sorry, was away for a second. So what about bugs? How do we communicate with Debian about bugs?
[05:29] <LaserJock> whenever we get a bug that isn't Ubuntu specific what should we do?
[05:29] <sistpoty> minghua: don't know... maybe ask elmo about it?
[05:29] <sistpoty> LaserJock: if I can fix it, I do and report it back to BTS with patch
[05:30] <minghua> LaserJock: I would first ask if the debian maintainer to subscribe to said package in manlone
[05:30] <LaserJock> seems like we have to do the work of 2 distros :(
[05:31] <minghua> LaserJock: if he is not willing to (maybe because the change in ubuntu is too large), I'll ask him if it's okay for me to forward the bug to debian BTS if I _think_ it applys to debian as well
[05:31] <LaserJock> but I guess we get a lot of packaging from Debian so it evens out
[05:31] <minghua> LaserJock: if he is still not happy, I'll have to try to reproduce the bug in debian and then report
[05:32] <minghua> LaserJock: an important point is that the Debian maintainer may know better than we do about the package
[05:32] <minghua> LaserJock: and as I've been saying these are my personal opinions
[05:33] <LaserJock> but I think we could literally spend all MOTU time just communicating with Debian, or is it not that bad?
[05:35] <LaserJock> minghua: I agree with what your saying, I'm just trying to figure out how I can do it in a pratical and effective way
[05:35] <sistpoty> LaserJock: we could spend all motu-time with merging, if we didn't communicate back to debian
[05:36] <LaserJock> sistpoty: true, true
[05:36] <LaserJock> we do spend a lot of effort merging
[05:38] <LaserJock> I'm just wondering if we can create some tools to help
[05:39] <LaserJock> something like a button in Malone to send an email to BTS or at least a template for common things
[05:41] <LaserJock> at this point I'm a bit overwhelmed and shell shocked by Debian so anything to make it easier would be nice ;-)
[05:44] <sistpoty> LaserJock: with an unstable chroot, you can just use reportbug (I guess I'm faster with it, since I'm used to shell)
[05:45] <minghua> not to mention reportbug adds ton of useful information for debugging as well :-)
[05:46] <sistpoty> that's what I really dislike from malone... not even the version of the package installed
[05:46] <LaserJock> I used reportbug to do an ITP the other day :-)
[05:46] <LaserJock> but I had to get exim4 installed first
[05:47] <Kyral> Emacs has an ITP Mode lol
[05:47] <LaserJock> sistpoty: do I need to be in a sid chroot for reportbug? I used dapper but sent it to Debian
[05:48] <minghua> LaserJock: use "reportbug -f file" then post it into your email client
[05:48] <sistpoty> LaserJock: didn't look at the changes of reportbug... and I only have unstable around (even a real system, that I use for chroot)
[05:48] <LaserJock> anyway, something in Malone would be nice because that is where the Ubuntu bug info is
[05:48] <minghua> LaserJock: for ITP it's okay, but probably not good for a real bug
[05:48] <LaserJock> oh, that makes sense
[05:49] <LaserJock> it sense system info doesn't it
[05:53] <LaserJock> ok, so does anybody know what "Request fix: + Upstream + In Distribution" are for?
[05:58] <LaserJock> gotta go, cya MOTU
[05:58] <sistpoty> cya LaserJock
[05:58] <sistpoty> gn8 everyone
[05:58] <LaserJock_away> cy sistpoty
[05:58] <LaserJock_away> cya I mean
[06:25] <Kyral> The HURD is in Ubuntu now?
[07:19] <bur[n] er> anyone know where to report a bug about the gnome run dialog?
[07:23] <Gloubiboulga> hub, ping
[07:25] <Gloubiboulga> bur[n] er, have a look at https://launchpad.net/malone
[07:25] <bur[n] er> yeah, but know what package the run dialog is part of?
[07:27] <Gloubiboulga> I don't know
[07:28] <minghua> bur[n] er: by "run dialog", do you mean the one that pops out when you press alt-F2?
[07:31] <bur[n] er> yeah
[07:31] <bur[n] er> or "doesn't" ;)
[07:31] <bur[n] er> hence my bug
[07:31] <bur[n] er> (it stays behind any open windows for some odd reason)
[07:32] <minghua> bur[n] er: then gnome-panel, I believe
[07:32] <bur[n] er> danke
[07:32] <minghua> I am not positive, but even if it's wrong, I don't think the maintainer will be unhappy
[07:33] <minghua> should be close enough
[07:34] <bur[n] er> that would make sense, that was one of the new packages I received today
[07:48] <viviersf> mornin
[07:48] <viviersf> yo @ ajmitch
[07:49] <raphink> hub: don't get your comment on http://revu.tauware.de/details.py?upid=1482 ... There's no orig.tar.gz . How then did you review the package?
[07:49] <raphink> hi viviersf
[07:50] <viviersf> lo
[07:53] <ajmitch> hi viviersf
[07:53] <raphink> hi ajmitch
[07:53] <ajmitch> hello raphink
[08:29] <raphink> ajmitch: could you give me your opinion on this package ? http://revu.tauware.de/details.py?upid=1545
[08:29] <raphink> if you think my remark is correct or not?
[09:00] <tepsipakki> I still can't login to REVU, although I can decrypt the recover-message, duh
[09:08] <raphink> tepsipakki: ping a REVU admin
[09:23] <dholbach> good morning
[09:23] <tepsipakki> ok, any revu-admins around?-)
[09:24] <Gloubiboulga> morning dholbach
[09:24] <dholbach> hey Gloubiboulga
[09:39] <raphink> hi dholbach && Gloubiboulga
[09:39] <dholbach> hellas raphink
[09:39] <raphink> dholbach: could you give me your opinion on http://revu.tauware.de/details.py?upid=1545 please?
[09:39] <Gloubiboulga> hello raphink
[09:39] <raphink> dholbach: it's not a review, just an opinion on the status of the package
[09:41] <dholbach> I personally don't like patchsets in the orig.tarball.
[09:42] <raphink> dholbach: it's mostly about the merging stuff actually
[09:42] <dholbach> It's a maintainer decision to ship patches or not, so if there'd be a bunch of patches in debian/patches (however big they are) and people are notified that it's the Nicotine DA version (or whatever), I'm fine with it.
[09:42] <raphink> I'm worried we have to carry around such a huge patch
[09:43] <raphink> well dholbach then it should be a new package
[09:43] <raphink> and should not use the existing changelog I guess
[09:43] <dholbach> If the package uses a nice build/patch system, that's 'easy' to do.
[09:43] <dholbach> If it improves the package...
[09:45] <raphink> hmmm
[09:47] <raphink> dholbach: I found some packages that were advocated twice a long time ago and never uploaded
[09:47] <raphink> could you check them?
[09:47] <dholbach> I'd prefer if somebody else could do this.
[09:47] <raphink> I checked there is no newer version available, so they are ready to go but I havn't got upload rights yet
[09:47] <dholbach> I'm *very* busy.
[09:47] <raphink> hmm ok
[09:47] <raphink> sorry then :)
[09:47] <dholbach> Don't worry.
[09:47] <dholbach> If it's urgent, I can do it.
[09:48] <raphink> well it's not urgent, but these packages have been advocated months ago for some of them
[09:48] <raphink> http://revu.tauware.de/details.py?upid=1258 this one was ready to go before xmas
[09:49] <raphink> and this one aswell http://revu.tauware.de/details.py?upid=1238
[09:50] <dholbach> and they did not just ftbfs?
[09:50] <raphink> hmmm
[09:51] <raphink> where shall I check ? :s
[09:51] <raphink> I don't remember the url to the buildd logs
[09:51] <dholbach> http://people.ubuntu.com/~lamont/buildLogs/
[09:52] <raphink> ty
[09:53] <raphink> there's no entry in the build logs for these packages :s
[09:53] <dholbach> Ok.
[09:53] <dholbach> then it's up to elmo to ask him, if he maybe rejected them because of one reason or the other
[09:53] <raphink> pretty normal since they were not uploaded
[09:53] <raphink> I can check if they build on a pbuilder now
[09:53] <raphink> dholbach: I think they were not uploaded, at all
[09:53] <raphink> from REVU
[09:54] <raphink> the comments say : ok twice
[09:54] <raphink> but not uploaded
[09:54] <dholbach> Hm.
[09:56] <\sh> moins
[09:56] <raphink> hi \sh
[09:57] <raphink> dholbach: checking if they FTBFS or not
[10:09] <\sh> oh well..some problems are resolving magically
[10:10] <\sh> from a company employee to a freelancer in less then one month..
[10:13] <ajmitch> \sh: you have some work now?
[10:14] <\sh> ajmitch: not really I'll do some monitoring and sysadmin job for a company as freelancer. A friend who is doing that normally can't right now, because he has troubles with his other company, and he and I worked before that for ISH...so I step in, and earn some money for some weeks
[10:15] <\sh> ajmitch: yeah..I'm just waiting for some syncs as wlel
[10:16] <ajmitch> about a week I've been waiting now
[10:20] <ajmitch> went over my traffic allowance
[10:39] <ajmitch> sigh, 116 merge bugs still open
[10:40] <ajmitch> ls -alrt
[10:40] <ajmitch> EWIN
[10:40] <ajmitch> :)
[10:41] <\sh> dholbach: don't merge wesnoth 1.1-2, I beg you not to do it :)
[10:41] <ajmitch> sigh
[10:41] <ajmitch>  zope-extfile_1.4.4-1ubuntu1_source.changes REJECTED
[10:41] <dholbach> \sh: It's not assigned to me, I won't do it - I have enough to do atm.
[10:42] <\sh> dholbach:
[10:42] <\sh> wesnoth  daniel.holbach@ubuntu.com  ASSIGNED
[10:42] <\sh> whysoever :)
[10:43] <ajmitch> it's probably a mistake
[10:43] <\sh> yes but I'm careful :)
[10:43] <dholbach> \sh: https://launchpad.net/distros/ubuntu/+source/wesnoth/+bug/6559
[10:43] <Ubugtu> Malone bug 6559: "wesnoth: merge new debian version" Fix req. for: wesnoth (Ubuntu), Severity: Normal, Assigned to: Stephan Hermann, Status: Unconfirmed
[10:43] <\sh> bah....sistpoty :)
[10:44] <\sh> dholbach: and yes I know the bug :)
[10:44] <ajmitch> hm, last released in 2003
[10:45] <siretart> hi folks
[10:45] <siretart> any news about syncs?
[10:45] <dholbach> \sh: It's assigned to you, man.
[10:46] <ajmitch> siretart: none at all
[10:46] <\sh> dholbach: I know the bug is assigned to me, I just was suprised that the list had your name :)
[10:46] <siretart> ajmitch: I've seen one from infinity yesterday
[10:46] <ajmitch> siretart: was it really a sync?
[10:46] <ajmitch> it might have been done on the spot
[10:46] <ajmitch> as elmo has done that for me before
[10:47] <siretart> it looked like the sync
[10:47] <ajmitch> php4, looks synced
[10:47] <ajmitch> unless he faked it :)
[10:47] <siretart> but mdz mentioned the last tb meeting we will be on soyuz next week anyway...
[10:47] <lifeless> opensync is getting close to top
[10:47] <lifeless> :[
[10:47] <ajmitch> yes but we don't know if that changes sync processes
[10:47] <siretart> .. perhaps thats why elmo has no time to do it. but thats just a guess :(
[10:48] <ajmitch> lifeless: we can probably get it in - new packages can still get in universe until feature freeze
[10:48] <ajmitch> I hope
[10:48] <lifeless> heh
[10:48] <siretart> I hope that results that we can request syncs directly. but thats just a hope
[10:48] <ajmitch> siretart: probably not, to start with
[10:48] <ajmitch> oh good
[10:48] <ajmitch> my upload to debian yesterday is on the autosync list
[10:49] <ajmitch> no sign of zope3 being synced
[10:50] <siretart> perhaps anyone should raise this topic on #ubuntu-devel, but I'm too busy atm with work
[11:09] <ajmitch> sigh, why does this install into /usr/lib/zope/Products?
[11:09] <ajmitch> broken thing
[11:17] <ajmitch> my bad, not broken, the package has .so files in it
[11:21] <ogra> if you need it broken, just break it :P
[02:26] <marcin`> hi MOTU
[02:27] <marcin`> got a problem - I'm propably just dumb... but... could someone help me anyway?
[02:27] <marcin`> I got gpg key that I sent to REVU
[02:27] <marcin`> and it's accepted so I got mail that I can upload my packages to REVU
[02:27] <marcin`> I also got package in pbuilder/results directory
[02:28] <marcin`> and I would like to upload it's *.changes file to REVU
[02:28] <marcin`> the problem is that it says that my package is not signed
[02:29] <marcin`> could someone help me and tell how to sign *.changes file?
[02:29] <\sh> marcin`: only source uploads :) so *_sources.changes has to be used for dput
[02:29] <lfittl> marcin`: Create a source package by using dpkg-buildpackage -S -sa -rfakeroot
[02:29] <\sh> or just shortways debuild -S -sa
[02:30] <marcin`> and the same thing but with pbuilder?
[02:31] <marcin`> pbuilder --debbuildopts '-S -sa' is ok?
[02:31] <Nafallo> nope, but pbuilder does something like that before it starts working inside the chroot.
[02:31] <lfittl> source packages are created without pbuilder, simply execute the above command in the directory where you normally call pbuilder
[02:34] <marcin`> lfittl: hmm right...
[02:34] <marcin`> lfittl: so anyway I hope that there will be no problem that I use breezy and want to build source packages for dapper
[02:35] <Nafallo> and then debsign *_sources.changes before dput-ing them :-)
[02:35] <lfittl> marcin`: as long as you test them in your dapper pbuilder, that should be no problem
[02:35] <marcin`> Nafallo: woooow finally :)
[02:35] <marcin`> Nafallo: thanks - now I know how to sign this stuf... that should be in wiki or something...
[02:36] <Nafallo> well, I have pbuilder sign my stuff automagically ;-)
[02:36] <lfittl> marcin`: Feel free to add it ;)
[02:45] <marcin`> ehh troubles troubles troubles...
[02:45] <marcin`> what should I do when dpkg-buildpackage says that
[02:45] <marcin`> gpg: [stdin] : clearsign failed: secret key not available
[02:45] <marcin`> ?
[02:47] <tepsipakki> you are fakeroot?
[02:47] <Nafallo> see to that the e-mailaddress you use in the changelog is a uid of your gpg-key.
[02:47] <\sh> marcin`: then you have a problem with your key or the uid in the changelog doesn't match the uid of you gpg key
[02:48] <marcin`> and uid is my name + mail?
[02:48] <tepsipakki> ah, I remember seeing that myself, and the reason was the email
[02:57] <Tonio_> hum I saw in some Riddell's REVUs that some tarball have a lot (while not all) executable files....
[02:57] <Tonio_> what would you do ? rebuild tarball, cdbs patch or a series of chmod in the rules file ?
[03:09] <raphink> sorry Riddell I didn't really check if the files chmod had been checked before advocating again, my fault ;)
[03:09] <raphink> s/checked/changed/
[03:55] <azion> Hey all
[03:56] <zakame> hi azion
[03:57] <azion> How do I submit an updated package version
[03:59] <Kyral> morning MOTU
[04:00] <zakame> heya Kyral :)
[04:00] <zakame> and mhz :)
[04:00] <mhz> hey all
[04:01] <zakame> azion: hmm, you mean a new version of a package, or a request for updating a package to a new version?
[04:01] <zakame> heya ajmitch_
[04:02] <azion> zakame, Either, new version of aMSN is out
[04:02] <Kyral> Is it in Debian?
[04:02] <\sh> it's uvf
[04:04] <zakame> azion: ah... well, its UpstreamVersionFreeze time, so unless there are critical fixes (like security ones) I don't think we'll be able to push that in dapper now :(
[04:04] <Hieronymus> azion: it was synced
[04:04] <Hieronymus> or well, that was requested..
[04:04] <azion> Sweet, cool
[04:04] <azion> Yer doing uvf today, eight?
[04:04] <azion> Yer doing uvf today, right?
[04:05] <Kyral> So...what does X11R7 bring...
[04:06] <ogra> a shiny new version number at least :)
[04:06] <dholbach> It IS UVF.
[04:07] <Treenaks> dholbach: some people are special...
[04:07] <\sh> And I don't like writing exception reports for uvf...which I have already for pykde
[04:07] <\sh> I could have done it yesterday night, but I was sleeping and not reading the release announcement
[04:08] <dholbach> \sh: I just don't want to be flooded with requests like "look at this 3.5MB diff and tell me if I can upload it" - if we all have a look at stuff, it's easier to manage.
[04:08] <dholbach> We can surely be a bit more lax now still.
[04:08] <dholbach> If you don't like the process I had in mind, comment on it on the mailing list and propose something else.
[04:09] <\sh> dholbach: hehe I'm talking about main :) which is much more difficult because of colin/matt double :)
[04:09] <ogra> lax == 7MB diff ?
[04:09] <dholbach> \sh: ahh right
[04:09] <dholbach> ogra: yeah :-p
[04:09] <\sh> dholbach: and your proposal is absolutly ok :)
[04:09] <ogra> :)
[04:09] <dholbach> ogra: no, for example the lyx update looks good to me
[04:09] <ogra> yup, i thought the same
[04:09] <dholbach> it introduces just bug fixes.
[04:10] <ogra> the argument for backwards compatibility is also convincing
[04:10] <\sh> dholbach: think we have to stick with some main workflows for serious things like UVF but that's a normal workflow in my POV
[04:10] <dholbach> Cool.
[04:11] <dholbach> I'll mail lfittl and the list, that his update is in order.
[04:22] <azion> What exactly does upstream mean?
[04:23] <Hieronymus> azion: the people who develop an application, most of the time
[04:23] <Kyral> The originial dev
[04:23] <zakame> in most cases for Ubuntu, its Debian; for some (like Wine), its the Wine devs from WineHQ
[04:24] <tseng> saying Debian is upstream is pretty misleading in this context
[04:24] <tseng> upstream most always means the software author{,s}
[04:25] <azion> Ok, so we'll say Windows would be microsoft, or the 2000 kernel?
[04:25] <tseng> the 2000 kernel is irrelevant
[04:25] <tseng> Microsoft
[04:26] <tseng> but upstream is pretty irrelevant in windows, as ms does all the packaging
[04:26] <azion> Ah I get you now, thanks man
[04:26] <Hieronymus> azion: the people who make a program. GNU, Linux kernel hackers, Freeciv people, ..
[04:26] <tseng> upstream describes the relation between an open source software developer
[04:26] <tseng> and the distributor
[04:27] <azion> And versionfreeze?
[04:27] <tseng> uh
[04:27] <azion> Is that when ye stop taking on new packages
[04:27] <Hieronymus> yes
[04:27] <tseng> new versions of packages
[04:28] <azion> So from here until dapper's released ye'l be working on enhancements, bugs etc.
[04:30] <Nafallo> new versions of upstream, not of packages :-)
[04:30] <Nafallo> except the exceptions ofcourse. like gnome :-).
[04:30] <Kyral> New packs *points to REVU*
[04:30] <Kyral> *cough cough* ;P
[04:36] <Nafallo> ajmitch: zope3.2 seems to be auto-synced :-)
[04:41] <siretart> woooho
[04:44] <zakame> w00t
[04:52] <hub> crap
[04:52] <hub> the latest thunderbird update kills enigmail
[04:52] <hub> :-(
[04:53] <hub> looks like I have to rebuild it
[04:54] <Nafallo> hub: changelog etc... ;-)
[04:55] <hub> Nafallo: ?
[04:55] <Kyral> I <3 Mutt
[04:55] <\sh> hub: check the changelog of thunderbird...know issue
[04:55] <\sh> known issue even
[04:55] <hub> no doubt
[04:55] <hub> enigmail is tied to a specific version of tbird anyway
[04:55] <hub> but I don;t have the changelog
[04:55] <hub> I haven't upgraded yet
[04:57] <hub> upgrading
[04:57] <hub> I'll fix the enigmail package
[05:03] <crimsun> siretart: for ones that you just re-requested?
[05:04] <Nafallo> I think enigmail is in main anyway :-)
[05:05] <siretart> crimsun: sorry?
[05:06] <siretart> crimsun: no, for earlier requests, too. but not for all, hence my re request
[05:06] <crimsun> siretart: ah, cool :)
[05:15] <hub> Nafallo: last I looked Enigmail was in universe
[05:21] <Nafallo> k
[05:22] <Nafallo> it's in main for dapper anyway :-)
[05:26] <jeld> hello all
[05:27] <jeld> is there a way to make dpkg run post/pre install scripts verbously?
[05:27] <jeld> trying to debug package install and cannot seem to be able to figure out what exactly fails
[05:28] <crimsun> what happens when you dpkg -i [..] ?
[05:33] <jeld> it reports that post-install script failed
[05:35] <crimsun> what package's postinst?
[06:01] <lucas> hi
[06:07] <Kyral> Skate time :D
[06:09] <Kyral> http://yro.slashdot.org/article.pl?sid=06/01/19/1346237&from=rss <--And HOW!
[06:16] <bddebian> Heya Gang
[06:17] <LaserJock> hi bddebian
[06:17] <bddebian> Howdy LaserJock, how goes the battle? :-)
[06:17] <LaserJock> can we ask for a sync if it is a new package in Debian?
[06:17] <LaserJock> oh, it's alright
[06:18] <LaserJock> bddebian: you read ubuntu-motu ?
[06:18] <bddebian> LaserJock: Afaik, yes, you can request a sync of a new package
[06:18] <\sh> LaserJock: it's UVF
[06:18] <bddebian> LaserJock: No, I need to join that
[06:19] <LaserJock> \sh: but for new packages I have until FF, right?
[06:19] <\sh> LaserJock: only new revisions of debian packages are allowed without an exception..but new upstream versions == no, or try to explain yourself like dholbach explained :)
[06:19] <\sh> LaserJock: yes
[06:19] <LaserJock> even if the new package is coming from Debian, right?
[06:20] <\sh> LaserJock: if it's completly NEW?
[06:20] <bddebian> Oh yeah, UVF
[06:20] <\sh> LaserJock: I think thats allright as well..
[06:20] <LaserJock> ok, I think I've got it now
[06:21] <LaserJock> I have two packages going into Debian NEW and I had hoped that they would make it into dapper
[06:25] <lucas> LaserJock: libgnuplot-ruby should get in before FF too
[06:34] <LaserJock> lucas: hmm, I wonder if that counts. I think we could make a case ;-)
[06:57] <nomed> could anyone try out the example ...
[06:57] <nomed> /usr/share/doc/python-gnome2-extras/examples/gtkhtml2/simple-browser.py ?
[06:57] <nomed> i made a dist-upgrade to dapper ..
[06:58] <nomed> and the pymozembedded modules seems to "segfault" ...
[06:59] <nomed> in breezy i hadn't that problem ...
[07:56] <Kyral> Ahh cleaning out the system
[07:57] <Treenaks> Kyral: uh.. TMI?
[07:57] <Kyral> my computer...
[07:57] <Kyral> of packages I don't use anymore
[07:57] <Treenaks> ah ok :)
[07:57] <Kyral> like GNOME and KDE go bye bye ;P
[07:58] <\sh> hehe...alice in wonderland
[07:58] <Treenaks> down the rabbit hole? still TMI :)
[07:59] <\sh> strange, that 1999 matrix movie still has this impact to people
[07:59] <tseng> alice in wonderland is from the 1800s
[07:59] <Treenaks> The Matrix just referenced it because it was convenient :)
[08:00] <\sh> tseng: but not the attached string to, how did cypher said it, "alice is going bye bye" or so.
[08:01] <tseng> er
[08:01] <tseng> you are weird :)
[08:01] <\sh> it's just like "make my day"
[08:01] <\sh> or "hasta la vista, baby"
[08:02] <Treenaks> \sh: he said 'Kansas is going bye-bye'
[08:02] <\sh> Treenaks: right...because alice came from kansas...
[08:02] <Treenaks> \sh: no, that was Dorothy from the Wizard of Oz :)
[08:02] <\sh> but kansas was "the wonderland", regarding that everything was a bad dream, because she banged her head badly during a tornado
[08:02] <\sh> ah come on...who cares
[08:02] <Treenaks> you're confusing stuff now :)
[08:03] <\sh> Treenaks: right.
[08:03] <\sh> wizard of oz, alice in wonderland, \sh in lingerie, everything the same
[08:03] <Treenaks> \sh: whatever turns you on man...
[08:04] <\sh> Treenaks: a good job and a lot of money..
[08:04] <Treenaks> \sh: what? being a male lingerie model?
[08:05] <\sh> Treenaks: not possible..but I'm waiting for king kong 2006 movie remake...I'm playing king kong :
[08:05] <\sh> )
[08:05] <Treenaks> in lingerie?!
[08:06] <\sh> if we substitute lingerie with "hairy chest" why not
[08:06] <\sh> stop now...I can't smoke properly
[08:07] <rbelem> hey people, i have one question about cdbs. can you help me?
[08:09] <rbelem> is there a possibility to build a package with two different configuration? like package and package-minimal
[08:14] <azeem> rbelem: yes
[08:15] <azeem> rbelem: have your build target depend on two other, like build-all, build-minimal
[08:15] <azeem> and then either install everything first, clean, and configure/build again, or have two seperate build dirs, if the package allows
[08:16] <rbelem> azeem: hum... i see
[08:16] <rbelem> azeem: but is it possible with cdbs?
[08:16] <azeem> no
[08:17] <rbelem> ok, thx azeem
[08:17] <slomo_> rbelem: look at mplayer or totem for an example how to do it
[08:18] <Kyral> hmm
[08:18] <rbelem> slomo_: cool!
[08:18] <Kyral> nice looking
[08:18] <Kyral> http://jr.falleri.free.fr/keep/wiki/Download
[08:19] <Kyral> ah its already in REVU lol
[08:20] <Kyral> oh hub thanks for reviewing and advocating GTKEdit </late>
[08:21] <\sh> GTKedit?
[08:21] <Kyral> Yah
[08:21] <Kyral> Its a new package I have in REVU
[08:22] <Kyral> http://revu.tauware.de/details.py?upid=1523
[08:25] <Kyral> feel free to advocate ;P
[08:33] <Kyral> Okay question
[08:33] <Kyral> which runlevel would I enable for Fetchmail for it to start on boot?
[08:36] <aa_> is there a list of packages anywhere please?
[08:36] <Kyral> packages.ubuntu.com?
[08:37] <aa_> no idea, I can only find wiki tips on how to become a ubuntu maintainer
[08:37] <aa_> ah yes, that works, thaks
[08:38] <Kyral> You have to be a member first...
[08:38] <aa_> oh, nah, I am a developer. This stuffs just confuse me.
[08:38] <aa_> just wanted to check some things
[08:38] <Kyral> lol
[08:39] <Kyral> glad to meetcha..I'm one of the dudes who makes packages ;P
[08:39] <jamessan> aa_: you following me around or something?
[08:39] <Kyral> lol
[08:39] <jamessan> ;)
[08:39] <aa_> jamessan: yes!
[08:39] <Kyral> Attentive Upstreams are nice :D
[08:39] <aa_> jamessan: I believe you did tell me about the existence of this channel, yes
[08:40] <aa_> jamessan: are you a ubuntu maintainery-type-person?
[08:40] <jamessan> aa_: nah, I just idle here
[08:40] <aa_> who packages supy?
[08:40] <jamessan> learning by osmosis is fun
[08:40] <jamessan> me
[08:41] <aa_> ah
[08:41] <jamessan> someone in MOTU then syncs it for Ubuntu
[08:41] <slomo_> aa_: hm, i can't find a package named supy in ubuntu
[08:41] <jamessan> slomo_: supybot
[08:41] <aa_> yes, that
[08:42] <jamessan> aa_: there's even one in the channel  :)
[08:42] <slomo_> ah ok :)
[08:42] <aa_> ah, nice
[08:45] <jamessan> heh
[08:45] <rbelem> hey slomo_
[08:45] <Kyral> someone shot down GTKEdit just because it is GTK 1.2
[08:45] <Kyral> I think he failed to see the target machine for this app....
[08:45] <jamessan> aren't they trying to drop GTK 1.2?
[08:46] <rbelem> slomo_: do you know something about libraw1394?
[08:46] <slomo_> Kyral: who would it be that wants gtk 1.2? it's a nightmare imho ;) and i doubt gtk2 is much more demanding in memory/cpu
[08:46] <Kyral> Target machine for GTKEdit. Pentium 166 MHz, 32MB RAM
[08:49] <\sh> with 32mb i would use vi
[08:49] <Kyral> lol
[08:49] <\sh> not vim, plain vi :)
[08:49] <\sh> real vi
[08:49] <Kyral> What of those people who 1. Don't like vi 2. Don't like the commandline?
[08:49] <\sh> not the newly vim...no unix vi :)
[08:49] <\sh> Kyral: buy a new machine :)
[08:50] <\sh> hehe
[08:50] <Kyral> jeez...
[08:50] <Kyral> frankly this thing screams "Damn Small Linux" to me
[08:51] <\sh> damn small linux? the usb distribution on 128MB ram sticks?
[08:51] <Kyral> Its down to that now?
[08:51] <\sh> dunno :)
[08:52] <Kyral> Why do I think it will be hard to get another vote?
[09:32] <stratus> lucas, ping
[09:49] <lightbright> hello
[09:49] <LaserJock> hi
[09:50] <lightbright> LaserJock: hi
[09:53] <teprrr> hello there.. Riddell and \sh_away told me that I should get an account to REVU. came to ask if someone can help me with gpgkey thing.. anyone wants to help me a bit?
[09:54] <LaserJock> teprrr: so I take it you don't have a key currently
[09:56] <teprrr> LaserJock, correct
[09:56] <teprrr> though I have tested and created a key with kgpg
[09:56] <LaserJock> then you should have a key ;-)
[09:56] <teprrr> but it's been a while ago and don't have the key anymore
[09:56] <LaserJock> oh
[09:56] <teprrr> heh :)
[09:57] <LaserJock> so can you make a new key with kgpg ?
[09:57] <teprrr> so I just create a new key and send public part or..?
[09:58] <mbreit> teprrr: exactly
[09:58] <LaserJock> well, I'm not terribly familiar with kgpg but you should be able to send your key to a key server from it
[09:58] <lucas> stratus: pong
[09:58] <mbreit> yeah, having that key on a keyserver would be great ;)
[09:58] <LaserJock> teprrr: I would also look at https://wiki.ubuntu.com/GnuPrivacyGuardHowto
[09:58] <LaserJock> teprrr: especially the the "Uploading the Key" section
[09:59] <teprrr> ahh, okay, thanks
[09:59] <mbreit> teprrr: but remember that you can't ever delete a key from a keyserver once you uploaded it
[10:00] <stratus> lucas, oh i replied your message in -devel, i was going to talk here but i think it's better discuss there.
[10:00] <lucas> okey
[10:01] <stratus> lucas, are you reading utnubu-discuss too?
[10:01] <LaserJock> lucas: yes, interesting email
[10:01] <lucas> stratus: yes
[10:01] <lucas> stratus: I prefer to go slowly with this proposal
[10:01] <stratus> np, so you'll see the buxy' mail.
[10:01] <lucas> first get accepted by ubuntu, then move to debian
[10:02] <stratus> lucas, sure but debian has no problems with volunteers (really)
[10:02] <stratus> read my reply and you'll understand
[10:02] <LaserJock> lucas: so this DCT would be different than the Utnubu?
[10:03] <ogra> stratus, did someone find out what happened with the ltsp package in debian ?
[10:03] <stratus> i really believe that a small group of DDs and some others as a MOTU subteam (or whatever) can handle the DCT thing in universe
[10:03] <stratus> ogra, i think otavio talked with ajt.
[10:03] <ogra> ah, he didnt mail, i was wondering
[10:04] <lucas> LaserJock: yes, utnubu is more a debian team talking to ubuntu
[10:04] <stratus> ogra, i'm waiting otavio' reply to pkg-ltsp ml, but i'm gonna ask tomorrow anyway
[10:04] <lucas> DCT would be an ubuntu team talking to debian
[10:04] <ogra> yup
[10:04] <lucas> of course, both teams would talk together
[10:04] <LaserJock> lucas: oh, ok
[10:05] <lucas> stratus: Raphael (buxy) reviewed the proposal before I sent it to ubuntu-devel@
[10:05] <stratus> ogra, i think pere and/or vagrant are reviewing the bzr repo changes, after that the things will start to move faster. I believe that in the next month we will have the first pkg-ltsp release.
[10:05] <ogra> fine
[10:05] <stratus> lucas, funny because i pointed him to the proposal at utnubu-discuss
[10:06] <lucas> yup, saw that :)
[10:06] <ogra> in the next month most of my development will hit the ubuntu package
[10:06] <stratus> ogra, following the roadmap the second step will be jump on your changes
[10:06] <ogra> yup, should be half way stable and tested then, good timing ;)
[10:07] <stratus> ogra, yes but i still believe that we will have even better results (as a group) for etch and dapper+1
[10:08] <stratus> that's just the start up
[10:08] <dholbach> Riddell: going to merge musicbrainz - to get python funkyness
[10:17] <LaserJock> hmm, so what happens to the 115 packages on the tiber "Accepted" list ?
[10:31] <hub> raphink: if you have time, can you review my pkg... I have a few of them without any comment
[10:31] <raphink> not now hub
[10:31] <raphink> I'm going to bed now
[10:31] <hub> raphink: tomorrow is fine.
[10:31] <raphink> ok :)
[10:31] <hub> to bad at 10:30PM?
[10:31] <hub> :-)
[10:32] <hub> to bed I meant
[10:32] <hub> :-/
[10:33] <rbelem> hey raphink
[10:34] <rbelem> raphink: i updated lives, can you review?
[10:34] <raphink> rbelem: not right now i'm going to bed
[10:34] <raphink> rbelem: send me the link to my email and I'll do it tomorrow ok?
[10:34] <rbelem> raphink: ok ;-)
[10:34] <raphink> hub: I go to sleep with my friend because it's nicer and she wakes up at 6
[10:34] <raphink> so I review in the morning
[10:34] <hub> hehe
[10:35] <raphink> and there's nobody around here so i can work well ;)
[10:35] <rbelem> raphink: good night
[10:35] <hub> have fun :-)
[10:35] <raphink> thanks
[10:35] <raphink> hub: idem pour toi : tu peux m'envoyer l'url
[10:36] <rbelem> hub: i updated libiec61883 too
[10:37] <rbelem> hub: can you review?
[10:37] <hub> rbelem: later
[10:37] <hub> rbelem: at work atm
[10:38] <rbelem> hub: can you review muse-streamer too?
[10:38] <rbelem> ;-)
[10:39] <rbelem> hub, raphink: thx ;-)
[10:40] <hub> rbelem: np
[10:43] <rbelem> have to go now
[10:43] <rbelem> good night
[10:43] <raphink> night guys
[10:50] <thierry_> where can I find the date and holder of the copyright of a librairy, I can't find it for fxruby http://revu.tauware.de/revu1-incoming/libfxruby1.4-0601061255/libfxruby1.4-1.4.3/
[10:58] <Kyral> is anyone working on Malone 6052?
[10:58] <Ubugtu> Malone bug 6052: "Missing library dependencies" Fix req. for: dhcdbd (Ubuntu), Severity: Normal, Assigned to: MOTU, Status: Confirmed http://launchpad.net/bugs/6052
[11:01] <Kyral> Oh wait, this is Nafallo's package
[11:01] <Kyral> oh well, I can still fix the bug no?
[11:02] <LaserJock> hmm, new xorg took out vnc4server. bummer :(
[11:07] <ajmitch> morning
[11:07] <LaserJock> hi ajmitch
[11:09] <Kyral> hey ajmitch
[11:13] <LaserJock> anybody know of a good vnc server other than vnc4server?
[11:13] <Kyral> Shoot I forgot how to close a bug lol
[11:14] <LaserJock> Kyral: umm, change the status
[11:15] <Kyral> yah, Attach the debdiff
[11:15] <Kyral> but what do I change the status to?
[11:15] <dholbach> I'll call it the day. Have a nice evening.
[11:15] <LaserJock> cya dholbach
[11:16] <dholbach> bye LaserJock
[11:16] <Kyral> Should I change it to "In Progress"?
[11:16] <Kyral> or "Fix Released"
[11:17] <LaserJock> Kyral: so you added a patch?
[11:17] <Kyral> yah
[11:17] <Kyral> Attached it to the bug
[11:17] <LaserJock> Kyral: well, unless the patch is uploaded it shouldn't be "Fix Released"
[11:18] <LaserJock> Kyral: I would go with "In Progress" or "Fix Commited"
[11:18] <Kyral> There should be a "Fix Attached" option...
[11:18] <minghua> LaserJock: I just had time to read through the threads you initiated on debian-science
[11:19] <LaserJock> minghua: lol, that was a little while ago
[11:19] <Kyral> okay done
[11:19] <minghua> LaserJock: yeah, that's why I tell you here
[11:19] <Kyral> ping someone who can upload lol
[11:19] <LaserJock> minghua: what did you think? I might be a little nieve when it comes to Debian
[11:19] <minghua> LaserJock: I think I'll work on that with you soon
[11:19] <LaserJock> minghua: but I'm learning
[11:20] <Kyral> Malone 6052
[11:20] <Ubugtu> Malone bug 6052: "Missing library dependencies" Fix req. for: dhcdbd (Ubuntu), Severity: Normal, Assigned to: MOTU, Status: Fix Committed http://launchpad.net/bugs/6052
[11:20] <Kyral> now someone just has to upload
[11:20] <LaserJock> minghua: MOTUScience has some good info that I started
[11:20] <LaserJock> minghua: I was going to do some sort of MOTUScience Update email to debian-science soon, after UVF
[11:21] <Kyral> anyone even around?
[11:21] <LaserJock> Kyral: I'm here ;-)
[11:21] <Kyral> I meant who can upload the patch :P
[11:22] <LaserJock> Kyral: you might also reassign it to MOTU Reviewers
[11:22] <minghua> LaserJock: I think one big opportunity here is we can use MOTUScience to show how ubuntu-debian collaboration should work
[11:22] <LaserJock> minghua: that was my thought
[11:23] <minghua> LaserJock: and since it's an old thread, I don't think I'll reply to it, but I have a few comments about the "separation" concern about two lists you may want to hear
[11:23] <minghua> LaserJock: so you can use as your defense later
[11:23] <Kyral> you sure MOTUReviwers is the right reassign?
[11:24] <LaserJock> minghua: right now, there are 10 packages in Ubuntu and not in Debian. 6 are from apt-get.org. 3 of the others have ITPs
[11:24] <LaserJock> minghua: and of the 6 apt-get.org 1 is going into Debian and I got one fixed so that it works in Ubuntu
[11:24] <Kyral> anyway I have to go to dinner
[11:25] <minghua> LaserJock: 1. the MOTUScience people are more closely organized, we know each other on IRC, and can usually talk with others or upload fixed packages for others, this is not the case for Debian, so motu-science is probably going to be like sounder list a bit
[11:25] <LaserJock> Kyral: MOTU Reviewers is for reviewing patches, etc. and I think it goes to the same address as the revu stuff so I think it would work
[11:26] <minghua> LaserJock: 2. motu-science list also serves as the team role address on launchpad, and will receive bug reports in the future, I am sure debian-science doesn't want that
[11:26] <minghua> LaserJock: So I believe as long as we keep communication back and forth, separating lists shouldn't be a problem
[11:26] <LaserJock> minghua: that was my thinking
[11:27] <ajmitch> dholbach: so what happens with the large number of syncs that didn't get through before UVF?
[11:27] <dholbach> ajmitch: raise the issue on #ubuntu-devel
[11:28] <LaserJock> minghua: btw, there are only 5 out of 452 packages that are in Ubuntu but not going to be in Debian
[11:28] <minghua> LaserJock: yeah, I saw that the most clear voice in those threads is "try to get the packages only in ubuntu in debian", so I think that should be our priority
[11:29] <minghua> LaserJock: however I have a fear that for the apt-get.org packages we MOTUScience people are not qualified maintainer
[11:29] <LaserJock> minghua: right, and so I think Debian should be ok with leaving the apt-get.org ones out
[11:30] <LaserJock> minghua: but I've done 2 ITPs, Kyral has done at least 1, and the texmaker guy also did 1
[11:30] <minghua> LaserJock: yes, I think what we should do right now is identifying the package that has an active ubuntu maintainer and push it to debian
[11:30] <minghua> LaserJock: like what Kyral and you have been doing
[11:30] <minghua> LaserJock: I think I'll join soon
[11:31] <azeem> LaserJock: talking of which, why does you packaeg only Recommends: gnuplot, is it useful without it?
[11:31] <azeem> I have to admit I haven't tried it out yet, only glanced at it
[11:31] <azeem> been pretty busy with Uni lately
[11:31] <minghua> LaserJock: ITP and RFP are fine, we probably don't want to RFS for those apt-get.org stuff
[11:32] <LaserJock> minghua: we've only ITP'd the ones we have packaged ourselves. I did get lucas to get a new ruby-gnuplot package into Debian
[11:32] <LaserJock> azeem: you can use it withought gnuplot plot but it really is supposed to be used with it
[11:33] <LaserJock> azeem: it was what the original packager put
[11:33] <minghua> LaserJock: cool, a very good start, I would say.  Thank you for working on this front
[11:33] <LaserJock> azeem: I can change it if you want
[11:33] <azeem> LaserJock: ah
[11:33] <azeem> well, whatever you think is reasonable
[11:33] <LaserJock> minghua: that's ok
[11:33] <ajmitch> hi azeem
[11:33] <azeem> I just wondered, because from the description I thought it would be useless without
[11:34] <azeem> heya Andrew!
[11:34] <lucas> my package in debian Depends on gnuplot
[11:34] <LaserJock> azeem: well, you can basically grep an output file with it if you don't have gnuplot, but that's about it
[11:35] <LaserJock> lucas: we're talking about a package I'm having azeem sponsor.
[11:35] <lucas> ah sorry
[11:35] <LaserJock> lucas: np
[11:35] <LaserJock> too many gnuplots running around ;-)
[11:35] <lucas> thought it was about ruby-gnuplot
[11:35] <lucas> yeah :)
[11:36] <LaserJock> azeem: I'm going to switch it because it is just basically grep if you don't have gnuplot
[11:36] <azeem> one could argue that any serious scientific workstation has gnuplot installed anyway
[11:36] <azeem> but a Depends is better I think
[11:36] <LaserJock> azeem: true ;-)
[11:38] <LaserJock> minghua: have you seen the package lists that I made?
[11:40] <hub> w00h00
[11:40] <hub> key in keyring
[11:46] <ajmitch> hub: great
[11:46] <LaserJock> azeem: done, uploaded to same URLs. when do you think you'll have a chance to look at them?
[11:53] <LaserJock> hmm, I'm starting to see "Malone as web only" as a pain, do you think we will eventually be able to do database type queries?
[11:54] <ajmitch> eventually, one day
[11:54] <ajmitch> via xml-rpc
[11:54] <LaserJock> hmm, does eventually mean in the forseable future?
[11:55] <LaserJock> or as in, "don't count on it"
[11:55] <minghua> LaserJock: you mean the ones comparing the versions of packages in ubuntu and debian?
[11:55] <Lathiat> its definately planned, i don't know on the timeframe its planne dfor
[11:55] <ajmitch> LaserJock: in the future, not sure when
[11:55] <ajmitch> morning Lathiat
[11:55] <Lathiat> yo
[11:55] <LaserJock> minghua: yes, I think they could be very useful
[11:55] <Lathiat> i fly out tomorrow :)
[11:56] <minghua> LaserJock: it's very useful for us, but I'm not sure if a debian maintainer can read it easily
[11:57] <LaserJock> minghua: what do you think would be easier for DDs?
[11:57] <LaserJock> minghua: maybe just a alphabetical list with versions and links?
[11:58] <ajmitch> probably
[11:58] <minghua> LaserJock: ideally, a list only showing the packages with differences, sorted by the name of maintainer, with only links to the ubuntu .dsc/.diff.gz and a debian bug
[11:58] <minghua> LaserJock: it's a lot of work, for sure
[11:59] <LaserJock> minghua: lucas's scripts are pretty good. I might be able to get something close.
[11:59] <minghua> LaserJock: but I think that's the best bet if we want all DDs look at our list
[11:59] <lucas> LaserJock: don't hesitate to build on them :)
[12:00] <LaserJock> anyway, I think the lists I made are good for showing DDs that we aren't changing huge amounts of stuff here
[12:00] <minghua> LaserJock: yeah, but we also need to identify our changes and submit debian bugs accordingly
[12:00] <LaserJock> minghua: sure, but the first step is to figure out just how large and where the "problem" is
[12:01] <minghua> LaserJock: well, some people in the debian-devel thread are also saying "even if the source package is the same, if you build with a different toolchain/dependency chain, it's still a different package", so you can never satify everybody.  But we try to do what we can do
[12:02] <minghua> LaserJock: definitely.  that's why I said "it's very useful for us".  we can look at that list and figure out what we should do next
[12:02] <LaserJock> minghua: well, I'm starting to understand that you will never please all of d-d and nor should we.