[00:09] sistpoty, http://pastebin.ubuntu.com/269459/ [00:10] *downloading source* [00:12] sistpoty, the patch I applied is http://www.mail-archive.com/lftp-devel%40uniyar.ac.ru/msg01706.html [00:27] cody-somerville: interesting... I've fiddled a little bit to find out what went wrong, here's the resulting (non-cleaned) patch: http://paste.ubuntu.com/269465/ [00:27] cody-somerville: the guilty part seems to be nesting [] in other [] [00:28] cody-somerville: I must admit that I'm not 100% sure what the nested brackets do, or if these are allowed in the first place [00:28] interesting [00:29] cody-somerville: the rest of the changes can be ignored (it just made vim happy to not have a ' in the strings) [00:29] (and of course the spelling errors must be ignored *g*)( [00:30] the nested brackets just show up in the help output [00:30] so changing them to parenthesis should be safe [00:30] thanks! :) [00:30] you're welcome ;) [00:31] so would I want to run autoreconf at build time or use that to generate the patch? The former, right? [00:33] cody-somerville: personally, I prefer to run autotools at build time [00:34] cody-somerville: iirc there are arguments against doing it, but the only valid one I've heard is that many people claimed a ftbfs to be a fault of changed autotools (due to maintainers not knowing what went wrong) [00:34] (and hence blaiming autotools for it) [00:50] kirkland: Hey. Seems like if you create a user, run screen and later delete the user, an entry for it in /var/run/screen remains. If you then try to install or update byobu it will fail on postinst because it creates a .reload-required file for the user but can't do the chown. [00:50] kirkland: (also, why does it warn about the update on install?) [00:54] RainCT: sounds like "delete user but not all files the user owns" problem? I assume slangasek has a stance on this one ;) [00:55] well, admins should be allowed to do that if they wish [00:55] Yeah, I don't want to delete it's files, only the user :) [00:56] *its [00:58] RainCT: oh, so it's not the problem that a postint deletes a user... sorry for getting that wrong [00:58] erm, postrm [01:01] sistpoty: no, it's the postinst doing this http://paste.ubuntu.com/269478/ where the user has been deleted (so chown $u fails) [01:03] RainCT: ah, but that doesn't stem form postrm deleting a user [01:04] RainCT: imo that's a mere bug of assuming that a user exists [01:04] sistpoty: yeah, I've never mentioned postrm deleting any user [01:04] (just because there's a directory called like the username) [01:04] RainCT: sorry, I didn't read good enough ;) [01:05] hehe np === rickspencer3 is now known as rickspencer3-afk [09:07] So I saw that fluidsynth-dssi FTBFS, and the fix was simple; to depend on liblash-dev instead of ladcca-dev [09:09] That was probably my fault from the beginning, since when I updated fluidsynth to 1.0.9 I changed it to depend on liblash instead of ladcca [09:10] But I fail to see why fluidsynth-dssi should need liblash.la at all === yofel_ is now known as yofel [10:15] Newbie packaging question: if a `make install` creates directories that do not match the preferred layout of ubuntu packages (of this type), should I modify the Makefile or is there a file in the ./debian directory that can remap these locations? [10:18] do I create a patch for the Makefile or something else? [10:19] or...does someone have a good newbie guide link lying aroundL [10:19] ? [10:19] try asking in #ubuntu-motu [10:20] azeem: thanks [13:38] where i can look changes between karmic daily live cds? === asac_ is now known as asac [15:41] I wonder why -Wl,--as-needed is not automatically added to LDFLAGS by dpkg-buildpackage === ksymoops is now known as _09226082168 === _09226082168 is now known as dous [20:49] who is the xsplash master [20:49] ? [21:08] hey. where are my ctrl+alt+FX virtuals? [21:09] did you start your gettys? [21:10] ps -C getty [21:10] hyperair, since when do they need starting? [21:10] :) [21:11] hyperair, they are running [21:12] then what do you see when you do ctrl+alt+fX? [21:12] blinky cursor [21:12] no login prompt? [21:12] how strange [21:13] hyperair, yeah [21:13] * hyperair doesn't know [21:14] and where is DontZap [21:14] whats going on here? [21:17] DontZap? wasn't that in xorg.conf? [21:17] “dontzap” source package in Ubuntu Deleted in karmic-release (Reason: obsolete) [21:18] obsolote, because? [21:18] IIRC because xorg upstream removed the option from xorg.conf entirely [21:18] prolly because xorg.conf has that [21:18] ahh, it's not even in xorg.conf anymore? [21:19] maxb, any other methods? [21:19] gdm restart? [21:19] there's something complicated that you can do with x key bindings to enable zapping [21:20] There's GUI for it. [21:20] ScottK, ahh the hard way of doing simple things.. great. what is that? [21:20] I don't know for Gnome. Don't use it. [21:21] It's in systemsettings for KDE. [21:21] suddenly felt like trying my netinstall archlinux image.. [21:21] lemme grab a cdr [21:22] ulaas_: in the system - keyboard settinsg [21:22] *settings [21:22] ulaas_: It's buried deep in gnome-keyboard-properties [21:22] Layouts tab, "Layout Options...", "Key sequence to kill the X server" [21:24] maxb. thanks man. [22:12] lol [22:12] Pressing alt+f4 dismisses the login window. Pressing it again asks you if you want to log out or switch users.