[00:10] <Nairwolf> floculant : how can I verify if this bug affects me ? https://bugs.launchpad.net/ubuntu/+source/xubuntu-artwork/+bug/1548647
[00:45] <krytarik> Nairwolf: https://kdeonlinux.files.wordpress.com/2015/03/libreoffice3.png  vs.  http://xubuntu.org/wp-content/uploads/2015/07/lo-writer.png
[00:51] <Nairwolf> oh, thank you, the first one is much nicer ;)
[00:52] <Nairwolf> I hope it will be changed ;)
[00:54] <knome> actually, the latter one is what you should have.
[00:56] <bluesabre> :D
[01:00] <Nairwolf> i've shut down my test-computer, but it seems that I had the second one
[01:01] <Nairwolf> why this theme ? 
[01:01] <knome> there are actually a few things that are different in those two screenshots, so there is no clear answer
[01:09] <Nairwolf> ok
[01:19] <bluesabre> gnome-software seems to do *some* stuff now
[01:19] <knome> :)
[01:19] <knome> branau, hello
[01:19] <branau> Hey knome! How goes it?
[01:19] <knome> not bad
[01:20] <knome> to answer to your email:
[01:20] <knome> as i said, my original intention was to work on the UI side of things
[01:20] <knome> then i noticed that the uploader on your version had a possibility to upload from an URL
[01:20] <knome> plus the regular metadata stuff wordpress offers
[01:21] <knome> i quickly checked if there was an option to be able to remove those, but there didn't seem to be a trivial choice 
[01:21] <knome> i mean we only want the user to upload a file, without touching it's title, or too much else
[01:22] <branau> Yeah, I thought you wanted me to use the built-in WordPress uploader, at least that was what I had understood
[01:22] <knome> yeah; my code uses wp to handle the upload too
[01:22] <knome> i think this is the old widget though
[01:22] <knome> which turned out to be perfect for us :)
[01:22] <branau> Gotcha, I must've misunderstood what you meant
[01:22] <knome> less dependencies too!
[01:23] <knome> i mean your version was fine too - it just had that URL thing, and other options we actually didn't want to show the user if possible
[01:23] <knome> i totally didn't mean to snatch the work from you...
[01:24] <knome> at the point i had the upload thing done, and having heard you say that you didn't touch the voting stuff yet, i quickly dropped that in too
[01:24] <branau> It's all good, I should've clarified before jumping into it
[01:24] <knome> the version you got actually saves all the votes in a single option; i've now updated the tarball into a version where each image has its own metadata with votes
[01:25] <knome> (and licence/attribution in their own meta fields instead of the "content" field, so people can't mess with it now)
[01:25] <branau> Sounds good, so you want me to upload that plugin so we can test it then=
[01:25] <branau> ?*
[01:25] <knome> it's still on temp.knome.fi
[01:26] <branau> Ah, same url as before?
[01:26] <knome> i've actually sent a request to the canonical IS to set up a new subdomain contest.xubuntu.org
[01:26] <knome> so once we have that linked, i'll push the code to the server and set it up for further testing
[01:26] <branau> Ah, sounds good
[01:26] <knome> (i should also push the code to a repository under xubuntu-website in launchpad)
[10:55] <bluesabre> Assuming we're leaving our monospace font as DejaVu, this should be it for the changes to desktop branches
[10:55] <bluesabre> https://code.launchpad.net/~bluesabre/xubuntu-default-settings/noto-sans
[10:55] <bluesabre> https://code.launchpad.net/~bluesabre/ubuntu-seeds/xubuntu.xenial.noto-sans
[11:25] <SwissBot> feed xubuntu-default-settings had 8 updates, showing the latest 3
[11:28] <knome> bluesabre, well done
[12:25] <bluesabre> flocculant: new catfish-daily package building in https://code.launchpad.net/~catfish-search/+archive/ubuntu/ppa - fixed
[12:25] <bluesabre> https://bugs.launchpad.net/catfish-search/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=FIXCOMMITTED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branche
[12:25] <bluesabre> s.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search
[12:25] <knome> huhu
[12:26] <bluesabre> that failed
[12:26] <bluesabre> :D
[12:26]  * knome grants bluesabre the sherlock of the day award
[12:26] <bluesabre> huzzahhhh
[12:26] <bluesabre> flocculant: better link https://bugs.launchpad.net/catfish-search/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=FIXCOMMITTED
[12:28] <bluesabre> with the recent annoyances in clutter, might set parole
[12:29] <bluesabre> 's default back to xv and add some patches to make that better
[12:29]  * bluesabre can't seem to type today
[12:29] <bluesabre> will have to figure something out with mugshot :\
[12:31] <knome> ok everybody, likely going to break dev.xubuntu.org for a sec
[12:31] <ochosi> bluesabre: what's so broken with clutter in 16.04?
[12:31] <ochosi> (i presume totem/video still works as always)
[12:32] <bluesabre> ochosi: API change in ClutterGst... the old video sink was dropped and the new one is a pain to integrate
[12:32] <bluesabre> ochosi: the old one was a clutter actor that could be easily embedded, the new one, not so much
[12:32] <bluesabre> ochosi: I'm also apparently the only person using the API in python
[12:33] <bluesabre> no code examples >.<
[12:34] <bluesabre> will hop on one of those channels trying to get support sometime soon, haven't quite had time lately
[12:35] <bluesabre> so to summarize... in mugshot the video appears white but a photo can technically be taken
[12:35] <bluesabre> and in parole, I have code that makes it do something now, but it just pops the video window out of the player
[12:41] <flocculant> bluesabre: what a good chap you are :)
[12:47] <flocculant> bluesabre: still got issues with images and laptops - which probably is actually useful - not loads of rebuilds going on :D
[12:48] <flocculant> I've managed to jury rig a laptop up so can at least test the installer doesn't crash prior to deciding to release or not
[12:49] <ochosi> bluesabre: that sounds really meh
[12:49] <flocculant> I'd likely still release anyway - it can install on laptop as long as remove battery/use ac
[12:49] <flocculant> hi ochosi 
[12:54] <bluesabre> flocculant: funnnn
[12:55] <bluesabre> flocculant: used gnome-software any lately?
[12:55] <bluesabre> it does some stuff now
[12:55] <bluesabre> and last night it consumed all of my ram after closing it
[12:56] <bluesabre> :D
[12:56] <bluesabre> going to try to reproduce tonight, then file a bug if I can
[12:57] <bluesabre> ochosi: yes, especially since I moved to clutter with the idea that things should be stable and supported and easy to maintain
[12:57] <bluesabre> (pretty much none of those ideals came true)
[12:59] <flocculant> bluesabre: nope - not used it lately
[12:59] <bluesabre> still doesn't list uninstalled apps (for me)
[13:00] <flocculant> same
[13:00] <bluesabre> but the updater functionality is starting to work, and existing apps can be launched now
[13:00] <flocculant> really
[13:01] <flocculant> it's telling me there are updates when there aren't
[13:01] <bluesabre> *starting*
[13:01] <flocculant> ha ha ha 
[13:01] <flocculant> in as much as it probably could :)
[13:02] <bluesabre> I think that might be related to the "Restart & Install" button at the top of mine
[13:02] <bluesabre> scared to think of what that might do if it does not currently work
[13:02] <flocculant> I dare you :p
[13:02] <bluesabre> I'll do it in a vm later ;)
[13:02] <flocculant> ha ha ha 
[13:03] <flocculant> I see you are sensible then :D
[13:03] <bluesabre> only a bit
[13:03] <flocculant> :)
[13:05] <flocculant> bluesabre: I assume the catfish changes are in the ppa? I tested the click not working properly one I reported - that appears to work now, so I hope so :)
[13:07] <flocculant> right - I'm off again - bbl
[13:08] <bluesabre> flocculant: yes, the "catfish-daily" package
[13:55] <knome> bluesabre, have you ever used dokuwiki with mysql?
[13:58] <bluesabre> knome, nope
[13:58] <knome> mhm
[13:58] <bluesabre> Time for work, bbl
[13:58] <knome> i don't remember if i have, i might...
[16:27] <Nairwolf> hi flocculant, I've received your message
[16:28] <Nairwolf> I would like to help more, so tell me what I'm supposed to do ;)
[16:30] <flocculant> Nairwolf: you read the QA dev docs? generally just carry on as you are for the time being - you're doing fine
[16:31] <flocculant> assuming you're about still in May then we can look at getting you to do more for sure
[16:46] <Nairwolf> flocculant: I need to admit, I'm often lost with all links to deal with (docs.xubuntu.org, ubuntu wiki, launchpad)
[16:46] <flocculant> :D
[16:47] <flocculant> for QA you need one :)
[16:47] <flocculant> http://docs.xubuntu.org/contributors/ 
[16:53] <Nairwolf> ok !
[16:53] <Nairwolf> I'm gonna read that
[16:53] <Nairwolf> thanks
[16:53] <flocculant> 3 of the chapters are qa
[16:53] <Nairwolf> I need to do some stuff right now, maybe I'm going to ask some questions later
[16:53] <Nairwolf> yes, I've seen that
[17:17] <Nairwolf> oh, I wasn't connected, what was my last message ? 
[17:17] <Nairwolf>  I've just discovered that : https://trello.com/b/IV66JCHl/xubuntu-qa
[17:17] <Nairwolf> what does mean "Priority 5" ? 
[17:24] <flocculant> it';s the 5th time it was going to get called
[17:26] <Nairwolf> what is "it" ? 
[17:26] <flocculant> don't really use that anymore - not likely to make it into the yogic yinepu cycle
[17:27] <Nairwolf> Can I join this team or do I need to show my work, before ? 
[17:27] <Nairwolf> https://launchpad.net/~xubuntu-testers
[17:28] <flocculant> you can join that - it's open team 
[17:29] <Nairwolf> okay, what are the implications ? Will I receive some mails ? 
[17:29] <flocculant> some - not many 
[17:30] <Nairwolf> ok, ok, I will see
[18:54] <flocculant> bluesabre: I think I asked this before - lost in the logs of time though ... why do we have evince and evince-gtk?
[19:21] <Unit193> flocculant: evince-gtk is a transitional dummy package back to evince now.
[19:56] <knome> Unit193, since you mentioned it, navigation on dev. and wiki. should now work seamlessly
[19:56] <knome> (seamlessly meaning that if you have dev. open and go to wiki. (or the other way), your irc tab will be reset)
[19:57] <knome> but maybe the irc tab should default to opening in _blank anyway
[20:03] <Unit193> Great, nice.
[20:23] <flocculant> knome: can I leave the website release doodah for tomorrow to you? 
[20:24] <flocculant> bluesabre: draft wiki is https://wiki.ubuntu.com/XenialXerus/Beta1/Xubuntu - if you could look at the bug fix/enhancement thing that'd be nice :)
[21:07] <knome> is there something we specifically like to highlight on the announcement?
[21:08] <knome> maybe gmb/no media manager?
[21:08] <knome> and noto
[21:12] <flocculant> sounds like the sort of things which should be on it 
[21:13] <knome> https://xubuntu.org/?p=3731&preview=true
[21:13] <flocculant> not sure there are any other major changes from 15.10
[21:13] <flocculant> knome: thanks - looks just how I thought it would :)
[21:14] <knome> i checked http://dev.xubuntu.org/#tab-timeline and searched for "in development"
[21:14] <knome> and no, i didn't find anything specific
[21:16] <knome> did a few updates
[21:17] <flocculant> yep
[21:17] <knome> do we want to mention the beta on the footer?
[21:17] <knome> like we did before with 15.10
[21:18] <knome> and
[21:18] <knome>  This is the first beta towards the final release in October.
[21:18] <knome> not
[21:18] <flocculant> yea I think so 
[21:18] <knome> s/15.10/16.04/ too :P
[21:18] <flocculant> mmm
[21:18] <flocculant> actually not so sure
[21:18] <knome> about mentioning on footer?
[21:19] <flocculant> yea
[21:19] <knome> then the beta release won't be visible on the front page at all
[21:19] <flocculant> as you know on Friday it's out of date
[21:19] <knome> (not saying this is unwanted, just saying)
[21:19] <flocculant> why is it not on the front page? 
[21:20] <knome> the blog articles we show only show "articles", eg. not news
[21:20] <flocculant> ok
[21:20] <knome> that's intentional, because we don't want it to be littered with "15.10 b1 out", "15.10 b2 out", etc...
[21:20] <knome> (and because the latest real releases are highlighted already)
[21:21] <flocculant> I'm not convinced that advertising b1 is what we should do tbh - I'd rather people asked and got pointed at daily
[21:21] <knome> ack
[21:21] <knome> i was just saying so that you are aware
[21:21] <flocculant> yea I understand that :)
[21:21] <knome> (and because we did the footer thing before)
[21:21] <flocculant> I think when we get to RC time we can do it 
[21:22] <knome> yeah
[21:22] <flocculant> yep - I've just been mulling it over as we started talking about it 
[21:22] <knome> :)
[21:22] <flocculant> given the lack of testing we *know* about - I don't want much to get into that install b1 and apt-get update it till April thing :)
[21:22] <knome> bug 1462445 ?
[21:23] <knome> bug 1515425 ?
[21:23] <knome> re: issues we might want to highlight
[21:25] <flocculant> yea I've got a list - the mousepad one isn't on it :D
[21:25] <knome> :)
[21:25] <flocculant> the other mousepad one is ;)
[21:25] <knome> hah
[21:25] <knome> i should tackle that *some day*
[21:25] <flocculant> :D
[21:25] <knome> but yeah, i think i should be around during the day enough tomorrow to take care of the website update
[21:25] <knome> if not, and you are, feel free to go push the publish button
[21:26] <flocculant> well - I'm driving the train with stgraber so ... 
[21:26] <knome> the announcement should be ready to go already considering the download link is correct
[21:26] <flocculant> yep
[21:26] <flocculant> he's apparentyl working pacific time - so it'll be later in the day I guess
[21:27] <knome> yeah, not EU-based
[21:27] <knome> we have guests afternoonish
[21:27] <flocculant> right 
[21:27] <knome> but i'm not completely tied to them
[21:27] <knome> i mean i can check the situation etc
[21:27] <flocculant> I just didn't want to find I had to write the website thing at the last minute :)
[21:28] <knome> sure
[21:28] <knome> tbh, this is all *so* much easier with the tracker now
[21:28] <knome> it isn't like "wait, what did we change" at all
[21:28] <flocculant> well I don't really use it for this much - I'm more interested in what bugs I see on the 2 trackers
[21:29] <flocculant> yea for sure :D
[21:29] <knome> yeah, sure
[21:29] <knome> but since the critical ones are likely to be tracked on the bugs blueprint...
[21:29] <knome> (there's one good reason to maintain it, since you were once wondering)
[21:29] <flocculant> generally - I've not been good lately 
[21:29] <knome> le sigh
[21:30] <knome> if IS would just get our subdomain ready, i could proceed with the wallpaper contest stuff
[21:30] <flocculant> :)
[21:30] <flocculant> \o/ 32 and 64 bit finally installed on a battery laden hardware
[21:33] <flocculant> knome: while back there was that blueman applet discussion where we were trying to work out what it affected
[21:33] <flocculant> seems to not affect 64bit on this laptop - but does on 32bit ... 
[21:36] <knome> "heh"
[21:58] <Nairwolf> when new daily build are done ? 
[21:59] <Nairwolf> is it programmed ? In order to know when I need to check with zsync
[21:59] <knome> always check
[21:59] <knome> there might be a manual rebuild
[21:59] <knome> usually not for dailies, but who knows.
[22:01] <Nairwolf> yes, but I wanted to say that I've checked few hours ago, and it wasn't updated. And flocculant told me at #xubuntu that it was updated. I wanted to know when automatic builds are done
[22:01] <knome> noonish UTC afaik
[22:02] <knome> flocculant, am i right?
[22:05] <flocculant> 10 am UTC for cron led builds
[22:06] <flocculant> milestone one's are whenever - our latest was when I kicked it off after ubiquity new landed
[22:07] <knome> i would still say better test every time; you never know what the 1337 people are up to.
[22:10] <bluesabre> knome: no noto yet, waiting until after b1 (so tomorrow night)
[22:10] <knome> aha
[22:11] <knome> done
[22:12] <bluesabre> Haven't reviewed the rest yet, on way home
[22:12] <knome> bluesabre, just that we don't forget, can you add a work item for droid->noto
[22:12] <bluesabre> Will do
[22:12] <knome> thanks
[22:13] <Nairwolf> knome: I can't run zsync everytinme ! Or I need to make it automatic ^^
[22:13] <knome> Nairwolf, why can't you?
[22:13] <Nairwolf> do you mean, why I can't run rsync for example every hour ? 
[22:14] <knome> well if you run a test every hour, you surely can run the zsync command once an hour too
[22:14] <knome> tbh, you likely need to run it only once per test session
[22:14] <knome> and that's in most cases fine
[22:14] <Nairwolf> I can't run a test every hour...
[22:15] <knome> so why would you need to run the zsync every hour then?
[22:15] <knome> just run it every time before you do a test.
[22:15] <Nairwolf> because you told me that I have to test everytime ^^
[22:16] <Nairwolf> obviously, before I launch a test, I update the iso
[22:16] <knome> yes, every time you run a test...
[22:16] <knome> i didn't mean (or say) "every hour"
[22:17] <Nairwolf> ok, I think I misunderstood you
[22:19] <Nairwolf> maybe my english is not perfect. I've checked if there is a new version few hours ago, and there wasn't. The iso wasn't updated, so I was saying to myself (no need to test today). And then, few minutes ago, I've learnt that there is a new update. That's why I wanted to know when the build are done. That's all. 
[22:19] <knome> as said, the *automatic* updates happen noonish UTC, but there can be other manual updates
[22:20] <knome> so that's why it makes sense to test if the ISO has changed every time you are about to run a test
[22:22] <Nairwolf> yes, you right. But tonight I've some freetime, and if flocculant didn't tell me that there is a new update, I wouldn't have tested it right now. 
[22:22] <knome> sure
[22:22] <Nairwolf> But, that's okay, thank you for telling me the hour. 
[22:22] <knome> that's why we have these communication channels
[22:22] <Nairwolf> indeed ;)
[22:29] <Nairwolf> thank you anyway
[22:29] <flocculant> Nairwolf: for when we are doing milestone tests the quickest way to see if we have a rebuild is check the version listed on the tracker
[22:30] <Nairwolf> ok, flocculant
[22:30] <flocculant> it now says 201602224, if I did a rebuild now it would be 20160224.1
[22:30] <flocculant> for dailies - the time is ~10.00UTC
[22:30] <flocculant> unless it's not building - always check the date :)
[22:32] <Nairwolf> thank you
[22:32] <flocculant> welcome
[22:32] <Nairwolf> I've the same bug as yesterday "the creation of swap space in partition #5 of SCI3 failed" before the time zone window...
[22:33] <flocculant> Nairwolf: it's useful if you made note of things you've needed to ask about - so we can add information 
[22:36] <Nairwolf> sorry, maybe I don't have understood again... 
[22:36] <Nairwolf> It's during ubiquity, how can I get some information (like traceback ?)
[22:41] <Nairwolf> I don't really know which information I need to add
[22:44] <flocculant> Nairwolf: report bug 990744 on the tracker against the testcase you followed
[22:48] <Nairwolf> thank you flocculant, it seems to be this bug, you right !
[22:48] <Nairwolf> I was starting to write a bug, I will just write a comment. Thank you
[22:49] <flocculant> no need to comment - you can click affects me at the top though
[22:49] <flocculant> important you get it on the tracker - when I do release notes I refer to the tracker for bugs people have seen
[22:49] <Nairwolf> yes, but I would like to add some information
[22:49] <Nairwolf> ok
[22:52] <Nairwolf> that's done
[22:52] <flocculant> thanks 
[22:52] <flocculant> time for me to wander off for a while - night all
[22:52] <Nairwolf> good night ;)
[22:58] <Nairwolf> which is weird is I had the same issue yesterday, and I succeded to install the iso. Today, I can't ! 
[22:58] <Nairwolf> I'm still stuck with this bug