[12:03] <LaserJock> uniq: you might try #kubuntu-devel
[12:05] <freeflying-ibook> uniq:is it in main?
[12:06] <uniq> it's a motu package in universe. and it's on the priority list https://launchpad.net/distros/ubuntu/+bugs?field.searchtext=unmetdeps&orderby=-datecreated&search=Search
[12:06] <freeflying-ibook> uniq: I can review it for you
[12:06] <uniq> freeflying-ibook: no, it's on dholbacks list of unmet deps packages. very MOTU imho.
[12:07] <uniq> well, the patch adds a >, not much to review. But sure.
[12:40] <zul> heylo
[12:40] <LaserJock> hi zul
[12:41] <zul> hey LaserJock
[01:05] <allee> hi, I've a bug in malone, and right now preparing the bug report for upstream bts.  Upstream told me to keep him up to date
[01:06] <allee> Now I'm ponder if it's okay to create a  lauchpad account for upstream (asking upstream before of course) and subscribe this account to bugs that are upstream bugs.
[01:07] <allee> this would keep upstream automaticly informed in case more info gets added to malone.
[01:08] <allee> Or are there other ways better achieve this?
[01:08] <lifeless> yup
[01:08] <lifeless> get upstream to make their own account ;)
[01:08] <lifeless> then you can subscribe them to those bugs
[01:08] <lifeless> do upstream have a bts ?
[01:09] <allee> lifeless: okay is there a naming conventions  like  <product>-upstream  or <product>-devel
[01:09] <lifeless> allee: no, accounts are for *people*
[01:09] <allee> lifeless: yes KDE bts (and I add a lauchpad link when KDE bts bug is filed)
[01:10] <lifeless> allee: what sort of updates was he/she asking for ?
[01:11] <allee> lifeless: we were hunting https://launchpad.net/distros/ubuntu/+source/digikam/+bug/34462  on #digikam channel
[01:11] <Ubugtu> Malone bug 34462 in digikam "Digikam deletes EXIFs when auto-rotating on import" [Major,Confirmed] 
[01:11] <allee> lifeless: yeah, but upstream are several people.  3-5 in this case
[01:11] <lifeless> creating an account for a list is wrong
[01:11] <allee> lifeless: all digikam bugs in KDE bts are send to digikam-devel ml
[01:12] <lifeless> allee: so, when you file it upstream, they will get mail.
[01:12] <lifeless> allee: I'm trying to understand what 'upstream' want to happen here
[01:12] <lifeless> then I can advise how to make malone do that
[01:13] <allee> lifeless: upstream told me: keep me inform, send debug output etc
[01:13] <lifeless> allee: once its filed upstream, you should be doing that in the upstream bts though
[01:13] <lifeless> allee: thats what *upstream* means.
[01:13] <jmg> hi all
[01:13] <allee> lifeless: I'll do this in KDE bts.  But what happens when other see the malone bug and add infos to the malone bug, then
[01:14] <lifeless> allee: the bug is tagged upstream. So other know to go to the upstream bts.
[01:14] <allee> a) I've to tell them please use upstream bts or b) forward it myself
[01:14] <allee> checking ...
[01:14] <lifeless> allee: there are two choices here. you can use the upstream bts, or malone, as this bug gets fixed.
[01:15] <lifeless> if you use malone, and upstream want to be involved, then they need to use malone
[01:15] <lifeless> given that you are saying this *is an upstream bug*, its entirely appropriate that you use the upstream bug tracker.
[01:16] <lifeless> malones upstream bug watch will synchronise data from the kde bts eventually, though it doesn't right now.
[01:18] <allee> heh, develish: for marked-as-upstream don't allow additional comments, redirect to upstream bug URL instead ;)
[01:18] <lifeless> :0
[01:19] <lifeless> hmm, digikam product isn't linked tothe source package
[01:20] <lifeless> allee: is it still stable in dapper ?
[01:21] <allee> is a product created automaticly?  I vaguely remember that I started long ago to add it but when bazarr came into play aborted
[01:21] <lifeless> you created the product
[01:21] <lifeless> its a little stale, just updating it
[01:21] <allee> lifeless: for cameras without gravity sensor, yes.
[01:21] <lifeless> is it still the stable release that we package in dapper ?
[01:22] <allee> yes
[01:22] <allee> lifeless: but there's 0.8.2-beta1 that better than 0.8.1 (I've a half finished UVF for it  + digikamimageplugins later)
[01:24] <allee> UVF not finished because I could convience upstream to look into the exif-list bug (fixed in devel trunk already, for of future 0.9 release)
[01:30] <jmg> 41678
[01:30] <jmg> #41678
[01:34] <lifeless> bug 41678
[01:34] <Ubugtu> Malone bug 41678 in ispellcat "Please sync with Debian unstable" [Normal,Unconfirmed]  http://launchpad.net/bugs/41678
[01:35] <jmg> heh
[01:42] <jmg> crimsun
[01:42] <crimsun> jmg: hi
[01:42] <LaserJock> oh sweet, irssi is sponsoring SoC projects
[01:43] <jmg> dont know if i should bother you with alsa stuff
[01:43] <crimsun> jmg: I'll be in a much more suitable timeframe to look at alsa stuff in an hour
[01:43] <jmg> ok
[03:01] <LaserJock> hi Kyral
[03:01] <zul> heylo
[03:10] <ajmitch> hi
[03:11] <zul> how is it going ajmitch?
[03:11] <ajmitch> good, how are you?
[03:11] <zul> good
[03:23] <jmg> if network-manager is interfering (i think) with my bootup, wheres the right place to file a bug?
[03:23] <jmg>  /etc/init.d/networking start after bootup will fix the problem. hmm
[03:50] <freeflying> ajmitch: ping
[03:51] <ajmitch> yes? any reviews must wait, i'm at work
[03:52] <freeflying> ajmitch: not reviews, heh, can I ask for sync from sid now
[03:53] <ajmitch> you can, but why ask me?
[03:55] <freeflying> ajmitch: thanks, just wanna confirm from you that can ask for now.
[04:38] <bddebian> Heya gang
[04:38] <dolson> hi
[04:39] <bddebian> Hello dolson
[04:40] <zakame> hi all
[04:40] <zakame> hello dolson
[04:40] <dolson> hi zakame
[04:40] <dolson> zakame: I got a job today, did you hear? :D
[04:41] <bddebian> dolson: Cool, congrats :-)
[04:41] <zakame> dolson: w00t! :D
[04:41] <zakame> dolson: good for you, now its my turn to find a job :)
[04:41] <dolson> bddebian: I thought you were here earlier when I said it :D
[04:41] <dolson> zakame: yeah, I'm a Perl developer starting Monday. I get to install Ubuntu on my workstation. And now I'm looking for a good book on learning Perl
[04:42] <bddebian> dolson: I sorta was but I was swamped at work so I didn't say anything :(
[04:42] <zakame> dolson: now, double w00t! I'm doing Perl too... I have the Llama, second ed
[04:42] <crimsun> dolson: the ora.com cookbook & learning perl are good
[04:42] <dolson> bddebian: ;) it's all good. I hope that I can pull it off
[04:42] <dolson> crimsun: thanks bro, I'll check out the ora one (I already bookmarked Learning Perl)
[04:43] <crimsun> zakame: it seems you and I are triggering the same soyuz bug with '.' ;)
[04:43] <bddebian> Who reviews the MOTU UVF requests?
[04:43] <zakame> crimsun: looks like it
[04:44] <crimsun> bddebian: the uvfe team (sire,slom,dholb)
[04:44] <zakame> a workaround would be to update my key's UIDs, right? add a "Zak Elep" without the B...
[04:44] <crimsun> zakame: just make sure your display name and your changeslist name both have no '.'
[04:44] <crimsun> zakame: that's the workaround that cprov recommended to me
[04:45] <zakame> ah, ok
[04:45] <crimsun> like I have to use "Daniel T Chen" instead of "Daniel T. Chen"
[04:45] <dolson> oh no, it's Beginning Perl that I bookmarked
[04:45] <zakame> but anyhow, celso's already doing the fix :D
[04:46] <crimsun> yeah
[04:53] <bddebian> Hmm, to attempt to look at bugs at this hour or not...
[06:14] <bddebian> Gnight gang
[06:38] <dolson> how does Yelp work, exactly? if I install something like postgresql-doc-8.1 does it show up docs in Yelp, or do I have to browse to the files and such?
[06:41] <crimsun> it's unlikely that pgsql's docs will show up in yelp by default, since yelp is gnome-centric
[06:41] <crimsun> you'll more than likely need to use info, man, and $PAGER in /usr/share/doc/postgresql-doc-8.1
[06:43] <dolson> oh, there it is
[06:43] <dolson> I just tried it and it does show up
[06:43] <crimsun> ah, excellent.
[06:43] <dolson> yeah, I'm impressed :D
[06:44] <dolson> go to System > Help > System Documentation to launch Yelp, then go to Applications > Programming, and it lists it there. Pretty slick stuff
[06:44] <crimsun> cool
[06:45] <dolson> ooh, Yelp has bookmarks too. I love this.
[06:54] <XhyldazhK> hi all
[06:54] <XhyldazhK> i have... kind of a request...
[06:55] <XhyldazhK> i'm a chicken scheme user, but i've found that chicken in dapper drake is 1.63, that is ancient (2004 or earlier)
[06:55] <XhyldazhK> there is a chicen source .deb in debian unstable, currently i'm compiling it
[06:56] <XhyldazhK> please update chicken, it shouldn't be very hard
[06:56] <XhyldazhK> the one in debian unstable is latest one, 2.3
[06:56] <crimsun> we're two months past upstream version freeze.
[06:56] <XhyldazhK> oops
[06:56] <XhyldazhK> sorry...
[06:56] <lifeless> XhyldazhK: that means, that unless there is a serious bug in chicken, we'd rather not update it
[06:56] <lifeless> because we'll run the risk of *adding* bugs.
[06:57] <lifeless> we can make exceptions, there is a process.
[06:57] <XhyldazhK> ok... but it will be updated in system updates / next version?
[06:57] <crimsun> in dapper+1, yes
[06:57] <lifeless> you can file a bug on chicken in dapper now if you like, as a memo
[06:57] <lifeless> but it *should* be automatica.
[06:58] <XhyldazhK> well is not a bug, its simply that 1.63 cannot use chicken 'egg' modules in static linking and 2.2+ can
[06:58] <XhyldazhK> automatica?
[06:58] <lifeless> s/a\./\./
[06:59] <crimsun> XhyldazhK: are these modules already packaged in dapper?
[06:59] <crimsun> (I don't know anything about chicken, sorry)
[06:59] <XhyldazhK> nope... they are installable via a program that is included with chicken
[06:59] <XhyldazhK> it downloads them and installs them
[07:00] <crimsun> if it were to install 1.63 now, would said modules be usable by default, or is extraordinary effort required to make them work?
[07:00] <crimsun> s/if it/if I/
[07:01] <lifeless> crimsun: what are you trying to ask ?
[07:01] <XhyldazhK> 1.63 can use those modules, only cant make a statically linked executable using them
[07:02] <crimsun> lifeless: if the current package is unusable (as in the older version of gtk-gnutella, say), then that's viable for a UVFe request
[07:02] <XhyldazhK> what is a problem for me because i'm developing for the gamepark holdings gp2x using a compiler installed by myself and using a cross-compiled chicken installed by myself(2.3) in addition to the 'normal' chicken 1.63
[07:03] <XhyldazhK> now that I speak, for dapper+1 a cross compiler for gp2x would be great
[07:03] <dolson> XhyldazhK: is there one in Sid?
[07:03] <XhyldazhK> sid = unstable?
[07:03] <dolson> XhyldazhK: debian unstable, yeah
[07:03] <crimsun> XhyldazhK: ok, as long as 1.63 is usable at least with those modules, then the impetus to file a UVF exception is much lower
[07:04] <XhyldazhK> yes, i know...
[07:04] <XhyldazhK> if that's not possible i will simply post somewhere the method to get ht updated chicken deb
[07:05] <dolson> XhyldazhK: if there is a gp2x cross-compiler in debian unstable/sid, then it should be in ubuntu edgy automatically, but if not, then someone has to package it
[07:05] <crimsun> (never fear, dapper+1 is only a bit over one month away)
[08:04] <ivoks> hi
[08:18] <ivoks> no one? :)
[08:18] <crimsun> hi ivoks
[08:18] <crimsun> & Hobbsee
[08:18] <ivoks> hi crimsun
[08:18] <Hobbsee> hi crimsun
[08:19] <ivoks> crimsun: did you wrote any spec?
[08:19] <ivoks> crimsun: i tried to contribute something, but I guess that owner has to put me in Contribute list, right?
[08:20] <crimsun> ivoks: I haven't yet, no
[08:20] <ivoks> ok
[09:44] <zakame> hi all
[09:45] <zakame> wb all
[09:51] <zakame> what's up with malone 28810?
[09:51] <Ubugtu> Malone bug 28810 in kdrill "undeclared dependency on libXp6" [Major,In progress]  http://launchpad.net/bugs/28810
[10:06] <Unfrgiven> hi all!
[10:07] <highvoltage> hi :)
[10:07] <Hobbsee> hi Unfrgiven and highvoltage
[10:08] <highvoltage> hi Hobbsee
[10:08] <zakame> hello Hobbsee highvoltage Unfrgiven
[10:10] <highvoltage> public holidays++
[10:20] <slomo> zakame: ping?
[10:20] <zakame> slomo: pong, what's up? =)
[10:20] <slomo> zakame: regarding bug #6004... please look bug #6003
[10:20] <Ubugtu> Malone bug 6004 in xvidcore "Changed CFLAGS for a speed increase." [Normal,In progress]  http://launchpad.net/bugs/6004
[10:20] <Ubugtu> Malone bug 6003 in transcode "Changed CFLAGS for a speed increase." [Normal,Needs info]  http://launchpad.net/bugs/6003
[10:21] <slomo> zakame: so don't do it ;)
[10:21] <zakame> slomo: ah, thanks for the heads-up ;-)
[10:22] <slomo> zakame: np :)
[10:51] <dholbach> unmetdeps went from 91->85
[10:52] <dholbach> rock on!
[10:54] <Hobbsee> 85 hey?
[10:54] <zakame> wtg
[10:56] <dholbach> and that was on i386
[10:57] <dholbach> i suppose there are more around on amd64 and powerpc
[10:57] <dholbach> it'd be nice if we could clean those up
[10:57] <dholbach> most are easy rebuilds
[10:58] <dholbach> and others might be just stuff we might want to remove
[10:58] <dholbach> or sync from debian
[10:59] <Hobbsee> dholbach: ping?
[10:59] <dholbach> Hobbsee: pong
[10:59] <dholbach> i'm here :)
[10:59] <Hobbsee> bug 41535 - that package can now be removed from the repos, it's depreciated with kde 3.1
[11:00] <Ubugtu> Malone bug 41535 in konq-shellhere "[UNMETDEPS]  xsim has unmet dependencies" [Minor,Confirmed]  http://launchpad.net/bugs/41535
[11:00] <dholbach> yeah
[11:00] <dholbach> i followed up on the bug
[11:00] <dholbach> i'd rather like somebody from the kubuntu camp to get that done
[11:00] <Hobbsee> oh, didnt see that
[11:00] <dholbach> i don't want to be blamed for removing kubuntu packages :)
[11:00] <Hobbsee> dholbach: well, i'm more from the kubuntu side, adn i'm telling you that you can remove it...that okay?
[11:00] <Hobbsee> :P
[11:00] <dholbach> no :)
[11:01] <dholbach> I want somebody to justify and present it to 'ubuntu-archive' team.
[11:01] <Hobbsee> damn.  i'll raise it in our meeting tomorrow then
[11:01] <dholbach> ... somebody else than me.
[11:01] <Hobbsee> *wonders how to do that*
[11:01] <dholbach> just say: it's obsolete, functionality is nowadays in blah, makes no sense, package has no rdepends, remove it please.
[11:02] <Hobbsee> how can you see if anything relies on the package?
[11:02] <dholbach> apt-cache rdepends <something>
[11:02] <Hobbsee> gotcha
[11:02] <dholbach> rock on
[11:02] <Hobbsee> nothing, great.
[11:02] <Hobbsee> gets justified in the bug report?
[11:03] <dholbach> yeah
[11:03] <dholbach> and subscribe 'ubuntu-archive'
[11:03] <dholbach> and make the bug description a bit more telling :)
[11:03] <dholbach> <-- my fault
[11:03] <Hobbsee> hehe gotcha
[11:03] <dholbach> but as I said in my mail to ubuntu-motu, the bug in the script is fixed now
[11:03] <dholbach> so next bug massfiling will be happier :)
[11:04] <Hobbsee> hehe
[11:08] <Hobbsee> dholbach: okay, done that one :)
[11:08] <dholbach> nie!
[11:08] <dholbach> nie!
[11:08] <dholbach> nice!
[11:08] <dholbach> ...
[11:08] <Hobbsee> hehe
[11:08] <Hobbsee> ni!  to you too
[11:10] <Hobbsee> er...for bug 41564 the package doesnt seem to exist on my system...
[11:10] <Ubugtu> Malone bug 41564 in illuminator "[UNMETDEPS]  xsim has unmet dependencies" [Normal,Confirmed]  http://launchpad.net/bugs/41564
[11:12] <ajmitch> that's the source package name
[11:12] <ajmitch> binary packages are on https://launchpad.net/distros/ubuntu/+source/illuminator/0.9.1-3
[11:12] <Hobbsee> ooh, more hugs!
[11:12] <dholbach> hey ajmitch :)
[11:13] <Hobbsee> gotcha
[11:13] <ajmitch> hey daniel, how's it going?
[11:13] <dholbach> fine, thanks
[11:13] <dholbach> just trying to look into a gok segfault
[11:13] <ajmitch> sounds nasty
[11:15] <Hobbsee> ooh goody...i think i can fix this one too...
[12:50] <kelmo_lap> moin siretart
[12:54] <siretart> hey kelmo_lap
[12:55] <siretart> kelmo_lap: I uploaded something based on r370 to ubuntu for fixing the wext issue
[12:56] <siretart> kelmo_lap: there are quite a lot of reports in NM which I think will be fixed by this
[12:56] <kelmo_lap> siretart, sure there would be
[01:01] <kelmo_lap> siretart, cheers for verifying that on the ipw2100 hardware, i do not have ipw2100 available to me
[01:01] <siretart> :)
[01:04] <kelmo_lap> r370 or r320?
[01:04] <siretart> err, the one just before you refactored the ifupdown script
[01:04] <kelmo_lap> ok, 320
[01:04] <siretart> I didn't get to thorough testing of the new script
[01:04] <siretart> ok
[01:05] <kelmo_lap> i would like to push a new upload, but would appreciate testing/advocating of the "refactored" script
[01:05] <kelmo_lap> siretart, wouls that be possible for you todo sometime in the next week or so?
[01:05] <kelmo_lap> s/wouls/would
[01:07] <siretart> kelmo_lap: I see that I get at week end to it
[01:07] <siretart> kelmo_lap: a quick test showed me that it works
[01:07] <siretart> but since we are in deep freeze for dapper, I'm more conservative with uploading there than to unstable
[01:07] <kelmo_lap> sure, you have every right to be
[01:11] <kelmo_lap> siretart, the other thing a didn't get a chance to say, madwifi-ng is on the verge of experimental (rotting in NEW), the madwifi-includes patch i already have in preparation for our experimental branch
[01:11] <kelmo_lap> siretart, but we could make another choice
[01:12] <kelmo_lap> siretart, on second thought, probably not
[01:12] <kelmo_lap> siretart, again, i'd like to test your thoughts on that issue
[01:23] <kelmo_lap> heh, as i ask, a bug is filed with an interesting patch
[01:24] <kelmo_lap> debian bug #365014
[01:24] <Ubugtu> Debian bug 365014 in wpasupplicant "Subject: wpasupplicant: Patch for supporting madwifi-old and madwifi-ng in parallel" [Wishlist,Open]  http://bugs.debian.org/365014
[01:24] <kelmo_lap> hmm, interesting
[01:56] <siretart> kelmo_lap: err
[01:56] <siretart> kelmo_lap: I don't get it quite, I think. Why don't we just keep the madwifi-old headers in the package, and let the madwifi-ng users just use wext?
[01:57] <kelmo_lap> siretart, that was my "second thought"
[01:57] <StevenK> Is wext less sucky than supplicant?
[01:57] <kelmo_lap> siretart, i would be happy todo that until as madwifi upstream, i declare madwifi-old dead
[01:58] <kelmo_lap> siretart, which could be as soon as 2.6.17
[01:59] <siretart> and why do you want to switch the headers from madwifi-old to madwifi-ng at all?
[01:59] <siretart> I understand that it is for madwifi-old users only anyway
[02:00] <siretart> wb kel ;)
[02:00] <kelmo_lap> sorry, my sesion timed out
[02:00] <kelmo_lap> +s
[02:01] <kelmo_lap> _always_ happens mid-conversation
[02:01] <kelmo_lap> never when its quiet
[02:02] <siretart> gnar
[02:02] <siretart> f
[02:02] <siretart> why do you want to switch the headers from madwifi-old to madwifi-ng at all? I understand that we need the driver backend 'madwifi for madwifi-old users only anyway
[02:03] <kelmo_lap> siretart, i said yes, we should do exactly that, until madwifi-old is oldr than old, when it becomes madwifi-dead
[02:03] <kelmo_lap> soon it will be cactus ; )
[02:04] <kelmo_lap> siretart, but like i said before, i am extremely wary about supporting both madwifi and madwifi-ng private ioctls, like suggested in the new bug
[02:04] <siretart> kelmo_lap: even if it becomes dead, the header is gpl'ed, and it doesn't harm
[02:04] <kelmo_lap> siretart, i use madwifi-ng on 2.4.32
[02:04] <kelmo_lap> siretart, there is no wext there
[02:05] <siretart> kelmo_lap: I completly understand. and now there is the new fact, that madwifi-ng is happy with wext, so the bug report gets sort of 'invalid'
[02:05] <siretart> oh
[02:05] <siretart> but didn't you say that madwifi-ng would work with wext?
[02:05] <siretart> aah, not on 2.4. I see
[02:05] <siretart> hi Fuddl :)
[02:05] <Fuddl> hi siretart
[02:06] <kelmo_lap> siretart, yes i completely agree with you in some ways
[02:06] <kelmo_lap> siretart, but in other ways i take a different rtain of thought
[02:06] <kelmo_lap> s/rtain/train
[02:07] <kelmo_lap> siretart, as you can already see, I am already telling the reporter of the new bug that madwifi-ng supports wext, therefore no extra patching is required
[02:07] <kelmo_lap> siretart, but in a way, as a madwifi admin, i feel like madwifi-ng should have full support at some stage
[02:08] <kelmo_lap> siretart, just at the right time ; )
[02:08] <kelmo_lap> siretart, so thanks for your input, i think we can agree that since wext support is there, we can leave things as they are for now, ok?
[02:10] <siretart> kelmo_lap: I completely agree.
[02:11] <siretart> kelmo_lap: I suppose that there are still many users out there who don't want to switch to madwifi-ng (yet). I'd like to provide them with a working wpasupplicant as well
[02:11] <kelmo_lap> siretart, sure, but i don't like patches to support both
[02:11] <siretart> and for those who run madwifi-ng, there is wext. So only 2.4 users with madwifi-ng are in the cold, right?
[02:12] <kelmo_lap> siretart, no matter how good these patches are
[02:12] <kelmo_lap> siretart, because upstream already rejected such ideas
[02:12] <siretart> if upstream doesn't support that, we needn't either
[02:12] <kelmo_lap> good
[02:13] <kelmo_lap> siretart, 2.4 users, and users of <=2.6.13
[02:13] <kelmo_lap> will be "in the cold"
[02:13] <siretart> I think that should be the minority. or become the minority in the foreseeable future
[02:13] <siretart> we cannot satisfy everyone anyway
[02:14] <kelmo_lap> well, when madwifi-old ceases to exist, i will change my tune
[02:14] <kelmo_lap> my point was: this is happening much sooner than i anticipated
[02:17] <kelmo_lap> did ubuntu just commit some persistent net renaming to their udev package or so?
[02:20] <siretart> I think it is there for some time.. You may want to ask Scott (Keybuk) for that, he cares for udev
[02:49] <sivang> can anyplease check if he can install a package named "upbackup" ?
[02:49] <sivang> that's the HomeUserBackup package, that has been already uploaded 2 days ago but for some reason did not appear
[02:49] <sivang> it alreayd came out from NEW as I recived 'Accepted' message
[02:49] <sivang> anyone an idea?
[02:50] <freeflying> sivang: can not
[02:50] <sivang> freeflying: what do you get?
[02:51] <freeflying> sivang: no package
[02:52] <freeflying> sivang: seems it's atill in NEw queue
[02:53] <sivang> freeflying: I see
[02:53] <sivang> freeflying: thanks
[02:53] <freeflying> sivang:  :)
[03:44] <zakame> hi all
[04:18] <trappist> if I assign a bug to motu-reviewers, is motu-reviewers implicitly subscribed to the bug?  It doesn't seem to be getting any attention (bug 36051)
[04:58] <bddebian> Heya gang
[04:59] <bddebian> :-)  Hi Hobbsee
[04:59] <Hobbsee> :)
[04:59] <Hobbsee> this is a script, pretending to be hobbsee :P
[05:00] <bddebian> heh
[05:01] <Hobbsee> wish the script would find her phone, and figure out the correct time for the alarm though
[05:25] <Yagisan> G'day all
[05:30] <bddebian> Heya Yagisan, how's things?
[05:32] <Yagisan> bddebian: not to bad. short of cash though
[05:32] <bddebian> Yagisan: Who isn't? :-)
[05:46] <Yagisan> bddebian: looks like my ddns provider has disappeared tonight. damm that is annoying.
[07:11] <Amaranth> ooh, azureus
[07:14] <LaserJock> mutt doesn't come with an addressboook, right?
[09:00] <Spec> I have a .changes file I want to upload to my apt repository sitting elsewhere, I have dput set up to use scp, but when I do dput GANGES blah.changes, I get a traceback, for file in changes.dict['files'] .split('\n'):  KeyError: 'files'
[09:30] <webwolf_27> nothing going on here
[09:30] <LaserJock> webwolf_27: not much
[09:30] <webwolf_27> I noticed
[09:31] <webwolf_27> so now I'm gonna go check #mysql
[09:31] <crimsun> webwolf_27: most of us are in exams or working
[09:32] <webwolf_27> but say, there is a debian package that I want to port to breezy and dapper, who do I put in as the packager?
[09:32] <webwolf_27> crimsun, I done with exams, and haven't found a job yet :(
[09:32] <LaserJock> webwolf_27: you would probably just add a new changelog entry
[09:32] <crimsun> webwolf_27: it exists in debian but not in dapper?
[09:32] <crimsun> s/dapper/ubuntu/
[09:33] <webwolf_27> dapper I haven't checked yet but it's not in breezy
[09:33] <webwolf_27> avidemux
[09:33] <Gloubiboulga> it's in dapper
[09:34] <crimsun> Binary: avidemux
[09:34] <crimsun> Version: 1:2.1.2-0.0ubuntu1
[09:34] <crimsun> we just approved a uvfe for it, heh
[09:34] <webwolf_27> ok, and how do I get it for breezy
[09:34] <crimsun> take the dapper package and build it in a breezy pbuilder
[09:34] <crimsun> dapper srcpackage, that is
[09:36] <webwolf_27> crimsun, of course source package
[09:37] <webwolf_27> when I finnally get a few of my own projects finished I'll package them too
[09:39] <LaserJock> so I'm interested to see what happens with the SoC. I wasn't around for the last one but seem like a lot happened
[10:28] <phanatic> hi people
[10:29] <Gloubiboulga> hey phanatic :)
[10:29] <phanatic> hello Gloubiboulga :)
[10:35] <bddebian> Hello phanatic
[10:35] <phanatic> hey bddebian
[10:36] <LaserJock> hi bddebian
[10:40] <bddebian> Heya LaserJock
[11:02] <phanatic> hi raphink
[11:02] <raphink> hi phanatic
[11:04] <zul> bbl