[12:06] <haggai> herve: looking at why python-qt3 is uninstallable.  Seems it conflicts with the sip4-qt3 new version you uploaded
[12:07] <crimsun> haggai: it's due to the requirement on python2.4-sip4-qt3 (<< 4.2)
[12:07] <crimsun> haggai: I'm on it already :)
[12:07] <herve> yes :-(
[12:07] <crimsun> haggai: but --
[12:07] <crimsun> haggai: if you want to fix it, go ahead! :D
[12:07] <crimsun> (since I need it a fixed version to fix python-kde3 :-)
[12:07] <haggai> crimsun: ok, elmo pinged me about it.
[12:07] <crimsun> haggai: ok
[12:08] <haggai> crimsun: I don't have time to fix it, sorry too busy with kubuntu bugs
[12:08] <crimsun> haggai: ok
[12:11] <dholbach> tritium's xawtv was fine
[12:11] <dholbach> *rock*
[12:11] <dholbach> uploading
[12:11] <herve> rock even more!
[12:11] <herve> :-)
[12:12] <herve> good night all!
[12:13] <dholbach> good night herve
[12:13] <dholbach> thanks for being here
[12:13] <herve> haggai, that I can admit :-)
[12:15] <schweeb> MERGE ON PAIN OF DEATH lol
[12:18] <dholbach> we should try to be more serious about the list; i'll walk through the list again and check which packages we can really include and be confident about them
[12:18] <dholbach> it'll be a hard task for all of us
[12:19] <dholbach> but i spotted some nice things in there and if we manage to get the maintainers/upstream guys involved, breezy will rock even harder
[12:19] <dholbach> didnt we have someone with powerpc around? to get usbview going?
[12:20] <crimsun> dholbach: ajmitch_ has access to ppc
[12:21] <dholbach> the idea i had about http://people.ubuntu.com/~lamont/buildLogs/Test/u/usbview/1.0-6/usbview_1.0-6_20050328-0655-powerpc-failed isnt nice, but i'd include a patch with the changes of rerunning aclocal and automake
[12:21] <dholbach> that could make it work again
[12:24] <ajmitch_> dholbach: I haven't had time to install ubuntu on the mac
[12:24] <ajmitch_> partly because it's not mine :)
[12:24] <dholbach> ajmitch_: don't worry
[12:24] <dholbach> ajmitch_: i think koke and jbailey had one
[12:24] <dholbach> someone who would take his time in the next days to walk with me through the kernel-packages in universe in the next days?
[12:25] <ajmitch_> jbailey has a pegasos ppc iirc
[12:25] <schweeb> dholbach: what do you need exactly?
[12:25] <jbailey> Yup
[12:25] <dholbach> jbailey: we were discussing http://people.ubuntu.com/~lamont/buildLogs/Test/u/usbview/1.0-6/usbview_1.0-6_20050328-0655-powerpc-failed
[12:25] <jbailey> Someone had me look at usbview yesterday...
[12:26] <dholbach> jbailey: and i said that a patch with the changes of rerunning aclocal and automake wouldnt be nice, but could work
[12:26] <dholbach> ah...
[12:26] <tritium> hi dholbach.  Looks like you uploaded xawtv for me :)
[12:26] <dholbach> tritium: yeah... good work
[12:26] <tritium> Thanks, dholbach :)
[12:26] <jbailey> dholbach: You need to add AUTOMAKE_OPTIONS=foreign, and then autoreconf -f -i, and the package is otherwise fine.
[12:27] <jbailey> dholbach: A simpler solution for now is to not have automake loaded in the chroot.
[12:27] <jbailey> Why is it there>
[12:27] <dholbach> jbailey: dunno
[12:27] <jbailey> dholbach: I think the rebuild methodology is a bit bogus.  Having random versions of automake presence is a good way of cuasing grief.  It's one of the suckages of automake.
[12:28] <dholbach> yes
[12:28] <jbailey> You can solve it by setting maintainer-mode in the packages, but that's way more work.
[12:28] <dholbach> jbailey: thanks for elaborating
[12:28] <jbailey> When I argued against maintainer mode ages ago, I hadn't understood what kind of nightmare we were going to see.  I'd love to see it always in and disabled, with an option to enable it.
[12:28] <jbailey> But either way, I don't know who maintains automake these days.
[12:29] <dholbach> jbailey: must be quite a lot of people :-)
[12:29] <jbailey> dholbach: np.  Anything else you need while I'm here?
[12:29] <dholbach> so now... who fixes usbview? ;-)
[12:29] <tseng> HI DHOLBACH
[12:29] <dholbach> HEY TSENG!
[12:29] <schweeb> dholbach: what are you lookin to do with kernel-packages?  I'm willing to help
[12:29] <dholbach> jbailey: not from my side... thanks for replying so fast :-)
[12:29] <jbailey> dholbach: The current version is in the archive, this is only a failure from the rebuild.
[12:29] <StoneTable> hey tseng, just the person I was looking for.  You're working on mono 1.1.5, right?
[12:30] <jbailey> dholbach: I'd be inclined to ignore the problem, given that there are probably real bugs to chase.
[12:30] <koke> dholbach: I'm trying...
[12:30] <dholbach> jbailey: alright
[12:30] <dholbach> jbailey: will there be a cdbs-bof in .au? :-)
[12:30] <jbailey> dholbach: I don't think so.  I thought about it after I heard the the bof schedule was frozen.
[12:30] <dholbach> schweeb: there are LOADS of packages that won't work anymore, aren't installable
[12:31] <jbailey> dholbach: Hopefully there'll be a bit of free time around drinks or something to preview cdbs2 and answer questions about cdbs1.
[12:31] <dholbach> yeah cool
[12:31] <dholbach> i'd very much look forward to that one
[12:31] <schweeb> dholbach: well, count me in, as long as I don't have to demolish my system doing so :)
[12:31] <schweeb> cdbs rules.
[12:31] <schweeb> very very much
[12:31] <dholbach> schweeb: we should focus on the last debian packages and weed out, what we don't need
[12:31] <jbailey> dholbach: If you want something more than that, I don't know who to ask, really.  I haven't thought much about UDU.
[12:31] <dholbach> schweeb: thank you very much
[12:32] <dholbach> jbailey: i can imagine
[12:32] <schweeb> dholbach: we have a list of those kernel packages that have problems?
[12:32] <dholbach> schweeb: wiki/UniverseUnmetDeps
[12:32] <schweeb> ah
[12:32] <dholbach> schweeb: http://archive.ubuntu.com/ubuntu/pool/universe/k/ should give you an idea as well
[12:33] <schweeb> so we wanna get rid of stuff like m68k and shit?
[12:33] <jbailey> dholbach: http://www.ubuntulinux.org/wiki/UbuntuDownUnderBOFs seems to be the list.  I thought I heard that the list was frozen, but I don't see anything here indicating that.
[12:33] <dholbach> schweeb: yes
[12:34] <jbailey> dholbach: If you want a formal cdbs bof, could you add it, with some notes as to what you want to get out of it?  (training, improvements, a chance to treat one of the authors as a piata...)
[12:34] <dholbach> jbailey: i guess there'll be a lot of last-minute-bofs or discussions-that-anybody-is-interested
[12:34] <jbailey> dholbach: As full as the schedule is sounding, I'm not sure there will be.
[12:35] <dholbach> piata?
[12:35] <dholbach> hrm
[12:35] <dholbach> jbailey: you're right... for one week
[12:35] <jbailey> dholbach: http://en.wikipedia.org/wiki/Pinata
[12:36] <dholbach> ahhhhh coool :-)
[12:36] <jbailey> You're sounding a little too eager on that one...
[12:36] <dholbach> jbailey: i guess there'll be a lot of interested guys and we'll have our fun, even if it's not on the schedule
[12:36] <dholbach> it shouldnt be toooo official either ;-)
[12:39] <koke> http://www.mikesjournal.com/images/Pinata%201.jpg <-- quite graphic :P
[12:41] <dholbach> :-)))
[12:44] <schweeb> dholbach: I say we just drop all the kernel stuff that doesn't work :)
[12:44] <tritium> tons of packages given back
[12:52] <koke> http://www.amedias.org/~koke/debian/hoary/usbview_1.0-6ubuntu1.diff.gz
[12:52] <koke> I'm building now...
[01:02] <nictuku> i'm not really familiar with "version changes" in debian packages. I mean, I don't know what to update besides debian/changelog
[01:03] <dholbach> you said debian/rules would have to be changed
[01:03] <nictuku> sure
[01:03] <nictuku> but I'd have to update debian/changelog to explain what was changed.
[01:03] <dholbach> yes
[01:03] <dholbach> dch -i -Dhoary is most easy
[01:04] <nictuku> hmm what package provides dch?
[01:05] <dholbach> devscripts
[01:05] <nictuku> thank you.
[01:08] <nictuku> hmm.. how do I create the source package after I've made the changes?
[01:11] <dholbach> with debuild
[01:13] <nictuku> I didn't know even that MOTU existed. great idea
[01:13] <schweeb> bbiaf
[01:33] <dholbach> lamont: you know why http://people.ubuntu.com/~lamont/buildLogs/Test/g/gpm/1.19.6-19ubuntu1/ was only built on amd64 and powerpc?
[01:35] <nictuku> guys
[01:36] <lamont> dholbach: likely the result of one or more of the issues I was fighting in the DC.  FWIW, a fresh hoary-test run is starting, and I'll be grumbling if anyone mentions logs predating somewhere < now (really about 10-40 minutes)
[01:36] <nictuku> now I have the source package, what's next? sign it?
[01:36] <lamont> otoh, if it failed > 18:57, it's probably gonna fail again
[01:36] <dholbach> lamont: ack
[01:36] <nictuku> I mean, somebody signing my key...
[01:37] <lamont> nictuku: and you tweaked the version to end with ubuntu1, yes?
[01:37] <dholbach> nictuku: if you want to thoroughly help us out, you'll (at some stage) have to have a nicely signed key
[01:37] <dholbach> nictuku: having a good signed key is always GOOD, but before you upload your own packages to ubuntu, some guys will have to review them
[01:43] <nictuku> lamont: hmm actually, no.
[01:43] <lamont> 1.2-3 is followed by 1.2-3ubuntu1 :-(
[01:44] <lamont> because otherwise, you conflict with the other guy building 1.2-4, and that'd be bd.
[01:44] <lamont> bad
[01:44] <nictuku> yeah I got it.
[01:44] <nictuku> how can I have my key signed? I live in Brazil, btw.
[01:45] <lamont> where in brazil
[01:45] <lamont> ?
[01:45] <nictuku> Goiania, state of Goias
[01:45] <lamont> hrm.. no clue where that is.. second
[01:46] <dholbach> you could talk to guys on http://nm.debian.org/gpg_offer.php
[01:46] <dholbach> but i'm not sure how far you'd have to travel
[01:46] <nictuku> been there, no one near me. not even close.
[01:47] <nictuku> In debian, they would sign a key in extreme cases, if one sends a scanned version of its real ID or drivers license...
[01:48] <lamont> and Fortaleza, Curitiba, Recife, Sao Paulo all far away?
[01:48] <dholbach> nictuku: http://www.ubuntulinux.org/wiki/UnsignedGpgKey
[01:48] <nictuku> very far.
[01:48] <lamont> nictuku: is really a mako question -he's got connections _everywhere_.
[01:48] <nictuku> :)
[01:49] <dholbach> anyway... while you're working towards a gpg key and really want to help out, you will have to have us review packages and upload them for you :-)
[01:50] <nictuku> yep. where should I send the diff file to?
[01:50] <nictuku> about wiki/UnsignedGpgKey - biglumber didn't help either.
[01:51] <nictuku> I'm not in a hurry to do that, though. I can wait till I meet with a dd (that happens sometimes in events)
[01:51] <dholbach> nictuku: you have access to some webspace where you could add .diff.gz .orig.tar.gz and .dsc ?
[01:52] <nictuku> yes. wait a second, please.
[01:52] <dholbach> nictuku: next step: add the link to it on wiki/MOTUTodo ("to review" section)
[01:52] <dholbach> someone will get in touch with you, when he finds the time
[01:52] <dholbach> and hey... thanks for helping out :-)
[01:54] <nictuku> nah, I'm the one grateful here! :)
[01:56] <dholbach> so we're all glad in here :-)
[01:56] <dholbach> ok... i'll go for the last walk tonight and get murphy out
[01:56] <dholbach> good night
[02:05] <nictuku> night
[02:05] <tritium> good night dholbach
[02:08] <dholbach> bye tritium, nictuku
[02:09] <nictuku> is this currently accessible? http://www.grupomabel.com.br/ubuntu/
[02:13] <fredix> hu
[02:13] <fredix> hi
[02:19] <fredix> where i can report a bug for universe ?
[02:22] <nictuku> maybe http://bugzilla.ubuntu.com/ ?
[02:22] <Burgundavia> no
[02:22] <fredix> not for universe
[02:22] <Burgundavia> launchpad.ubuntu.com/malone
[02:24] <diamond> dredg: morning.
[02:26] <fredix> someone know who upload libgtk-trayicon-ruby into universe ?
[02:27] <nictuku> can anybody see an explanation for the wontfix in debian #242066?
[02:28] <nictuku> oh i found it
[03:38] <tritium> crimsun, how are things?
[03:38] <crimsun> not too bad
[03:38] <crimsun> just uploaded python-qt3, have to wait for it to build so I can fix python-kde3 :)
[03:38] <crimsun> yourself?
[03:38] <tritium> congratulations!
[03:39] <crimsun> small fries compared with universe :/
[03:39] <tritium> dholbach reviewed xawtv, and it's already uploaded and built just fine
[03:39] <tritium> thanks for offering earlier
[03:39] <crimsun> yep, read above.  Great!
[03:39] <tritium> thanks
[03:40] <crimsun> yeah, sorry about the lag, I had been called away and wasn't able to even finish python-qt3 til now
[03:40] <tritium> no, don't even worry about it.  It's fine.
[03:45] <StoneTable> What should I do when I come across a package that won't build, due to api changes?  Looks like gnome-alsamixer is busted.  Upstream is broke, and doesn't look like it's been touched since the middle of last year
[03:53] <crimsun> StoneTable: personally, it's a morgue candidate
[03:53] <StoneTable> sunds like a plan to me.
[03:53] <crimsun> StoneTable: gnome's Volume Control (in 'gnome-media')) already provides the functionality through gst's mixer
[03:54] <StoneTable> yeah, maybe that's why it's been abandoned
[03:56] <diamond> newbie question here, looking at packages in UniversePriorityList, some of them don't build purely because apt isn't accepting unauthenticated dependancy packages,
[03:56] <diamond> how does that get fixed? the maintainer tweaks the build env?
[03:56] <crimsun> none of them should build if you're using pbuilder
[03:57] <crimsun> you have to add an explicit configuration
[03:57] <diamond> crimsun: for example, putty is listed on that page as failing, but builds fine here in pbuilder with the steps provided in the pbuilder howto wiki entry
[03:58] <crimsun> diamond: if it builds fine for all 4 arches, then note it as done
[03:58] <crimsun> (add a note)
[03:59] <diamond> wait. i'm a moron, sorry. i've mixed up amd64 and ia64.
[04:00] <diamond> looking at the build logs now, it appears to have build successfully on i386, ppc, amd64 and ia64 (which i presume are the four arches).
[04:00] <crimsun> yes, I was just about to say that.
[04:01] <diamond> so, the maintainer will presumably take care of updating the UniversePriorityList, and i should go pick a different broken package, right?
[04:02] <diamond> (apologise for the flood of painfully unsure questions ,-)
[04:02] <diamond> *apologies
[04:02] <schweeb> hooray
[04:02] <tritium> diamond, the maintainer may not be aware of the UniversePriorityList
[04:02] <schweeb> my Samba migration went about as good as possible
[04:02] <tritium> what's up schweeb ?
[04:02] <tritium> ah, cool
[04:02] <schweeb> howdy
[04:02] <schweeb> I'll just say that WINS sucks.
[04:03] <diamond> tritium: ah. what can i do then? apt-cache show putty says the maintainer is Colin Watson (@debian.org).
[04:04] <schweeb> colin watson = Kamion :)
[04:04] <tritium> yeah, you could tell him I guess
[04:04] <schweeb> although why you would run putty on linux...
[04:04] <tritium> no idea...
[04:04] <diamond> schweeb: i use it elsewhere, mainly for pterm, the terminal emulator.
[04:04] <diamond> schweeb: it's fast, and pretty bug-free
[04:05] <diamond> schweeb: gnome-terminal for example is paaaainfully slow on my p3-800 in work
[04:05] <crimsun> I'd use rxvt-unicode then ;)
[04:05] <StoneTable> <3 aterm
[04:05] <schweeb> aterm or Eterm
[04:05] <diamond> crimsun: aye, utf8 support is a must, but i've had issues with rxvt too. basically, every terminal emulator sucks (just like osen -), pterm just sucks a little less
[04:06] <schweeb> although I'm using gnome-terminal currently out of laziness...
[04:06] <diamond> i have a friend tho who had to resort to using putty on his box because openssh couldn't get past his router.
[04:06] <diamond> t'was a really weird issue
[04:06] <crimsun> diamond: well in my case I was using zsh, which has issue with utf-8
[04:06] <crimsun> err, issues
[04:07] <diamond> as i was saying before i so rudely interrupted myself,
[04:07] <diamond> it eventually turned out that openssh was setting some QOS bits for some of it's inital packets,
[04:07] <tritium> It's hard to pick a package to fix.  It does seem like some failed to build only because build-dependencies weren't available in some cases.
[04:07] <diamond> and his router, being a cheap piece of crap, was dropping on them
[04:07] <diamond> tritium: indeed
[04:07] <diamond> s/on//
[04:07] <tritium> (e.g. octave2.1 on ia64)
[04:08] <schweeb> * on ia64
[04:08] <tritium> indeed
[04:08] <diamond> if anyone has any favourite packages that aren't building on amd64, i'm willing to have a poke
[04:08] <tritium> cool, diamond.  Thanks.
[04:09] <tritium> You could look at vpnc.  It seems to be failing to build only on amd64, if I recall correctly
[04:10] <diamond> tritium: just checking the logs now, it looks like everything except ppc is currently building
[04:10] <tritium> no, looks like it built, actually
[04:10] <tritium> yeah, that's new status info on that
[04:10] <diamond> for that matter, i can poke i386 and ppc stuff too, but i'm guessing there are more people around with those platforms
[04:11] <schweeb> yea, most of us have i386 :)
[04:11] <diamond> amd64 is the way of the future i tell you -)
[04:12] <crimsun> ppc64 :)
[04:12] <diamond> either that or i've just bought myself a rather expensive flop
[04:12] <schweeb> I'll reserve my judgement for when I actually own one
[04:12] <diamond> er. pun unintented, obviously.
[04:12] <schweeb> I'm pretty happy with i386
[04:14] <diamond> schweeb: tbh, i switched mainly because i was looking for a new machine, and amd are selling the 64-bit athlons as their main line now
[04:14] <schweeb> yea
[04:15] <tritium> crimsun, you have a G5?
[04:15] <diamond> right. mr. watson mailed re: putty.
[04:16] <schweeb> okay, I'm gonna go through and start moving stuff where the only platform it doesn't build on is ia64...  should I add a new page with DoesNotBuildIA64, or should I just put them in the comments section on the UniversePriorityList?
[04:16] <tritium> he's in #ubuntu-devel, you probably could have talked to him in real-time
[04:17] <diamond> tritium: ah hah. right. i scanned the channel list here, didn't think of poking in there.
[04:17] <tritium> so what did he tell you?
[04:17] <schweeb> anyone have an opinion?  ia64 does not build, new page, or add to comments
[04:18] <tritium> schweeb, my bet is that dholbach (and everyone else) trusts you enough to do what you feel is best
[04:18] <schweeb> alright :)
[04:18] <tritium> not that I have any say in the matter, but I know you do good work
[04:19] <crimsun> (yes, DoesNotBuildIA64 was mentioned before.  Go for it.)
[04:19] <crimsun> tritium: access to, yes, not personally (unfortunately)
[04:20] <tritium> crimsun, I see.  It turns out, my hard-drive problems were fixed with an fsck, but I'm still considering a new machine.
[04:20] <crimsun> tritium: ah!  Well, at least that's good news.
[04:20] <tritium> Yeah, it was!
[04:21] <tritium> I wouldn't mind seeing a G5 powerbook come out next month with OS X 10.4, but there's no indication of that happening.
[04:24] <StoneTable> my wife is dreaming of a g5 powerbook
[04:24] <StoneTable> my pocketbook, however, is not ;)
[04:24] <tritium> heh
[04:28] <diamond> tritium: told me to go ahead and update the page, putty is now moved to the 'done' section.
[04:29] <tritium> diamond, congrats
[04:29] <diamond> tritium: well, t'was he that fixed it, i did nothing only notice and tell him -)
[04:30] <tritium> well, it's still a good thing :)
[04:31] <diamond> true
[04:34] <crimsun> back later, need go to for a run.
[04:34] <crimsun> err, word order switch.
[04:35] <tritium> see you crimsun
[04:36] <tritium> cool, a fellow runner :)
[04:39] <schweeb> nice
[04:39] <schweeb> lots of these ia64 only bugs seem to just be buildd problems
[04:40] <schweeb> might be able to clear up a bunch of bugs tonight
[04:40] <tritium> that would be way cool
[05:09] <wasabi_> So are we still accepting new packages to universe for hoary?
[05:11] <tritium> wasabi_, I tend to doubt it at this point
[05:16] <schweeb> jeeze this ia64 buildd is messed up a good portion of the time it seems
[05:18] <tritium> schweeb, are you putting that list together by hand?
[05:26] <schweeb> yep
[05:26] <schweeb> I'm looking at the buildlogs and determining the general problem too
[05:26] <schweeb> so it can't be scripted
[05:27] <tritium> fun
[05:27] <schweeb> gotta be done
[05:28] <schweeb> this stuff would be way better if it was in a database and you could query for certain attributes
[05:40] <lamont> schweeb: the dev/null antics were all over, but ia64 had more stuff to do when it started hitting the fan
[05:40] <lamont> ditto ppc
[05:40] <lamont> and then there was the fact that one of the ia64 buildd's wasn't really happy, iirc, which meant it went flying through the packages vomiting
[05:48] <schweeb> lamont: well, I'm compiling a list of stuff that needs to be kicked for you on ia64
[05:49] <lamont> schweeb: uh, everything got kicked.
[05:49] <schweeb> oh
[05:49] <schweeb> :-/
[05:49] <schweeb> are the logs going into Test still?
[05:49] <lamont> Total 27 package(s) in state Building.
[05:49] <lamont> Total 1468 package(s) in state Needs-Build.
[05:49] <lamont> Total 3 package(s) in state Uploaded.
[05:49] <lamont> Total 1498 package(s)
[05:49] <lamont> yes
[05:49] <lamont> but atm, it's just main.
[05:49] <schweeb> you mean just main that's building?
[05:50] <lamont> that'll take 6-8 hours or more to finish, and then we just have to convince elmo to reimport universe
[05:50] <lamont> main always beats universe in the build ordering
[05:50] <schweeb> right
[05:50] <lamont> just as universe beats multiverse
[05:50] <diamond> hum. i'm beginning to suspect a gcc/libc6 but is causing this problem with snacc on amd64
[05:51] <diamond> *bug
[05:51] <lamont> so the fact that only main is in the test repository doesn't really affect things until it finishes...
[05:51] <lamont> diamond: that or it's doing something stupid like casting between pointers and int's...
[05:52] <schweeb> lamont: well, I'm at least compiling a list of stuff that's only wrong on ia64 right now :)
[05:52] <diamond> lamont: the point at which it crashes is definetely safe,
[05:52] <diamond> lamont: but Weird Stuff appears to be happening.
[05:52] <schweeb> unclutter the PriList a bit
[05:52] <tritium> hmm, I just got qemu to build without modification
[05:53] <lamont> hrmpf no nice neat warnings-that-are-really-errors
[05:53] <tritium> I'll double-check...
[05:53] <lamont> schweeb: coolness
[05:53] <diamond> lamont: heh, aye -)
[05:53] <lamont> diamond: interesting
[05:53] <tritium> not at first glance
[05:54] <diamond> lamont: the code does, basically:   long int t; printf("%s",ctime(&t));
[05:54] <diamond> lamont: and strlen inside printf (well it's actually fprintf, but no matter) barfs
[05:55] <lamont> diamond: and there's a #include <time.h>, I expect
[05:55] <diamond> er. i left out the 't=time(NULL)' bit -)
[05:55] <lamont> wonder if making that say 'time_t t' helps
[05:55] <diamond> lamont: i checked the headers, time_t == long int
[05:56] <lamont> yeah
[05:56] <diamond> hum. you know, you're right. time.h ain't included.
[05:57] <lamont> that could matter
[05:57] <diamond> whaddya know, i think it's actually building now ,-)
[05:57] <diamond> i blame the 5am time for me not having checked that
[05:58] <lamont> only 9PM here. :-)
[05:58] <diamond> bing. that fixed it!
[05:58] <diamond> lamont: cheers for the hint
[05:58] <diamond> wooo
[05:59] <diamond> right. i'm a newb. where do i go from here? i have a patch...
[05:59] <diamond> (and yeah, it's a oneliner ,-)
[06:00] <lamont> diamond: and I presume that you're not in the universe-uploaders keyring
[06:00] <diamond> lamont: no, i'm not
[06:01] <schweeb> lamont: so are all arches being rebuilt from source again, then?
[06:01] <diamond> dredg can vouch for who i am, apart from that...
[06:01] <lamont> hrm....  /me isn't sure of the actual process either...
[06:01] <diamond> lamont: heh heh, k.
[06:01] <lamont> schweeb: yes
[06:01] <schweeb> diamond: you'll have to wait till one of the MOTUs are around
[06:02] <schweeb> lamont: an MOTU reviews it and uploads it if satisfactory :)
[06:02] <lamont> schweeb: yeah.  that much I knew
[06:02] <schweeb> that's about it, heh
[06:02] <lamont> then there's the issue of email addr whitelisting, etc, etc,etc.
[06:02] <schweeb> ah, yes
[06:03] <diamond> schweeb: right
[06:03] <lamont> I mean, I could upload it, but that would feel like , dunno, cheating somehow...  we should give diamond the proper visibility with the MOTU's
[06:03] <schweeb> elmo should just make a web form to whitelist :)
[06:03] <schweeb> right
[06:04] <diamond> lamont: aye, i'd like to work towards motu-ship
[06:04] <lamont> schweeb: is just email to elmo to do it, yes?
[06:04] <schweeb> oh
[06:04] <schweeb> I just poked him in IRC :)
[06:04] <lamont> well, that too
[06:05] <schweeb> all the whitelist gains for you is emailing you if you're in the Changed-By header, right?
[06:05] <lamont> diamond: in that case, you probably want to send email to james.troup@ubuntu.com, or poke elmo in irc, and ask him to add your email addr to the whitelist.  Then, as you build source packages, you will get the nice email from the installer, etc.  and your name will be in the changes mail that goes to everyone and their mother.
[06:05] <lamont> schweeb: and the visibility that goes with it
[06:06] <lamont> then we know we've been seeing your work... otherwise it just comes from 'Ubuntu installer'
[06:06] <lamont> and we don't readily know who did the changes...
[06:06] <schweeb> oh
[06:06] <lamont> admittedly, that's just reading the From: header in the mail, rather than the Changed-By field inside the body
[06:06] <diamond> lamont: cool.
[06:06] <schweeb> my stuff has all been Ubuntu Installer so far I think....  but I think that was before I was whitelisted
[06:07] <lamont> once whitelisted, you should appear as the From address
[06:07] <lamont> (yes, katie forges email.  so?)
[06:07] <schweeb> lol
[06:09] <lamont> diamond: see also http://www.ubuntulinux.org/wiki/DeveloperResources
[06:09] <tritium> lamont, qemu sure appears to have built correctly on i386.  The log appears to indicate there were unsatisfied build-deps when the buildd made its attempt
[06:10] <lamont> tritium: le huh?  URL?
[06:10] <tritium> http://people.ubuntu.com/~lamont/buildLogs/Test/q/qemu/0.6.1-1/qemu_0.6.1-1_20050327-1915-i386-failed
[06:11] <lamont> is missing zlib1g-dev build-dep
[06:11] <tritium> looks that way, yet it built
[06:11] <lamont> now, whether that should be a direct build-dep:, or some other package is missing a Depend:, remains as a question
[06:12] <tritium> it's in the control file
[06:12] <lamont> what's in the control file?
[06:13] <tritium> zlib1g-dev
[06:13] <lamont> when it built for the archive in november, something Depended: on zlib1g-dev
[06:13] <tritium> (as a build depend)
[06:13] <tritium> Yes, qemu
[06:13] <lamont> Build-Depends: cdbs, debhelper (>= 4.1.0), libx11-dev | xlibs-dev, libsdl1.2-dev (>> 1.2.1), texi2html, sharutils, libgpmg1-dev | not+linux-gnu
[06:14] <lamont> and it clearly needs a Build-Depends: zlib1g-dev
[06:14] <lamont> since it references -lz directly (Makefile, Makefile.target)
[06:14] <tritium> Build-Depends: cdbs, debhelper (>= 4.1.0), libx11-dev | xlibs-dev, libsdl1.2-dev (>> 1.2.1), texi2html, sharutils, libgpmg1-dev | not+linux-gnu, zlib1g-dev
[06:14] <tritium> (that's what I have here)
[06:14] <tritium> no modification
[06:15] <lamont> and what does head debian/changelog say?
[06:15] <tritium> heh, ajmitch fixed it today ;) sorry
[06:15] <lamont> thank you
[06:15] <tritium> sorry for the bother
[06:15] <lamont> no
[06:16] <lamont> np
[06:16] <lamont> damn keyboard
[06:16] <lamont> typing break
[06:19] <tritium> I just assumed it hadn't been fixed since it wasn't in the "Done" section of UniversePriorityList.  My bad.
[06:20] <lamont> workrave and I haven't agreed in the past
[06:20] <schweeb> hehe
[06:20] <schweeb> I've never tried it
[06:21] <schweeb> does it actually prevent you from typing after a certain point, or can you circumvent it?
[06:21] <lamont> you can tell it to let you postpone or not
[06:21] <lamont> hence knowing that i need to take a break... had postponed it a few times already
[06:25] <schweeb> wooo
[06:25] <schweeb> almost done with the first 50%
[06:28] <schweeb> and I just remembered I should go to sleep soon
[06:28] <diamond> schweeb: sleep is good.
[06:29] <schweeb> diamond: I know better than most
[06:30] <diamond> ah. ouch. i'm the exact opposite
[06:30] <diamond> well, no. i guess the exact opposite is someone who is asleep all the time and wakes up at random intervals ,-)
[06:31] <schweeb> I only have problems in class and watching TV really
[06:31] <schweeb> so, it's not so bad
[06:31] <diamond> i'm currently on a month off from work due to a sleep disorder
[06:31] <diamond> so i decided i'd help out with ubuntu with my spare time, heh.
[06:32] <schweeb> good call.
[06:33] <tritium> wow, diamond
[06:35] <diamond> interdiff! what a wonderful program. (that i've only just found out about -)
[06:36] <diamond> tritium: i'm supposed to be doing a research postgrad in computer science, but the last 6 months have been completely unproductive due to lack of sleep, so between that and the stress of not getting anything done, it was agreed i'd take off for a month. they even offered to still pay me for the time off, which i gladly accepted
[06:36] <tritium> diamond, post-doc?
[06:36] <diamond> 'course i'm supposed to be trying to set up a regular sleeping pattern, but i'll start that tomorrow, right? -)
[06:36] <diamond> tritium: nah, just a lowly masters
[06:37] <tritium> diamond, don't say "lowly".  That's an awesome accomplishment.
[06:37] <tritium> That's nice that they'll pay you :)
[06:37] <diamond> tritium: it will be if i ever finish it (or tbh, start it properly)
[06:37] <diamond> tritium: yeah, they're very supportive.
[06:38] <tritium> diamond, that's good.  I hope you'll take good care of yourself in the month you have off.
[06:38] <schweeb> lamont: what bout packages that say ia64 isn't in their arch list... should they be fixed and reuploaded, or what
[06:38] <tritium> We'll support you fully in your recovery!
[06:39] <lamont> schweeb: depeends.
[06:39] <schweeb> http://people.ubuntu.com/~lamont/buildLogs/Test/d/dfsbuild/0.6.17/dfsbuild_0.6.17_20050325-0106-ia64-failed
[06:39] <diamond> tritium: cheers -)
[06:39] <lamont> generally speaking, the answer to that question is either (1) fix the package and upload, (2) live with it, or (3) edit PaS to exclude the package from the build on that architecture
[06:39] <tritium> :)
[06:40] <schweeb> lamont: k
[06:41] <lamont> schweeb: and that particular package is probably (3)
[06:41] <lamont> or (2)
[06:41] <lamont> since (1) is beyond the scope of the current exercise
[06:41] <tritium> crimsun, how was the run?
[06:41] <lamont> schweeb: as in, (1) involves actually finishing the _port_ of the package to ia64.
[06:41] <crimsun> tritium: not too bad, thanks
[06:41] <schweeb> heh
[06:42] <schweeb> and me no havey ia64
[06:43] <lamont> schweeb: neither does hoary. :-)
[06:44] <schweeb> are installer CDs even generated for ia64?
[06:44] <lamont> schweeb: yes, but not as of 3/28
[06:44] <lamont> and not in the release directory
[06:44] <tritium> doko, ping
[06:44] <lamont> server install works, desktop is really close, last I heard
[06:44] <lamont> right
[06:45] <schweeb> is ia64 eventually gonna be a target arch, or is it just kinda bonus?
[06:45] <schweeb> I hear fabbione has a soft spot for sparc and has an unofficial buildd for that too ;)
[06:47] <diamond> right. i'm a little lost. i've fixed a couple of bugs in a package (snacc). i've made a patch. how do i go about incorporating this patch into the ubuntu.diff.gz so that i can test the entire build using pbuilder?
[06:48] <schweeb> which files did you patch?
[06:48] <schweeb> if they're in debian/ then the methodology is different than if they're in the actual source
[06:48] <diamond> schweeb: they're in the actual source
[06:49] <tritium> diamond, do you use cdbs for your rules file?
[06:49] <schweeb> you'll wanna look at incorporating dpatch into your rules file
[06:49] <tritium> I use simple-patchsys with cdbs
[06:49] <crimsun> (cdbs makes patching a cinch!)
[06:49] <diamond> schweeb: ah. right
[06:50] <schweeb> yea, cdbs rules
[06:50] <schweeb> tritium: dpatch has dependencies and stuff I believe
[06:50] <diamond> right, i'll look at that so. however, from what i understand,
[06:50] <schweeb> like, inter-patch deps
[06:50] <tritium> schweeb, probably.  I know very little about dpatch
[06:50] <diamond> nm. i'll go read first. ask confused questions later. -)
[06:50] <schweeb> and a few other benefits I can't list ATM
[06:51] <schweeb> it's only a little bit harder to use dpatch than simple-patchsys
[06:51] <crimsun> just tell cdbs to grok your debian/patches/
[06:53] <tritium> anybody know if doko is working on python-gnome?
[06:55] <schweeb> okay, I'm done for the night
[06:55] <schweeb> https://www.ubuntulinux.org/wiki/DoesNotBuildIA64
[06:55] <tritium> Good night schweeb
[06:55] <diamond> schweeb: nite
[06:56] <crimsun> night, schweeb
[06:56] <schweeb> there are some packages at the bottom that are all the way fixed on all arches
[06:56] <tritium> nice work, schweeb!
[06:56] <crimsun> tritium: do you mean the source package 'gnome-python'?
[06:56] <schweeb> if someone wants to go through and remove them, please do
[06:56] <tritium> crimsun, yes, from the UniversePriority list
[06:56] <schweeb> (from the UniversePriorityList)
[06:57] <tritium> looks like he fixed it up for the python transition at least
[06:57] <crimsun> hmm.  It built on 7 Marrch
[06:58] <schweeb> I'm guessing after the Test archive gets resynced, we'll probably want to entirely regenerate these lists... it'll probably be easier
[06:58] <tritium> probably
[06:59] <tritium> crimsun, I'm looking at the Logs linked to from UniversePriorityList for python-gnome
[06:59] <tritium> failed as recently as 27th
[06:59] <crimsun> hmm!
[07:03] <tritium> This is odd, considering python-dev (>=2.4) Build-Depends:  checking if Python version >= 1.5.2... configure: error: too old
[07:04] <crimsun> k, I'll pull the source
[07:07] <tritium> ok, thanks
[07:11] <crimsun> I'm pretty sure that's a hiccup - it just built fine here (unchanged).
[07:11] <tritium> really?  not here...
[07:12] <tritium> thanks for checking it
[07:12] <crimsun> hmm, when did you last update your pbuilder?
[07:12] <crimsun> I updated mine just before I threw the .dsc at it
[07:12] <tritium> earlier tonight, but I'll do it again now
[07:19] <tritium> gee, still failed after I updated pbuilder.
[07:21] <crimsun> hmm, i386, correct?
[07:21] <tritium> yeah
[07:21] <crimsun> could you post your config.log somewhere?
[07:21] <tritium> sure, one sec
[07:24] <tritium> crimsun, I can't find a config.log
[07:24] <crimsun> configure.log?
[07:25] <crimsun> sorry, my brain's fuzzy, so I probably misstated it
[07:26] <tritium> sorry, the build log?
[07:27] <crimsun> just the log of configure running up until it fails
[07:28] <lamont> tritium: it doesn't check for python2.4, just 2.3 down to 1.5.2, I bet
[07:28] <lamont> that or it fails to Build-Depend: python
[07:28] <crimsun> it does b-d on python (>= 2.4)
[07:28] <lamont> since python2.4 nor python2.4-dev Depends python.
[07:28] <lamont> hrm
[07:29] <crimsun> and python2.4 is passed explicitly to ./configure
[07:29] <crimsun> and I built it successfully on a P4 here just a few minutes ago, so this is an odd one
[07:29] <lamont> then you'll want that config.log from the build tree
[07:29] <tritium> crimsun, when I run pbuilder, I don't know how to find the configure logs.  I only know how to save a build log.
[07:30] <crimsun> tritium: use login
[07:30] <tritium> ok
[07:30] <crimsun> invoke debian/rules manually, check config.log
[07:31] <tritium> thanks
[07:31] <crimsun> np
[07:37] <tritium> is there an easy way to copy the file out of the chroot?
[07:38] <crimsun> just copy it as a user out of the /tmp/foo
[07:39] <crimsun> (or use --save-after-login)
[07:39] <tritium> ok
[07:41] <tritium> I'm too inexperienced with chroots.  I don't see anything in /tmp, so I'll try the --save-after-login
[07:48] <diamond> tritium: i think pbuilder uses /var/cache/pbuilder
[07:49] <tritium> diamond, yeah, thanks.
[07:49] <tritium> crimsun, sorry for the delay: http://mip-lab4.ecn.purdue.edu/~rimbert/config.log
[07:50] <readingboy> hello everyone
[07:50] <diamond> morning
[07:50] <tritium> hello
[07:50] <readingboy> this is the packaging group, correct?
[07:51] <crimsun> for universe, yes.
[07:51] <tritium> crimsun, I don't think I did that right.
[07:51] <readingboy> I'm interested in knowing how packaging works and learning how to do that myself. Is there a good place to go learn about this?
[07:51] <readingboy> I've googled to not much avail...
[07:52] <tritium> readingboy, The first step I took was to read the Debian New Maintainer's Guide
[07:53] <readingboy> tritium, excellent! I've found the page and am off to read now. thanks!
[07:53] <tritium> sure :)
[07:54] <crimsun> apparently configure is dying because Python.h isn't found
[07:55] <tritium> I don't think I could have done that right.  logging in to the chroot doesn't get any of the build-deps it needs
[07:55] <tritium> can you log in to a running build process?
[07:56] <crimsun> not that I know of, besides possibly ptracing
[07:56] <crimsun> but that wouldn't be "logging in," really
[07:56] <diamond> woo. think i've finally got dpatch doing what i want.
[07:56] <tritium> let me apt-get build-dep python-gnome in the chroot, and try again
[07:56] <schweeb> tritium: you could apt-get build-dep inside the chroot... or use dpkg-checkbuilddeps to tell you which ones are missing...
[07:57] <tritium> schweeb, :)
[07:57] <schweeb> apt-get build-dep will only grab the deps from the source in the archive, not your modified sources
[07:57] <crimsun> tritium: you're on ia32, not amd64, correct?
[07:57] <tritium> it's unmodified right now anyway
[07:57] <tritium> crimsun, yes
[07:59] <crimsun> tritium: try invoking autoconf explicitly in the build-2.4/config.status target immediately proceeding dh_testdir
[07:59] <crimsun> tritium: which means you'll have to add autoconf to debian/control/Build-Depends
[07:59] <crimsun> err, debian/control:Build-Depends
[07:59] <crimsun> (yes, hackety-hack)
[08:00] <tritium> okay, shall I proceed with this first, and get you a new config.log?
[08:01] <crimsun> yes, please
[08:01] <tritium> ok
[08:01] <crimsun> brb, drink
[08:01] <tritium> ok
[08:08] <crimsun> (back)
[08:08] <tritium> ok
[08:08] <tritium> new file up at same URL
[08:08] <crimsun> k
[08:11] <tritium> lamont, thanks for the suggestions earlier :)
[08:11] <crimsun> ok, it gets further
[08:12] <diamond> sweet. finally. i have got snacc building in pbuilder
[08:12] <crimsun> what did it die on this time?
[08:12] <tritium> nice job diamond
[08:12] <diamond> (for amd64)
[08:12] <diamond> tritium: cheers
[08:12] <tritium> checking if Python version >= 1.5.2... configure: error: too old
[08:12] <tritium> configure: error: /bin/sh './configure' failed for pygtk
[08:12] <tritium> those are the last 2 lines
[08:13] <ajmitch> ah, I see I wasted your time today, tritium  :(
[08:13] <ajmitch> sorry about that, forgot to edit the wiki after fixing up qemu
[08:13] <crimsun> tritium: hum, still?  That's even more odd.  Where did you edit debian/rules?
[08:14] <tritium> ajmitch, no, you didn't :)
[08:14] <tritium> crimsun, so far, no changes yet.  I'll try your suggestions next.
[08:15] <tritium> this is wacky, especially since it builds on your machine
[08:15] <tritium> ajmitch, I'm glad you got it fixed!
[08:16] <crimsun> tritium: extract gnome-python source (via apt-get source) in a temp directory, edit gnome-python-2.10.0/debian/rules to invoke autoconf, and use pbuilder debuild
[08:16] <ajmitch> tritium: it was an easy fix
[08:16] <tritium> ajmitch, yeah, that's why I was going to attempt it ;)
[08:16] <ajmitch> previously the Build-Depends pulled in zlib1g-dev by themselves
[08:16] <tritium> it was pretty obvious from the buildd log what was needed :)
[08:16] <ajmitch> yep
[08:17] <tritium> crimsun, ok
[08:17] <ajmitch> just took awhile to compile ;)
[08:17] <tritium> yeah
[08:19] <diamond> right, should i upload my changes to my website, and add a line to 'waiting review' on UniversePriorityList?
[08:20] <crimsun> and MOTUToDo
[08:20] <diamond> right. cheers.
[08:23] <tritium> I think I'll create a new pbuilder base.tgz.  it's huge now
[08:27] <tritium> crimsun, how late do you plan on being up?  Should we continue this tomorrow?
[08:28] <tritium> They're going to be rebooting the freenode us hub in 30 minutes anyway
[08:29] <crimsun> I'll be up for a good while, since I have to grade quizzes and make a programming assignment
[08:29] <tritium> Ah, okay.
[08:29] <crimsun> tomorrow(today)'s fine if you feel like turning in
[08:31] <tritium> I'm good for a while.  Hopefully the freenode hub reboot won't be too disruptive
[08:32] <crimsun> k
[08:34] <tritium> crimsun, I just noticed you grabbed gnome-python, and I'm working on python-gnome
[08:34] <tritium> the version # difference is what I first noticed
[08:36] <tritium> ajmitch, how are things?
[08:36] <ajmitch> ok
[08:37] <crimsun> tritium: python-gnome2, right?
[08:37] <crimsun> tritium: (I don't see a python-gnome)
[08:37] <crimsun> tritium: I use apt-get source $source_name
[08:37] <tritium> crimsun, I used apt-get source python-gnome
[08:38] <crimsun> whoa.
[08:38] <crimsun> I don't even have a python-gnome.
[08:39] <tritium> apt-cache search only shows python-gnome2, but apt-get source python-gnome does find version 1.4.5
[08:39] <crimsun> what does ,,apt-cache policy python-gnome'' print out?
[08:39] <tritium> no candidate
[08:40] <crimsun> how in the world...
[08:40] <crimsun> http://higgs.djpig.de/cgi-ubuntu/search_contents.pl?word=python-gnome2&searchmode=searchword&case=insensitive&version=hoary&arch=i386   also finds no python-gnome
[08:40] <tritium> you can't apt-get source python-gnome ?
[08:41] <crimsun> ah!
[08:41] <crimsun> I see.
[08:41] <crimsun> my apologies
[08:41] <ajmitch> tritium: grep python-gnome /var/lib/apt/lists/*
[08:43] <tritium> crimsun, okay, cool.  This is strange, huh?
[08:43] <diamond> right. it's 7:45am, i'm going to bed. 'nite' folks ,-)
[08:43] <ajmitch> 'night' diamond  ;)
[08:43] <tritium> ajmitch, lots returned
[08:44] <crimsun> tritium: actually that makes a lot of sense now.  Anyhow, the cause is a missing b-d on python (>= 2.4), python (<< 2.5)  just as lamont said
[08:44] <ajmitch> heh ok
[08:44] <crimsun> :)
[08:44] <tritium> crimsun, yet, python-dev (>=2.4) should depend on it
[08:44] <lamont> tritium: no, it shouldn't.
[08:45] <ajmitch> perhaps I should have specified grep-dctrl on the sources lists
[08:45] <lamont> in fact, that dependency was specifically removed about 6-8 months ago
[08:46] <crimsun> tritium: I trigged that same missing b-d on python2.4 for one of the packages I transitioned.
[08:46] <tritium> lamont, why does apt-cache depends python2.4-dev return python2.4 ?
[08:46] <lamont> because it does.
[08:46] <lamont> but python2.4 doesn't deliver /usr/bin/python
[08:47] <lamont> it delivers /usr/bin/python2.4
[08:48] <tritium> That's confusing to me, but I'll add the build-depends.  Thanks crimsun and lamont.
[08:49] <crimsun> (python-minimal actually delivers /usr/bin/python, and python-minimal depends on python2.4-minimal)
[08:50] <lamont> amusingly, now that python2.4-minimal (and python-minimal) are essential, you don't actually have to declare python build-depends...
[08:50] <lamont> if minimal works, that is.
[08:50] <lamont> s/works/works for you/
[08:50] <lamont> although it doesn't hurt, since it would cause ftbfs in debian
[08:50] <ajmitch> bbl
[08:50] <tritium> the way I checked was apt-cache depends python-dev
[08:50] <tritium> that depends on python2.4-dev
[08:50] <tritium> wich in turn depends on python2.4
[08:51] <crimsun> right, but configure only checks for python, which would be /usr/bin/python, which python-minimal delivers, which is really python2.4-minimal...)
[08:51] <tritium> But I must be misunderstanding things.
[08:52] <crimsun> had I realized that I should have been getting the source for python-gnome instead of gnome-python (?!), you could have saved an hour :\
[08:52] <tritium> crimsun, not your fault at all.  Thanks for helping me.  Sorry if I wasted your time.
[08:53] <crimsun> oh no, I was up anyway hacking at python-kde3 :)
[08:53] <crimsun> which of course is $fun
[08:53] <tritium> okay.  Well, I appreciate the mentoring.  You too, lamont.
[08:53] <crimsun> yep, thanks lamont.
[08:54] <encolpe> good morning
[08:54] <crimsun> morning, encolpe
[08:54] <tritium> I'll need to re-add python (>= 2.4) build depends to some of my new packages, then.
[08:54] <crimsun> only if it needs it
[08:55] <tritium> it doesn't need it to build
[08:55] <crimsun> then they're fine without python as a b-d
[08:55] <tritium> ok...I think I'll re-visit this tomorrow morning with a fresh mind.
[08:56] <crimsun> we try and use the minimal b-d list
[08:56] <crimsun> k, night
[08:56] <tritium> ok, goodnight.  thanks again
[08:56] <crimsun> np :)
[08:57] <tritium> :)
[09:57] <koke> morning all!
[11:59] <dholbach> hai
[12:01] <dholbach> added #8367 and #8369 to the motutodo
[12:20] <dholbach> i'm off - have to use a friends scanner *grmbl*
[01:01] <mdke> anyway to post bugs on universe packages?
[01:05] <mdke> no one home?
[01:13] <jani> hello all
[01:25] <pvanhoof> A few weeks ago I posted a proposal for the quickcammes module, which adds support for Logitec Quickcam messenger, tot he mailinglist. Did somebody picked this up? I've wrapped the module in an easy-to-build build environment and did some bugfixes to it. You can find more information here: http://freax.be/wiki/index.php/Quickcam_Messenger_Linux_kernel_2.6_driver (please forward it to a kernel-packager, it would be nice if it was support
[01:25] <pvanhoof> and a few people already asked for packages)
[01:26] <pvanhoof> there's a package for normal Quickcams in ubuntu, however, a) it requires that you still build it (some wieerd way of installing itusing source packages) and b) it doesn't support the messenger (which is slightly different)
[02:18] <dholbach> pvanhoof: are there any packges yet?
[02:18] <Treenaks> dholbach: no
[02:18] <dholbach> pvanhoof: then please add it to wiki/UniverseCandidates
[02:18] <Treenaks> dholbach: we're going to start working on our private fork of the driver, and get it into mainline
[02:18] <Treenaks> dholbach: so the MOTU won't have anything to do with it, eventually
[02:18] <dholbach> Treenaks: sounds charming
[02:19] <pvanhoof> :p
[02:19] <Treenaks> dholbach: less work for you, though :P
[02:19] <dholbach> Treenaks: i'm glad to hear that
[02:19] <pvanhoof> I can still add it to that wikipage, of course, if you want to add support for it while we are trying to get it acceptable for mainline
[02:20] <pvanhoof> since it does work and is easily packagable atm
[02:20] <dholbach> pvanhoof: we're incredibly busy at this stage, so i hope you understand, when i can't promise anything
[02:20] <pvanhoof> (it's code is just a bit ugly and it tries to support to many different kernel versions, stuff like that)
[02:20] <pvanhoof> ok, I understand. I'll add it to the wiki?
[02:21] <Treenaks> pvanhoof: great idea
[02:21] <dholbach> yes
[02:43] <ajmitch> night all..
[03:33] <tritium> good morning, dholbach
[03:34] <StoneTable> is there a policy on what to do with abandoned packages?  I was working on aime, trying to get the package to build, and I see the project hasn't had a release in almost 3 years
[03:34] <dholbach> hey tritium
[03:34] <dholbach> StoneTable: if you're fully confident in the package's removal head straight to wiki/MorgueCandidates
[03:35] <StoneTable> hopefully I can find a package that won't be a morgue candidate ;)
[03:36] <dholbach> StoneTable: please check   apt-cache rdepends <package>  before
[03:36] <dholbach> so we make a clean job
[03:36] <StoneTable> oh, cool I didn't know about rdepends :)
[03:43] <tritium> arg, more Input/Output errors...going to fsck again...
[04:14] <schweeb> mornin
[04:14] <tritium> good morning, schweeb
[04:14] <schweeb> dholbach: I got through about the first 50% and wrote down all the pkgs that were ia64 problems only
[04:14] <schweeb> haven't yet had time to remove them from the list yet
[04:14] <dholbach> wow!
[04:15] <schweeb> but they're on wiki/DoesNotBuildIA64
[04:15] <schweeb> I also noted some packages that are building on all now on the same page
[04:15] <schweeb> some story, havent' had time to remove from the list yet
[04:15] <dholbach> alright
[04:16] <schweeb> but, apparently they're retrying Test, starting yesterday
[04:16] <schweeb> so everything should be rebuilding
[04:16] <dholbach> brb
[04:16] <schweeb> k
[04:17] <HostingGeek> dholbach said he wont ban me for saying this useless funny link so here goes nothing: http://www.tomsphotos.com/router/
[04:17] <HostingGeek> walmart takes back every and anything
[04:35] <schweeb> whoa
[04:35] <schweeb> diamond fixed snacc last night? cool
[04:36] <tritium> yeah, he did
[04:44] <diamond> morning.
[04:45] <tritium> good morning
[04:56] <diamond> right. i've fixed snacc, would someone mind reviewing it for me? it's at diamond.nonado.net/packages/snacc
[04:57] <schweeb> this top 25% list is getting pretty short
[04:57] <tritium> I tried fixing python-gnome.  Adding a python (>=2.4) Build-Depends did not help.
[05:04] <pitti> Hi guys
[05:04] <pitti> I'm currently doing a full security review of Ubuntu
[05:04] <pitti> many universe packages can be fixed with Debian syncs
[05:04] <pitti> ogra/dholbach agreed that I shall just do the syncs instead of asking for every package
[05:05] <dredg> hey pitti
[05:05] <pitti> however, I don't overwrite Ubuntu changes
[05:05] <pitti> can somebody please merge grip?
[05:05] <pitti> (CAN-2005-0706)
[05:07] <pitti> Hi dredg
[05:07] <pitti> ogra: is there anybody in particular I shall contact about universe security issues?
[05:08] <dredg> pitti: there will ultimately (i hope) be a MOTU security team of some description.
[05:09] <ogra> pitti, we dont have a MOTUSecurity team yet, someone needs to go for that....
[05:09] <ogra> pitti, but its on the plan: http://www.ubuntulinux.org/wiki/MOTUTeams
[05:10] <pitti> ogra: wine has a CAN too, but it is a "heavily new" upstream version
[05:10] <pitti> ogra: any reasons against syncing?
[05:10] <ogra> pitti, no, absolutely not, i had it on my list as well
[05:10] <pitti> okay, I ask elmo about it
[05:12] <dredg> pitti: grip is a small patch. i'll apply and upload in a bit
[05:12] <dredg> (assuming nobody else has jumped on it)
[05:13] <pitti> thanks
[05:14] <pitti> you all know Keybuk's MOM output?
[05:21] <schweeb> pitti: MOM output?
[05:22] <pitti> http://people.ubuntu.com/~scott/ongoing-merge/
[05:22] <pitti> merge-o-matic
[05:22] <tritium> being his mother's child, should he be it?
[05:22] <tritium> ;)
[05:22] <pitti> http://people.ubuntu.com/~scott/ongoing-merge/SOURCE/SOURCE-ubuntu.patch has the Ubuntu changes
[05:22] <pitti> and there is also an automatically merged source package
[05:23] <pitti> i. e. grip was successfully merged automatically
[05:23] <pitti> http://people.ubuntu.com/~scott/ongoing-merge/grip/
[05:23] <pitti> dredg: ^
[05:23] <pitti> so you only need to verify that this worked and is current, and upload it
[05:24] <diamond> really have to stop doing that -/
[05:26] <schweeb> okay, just knocked about 50 things off the PriorityList
[05:26] <diamond> schweeb: wow. sweet.
[05:28] <dredg> pitti: oh, excellent. yeah, debian already includes the patch for CAN-2005-0706. i'll go over the diff
[05:28] <pitti> dredg: that was the purpose for syncing/merging :-)
[05:28] <pitti> dredg: I mean, the Ubuntu changes should not get lsot
[05:28] <pitti> lost, even
[05:30] <tritium> lamont, do you have any other ideas regarding python-gnome, since adding the python (>=2.4) Build-Depends did not help?
[05:31] <lamont> tritium: uh, not without looking at it... give me a minute
[05:31] <tritium> sure
[05:40] <koke> hi all!
[05:40] <tritium> hi koke
[06:06] <lamont> tritium: that _should_ fix it.
[06:06] <tritium> lamont, yeah, I had hoped
[06:06] <lamont> one could either regenerate the autocrap files, or edit configure and add python2.4 to the list near line 19000
[06:08] <diamond> i suspect the test is broken
[06:08] <tritium> thanks, both of you
[06:10] <dredg> pitti: i just added a quick patch to grip to fix CAN-2005-0706. I haven't really got time to go over the merge patch atm, i might be able to check it out later
[06:11] <pitti> dredg: that's fine
[06:11] <dredg> pitti: it's uploaded
[06:14] <HiddenWolf> dredg: grip rips cd's, how can it have a security problem? :S
[06:15] <dredg> HiddenWolf: buffer overflow in the cddb lookup bit
[06:16] <HiddenWolf> dredg: ugh, that's nasty.
[06:16] <tritium> diamond, you probably know autoconf a lot better than I.  If you care to look at python-gnome, be my guest.
[06:17] <diamond> tritium: i wouldn't bet on it, but sure, i'll have a poke -)
[06:17] <tritium> diamond, you're CS, I'm EE, so I'm betting on it ;)  Thanks for taking a look.
[06:18] <dredg> tritium: he's far far far worse than that
[06:18] <diamond> lol
[06:19] <diamond> tritium: i'm originally CE -)
[06:19] <tritium> diamond, no kidding... ;)
[06:19] <tritium> dredg, that's what you mean?
[06:20] <dredg> tritium: no. and now i shall be enigmatic and vague about the whole thing.
[06:20] <tritium> heh, okay
[06:20] <HiddenWolf> Do any of you guys of any app/way that can restrict a program to a certain portion of the screen?
[06:20] <tritium> cool, schweeb :)
[06:22] <tritium> with each fsck, my /lost+found grows :(
[06:23] <schweeb> o_O
[06:23] <schweeb> are you aggressively shutting down your system or what
[06:24] <tritium> No, not at all.
[06:25] <tritium> only 24 days left on the support contract...
[06:26] <tritium> schweeb, I'm contemplating a new laptop
[06:28] <schweeb> you really shouldn't be seeing fs damage then
[06:28] <schweeb> only reason for stuff in lost+found is if you haven't properly unmounted
[06:28] <tritium> I think it's the controller.  This is the second drive I've had in less than 6 months.
[06:29] <schweeb> ah
[06:42] <sabdfl> hello-motu!
[06:42] <diamond> morning
[06:42] <dredg> hey sabdfl
[06:42] <tritium> hello!
[06:42] <crimsun> morning!
[06:42] <schweeb> mornin
[06:48] <ogra> hey sabdfl
[06:52] <trulux> btw, I'm trying to apply for membership and maintainer"-ship", and I've been told to ask for those who know on my contribution to write something in my wiki page
[07:01] <ogra> trulux, who asked for that ? normally its required that yo fill your wiki page yourself....
[07:01] <trulux> ogra: mako
[07:07] <trulux> ogra: my page is just done, but mako asked for references, for those who know on my contrib. to write one statement
[07:13] <koke_> bye koke :P
[07:29] <dredg> argh i'm a retard
[07:29] <diamond> dredg: in which way?
[07:30] <dredg> the ways that matter sometimes
[07:30] <diamond> heh
[07:30] <dredg> added patch for grip, never put it in 00list
[07:30] <dredg> woo, great. a patch that won't be applied
[07:30] <dredg> gah :(
[07:30] <diamond> ah. yes. handy -)
[07:33] <dredg> right, re-uploaded
[07:59] <jani> hello all
[07:59] <herve> hol!
[08:04] <schweeb> that was fun
[08:04] <schweeb> my LDAP server crashed, hence crashing my domain
[08:09] <diamond> woo. python-gnome building!
[08:14] <jani> can anyone tell me what version of darcs does apt-cache show?
[08:15] <schweeb> Version: 1.0.2-1
[08:15] <jani> I cannot find in hoary-changes  whenit got to 1.0.2
[08:15] <jani> thanks, here as well
[08:15] <schweeb> maybe elmo synced it?
[08:15] <schweeb> do syncs go to -changes?
[08:15] <jani> Yes, I asked him to do it yesterday
[08:16] <jani> that's why I am confused
[08:16] <diamond> silly question. when i change something in a package, i should be adding an entry into the changelog and uping the version number, yes?
[08:16] <jani> and today at work it was there before I updates
[08:16] <jani> updated
[08:16] <jani> and I cannot see it on hoary-changes even though I thought syncs go there
[08:16] <herve> diamond, yes
[08:17] <tritium> diamond, you got it building?  awesome :)  What did it need?
[08:17] <herve> diamond, updating means adding ubuntu1 to it
[08:17] <jani> schweeb, I thought syncs go to changes ,yes
[08:17] <herve> diamond, or ubuntun+1 if n exists
[08:17] <tritium> diamond, just some smiting autoconf in the face?
[08:17] <diamond> tritium: a whole bunch of headwrecking searching, followed by lots of autoconf smiting
[08:18] <jani> I'll ask in devel
[08:18] <tritium> heh
[08:18] <diamond> herve: right, that last bit was the bit i wasn't sure about. cheers.
[08:18] <diamond> tritium: took me hours to figure out that the issue wasn't in the main configure script,
[08:18] <tritium> diamond, thanks for doing that.  I'm terrible at smiting, particularly in the face.
[08:18] <herve> yell if you need something, going washing the dish ;-)
[08:18] <diamond> tritium: it was in pygtk/configure
[08:18] <diamond> tritium: hehe. np
[08:19] <diamond> anyway, currently confirming it builds in pbuilder before throwing it onto the web
[08:19] <tritium> awesome job!
[08:20] <dredg> diamond: dch is useful for editing changelogs
[08:20] <diamond> i'm pretty happy to have made 2 small contributions in my first day. that said sleep would also be good ,-)
[08:20] <diamond> dredg: ok, will look at that
[08:20] <herve> diamond, dch is *mandatory* to edit the changelog!
[08:20] <herve> including the -Dhoary flag
[08:21] <diamond> herve: right, noted.
[08:21] <dredg> just make sure to fix your alternatives so that editor points at something useful. like vi.
[08:21] <schweeb> i.e. not nano :)
[08:21] <dopey> export EDITOR=
[08:21] <diamond> schweeb: agreed -)
[08:21] <dredg> herve: could you tell the difference between a changelog edited using dch and one edited by hand? :)
[08:22] <schweeb> I occasionally edit by hand, if it's a quick fix
[08:22] <tritium> or even worse, the mc editor
[08:22] <herve> dredg, I just want to reduce those tiny errors and ease the job of reviewers
[08:22] <herve> dredg, but to answer you, no :-)
[08:22] <dredg> update-alternatives --set editor /usr/bin/vim :)
[08:22] <diamond> dredg: just done
[08:22] <schweeb> dredg: damn, I was about to paste the same thing
[08:23] <schweeb> :p
[08:24] <dredg> diamond: when a package comes from debian it has a version like `1.0-1'. when we modify it, we change that to '1.0-2ubuntu1'. This allows us to increment the version without getting ahead of the upstream debian version
[08:25] <diamond> dredg: did you intend to change -1 to -2 there?
[08:25] <dredg> though while useful, it does tend to hurt when a sync from debian wipes out some ubuntu-specific changes
[08:25] <dredg> er
[08:25] <dredg> `1.0-1ubuntu1'
[08:25] <dredg> ahem
[08:25] <diamond> dredg: right so -)
[08:25] <dredg> you saw nothing
[08:26] <herve> don't worry ;-)
[08:26] <tritium> diamond, if I recall, doko already made 1.4.5-2ubuntu1, so you'll want to increment to ubuntu2
[08:26] <diamond> tritium: right
[08:28] <diamond> hum. dpkg-buildpackage seems to have changed config.sub and config.guess. should i be removing those diffs from my updated package?
[08:30] <tritium> diamond, you didn't build it in pbuilder?
[08:31] <diamond> tritium: ah. good point. i've confused myself with the different locations
[08:32] <diamond> tritium: wait, in order to get pbuilder to build it, i need to use dpkg-buildpackage to create the appropiate diff.gz, no?
[08:32] <tritium> diamond, I usually use debuild
[08:32] <schweeb> you can use dpkg-buildpackage -S
[08:32] <diamond> ah, k
[08:33] <tritium> diamond, debuild would also require -S
[08:33] <diamond> ok
[08:34] <herve> debuild is just a front-end
[08:34] <herve> all options are passed to dpkg-buildpackage
[08:34] <herve> (roughly
[08:34] <schweeb> dpkg-buildpackage is a frontend as well :)
[08:34] <schweeb> it calls dpkg-source or some shit
[08:35] <herve> all the mess you don't want to see :-)
[08:36] <diamond> right. think i'm gonna just make all the changes from scratch again. unsure as to what perversions i've introduced -)
[08:37] <dredg> debdiff is also a useful tool :)
[08:37] <tritium> hi sivang
[08:40] <diamond> right. i'm well confused. why would 'diffstat snacc_1.3bbn-5.1ubuntu1.diff.gz snacc_1.3bbn-5.1ubuntu2.diff.gz' think i've changed every file?
[08:40] <diamond> is it just because the version number has changed?
[08:42] <herve> diamond, do you know debdiff?
[08:43] <diamond> herve: no, but dredg has just poked me with it
[08:43] <diamond> i had thought it was for comparing .debs
[08:44] <dredg> it is
[08:44] <dredg> it can also do source packages
[08:44] <diamond> ah, right.
[08:44] <herve> man, I'm really a-way!
[08:46] <diamond> ok. deb-diff is showing that config.guess and config.sub have changed in addition to my changes, is that expected behaviour?
[08:46] <diamond> (they look like they're updated versions)
[08:47] <diamond> apologies for the string of questions
[09:00] <diamond> tritium: http://diamond.nonado.net/packages/python-gnome/
[09:01] <tritium> diamond, cool :)
[09:02] <tritium> diamond, you should probably edit https://www.ubuntulinux.org/wiki/UniversePriorityList, requesting a review of it
[09:02] <diamond> tritium: just done
[09:03] <diamond> ditto MOTUTodo
[09:04] <tritium> thanks again, diamond
[09:05] <diamond> tritium: np. i'm looking to get package fixes under my belt anyway, so if there's any more you'd like fixed, just shout. otherwise, i'll keep poking at the priority list
[09:05] <dredg> fear
[09:05] <dredg> debdiff python-gnome_1.4.5-2ubuntu1.dsc python-gnome_1.4.5-2ubuntu2.dsc|wc -l
[09:05] <dredg> 34239
[09:06] <diamond> dredg: yeah, that's what i was talking about...
[09:06] <diamond> dredg: any idea what it's like that?
[09:06] <dredg> autoconf crack i'm guessing
[09:07] <diamond> dredg: ah, wait, that is actually correct. all the makefiles etc were re-created in the pygtk subdir
[09:07] <dredg> mc is so useful for looking through diffs :)
[09:08] <diamond> oh dear. looks like i didn't delete the autom4te dir. oops.
[09:09] <dredg> that would do it :)
[09:09] <diamond> dredg: that brings it down to 11012 lines changed.
[09:10] <dredg> sweet jesus
[09:10] <dredg> curse you automake
[09:10] <diamond> dredg: it's only ~4 fiiles tho
[09:10] <diamond> aye
[09:11] <diamond> *files
[09:11] <dredg> er, autowhatever
[09:11] <diamond> right. updated python-gnome_1.4.5-2ubuntu2.dsc now
[09:16] <dredg> still crack addled :)
[09:16] <diamond> yeah, but it's _all_ auto*'s fault now -)
[09:18] <dredg> looks fine to me
[09:18] <dredg> i'll let someone else review it as well though
[09:19] <diamond> dredg: cheers
[09:19] <diamond> dredg: if you're feeling really reviewy, have a look at snacc there too ,-)
[09:20] <dredg> ok, but only because i can't hunt for an insurance quote from quinn direct...
[09:20] <diamond> woo -)
[09:23] <dredg> only 440 changed lines in this one ;)
[09:23] <dredg> you updated config.sub and config.guess, yes?
[09:24] <diamond> dredg: aye, config.guess and config.sub got updated by dpkg-buildpackage. no idea why
[09:26] <dredg> not necessarily a bad thing
[09:26] <dredg> all that was missing was include <time.h>?
[09:27] <dredg> heh
[09:28] <dredg> looks fine as well, though i'd still prefer if someone else took a look over as well
[09:29] <dredg> and for dpatch stuff, have a read of http://tseng.ath.cx/log/?p=7
[09:29] <diamond> dredg: yup. it was only biting in once place, but i found another similar usage so i added it there too
[09:29] <dredg> nothing wrong with what you did, that's just easier...
[09:30] <diamond> dredg: ah. nicey.
[09:30] <diamond> very nicey
[09:31] <dredg> yeah. it wins
[09:32] <dredg> let's not inflict the game on the folk here :) no work will get done.
[09:34] <dredg> care to share your config? :)
[09:36] <diamond> dredg: sure. one sec, i'll drop it onto nonado
[09:37] <diamond> dredg: http://diamond.nonado.net/misc/apt-proxy-v2.conf
[09:37] <diamond> dredg: my apt-proxy cache is currently ~2.2G
[09:38] <diamond> dredg: the only stuff changed from defaults (afair) are the backends i've added
[09:40] <dredg> urk
[09:40] <dredg> right
[09:42] <diamond> the cache is rather large due to the large number of archs+distros that have been using it
[09:43] <diamond> i386, ppc, amd64. debian, ubuntu, fedora
[09:46] <dredg> your dsl upgrade will come in useful for that then :)
[10:04] <schweeb> heh
[10:04] <schweeb> proto just got linkedin finally?
[10:05] <diamond> dredg: indeedy
[10:05] <schweeb> whoops, wrong window
[10:41] <koke> hi all!
[10:41] <koke> is the universe also frozen??
[10:42] <schweeb> no
[10:42] <schweeb> main isn't fully frozen either, but mostly frozen
[10:43] <mdz> main is pretty densely frozen at the moment
[10:43] <koke> ok, so we keep fixing the universe... ;)
[10:45] <schweeb> koke: yes
[10:45] <mdz> lamont: I believe it was pitti, check -changes
[10:45] <schweeb> hah
[10:47] <lamont> mdz: so can we sync squirrelmail-locales too?
[10:47] <lamont> so it's installable again?
[10:47] <mdz> lamont: yes
[10:47] <lamont> s
[10:48] <diamond> if anyone here has a couple of spare minutes, i have a few package fixes that need to be reviewed (snacc, python-gnome, and xfcalendar)
[10:48] <lamont> mdz: sent
[11:01] <diamond> hurm. X just hung on me -/
[11:23] <bradb> hey dudes
[11:23] <bradb> how's the Malone usage going? i haven't heard a lot of feedback from you guys up to now.
[11:24] <herve> re
[11:27] <bradb> ogra: ping
[11:27] <ogra> bradb, pong
[11:27] <bradb> ogra: hi
[11:28] <ogra> bradb, soryy, i didnt do very much universe work recently (was very busy with hwdb)...so no bugs from me
[11:28] <ogra> when did you adjust the font ?
[11:28] <bradb> me? :)
[11:29] <bradb> that was an sabdfl inspiration
[11:29] <ogra> yeah, or i have new font settings since my last xorg update...it looks bigger
[11:29] <bradb> well sabdfl and mpt
[11:29] <ogra> ah
[11:30] <bradb> so, MOTU is officially using Malone though, right? from what kiko's relayed to me, dholbach/mdz seem to be unsure of this, or perhaps even of the impression that i "haven't given the go-ahead" yet for that, despite the fact that the IRC log in the /topic contains that very announcement giving the official go-ahead from me :)
[11:31] <bradb> the only thing i'd prefer to not happen right now is an "official" announcement, i.e. on ubuntu-users
[11:32] <ogra> bradb, but without user input a bugtracker is not quite useful...
[11:32] <bradb> ogra: indeed :) i encourage you all to use Malone though.
[11:32] <bradb> ogra: if you make an official announcement though, next thing you know we're on Slashdot. :)
[11:34] <ogra> bradb, the probelm here is that if a MOTU finds a bug, he fixes it right away, the only thing we could put in there would be one of our transition lists i think...
[11:34] <bradb> he does? heck, i find bugs all the time in Malone that I can fix right away :)
[11:34] <ogra> the other possibility would be that someone stis down and transfers all bugs from ubuntu-users....
[11:35] <bradb> to restate this clearly though: i encourage
[11:35] <bradb> er, my return key got in the way there
[11:36] <bradb> to restate this clearly though: i encourage all MOTU's (and MOTU end-users) to use Malone. i wouldn't yet endorse an official announcement of MOTU to any public forum or mailing list though. spreading the word on IRC is cool though, but keep in mind that if we get slashdotted, we don't yet have the admin-availability to immediately recover.
[11:36] <ogra> w
[11:36] <ogra> oops
[11:37] <ogra> ok i meant...i'll try to spread this spirit herea bit
[11:37] <bradb> share the love, spread the joy
[11:37] <bradb> :P
[11:38] <ogra> but since the ML is our current bugtracker its hard not to answer "please put that in malone" ;)
[11:38] <bradb> you could even add the bug filing URL to the /topic.
[11:38] <bradb> ogra: heh, fair point ;)
[11:39] <ogra> so the real bug will still get handled in the ML...i'll see that every MOTU that does support in #ubuntu points to malone, this will probably be a good start
[11:39] <bradb> sure, that'd be good
[11:40] <ogra> URL ok ?
[11:41] <bradb> https://launchpad.ubuntu.com/distros/ubuntu/+bugs
[11:41] <ogra> or do you like it better without /istros
[11:41] <ogra> :)
[11:41] <bradb> cool, thanks
[11:41] <ogra> yeah
[11:43] <\sh> howdy ogra
[11:43] <ogra> hey \sh
[11:43] <\sh> ogra: i'm missing u @irrenhaus ;)
[11:44] <ogra> hehe, i dont miss it.... :) but you guys i miss indeed...klaus ICQed too today :)
[11:45] <\sh> hehe yeah he helped a lot today
[11:45] <\sh> but he has a nice night in front of him ;)
[11:45] <ogra> nightshift ? him ?
[11:45] <\sh> ogra, FLPs + channel shuffling ;)
[11:46] <\sh> nagra screwing, kryptons bashing
[11:46] <ogra> hehe, darn DigiTV.... i'm happy i will never get nearer then my remotecontrol allows anymore ;)
[11:46] <\sh> todays reading en_300468v010501p.pdf
[11:48] <\sh> ETSI EN 300 468  DVB: SPEC ON SI in DVB Systems
[11:48] <ogra> heh
[11:48] <\sh> i want to know, if some humax dev suckers screwed up the spec
[11:48] <\sh> in their new software release
[11:48] <ogra> no, they would _never_ do that  ;)
[11:49] <\sh> ogra: they fucked up the whole EIT p/f stuff in the humax pr fox-c
[11:49] <\sh> any service without EIT p/f or any service with broken EIT p/f you can't watch it on their boxes anymore
[11:49] <ogra> heh
[11:49] <\sh> we spreaded today dummy events to those services...
[11:51] <\sh> ogra: i'm really pissed off with humax...u don't know whats going on between me and ksc..fossy is not there, and i'm right now the interface between isp/dtv team and P.F. ;)
[11:52] <ogra> oh, so you took a piece of my job :)
[11:52] <\sh> no
[11:52] <\sh> no no and no :)
[11:52] <ogra> hehe
[11:53] <\sh> but i send all tickets to EDP ;) so to p.f. and klaus...and klaus was not amused ;) because he's not in charge of that...understandable
[11:53] <ogra> you know you can puh the loan a lot if you offer to take my job ! if this position isnt filled soon they are fucked
[11:53] <ogra> s/puh/push
[11:54] <\sh> ogra: no money increasement right now
[11:55] <\sh> ogra: and I don't want to play political stuff between jim, guenther, helmut and all the others...I'm operational staff
[11:56] <ogra> yeah, i learned a lot of poiltical mess there, more then i liked as you can see ;)
[11:58] <ogra> yeah, 527 submissions today...on http://hwdb.ubuntu.com/
[11:58] <\sh> ogra, well..u r doing your job very well @ubuntu...ogra for president ;)
[11:59] <ogra> i'm really wondering how my old server will cope with the masses tomorrow....if they all have downloaded the RC
[11:59] <\sh> ogra: if u need bandwidth and space :) i'll welcome u
[12:00] <schweeb> ogra: does RC automatically start hwdb after install?
[12:00] <\sh> ogra, but will be a gentoo server *eg
[12:00] <ogra> \sh, if it gets to tight for me i'll have a place in the ubuntu DC ;) no probs
[12:00] <ogra> its easy to bend the DNS
[12:01] <ogra> schweeb, nope