[04:07] <pteague> how do i get tomcat5.5 to start on ubuntu?
[01:36] <hagabaka> i installed the package libaxis-java, but it doesn't seem to include some files which AXIS should have, like tomcat/webapps/axis/*. is there another package that provides it?
[01:37] <vil> hi hagabaka
[01:38] <hagabaka> hi
[01:38] <vil> I don't think so
[01:38] <hagabaka> so i should install axis from tarball?
[01:38] <vil> you can try to look up a particular file using the package searching tool at http://packages.ubuntu.com
[01:39] <vil> if you don't find it there, pls write a bug report against the package at http:/launchpad.net and / or bugs.debian.org
[01:39] <vil> http://launchpad.net and / or http://bugs.debian.org
[01:41] <hagabaka> well i'm not familiar with packaging or axis itself. i just need to install it for a class project :/
[01:41] <hagabaka> i don't know how to write the bug report or if it would be a bug
[01:48] <vil> ok, the libaxis-java provides ujst the basic axis library, which you can use with tomcat by setting the classpath properly
[01:48] <vil> it does not contain the exaples "tomcat/webapps/axis"...
[01:49] <vil> if you need them, pls file the bug
[01:49] <vil> using launchpad is really easy


[00:01] <sarnold> oh....
[00:01] <Delemas> Seems 12.04 it will work with an alternative installer.
[03:42] <Deep6> anyone here run honeyd?
[08:10] <SaberUK> hey, i'm using unattended-upgrades with automatic rebooting enabled, is there any way to tell it not to reboot if a named process is running?
[09:04] <irqq> what am I missing in the following syntax : sudo for i in {a..c}; do echo $i; done ?
[09:15] <shauno> irqq: I don't believe you can sudo a bash builtin (for).  you'd want to sudo bash -c "the command"
[09:16] <shauno> (or move sudo inside the loop, for expression; do sudo action; done)
[09:24] <irqq> shauno: I see, thanks. I other words, the $cmd in the `sudo $cmd` should be an executable found in $PATH ?
[09:25] <shauno> right.  it has to be a process that sudo can fork
[09:28] <irqq> thank you
[15:28] <sw0rdfish> hmmmmmmmmm
[16:21]  * RoyK hmmms @sw0rdfish
[16:22] <sw0rdfish> heh
[17:34] <RoyK> http://munin.karlsbakk.net/munin/karlsbakk.net/smilla.karlsbakk.net/index.html <-- interesting... the WD2001FASS drives show, over time, to be 30% faster than the Hitachi HDS723020BLA642 drivess (sde,sdh)
[20:40] <sw0rdfish> hmmmm


[11:53] <jaddi27> hi sagaci
[12:10] <sagaci> hi jaddi27
[12:11] <jaddi27> I saw you finished off the compiz strings
[12:11] <jaddi27> I was wondering whether 'bunding' should actually be 'binding', as I have never heard of the word bunding before
[12:12] <sagaci> well I guess its an upstream issue if that's the case
[12:13] <jaddi27> Yeah, it would be. I am not really sure, but just don't think bunding looks like the right word
[12:14] <jaddi27> Ah, just found something on it: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/694169
[12:15] <jaddi27> And this one: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/757945
[12:15] <jaddi27> The second one says that a fix has been released upstream (on 20 Jan 2012), and will be sent to Ubuntu soon
[12:15] <jaddi27> so I guess that answers my question
[12:16] <sagaci> yeah, the strings should be replaced whenever it hits the real updates
[12:20] <jaddi27> so when that happens, will the strings be marked as untranslated, or will it be in the changes column?
[12:22] <sagaci> it will appear as an untranslated string with the wrong version as a suggestion
[12:25] <jaddi27> Ok. I will keep an eye out for it (but will be probably beaten to it by you!)
[12:25] <sagaci> doubt it, I don't check it every day these days, usually just get for the updated language packs
[12:27] <jaddi27> Right. I have been trying to keep it down as much as I can - just leave things I am unsure of like Compiz and Nautilus


