[13:38] <slytherin> Mithrandir: Gentle Reminder about bluez-gnome. :-D
[13:39] <Mithrandir> main's frozen at the moment
[13:40] <Mithrandir> it's on my list of stuff to get updated post-freeze
[13:44] <slytherin> Mithrandir: Oh, you mean soft freeze for for Alpha 6? If possible can you upload it to bluetooth team ppa and announce it on mailing list so that we will no if there are any problems before package hits main archives.
[13:44] <Mithrandir> I could do that, sure
[13:50] <Mithrandir> slytherin: hm, I think I failed at applying the "disable" patch in the first place, so the current version in hardy should be good, I think
[13:51] <slytherin> Mithrandir: Oh. I didn't check it actually. I just thought it was disabled. :-)
[13:52] <Mithrandir> slytherin: I meant to disable it, but I forgot to, it seems.
[13:52] <Mithrandir> (or rather, I was playing around with the gvfs-obex stuff and therefore disabled the disabling)
[13:53] <slytherin> Mithrandir: So only thing that remains is dropping gnome-vfs-obexftp dependency.
[13:53] <Mithrandir> yup
[17:53] <GrueMaster> I have a dpkg apt-get newb question.  I have a package that is dependent on a kernel module package.  The kernel module is installed by default (as opposed to stand alone), but how do I install the other package w/o apt complaining about missing dependencies?  I can do a --ignore-depends or a --force-depends, but the next time I go to install something, apt-get wants to remove that package.
[17:53] <GrueMaster> For the record, I'm an RPM wiz.
[18:41] <lool> GrueMaster: You shouldn't ever --force anything
[18:42] <lool> GrueMaster: If your module is provided the kernel itself instead of being standalone, then either the dependency should be relaxed to be <standalone-package> | <kernel-image-with-the-module> OR you could make the kernel package Provide: that module package name
[18:47] <GrueMaster> ok.  Not sure I understand any of that.
[18:51] <lool> GrueMaster: You have a dependency on something which you can't satisfy, what's something?
[18:51] <mjg59> GrueMaster: If the file can be shipped without being in a standalone package, then your other package should not depend on that module package
[18:51] <mjg59> GrueMaster: Instead, you should make it something like "module-package | kernel-package (>=version)"
[18:52] <mjg59> GrueMaster: Where version is the first version of the kernel package that ships that module
[18:52] <GrueMaster> I've got it worked around, thanks.
[18:54] <GrueMaster> I find it interesting that if a package depends on another package, even if the other package is installed by different means (direct from source, part of another package, etc), there is no graceful way to tell dpkg to ignore the dependency without rebuilding.
[18:55] <lool> There are many ways to workaround such as equivs or dpkg-repack, but it's usually simpler to rebuild
[19:05] <kyleN> lool. got a moment to clarify for me what you meant by "the corresponding xsetting"? That is, what is it, where would I find it, and how do I set it? 
[19:18] <lool> kyleN: There's a layer atop of X which allows to get X messages when some Xsettings change; it's implemented in libxsettings; Gtk+ apps listen to some settings and you can find a list by googling for gtk+ + xsettings
[19:19] <lool> kyleN: I have to go for dinner
[19:19] <kyleN> lool: great
[19:19] <lool> It's simply not covered by any proper doc, so you'll have to dig the source
[19:19] <kyleN> cheers
[19:19]  * lool &