[01:14] <bluesabre> jjfrv8: try clicking on "current configuration" and then save
[02:35] <bluesabre> flocculant, jjfrv8, ochosi: uploaded a new release of xfpanel-switch to xubuntu-staging. For some reason it displays preinstalled templates twice there, but seems to work otherwise. Please give it a shot when you have a chance so I can upload to wily tomorrow :)
[02:36] <bluesabre> flocculant, jjfrv8, ochosi: release notes: https://launchpad.net/xfpanel-switch/1.0/1.0.1
[02:37] <bluesabre> need to get some sleep now.... night all!
[06:28] <flocculant> bluesabre: tried the updated xfpanel-switch ... saved it(it assumed it was a copy of xubuntu modern apparently) then changed my panel about, tried to restore my panel
[06:29] <flocculant> that didn't work - I ended up with a default panel at the top, with things I remove from default back again
[06:29] <flocculant> things I add not there
[06:30] <flocculant> but I no longer see the problems with closing dialogues and prompts
[06:40] <flocculant> knome: on the tracker, bugs specifically - what's triggering something not to count, because at least one is expired/won't fix but shows as something to do :)
[07:12] <Unit193> Logan: Re: #ubuntu.  I like you.
[07:14] <Logan> I like myself too
[07:35] <bluesabre> flocculant: can you try selecting "current configuration", then click save, change it up, and then restore?
[07:37] <flocculant> bluesabre: ok - that worked
[07:37] <flocculant> what you doing about this time of the day ... 
[07:37] <bluesabre> woke up to use the bathroom, made the mistake of looking at my laptop
[07:37] <bluesabre> :D
[07:37] <bluesabre> back to bed, bbabl
[07:38] <flocculant> ha ha ha 
[07:38] <bluesabre> oh, but what is happening with xfpanel-switch...
[07:38] <flocculant> go to bed :D
[07:39] <Unit193> ...bluesabre?
[07:39] <bluesabre> current config > save: save new config, others > duplicate config
[07:39] <bluesabre> last release didn't sort, so current was always the first item
[07:40] <bluesabre> back to bed :D
[07:55] <flocculant> shame it doesn't remember configs - have to reenter weather plugin configs
[09:54] <bluesabre> flocculant: it remembers everything stored in the normal panel config location... guessing the weather plugin stores it somewhere else
[09:55] <Unit193> panel/weather-29.rc
[10:02] <bluesabre> suppose we can extend panel-switch for the next release with that support :)
[10:03] <flocculant> bluesabre: ok - just thought I'd say what I saw :)
[10:03] <bluesabre> flocculant: much appreciated :)
[10:04] <bluesabre> this is quickly turning out to be a pretty solid xubuntu release
[10:04] <flocculant> yep sure is that :)
[10:06] <bluesabre> apport (2.18.1-0ubuntu1) wily; urgency=medium
[10:06] <bluesabre>   * etc/apport/crashdb.conf: Enable crash reports on Launchpad for wily.
[10:06] <bluesabre>     Really late, sorry about that!
[10:06] <bluesabre> nice
[10:07] <flocculant> one of the things I do pretty much at the start
[10:16] <bluesabre> flocculant: I'm going to go ahead and upload this xfpanel-switch release, and will try to take care of the few nagging bugs by the end of this weekend
[10:17] <flocculant> ok - works for me 
[10:18] <bluesabre> cool
[10:19] <bluesabre> or not
[10:19] <bluesabre> xfpanel-switch not in packageset
[10:19]  * bluesabre grumbles
[10:20] <knome> ehehehe
[10:20] <knome> :P
[10:20] <knome> about time to poke a packageset wizard?
[10:21] <bluesabre> i'll drop it into my ppa, poke micahg for an upload, and mail the DMB to get it added
[10:21] <bluesabre> hopefully micahg can sponsor shimmer-themes today too
[10:24] <flocculant> bluesabre: do bug 1385624 and bug 1332931 need to be on the tracker? 
[10:24] <knome> bluesabre, what about just asking people to add xfpanel-switch to our packageset?
[10:24] <knome> bluesabre, i can't imagine it being a biggie.
[10:25] <bluesabre> knome: can't, all requests have to go through dmb
[10:25] <bluesabre> flocculant: sure, but probably not going to be able to fix that
[10:25] <knome> ugh..
[10:25] <knome> there was that mailing list for it
[10:26] <flocculant> bluesabre: ok - I'll leave them on there then - just seemed a bit daft to track expired or 14.04 things
[10:26] <bluesabre> knome: yup
[10:26] <bluesabre> devel-permissions
[10:26] <bluesabre> writing the email now
[10:27] <knome> flocculant, what was the bug that was still showing up even if invalid?
[10:27] <flocculant> 1385624 - not invalid, marked won't fix/expired
[10:28]  * knome checks
[10:28] <knome> bug 1385624
[10:30] <knome> right, we aren't tracking that..
[10:30] <flocculant> so why is it on the tracker
[10:30] <bluesabre> knome: if micahg is not around, we can reach out to folks that have helped in the past to sponsor packages in https://launchpad.net/~bluesabre/+archive/ubuntu/sponsoring
[10:30] <knome> flocculant, i mean, we aren't tracking those statuses..
[10:30] <flocculant> oic :D
[10:30] <knome> do we want to let things that are expired disappear?
[10:31] <bluesabre> kiiiiinda
[10:31] <knome> i mean, that's on organic status after all
[10:31] <knome> but okay
[10:31] <knome> i'll hack that in
[10:32] <flocculant> another thing - if we've got bp for bugs - should we keep a 14.04 one that's seperate to wily (or x or y) 
[10:33] <flocculant> not huge issues ofc - but nevertheless the non wily ones show up on tracker
[10:33] <bluesabre> maybe have a parent bp xubuntu-bugs that links to current releases?
[10:33] <knome> hmm
[10:34] <flocculant> at the end of the day - adding to the bug bp is manual - so we could just not do it :)
[10:35] <knome> ok, so i'm just not catching those bugs at all to the tracker now
[10:35] <knome> with the newest change, that is
[10:35] <knome> will be live when the cron runs the next time
[10:36] <flocculant> now to stop QA showing on the tracker at all :D
[10:37] <bluesabre> Logan: if you are bored, got some easy sponsorships you can do in https://launchpad.net/~bluesabre/+archive/ubuntu/sponsoring
[10:37] <knome> huhu
[10:37] <bluesabre> :)
[11:11] <knome> flocculant, there we go
[11:25] <flocculant> knome: thanks :)
[11:26] <knome> no problem
[11:26] <knome> happy to tweak the tracker to fit our needs
[11:29] <flocculant> :)
[13:17] <jjfrv8> bluesabre, oic, current config b4 save. Any chance current config could be the default selection?
[13:17] <jjfrv8> Could be a gotcha, since two of us highly experienced guys made the same mistake :D
[15:38] <GridCube> slickymasterWork: i'd like to present you to MrTulias :)
[15:39] <GridCube> he has been translating to spanish for the past few releases and has recently been granted a psotion on the translator team
[15:45] <krytarik> GridCube: Ooh, lovely!
[15:45] <krytarik> Also, hi there, MrTulias.
[15:45] <MrTulias> Hi
[15:49] <knome> hello
[15:50] <slickymasterWork> Hi MrTulias, GridCube 
[15:50] <slickymasterWork> sorry, was afk due to work issues
[15:51] <slickymasterWork> MrTulias, as I'm not sure you've already saw it, or if you receive our m/l for that matter, let me provide you some links
[15:52] <slickymasterWork> https://lists.ubuntu.com/archives/xubuntu-devel/2015-September/010885.html
[15:52] <slickymasterWork> https://lists.ubuntu.com/archives/xubuntu-devel/2015-August/010863.html
[15:54] <slickymasterWork> https://lists.ubuntu.com/archives/xubuntu-devel/2015-July/010811.html
[15:55] <slickymasterWork> please feel free to ping me here if you have any doubts or if you need any specific info
[15:57] <MrTulias> Thanks. Yes, I get the message, I'm signed up to m / l
[15:58] <slickymasterWork> great 
[19:12] <flocculant> knome: if we assumed that when the new jenkins deal gets to work and that the output can be the same, could we add the results from that to the tracker
[19:13] <flocculant> previously there was at least rss feeds out from it https://jenkins.qa.ubuntu.com/view/Ubiquity/view/Xubuntu/
[19:13] <flocculant> just trying to think about "Methods of - reporting automated image testing results to -team"
[19:34] <knome> we can totally bring in the results
[19:53] <flocculant> let's hope that it's the same then :)
[21:50] <Unit193> C/index.xml:69: element abstract: validity error
[21:50] <Unit193> xi-pdf-files.xml:1: element section: validity error :
[21:54] <knome> what?
[21:57] <knome> that is totally outrageous
[23:24] <bluesabre> jjfrv8: yeah, going to fix that with the next release (which I hope to have this weekend)
[23:25] <bluesabre> micahg: if you get a chance, please upload shimmer-themes and xfpanel-switch in https://launchpad.net/~bluesabre/+archive/ubuntu/sponsoring
[23:35] <knome> i'm off, see you tomorrow or sth :)