[01:09] <bluefoxicy> I have a question about packaging.
[01:09] <bluefoxicy> Why is the version of Evolution in Ubuntu shipped without support for "Send an e-mail" as an alarm action?
[01:10] <bluefoxicy> it's there, yet grayed.
[04:08] <YokoZar> Is Firefox 3.5 scheduled for alpha 4?
[07:01] <\sh> moins
[09:11] <slytherin> A quick question. Does 'better dependency calculation' work for programs linked against gtk2 libraries?
[09:41] <james_w> which package provides the knotify stuff in KDE?
[09:43] <Riddell> james_w: >dpkg -S /usr/bin/knotify4
[09:43] <Riddell> kdebase-runtime: /usr/bin/knotify4
[09:43] <Riddell> if that's what you're after
[09:43] <james_w> thanks
[10:21] <mdz> TheMuso, where is that PPA you mentioned this morning? I'm happy to install the latest pulseaudio and test
[10:22] <StevenK> mdz: http://launchpad.net/~ubuntu-audio-dev/+archive from TheMuso's mail to -platform
[10:24] <mdz> StevenK, thanks, can't get to my mail atm
[10:44] <directhex> yay for mdz getting his bag back
[10:49] <mdz> apparently I am one of the lucky ones
[10:56] <directhex> mdz, well, a lost bag not being blown up by the bomb squad is an event
[10:57] <TheMuso> mterry: You are the first person who has had a pulseaudio upgrade problem of that nature, which makes me think that its probably something to do with your system.
[10:57] <TheMuso> I have installed these packages fresh several times over the last week or so, and no changes were made to the upgrade scripts, and I had no problems, and it seems others are not either.
[10:57] <mterry> TheMuso, fair enough....  looked like bad syntax of some dpkg call, which would surprise me if it was machine dependent, but if I'm the only one...
[11:01] <TheMuso> mterry: I'll still take a look though.
[11:02] <TheMuso> mterry: Actually, found the problem, thanks for the heads up.
[11:03] <mterry> TheMuso, sweet
[11:09]  * cjwatson finally fixes the stupid bug where console-setup doesn't work on boot
[11:11] <TheMuso> mterry: Give it an hour max, and new pulse packages should be available with the fix.
[11:11] <TheMuso> I've not long uploaded the fix.
[11:11] <mterry> TheMuso, awesome, thanks
[11:47] <mdz> cjwatson, I wonder if we shouldn't seed iw in all of the places where wireless-tools currently is
[11:50] <slytherin> is there any particular reason why gtk+2.0 package in karmic does not contain libgtk2.0-0.symbols file?
[11:53] <seb128> slytherin, we didn't merge on debian since they added it
[11:54] <seb128> slytherin, it's probably useful for gtk but no fun to maintain because you have to build gtk once for nothing, get to break because .symbols is not updated, do the update, etc
[11:54] <slytherin> Anyway, I am not sure how much the symbol file form Debian will be useful as it is old version.
[11:54] <l3dx> off-topic: anyone know a good resource for setting up emacs for C++ dev?
[11:55] <seb128> slytherin, the idea is that you should update that file which each update
[11:55] <slytherin> hmm
[11:55] <slangasek> pitti: hal in karmic has debian/patches/04_nvidia_brightness.patch, but it's not in the series file?
[11:55] <slytherin> I can understand why it is not easy task.
[11:55] <slangasek> pitti: (I would like it to be in the series file)
[11:56] <seb128> slangasek, isn't hal deprecated anyway?
[11:56] <slangasek> seb128: is something else doing backlight handling today?
[11:57] <seb128> isn't gnome-power-manager doing that using devkit-power?
[11:57] <slangasek> I don't know
[11:59] <slangasek> seb128: basically, I'm trying to bring closure to bug #277589, which continues to haunt me because people affected by it are making arbitrary changes to their fdi files in ways that fix it for them, break it for everyone else, and provide no guidance regarding a fix that can be integrated properly :/
[12:01]  * slangasek finds no instances of 'bright' or 'backlight' in the devicekit-power source, so I guess it's not doing it today?
[12:05] <seb128> slangasek, that's a question for pitti I guess, I didn't look at that closely
[12:06] <slangasek> seb128: pull pitti's beard to make him pay attention to me, then ;)
[12:06] <seb128> slangasek, done
[12:07] <pitti> hey
[12:08] <pitti> slangasek: that sounds like a bug indeed, it's supposed to be there
[12:08] <pitti> slangasek: ah, I might have disabled it because we don't use it any more anyway
[12:09] <pitti> but that might have been a lie, g-p-m still talks to hal for brightness
[12:09] <pitti> so if it fixes it, let's re-add it
[12:09] <pitti> slangasek: beard> ouch :)
[12:11] <slangasek> pitti: it doesn't fix it, I just noticed as I went to try to follow through on it that the patch wasn't applied
[12:11] <slangasek> pitti: anyway, I need your brain to help me with the question in https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/277589/comments/51 in order to finally nail this, I think
[12:12] <slangasek> (or, well, if your brain is not available, I'll muddle through and come up with something that looks suitable to me)
[12:14] <pitti> slangasek: right, that would make sense; they need to point to the smartdimmer specific scripts to change the brightness
[12:15] <pitti> slangasek: the get/set scripts just call some CLI tool, so it doesn't need an addon?
[12:17] <slangasek> pitti: uh... that sounds accurate
[12:17] <pitti> slangasek: an addon is something that runs all the time, like the process that polls CD-ROMs for media
[12:18] <pitti> but since I suppose we don't need to react to events from the backlight (just from input events from keys, which is already provided), it doesn't need an addon
[12:24] <TheMuso> cjwatson: I have just come up with a preliminary list of source packages that libpulse0 depends on that will need to be made bi-arch. I have a feeling that some of these are not actually depended on, so I will have to look at the pulse code to see what are actually needed, so that list may yet be trimmed.
[12:24] <TheMuso> Nevertheless, there is currently 11 packages on the list. So I certainly think I will likely need help to address all of these.
[12:27] <cjwatson> TheMuso: lovely :-/
[12:27] <cjwatson> mdz: sounds sensible, though it's in universe right now ... this is the first I've heard of iw
[12:29] <TheMuso> cjwatson: My thoughts exactly.
[12:45] <slangasek> james_w: bug #408342
[12:46] <slangasek> jml: ^^
[14:46] <stoicaler> is it ok not to use firewalls?
[14:46] <Pici> stoicaler: Please ask in #ubuntu , #ubuntu-devel isn't a support channel.
[14:46] <stoicaler> ok
[14:46] <stoicaler> tx
[14:59] <slytherin> can someone please give back nautilus-sendto on armel?
[15:01] <pitti> slytherin: done
[15:02] <slytherin> thanks
[15:46] <TheMuso> cjwatson: it seems that there are a few packages that libpulse0 depends upon, but are not actually needed, however due to the way pulse is built, they are linked against libpulse0 anyway, even though no symbols are used. I am going to see if I can fix this somehow.
[15:47] <pitti> TheMuso: -Wl,--as-needed might work for some of them
[15:48] <pitti> this usually does a good first cut of cutting down stray dependencies
[15:48] <TheMuso> ok thanks
[15:50] <pitti> TheMuso: LDFLAGS+= -Wl,--as-needed
[15:57] <TheMuso> For the record, this caused pulseaudio to FTBFS.
[16:01] <seb128> TheMuso, which means it's probably using libraries and not specifying -l<lib> for all the libs it's using
[16:01] <seb128> TheMuso, and you want to use the flag on client applications to cut the unneeded depends not on pulseaudio directly
[16:06] <TheMuso> seb128: I am trying to cut down on the unneeded dependencies of libpulse0, as it is linked/depends on libraries even though it doesn't use any of their symbols.
[16:10] <seb128> TheMuso, right, so you need to use --as-needed on applications who depends on libpulse now wrongly
[16:11] <seb128> that should cut the shlibs:depends to real depends
[16:22] <slytherin> Why isn't --as-needed a default flag? does it not always work as expected?
[16:22] <slangasek> ScottK: boost1.37 removed, asio appears to still depend/build-depend on it: any plans for fixing that?
[16:23] <seb128> slytherin, it breaks builds when you don't use -llibraries correctly
[16:23] <slangasek> ah, some other packages as well, e.g., wesnoth (checkrdepends is still running, bah)
[16:23] <slytherin> seb128: Didn't know that.
[16:23] <seb128> slytherin, it also doesn't work for things you dlopen etc
[16:32] <sebner> slangasek: fighting with Arnaud Soyez hmm? :)
[16:32] <slangasek> sebner: fighting?
[16:32] <sebner> slangasek: having fun may be a better word :D
 I'm just pushing the buttons, archive admin duties are a fairly emotionless process :)
