[00:09] <cody-somerville> sistpoty, http://pastebin.ubuntu.com/269459/
[00:10] <sistpoty> *downloading source*
[00:12] <cody-somerville> sistpoty, the patch I applied is http://www.mail-archive.com/lftp-devel%40uniyar.ac.ru/msg01706.html
[00:27] <sistpoty> 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] <sistpoty> cody-somerville: the guilty part seems to be nesting [] in other []
[00:28] <sistpoty> 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] <cody-somerville> interesting
[00:29] <sistpoty> cody-somerville: the rest of the changes can be ignored (it just made vim happy to not have a ' in the strings)
[00:29] <sistpoty> (and of course the spelling errors must be ignored *g*)(
[00:30] <cody-somerville> the nested brackets just show up in the help output
[00:30] <cody-somerville> so changing them to parenthesis should be safe
[00:30] <cody-somerville> thanks! :)
[00:30] <sistpoty> you're welcome ;)
[00:31] <cody-somerville> so would I want to run autoreconf at build time or use that to generate the patch? The former, right?
[00:33] <sistpoty> cody-somerville: personally, I prefer to run autotools at build time
[00:34] <sistpoty> 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] <sistpoty> (and hence blaiming autotools for it)
[00:50] <RainCT> 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] <RainCT> kirkland: (also, why does it warn about the update on install?)
[00:54] <sistpoty> RainCT: sounds like "delete user but not all files the user owns" problem? I assume slangasek has a stance on this one ;)
[00:55] <slangasek> well, admins should be allowed to do that if they wish
[00:55] <RainCT> Yeah, I don't want to delete it's files, only the user :)
[00:56] <RainCT> *its
[00:58] <sistpoty> RainCT: oh, so it's not the problem that a postint deletes a user... sorry for getting that wrong
[00:58] <sistpoty> erm, postrm
[01:01] <RainCT> 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] <sistpoty> RainCT: ah, but that doesn't stem form postrm deleting a user
[01:04] <sistpoty> RainCT: imo that's a mere bug of assuming that a user exists
[01:04] <RainCT> sistpoty: yeah, I've never mentioned postrm deleting any user
[01:04] <sistpoty> (just because there's a directory called like the username)
[01:04] <sistpoty> RainCT: sorry, I didn't read good enough ;)
[01:05] <RainCT> hehe np
[09:07] <diwic> So I saw that fluidsynth-dssi FTBFS, and the fix was simple; to depend on liblash-dev instead of ladcca-dev
[09:09] <diwic> 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] <diwic> But I fail to see why fluidsynth-dssi should need liblash.la at all
[10:15] <tilgovi> 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] <tilgovi> do I create a patch for the Makefile or something else?
[10:19] <tilgovi> or...does someone have a good newbie guide link lying aroundL
[10:19] <tilgovi> ?
[10:19] <azeem> try asking in #ubuntu-motu
[10:20] <tilgovi> azeem: thanks
[13:38] <darkham> where i can look changes between karmic daily live cds?
[15:41] <c_korn> I wonder why -Wl,--as-needed is not automatically added to LDFLAGS by dpkg-buildpackage
[20:49] <tripzero> who is the xsplash master
[20:49] <tripzero> ?
[21:08] <ulaas_> hey. where are my ctrl+alt+FX virtuals?
[21:09] <hyperair> did you start your gettys?
[21:10] <hyperair> ps -C getty
[21:10] <ulaas_> hyperair, since when do they need starting?
[21:10] <ulaas_> :)
[21:11] <ulaas_> hyperair, they are running
[21:12] <hyperair> then what do you see when you do ctrl+alt+fX?
[21:12] <ulaas_> blinky cursor
[21:12] <hyperair> no login prompt?
[21:12] <hyperair> how strange
[21:13] <ulaas_> hyperair, yeah
[21:13]  * hyperair doesn't know
[21:14] <ulaas_> and where is DontZap
[21:14] <ulaas_> whats going on here?
[21:17] <hyperair> DontZap? wasn't that in xorg.conf?
[21:17] <maxb> “dontzap” source package in Ubuntu    Deleted in karmic-release  (Reason: obsolete)
[21:18] <ulaas_> obsolote, because?
[21:18] <maxb> IIRC because xorg upstream removed the option from xorg.conf entirely
[21:18] <tripzero> prolly because xorg.conf has that
[21:18] <tripzero> ahh, it's not even in xorg.conf anymore?
[21:19] <ulaas_> maxb, any other methods?
[21:19] <ulaas_> gdm restart?
[21:19] <maxb> there's something complicated that you can do with x key bindings to enable zapping
[21:20] <ScottK> There's GUI for it.
[21:20] <ulaas_> ScottK, ahh the hard way of doing simple things.. great. what is that?
[21:20] <ScottK> I don't know for Gnome.  Don't use it.
[21:21] <ScottK> It's in systemsettings for KDE.
[21:21] <ulaas_> suddenly felt like trying my netinstall archlinux image..
[21:21] <ulaas_> lemme grab a cdr
[21:22] <sebner> ulaas_: in the system - keyboard settinsg
[21:22] <sebner> *settings
[21:22] <maxb> ulaas_: It's buried deep in gnome-keyboard-properties
[21:22] <maxb> Layouts tab, "Layout Options...", "Key sequence to kill the X server"
[21:24] <ulaas_> maxb. thanks man.
[22:12] <cody-somerville> lol
[22:12] <cody-somerville> Pressing alt+f4 dismisses the login window. Pressing it again asks you if you want to log out or switch users.