[06:43] <ochosi> morning everyone
[06:46] <elfy> morning ochosi 
[06:47] <ochosi> good good, busy bee, but good
[09:59] <slickymasterWork> ochosi, in a default 12.04 this is what I got at startup, running tail .config/xfce4/xfconf/xfce-perchannel-xml/xfce4-panel.xml -> http://paste.ubuntu.com/7835132/
[09:59] <slickymasterWork> ochosi: do you think that it could be some missing?
[10:01]  * skellat goes back to bed as he realizes the meeting is **next week**
[10:02] <slickymasterWork> ochosi: also out of dpkg -l indicator -* ->http://paste.ubuntu.com/7835170/
[10:32] <ochosi> slickymasterWork: well from my memory i'd say you have to remove the -gtk2 indicators
[10:32] <ochosi> have you tried anything yet to get them running again in 14.04?
[10:33] <slickymasterWork> ochosi: still updating the box to then be able to run the upgrade
[10:37] <slickymasterWork> upgrading now
[10:39] <ochosi> okeydokey
[10:39] <ochosi> just document every step until you get the indicators back :)
[10:39] <ochosi> here's a guess:
[10:40] <ochosi> 1) sudo apt-get remove indicator-*-gtk2
[10:40] <ochosi> 2) remove the autostart entries for individual indicators from settings-manager > sessions and startup > application autostart
[10:40] <ochosi> 3) reboot the machine
[10:40] <ochosi> 4) hope for the best
[10:40] <ochosi> :)
[10:41] <slickymasterWork> lol, I'll make sure that point 4 will be present in the list ;)
[10:57] <ochosi> bbabl
[12:37] <ochosi> morning bluesabre 
[12:37] <bluesabre> morning ochosi
[12:38] <bluesabre> going through SRU bugs for menulibre to bug you guys to test them ;)
[12:39] <ochosi> heh
[12:40] <ochosi> i managed to snuck in x-d-s at the very last minute to 14.04.1
[12:40] <ochosi> (well, without a respin, that is)
[12:40] <ochosi> today i need to focus on work more
[12:40] <bluesabre> good job
[12:40] <bluesabre> :)
[12:49] <bluesabre> ok, so if anybody is around and would like to do some SRU verification for https://bugs.launchpad.net/ubuntu/trusty/+source/menulibre/+bug/1323405 , that would be awesome ;)
[12:49] <bluesabre> The remaining bugs need verification in trusty-proposed:
[12:49] <bluesabre> https://bugs.launchpad.net/menulibre/+bug/1313276
[12:50] <bluesabre> https://bugs.launchpad.net/ubuntu/+source/menulibre/+bug/1306999
[12:50] <bluesabre> https://bugs.launchpad.net/menulibre/+bug/1318209
[12:50] <bluesabre> https://bugs.launchpad.net/menulibre/+bug/1313586
[12:50] <bluesabre> https://bugs.launchpad.net/menulibre/+bug/1214815
[12:51] <bluesabre> Let me know if you need any help or more information, several of these are pretty straight-forward and quick to complete
[13:57] <slickymasterWork> ochosi: after upgrading the output of tail .config/xfce4/xfconf/xfce-perchannel-xml/xfce4-panel.xml -> http://paste.ubuntu.com/7836249/
[13:57] <slickymasterWork> and the output of dpkg -l indicator-* ->http://paste.ubuntu.com/7836239/
[13:57] <ochosi> yeah
[13:57] <ochosi> so i guess you're not seeing any indicators now, right?
[13:58] <slickymasterWork> no, I'm seeing indicators
[13:58] <ochosi> oh, you are?
[13:58] <ochosi> so they're simply working?
[13:58] <ochosi> that's a nice surprise
[13:58] <slickymasterWork> bluetooth, sound and network
[13:59] <ochosi> i guess the problem here was that i wasn't doing an LTS->LTS upgrade then (had 13.04, went to 13.10)
[13:59] <ochosi> bluetooth should be a trayicon i think
[13:59] <slickymasterWork> re the power one I'm not able to say anything as this is on a desktop
[13:59] <slickymasterWork> no, it's not a tray icon
[14:00] <ochosi> right
[14:00] <slickymasterWork> if I remoce indicator plugin from the panel it also disappears 
[14:00] <slickymasterWork> *remove
[14:00] <ochosi> fun, for me the bluetooth thingy is a trayicon :)
[14:00] <slickymasterWork> over here it's in the indicator plugin 
[14:01] <ochosi> right, so if everything works out of the box with indicators, there's no need for that paragraph
[14:01] <slickymasterWork> so, with these results what to do with that item in the list 
[14:02] <ochosi> other than maybe saying that ppl can install indicator-power and indicator-messages
[14:02] <slickymasterWork> lol, I'll remove it then
[14:02] <ochosi> or wait, that got pulled for you automatically too?
[14:03] <slickymasterWork> re indicator power it's ticked in sessions and starup, but since this is on a laptop won't get showed in the panel 
[14:03] <ochosi> sure, but indicator-power wasn't installed in 12.04 by default
[14:03] <ochosi> that's what i meant
[14:03] <slickymasterWork> give a second and I'll conform that
[14:04] <slickymasterWork> *confirm
[14:05] <slickymasterWork> exactly ochosi, it wasn't
[14:06] <slickymasterWork> so, I'm thinking in rewritting that paragraph just pointing out that ppl can install indicator-power and indicator-messages
[14:06] <ochosi> well if it got pulled in automatically, then everything is fine
[14:06] <slickymasterWork> what do you think?
[14:06] <ochosi> no need to point out anything in that case
[14:06] <slickymasterWork> it did in this setup
[14:06] <ochosi> it was a clean 12.04 install, right?
[14:07] <slickymasterWork> yes, 12.04.4
[14:07] <slickymasterWork> the image is from 11-04-2014
[14:08] <ochosi> ok, then skip the indicators paragraph as a whole
[14:08] <ochosi> if it works, why mention it
[15:06] <slickymasterWork> sorry ochosi, got a call from my boss
[15:06] <slickymasterWork> :P
[15:07] <ochosi> no worries
[15:12] <kean> Hi everyone. Is there a place where I can ask about problems I'm experiencing when trying to build a patched package for the first time?
[15:16] <ochosi> kean: is the package directly related to xubuntu/xfce?
[15:18] <kean> ochosi: Yes, at least as far as I can tell. You may remember I was here last week regarding a bug in light-locker-settings I'd like to fix, but haven't had time to do much since.
[15:26] <ochosi> ah
[15:26] <ochosi> right
[15:26] <ochosi> so you'er building a light-locker-settings package?
[15:26] <ochosi> you're
[15:27] <ochosi> kean: ^
[15:28] <kean> ochosi: I'm trying to. This is what I did so far, following the Ubuntu bug fixing guideline: bzr branch lp:light-locker-settings, followed by a simple change in light-locker-settings.py and bzr bd -- -S -us -uc
[15:28] <ochosi> humm, i wouldnt do that tbh
[15:28] <ochosi> 1) you can simply run lls, because it's python
[15:28] <ochosi> so not sure why you need the package
[15:29] <ochosi> 2) i'd go for the easy variant if i really had to build a package, which is the one described e.g. here: http://pascal.nextrem.ch/2010/05/06/build-ubuntudebian-packages-from-source-and-apply-a-patch/
[15:29] <kean> dpkg-source then tells me: "aborting due to unexpected upstream changes", listing not only the file I changed, but numerous others as well.
[15:29] <ochosi> (couldnt find the source in the ubuntu wiki for that, but it's pretty much the same)
[15:29] <ochosi> sry, i'm not really into packaging, can't help you much with that
[15:30] <kean> ochosi: I wanted to build a package because I have no experience with that, and I wanted to make sure that my patch doesn't somehow break packaging, unlikely as it may seem.
[15:32] <kean> dpkg-buildpackage gives me the same error when I try to run it on the bzr branch. It works with what apt-get source gets me, though
[15:33] <ochosi> right
[15:33] <ochosi> i'd try to just verify that the fix works in a first step and attach it to a bugreport
[15:33] <ochosi> if it works for everyone we can still figure out the packaging
[15:33]  * ochosi forgot what the bug was actually
[15:34] <kean> It's LP #1306917: https://bugs.launchpad.net/ubuntu/+source/light-locker-settings/+bug/1306917
[15:34] <ochosi> ah right
[15:36] <kean> ochosi: What's the preferred way of suggesting a patch? Upload a plain patch file, or make a branch and propose a merge?
[15:37] <ochosi> the latter
[15:38] <kean> So it's okay if I just change light-locker-settings.py and not any of the debian/ files?
[15:38] <ochosi> yeah, let's start with that
[15:39] <kean> Okay, please give me a few minutes.
[15:42] <ochosi> sorry, gotta go
[15:43] <ochosi> kean: feel free to also bug bluesabre about this if he's around and i'm not
[15:43] <ochosi> but yeah, just start with the MR and we'll review
[15:44] <ochosi> mmm, 14.04.1 is spinning up (lubuntu is the first it seems)
[15:44] <ochosi> bbl
[15:47] <kean> ochosi: Thanks for your help. I created a merge proposal now. Please let me know what you think of it. I'm happy to receive guidance, especially since I'm new to launchpad and (x)ubuntu development.
[15:50] <kean> I'm offline for a few minutes.
[15:55] <kean> Back again.
[16:05] <slickymasterWork> ok ochosi, currently waiting for review: http://xubuntu.org/?p=2548 and http://xubuntu.org/?p=2581
[16:29] <elfy> bluesabre: after the day has calmed down a bit for me I'll try and verify those SRU bugs - I'll ping team with those I don't manage to crack 
[16:29] <elfy> ochosi: unless it's too late to get them for .1 ?
[16:43] <bluesabre> elfy, thanks
[16:44] <elfy> bluesabre: try and ping me with those if you remember - I only know cos slickymasterWork told me eslewhere :)
[16:45]  * elfy just got in from work
[16:46] <bluesabre> ah
[16:46] <bluesabre> elfy: http://paste.ubuntu.com/7837132/
[16:46] <elfy> yep - caught up now :)
[16:46] <elfy> got the bugs in a window 
[16:52] <bluesabre> great, thanks
[16:52] <bluesabre> let me know if you have any questions
[16:52] <elfy> I will - it'll be a couple of hours I guess
[17:22] <kean> bluesabre: I've been trying to build a source package for light-locker-settings from the bazaar branch, but bzr bd -S fails with dpkg-source saying "aborting due to unexpected upstream changes". Could you help me, a newcomer, learn why this is and how to resolve it?
[17:23] <bluesabre> to build the source package, you'll need to create a quilt patch
[17:23] <bluesabre> one sec, and I'll help you through that
[17:25] <kean> Thanks. :)
[17:26] <bluesabre> kean: have a look at this to set up your quilt env, https://wiki.debian.org/UsingQuilt
[17:27] <kean> From what I learned so far, I think I understand that I'd need to create a quilt patch if I wanted to introduce a debian/ubuntu specific change. In this case, as a first step, I tried to build the latest launchpad branch without any modifications of my own. Shouldn't it build finde then?
[17:31] <kean> bluesabre: Did that, thanks. It just occured to me that maybe branching lp:light-locker-settings might be where I went wrong. I assume lp:lls is what could be considered "upstream", while the ubuntu packages should be built from ubuntu:lls?
[17:32] <bluesabre> kean: that's correct.
[17:33] <bluesabre> and we already have a single patch in there, so you just need to
[17:33] <bluesabre> 1. pull
[17:33] <bluesabre> 2. quilt push -a
[17:33] <kean> bluesabre: I see. Please excuse my confusion, but why does lp:lss have a debian/ directory then?
[17:33] <bluesabre> It's native packaging since lls is native to ubuntu
[17:34] <kean> What's the distinction between lp:lss and ubuntu:lls then?
[17:35] <bluesabre> ubuntu:lls is the current release in ubuntu
[17:36] <bluesabre> lp:lls is upstream trunk
[17:36] <bluesabre> at times, they may be identical, but lp:lls is almost always more up-to-date
[17:38] <kean> bluesabre: Thanks, that makes more sense now. So, I submitted a merge proposal to lp:lls earlier, where I changed only light-locker-settings.py, and none of the debian/ files. Is that the correct way in this case?
[17:41] <bluesabre> yes, we can merge that from there to fix upstream
[17:42]  * bluesabre needs to fix some bugs with lls soon
[17:44] <bluesabre> ... and several other things
[17:45] <kean> I hope I don't overstrain your patience, but what I wanted to ask was whether this would be considered the ideal way of dealing with this situation, or whether I should have done things differently, or additionally. I'm asking because I'm new to this and would like to contribute more to (x)ubuntu, and do so in an effective manner.
[17:46] <bluesabre> Yeah, offering a patch in that manner is generally preferred.
[17:47] <bluesabre> If you go to the top of the bug report, you can click "Link a related branch" to make it more visible as well (I think that should be visible for everyone)
[17:49] <bluesabre> With most of our projects (and a lot of xfce even), there are only a few (1-2, 3 if lucky) people maintaining them, so patches might sit around for a while
[17:50] <bluesabre> But offering merge requests like that make sure we do find them, when we do get around to them :)
[17:52] <kean> Okay, linked the branch now. Thanks for letting me known, I wouldn't have realized there was that possibility otherwise. I just assumed the package maintainers would be notified by mail or something as soon as a merge proposal is created.
[17:52] <bluesabre> Thanks!
[17:53] <bluesabre> Also, we have lots of different areas where we need contributing, in case you're interested -- http://xubuntu.org/contribute/ outlines our focus areas
[17:53] <kean> Thank you for guiding me through this. :)
[17:54] <bluesabre> np
[17:57] <kean> I surely am interested, thanks for that link. However, I planned on seeing whether I could help with two other bugs that affect me directly.
[17:57] <bluesabre> Sure thing, that's always the best place to start
[17:58] <kean> Oh, one more thing: in many bug reports I see people linking PPA packages in order to see whether affected people have their issues resolved by a patch. Is that usually done by the one who proposes a patch, i.e. me, or by the maintainers?
[18:00] <bluesabre> Usually by the maintainers.  We'll roll in the proposed fix to see if that resolves the issue, and then verify with others
[18:04] <kean> I see, thanks again.
[18:16] <kean> I just tried whether I could change the bug status in lls from New to Confirmed, and to my surprise it seemed to work. Sorry if that disturbed you, really didn't expect it to go through. I expected that only people with appropriate permissions could do that. Is anyone able to change the bug statuses by default?
[23:21] <ochosi> 14.04.1 xubuntu build has been added it seems