[16:33] <sebner> slangasek: will be say that again after 10 sync requests by him? :P
[16:34] <slangasek> if he continues to file sync requests inappropriately, then I'll escalate accordingly. <shrug> :)
[16:35] <sebner> haha
[16:35] <sebner> I'll point him to the wiki then to save him =)
[16:44] <cody-somerville> ---., /;8*/,l4841794976125+*954 9kj\
[16:44] <cody-somerville> oops
[16:44] <StevenK> cody-somerville: Was that a cat, or your head hitting the keyboard?
[16:45] <cody-somerville> Judging by the lump on my head...
[16:45] <maco> the cat, then?
[16:47] <mneptok> cody-somerville: if i ROT13 that do i get interesting bits of your medical history?
[16:57] <slangasek> ScottK: oh right, you addressed this in the text of the bug report. <whistle>
[17:17] <sebner> slangasek: I'm wondering you synced monkeysphere 0.25 where 0.26 was requested. (also testbuilt by me since pull-debian-source already pulled in 0.26 back then)
[17:17] <slangasek> sebner: probably an error from not having done an update-sources first; let's try again
[17:19] <sebner> slangasek: Many Thanks! :)
[17:27] <momesana> hi all
[17:27] <momesana> I am having problems starting X on every ubuntu version since 7.04
[17:28] <momesana> it's because the via drivers suck
[17:28] <momesana> now, I was wondering if the newest version of ubuntu comes with unichrome so they may work
[17:31] <cjwatson> momesana: I know nothing about this directly, but https://launchpad.net/ubuntu/+source/xserver-xorg-video-unichrome says that the Unichrome driver was in 7.04, 7.10, and 8.04, and was then removed in 8.10 because it was broken (bug 284042)
[17:31] <cjwatson> see also bug 196349
[17:32] <momesana> ubottu: thanks ... 7.04 works ... it's currently installed
[17:32] <bryce> momesana, have you tried -openchrome?
[17:32] <momesana> the other ones load the framebuffer driver and then immediately blank the screen so i cant do nothing but restart
[17:32] <momesana> 9.04 is a little better in this respect ... it doesn't load anything but I also don't have X
[17:32] <momesana> bryce: the openchrome driver fails starting X
[17:33] <momesana> bryce: as does the vesa driver
[17:33] <bryce> momesana, did you file a bug report?
[17:34] <momesana> bryce: nope but there was a bugreport somewhere with the same error message I got ...
[17:34] <momesana> and no response
[17:34]  * momesana writing karmic to a disc
[17:34] <bryce> bug#?
[17:34] <momesana> bryce: yes, it's definetly a bug
[17:35] <momesana> bryce: what I can't understand is why the vesa driver fails to load
[17:35] <bryce> momesana, bug number?
[17:35] <momesana> bryce: I can't remember anymore but it was on launchpad I think
[17:35] <cjwatson> ... that may not narrow it down ;-)
[17:35] <momesana> bryce: I will file a bugreport if I can't find it
[17:36] <cjwatson> there are 39 bugs on https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bugs right now
[17:36] <momesana> I'll boot with the karmic driver and save both the Xorg.0.log and the Xorg file ... then try vesa etc. and save everything so the devs have something to referr to
[17:37] <cjwatson> momesana: https://wiki.ubuntu.com/X/Reporting
[17:37] <momesana> cjwatson: thanks, let me read the bug reports ... maybe someone has the same problem
[17:37] <ogra> cjwatson, i would love to ask you to merge my debian-cd change to get imx51 in chape but somehow LP doesnt wont to show me code.LP.net today
[17:37] <cjwatson> ogra: URL?
[17:38] <bryce> momesana, it's probably best to file a new bug regardless; if there's one you suspect to be the same bug, just mention that and I can evaluate if it really is a dupe
[17:38] <ogra> bzr+ssh://bazaar.launchpad.net/~ogra/debian-cd/ubuntu/
[17:38] <ogra> cjwatson, ^^^
[17:38] <bryce> often two bug reports *look* like the bug, but really need each their own fix
[17:38] <ogra> cjwatson, and/or https://code.launchpad.net/~ogra/debian-cd/ubuntu
[17:39] <momesana> bryce: allright :)
[17:43] <momesana> bryce: strange ... it seems to work on the newest version of ubuntu ... now the strange thing is ... I downloaded karmic and it boots ubuntu?!?
[17:44] <TheMuso> Has anybody ever had to clean .la files during a package build, the .la files in question being generated by the package build itself?
[17:45] <seb128> TheMuso, "had"
[17:45] <seb128> ?
[17:45] <seb128> ie, how do you want to clean those and why?
[17:45] <seb128> we stopped installing those for random package and clean content for others in gnome
[17:45] <TheMuso> seb128: Clean them, as in clearing the dependency_libs variable, because its causing libraries to be uselessly linked against other libraries
[17:46] <seb128> TheMuso, if you use cdbs you can include clean-la.mk
[17:46] <seb128> TheMuso, that does what you want
[17:47] <seb128> TheMuso, otherwise you can copy the /usr/share/cdbs/1/rules/clean-la.mk snippet
[17:47] <TheMuso> seb128: yes, during the package install. My issue is with .la files that are used during the package build itself, that are internal to the package, not external.
[17:48] <TheMuso> Ok, pulseaudio has several libraries that parts of itself need linking to. When these libraries are initially built, they create .la files that include dependencies which are then uselessly linked against other libraries.
[17:48] <seb128> TheMuso, you can probably patch the source package directly too
[17:49] <TheMuso> Yeah I think thats the best option.
[17:51] <cjwatson> ogra: done
[17:52] <ogra> cjwatson, merci :
[17:52] <ogra> :)
[17:53] <seb128> TheMuso, gtk only does clean the .la in the install target not during the build
[17:53] <seb128> ie similar to what cdbs is doing, not really useful for your issue
[17:54] <TheMuso> seb128: ok thanks, I'll see if I can patch the build system, perhaps ltmain.sh to work around the issue.
[17:55] <seb128> TheMuso, you can try asking Keybuk about that maybe, he's the libtool expert around
[17:59] <TheMuso> seb128: thats also a thought, thanks.
[18:15] <TheMuso> i/c
[18:22] <cjwatson> soren: any idea what http://paste.ubuntu.com/246467/ means? I just installed eucalyptus-{cloud,cc,nc} with the intention of setting up a trivial one-node cloud on localhost, and it doesn't seem to want to start the cluster
[19:28] <slytherin> Can any of the archive admin please explain me what is the meaning of error 'failed to upload'?
[19:29] <cody-somerville> slytherin, soyuz issue
[19:29] <cody-somerville> cprov, ^^
[19:29] <cody-somerville> slytherin, link to upload log?
[19:29] <slytherin> just a sec
[19:29] <slytherin> https://edge.launchpad.net/ubuntu/karmic/+source/lucene2/+builds
[19:30] <cprov> slytherin: it means you source was built successfully but resulted in binaries that cannot be uploaded.
[19:30] <slytherin> I got the error twice for same package. First I thought was transitional so I tried it again.
[19:30] <slytherin> let me paste the email notification content.
[19:31] <slytherin> cprov: http://paste.ubuntu.com/246545/
[19:31] <cprov> slytherin: it's an issue processing one of the emails in the changesfile
[19:32] <slytherin> is it known issue?
[19:32] <cprov> slytherin: right, we all can access it directly from librarian -> http://launchpadlibrarian.net/29832266/upload_1145807_log.txt
[19:32] <cprov> slytherin: no, not really
[19:33] <slytherin> So I guess there is nothing I can do than wait.
[19:35] <cprov> slytherin: this email is associated with an account but it has no user ... weird.
[19:35] <slytherin> the package was synced from Debian.
[19:35] <cprov> slytherin: can you please file a bug, while I investigate it
[19:35] <slytherin> sure.
[19:37] <cprov> slytherin: thank you.
[19:41] <slytherin> cprov: bug 408528
[20:07] <Laney> can someone unprivate bug 408499?
[21:07] <AnAnt> Hello, I got a question about NotificationOSD
[21:07] <AnAnt> how can I disable a certain capability ?
[21:13] <maco> AnAnt: can't
[21:13] <maco> well unless you mean like "tell pidgin not to notify when someone signs on"...then the answer'd be "configure it in pidgin"
[21:14] <AnAnt> maco: no, I mean, there is a capability called truncation, can I disable that ?
[21:16] <maco> as a user? or as an application developer?
[21:16] <maco> as a user, there's very little able to be configured
[21:16] <AnAnt> developer
[21:16] <AnAnt> I use python
[21:16] <AnAnt> so I do pynotify.get_server_caps() to get capabilities
[21:17] <AnAnt> so I find that 'truncation' is one of them
[21:17] <AnAnt> can I disable that ?
[23:11] <Sp3c1alK> is there an API for ubuntu?
[23:11] <Sp3c1alK> or some type of documentation for code, more specifically networking?
[23:12] <directhex> um... that sorta depends on which of the several thousand programming languages available to you you decide to use
[23:12] <directhex> and is also not an ubuntu question
[23:12] <directhex> and is also a bit off-topic
[23:13] <directhex> (this channel is for development OF, not ON, ubuntu)
[23:13] <Sp3c1alK> yeah, I figured people who were developing ubuntu would know of an api
[23:16] <directhex> well... sure. I'd use System.Net or System.Web from your local friendly C# compiler