=== _Enchained [n=cyrille@ADijon-153-1-73-113.w81-49.abo.wanadoo.fr] has joined #ubuntu-motu === PriceChild [n=PriceChi@host86-138-223-156.range86-138.btcentralplus.com] has joined #ubuntu-motu [12:25] ajmitch: looking at your list of missing bugfixes from Debian: do you know from where your script got the fixed debian version for cacti? [12:27] yes [12:27] dbconfig-common [12:27] it looks like it misparsed the fixed in versions line from the bug. it contains two packages [12:27] I know === jdong [n=jdong@ubuntu/member/jdong] has joined #ubuntu-motu [12:53] ajmitch: can your script also scan the tags in Debian bugs? [12:58] I guess so [12:59] can you search for Tags: security like in Debian bug #409296? [12:59] Debian bug 409296 in mpg123 "CVE-2007-0578: http_open function in httpget.c can get into infinite loop" [Important,Closed] http://bugs.debian.org/409296 [12:59] yeah, they're in the same summary file [12:59] sure, I'll try & get it to play along === _Enchained [n=cyrille@ADijon-153-1-96-17.w86-204.abo.wanadoo.fr] has joined #ubuntu-motu [01:00] it would be good if security bugs be also included in the list [01:00] thanks === Tonio_ [n=tonio@28.8.100-84.rev.gaoland.net] has joined #ubuntu-motu === ogra_ [n=ogra@p548ACDDF.dip.t-dialin.net] has joined #ubuntu-motu === ogra [n=ogra@ubuntu/member/ogra] has joined #ubuntu-motu === rrittenhouse [n=tad@unaffiliated/rrittenhouse] has joined #ubuntu-motu === Amaranth [n=travis@ubuntu/member/Amaranth] has joined #ubuntu-motu === zul [n=chuck@ubuntu/member/zul] has joined #ubuntu-motu === esaym [n=user@cpe-72-183-201-32.satx.res.rr.com] has joined #ubuntu-motu === lotusleaf [n=lotuslea@kernel-panic/member/carne.asada.burrito] has joined #ubuntu-MoTu === philwyett [n=philwyet@bb-87-81-146-45.ukonline.co.uk] has joined #ubuntu-motu === Tonio_ [n=tonio@28.8.100-84.rev.gaoland.net] has joined #ubuntu-motu === hub [n=hub@toronto-hs-216-138-231-194.s-ip.magma.ca] has joined #ubuntu-motu === PuMpErNiCkEl [n=pumperni@CPE0016b6c9fba4-CM0012c9a9a6dc.cpe.net.cable.rogers.com] has joined #ubuntu-motu === redguy [n=mati@unaffiliated/redguy] has joined #ubuntu-motu === finalbeta [n=finalbet@d5152A68A.access.telenet.be] has joined #ubuntu-motu === caravena [n=caravena@67-29-246-201.adsl.terra.cl] has joined #ubuntu-motu === somerville32 [n=somervil@ubuntu/member/somerville32] has joined #ubuntu-motu === bddebian [n=bdefrees@c-71-224-172-103.hsd1.pa.comcast.net] has joined #ubuntu-motu [02:05] Heya gang [02:06] hi bddebian [02:07] Heya LaserJock [02:12] la la la MIR MIR MIR === Tonio_ [n=tonio@28.8.100-84.rev.gaoland.net] has joined #ubuntu-motu [02:15] LaserJock: :-) [02:15] la la la gpib build sucks.. :-) [02:16] sorry dude [02:16] I use the proprietary (must use 2.4 kernel) crap for a reason === RAOF [n=chris@202.63.35.99] has joined #ubuntu-motu === somerville32 [n=somervil@ubuntu/member/somerville32] has joined #ubuntu-motu [02:30] hum [02:31] hrm, I uploaded a package to REVU and it shows as uploaded by "matt@devi" which is my local Linux login & host instead of my email [02:31] so I can't comment on it since it doesn't think I'm the uploader [02:31] I tried setting DEBEMAIL and reuploading it, but that doesn't seem to have an effect [02:31] fix the debian/changelog ( should have been signed anyhow ) and reupload [02:31] What did you use in debian/changelog? [02:32] heya bddebian [02:32] Heya imbrandon [02:33] hi imbrandon [02:34] bddebian/imbrandon: doh, yeah that seems to be the problem [02:34] heya LaserJock === Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-motu [02:34] I forgot to set DEBEMAIL in my .bashrc on my pbuilder machine [02:35] imbrandon: yeah, it should have the right signature though, I guess REVU just check the changelog though === Hobbsee waves [02:37] Hobbsee! [02:37] LaserJock!! [02:37] yikes! [02:37] haha [02:37] I say hi to Hobbsee and LongPointyStick comes after me [02:38] is REVU using an old lintian? [02:38] must be jelousy ;-) [02:38] LaserJock: haha [02:38] lol === LongPointyStick hugs Hobbsee [02:38] matt_good, possibly [02:38] it shows a "newer-standards-version 3.7.2" error, but I know that's supported on Edgy === LaserJock waves goodby as he heads home [02:38] yes ignore that on tiber [02:39] crimsun@tiber:~$ lsb_release -r [02:39] Release: 6.06 [02:39] heya crimsun [02:39] imbrandon: how about "source-nmu-has-incorrect-version-number 0.2.0-2"? [02:40] what should I use for the revisions on new packages? [02:40] we dont worry about nmu error but that is the wrong versioning for ubuntu [02:40] depends , it goes like this ...... [02:41] -upstreamXubuntuY where X is debian rev and Y is ubuntu rev [02:41] like upstream 3.4 would be 3.4-1 in debian and 3.4-1ubuntu1 in ubuntu , and if it wasent in debian it would be 3.4-0ubuntu1 [02:41] etc [02:42] thats the short of it, there are exceptions etc [02:42] thus ignore the nmu warning BUT the versioning is wrong === freeflying [i=flyingfr@gobstopper.dreamhost.com] has joined #ubuntu-motu [02:44] ... [02:47] imbrandon: so should I stick to -0ubuntu1 even if I make changes before it's accepted, or should I add new changelog entries for those? [02:48] matt_good: keep at -0ubuntu1 [02:48] no, always version it what you intend to be uploaded [02:48] but -0ubuntu1 implys its not in debian, where did the package start from ? [02:48] heya Hobbsee [02:49] hey imbrandon :) [02:50] imbrandon: it's my application which I've packaged [02:50] ok, just checking ;) [02:51] and I think Debian's missing the packages for pygobject, so I can't package it there yet [02:52] ok, one more lintian error: build-depends-without-arch-dep [02:52] it mentions changing Build-Depends to Build-Depends-Indep, but there's an exception for debhelper [02:53] I'm using debhelper, but should I move other dependencies into -Indep? [02:59] now python packaging isnt my stong point, you'll have to poke someone else for that [02:59] strong* === DarkMageZ [n=richard@ppp40-172.lns2.syd6.internode.on.net] has joined #ubuntu-motu [03:14] imbrandon: well, REVU thinks that the 0.2.0-2 version I uploaded is the latest, but that needs replaced with 0.2.0-0ubuntu1, is there any way to fix this? [03:15] also despite fixing my email in the changelog it still thinks "matt@devi" is the uploader [03:16] oh, it's still just showing the files from the earlier bad upload === fernando [n=fernando@unaffiliated/musb] has joined #ubuntu-motu [03:22] oh, n/m [03:23] I just realized I was just viewing that particular upload and that the others are separate pages [03:28] Gawd I hate CDBS [03:30] lol bddebian [03:31] I can't figure out where the fsck this build-tree dir is supposed to be coming from.. :-( [03:32] ah, cdbs magic [03:32] it's great [03:32] hum [03:33] using tarball.mk? [03:34] sudo apt-get install ubuntu-desktop [03:34] gah wrong damn keyboard, not jsut window === imbrandon needs a kvm [03:36] ajmitch: Yes :-( === mwolson [i=mwolson@jpi-wlafyte-212-116.dmisinetworks.net] has joined #ubuntu-motu [03:38] ajmitch: But after all the clean crap, the first couple errors I get are: [03:38] dh_clean [03:38] cd build-tree/linux-gpib-3.2.08 && python2.4 language/python/setup.py clean -a [03:38] cd: 1: can't cd to build-tree/linux-gpib-3.2.08 [03:38] make: [python-clean-2.4] Error 2 (ignored) [03:38] imbrandon: if you have two monitors try synergy -- synergy2.sf.net [03:39] i have many monitors ;) [03:39] synergy's a software KM switch [03:39] basically you move the mouse off the edge of the screen and it controls the mouse & keyboard on the other computer [03:40] over then network [03:40] but of course each box needs a monitor [03:40] ahh, wouldent be pratical for me, but sounds cool [03:41] wb LaserJock [03:41] hi all [03:43] bddebian: I feel your pain, I'm trying to figure out how to work with the CDBS in ubuntu-docs [03:43] heh [03:43] This is frickin' craziness. I get a different problem building locally [03:45] mm, libflashsupport has all sorts of cruft === Q-FUNK [n=q-funk@modemcable196.33-82-70.mc.videotron.ca] has joined #ubuntu-motu === lotusleaf [n=lotuslea@kernel-panic/member/carne.asada.burrito] has joined #ubuntu-motu === jwhitlark [n=jwhitlar@h-67-102-70-2.snfccasy.covad.net] has left #ubuntu-motu [] [03:58] Does anyone want to review: http://revu.tauware.de/details.py?upid=4300 (gnome-compiz-manager [03:58] )? [03:58] It's not my package, I'd just like to make sure it gets in :) [03:59] do we get to have any beryl package for feisty? [03:59] I've looked at it, and it seems OK (except for needing a depencency on 4.1.0) [03:59] I've looked at it, and it seems OK (except for needing a depencency on debhelper 4.1.0) [04:03] Q-FUNK: not that I know of yet [04:03] anybody know where a changelog would be for the ubuntu kernels? [04:04] LaserJock: we seem to have the beryl config tool, but not beryl-core, for some strange reason [04:05] esaym, http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-source-2.6.20/linux-source-2.6.20_2.6.20-8.14/changelog [04:05] and the like [04:05] ( e.g. debian/changlog ) [04:06] ok thanks you! [04:06] I would like to meet this ben collins guys ;) [04:06] guy* [04:06] yea BenC is a nice guy [04:07] but i'm still gonna beat him in bowling next conf [04:07] ;) [04:07] Q-FUNK: I think beryl-core was rejected [04:07] imbrandon: is that Wii bowling? 'Cause I rock at that :) [04:07] real bowling ;) [04:08] :P [04:08] OK obviously this is over my head :'-( [04:09] you need combined powers of the motu trinity. [04:09] crimsun: No one ever wants to help me :'-( [04:09] ping me tomorrow mid-afternoon EST [04:10] OK, if I can. Thx [04:10] hmm, maybe some sort of Power Rangers combination of powers is what we need [04:10] heh [04:11] Man, between .NET at work, glibc for Hurd, and Ubuntu stuff I feel like a complete failure these days :-( [04:11] actually, Transformers might be more appropriate for MOTU ;-) [04:11] haha i cant wait for the new transformers movie === ajmitch should probably find some food sometime today [04:16] imbrandon: Aye, the trailer looks cool [04:17] hum is the evolution exchange connector packaged? [04:18] guess so === poningru hugs bddebian [04:18] you'll always be a success in our eyes :) [04:19] Hah, right, but thanks :-) [04:22] bddebian: you still do more than me :P [04:26] bddebian: how long are you sticking around for? === ajmitch uses cdbs+tarball.mk in a couple of packages [04:27] I'm probably up for at least a couple of hours [04:27] right === ajmitch is heading out for an hour or so now [04:28] so I may be able to look at it [04:28] ok, thx [04:35] Oooh. bddebian, can you summon me when ajmitch gets back and explains tarball.mk? I've always wanted to know what the hell that does :) [04:37] RAOF: You can have a tarball embedded inside a source tarball. So foo-1.0.orig.tar.gz unzips to /debian + foo.tar.gz or so [04:37] tarball.mk unzips foo.tar.gz before building [04:38] I'm probably oversimplifying it a little but that's the gist of it [04:38] Why would you want to do that, though? So much that it's the default in dh_make? === jdong [n=jdong@ubuntu/member/jdong] has joined #ubuntu-motu [04:39] RAOF: I wouldn't. I frickin' hate packages that have tarballs in the source package :-) [04:39] I thought it was against policy to have tarballs in the source package, too :) [04:42] Well pull the gpib source for an example if you don't believe me :) [04:42] :( [04:43] Why :(? [04:45] Gah, is this new? [04:45] dpkg-source: error: Version number suggests Ubuntu changes, but Maintainer: does not have Ubuntu address [04:45] pbuilder: Failed autobuilding of package === TomSwift [i=TomSwift@user-142h7sq.cable.mindspring.com] has joined #ubuntu-motu [04:50] what? thats strange, ubuntu revisions dosent mean a ubuntu-dev did it === jhnjwng [n=wj1918@pool-70-21-130-84.nwrk.east.verizon.net] has joined #ubuntu-motu [04:57] bddebian: that's the new Maintainer spec [04:57] you need to adjust the Maintainer field [04:58] bddebian: https://wiki.ubuntu.com/DebianMaintainerField [05:03] LaserJock: Ah, I didn't know it was decided, thx === janm [n=jmalonzo@ppp4592.dsl.pacific.net.au] has joined #ubuntu-motu [05:32] hmm === RAOF [n=chris@202.63.35.99] has joined #ubuntu-motu [05:39] Gah, what package is /lib/modules/linux-foo/ from? [05:41] bddebian: Can't you just "dpkg -S /lib/modules/linux-foo" ? [05:42] boo === Ademan [n=dan@h-67-101-47-9.snfccasy.dynamic.covad.net] has joined #ubuntu-motu [05:43] RAOF: Hmm, I didn't think it would work but it did, thx [05:48] bddebian: You could return the favour by fixing python-pyinotify on AMD64 :P === cypher1 [n=cypher1@59.92.166.94] has joined #ubuntu-motu === LaserJock [n=LaserJoc@ubuntu/member/laserjock] has joined #ubuntu-motu [05:51] RAOF: Send me an amd64 and I'll be happy to try :) [05:53] Failing that, could you point me to the debian-maintainer spec LaserJock gave you, so I could builld the sources and see what's breaking? [05:53] https://wiki.ubuntu.com/DebianMaintainerField === tonyyarusso [n=anthony@ubuntu/member/tonyyarusso] has joined #ubuntu-motu [05:55] Thanks muchly === LaserJock [n=mantha@ubuntu/member/laserjock] has joined #ubuntu-motu [06:02] Anyone know how to fix linking problems in python, I'm trying to fix bug #85705 [06:02] Malone bug 85705 in pyinotify "Undefined symbol error when importing pyinotify" [Undecided,Unconfirmed] https://launchpad.net/bugs/85705 === ajmitch returns === Amaranth [n=travis@ubuntu/member/Amaranth] has joined #ubuntu-motu === jkimball4 [n=jerrid@pc006629.mbsc.unomaha.edu] has joined #ubuntu-motu [06:04] Anyone know how many megs the minimal install that pbuilder needs actually is? [06:05] -rw-r--r-- 1 root root 82M 2007-02-09 11:28 feisty-base.tgz [06:05] That's a minimal feisty pbuilder chroot. [06:05] that's tar'd up though [06:06] True, but that's how much it takes up on disc. [06:06] When it's not being used. [06:06] So,, probably 100ish. hmm [06:06] Hey, Amaranth. You're a python god, right? [06:06] bddebian: still alive? [06:06] Well, I could probably get that by about Sunday afternoon if I let it run, but it's a weekend so the family needs on too. Dang. [06:07] RAOF: sure, why not [06:07] ajmitch: More or less. [06:07] You don't need a pbuilder to package properly. Although it is helpful [06:07] bddebian: still having issues? [06:07] Amaranth: How would you debug a linking error in a python module? [06:07] ajmitch: I sort of figured out my problem but I'm debating whether to try to get it to build the modules or add the patches back in to not build them :-( [06:07] Amaranth: Or rather, how would you fix it so it's correctly linked. [06:08] RAOF: you're building a C extension and getting linker errors? [06:08] bddebian: ah alright [06:08] RAOF: First crack at it, figured it might be a good idea. [06:08] RAOF: what are the errors [06:08] Amaranth: I'm talking about bug #85705 [06:08] Malone bug 85705 in pyinotify "Undefined symbol error when importing pyinotify" [Undecided,Unconfirmed] https://launchpad.net/bugs/85705 [06:08] tonyyarusso: pbuilders _always_ has to get more stuff === ajmitch checks [06:08] RAOF: only on amd64? [06:08] tonyyarusso: afaik that 82M is just "essential" packages [06:08] ajmitch: Only tested on AMD64. [06:08] RAOF: right [06:08] Amaranth: right [06:08] ajmitch: I suppose I could try and fire up my i386 pbuilder. [06:08] RAOF: rebuild the package please [06:08] ajmitch: I'll go check :) [06:09] But damn, neither linux-headers-foo, linux-restricted-modules-common, nor linux-source-foo puts stuff in /lib/modules :-( [06:09] Amaranth: Have done. Same result. === ajmitch installs pyinotify [06:10] Amaranth: I've also just installed it with "sudo python setup.py install --prefix=/usr", and the same thing's happening. === ajmitch tests on x86 [06:10] So it doesn't seem to be a problem with the packaging per-se === Amaranth stabs that package name === RAOF would love it to be renamed python-inotify [06:11] /var/lib/python-support/python2.5/pyinotify/inotify.py:49: RuntimeWarning: Python C API version mismatch for module _inotify: This Python has API version 1013, module _inotify has version 1012. [06:11] RAOF: probably some change in python2.5 [06:11] this is what i get [06:11] how special [06:11] i'll try to fix it [06:12] so it needs updated, should be trivial [06:12] Except I've just built it on my AMD64 box. And it gives *me* a different error. [06:12] RAOF: not necessarily rebuilding [06:13] Py_InitModule4 probably doesn't exist anymore [06:13] python doesn't guarantee extension api/abi [06:13] Amaranth: so it fails for you on x86? [06:13] Sorry, I seem to have read "updated" as "rebuilt" :) [06:13] there are certainly some amd64-only bugs out there, eg bug 83551 [06:13] ajmitch: yeah [06:13] Malone bug 83551 in rhythmbox "python plugins don't work in amd64" [High,Fix committed] https://launchpad.net/bugs/83551 [06:14] damn i need to update my pbuilder more often [06:14] hehe [06:14] it's 80MB and i have to get 40MB of packages :P [06:15] import pyinotify worked fine on x86 laptop, which is out of date [06:15] but it's still py 2.5 [06:15] interesting === ajmitch upgrades to the latest & greatest feisty === tuxmaniac [n=aanjhan@unaffiliated/tuxmaniac] has joined #ubuntu-motu [06:17] dpkg-source: error: Version number suggests Ubuntu changes, but Maintainer: does not have Ubuntu address [06:17] i am going to stab someone [06:17] Hm. inotify.c uses Py_InitModule3, but that never hits the object code. [06:18] why does the maintainer have to have an ubuntu address? [06:18] Amaranth: Debian-maintainer spec. https://wiki.ubuntu.com/DebianMaintainerField [06:18] yeah but what if i want to use my gmail address? :) [06:18] :) [06:19] wtf [06:19] Amaranth: to inconvenience us [06:19] i still get the API warning after building :P [06:20] the version warning, i mean [06:20] Oh. [06:20] I *think* it might be building 2.4 modules only. [06:21] does inotify work if you use python2.4? [06:22] Yup. [06:22] :( [06:22] Or, at least, it imports. [06:22] it almost looks like it's building the python 2.4 version and calling it the python 2.5 version... [06:24] for python in $(PYVERS); do \ [06:24] $$python setup.py install --root=$(CURDIR)/debian/python-pyinotify; \ [06:24] hrm [06:24] i think it installs the 2.4 version on top of the 2.5 version [06:28] Oh, it also doesn't clean between building different versions. [06:29] for python in $(PYVERS) ; do "$${python}" setup.py build' === jkimball4 [n=jerrid@pc006629.mbsc.unomaha.edu] has joined #ubuntu-motu [06:30] Do you want to fix that Amaranth, or shall I give it a try? [06:33] go ahead [06:34] i was trying to convert it to cdbs :P [06:34] Hm. That *would* be easy :) [06:51] Amaranth: Done. Shall I add a debdiff to the bug? === RedKrieg [n=RedKrieg@ip68-230-209-186.rd.hr.cox.net] has joined #ubuntu-motu === Fujitsu wonders if we can collect some people and revolt against the debian-maintainer spec. [07:01] Fujitsu: ?? [07:01] WHy? [07:03] It's inconveniencing (it's no longer possible to create packages unless you're an Ubuntu Member, some maintainers (such as myself) don't use @ubuntu.com, so have to have the field mangled)... There's no option to have it unmangled. [07:04] With the binary-mangling, there was at least a method to opt-out. [07:05] Fujitsu: it won't be hard to find annoyed people [07:05] but I doubt it'll do much good [07:05] did you see that doko has uploaded a fixed zope3? [07:05] it's not really that bad though [07:05] I guess it won't bother me, as I use themuso@ubuntu.com === ajmitch uses ajmitch@debian.org for some packages [07:06] they idea is that we are supposed to use ubuntu-motu@lists.ubuntu.com [07:06] so it shouldn't matter [07:06] ajmitch, nice. How'd he fix it? [07:07] from the changelog, looks like he just had some patches [07:07] & it's 3.3.1 [07:07] Ah. [07:07] I'm not up-to-date with feisty-changes since Herd 4. === Fujitsu gets up to date. [07:08] Fujitsu: Oh you mean for the maintainer field. [07:08] I thought you meant for the changelog entries. [07:08] TheMuso, ah. [07:08] but I guess it still causes the same problems. [07:08] Right. #85705 now has a fix attached. [07:09] ajmitch: It seems to just be 3.3.1. That patch was already existing (it's the one that fixes that issue in Edgy). [07:09] ok [07:09] hm [07:09] bug 85795 [07:09] we'll see how well 3.3.1 goes :) [07:09] bug 85705 [07:09] Malone bug 85705 in pyinotify "Undefined symbol error when importing pyinotify" [Undecided,Unconfirmed] https://launchpad.net/bugs/85705 [07:09] http://svn.zope.org/*checkout*/Zope3/tags/3.3.1/doc/CHANGES.txt === Fujitsu tests if 3.3.1 will actually start. [07:10] I hope so [07:10] `Fixed issue 535: make HTTPInputStream work with Python 2.4.4.'... That should obsolete the patch the changelog says he updated. [07:13] Soyuz seems to have eaten that upload. [07:13] There's an accepted message, but that's all. [07:14] Gnight gang [07:14] Night, bddebian. [07:16] Ah, the publisher is probably still on manual. [07:17] shouldn't be [07:17] Well, there are 62 items in Accepted. [07:17] They're not being published. [07:18] you may be right [07:18] how inconvenient [07:19] And it's a weekend too. [07:19] No Zope for me. [07:19] sigh === ajmitch fetches the source to build [07:20] or not [07:20] not even the source package is published this time [07:20] hahaha [07:20] No. [07:20] Exactly. [07:20] I had other stuff go through earlier [07:20] Everything since 7am AEST this morning is still there. [07:20] s/this morning // [07:21] probably something broken, rather than the publisher being disabled intentionally [07:21] Like someone not starting something after the last rollout, which happened last time? === Fujitsu ponders asking in #launchpad. [07:21] is beta running? [07:21] No. [07:21] beta is still 503ing. [07:22] sigh [07:22] been like that for hours [07:22] I would presume a rollout would take somewhat less than 10 hours. [07:22] (it's been broken since I got up) [07:22] yes, same [07:22] & I repointed my bookmarks towards beta.lp [07:23] Yep, all my keyword bookmarks do too. === tuxmaniac [n=aanjhan@unaffiliated/tuxmaniac] has joined #ubuntu-motu [07:23] I'm sure they impressed upon their devs a couple of weeks ago that beta.lp was now a critical service, and should have similar uptime to production. [07:23] hah [07:23] funny [07:24] lol [07:24] you are too cynical sometimes :) [07:24] I do that. [07:24] heh === LaserJock [n=mantha@ubuntu/member/laserjock] has joined #ubuntu-motu [07:25] well, that wasn't nice [07:26] no, it wasn't, was it? [07:26] I was KDE and it just shut my computer off [07:27] LaserJock, huh? [07:27] I've had very bad luck with KDE and power managment [07:28] turn back to GNOME [07:28] I did [07:28] it's a sign [07:28] but I keep trying KDE [07:28] heh , thats funny because they both use the same backend [07:28] for PM [07:28] well, must be the frontend or something [07:28] but KDE was randomly hibernating last time [07:28] if its a bug in the frontend UI Riddell and Sebas are upstream , hint hint [07:29] :) [07:29] well, they'll just laugh at me I guess [07:29] LaserJock, I had KDE hibernate on me a few times during Dapper development, when I had a GNOME session at the sa me time. [07:29] although i did install gnome on a box at home last night, just to have one pure ubuntu box [07:29] shhh [07:30] :O === Fujitsu tells... Hobbsee! [07:30] (*jarring chord*) [07:30] Hobbsee won't mind [07:30] heh hobbsee plays with gnome now and then too, and SuSE and stuff hehe [07:30] what a confused individual [07:30] well, I just can't trust KDE unfortunately on my laptop [07:31] SuSE? Ick. [07:31] LaserJock, i would look deeper into it serouisly, not to start a KDE / Gnome thing, but they are using the same PM backends [07:31] that is if you have the time [07:31] imbrandon: I know [07:32] I just can't have my "production" machine randomly quiting [07:32] I'm not sure if I get any data loss [07:33] but I was in the middle of a lengthy build [07:33] haha i dont have any "production" machines anymore [07:33] lol [07:33] other than the servers [07:33] well, my "production" machine runs Feisty [07:34] LaserJock, start long builds on aurora with screen :) [07:34] tis what i do [07:34] it's not a pbuilder build [07:34] ahh [07:34] screen screen screen, we all screen for ice screen [07:34] i was this >< close to getting jokosher running on windows this morning [07:34] zakame: lol [07:35] I'm working on upstream stuff [07:35] hi all btw :D [07:35] I finally got some working C++ [07:35] heya zakme [07:35] I'm so proud of myself ;-) [07:35] Heya zakame. [07:35] zakame* [07:35] woo LaserJock :D [07:35] hi TheMuso, imbrandon :) === zakame is playing upstream lately === Fujitsu pulls zakame back downstream. [07:36] it's kinda fun [07:36] hehe [07:36] I think I like upstreaming better than distro'ing [07:36] I prefer them in different ways. [07:37] And I prefer Python to C++ in most situations. [07:37] imbrandon: well, I was starting to get the hang of some KDE stuff, and got some customization done [07:37] Python == good. [07:37] quite quite [07:37] Fujitsu: I'm learning both [07:37] I think it's handy [07:37] LaserJock, rockin, dont give up now ;) === ajmitch is not qualified to be an upstream [07:37]