[00:29] <Sarvatt> byebye klingon? :D
[00:30]  * Sarvatt slaps forehead
[00:30] <Sarvatt> mistook the libXi sync for libX11 :)
[00:36] <Sarvatt> RAOF: savage DRI sucks huh?
[00:36] <RAOF> Sarvatt: Looks like it :)
[00:37] <RAOF> That said, in hindsight I should probably have pushed that bug on the DDX; running with swrast kills X.
[00:37] <Sarvatt> every time I see bug mail from you for desktop app crashes it's always savage DRI :D
[00:37] <RAOF> Yes! :{
[00:46] <Sarvatt> the crashes fixed by http://lists.x.org/archives/xorg-devel/2010-March/006436.html seem to be triggered by kmail mostly
[00:46] <Sarvatt> https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/401045
[00:46] <Sarvatt> https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/442144
[00:46] <Sarvatt> https://bugs.edge.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180/+bug/479031
[00:46] <Sarvatt> lots :)
[00:48] <Sarvatt> will give it a few days and see if anyone reviews it before building test packages for people, not sure if its correct. the commit its referencing is from 2007 so its been around awhile
[01:35] <Sarvatt> ok, updated the wiki some more with these new symptoms
[01:38] <Sarvatt> https://wiki.ubuntu.com/X/Bugs that is
[02:22] <RAOF> Balls.  It looks like just *loading* vga16fb can annoy the precious flower that in nouveau.
[03:10] <Sarvatt> huh RAOF? vga16fb isn't loading at all in that guys blacklist=vga16fb dmesg
[03:11] <RAOF> Right.  And in that dmesg you'll note that nouveau complains a lot less? :)
[03:11] <Sarvatt> oh i didnt look at the one with it, the blacklisted one still locks up as soon as it starts
[03:11]  * Sarvatt has WAY too many tabs open
[03:12] <RAOF> :)
[03:12] <Sarvatt> https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/447159
[03:12] <Sarvatt> needs some serious love
[03:12]  * Sarvatt todo's
[03:14] <Sarvatt> RAOF whats the bug# for the nouveau guy?
[03:14] <Sarvatt> i just had the dmesg tab open
[03:14] <Sarvatt> nevermind I see it in #nouveau
[03:14] <RAOF> 542950
[03:14] <RAOF> Yah.
[03:15] <Sarvatt> hmm, first though, that an AGP card?
[03:15]  * Sarvatt looks
[03:16] <Sarvatt> oh 6100 IGP..
[03:16]  * Sarvatt has a 6150IGP booted up right next to me with nouveau
[03:18] <Sarvatt> sure wish it was easier to see what commits we have in our kernel
[03:19] <RAOF> I recently learnt that “git log nouveau/master...” is git for “the commits in nouveau/master that aren't in your current HEAD”
[03:21] <Sarvatt> all of nouveau was added in one commit
[03:21] <RAOF> That's quite true.  Why was that command useful to me again?...
[03:23] <RAOF> Oh!  Because we know that lucid has drm from 2.6.33, so you can find the commits in nouveau/master that aren't in 2.6.33
[03:24] <RAOF> Acutally, we now have drm from <IP_ADDRESS> I believe, but there weren't any nouveau commits of interest.
[03:26] <Sarvatt> dont know what i'm gonna do with lbm-nouveau now that its 2.6.34
[03:27] <Sarvatt> theres more changes that touch nouveau outside of drm, some acpi change
[03:27] <RAOF> How much does drivers/gpu/drm interact with stuff that's out of that tree?
[03:28] <RAOF> Ah.
[03:28] <RAOF> Maybe it's time to switch to providing full-on kernels?
[03:31] <RAOF> That shouldn't be *that* much more effort than updating lbm-nouveau.
[03:32] <RAOF> “lshw causes display to freak out”.  That's my sort of bug title.
[03:48] <Sarvatt> yeaaah drivers/gpu/drm/nouveau/nouveau_irq.c where the messages are happening is a pretty rough read
[03:49] <Sarvatt> thats happening for alot of people on intel right now for some reason
[03:49] <Sarvatt> the lshw -C video making the screen trippy, doesn't happen here
[04:02] <RAOF> I think there are rather a lot of duplicates of bug #535640 wandering in at the moment.
[04:18] <Sarvatt> yeah which is odd since we had a patch to fix that in -15
[04:19] <Sarvatt> something tells me it got dropped with the drm backport and its not in there
[04:20] <Sarvatt> is EIR: 00000000 in those? batchbuffer I/O errors?
[04:20]  * Sarvatt looks
[04:20] <Sarvatt> [   74.800222] render error detected, EIR: 0x00000000
[04:20] <Sarvatt> [   74.800252] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 2128 at 2125)
[04:20] <Sarvatt> yup we are missing the patch, looking into it
[04:21] <Sarvatt> it wasn't upstream yet and I think it got dropped
[04:24] <Sarvatt> i'll ping smb since apw is on vacation, we did drop the patch
[04:33] <Sarvatt> that affected *alot* of machines, theres probably dozens of other dupes of that now
[04:37] <RAOF> Yup.  I'm wandering through them.
[04:37]  * RAOF sings the “...upon closing the laptop lid...” song.
[04:47] <RAOF> ...and that's the last of the intel bugmail.  Has the nouveaufixes kernel built yet? :)
[04:50] <Sarvatt> nouveaufixes kernel?
[04:52] <RAOF> Just pulling a couple of patches from nouveau/linux-2.6
[04:53] <RAOF> Particularly: mark LVDS as unknown if lid-closed, the slight monitor timing fix for VGA outputs, and fixing framebuffer fonts with width%8 != 0
[04:54] <RAOF> I'm going to guess that bug #540017 is *also* that missing patch :)
[04:57] <Sarvatt> theres a few grctx update commits too
[04:57] <Sarvatt> yeah but that guy is on a 945, i haven't seen that issue on <965 so I didn't dupe it yet but it does look the same
[04:58] <RAOF> Yeah.
[05:11] <RAOF> Sarvatt: Have you seen a number of intel bugs where the drm bails because agpgart loads *after* drm tries to initialise?
[05:13] <Sarvatt> no actually, I haven't come across any of those yet in ubuntu
[05:14] <RAOF> bug #542251 seems to be one, but I think I saw some more during my mail-purge.
[05:14] <RAOF> I wonder if it's reproducible?
[05:17] <Sarvatt> with these 5 second SSD boots I bet it is a big problem..
[05:24] <Sarvatt> RAOF: if you see an error like agp loading after drm in dmesg would ya mind pasting that chunk into the bug description so its searchable?
[05:25] <RAOF> Ok.
[05:26] <Sarvatt> helps *alot* later on finding dupes like https://bugs.edge.launchpad.net/ubuntu/+bugs?field.searchtext=*ERROR*+Cannot+initialize+the+agpgart+module&orderby=-importance&search=Search&field.status:list=NEW&field.status:list=INCOMPLETE_WITH_RESPONSE&field.status:list=INCOMPLETE_WITHOUT_RESPONSE&field.status:list=CONFIRMED&field.status:list=TRIAGED&field.status:list=INPROGRESS&field.status:list=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.
[05:26] <Sarvatt> omit_dupes=on&field.has_patch=&field.has_no_package=
[05:27] <Sarvatt> err
[05:27] <Sarvatt> https://bugs.edge.launchpad.net/ubuntu/+bugs?field.searchtext=*ERROR*+Cannot+initialize+the+agpgart+module
[05:28] <Sarvatt> upstream people really want all agp modules built in :(
[05:29] <RAOF> Really?  Why?
[05:31] <Sarvatt> i'd have to dig through mails to find reasons, i've just seen it brought up by the radeon and intel people a ton of times over the past year
[05:32] <Sarvatt> think there was a recent thread on intel-gfx about it, lets see..
[05:37] <Sarvatt> here we go
[05:37] <Sarvatt> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1f7a6e372e9cb4d749f34c0738d832e6cadb4071
[05:37] <RAOF> Ok, so that's probably not in our tree.
[05:37] <Sarvatt> nope was post .33
[05:38] <Sarvatt> thought i saw it recently
[05:38] <Sarvatt> hmm it looks like it just fails to load if agp isn't already loaded, not sure that it tries again?
[05:39] <RAOF> It uses the magic of linkage.
[05:40] <RAOF> You'll notice that intel-agp.c exports the symbol that i915 consumes?  That should ensure that intel-agp is loaded before i915.
[05:41] <RAOF> At least, that's my understanding of it.  By explicitly depending on a symbol in intel-agp, i915 will be guaranteed to load after intel-agp, which will have done its init.
[05:42] <RAOF> Are you going to attach that patch to the bug?
[05:42] <Sarvatt> ok so thats 3 patches now I'll see if stable will take
[05:42] <Sarvatt> yepyep
[06:00]  * RAOF :note to self.  Don't try to rsync /proc
[06:13] <tjaalton> airlied mentioned it once that he's probably going to make the agp modules mandatory (built-in)
[06:15] <RAOF> It seems like a rich seam of bugs is possible if drm only depends on the agp core, which won't actually provide the necessary stuff until the platform-specific module is loaded.
[06:28] <Sarvatt> i've seen it happen on radeon too and they just say agp should be built into the kernel
[06:29] <Sarvatt> sheesh so many dupes for that 965 hang
[06:32] <Sarvatt> at least its super easy to spot, EIR is 0000000 and do_wait_request returns -5 (which is -EIO) in current dmesg
[06:33] <Sarvatt> found a bunch more dupes for the agp one too
[06:53] <ara> bryceh, hello, still around?
[07:20] <Sarvatt> thats a new one - intel_gpu_dump: page allocation failure. order:8, mode:0x40d0
[07:21] <Sarvatt> getting close to  hitting 50 dupes tonight on https://launchpad.net/bugs/535640 :D
[07:22] <Sarvatt> oh only 27 so far, i was going by the total bug count on -intel and someone else must be working it :D
[07:46] <Sarvatt> ahhh so these two bugs are intertwined
[07:47] <Sarvatt> we've got DPMS events hanging the GPU, then batchbuffer I/O errors, then in comes the "X: ../../src/i830_batchbuffer.h:79: intel_batch_emit_dword: Assertion `pI830->batch_ptr != ((void *)0)' failed." from the other bug with tons of dupes
[07:49] <Sarvatt> found one of the dupes that showed both bugs happening in one log and it all makes sense now :)  http://launchpadlibrarian.net/41051827/GdmLog2.txt
[09:01] <jcristau> Sarvatt: ewww order 8 allocation?  that's... bad.
[09:06] <RAOF> Sarvatt: I've wandered through and duped a bunch of bugs that one. :)
[09:13] <bryceh> ara, hi
[10:47] <jibel> could you have a look at bug 544781 . nvidia-96 failed to upgrade from 9.10 to 10.04. Thanks.
[10:51] <RAOF> Well, that's pretty cool.  We've managed to russtle up a guy with some hardware where the -nv driver can only drive the LVDS and the nvidia driver can only drive an external monitor.
[10:53] <bryceh> %-)
[12:14]  * tormod curses xchat-gnome
[12:43] <bjsnider> tormod, just use xchat
[12:44] <bjsnider> xchat-gnome is notable for being functionally challenged
[12:46] <tormod> bjsnider, thanks I'll try it, this time connections were acting up after resume
[15:59] <komputes> bryceh: So, any ideas what is causing gnome-session to flip my screen (Bug #544813). Any testing/troubleshooting you would like me to preform?
[16:00] <jcristau> komputes: bogus stuff in ~/.config/monitors.xml (or whatever it's called)
[16:01] <komputes> jcristau: would you like me to remoce and test again (I think I have already tried this)
[16:01] <tjaalton> create a new user and try with it
[16:02] <komputes> jcristau: the monitor is not flipped upside down as gnome-display-properties proposes it, if you look carefully, the items are flipped inside out
[16:02] <komputes> tjaalton: I have done this as well, but will try it again now
[16:03] <tjaalton> nice effect
[16:05] <tjaalton> so just the upper panel flipped over
[16:05] <tjaalton> both actually
[16:06] <tseliot> komputes: I guess your problem is that you're using the wrong libraries for your driver
[16:06] <tseliot> komputes: how did you switch between drivers?
[16:07] <tjaalton> this isn't a driver issue
[16:07] <tjaalton> the panels are mirrored somehow
[16:07] <komputes> tseliot: jockey-gtk
[16:07] <tseliot> tjaalton: which is why I didn't call it driver issue ;)
[16:07] <komputes> yes, but when entering and exiting gnome-session, the windows/screen is notmal for a second
[16:08] <tjaalton> tseliot: wrong libGL could do that?
[16:08] <tseliot> tjaalton: yep
[16:08] <komputes> tseliot: however I did reproduce it to see if it constantly fails after installing the nvidia driver and it does seem to be the root cause
[16:09] <tjaalton> alrighty
[16:09] <tseliot> komputes: let me rephrase my question, what did you do to switch between drivers in Jockey?
[16:10] <tseliot> and did you restart your computer?
[16:10] <tseliot> I suspect that you're using Nvidia's libGL with intel
[16:11] <komputes> tseliot: i plugged in the usb key, ran kockey, downloaded nvidia driver, rebooted, changed the resolution and wrote to xorg.conf, moved usb key to mini 9, removed xorg.conf from tty, restarted, and screen was flipped.
[16:11] <komputes> tseliot: shouldn't bulletproof-X know better?
[16:11] <tseliot> komputes: you should have disabled nvidia from Jockey first
[16:12] <komputes> tseliot: I don't remember having to do this before
[16:12] <komputes> tseliot: how can I disable it from a TTY?
[16:12] <tseliot> yes, provided that X fails to start
[16:12] <tseliot> komputes: sudo update-alternatives --config gl_conf
[16:12] <tseliot> sudo ldconfig
[16:13] <komputes> tseliot: so i need to diable nvidia from jockey and remove the xorg.conf every time i move my USB key to another computer?
[16:13] <tseliot> sudo update-initramfs -u
[16:13] <tseliot> and reboot
[16:13] <tseliot> komputes: yep, or you can do it manually
[16:14] <tseliot> disabling nvidia shouldn't remove the package though, I'll talk again to pitti about this
[16:14] <komputes> tseliot: any way around this, that it could be made to auto-detect?
[16:14] <komputes> (as I believe this has worked in previous releases)
[16:14] <tseliot> komputes: things were quite different in previous releases
[16:15] <tjaalton> and they didn't work
[16:15] <tjaalton> like you suggest
[16:15] <tjaalton> komputes: ^
[16:15] <komputes> thanks Alberto
[16:15] <komputes> tjaalton: will test to make sure, cheers
[16:17] <tseliot> np
[16:45] <Sarvatt> hmm, newest blob is failing to resume about 1 in 5 times and not having any luck finding out why unlike before
[18:42] <Sarvatt> hmm, think this would work? I know its a horrible hack, not sure if it's correct and wont be around a machine I can try it on until tonight - http://sarvatt.com/downloads/patches/0001-hw-xfree86-common-xf86AutoConfig.c-Append-Module-sec.patch
[18:45] <Sarvatt> nvidia works without an xorg.conf but it loads libglx.so from /usr/lib/xorg/modules/extensions/ instead of /usr/lib/extra-modules/ where nvidia-current puts it unless there's a module section explicitly loading glx
[18:47] <Sarvatt> so it loads SGI-GLX stuff instead of NV-GLX, thats the only thing stopping us from having no a xorg.conf nvidia blob. not sure about fglrx though
[18:50] <Sarvatt> fglrx looks strange, its not installing stuff to /usr/lib/xorg/extra-modules like nvidia is and still has an xsession script changing LIBGL_DRIVERS_PATH and LD_LIBRARY_PATH?
[18:53] <tjaalton> still, if you have a conffile it'll only try the one on the top of the list
[18:53] <tjaalton> so if you put a blob in there it'll fail if you don't have it installed...
[19:46] <Sarvatt> i dont know for sure but it looks like disabling nvidia-current will unset the extra-modules alternative link so the libglx from there wouldn't be used anyway and wouldn't hurt?
[20:30] <Sarvatt> i'll put it on a ppa with a change to prefer nvidia first then nouveau and test it out on a bunch of configurations
[21:18] <Sarvatt> oops, thought disabling FBC didn't actually work afterall since I started getting hangs again today but I didnt notice we got a -17 kernel update that overwrote my old one :D
[21:21] <bryceh> heh
[21:39] <Sarvatt> hmm, anyone else having problems with gnome-terminal after todays updates? its blacking out my screen except a sliver of the panel until i move the cursor out of the gnome-terminal window, this has been happening for awhile but its happened at least 10 times today vs once a week for the past few weeks
[21:44] <Sarvatt> ok *thats* odd, someone reporting lshw corrupts their display on my exact machine
[21:51] <tjaalton> xserver merge pushed to git, not build-tested though. wondering if more of the udeb support needs to be dropped
[21:54] <Sarvatt> hmm, I wonder if lshw screwing up the display might be related to having vga16fb on fb1, only difference i can see between me and this bug report with my machine
[21:54] <tjaalton> or bdeps relaxed
[21:54] <RAOF> Sarvatt: That's an excellent guess.  Let's see...
[21:55] <Sarvatt> rebooting now to find out
[21:56] <RAOF> Well, doesn't kill *this* laptop.
[21:56] <Sarvatt> hmm, i should use a livecd incase its different, all these bugs are
[22:19] <BUGabundo> I'm truly disappointed... installed Lucid on a recently new Desktop PC, running on a 64GB SSD, with Win7 and VirtualBox. install time inside the VM: 2-3min. boottime: 2-3 sec till gdm.  after installing guest additions X would not start :(
[22:26] <Sarvatt> yay
[22:26] <Sarvatt> livecd + lshw -C network = trippy colors
[22:28] <BUGabundo> ahaha
[22:28] <BUGabundo> oh man
[22:28] <BUGabundo> I remember gusty
[22:28] <BUGabundo> I had so many colors on my screen back then
[22:38] <kklimonda> BUGabundo: hmm? you have a computer with win7?
[22:38] <BUGabundo> no
[22:38] <BUGabundo> it wasn't mine
[22:38] <BUGabundo> from a friend
[22:39] <BUGabundo> he was showing off how fast the SSD was
[22:39] <BUGabundo> so I installed Ubuntu on it
[22:40] <kklimonda> inside vm?
[22:40] <BUGabundo> yep
[22:40] <BUGabundo> virtual box
[22:40] <BUGabundo> it was SOOOOOOOOOOOOOOO fast
[22:40] <BUGabundo> I was planning buying a 32GB ssd. now I definitely want one
[22:41] <kklimonda> :)
[22:45]  * baptistemm have a 160 GB ssd disk :p
[22:45] <BUGabundo> you did???
[22:45] <baptistemm> and yes this blazing fast to boot
[22:45] <BUGabundo> how much did that baby cost
[22:45] <baptistemm> and even for testing vm this really really valuable
[22:46] <baptistemm> BUGabundo, too much
[22:46] <BUGabundo> I bet
[22:46] <BUGabundo> at current cost its around 400-500€
[22:46] <BUGabundo> for a 128GB
[22:46] <BUGabundo> so a 160 who whooo
[22:52] <baptistemm> I paid mine 350€
[22:52] <baptistemm> coming from taiwan
[22:54] <kklimonda> how long is life expentancy for ssd disks?
[22:58] <BUGabundo> ahh that's _cheap_
[22:58] <BUGabundo> kklimonda: depends *very* much on manufacture and series
[22:59] <RAOF> And correlates well with cost - the best ones will be single-level cells, and will cost a bomb.
[22:59] <BUGabundo> on those without realiners you can count with about 10k re-writes for sector
[23:00] <BUGabundo> on the most recent, dynamic reallocation , and extra sectors, from high brand manufactures (intel, coz, etc) something like 500k-1M re-writes
[23:05] <BUGabundo> you got entry level kingston for 150€ for 32GBs
[23:05] <BUGabundo> and intel is launching a new series of their famous X25 for entry price
[23:07] <baptistemm> BUGabundo, mine is a x25 g2
[23:08] <BUGabundo> don't know the g2 series
[23:14] <bryceh> RAOF, btw when you get a chance look at #545493 - this is from a friend of mine here in Portland
[23:16] <RAOF> Hm.  Someone complaining about poor compiz performance with nouveau.
[23:17] <Sarvatt> lol
[23:18] <RAOF> Actually, it seems to be just mis-filed against nouveau; the user doesn't seem to be using the PPA, so...
[23:19] <tormod> bryceh, now that Benjamin has triaged bug 544904, is anything else needed or can I trust the archive managers to get to it?
[23:20] <Sarvatt> not a single 965 GPU hang report that isn't a dupe of the DPMS problem
[23:20] <bryceh> Sarvatt, wow
[23:21] <bryceh> tormod, should be good.  Note that the sync processing crew is a bit slow so might be a few days
[23:21] <tormod> is anyone gonna merge -ati? I can volunteer but not today
[23:22]  * tormod reboots into 2.6.32-17
[23:23] <Sarvatt> not sure its a good idea :D
[23:25] <bryceh> Sarvatt, why?
[23:25] <Sarvatt> https://bugs.freedesktop.org/show_bug.cgi?id=27186
[23:25] <bryceh> oh yeah
[23:25] <RAOF> Sarvatt: There's no lbm-nouveau for -17 yet, is there?
[23:26] <Sarvatt> fixed just today but the fix isnt in 6.12.192
[23:26] <bryceh> Sarvatt, but it's marked fixed
[23:26] <RAOF> Sorry, should just look myself :/
[23:26] <bryceh> well, we can pull the patch in
[23:26] <Sarvatt> RAOF: i uploaded it like 8 hours ago but its mozilla-ed I think
[23:26] <bryceh> tormod, if you can get to it tomorrow I'll be happy to sponsor it
[23:27] <bryceh> otherwise it's on my todo list to do this week
[23:27] <Sarvatt> looking through the lshw code to see how to get around it turning the drmfb into the vga16fb..
[23:28] <RAOF> Can we just make vga16fb fail to load when we've got a real framebuffer?
[23:28] <RAOF> As I say, then nouveau guys are paranoid about it messing things up.
[23:30] <Sarvatt> we've got a silly patch to vga16fb making it bind to all video devices
[23:30] <tormod> bryceh, ok I'll either try tomorrow or not at all :)
[23:30] <RAOF> Sarvatt: Why?  Can we drop that patch?
[23:30]  * Sarvatt wishes plymouth could be deferred to MM..
[23:31] <bryceh> Sarvatt, what's that patch against? kernel?
[23:31] <Sarvatt> so there's a FB for plymouth to use for any video card always
[23:32] <Sarvatt> yeah its in ubuntu-lucid.git
[23:32] <Sarvatt> they added that back in november or december
[23:32] <RAOF> Can't we just have that keybuk's swanky text-boot?  That looks awesome :)
[23:32] <Sarvatt> swanky text-boot?
[23:32] <Sarvatt> you mean the splash you see when you dont have KMS?
[23:32] <RAOF> Yeah; the one you'll get currently if you don't have kms.
[23:32] <Sarvatt> because that needs a color framebuffer
[23:33] <RAOF> bryceh: #545493 dealt with; nouveau kernel ABI bump in xorg-edgers strikes again!
[23:34] <RAOF> Now, coffee.
[23:34] <Sarvatt> heyo tormod! :)
[23:36] <tormod> hey sarvatt :)
[23:41] <Sarvatt> tormod: you have an rv515 don't you? do you have any problems with lucid at the moment?
[23:42] <tormod> Sarvatt, I haven't got to test it with lucid yet. maybe friday.
[23:42] <Sarvatt> ahh ok, there are alot of complaints from people on RV515 and RV530 with 2.6.33's drm
[23:43] <Sarvatt> radeon.new_pll=0 is fixing it for RV530 people but haven't figured out the RV515 flickering problems yet
[23:46] <tormod> the irc log mentions savage DRI trouble? I have to test that again also, now that the X crasher got fixed
[23:48] <Sarvatt> yeah savage is horrible at the moment with so many clutter based apps, clutter completely falls apart on savage because it only has 16 bit visuals and breaks some assumptions it has
[23:52] <tormod> I think savage can do 24 bit, but 16 bit is default because it works better and many cards have little VRAM
[23:52] <tormod> will clutter be fixed?
[23:55] <RAOF> Isn't clutter 1.2 supposed to be better about that?  That's getting merged in soon.
[23:55] <Sarvatt> sweet, it is?!
[23:56] <RAOF> Yup.  GNOME 2.30 requires it, apparently.
[23:56] <Sarvatt> 1.2 is a lot better about it but it still needs fixes
[23:56] <Sarvatt> oh mutter counts for gnome 2.30? thought that was the only thing requiring 1.2
[23:56] <Sarvatt> one sec, I'll find the bug where some guy posted some patches for clutter 1.2 branch to work on savage
[23:56] <Sarvatt> it was that netbook launcher bug you were working on RAOF
[23:57] <Sarvatt> https://bugs.launchpad.net/bugs/467474


