[00:16] <jdstrand> cjwatson: fyi, heading out for the day (and long weekend). I did find out a few things on bug #423485 if you want to llok at it more
[00:16] <jdstrand> cjwatson: if not, I can look at it next week
[01:40] <Ryan52> asac: I can't figure it out.
[01:41] <Ryan52> asac: it seems there's support for the XPCOM stuff from reading the source code, it's just linking/compiling/something wrong.
[01:41] <Ryan52> asac: messing with configure for a while (could just edit the .m4 and autoreconf, because something else's broken..) proved useless.
[01:43] <Ryan52> asac: tho I did pop in a karmic live cd and reproduced the problem finding libxul (or whatever the message was) when running gnome-web-photo, so my results match up with the bug reported not dholbach.
[01:44] <Ryan52> asac: anyways, if you could give me a hint, maybe.. :)
[01:44] <Ryan52> asac: everything I do I get undefined references.
[01:45] <slangasek> pitti, ArneGoetje: are these language-support-translations-* packages meant to be demoted to universe?
[01:47] <slangasek> pitti: er, you're dropping the cupsys transitional packages that are still used on upgrade from hardy?
[02:38] <pburleson> Not sure if this is the right place to ask, but I think it is: how do I find out what configuration and make options were used to generate an Ubuntu binary package?
[02:39] <pburleson> I need to deploy new version of Proftpd and I wanted to make sure I used the same configuration parameters the normal Ubuntu package is built with
[02:39] <Ryan52> pburleson: usually by looking at it's debian/rules file.
[02:40] <pburleson> in the source package?
[02:40] <Ryan52> yes.
[02:40] <pburleson> thank you
[02:40] <Ryan52> tho for some packages, it requires knowledge of debhelper/CDBS/etc.
[02:40] <pburleson> oh, fun
[03:58] <YokoZar1> jcastro: Is this you: http://video.linuxfoundation.org/users/canonical  ?
[04:31] <jcastro> YokoZar1: no, I have no idea how that got on there
[04:48] <YokoZar1> jcastro: well it's a good outlet as I got an email from a Wine dev who didn't see it until it was there
[11:55] <asac> Ryan52: how are you trying to link now?
[12:05] <melvin> Hi. The run dialog isn't working  after yesterdays update. is it a known problem?
[12:05] <melvin> and pulseaudiu doesn't sound out anything
[12:05] <melvin> Error MEssage from teh Run dialog: "Unable to load file '/usr/share/gnome-panel/glade/panel-run-dialog.glade'"
[13:40] <fta> cjwatson, fyi, the new zlib in karmic is causing me some troubles: http://paste.ubuntu.com/265545/
[13:43] <moldy> hi
[13:44] <moldy> when uploading to my ppa, i get File <UPLOADED_FILE> already exists in <LOCATION>, but uploaded version has different contents.
[13:44] <moldy> but i don't really understand why
[13:44] <moldy> am i forced to bump the version number?
[13:49] <fta> moldy, you're sending a source package with the same .orig.tar.gz name but not the same content (different md5/sha). See -sa vs -sd
[13:50] <moldy> fta: hm, ok, i think i begin to understand :)
[13:50] <asac> i added the chromium zlib log fta gave me to the bug 402178
[13:50] <moldy> fta: i am changing the source along with the ubuntu package... i guess the solution is to just delete the package from the ppa and upload it again
[13:51] <fta> moldy, no
[13:51] <fta> moldy, just redo your source package with -sd instead of -sa
[13:51] <moldy> fta: will try that, thanks
[13:56] <moldy> fta: hm, same results
[13:58] <fta> moldy, either you don't include the .orig.tar.gz in the dsc (as i said), or you have to reuse the exact same tarball already in the archives
[13:58] <fta> moldy, this question is more for #ubuntu-motu btw
[13:59] <moldy> hm, maybe i included the orig.tar.gz by accident
[13:59] <moldy> fta: ok, thank you
[14:07] <moldy> hm, the thing is, i am using -sd, but orig.tar.gz still seems to end up in the dsc...
[14:07] <james_w> moldy: -sd controls the .changes file
[14:07] <james_w> the .orig.tar.gz always has to be in the .dsc
[14:08] <james_w> for the checksum
[14:09] <moldy> ok, i see. but then i still don't understand why i get that error e-mail
[14:09] <james_w> well, it applies to all the parts, not just the .diff.gz
[14:09] <james_w> so if you are re-using a version number that is in Ubuntu or in your PPA then you will likely see it
[14:10] <moldy> hm, the error message only complains about the orig.tar.gz
[14:10] <james_w> well, you uploaded the orig.tar.gz then
[14:10] <james_w> -sd should have stopped that, but maybe you didn't upload what you expected to
[14:10] <moldy> hm, i will re-check this
[14:10] <moldy> when you're talking about -sd, you are talking about dpkg-buildpackage?
[14:11] <james_w> yeah
[14:16] <moldy> ok, the dput output said it uploaded the .dsc, the .diff.gz and the .changes
[14:16] <moldy> ... but i still get that error e-mail :(
[14:17] <moldy> now both for the .orig.tar.gz and the .diff.tar.gz
[14:23] <asac> siretart: would you mind to join #ubuntu-mozillateam for a while ;) ... on ffmpeg.
[14:28] <pitti> slangasek: language-support-translations-*> please leave them for now, they will be removed once the new language-selector is uploaded
[14:28] <pitti> slangasek: cupsys transitional packages> eww, forgot; will re-add them
[14:29] <james_w> moldy: ah, I remember it's comparing the checksums, even though you don't upload it
[14:29] <james_w> moldy: use the same .orig.tar.gz that is in the archive when building
[14:30] <james_w> but still use -sd
[14:40] <moldy> james_w: ok, will try that, thank you
[14:42] <moldy> james_w: will just bumping the version number also work? i'm beginning to think it's the easiest solution
[14:54] <moldy> james_w: now it complains that orig.tar.gz is missing "in upload or distribution" :) i'm giving up, trying to see if another version number works
[16:04] <hyperair> is anyone noticing underruns when something is playing sound, and something else interrupts it?
[16:05] <ion> My guess would be is that pulseaudio expects a lower latency than it can actually achieve, because rtkit isn’t able to provide that for it, because the kernel patch isn’t added to Ubuntu yet.
[16:13] <ulaas> hi .whats wrong with libldb-samba4-0
[16:22] <ulaas> will evolution-mapi see some love before karmic release?
[18:02] <donri> why software-store over gnome-packagekit? if something is wrong with it, would it not be better to fix it? ubuntu specific things required? is that really a good thing?
[20:23] <Ryan52> asac: I dunno, I just messed around for a while...I don't really have a clue what I'm doing when it comes to this XPCOM glue stuff :)
[20:44] <cjwatson> fta: I thought that's what mvo was fixing; if he broke it, best check with him rather than me
[20:45] <fta> cjwatson, ok
[21:08] <slangasek> pitti: ok.  btw, those uninstallable gnome langpack packages are the current cause of Ubuntu DVD build failures
[21:09] <cjwatson> anyone have any idea where bug 70317 ought to be fixed?
[21:09] <slangasek> jelmer: bug #424626> anything I can do to help with getting the new version into karmic, then?
[21:10] <slangasek> cjwatson: either udev or the kernel
[21:10] <slangasek> (depending on whether the key presses are already recognized - kernel - or not - udev)
[21:11] <cjwatson> if I reassign it to udev, won't Scott just tell me that some console package should be figuring out the keyboard in use and installing a udev rule? :-)
[21:12] <cjwatson> (and he might have a point, unless udev already has keyboard stuff in it ...)
[21:12] <slangasek> udev does have keyboard stuff in it
[21:12] <slangasek> /lib/udev/keymaps
[21:13] <cjwatson> ah, does it now - that's new since I last looked
[21:13] <slangasek> part of the halsectomy :)
[21:13] <cjwatson> the current iteration of the report is on 9.04 so it may predate that
[21:14] <slangasek> I don't think there are /currently/ any keymaps in place for non-laptop keyboards (I see now this is a Microsoft wireless keyboard), but no reason there can't / shouldn't be
[21:15] <slangasek> OTOH, if these are "power status messages" that shouldn't register as keys at all, then it may yet be a kernel bug
[21:17] <cjwatson> well, I've learned something today, thanks
[21:17] <cjwatson> reassigned the bug
[21:17] <slangasek> :)
[22:03] <LaserJock> you guys happen to know what might cause having to resume twice after suspend in order to get it to actually resume?
[22:31] <slangasek> LaserJock: double suspend event handling
[22:31] <slangasek> possibly because of buggy hotkey configuration
[22:32] <LaserJock> I noticed that at least some of my laptop's function keys no longer work
[22:33] <LaserJock> but I'm somewhat hardware-illiterate as almost always Ubuntu just works on my hardware
[22:34] <LaserJock> slangasek: what would be a likely package to look for bugs of this kind?
[22:36] <slangasek> LaserJock: https://wiki.ubuntu.com/Hotkeys/Troubleshooting
[22:37] <LaserJock> slangasek: awesome, thanks
[22:41] <LaserJock> with xev, if I press a keyboard key should I expect 2 events? like one for pressing down and one for releasing?
[22:42] <slangasek> yes
[22:42] <slangasek> (if it's a key that's passed via X)
[22:42] <LaserJock> ok