[00:01] <bluesabre> nm
[00:01] <bluesabre> weekend finally here
[00:01] <knome> true
[00:01] <knome> any special plans?
[00:02] <bluesabre> nope
[00:02] <bluesabre> bug fixes, and finding some time to sleep
[00:02] <knome> hah :)
[00:29] <knome> bluesabre, ping, see #x
[00:36] <pleia2> knome: eep, social media for b2
[00:36]  * pleia2 gets to it
[00:36]  * knome hangs our lazily in the sofa, looking at pleia2 run all over social media
[00:36] <knome> *out
[00:37] <pleia2> kk
[00:37] <knome> i can tweet if you want though :P
[00:37] <knome> did we change the twitter password?
[00:38] <pleia2> no
[00:38] <knome> nvm
[00:38] <knome> i fail
[00:38] <pleia2> I'm logged in already
[00:38] <knome> kay
[00:38] <knome> thanks pleia2 
[00:39] <pleia2> all done
[00:39] <knome> 39 wallpaper submissions
[00:39] <knome> only have to pick 15%!
[00:41] <pleia2> should social media the contest over the weekend again
[00:42] <knome> i've socially mentioned it to a few people :P
[00:57] <knome> ok, time to go to bed
[00:57] <knome> ttyl
[00:58] <bluesabre> night knome
[09:36] <pavlushka> Q:  I never tried but is it possible to upgrade from 14.04 LTS to 16.04 LTS directly?
[09:37] <flocculant> pavlushka: try reading the b2 release notes
[09:42] <pavlushka> flocculant, I am talking about the final stable release, is it possible?
[09:43] <flocculant> if I could look forward 4 weeks I'd probably be more interested in the lottery numbers
[09:44] <flocculant> I would hope so - I can't imagine Canonical releasing with their OS un-upgradable
[09:46] <pavlushka> because some BD guy was telling that one has to upgrade from 14.04 to 16.04 through step by step using 14.10, then 15.04, then 15.10, then 16.04 LTS, that will ridiculous to no extent.
[09:47] <flocculant> no idea what a BD guy is - but that's rubbish
[09:48] <flocculant> and impossible in a supported environment as 2 of them are EOL 
[09:48] <pavlushka> Some Bangladeshi Ubuntu user.
[09:49] <pavlushka> Sorry "and impossible in a supported environment as 2 of them are EOL", I am not that technical.
[09:49] <flocculant> end of life
[09:49] <flocculant> there will be a direct upgrade lts to lts route at the end of April I would expect
[09:50] <flocculant> there are 3 supported versions out there, 12.04/14.04 and 15.10 - though for us just 14.04 and 15.10
[09:50] <pavlushka> thanks for the info's
[13:16] <pavlushka> How can I upload a po file to LP?
[13:16] <pavlushka> How can I upload a po file to LP?
[13:58] <bluesabre> pavlushka: either submit a bug report with it attached, or find the translations page for the project (for example,catfish https://translations.launchpad.net/catfish-search) and submit via the online editor
[13:59] <pavlushka> bluesabre, got it, thanks a million!
[17:52] <bluesabre> ochosi: marking the pidgin theme as postponed, we'll work on getting that in for 16.10 (along with the repackaging of elementary-* themes)
[17:52] <pavlushka> bluesabre, bug #1562338
[17:52] <pavlushka> bluesabre, bug #1562338
[17:54] <bluesabre> pavlushka: reassigned that to ubiquity-slideshow, I can't personally update that, but somebody else can
[17:55] <pavlushka> ok
[18:00] <bluesabre> flocculant, Unit193: postponing the xubuntu-core task for now... no progress for now
[18:00] <bluesabre> (I might recommend we just apply to be in ubuntu-cdimage and take a different route to core/base)
[18:01] <bluesabre> or
[18:01] <bluesabre> do we keep it in if we're targeting 16.04.1?
[18:01] <bluesabre> knome: blueprint master, thoughts?
[18:03] <Unit193> bluesabre: Hah, "for now".  You're funny!
[18:08] <flocculant> bluesabre: postpone it - see what happens for .1 
[18:08] <flocculant> Unit193: :)
[18:08] <Unit193> Or for 17.04? :P
[18:08] <Unit193> bluesabre: Oh, any thoughts on the future of packages in extras?
[18:09] <bluesabre> Unit193: I'm still in favor of getting them into the archive
[18:09] <bluesabre> flocculant: alrighty
[18:10] <flocculant> bluesabre: seems the most sensible course - then we can move to .2/.3/.4.17.04 in easy steps :p
[18:10] <bluesabre> indeed
[18:21] <bluesabre> flocculant: any high-priority stuff you need me to look at?
[18:21] <flocculant> be good if blueman fix was simple
[18:22] <flocculant> thought that was in hand upstream though
[18:23] <bluesabre> doesn't seem to happen if there is some bluetooth hardware on the actual machine
[18:23] <flocculant> indeed
[18:23] <flocculant> so I get it everywhere ... 
[18:23] <bluesabre> ha
[18:24] <flocculant> bug 1513590
[18:24] <flocculant> is odd
[18:26] <flocculant> either you can or you can't delete something - being able to make something deletable by moving the entry up or down seems not what we'd want
[18:26] <bluesabre> added a comment
[18:27] <flocculant> so did I :p
[18:28] <bluesabre> in that case, you're just deleting the local one, the system one would remain and be visible, no?
[18:29] <bluesabre> it's deleteable then because it is no longer the system launcher
[18:30] <flocculant> mmm
[18:30] <flocculant> so it doesn't delete - but asks all the stuff it would if you were going to delete it
[18:32] <flocculant> but cool - can mark it invalid or something 
[18:33] <bluesabre> probably mostly semantics
[18:34] <flocculant> bug 1402036
[18:34] <bluesabre> in alacarte, it's probably "delete" that hides, but that should really be "hide" I'd think, makes it clearer that its non-destructive
[18:34] <flocculant> yea
[18:34] <bluesabre> dang
[18:34] <bluesabre> the same fix in catfish would be good for mugshot there
[18:35] <bluesabre> but we're all frozen now
[18:35] <flocculant> but not a bug fix? 
[18:35] <bluesabre> maybe
[18:35] <bluesabre> it's a rewrite
[18:35] <bluesabre> in a lot of ways
[18:35] <flocculant> oh right 
[18:35] <bluesabre> for that particular bit
[18:35] <bluesabre> using pkexec
[18:35] <flocculant> which fixes a bug :p
[18:35] <flocculant> yea
[18:35] <bluesabre> :D
[18:36] <bluesabre> I'll get that together so you can kick the tires
[18:36] <flocculant> ok - wfm :)
[18:38] <flocculant> bluesabre: can't think of any other major things 
[18:39] <flocculant> I still get the usb3 remount on eject - but that'll turn up one day I guess
[18:44] <flocculant> bluesabre: I can't actually confirm that mugshot bug 
[18:46] <flocculant> and I assume that trusty would have the trusty-updates version now
[18:49] <flocculant> aah right - so I DID confirm dkessel's 1511979 a while back- that's with the same version I have now
[18:49] <flocculant> but - it appears to work fine now
[18:50] <flocculant> oh forget what I said - didn't read daniel's properly
[18:53] <flocculant> so it still is an issue :)
[18:53]  * flocculant wanders off to lie down again
[18:56] <bluesabre> lp 1511979
[18:56] <bluesabre> ah, gotcha
[20:03] <knome> bluesabre, keep the item in th blueprints, as it's still active for 16.04
[20:04] <knome> bluesabre, we never really tracked off-release work items sensibly, maybe we should have one "ongoing" blueprint we keep on updating and attach to all release umbrellas
[20:05] <Unit193> Would think things could get more easily lost there.
[20:06] <knome> why?
[20:06] <knome> they would still show up in the tracker
[20:06] <knome> it would be just something that was attached to the next umbrella, then next umbrella...
[20:16] <bluesabre> I wouldn't be opposed
[20:26] <flocculant> wouldn't it make sense to have a 16.04.1 attached to 16.10 or whatever the point release is during the cycle of? 
[20:44] <knome> flocculant, that's one option too