[02:15] <micahg> ajmitch: ping about backports open at feature freeze LP stuff :)
[02:16] <ajmitch> micahg: pong about replacement system sitting behind me for dead hardware at home ;)
[02:17] <micahg> ajmitch: heh, I just had to swap out RAM last night myself :)
[02:17]  * ajmitch had it go kaput altogether
[02:17] <ajmitch> yes it's been on my todo list to get it in, sorry I missed FF
[02:18] <micahg> ajmitch: anytime before R would be fine IMHO :)
[02:19] <ajmitch> sooner the better
[02:19] <ajmitch> I'll bug StevenK to help me land it soon, he won't mind much
[02:20]  * StevenK glares at ajmitch.
[02:20] <ajmitch> you did offer
[03:19] <ScottK> micahg: Cool.
[03:19] <ScottK> Thanks for letting me know.
[07:22] <oly> hi, I am quite new to debian packageing, is anyone able to shed some light on this error ? E: geany-plugin-code-snippets: dir-in-usr-local usr/local/share/
[07:36] <oly> I am also getting this error using a slightly different rules file which has me stumped, rmdir: failed to remove `debian/geany-plugin-code-snippets/usr/local/share/geany/geanypy/plugins/geany-snippets': Directory not empty
[07:37] <oly> why the build process would be creating files it can then not delete later on is a tad strange
[07:42] <geser> it's not a file but a non-empty directory you try to remove
[07:43] <oly> yeah i get that but i dont get why, as its all pretty much done and handled by the build process as far as i can tell
[07:44] <oly> I am no longer doing anything in the rules file and leaving it to the helpers to manage
[07:45] <oly> I basically have %:	dh $@ in my rules file
[07:45] <oly> this is a python program, and i have created similar projects and not hit the issue
[07:47] <oly> I have everything on launchpad bzr branch lp:~oly/geany-code-snippets/trunk
[07:47] <oly> and i am building with bzr-buildpackage -- -uc -us if thats any help, the debian files are in the repository as well if anyone has any ideas
[07:49] <geser> your debian/install files mentions to copy the geany-snippets directory to there (/usr/local/...)
[07:50] <oly> yeah, its the path for the plugin folder for geany
[07:51] <geser> a package shouldn't install to /usr/local/...
[07:51] <geser> does geany find the plugins also in /usr/share/geany/...?
[07:51] <oly> hum, maybe will look see if that exists
[07:52] <geser> if yes then let your debian/install install it there (simply remove the /local from the path)
[07:53] <oly> does not exist, but i recon your onto something geser :)
[07:53] <oly> got a feeling my machines have geany compiled from source, instead of from the debian file which could be why the paths are different
[07:54] <oly> I will setup a vm to test this out, thank you for your time.
[07:57] <oly> well changing the path fixes all my issues at least, so i know its definitely the /usr/local causing me the issues :)
[14:16] <marcos> hello everybody.
[14:16] <marcos> someone Can you tell me about "edit-patch" command? i try create a new patch for hello package but "no series file found" error occurs.
[14:17] <marcos> may be this is a basic question, but i'm a n00b :)
[14:17] <marcos> developer n00b*
[14:17] <arand> That sounds like there are no current patches? 'series' is normally the patch "index" file
[14:18] <marcos> arand: very curious. the help say to create a new patch with edit-patch.
[14:18] <marcos> where is series file?
[14:19] <arand> Which help?
[14:20] <marcos> arand: man page. sorry.
[14:21] <marcos> "It  can  also be used to incorporate new patches."
[14:23] <arand> I'm not sure if it would work if you just "mkdir debian/patches; touch debian/patches/series" ...
[14:25] <marcos> doesn't work :(
[14:26] <marcos> may be i wait for class about patches in ubuntu developer week to learn how i can make a patch
[14:26] <marcos> by the way, there's a channel about ubuntu cloud? i have a specific question about juju and cloud.
[14:27] <Bachstelze> marcos: "new patches" here means "adding a patch when patches already exist"
[14:27] <Bachstelze> if there are no patchs you have to create a patch system before
[14:27] <marcos> Bachstelze: first create a .patch file. second: add to source?
[14:28] <marcos> Bachstelze: or: exist a patch. add another patch?
[14:28] <Bachstelze> marcos: to create the first patch you can use quilt directly for example
[14:29] <marcos> Bachstelze: ok. thanks. the session about patches on developer week may be very helpful :)
[14:44] <dholbach> https://wiki.ubuntu.com/UbuntuDeveloperWeek Day 2 starting in ~15 minutes in #ubuntu-classroom
[17:02] <FlowRiser> uhmm, hello :D
[17:03] <FlowRiser> I want to develop a new login screen for Ubuntu. What's the best way to do this ? (to make it as lightweight as necessary)
[17:04]  * ogra_ thought that was actually the purpose of lightdm
[17:05] <FlowRiser> oh, hi ogra;
[17:05] <FlowRiser> ogra_: it is, but i want to style it up a bit
[17:05] <FlowRiser> and to be honest, i find the lightdm documentation lacking
[17:32] <xnox> FlowRiser: "style it  up" visuals or code/features? There are multiple lightdm login screen (greeters) providers in: gtk, kde, and other toolkits. (html/css as well or am I wrong)
[17:33] <xnox> FlowRiser: pull the sample code with apt-get source and hack away.
[17:33] <FlowRiser> xnox: i tried to do that, but they just won't make sense for me; Is it possible to use C++/GTK ?
[17:34] <FlowRiser> xnox: i found a python sample, a commented sample; That i can convert to c++, but i'm not sure if the headers will work ...
[17:35] <FlowRiser> My main problem is that the most sample codes are not commented at all
[17:36] <xnox> my opinion "you are doing it wrong if you are using C++ & GTK", but it should still all work just fine.
[17:37] <xnox> FlowRiser: take Qt sample/greeter. It's in C++. Look at the unity greeter (is it gtk? i think it is)
[17:37] <xnox> for equivalent gtkmm stuff.
[17:37] <FlowRiser> so gtkmm is for c++ ?
[17:38] <FlowRiser> this works
[17:38] <FlowRiser> wow
[17:38] <FlowRiser> thanks :D
[17:38] <FlowRiser> xnox: But why do you think, it is wrong to use C++ & GTK ?
[17:39] <xnox> FlowRiser: because GTK is a C toolkit for C and it implements it's own object model. gtkmm are C++ bindings with C++ objects.
[17:40] <xnox> using C implementations of objects in C++ is not sensible at all.
[17:40] <xnox> C++ & gtkmm is somewhat sensible
[17:43] <FlowRiser> xnox: Thanks allot! This is handy info, and the code makes sense to me now :)
[17:44] <FlowRiser> When i finish my greeter, how can i make it public ?
[17:44] <Manoj> #hackerrank