[12:17] <ajmitch> kalon33: I'll tell you when it's done
[12:17] <ajmitch> it seems to be going rather slowly
[12:18] <kalon33> ok, thank you :)
[12:18] <ajmitch> Kmos: for updates to existing packages, it's often easier to put it as a debdiff in a bug against the existing package
[12:19] <marseillai_> hi
[12:19] <marseillai_> i have to move lib from /usr/lib to /usr/lib/myapps . how can i do this with CDBS ?
[12:20] <LaserJock> Fujitsu: around?
[12:20] <Nafallo> LaserJock: JID says Sleeping.
[12:21] <LaserJock> now why would he be doing that? ;-)
[12:22] <LaserJock> I thought he might enjoy the last comment on Bug #85474
[12:22] <ubotu> Launchpad bug 85474 in maxima "Maxima frontends cannot connect" [Undecided,Needs info]  https://launchpad.net/bugs/85474
[12:22] <ajmitch> hi LaserJock
[12:22] <LaserJock> person reports a similar bug in fedora
[12:22] <LaserJock> hola ajmitch
[12:24] <crimsun> geser: ok, do you want to generate a new dsc and tarball, then?
[12:25] <jussi01> ok, ive made the man page, ive got dh_installman in my rules file, but i still have no man page. what am i doing wrong?
[12:25] <geser> crimsun: will do
[12:27] <boss-bcp> Could someone take a look at libpam-cups ( http://revu.tauware.de/details.py?upid=4936 ) for me? It's currently been advocated by one MOTU.
[12:31] <ajmitch> fixed up the build-depends?
[12:31] <ajmitch> there's also some very ugly stuff going on in postinst
[12:31] <ajmitch> alternatives *only* work when packages cooperate
[12:32] <ajmitch> a subsequent update of cups would probably blow away the symlinks you add
[12:39] <jekil> i run a suid program, so it has a uid xxx, but i cant display it on X session of user yyy, how i can do?
[12:40] <jekil> the program is a gnome applet that must run suid
[12:40] <geser> crimsun: https://bugs.beta.launchpad.net/ubuntu/+source/devscripts/+bug/108232/comments/10 contains the tar.gz
[12:40] <ubotu> Launchpad bug 108232 in devscripts "[Merge]  devscripts 2.10.4ubuntu1" [Undecided,Fix committed]
[12:42] <crimsun> thanks, looking as soon as these kids give me a moment
[12:44] <geser> the only changes are: chmod +x test/debchange.pl scripts/requestsync.py and the new changelog entry
[12:46] <ajmitch> Kmos: rather large whitespace-only changes in the diff, orig.tar.gz is modified from upstream
[12:48] <kalon33> /join #ubuntu-fr
[12:48] <kalon33> sorry :p
[12:48] <ajmitch> kalon33: you can upload now
[12:48] <kalon33> bad command :p
[12:48] <kalon33> thanks ajmitch :)
[12:49] <crimsun> geser: uploaded, thanks
[12:49] <Kmos> ajmitch: maybe it's because of the whitespace in the end of ddclient executable file
[12:50] <ajmitch> Kmos: there are literally thousands of lines with whitespace changes
[12:52] <Kmos> ajmitch: that whitespace in the end of file make diff to do that
[12:52] <Kmos> it's the only explanation, because the .orig.tar.gz isn't changed by me
[12:52] <kalon33> ajmitch : When I recover my password in the revu main page, I got "None" is it usual or not ?
[12:53] <ajmitch> kalon33: you can get your password after a successful upload
[12:53] <ajmitch> Kmos: nothing will touch the orig.tar.gz
[12:53] <ajmitch> so something you did must have changed it
[12:53] <kalon33> okay, thanks, I'm a newbie for that ^^
[12:53] <ajmitch> size is slightly different, md5sum is different
[12:55] <Kmos> ajmitch: i've uploaded another one
[12:55] <Kmos> you see that on file ddclient_3.7.1-0ubuntu1.diff.gz ?
[12:57] <Kmos> -				  'skip' => 'local:',
[12:57] <Kmos> +				  'skip' => 'local:',
[12:57] <Kmos> stuff like that ?
[01:00] <jekil> someone have an example of a setuid wrapper?
[01:00] <kalon33> here is my package http://revu.tauware.de/details.py?upid=4955 if someone could give his advice on it... :)
[01:01] <ajmitch> Kmos: yes, it's messy
[01:06] <Kmos> ajmitch: i think i've fixed it :)
[01:07] <Kmos> ajmitch: http://revu.tauware.de/details.py?upid=4956
[01:08] <ajmitch> diff is still 158KB
[01:08] <ajmitch> looks a lot saner though
[01:09] <ajmitch> you're still using a different orig.tar.gz to what is on sourceforge
[01:09] <Kmos> i've used svn export https://svn.sourceforge.net/svnroot/ddclient/trunk/svn ddclient
[01:10] <ajmitch> Kmos: um
[01:10] <ajmitch> why?
[01:10] <ajmitch> you're taking trunk & saying it's 3.7.1
[01:10] <ajmitch> btw, please remove the log file :)
[01:10] <Kmos> i'll download it
[01:10] <ajmitch> it contains things you'd rather not share with the world
[01:10] <Kmos> oki
[01:11] <ajmitch> (assuming it's yours)
[01:11] <Kmos> i'll do it, thx
[01:13] <geser> ajmitch: the debian package for ddclient contains also a log file
[01:15] <superm1> ajmitch, when you finish looking over ddclient, would you a few moments for another revu?
[01:17] <Kmos> ajmitch: http://revu.tauware.de/details.py?upid=4957
[01:17] <ajmitch> geser: I hope it's just an example then
[01:17] <ajmitch> superm1: no, and I shouldn't be spending any time on ddclient either
[01:17] <superm1> ajmitch, ah okay :)
[01:17] <ajmitch> this is as far as I can go right now with ddclient
[01:19] <Kmos> ups, now patches failed.. :(
[01:19] <Kmos> let's work
[01:19] <superm1> Well if there are any other takers up for a revu in here: http://revu.tauware.de./details.py?upid=4910
[01:30] <jmg> #55782
[01:30] <jmg> hmmm
[01:33] <kalon33> good night all ;)
[01:34] <pygi> somebody remind me the command to generate the time and date stuff for changelog pls?? :)
[01:34] <Nafallo> ehrm... dch? :-)
[01:35] <pygi> Nafallo, danke :)
[01:36] <ajmitch> pygi: emacs
[01:36] <pygi> ajmitch, I don't use that :P
[01:37] <ajmitch> your loss
[01:37] <superm1> thx for the backport jdong_
[01:38] <pygi> ajmitch, let's not go into that again :P
[01:41] <ajmitch> pygi: don't you want an editor war? :(
[01:41] <pygi> ajmitch, nah
[01:41] <ajmitch> oh well
[01:44] <pygi> ajmitch, mind doing an upload for me?
[01:44] <pygi> or anyone else who I can bug for that matter? :)
[01:45] <ajmitch> can't, heading out the door in a few minutes
[01:45] <pygi> oki, np
[02:03] <bddebian> Crap, I think some of the asterisk modules are going to need an SRU :-(
[02:04] <pygi> bddebian, heh
[02:04] <bddebian> Hello pygi
[02:05] <bddebian> Gah, biab
[02:08] <eolo999> pygi, 822-date
[02:09] <pygi> eolo999, danke, but got it already =)
[02:10] <eolo999> pygi, ok
[02:13] <ryanakca> Why isn't my package showing up on REVU? I dput'd it 20 or so minutes ago
[02:13] <pygi> ryanakca, patience :)
[02:14] <ryanakca> lol
[02:14] <ryanakca> pygi: I'm used to it showing up in 10 minutes :)
[02:14] <pygi> ^_^
[02:15] <eolo999> i'm looking for a guide on writing new dpatch rules for a package. I've seen it but don't remember where (motu-school?). Someone can give me an address?
[02:15] <ryanakca> And, can a REVU admin resync the keys or something? I added a uid to my gpg key (ryanakca@kubuntu.org), but, I can't retrieve my password for it on REVU... just for my old addy.
[02:15] <pygi> ryanakca, poke sispotty
[02:16] <ryanakca> eolo999: https://wiki.ubuntu.com/MOTU/School/PatchingSources?highlight=%28patch%29 https://wiki.ubuntu.com/MeetingLogs/openweekfeisty/patching?highlight=%28patch%29
[02:16] <eolo999> thx ryanakca
[02:16] <ryanakca> eolo999: the rest are https://wiki.ubuntu.com/?action=fullsearch&context=180&value=patch&titlesearch=Titles
[02:16] <ryanakca> pygi: kk, thanks
[02:28] <crimsun> `revu-key update` running.
[02:40] <crimsun> hmm, keyserver's timing out.
[02:40] <ryanakca> crimsun: thanks
[02:40] <ryanakca> pygi: hmm..
[02:45] <bddebian> Are we supposed to reject breezy bugs flat out now?
[02:45] <jdong> bddebian: sounds good :)
[02:46] <crimsun> bddebian: yes.  It was EOL'd circa 7.04 release.
[02:47] <crimsun> bddebian: free for a query?
[02:52] <bddebian> crimsun: Any time for you man
[02:53] <crimsun> thanks.
[02:53] <eolo999> ryanakca, i still can find an article i've seen about writing debian/rules from scratch... it is a package that had not a patch system...
[02:55] <ryanakca> eolo999: hmm... read http://doc.ubuntu.com/ubuntu/packagingguide/C/index.html and http://www.us.debian.org/doc/debian-policy/
[02:56] <bddebian> >4,000 unconfirmed bugs is just insane :-(
[03:04] <jmg> bddebian: where?
[03:04] <jmg> feisty?
[03:04] <bddebian> jmg: ubuntu
[03:04] <jmg> need some triagers
[03:07] <crimsun> keyring sync completed.
[03:09] <jmg>  ugh.
[03:14] <bddebian> Anyone know why we need orbit and orbit2 in the repos?
[03:15] <crimsun> well, a lot of packages build-dep on liborbit2-dev
[03:16] <crimsun> only a couple against liborbit-dev, though.
[03:17] <azeem> but Barry doesn't care about Gnome
[03:18] <ryanakca> crimsun: thanks
[03:18] <bddebian> hah
[03:19] <ryanakca> hmm... I dput my package to revu over an hour ago... nothing (jailkit)
[03:19] <ryanakca> (nothing = I can't see it on http://revu.tauware.de)
[03:20] <ajmitch> ryanakca: it's not in the rejected queue
[03:20] <ajmitch> ryanakca: which generally indicates that you uploaded to the wrong place
[03:22] <ryanakca> ajmitch: http://pastebin.ca/465259    ... same thing as last time
[03:22] <bddebian> I'm just wondering if Bug #31662 is worth giving a shit about
[03:22] <ubotu> Launchpad bug 31662 in orbit "orbit does use it's own copy of libIDL, not the packaged one" [Medium,Unconfirmed]  https://launchpad.net/bugs/31662
[03:23] <ajmitch> ryanakca: ok, it's there this time
[03:23] <ryanakca> ajmitch: kk
[03:25] <ryanakca> can someone please review http://revu.tauware.de/details.py?upid=4961
[03:26] <ryanakca> It's a chroot utility
[03:26] <ryanakca> builds fine in pbuilder-gutsy, and lintian + linda return no errors (Just a couple I: about a minus sign being used instead of a hypen in the man pages)
[03:27] <ryanakca> s/hypen/hyphen
[03:34] <ScottK> ajmitch: Do you have time to look at a debdiff for an SRU candidate?
[03:35] <crimsun> url?
[03:35] <ScottK> The last comment in Bug #108612.
[03:35] <ubotu> Launchpad bug 108612 in pythoncad "[apport]  pythoncad crashed with ExpatError in parse()" [Medium,Fix released]  https://launchpad.net/bugs/108612
[03:35] <ScottK> Thanks.
[03:36] <ScottK> ajmitch just isn't mean enough to keep fans like me away.
[03:36] <crimsun> ajmitch: are you handling the above debdiff?
[03:37] <crimsun> (avoiding stepping on toes)
[03:39] <crimsun> ScottK: 0.1.33-2ubuntu0.1~proposed1, please
[03:40] <ScottK> crimsun: Ah, yes.  Sorry about that.
[03:42] <ScottK> crimsun: Anything else?  If not I'll attach the change to the bug?
[03:43] <crimsun> ScottK: it looks fine to me aside from that triviality
[03:45] <ScottK> crimsun: Edited and attached.
[03:45] <ajmitch> crimsun: no, I should be working
[03:46] <crimsun> ajmitch: ok
[03:46] <crimsun> ScottK: uploaded.
[03:47] <ScottK> crimsun: Thanks.
[03:47] <crimsun> np
[03:49] <bddebian> Heya persia
[03:49] <persia> hey bddebian
[03:56] <TheMuso> Are there still known issues with linux-libc-dev?
[03:56] <crimsun> apparently.
[03:56] <crimsun> 2.6.22-1.5 FTBFS on !ia64
[03:57] <zakame> aww
[03:57] <crimsun> as steven pointed out about 14 hours ago
[03:57] <TheMuso> Ok, explains why a package here seems to bomb on an ioctl constant, even though its properly declared  by a chain of header files.
[03:57] <TheMuso> this is on i386.
[03:57] <TheMuso> Or is that something totally unrelated?
[03:57] <crimsun> it's likely related
[03:58] <crimsun> hmm, that's actually an awesome, if not brutal, idea
[03:58] <TheMuso> crimsun: ??
[03:58] <crimsun> ship a broken linux-libc-dev in the final release so those wacko compile-everything-yourselves can't
[03:58] <TheMuso> hahaha
[03:59] <TheMuso> crimsun: Ok do you want to deal with the bug reports?
[03:59] <TheMuso> for that
[03:59] <crimsun> -> "Fix released"
[03:59] <crimsun> :)
[03:59] <TheMuso> heh
[04:00] <crimsun> seriously, though, it'll probably make more sense to revisit the source package after >> 2.6.22-1.5 is available on i386
[04:00] <TheMuso> Yeah true.
[04:00] <TheMuso> WIll keep my eye out.
[04:00] <TheMuso> I'm actually surprised that the package in question uses ioctls.
[04:02] <TheMuso> No actually I shouldn't be.
[04:02] <TheMuso> uses sockets
[04:03] <TheMuso> I'll guess we won't see Mom back on until this problem is fixed also.
[04:04] <crimsun> is libxine1-ffmpeg installed?
[04:05] <crimsun> err, -ECHANNEL
[04:05] <TheMuso> heh
[04:18] <ScottK> Is dpatch a Build-Dep or a Build-Dep-Indep?
[04:23] <ajmitch> ScottK: build-dep, it's usually run in the clean: target
[04:23] <ScottK> ajmitch: Thanks.
[04:27] <ScottK> eolo999: Are you there?
[04:31] <ScottK> Is there any kind of special merit badge for successfully adding dpatch to a non-cdbs package (learned some things today)?
[04:31] <ajmitch> no
[04:32] <ScottK> OK.
[04:32] <ScottK> Back to fixing...
[04:34] <bddebian> ScottK: I'll give ya one ;-)
[04:40] <bddebian> Ah well, bed time gnight folks
[04:40] <persia> bddebian: good night
[05:05] <eolo999> ScottK, yes unluckily...it's five o clock and my son is not sleeping
[05:05] <ScottK> Yeck.
[05:06] <ScottK> Check your e-mail.
[05:06] <ScottK> I hope I did what you would have wanted.
[05:06] <ScottK> eolo999: ^^^
[05:08] <eolo999> thanks for all your work
[05:08] <ScottK> eolo999: Thank you for your contribution.
[05:09] <eolo999> i read the e-mail
[05:09] <ScottK> That one turned out to be a little more complex than I had expected.
[05:09] <eolo999> i hope that pysol now 'really works' and hope to find an easier app to package ;)
[05:09] <ScottK> Yes.
[05:10] <ScottK> But don't forget, next after it gets approved for Ubuntu, we want to send the patch to Debian so they can use it too.
[05:10] <eolo999> it's possible to have a list of commands you used?...
[05:11] <eolo999> or it's too long
[05:11] <ScottK> eolo999: Yes.  I will e-mail to you.
[05:12] <ScottK> Is there anyone from UUS available to look at eolo999's fix for Bug #39975.
[05:12] <ubotu> Launchpad bug 39975 in pysol "Automatic play -> Auto drop setting forgotten" [Medium,Confirmed]  https://launchpad.net/bugs/39975
[05:13] <eolo999> ScottK, again you have been very kind, thanks
[05:14] <ScottK> eolo999: The part I did is not something you should expect to have to do.  As the page you found said, adding dpatch is not easy.
[05:14] <ScottK> eolo999: If no one is available now, it also goes to a mailing list of people that can upload and so we just wait for the bug status to change.
[05:15] <ScottK> I also have a sync request: Bug #111155 that's ready for UUS.
[05:15] <ubotu> Launchpad bug 111155 in pyyaml "sync request pyyaml 3.04-1 from Debian Unstable (main)" [Undecided,Unconfirmed]  https://launchpad.net/bugs/111155
[05:16] <eolo999> if you got an idea of the next package I can work on, tell me ;-)
[05:16] <ScottK> OK. You can also pick.
[05:18] <ScottK> eolo999: You want to look into Bug #110219?
[05:18] <ubotu> Launchpad bug 110219 in python-gnuplot "python-gnuplot package not working in feisty fawn" [Undecided,Unconfirmed]  https://launchpad.net/bugs/110219
[05:18] <eolo999> exactly, where do i find packages that need a fix?
[05:18] <ScottK> Look for interesting looking bugs in Launchpad.
[05:19] <ScottK> I have not looked at that bug in any detail.  It was on my list of bugs to look at 'later'.
[05:19] <ScottK> It may turn out to be easy or hard, I have no idea.
[05:19] <ScottK> Your Python is clearly up to hard ones.  I thought your Pysol fix was a good approach.
[05:21] <jdong> heaven help me.....
[05:21] <jdong> I have just spent half an hour writing a russian reversal script......
[05:21] <ScottK> What have you done now jdong?
[05:22] <jdong> In Soviet Russia, a russian reversal script writing YOU
[05:22] <jdong> obviously it needs some work
[05:22] <jdong> but it is one step closer to cliche'ing yet another joke
[05:22] <ScottK> OK.
[05:22] <jdong> lol, just me being my wacko self :D
[05:23] <jdong> haha!
[05:23] <jdong> I still love Ubuntu :)
[05:23] <jdong> so how are you doing :)
[05:23] <ScottK> Doing good.
[05:23] <jdong> glad to hear
[05:23] <ScottK> Getting other people to fix bugs that annoy me is always good.
[05:24] <jdong> yay :)
[05:24] <ScottK> Grow the community at the same time.  All that good stuff.
[05:24] <jdong> now if only all these dapper-backports would triage themselves... :D
[05:24] <eolo999> thanks ScottK , now it's time to rest for me ... i'll give a closer look at that bug tomorrow, otherwise i could stay up till tomorrow : )
[05:24] <jdong> eolo999: you'll soon learn not to sleep :D
[05:25] <ScottK> eolo999: Yes, get some rest.
[05:25] <ScottK> jdong: He has an 11 month old.  He knows already.
[05:25] <eolo999> jdong, i'm learning with my little son
[05:25] <jdong> eolo999: ah, yes, that is an excellent way to learn :)
[05:25] <jdong> I remember when my little sister was that age
[05:25] <jdong> sleep definitely did not exist
[05:25] <eolo999> that's why i started python dev
[05:26] <ScottK> eolo999: Do you use Ubuntu or Kubuntu?
[05:26] <eolo999> Ubuntu
[05:26] <eolo999> u?
[05:26] <ScottK> OK.  I'll leave the Python/KDE bugs out of the stuff I push your way.
[05:26] <ScottK> Kubuntu
[05:27] <ScottK> I also have servers running Ubuntu.
[05:27] <jdong> aha, that's what /reconnect does......
[05:27] <ScottK> Gotta run for a bit (kitchen duty calls).
[05:27] <eolo999> dont't be hurt, i find kde still too messy
[05:27] <ScottK> If you like Gome, you should use Ubuntu.  I can't stand it myself.  To each his own.
[05:27] <jdong> I've used both heavily before....
[05:27] <jdong> currently I am using GNOME but with a bunch of KDE apps
[05:28] <eolo999> same for me jdong
[05:28] <jdong> I can't live without K3b, have gotten involved in development/packaging of KTorrent...
[05:28] <jdong> I love some of the stuff on KDE
[05:28] <jdong> a lot of the stuff on KDE
[05:28] <jdong> but I still do not find it intuitive for me as a DE
[05:28] <jdong> of course that's just my personal tastes :)
[05:29] <eolo999> ok, this a real 'CIAO'
[05:29] <eolo999> bye
[05:39] <RAOF> Hm.  Can I reject bug #94302 (and it's various Feisty duplicates)?  As I understand pacakging, the Conflicts line of the banshee pacakge *should* be preventing these bugs from cropping up, but there seem to be enough bugs filed about it to make me doubt my understanding.
[05:39] <ubotu> Launchpad bug 94302 in banshee "Banshee 0.12.x crashes when old banshee-official-plugins are installed" [Medium,Needs info]  https://launchpad.net/bugs/94302
[05:42] <crimsun> well, we definitely don't ship banshee-offical-plugins in feisty.
[05:43] <ScottK> OTOH, the bug reporter says he had it from Edgy before he upgraded.
[05:43] <RAOF> Edgy has one though, so people upgrading can still be hit.
[05:43] <crimsun> I'll attempt the upgrade path in two hours after a fresh reinstall of 6.10
[05:45] <crimsun> ah hell, this kernel won't finish.  I'll just reinstall 6.10 now.
[05:55] <persia> Should I be suprised if something build locally (with updated linux-libc-dev), and I see "'ECONNRESET' was not declared in this scope" in a buildd failure log?
[05:55] <ajmitch> persia: no
[05:56] <persia> ajmitch: Thanks.  May I presume resubmissions are as normal, but pending the resolution of the kernel issues?
[05:57] <ajmitch> sure
[05:57] <ajmitch> they'll just fail & get queued
[05:58] <persia> Will they be automatically requeued?  I thought requeuing required manual intervention.
[05:58] <ajmitch> depends
[05:58] <ajmitch> there'll most likely be a mass give-back
[05:59] <persia> Ah, that makes sense.  Thanks.
[06:00] <jdong> "dpkg-gencontrol: warning: unknown substitution variable ${source:Version}"
[06:00] <jdong> silliness...
[06:29] <Lichte> Hello
[06:29] <ScottK> Hello
[06:30] <Lichte> are there any people here who package gnome-java ?
[06:30] <ScottK> It's pretty quiet here right now.
[06:30] <Lichte> OK
[06:31] <Lichte> I'll have to check during the day
[06:31] <ScottK> I'd suggest wait and see.  Certainly not me though.
[06:31] <ScottK> During the day where?
[06:31] <Lichte> ScottK: :)
[06:31] <Lichte> USA
[06:31] <gpocentek> good morning #ubuntu-motu!
[06:31] <ScottK> Goog morning gpocentek.
[06:33] <ScottK> err.. Good morning.
[06:33] <ajmitch> hi gpocentek
[06:33] <Lichte> good evening gpocentek
[06:33] <ScottK> Lichte: There are people here from all over the world, so it's not always easy to tell when the best time to show up is.
[06:34] <ScottK> gpocentek: Do you have time for UUS review of a couple of bugs?
[06:34] <ajmitch> Hobbsee!
[06:35] <ScottK> Good evening Hobbsee.
[06:35] <gpocentek> ScottK: yep
[06:35] <ScottK> Bug #111155
[06:35] <ubotu> Launchpad bug 111155 in pyyaml "sync request pyyaml 3.04-1 from Debian Unstable (main)" [Undecided,Unconfirmed]  https://launchpad.net/bugs/111155
[06:35] <gpocentek> hello ajmitch
[06:36] <ScottK> gpocentek: and then Bug #39975 is the other.
[06:36] <ubotu> Launchpad bug 39975 in pysol "Automatic play -> Auto drop setting forgotten" [Medium,Confirmed]  https://launchpad.net/bugs/39975
[06:37] <ScottK> I may have one more if I can figure out why scapy isn't building even without my patch....
[06:37] <Hobbsee> hi ajmitch, ScottK
[06:38] <gpocentek> :)
[06:39] <ScottK> I will note for the record that you are the first to ask that question.
[06:40] <ajmitch> ScottK: don't worry, he's one of the ones who'll grill you when you apply
[06:40] <ScottK> I'd expect nothing less.
[06:40] <Hobbsee> hah
[06:40] <ajmitch> & dholbach can hug you to death
[06:41] <gpocentek> hehe
[06:43] <Hobbsee> !timebasedreleases
[06:43] <ubotu> Ubuntu releases a new version every 6 months. Each version is supported for 18 months to 5 years. More info at http://www.ubuntu.com/ubuntu/releases & http://wiki.ubuntu.com/TimeBasedReleases
[06:45] <crimsun> ponies!
[06:45] <Hobbsee> ajmitch: hah.  did you use that link, too?
[06:46] <gpocentek> ScottK: 111155 is OK, I subscribed the archive team
[06:46] <ScottK> gpocentek: Thanks.
[06:47] <jdong> ajmitch: heh I get those daily
[06:47] <jdong> I'm still getting "wah wah firefox wah"
[06:47] <crimsun> TB 2.0, too?
[06:48] <ajmitch> jdong: except I'm not a backports crack addict
[06:48] <crimsun> my fav are TB 2.0 and Azureus 2.5.0.x
[06:49] <jdong> ajmitch: I'm trying a new 5-step program for that.
[06:59] <TheMuso> Heya all.,
[06:59] <ScottK> Heya TheMuso.
[07:00] <RAOF> Afternoon, TheMuso
[07:01] <gpocentek> hello TheMuso
[07:02] <crimsun> gracious, a cd-based dist-upgrade takes ages on a Pentium II/266
[07:02] <TheMuso> Why does that not surprise me?
[07:03] <crimsun> require more pony powah
[07:03] <jdong> haha I found a 500MHz unbearable
[07:03] <jdong> it had a crappy little HDD in it
[07:03] <jdong> that took forEVER to Reading Package Database....
[07:04] <ScottK> gpocentek: Thanks for looking at the bugs.  I need to get to bed, so if you find anything wrong with Bug #39975, please just comment in the bug or let me know here (I'll read the scrollback).
[07:04] <ubotu> Launchpad bug 39975 in pysol "Automatic play -> Auto drop setting forgotten" [Medium,Fix committed]  https://launchpad.net/bugs/39975
[07:04] <ScottK> Good night all.
[07:04] <gpocentek> ScottK: I've just uploaded it. Good night!
[07:04] <ScottK> Great.  Thanks.
[07:06] <crimsun> RAOF: confirmed.  A dist-upgrade does not remove -official-plugins.
[07:07] <crimsun> RAOF: (using aptitude.  Did not test apt-get or synaptic.)
[07:07] <RAOF> crimsun: Mad.  What's aptitude thinking?
[07:09] <RAOF> What version of banshee-official-plugins is in Edgy and is not removed by dist-upgrade?
[07:09] <ajmitch> conflicts/replaces with << can be interesting at times
[07:11] <RAOF> Right.  So, how do we fix it?
[07:12] <crimsun> RAOF: -official-plugins 0.11.1-0ubuntu2
[07:13] <RAOF> Hm.  Which dpkg --compare-versions thinks is lt 0.11.4
[07:16] <crimsun> I can retry with apt-get in the morning
[07:17] <crimsun> according to Conflicts semantics, though, it /should/ work.
[07:17] <RAOF> Indeed, that's what's puzzling me.
[07:17] <crimsun> unless I've utterly misparsed the semantics.
[07:18] <crimsun> hmm, Breaks doesn't seem appropriate in this scenario, either.
[07:19] <crimsun> (from https://lists.ubuntu.com/archives/ubuntu-devel-announce/2006-July/000168.html )
[07:22] <RAOF> Hm.  Debian policy seems to suggest against a versioned conflicts, but the Ubuntu packages I've looked at have almost always have a versioned Conflicts.
[08:03] <TheMuso> Gotta love it when you have to contact authors of source code to ask that they add copyright/GPL source header, etc.
[08:03] <crimsun> cine*?
[08:04] <TheMuso> crimsun: No. A utility that is shipped with espeak.
[08:04] <crimsun> fun times.
[08:04] <TheMuso> Upstream added the utility, but there is no license stated for the code.
[08:04] <TheMuso> Indeed.
[08:05] <TheMuso> The utility will only be used in package building, but nevertheless, the source will be available.
[08:26] <siretart> morning
[08:26] <Fujitsu> Hi siretart.
[08:26] <siretart> anyone using ndiswrapper around?
[08:26] <siretart> hi Fujitsu
[08:26] <siretart> crimsun: around?
[08:26] <crimsun> siretart: hi
[08:27] <siretart> crimsun: I've asked you before, do you actually use the mailing list<EMAIL_ADDRESS>I see only spam there
[08:27] <crimsun> siretart: is the spam originating from my address?
[08:27] <crimsun> siretart: I read the list, if that's what you're asking
[08:27] <siretart> crimsun: no, I propose to remove that mailing list completely
[08:28] <crimsun> siretart: oh, ok.  What will replace it?
[08:28] <siretart> crimsun: what kind of traffic do we have there? bugmail has been disabled for some time now
[08:28] <Fujitsu> Why doesn't bugmail go there?
[08:28] <ajmitch> hi siretart
[08:28] <siretart> because I removed the contact address of the motumedia team
[08:28] <siretart> hi ajmitch
[08:28] <crimsun> siretart: I've seen perhaps one or two relevant emails.
[08:28] <Fujitsu> siretart: Well, yes, but why?
[08:29] <siretart> Fujitsu: I was getting nearly all motumedia bugmails twice
[08:29] <siretart> we can of course readd the adress, no problem. nobody objected when I proposed to remove it that time however
[08:29] <ubotu> Launchpad bug 85474 in maxima "Maxima frontends cannot connect" [Undecided,Needs info]  https://launchpad.net/bugs/85474
[08:30] <crimsun> siretart: sure, +1 on the complete removal.
[08:31] <gpocentek> siretart: hi, I use ndiswrapper
[08:33] <siretart> gpocentek: does ndiswrapper use 'wlan0' or 'eth0'?
[08:33] <gpocentek> wlan0
[08:33] <siretart> ok. thanks
[08:33] <gpocentek> np
[08:37] <dholbach> good morning
[08:37] <Fujitsu> Hi dholbach.
[08:37] <gpocentek> morning dholbach
[08:38] <TheMuso> Morning dholbach.
[08:39] <dholbach> hey Fujitsu, hey gpocentek, hey TheMuso
[08:40] <siretart> gpocentek: do you happen to use WPA with your ndiswrapper wifi device?
[08:40] <siretart> hi dholbach
[08:40] <dholbach> hey siretart
[08:42] <gpocentek> siretart: I don't
[08:51] <crimsun> siretart: I do.
[08:51] <crimsun> Do you need something tested?
[08:51] <crimsun> (I'm still at the office, but I can test when I arrive home.)
[08:51] <siretart> crimsun: it's about bug #108013
[08:51] <ubotu> Launchpad bug 108013 in wpasupplicant "wpa_supplicant doesn't work with ndiswrapper anymore (dup-of: 102385)" [Undecided,Needs info]  https://launchpad.net/bugs/108013
[08:51] <ubotu> Launchpad bug 102385 in wpasupplicant "netgear wg311v2 (acx chipset) using ndiswrapper 1.9 and wpa supllicant fails to associate with access point." [Undecided,Needs info]  https://launchpad.net/bugs/102385
[08:52] <siretart> I can't really believe it, and I think I've found something relevant on the upstream mailing list
[08:52] <crimsun> wpa_supplicant in 7.04 definitely works with ndiswrapper.
[08:52] <siretart> ok
[08:52] <crimsun> I've got an unfortunate bcm4311
[08:53] <siretart> ok, then the upstream post ist most probably correct
[09:10] <ajmitch> hi dholbach
[09:10] <dholbach> hey ajmitch
[09:24] <crimsun> RAOF: hmph, reproduced with apt-get, too.
[09:25] <RAOF> crimsun: Stupid dpkg.
[09:25] <crimsun> I wonder if the Breaks code affected it.
[09:26] <RAOF> Hm.  Maybe?
[09:26] <crimsun> will have to look later; it's 3:26 AM
[09:26] <RAOF> Good morning! :)
[09:27] <crimsun> :)
[09:31] <jussi01> can someone help me?, ive just created the man page for my program, but when i install the deb, it doesnt seem to have a man page, how do I make it install?
[09:32] <RAOF> jussi01: As I understand it you generally want some dh_installman magic to install your man pages (ie: it's not totally automatic)
[09:34] <jussi01> RAOF: yeah, ive got that uncommented, but it stilldoeesnt work... Im a little lost now...
[09:34] <RAOF> jussi01: You're not using CDBS, I suppose?
[09:34] <jussi01> RAOF: nah, debhelper
[09:35] <RAOF> Thought so.
[09:36] <RAOF> jussi01: Do you have a package.manpages?  Or do you explicitly pass the manpage filename to dh_installman?
[09:37] <jussi01> RAOF: no, i have package.1 (waon.1) i changed that like the instructions said from manpages.1
[09:38] <RAOF> jussi01: "man dh_installman" suggests that you need to either pass the manpage to install or have a package.manpages file in the debian/ directory
[09:38] <jussi01> ahhh, ok
[09:38] <persia> jussi01: You need to list all the manpages in package.manpages (see man dh_installman).
[09:39] <jussi01> with "package" meaning the name of my program?
[09:39] <RAOF> Indeed.
[09:39] <jussi01> :D Understood!!!
[09:39] <RAOF> Or, rather, the name of the binary package it should go in.
[09:39] <jussi01> okies, ill let you know how it goes. :D
[09:39] <persia> jussi01: If your source pacakage doesn't have multiple binaries, you can probably just use "manpages2.  If you have multiple binaries, whatevery the binary package name is.
[09:40] <jussi01> ok, thanks persia
[09:41] <jussi01> and thanks RAOF also :D
[09:45] <jussi01> do i really need a man page for the "g" version of the program - its self explainitory.
[09:46] <RAOF> Probably.  But you should be able to do what grep does (egrep, pgrep, etc all go to the same manpage)
[09:46] <persia> jussi01: It's annoying for users to not be able to type "man whatever" for any command.  If they are substantially the same, you could make a manpage for both, and link them.
[09:46] <jussi01> persia: ok.
[09:48] <persia> Is gutsy JACK likely to work?  I'm porting freqtweak to wx2.6 (with help from upstream prerelease 0.7.0), and Jack keeps crashing.  I'm not sure if I've broken something, or if it was broken beforehand.
[10:14] <jussi01> dholbach: ping?
[10:15] <jussi01> gpocentek: you around?
[10:15] <dholbach> jussi01: pong
[10:16] <gpocentek> jussi01: yep
[10:16] <jussi01> dholbach: Im sending you an email with the link for my upload to revu - could you have a look at it when you have time?
[10:16] <jussi01> gpocentek: you also?
[10:16] <jussi01> :D
[10:17] <jussi01> gpocentek: http://revu.tauware.de/details.py?upid=4963
[10:17] <jussi01> :D
[10:17] <dholbach> jussi01: yes, I'll do that once I got some other work done
[10:18] <jussi01> dholbach: thanks a lot!!
[10:20] <\sh> moins
[10:20] <jussi01> \sh: morning!
[10:20] <davisc> Can I ask here about status of bugs in the universe repo?
[10:25] <gpocentek> jussi01: I don't get why you don't build the pv binary
[10:27] <jussi01> I removed it because it is a seperate program, and should be its own package, but I can put it back in?
[10:27] <gpocentek> or you can build 2 binary packages from the same source
[10:27] <gpocentek> what does pv do?
[10:29] <jussi01> its a phase vocoder
[10:29] <jussi01> it is quite related
[10:29] <jussi01> hmmm, now im having second thoughts
[10:30] <jussi01> gpocentek: scratch that, Ill pop pv back in.
[10:31] <gpocentek> ok
[10:31] <gpocentek> the pixbuf thing is also very weird
[10:33] <jussi01> gpocentek: yeah, I still dont understand it.
[10:34] <jussi01> gpocentek: out of curiosity what is the gnome2 version of that package?
[10:35] <gpocentek> jussi01: looks like it's part of gtk+
[10:36] <jussi01> gpocentek: Ill have another look into it...
[10:37] <gpocentek> jussi01: it seems that you can patch the gwaon makefile to remove the gdk_pixbuf bits
[10:37] <gpocentek> it builds fine here without this
[10:37] <jussi01> gpocentek: could you send the patched makefile over?
[10:37] <jussi01> and the program runs fine?
[10:37] <gpocentek> testing...
[10:38] <gpocentek> yep, it works
[10:40] <gpocentek> jussi01: http://paste.ubuntu-nl.org/18346/
[10:40] <jekil> hello
[10:40] <jussi01> gpocentek: thanks a lot!!
[10:40] <gpocentek> np :)
[10:40] <gpocentek> hi jekil
[10:41] <persia> Is there something additionally wrong with the powerpc buildd environment?  I've gotten a couple assembler errors from the buildds, for packages that compile for i386 and amd64.
[11:02] <jussi01> gpocentek: now it should be better :D
[11:04] <dharrigan> Hi Everyone. I've setup a chroot in /var/chroot following this advice "https://wiki.ubuntu.com/DebootstrapChroot"
[11:04] <dharrigan> However, it lost me a bit near the end.
[11:04] <dharrigan> Shall I just perserve becoming root then sudo'ing to chroot to do building + installing (is this easiest)
[11:04] <dharrigan> ?
[11:05] <gpocentek> jussi01: it's usually a good idea to document the changes you apply to the sources in debian/changelog
[11:05] <\sh> siretart, ping ldt.c:80: error: '__NR_modify_ldt' undeclared (first use in this function) is because of broken linux-libc headers?
[11:05] <jussi01> gpocentek: ah, forgot about the
[11:05] <jussi01> that
[11:05] <gpocentek> jussi01: and it's even better if you use a patch system (though I don't think it's not worth the pain here)
[11:06] <gpocentek> s/not//
[11:06] <jussi01> :)
[11:08] <jussi01> gpocentek: so s ingle line entry to change log is all good?
[11:10] <zakame> anyone got around to making a sid pbuilder on feisty host?  it borks due to sid missing libdevmapper1.02 (it has 1.02.1)
[11:12] <gpocentek> jussi01: I'm fine with that, let's see what will say Daniel ;)
[11:12] <jussi01> gpocentek: excellent :D
[11:12] <jussi01> gpocentek: I just uploaded the one with the fixed changelog
[11:13] <gpocentek> ok
[11:14] <gpocentek> jussi01: did you drop the libgdk-pixbuf2 build dep?
[11:14] <jussi01> gpocentek: thanks for all your help so far! I wouldnt have been able to do it without you.
[11:14] <jussi01> gpocentek: yeah
[11:14] <jussi01> oh, no...
[11:14] <davisc> Can I ask here about status of bugs in the universe repo?
[11:14] <gpocentek> jussi01: we're here to help :)
[11:14] <DktrKranz> any sponsor here?
[11:15] <jussi01> gpocentek: anything else to add before i upload 1 more time?
[11:16] <jussi01> :D
[11:16] <gpocentek> let me have a closer look
[11:19] <gpocentek> jussi01: "Description:A Wave-to-Notes transcriber" << missing space
[11:19] <gpocentek> before "A"
[11:19] <jussi01> gpocentek: in control?
[11:19] <jussi01> yeps, fixed
[11:20] <gpocentek> jussi01: the "All rights reserved" in README might be a problem
[11:22] <jussi01> hmm, Ill email the guy and make sure its ok to take that out, but im pretty sure its just some random thing he put there...
[11:22] <gpocentek> I guess so, but I'm sure that our archive admins won't like it ;)
[11:23] <gpocentek> jussi01: I have to go, I'll review your next upload later
[11:23] <gpocentek> see you
[11:23] <jussi01> gpocentek: thanks again
[11:24] <cbx33> hey guys
[11:25] <siretart> \sh: looks like. try building in a feisty chroot
[11:29] <\sh> siretart, will do it just now :) I wasn't sure, because the symbol is there in asm-<arch>/...
[11:30] <siretart> \sh: this really smells like the general gutsy breakage
[11:31] <\sh> siretart, yepp
[11:33] <shawarma> siretart: "the general gutsy breakage"?
[11:34] <Nafallo> shawarma: ubuntu-devel@ has info from cjwatson :-)
[11:36] <siretart>   jepp
[11:38] <shawarma> Nafallo: ah, I see.
[11:39] <shawarma> So stuff that manages to compile is just fine, right? The binary packages in the archive should be in working order?
[11:41] <Fujitsu> If it works, it should be fine.
[11:41] <Fujitsu> s/works/has built/
[11:45] <shawarma> Alright.
[11:46] <shawarma> Otherwise, I'd probably be trying to downgrade my laptop to Feisty again right about now. :-)
[12:53] <Fujitsu> Yay, somebody asking why we don't just upload a Subversion checkout of mplayer to feisty-updates.
[12:54] <harrisony> feisty-svn ?
[12:54] <Q-FUNK> :D
[12:54] <Nafallo> Fujitsu: lart them from me ;-)
[12:55] <Q-FUNK> that's starting to sound dangerously close to OpenLSD
[12:55] <Q-FUNK>
[12:55] <Q-FUNK> OpenBSD
[12:55] <ogra> heh
[12:55] <Q-FUNK> update?  yes, fetch from CVS and make world.
[12:55] <ogra> see the dragonfly !
[12:55] <ogra> sooo colorful :)
[01:14] <dharrigan> Hi people. I have a chroot environment, that I switch into by "dchroot -c mychroot -d". When I want to sudo, I am asked to type in the root password, but it keeps telling me my passwd is wrong
[01:14] <dharrigan> from my normal (non-chroot) account, when I type in sudo and then the password, it works fine
[01:14] <dharrigan> I'm building a package, and I want to dpkg -i it, but I get this problem.
[01:15] <dharrigan> Anyone know how to fix?
[01:17] <Amaranth> your chroot has it's own set of passwords
[01:18] <ryanakca> can someone please review http://revu.tauware.de/details.py?upid=4961
[01:19] <ryanakca> It's a chroot utility. builds fine in pbuilder-gutsy, and nothing from lintian/linda (other than a couple I: about minus being used instead of hyphen in the man pages)
[01:27] <harrisony> bug 111217 is quite interesting
[01:27] <ubotu> Launchpad bug 111217 in matplotlib "not publication quality???" [Undecided,Unconfirmed]  https://launchpad.net/bugs/111217
[01:28] <StevenK> Is that another way of saying "this is a buggy pile of crap" ?
[01:28] <StevenK> Heh, no it isn't.
[01:35] <harrisony> nah its more along the lines of WTF is this doing here,
[01:40] <persia> harrisony: Looking at the upstream "What's new", it appears upstream claimed to be able to generate "publication quality" starting with 0.29.  Debian maybe?
[01:41] <Amaranth> !info matplotlib
[01:41] <ubotu> Package matplotlib does not exist in feisty, feisty-seveas
[01:41] <Amaranth> grr
[01:43] <StevenK> It looks like matplotlib has been NMU'd 3 times.
[01:43] <StevenK> I wouldn't NMU it just to change the description.
[01:46] <eolo999> gpocentek, thanks for uploading pysol...
[01:49] <gpocentek> eolo999: thanks for the patch ;)
[01:55] <ScottK> gpocentek: That was eolo999's first.
[01:57] <gpocentek> cool :)
[02:01] <Q-FUNK> LOL
[02:03] <PhinnFort> uh oh, we got an endless loop: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/91399
[02:03] <ubotu> Launchpad bug 91399 in console-setup "fail to install with subprocess post-installation script returned error exit status 3" [Medium,Needs info]
[02:03] <PhinnFort> (in the comments)
[02:04] <PhinnFort> he gets an update in the mail, the mailclient answers automatically, an update is sent, it answers, etc.
[02:04] <PhinnFort> (at least in the mailing archive)
[02:05] <ScottK> It looks fine on the bug AFAICT.
[02:06] <PhinnFort> doesn't seem like his mails stick in the comments
[02:06] <PhinnFort> but it's trickling into my mailbox;)
[02:06] <PhinnFort> "I am out of the Office until Sunday evening. I will check my mail during the week, but will only awnser a few E-mails."
[02:07] <ScottK> eolo999: Your job after the upload is to monitor the building of the new package.  Make sure it builds successfully and when it's fully built, mark the bug fix released.
[02:07] <ScottK> eolo999: https://launchpad.net/ubuntu/+source/pysol/4.82.1-4.1ubuntu6
[02:08] <eolo999> ScottK, ok__good morning
[02:08] <ScottK> PhinnFort: Look in the headers and see where the messages are coming from.  If you don't know how, pastebin the header and I'll tell you.
[02:08] <PhinnFort> ScottK: they're coming from "Florian Jensen<EMAIL_ADDRESS>[02:09] <eolo999> successfully built on gutsy
[02:09] <PhinnFort> Kmail is quite nice
[02:09] <ScottK> PhinnFort: Not the person in the from, but the server in the header.
[02:09] <ScottK> eolo999: Then mark it fix released.
[02:09] <PhinnFort> <IP_ADDRESS>
[02:09] <ScottK> PhinnFort: Would you pastebin the entire header please.
[02:10] <eolo999> ScottK, but not feisty
[02:10] <PhinnFort> http://rafb.net/p/P5XcLi94.html
[02:10] <ScottK> eolo999: No.  Feisty is already released, so it only goes back to Feisty if it meets specific "Really Important" criteria.
[02:11] <ScottK> eolo999: See the When section here https://wiki.ubuntu.com/MOTU/SRU
[02:12] <ScottK> PhinnFort: You're getting them from LP, so I'd go to #launchpad and discuss it there.
[02:23] <DarkSun88> Hi all
[02:23] <eolo999> ScottK, now its 'fix released'
[02:24] <ScottK> Great.
[02:25] <eolo999> ScottK, tried to give a look to Bug #110219, but mailing list reference is wrong
[02:25] <ScottK> eolo999: Because we had to add dpatch, feeding the patch to Debian is more complex than just sending them the patch.  I'm adjusting what we did to make it useful for them and will take care of sending to the Debian Bug Tracking Systmem.
[02:25] <ubotu> Launchpad bug 110219 in python-gnuplot "python-gnuplot package not working in feisty fawn" [Undecided,Unconfirmed]  https://launchpad.net/bugs/110219
[02:25] <eolo999> ScottK, good.
[02:26] <ScottK> eolo999: He responded to your post on the bug.  Looks like you may have to do some detective work.
[02:40] <DktrKranz> \sh, around?
[02:40] <\sh> DktrKranz, yepp
[02:41] <DktrKranz> I would like to thank you
[02:41] <DktrKranz> I noticed you just uploaded some packages :)
[02:42] <\sh> DktrKranz, yepp, just uploaded...3 minutes ago :;)
[02:43] <DktrKranz> I hope they won't suffer from build problems
[02:56] <yondie> does apt have any weird cool plugins?
[02:57] <shawarma> yondie: Not really.
[02:57] <shawarma> yondie: What do you want to do?
[02:58] <shawarma> yondie: There are lots and lots of tools that do things relating to the package database, but no plugins to apt-get as such.
[02:59] <DarkSun88> \sh: Thank you for upload. :)
[03:00] <yondie> shawarma: i want some plugins so that i can include https as a method
[03:17] <abogani> Someone can sponsor me for Cycletest (http://tglx.de/projects/misc/cyclictest/) package?  Useful package for Gutsy realtime kernel flavour.
[03:17] <ScottK> eolo999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418546 :-)
[03:17] <ubotu> Debian bug 418546 in pysol "Automatic play -> Auto drop setting forgotten" [Unknown,Open]
[03:18] <crimsun> err, sponsoring?  Is the source package on revu?
[03:21] <shawarma> yondie: apt-transport-https is your friend.
[03:21] <shawarma> Oh, he buggered off.
[03:22] <abogani> crimsun: No... Can i found more info about REVU on the wiki?
[03:22] <ScottK> !revu
[03:22] <ubotu> REVU is a web-based tool to give people who have worked on Ubuntu packages a chance to "put their packages out there" for other people to look at and comment on in a structured manner. See https://wiki.ubuntu.com/MOTU/Packages/REVU
[03:23] <abogani> ScottK: Thanks.
[03:27] <TheMuso> Yay for debug code in debian/rules. :)
[03:32] <TheMuso> /c/c
[03:32] <StevenK> TheMuso: Sea what?
[03:33] <TheMuso> heh
[03:33] <TheMuso> I'll have a good reason to move to GNOME/Orca this release.
[03:33] <TheMuso> and gnome-terminal
[03:33] <StevenK> Oh?
[03:33] <TheMuso> We're dropping speakup as from gutsy.
[03:34] <StevenK> Why?
[03:34] <StevenK> Great, now I have to get Sean's DECTalk working.
[03:34] <TheMuso> Code is a PITA to maintain, due to bad coding, breaks so easily, and the community haven't stepped up to try and help us support it and make it a better piece of code.
[03:35] <TheMuso> StevenK: If you mean a dec express, I have a replacement speakup_dtexp.c file that makes it work if you'd like it.
[03:35] <StevenK> I thought upstream had a plan?
[03:35] <TheMuso> StevenK: So did we.
[03:35] <TheMuso> StevenK: But its taken way to long to get it sorted, and the code is a mess as it is.
[03:35] <StevenK> TheMuso: I mean a Digital DECTalk box. Actual hardware.
[03:35] <TheMuso> The kernel eam want to have as little difference to their kernel from mainline as possible.
[03:35] <TheMuso> Ah.
[03:36] <StevenK> speakup + speech-dispatcher seems a little fragile, anyway.
[03:37] <StevenK> It gets in this funny state where it detaches from it's SHM and then spins. If you kill it, it doesn't clean up the SHM, so you need to do so manually. All without speech.
[03:37] <TheMuso> Yeah.
[03:37] <TheMuso> I think its more speechd-up than anything else
[03:37] <StevenK> Which is no problem for me, but is for Sean.
[03:37] <TheMuso> I know.
[03:38] <TheMuso> I'll be making speakup kernels available for gutsy once its released if people want them.
[03:38] <StevenK> Yeah, I keep forgetting you're well aware of that. Sorry.
[03:38] <TheMuso> thats ok
[03:38] <StevenK> TheMuso: How about free hardware synths for any visual impaired Ubuntu users? :-P
[03:39] <TheMuso> StevenK: If they can be found.
[03:39] <StevenK> That's a point.
[03:39] <TheMuso> The older serial only ones are hard to come by, unless you buy a doubletalk brand new
[03:39] <TheMuso> And I'm not giving any of mine up for anything!
[03:39] <StevenK> Sean said DECTalk's are as rare as hens teeth.
[03:39] <TheMuso> Damn straight.
[03:39] <TheMuso> I have two of them luckily.
[03:39] <TheMuso> Picked em up second hand for cheap as chips
[03:40] <StevenK> Neat.
[03:40] <TheMuso> If I have a choice, I'd rather use hardware synths any day.
[03:40] <TheMuso> Less crap tying up the CPU.
[03:40] <StevenK> Why not use them, then?
[03:40] <TheMuso> I do.
[03:40] <TheMuso> But only on the console.
[03:40] <TheMuso> I need to learn more python and write serial synth support for Orca.
[03:41] <StevenK> Orca, gnome-speech or both?
[03:41] <StevenK> I'm still not sure of the software stack for speech under X.
[03:41] <TheMuso> Orca can either use gnome-speech, emacspeak, or speech-dispatcher.
[03:42] <TheMuso> I'd actually write another speech module for orca to work with hardware synths, and tie in another GUI window to configure them.
[03:42] <StevenK> So if your Evil Plan is sucessful, it wouldn't use any of them.
[03:42] <TheMuso> Nope.
[03:42] <cbx33> oooh
[03:42] <cbx33> TheMuso, sounds .... evil !
[03:43] <TheMuso> For hardware synths at least.
[03:43] <cbx33> how ya doin
[03:43] <elkbuntu> cbx33, that's because TheMuso *is* evil
[03:43] <TheMuso> cbx33: I'm talking about speech synthesis here.
[03:43] <cbx33> hehe
[03:43] <StevenK> TheMuso: Need any help learning Python?
[03:43] <Hobbsee> yes, TheMuso is very evil.
[03:43] <TheMuso> StevenK: Not really. Just getting the syntax right, which is not hard to work out from reading the orca code. Then its just a matter of learning the API, and glade.
[03:43] <jsgotangco> he's evil
[03:44] <TheMuso> StevenK: I certainly know who to ask if I do, several people are here presently.
[03:44] <cbx33> hehe
[03:44] <cbx33> just gimme a shout if I can be of help ;)
[03:45] <StevenK> TheMuso: Glade seems to be pretty easy to pick up.
[03:45] <cbx33> it is
[03:45] <cbx33> very
[03:45] <StevenK> TheMuso: If an idiot like me can understand and use it, anyone can.
[03:45] <persia> TheMuso: Do you have a special attachment to sooperlooper?  I'd like to process the merge whilst working on my plan to abolish wxwindows2.4.
[03:46] <StevenK> persia: Abolish all the way out of the archive?
[03:46] <TheMuso> heh
[03:46] <cbx33> hehe
[03:46] <persia> StevenK: If possible.  eCos looks tricky :)
[03:46] <TheMuso> persia: Not particularly, but I can have a look if you'd like,.
[03:47] <persia> the: No worries, you just processed a merge since my last patch, and I wanted to check.  I'll proceed.
[03:47] <TheMuso> But I may be going to bed soon, and I'm still having fun with preparing a new upstream package for main.
[03:47] <siretart> persia: do you actually use eCos from the package?
[03:47] <Hobbsee> TheMuso: then you can bug StevenK into sponsoring it
[03:47] <persia> TheMuso: It will be a couple days.  sooperlooper waits for linux-libc-dev
[03:47] <StevenK> Can he?
[03:47] <StevenK> Well, he can try. :-P
[03:48] <persia> siretart: I don't use it at all.  It just build-depends on libwxgtk2.4-dev
[03:48] <crimsun> err, um, killing wxwindows2.4?
[03:48] <crimsun> that's ... interesting.
[03:48] <TheMuso> heh
[03:48] <crimsun> do you plan to drop audacity 1.2.x?
[03:48] <persia> crimsun: I want to.  It's only 14 packages.  3 have fixes in Debian.  4 have publically available patches.  I can probably do the others before I have to go back to work.
[03:49] <persia> crimsun: Um.  Debian did.  Do you want to keep it here?
[03:49] <crimsun> I have no compelling wish to, but I'm not its primary caregiver
[03:49] <crimsun> I'm not exactly thrilled about its current bug count
[03:50] <crimsun> it just needs to be evaluated carefully, since 1.3 is purportedly less stable
[03:50] <persia> I've not been giving it much attention for the past year or so :(  Sorry.
[03:51] <StevenK> TheMuso: We're that entertaining?
[03:51] <crimsun> I'm definitely not going to be pushing for random new versions given gutsy's purported intent of stabilisation
[03:52] <persia> I'm inclined to trust Free when it comes to audio apps, but I'll check about stability prior to pushing very hard.
[03:54] <TheMuso> StevenK: All the evil comments.
[03:54] <crimsun> fbond: any movement on the -firmware front?
[03:56] <ScottK> I have an update ready that fixes both an FTBFS and a crasher in scapy that's ready for UUS review if anyone is availalble.  The fix is attached to bug #111221.
[03:56] <ubotu> Launchpad bug 111221 in scapy "scapy FTBFS in Gutsy due to hard coded Python 2.4 paths" [Medium,Confirmed]  https://launchpad.net/bugs/111221
[03:56] <TheMuso> ScottK: I presume it doesn't need to wait on linux-libc-dev?
[03:56] <ScottK> TheMuso: It's a pure python package, so I would think not.
[03:57] <TheMuso> ah
[03:59] <StevenK> linux-libc-dev is almost sorted out.
[04:01] <ScottK> doko: If a Debian package is packaged with hard coded paths for Python 2.4, is that fair game to file a bug in BTS (wondering since they don't have 2.5 support yet)?
[04:01] <doko> ScottK: sure, and don't forget to attach a patch
[04:02] <ScottK> doko: No problem.  It's a one liner.
[04:02] <ScottK> Thanks.
[04:06] <ScottK> Is FTBFS an Ubuntu unique term or does Debian use it too?
[04:06] <TheMuso> I've seen it in Debian bugs.
[04:06] <StevenK> Debian does too.
[04:06] <ScottK> Thanks
[04:07] <persia> ScottK: Debian did it before Ubuntu existed.
[04:07] <ScottK> persia: Thanks.
[04:07] <TheMuso> Hobbsee: ?
[04:07] <Hobbsee> PBU == Package Blew Up.
[04:08] <TheMuso> ah
[04:09] <siretart> Hobbsee: smells like SNAFU ;)
[04:10] <StevenK> Situation Normal, All Fucked Up
[04:10] <siretart> right
[04:10] <Hobbsee> ahhh
[04:10] <TheMuso> haha good one
[04:12] <TheMuso> yay! Package builds at last!
[04:12] <ScottK> Hobbsee: You can also use Fouled for $F if needed for the audience.
[04:13] <Hobbsee> heh
[04:36] <TheMuso> Night folks.
[04:36] <dholbach> night TheMuso
[04:37] <cbx33> hi all
[04:37] <cbx33> I know this isn't exactly the place to ask, but it's the only IRC server i can get to right now
[04:37] <cbx33> anyone know the deskbar applet?
[04:38] <cbx33> if so
[04:38] <cbx33> how do they do that little window that comes up when you clikco nthe arrow?
[04:38] <cbx33> i know it's gtk jiggery pokery
[05:17] <fbond> crimsun: (re: -firmware) everything is quiet, and working correctly (to the best of my knowledge)
[05:31] <sivang> Has anyone seen Mellisa Draper?
[05:37] <codingmaster> Hello Ubuntu MOTU!
[05:37] <codingmaster> I am participating this year in the Summer of Code for Ubuntu.
[05:37] <codingmaster> I am working on the Ubuntu Firewall Configuration.
[05:37] <codingmaster> I hope you can help me by adding suggestions for a good project name, using this wiki:
[05:37] <codingmaster> https://wiki.ubuntu.com/UbuntuFirewallConfiguration/Name
[05:37] <codingmaster> Thanks in advance to all of you!!!
[05:38] <ScottK> codingmaster: But Ubuntu doesn't ship with a "firewall".  Not sure exactly what you mean.
[05:39] <codingmaster> just check the wiki page
[05:39] <codingmaster> I am working on a Ubuntu Firewall
[05:39] <codingmaster> that will be shipped
[05:39] <codingmaster> when it is finished
[05:39] <codingmaster> it is my Summer of Code project
[05:40] <codingmaster> I hope to get some good suggestions for a great project name :D
[06:22] <bddebian> Heya gang
[06:23] <boss-bcp> Could someone take a look at libpam-cups ( http://revu.tauware.de/details.py?upid=4936 ) for me? It's currently been advocated by one MOTU.
[06:33] <ScottK> bddebian: Got time for a bug fix upload?
[06:33] <ranf> hi
[06:34] <ScottK> Hi
[06:35] <geser> ScottK: what do you need uploaded?
[06:35] <ScottK> Bug #111221
[06:35] <ubotu> Launchpad bug 111221 in scapy "scapy FTBFS in Gutsy due to hard coded Python 2.4 paths" [Medium,Confirmed]  https://launchpad.net/bugs/111221
[06:35] <ScottK> geser^^
[06:37] <geser> will uploaded it
[06:38] <ScottK> geser: Thanks.
[06:39] <bddebian> ScottK: Probably in a little bit, sure
[06:39] <bddebian> Oh, nm
[06:40] <geser> Hi bddebian
[06:40] <bddebian> :-) Heya geser
[06:40] <geser> ScottK: what's the rationale to move B-D-I to B-D? doesn't it build without this change?
[06:41] <persia> bddebian: If you really want one, I can give you one :)
[06:41] <ScottK> geser: It does build, but Lintian givew you errors.
[06:42] <geser> ah, ok then
[06:42] <ScottK> geser: I looked and that same change is already in the svn trunk at Debian Python Modules Team for their next release.
[06:43] <bddebian> So won't we sync it?
[06:43] <ScottK> Eventually.  It's not released yet.
[06:43] <ScottK> The point is it's not a diff with Debian we'll have to maintain.
[06:44] <geser> and only if the Debian package fixes the python2.4 build failure
[06:44] <persia> ScottK: If you upload Xubuntu1, the automatic sync stops.  You'll have to watch for the release.
[06:44] <ScottK> geser: Yes.  I committed that change to Debian Python Modules Team svn.  The only long term diff we end up with is the fix for the Ubuntu specific networking problem.
[06:45] <geser> you have access to it?
[06:45] <ScottK> persia: Yes, but of bug #96753, we are going to have to merge anyway.
[06:45] <ubotu> Launchpad bug 96753 in scapy "[feisty]  scapy crashes using any version of python" [Medium,Confirmed]  https://launchpad.net/bugs/96753
[06:45] <ScottK> geser: Yes.
[06:45] <geser> yeah
[06:46] <persia> ScottK: Ah, right.  Nevermind, I'll go back to things I understand.
[06:46] <ScottK> If it weren't for there being an Ubuntu specific change we are going to be stuck with anyway, I would have just pushed the change in Debian and waited.
[06:46] <ScottK> NP
[06:46] <geser> ScottK: either fetch devscripts from gutsy or don't forget to change the distribution in the changelog :)
[06:47] <ScottK> Aww.  Rats.
[06:47] <ScottK> Do you want me to redo it or will you fix it.
[06:47] <ScottK> ?
[06:47] <geser> I've fixed it already
[06:47] <ScottK> geser: Thanks.
[06:48] <geser> I did it with pbuilder login --save-after-login and dist-upgraded
[06:49] <ScottK> geser: Thanks.  I'll give that a shot then.
[06:49] <bddebian> pbuilder update --distribution gutsy --override-config?
[06:49] <bddebian> Of course you need to change all your sources.list and such
[06:50] <persia> Wouldn't that also require an updated debootstrap?
[06:51] <ScottK> Which AFAIK isn't avaialble yet.
[06:51] <geser> ScottK: uploaded
[06:51] <ScottK> geser: Thanks.
[06:51] <bddebian> persia: Nope
[06:52] <persia> ScottK: gutsy debootstrap was published 25th April (in gutsy only).
[06:52] <ScottK> Ahh.
[06:52] <ScottK> That explain why I don't get it....
[06:52] <ranf> I grabbed <IP_ADDRESS>ubuntu3 today from the pool.
[06:52] <jdong> persia: is that debootstrap stable?
[06:52] <persia> jdong: I don't know.  I haven't tried to do anything with debootstrap for about 5 months.
[06:53] <jdong> ok, I'll test it out later then
[06:53] <jdong> if it's good then I'd like to backport it....
[06:56] <DktrKranz> jdong, if I mind well, it fixes a problem with sid
[06:57] <DktrKranz> so, it could be useful having it for feisty
[06:57] <jdong> K, I'll test it later on
[07:53] <sacater> hey, sorry, im still having SIP trouble, can anyonehere test ekiga with me, i have set it up my end
[08:07] <sacater> LaserJock: elli there :D
[08:07] <sacater> oh bye them :D
[08:07] <sacater> then*
[09:18] <Kmos> how is member of app-install-data-commercial team ?
[09:18] <Kmos> to update opera to v9.2
[09:18] <Kmos> bug 105859
[09:18] <ubotu> Launchpad bug 105859 in app-install-data-commercial "Opera 9.2 is out with many bug fixes" [Undecided,Confirmed]  https://launchpad.net/bugs/105859
[09:28] <boss-bcp> Could someone take a look at libpam-cups ( http://revu.tauware.de/details.py?upid=4936 ) for me? It's currently been advocated by one MOTU.
[09:46] <ajmitch> morning
[09:46] <crimsun> moin
[09:46] <ajmitch> boss-bcp: did you change what I asked you to?
[09:49] <ScottK> good morning ajmitch.
[09:49] <bddebian> Heya ajmitch
[10:16] <ScottK> I'm trying to convert a single source package to provide two binary packages instead of all in one.  It's a Python package that uses pysupport.  If anyone knows of I good example I can crib off of, I'd appreciate it if you'd point me in that direction.
[10:16] <imbrandon> moins ajmitch bddebian crimsun
[10:16] <bddebian> Heya imbrandon
[10:17] <jdong> hi imbrandon :)
[10:17] <imbrandon> ello jdong
[10:17] <jdong> does my ktorrent package look good for gutsy upload?
[10:18] <imbrandon> jdong, yea , i'm waiting on a phone call from jono then i'll hop on it
[10:18] <jdong> awesome :)
[10:18] <bddebian> w00t, I think I may have actually fixed rate-engine
[10:19] <jdong> I've now got a disk based spool going
[10:19] <jdong> so that it can actually have a queue of notifications _without_ race conditions
[10:19] <imbrandon> is there a ubuntu-mentors channel active ?
[10:19] <imbrandon> crimsun, ^
[10:20] <imbrandon> libnotify rocks
[10:20] <imbrandon> i've been playing with it a bit and irssi remote sessions lately
[10:21] <jdong> likewise
[10:21] <jdong> I was trying some of the blogged solutions for libnotify remotely queued popups
[10:21] <jdong> but haven't been able to get them to work without duplicating or truncating notification queue....
[10:22] <jdong> so I wrote a set of notify-push/notify-pop/notify-peek scripts that maintain a spool dir on disk
[10:22] <jdong> one file per notification, named by time.time()
[10:22] <jdong> so much work for those pretty bubbles :)
[10:22] <imbrandon> heh
[10:23] <imbrandon> well the nice thing is hopefully i can get them working with growl and/or libnotify via fink on osx also
[10:30] <crimsun> imbrandon: I don't know.  If so, it hasn't come across my vision.
[10:31] <imbrandon> crimsun, ok cool, just wondering
[10:42] <imbrandon> woot, goot a good MOTU plug on LugRadio
[10:43] <ajmitch> oh good
[10:43] <imbrandon> hopefully i dident sound like a a$$ too much :)
[10:43] <ajmitch> it was mentioned that we're a lazy pack of bums who lurk on irc?
[10:43] <imbrandon> heheh
[10:44] <imbrandon> not quite like that
[10:44] <imbrandon> just a 5 minute spot on MOTU packageing for s04 espsidode 18 iirc :)
[10:44] <ajmitch> ah right
[10:45] <ajmitch> imbrandon, international radio superstar
[10:45] <imbrandon> hahah not quite
[10:47] <imbrandon> i need to give jono hell for not recording it in jokosher yet though
[10:47] <imbrandon> :)
[10:49] <imbrandon> hrm
[10:50] <ryanakca> can someone please review http://revu.tauware.de/details.py?upid=4961
[10:50] <ryanakca> It's a chroot utility
[10:51] <ryanakca> builds fine in pbuilder-gutsy, and lintian + linda return no errors (Just a couple I: about a minus sign being used instead of a hypen in the man pages)
[10:52] <ajmitch> fun to see people requesting updates on u-devel-discuss for packages in feisty
[10:53] <imbrandon> ajmitch, like sru's ?
[10:53] <ajmitch> like new upstream versions
[10:53] <imbrandon> or [..]
[10:53] <imbrandon> ohh
[10:53] <ajmitch> new version of alsa, for example
[10:54] <ajmitch> firefox in < 512MB RAM is not happy ;)
[10:55] <imbrandon> heh
[11:22] <pochu> hi all!
[11:22] <DktrKranz> hi pochu
[11:23] <pochu> wxwidgets2.8 failed to build because the bad kernel headers, should I create a .build1, or ask an admin to give it back?
[11:23] <pochu> hi DktrKranz
[11:24] <DktrKranz> if I mind well, such builds should be rescheduled by a buildd admin
[11:24] <DktrKranz> I've got a similar issue too :(
[11:25] <pochu> so do I poke one in -dev, right?
[11:25] <pochu> gonna try :)
[11:25] <DktrKranz> maybe there's some here
[11:57] <Lichte> Hi all
[11:58] <Amaranth> so
[11:58] <DktrKranz> any sponsor for a FTBFS?
[11:59] <pygi> anyone wanna take a look and tell me how much mistakes I did? :)
[11:59] <Amaranth> is anyone getting to sevilla at around 1pm on the 5th?
[11:59] <Lichte> anyone here package gnome-java ?
[12:06] <gnomefreak> anyone know the policy for backporting python?
[12:08] <DktrKranz> gnomefreak, is it a standalone application?
[12:08] <Amaranth> gnomefreak: not going to happen
[12:08] <DktrKranz> or python interpreter?
[12:08] <gnomefreak> Amaranth: i didnt think so
[12:08] <Amaranth> _everything_ uses python :)
[12:09] <gnomefreak> yeah i know that is what i was explaining to him
[12:10] <jdong> gnomefreak: the entire interpretor? no way
[12:10] <jdong> and that's an authoritative no way
[12:10] <jdong> I saw the backport
[12:11] <gnomefreak> thats what ive been trying to tell him :(
[12:12] <jdong> I'll go ahead and handle the backports bug
[12:12] <gnomefreak> i just pasted it to him
[12:12] <jdong> if LP wouldn't be stupidly slow
[12:12] <gnomefreak> jdong: he said he filed one a little while ago so it might be his
[12:12] <jdong> @cox.net?
[12:12] <gnomefreak> hes wondering how to file a bug against feisty-backports
[12:13] <gnomefreak> yes thats him
[12:13] <jdong> against feisty?
[12:13] <jdong> ajmitch: lol


[06:34] <jarnos> Is it common that you can not start a laptop? I tried to follow instructions shown at http://www.mythtv.org/wiki/ACPI_Wakeup with a couple of laptops and they just did not pass the test.
[06:37] <Shadow__X2> how old?
[06:43] <jarnos> Shadow__X2, one is from 2009 (Samsung NC10), another is year 2006 model.
[06:44] <Shadow__X2> so are they having problems resuming from sleep or booting linux?
[06:45] <jarnos> "sudo grep -i rtc /var/log/dmesg" suggest their BIOS support timed wakeup.
[06:46] <jarnos> Shadow__X2, at least booting, I don't know, if you can do automatic timed resumes from S3 state.
[06:46] <Shadow__X2> i have no idea
[06:47] <Shadow__X2> i know for one machine i had to boot with no acpi
[06:49] <jarnos> Oh, there should be an item for it in BIOS setup program, but I could not find it there.
[06:54] <Shadow__X2> i had to tell linux to boot without it
[06:54] <Shadow__X2> not sure if thats the issue you are having though
[06:54] <Shadow__X2> anyway night time for me. good luck
[06:54] <jarnos> Shadow__X2, thanks
[06:54] <Shadow__X2> no problem


[07:45] <ochosi> morning everyone
[09:11] <ochosi> hey sergio-br2
[09:14] <sergio-br2> hey
[09:15] <ochosi> how's it going?
[09:16] <sergio-br2> well, don't touch anything since that day
[09:16] <sergio-br2> one thing i realized using unity
[09:17] <sergio-br2> thumbnails in nautilus is active by default, and mimetype for text files such as .c, .cpp, .txt and .lua, they not appear
[09:18] <sergio-br2> in humanity theme, text-x-preview is a .icon file, not a png or svg
[09:20] <sergio-br2> so, you have a thumbnail showing a small fraction of your text. But using elementary, all them are blank.
[09:21] <ochosi> right
[09:21] <ochosi> i think i'd consider that a bug in nautilus rather than a feature
[09:21] <ochosi> don't think there's much we can do about that
[09:22] <ochosi> thumbnails are also activated by default in thunar, but not all thumbnailers are installed by defaut
[09:22] <ochosi> default
[09:22] <sergio-br2> only for pictures?
[09:22] <ochosi> i think there's a tumbler-extras package or something
[09:22] <ochosi> pics and pdfs mostly
[09:22] <ochosi> and movie files i think
[09:23] <ochosi> but there can always be pics or movies where the thumbnailing service fails for some reason to create a thumbnail
[09:25] <sergio-br2> hum, so in nautilus, if  text-x-preview is a png or svg icon, it should use the default mimetypes of text files, instead a thumbnail?
[09:27] <sergio-br2> it makes more sense
[09:29] <sergio-br2> hum, tumbler-plugin-extra you said ?
[09:35] <ochosi> yeah
[09:36] <ochosi> in thunar you have very fine-grain control over thumbnailing
[09:36] <ochosi> you can enable specific thumbnailers only for some directories etc
[09:41] <sergio-br2> i will see this in trusty, maybe nautilus got improvements in this
[09:41] <sergio-br2> see you later !
[09:51] <bluesabre> morning ochosi
[09:54] <ochosi> hey bluesabre
[09:54] <ochosi> andrew has quite a few branches for the greeter in the pipe btw
[09:54] <ochosi> not only the one/s i referenced in the email today
[09:55] <ochosi> there's one for orca support (which would be great, i think)
[09:55] <bluesabre> saw all that, yeah, let's roll them into trunk
[09:56] <ochosi> as we've both been a bit slow processing his merge-requests i thought it's a good idea to motivate him to occasionally just push to trunk too
[09:56] <ochosi> especially when it's bugfix
[09:58] <bluesabre> yeah
[10:00] <bluesabre> I'll try to merge those in this morning/tonight
[10:00] <bluesabre> working on the debian merge atm
[10:01] <ochosi> for the 1.8.5 release?
[10:02] <bluesabre> yes
[10:05] <ochosi> cool
[10:16] <ochosi> bluesabre: btw, i'm really curious how the whole gtk3-only transition and using only a single window for the greeter will mess with all the positioning code
[10:16] <bluesabre> it will greatly simplify it
[10:16] <ochosi> yeah, and i guess there won't be such a big need for checking whether the window is offscreen
[10:16] <bluesabre> GtkOverlay lets you easily specify where the overlay items will be placed
[10:16] <ochosi> cause it'll be inside a window
[10:16] <bluesabre> yup
[10:17] <ochosi> just checked another item on the todo-list for xfpm today
[10:17] <ochosi> mostly one thing left to do, then we'll do a huge merge/push to the git repo
[10:17] <ochosi> and then a dev release
[10:18] <ochosi> really looking forward to that
[10:29] <ochosi> bluesabre: maybe we could look at the lid-close stuff again together soonis
[10:30] <ochosi> h
[10:30] <ochosi> i think the patch by eric needs to be tweaked/extended a little
[10:30] <bluesabre> ok, I'll probably be free this evening
[10:35] <ochosi> cool, can't promise yet but i'll try
[11:46] <knome> what do people generally think about the timespan for voting on the mailing list?
[11:47] <ochosi> i'm currently considering a 1-week period for votes like the one we're holding about the MÃL
[11:48] <knome> MÃL ?
[11:48] <ochosi> yeah, Mï¿½L
[11:48] <ochosi> that's a common shorthand for mailinglist in german ;D
[11:48] <knome> aha ;)
[11:48] <knome> i thought a with ~ was more connected to spanish ;)
[11:49] <knome> anyway, another idea is...
[11:49] <knome> we could *begin* the voting on the ML, then finish it off in a meeting
[11:49] <knome> currently people voted on the meeting, *then* we got the arguments on the ML
[11:50] <knome> so in a way, the votes on the meeting might not have been as informed as votes after the arguments
[11:50] <slickymasterWork> I agree with knome
[11:50] <slickymasterWork> or else will be dragging the vote
[11:50] <knome> i guess we all agree there has to be some deadline
[11:50] <ochosi> slickymasterWork: well the dragging is only a problem if there is no fixed maximum period
[11:50] <ochosi> yeah
[11:51] <slickymasterWork> but is that maximum period fixed?
[11:51] <knome> i don't see why it wouldn't be
[11:51] <ochosi> knome: in this current vote, we *did* have a discussion on the ML first
[11:51] <knome> ochosi, sure, but some of the arguments weren't posted before the voting :)
[11:52] <slickymasterWork> just asking because I don't remember when it was fixed
[11:52] <knome> which i guess can be pinpointed to be another problem
[11:52] <knome> slickymasterWork, it wasn't... there is no deadline for this vote
[11:52] <slickymasterWork> hence my question
[11:53] <slickymasterWork> but I do agree with your reasoning knome
[11:53] <ochosi> knome: i can also point arguments on the ML after this vote is finished... that can always happen
[11:53] <ochosi> i think that the order in which we executed this vote was fine
[11:54] <ochosi> first put the proposal on the mailinglist
[11:54] <ochosi> then discuss in the meeting, then vote
[11:54] <knome> ochosi, absolutely... what i'm saying is it would benefit the voters (and ultimately, the project) most if arguments were made in advance
[11:54] <ochosi> yeah, there's no arguing with that :)
[11:54] <knome> we could have had more time between the proposal and voting
[11:55] <ochosi> pleia2: ^ did you read that ;D
[11:55] <knome> otoh...
[11:55] <knome> we really should just decide/vote
[11:55] <knome> to not drag along
[11:55] <ochosi> yeah, discussions are fine, but i wanna get things done too
[11:55] <knome> hardly any decisions are irreversible
[11:56] <ochosi> yeah, and the proposal even contained a sort of "natural deadline" to the "lockdown"
[11:57] <knome> and finally, those who do, decide... so if somebody is away for more than a week or two (from the original proposal to voting ending), it's fair to not count their vote
[12:00] <knome> anyway, i'm off to buy some food
[12:00] <knome> bbl
[14:55] <elfy> the other question re this vote on m/l is - what happens if not enough people vote to get quorum?
[14:56] <elfy> I think that a week - given that it was on the agenda for at least as long as the discussion first started
[14:57] <elfy> however, perhaps there is some virtue in - discuss on m/l vote on m/l in the week leading up to the next irc meeting - final vote in the irc meet - then everyone knows exactly when the vote will end
[15:06] <ochosi> hey elfy
[15:07] <ochosi> yeah, i'm not sure though that this (slightly complicated) process, even though it might bear some virtue, is very feasible in practice
[15:07] <ochosi> imo we can keep voting as we did, try to announce votes (that aren't adhoc) previously on the ML
[15:08] <ochosi> and then if we don't have a quorum extend the voting for a week to the ML
[15:10] <elfy> I'm just throwing out thoughts - though I think the only complicated thing is knowing that we might want to vote on something :)
[15:11] <elfy> anyway - I'm pretty easy about it
[15:17] <ochosi> yup, same here :)
[18:59] <brainwash> ochosi: bug 1318307
[18:59] <brainwash> any idea?
[19:00] <brainwash> it can be only cause by xfdesktop, because it's the only Xfce app which has been patched to support accountsservice
[19:00] <brainwash> caused
[19:05] <ali1234> correct
[19:05] <ali1234> xfdesktop now has per-workspace wallpapers
[19:05] <ali1234> accounts service does not
[19:05] <ali1234> so each time you switch workspace, it writes the new wallpaper to accounts service
[19:06] <ali1234> this is just a guess
[19:06] <brainwash> yes, I think this is what's going on
[19:07] <brainwash> we... uhm, ochosi needs to adjust the patch then :)
[19:11] <brainwash> but it should work properly
[19:11] <brainwash> http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/xfdesktop4/trusty/view/head:/debian/patches/xubuntu_set-accountsservice-user-bg.patch
[19:15] <brainwash> Gtk-Message: Failed to load module "overlay-scrollbar"
[19:15] <brainwash> Gtk-Message: Failed to load module "unity-gtk-module"
[19:15] <brainwash> ali1234: any idea? ^
[19:15] <ali1234> about what?
[19:16] <brainwash> why something tries to load these gtk modules and fails?
[19:16] <ali1234> bug 1307657
[19:16] <brainwash> woot
[19:16] <brainwash> still not fixed
[19:16] <ali1234> patch available though
[19:17] <ali1234> poke tedg if it you have a specific problem caused by this... at the moment it is relatively harmless on a default setup
[19:17] <ali1234> (and attente)
[19:18] <brainwash> I thought that people which use xubuntu + unity have this problem
[19:18] <ali1234> yes, but that isn't a default setup
[19:19] <ali1234> and they're not al unity's fault either, eg fork() after gtk_init()
[19:19] <brainwash> but this cannot be a reason to not upload the patched version
[19:19] <ali1234> the patch hasn't even been merged upstream yet
[19:21] <brainwash> once a final release is out everything is going in slowmotion
[19:22] <ali1234> start chasing people then :)
[19:23] <brainwash> I already left the ubuntu channels :P
[19:39] <ali1234> the thunar crash should be fixed soonish... the fix is in saucy-proposed now


[09:57] <andyrock> hey
[09:58] <andyrock> I saw this: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1714489
[09:58] <andyrock> I've already proposed a fix
[09:59] <andyrock> but I'm wondering if this is going to create the same issue
[09:59] <andyrock> https://code.launchpad.net/~azzar1/update-notifier/ngettext-livepatch/+merge/329982