[02:36] <psusi> how do you set a property with gtkmm?  the docs say that MessageDialog has Glib::PropertyProxy< MessageType > property_message_type ()... doesn't that make a member you can just assign to?
[02:37] <EvilResistance> how hard is it to set up a multiple-binary source package (sort of how php5 and dpkg are)
[07:09] <Alison_Chaiken> I've been struggling with debian/rules for hours.
[07:10] <Alison_Chaiken> I hit this error: "dh-install: package-dev missing files (usr/include/*)"
[07:11] <Alison_Chaiken> Does anyone know if this failure means that the source directory can be located or the destination one?
[07:11] <Alison_Chaiken> I can't figure out why the failure is happening for this package but not the others.
[07:13] <Alison_Chaiken> And are files missing or is directories themselves that can't be located?   The error message is so unhelpful, and the script is perl (yuck!).
[07:13] <geser> Alison_Chaiken: the package "package-dev" is missing some expected files (listed in debian/package-dev.install) so it can't be build
[07:14] <Alison_Chaiken> Thanks geser.    So source files are not being found in the expected source directory?    My attempts to change DESTDIR are irrelevant?
[07:15] <geser> can you pastebin the debian/package-dev.install file? (if it contains more than just one line)
[07:15] <micahg> sounds like stuff isn't being installed in the proper place in debian/tmp
[07:20] <Alison_Chaiken> Sure.     Let me regenerate the system-built one since I've been screwing without them by hand just for debug.
[07:22] <geser> while you are it, please also pastebin debian/rules
[07:26] <dk> Alison_Chaiken: are you who is talking about Mobile linux at SCALE next month?
[07:30] <Alison_Chaiken> That's me.
[07:31] <Alison_Chaiken> Unfortunately, geser, I appear to have broken something else, as I can't get the build to proceed as far as the point I was talking about.    So I've now broken it upstream of where I've been stuck all afternoon.
[07:31] <Alison_Chaiken> Must be a sign of progress.
[07:37] <Alison_Chaiken> Sorry for wasting your time, geser and micahg, but I'm afraid I'm going to just have to go to bed and try again tomorrow.    I can't get the build to even start now, whereas before I merely couldn't get it to finish.
[15:13] <psusi> what does g_thread_self() return in the main thread?  is there a static instance of a GThread somewhere for the main thread?  I'm looking for a way to find out if I'm in the main thread context or not...
[16:12] <royh> do anyone know why chef-server is only in lucid and maverick?
[16:39] <jtaylor> when applying a debdiff from someone else do we leave the author of the debdiff in the changelog maintainer line?
[16:41] <udienz> jtaylor, i think you can mention in changelog his name
[16:41] <Laney> depends on what other changes you want to make
[16:42] <Laney> i usually leave it unless my changes are much bigger than theirs, but it's up to you
[16:43] <udienz> Laney, what 'depends'? usually i mention his name even he only change po files, is that right?
[16:43] <Laney> you should always mention it in the changelog, the question is about who gets the credit for the whole upload (Changed-By)
[16:43] <jtaylor> udienz: I mean the lower line inthe changelog which according to debia policy states the uploader
[16:46] <udienz> jtaylor, do you mean this line -- $DEBFULLNAME `date -U`?
[16:46] <jtaylor> yes
[16:47] <Laney> it is called the trailer
[16:50] <udienz> jtaylor, i agree with Laney. if we don't change, perhaps thats sponsoring
[17:26] <Alison_Chaiken> My project comes from 4 git repos: two libraries, a plugin framework and a plugin.
[17:26] <Alison_Chaiken> I must build the binaries in that order due to the dependencies.
[17:27] <Alison_Chaiken> I'm having trouble locating documentation that addresses this situation, where none of the 4 repos is currently packaged for me to use.
[17:28] <Alison_Chaiken> I guess that all 4 builds must output to the same root filesystem in a common build directory, as they need to see each others' headers and shared object.
[17:30] <Alison_Chaiken> I could fully package and install each of the projects in turn, I guess, but installing in the actual system directories during a build seems contrary to the accepted way of doing things.
[17:30] <Alison_Chaiken> If anyone could suggest an example to look at or documentation that doesn't assume one new source tree with all other packages from repos, I'd appreciate it!
[17:31] <Laney> Alison_Chaiken: It is common to set up a local repository (e.g. with reprepro) for such a situation
[17:31] <Laney> and add that as a source in the chroot you build in
[17:31] <Alison_Chaiken> Perhaps if all builds refer to one debian/tmp directory and one set of rules, that will do the trick?
[17:33] <Alison_Chaiken> So I build package one, install it in the local repo, then 2, then 3, and they each put their shared-object libraries and headers in that repo as they proceed?
[17:34] <Alison_Chaiken> I'll read up n reprepro Laney, thanks.
[17:35] <Laney> you put the /packages/ in the repository and add them to Build-Depends of the other ones as appropriate
[17:36] <Alison_Chaiken> Ah, in the control file.    And the control file docs will describe how to point at the local repo instead of the root filesystem.
[18:11] <fenryxo> Hi
[18:24] <fenryxo> I would like to package my application for Ubuntu. It's called Nuvola Player and provides integration of cloud music services with Linux desktop (multimedia keys, Ubuntu Sound menu, Unity Launcher Quick list, etc.). I've already created a "needs-packaging" bug report https://bugs.launchpad.net/ubuntu/+bug/909021 and first version of source package that is now ready for review. It's my first package so I'm sure it isn't without mistakes. Would someone 
[18:30] <EvilResistance> e
[18:30] <Resistance> whoops
[18:30] <Resistance> forgive the random "e" :P
[18:49] <broder> fenryxo: i can do a quick skim of the packaging, but have you considered trying to get the package into debian instead? we prefer that when possible because we've found that packages just seem to end up better maintained that way
[18:50] <broder> (i'm a fan of nuvola, so i'm happy to help as much as i can)
[18:51] <broder> fenryxo: https://wiki.ubuntu.com/Debian/ForUbuntuDevelopers#Getting_new_software_in_Debian might be useful information
[18:56] <broder> bah, it uses libunity
[18:58] <fenryxo> broder: I considered submitting to Debian, but the import freeze is already in January, Precise imports from Debian testing instead of unstable and I don't know how long would the whole process takes
[18:59] <fenryxo> libunity is used for integration with Unity Launcher (Quick list)
[18:59] <broder> fenryxo: that's ok - we have a little more time than that. import freeze is just when we stop automatically syncing from debian; we can continue to do manual syncs after that
[18:59] <broder> and syncing from unstable is also an option
[19:01] <broder> but debian doesn't have libunity
[19:01] <broder> we'd have to disable the libunity features in debian then re-enable them in ubuntu, but i think that's still preferable to uploading directly to ubuntu
[19:01] <fenryxo> libunity is not required if Nuvola is not build with "--with-unity-quick-list"
[19:03] <broder> fenryxo: it looks like the debian/docs file is empty, so you could drop that from the package
[19:04] <broder> can the build system detect the presence of libunity? if we can let it do that, then the only change we'd need to make on the ubuntu side is adding libunity-dev to the build deps
[19:05] <broder> the packaging mostly looks good, though - i'm mostly looking for things to nitpick over at this point
[19:08] <broder> instead of using the override_dh_installman target, i tend to prefer using debian/<package>.manpages
[19:08] <fenryxo> broder: the build system can detect libraries, autodetection of libunity looks like great solution. I'll fix it + the debian/doc file
[19:08] <broder> but like i said, nit
[19:09] <broder> can you turn on gtk3 for newer releases? do newer versions of webkitgtk3 work with flash?
[19:11] <fenryxo> I didn't check the newer versions yet. I've tested building with GTK3 only with version 0.1 and I'm sure the code contains some GTK3-incompatible code.
[19:12] <broder> gtk2 certainly isn't a blocker for anything, but it would definitely be nice to move anything to gtk3 that we can
[19:12] <broder> but that can be a more long-term goal
[19:16] <broder> the copyright file looks like it needs a little work: http://paste.ubuntu.com/786054/
[19:17] <fenryxo> GTK3 port is on the todo list, but currently I'm planning only bug fix releases until I pass all exams
[19:17] <broder> haha, sure, been there :)
[19:17] <broder> i would line wrap the copy of creative commons in the copyright file
[19:23] <fenryxo> ok, it seems I have to use more up-to-date lintian, because mine doesn't complain
[19:24] <broder> there are also a handful of complaints on the binary package: http://paste.ubuntu.com/786065/
[19:24] <broder> i think no-upstream-changelog is a red herring
[19:24] <broder> (since i believe ubuntu policy is to not include those)
[19:25] <broder> but i think that's my lintian being out of date
[19:28] <fenryxo> I currently use lintian included in Natty
[19:30] <broder> ah yes. precise's version of lintian definitely suppresses no-upstream-changelog on ubuntu. i should have known that, because i wrote the patch for it :)
[19:31] <broder> i like the ui changes in this new version
[19:32] <broder> dropping the toolbar at the top of the window and stuff
[19:37] <fenryxo> the tool bar was temporary solution :) I think Nuvola Plyer finally matured enough to be included in Ubuntu
[19:38] <broder> i've been really happy with nuvola. i'm looking forward to seeing it in the distro - thanks for working on it :)
[19:38] <broder> not quitting on close if music isn't playing is also awesome
[19:40] <fenryxo> this behavior is based on instructions at Ubuntu Sound menu page
[19:45] <broder> fenryxo: line 27 of the debian/rules file is an empty line but has a bunch of extra tabs. they're harmless but would be good to clean them up
[19:47] <broder> fenryxo: but in general, the packaging looks quite good. and if i drop the libunity-dev build-dep and the --with-unity-quick-list option, the package builds without modification on debian unstable
[19:48] <broder> so from here, i think the next steps are:
[19:48] <broder> (a) see if the build system can be modified to auto-detect libunity instead of using the build flag
[19:48] <broder> (and drop the build flag)
[19:48] <broder> (b) open an ITP bug with debian
[19:49] <broder> (c) make the modifications mentioned in https://wiki.ubuntu.com/Debian/ForUbuntuDevelopers#Required_packaging_changes
[19:49] <broder> (d) post the package to http://mentors.debian.net and send out a request for debian sponsorship
[19:51] <broder> sound reasonable?
[19:51] <fenryxo> broder: sounds great :)
[19:52] <fenryxo> broder: thanks for the review
[19:53] <broder> glad to help :)
[22:13] <KNRO> is {svn-revno} supported as variable substitution in recipe?
[22:57] <lifeless> KNRO: I don't believe so