[02:29] <bluesabre> flocculant: updated the pad
[02:31] <Unit193> flocculant: Now getting hit by LP 1560459 too.
[02:51] <Unit193> flocculant: ...So using the workaround for that bug, install works.  Not sure if bug fixed or that workaround just works for that too. >_>
[03:11] <bluesabre> knome: added a bit to the cloud article, not sure what else we need there unless we want team commentary on these posts
[03:12] <bluesabre> like
[03:13] <bluesabre> Simon (XPL): "I really like how Spotify plays music, better than my old tape deck of 80s mix tapes"
[03:31] <bluesabre> knome: confirmed that docs seem good now
[03:32] <bluesabre> I'll wait until morning, then reach out to -devel and upload
[03:32] <bluesabre> night all
[03:32] <Unit193> G'night.
[07:49] <flocculant> Unit193: I'd not say the existence of a cli workround to fix the gui update tool counts as fixed :p
[07:50] <Unit193> Right, though not sure if it's the workaround that helped or ubiquity was fixed, and broken differently. :P
[07:50] <flocculant> no idea - not looked since Saturday :)
[07:50] <Unit193> Sure, sure.  And at this point too late anyway, I'd think.
[07:51] <flocculant> who knows - given that the images are all getting marked as critical fails - I'd expect a rebuild :p
[07:51] <flocculant> if I get time I'll do an upgrade test - but you know how quick they are ... 
[08:02] <flocculant> and rebuilding :p
[08:17] <Unit193> https://launchpad.net/ubuntu/+source/ubiquity/2.21.51 that sounds important.
[08:24] <Unit193> FWIW, I started new builds too, but they'll take a bit to build.. :/
[08:24] <flocculant> yes - that does sound important :p
[08:25] <flocculant> also ack that 
[09:53] <Unit193> flocculant: Bah, back to the first issue.  So workaround works for this problem too.
[09:58] <flexiondotorg> Have you tested the new beta 2 isos?
[09:58] <flexiondotorg> Is Ubiquity still crashing for Xubuntu?
[09:59] <Unit193> flexiondotorg: Different thing.
[10:00] <flexiondotorg> OK, but is Ubiquity working for you?
[10:01] <Unit193> Not for what I'm doing no, but that's not to say the Beta 2 images don't install fine.
[10:34] <akxwi-dave> flexiondotorg, just testing the new beta 2 as we speak... Ubiquity seems ok so far.. got to the try xubuntu screen this time.. :-)
[10:35] <flexiondotorg> akxwi-dave, Thanks. In which case I've got a borked package :-(
[10:35] <flexiondotorg> And uninstallable images.
[10:36] <akxwi-dave> just about to run the full install as well.
[11:12] <bluesabre> flocculant: building here, https://launchpad.net/ubuntu/+source/xubuntu-docs/16.04.3, suppose you could start another rebuild once its published
[11:14] <bluesabre> knome: looks like we're still waiting for a new ubiquity-slideshow upload (vertical list of app icons)
[11:27] <knome> bluesabre, hmm.
[11:27] <knome> bluesabre, well, it'll land when the translations are uploaded i guess
[11:27] <bluesabre> just thought I'd let you know :)
[11:28] <knome> the last time i checked though, it looked like many flavors had the old 15.10 slideshows
[11:28] <knome> i just bumped their version numbers up
[11:28] <knome> i would imagine they want to update those as well
[12:21] <flocculant> bluesabre: mmm - even if I rebuild will it have that new docs package if it's in proposed? 
[12:22] <flocculant> guess not "Not touching package due to block request by freeze (contact #ubuntu-release if update is needed) " in excuses ...
[12:25] <flocculant> aah I see your request in -release now :)
[13:26] <ric_s> Hi, Is there a maximum number of photos to send to xubuntu contest? I did not find this information
[13:31] <knome> ric_s, not really; though we don't want to encourage people to send their whole photo directory for obvious reasons :)
[13:32] <ric_s> 1000 pictures is a good number?
[13:32] <ric_s> joke ;)
[13:32] <knome> pick 10 best
[13:33] <knome> :)
[13:33] <knome> or sth...
[13:33] <ric_s> thanks for the reply knome :)
[13:33] <knome> np
[13:33] <knome> thanks for participating and good luck!
[13:33] <ric_s> tks
[13:43] <Nairwolf> I'm gonna do upgrade test with the Beta 2 ;)
[13:53] <akxwi-dave> good luck,,
[13:55] <Nairwolf> thanks
[15:04] <Nairwolf> it's really long to upgrade my system ^^
[15:18] <akxwi-dave> still going?
[17:21] <flocculant> bluesabre knome: so I set an upgrade going this afternoon - it does boot to what appears to be a xenial desktop, even so - dpkg configure is still running now 5 minutes after I got that far :)
[17:26] <flocculant> knome: grabbed docs from -proposed, looks right eg no contr stuff, pdf looks right, not sure that it needs the green thing now the contr stuff has gone, no need to differentiate 
[18:21] <mexchip> hi
[18:21] <mexchip> I'd like to ask a question regarding this bug:
[18:21] <mexchip> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1560459
[18:22] <mexchip> yesterday I tried the 20160322 image and encountered that bug
[18:22] <mexchip> today, I see a fix has been released
[18:23] <mexchip> my question is, how long could it take for the fix to be applied to a new live image?
[18:23] <mexchip> so that I can repeat the test
[18:23] <mexchip> to confirm the bug has been solved
[18:28] <flocculant> mexchip: there was a rebuild about 10 hours ago - the bug is fixed
[18:29] <flocculant> mexchip: in future you can check for rebuilds on milestones fairly easily - go to tracker - check the version - we're now at 20160323
[18:29] <flocculant> if there were further rebuilds *today* then you'd see 20160323.1, .2 etc
[18:30] <flocculant> mexchip: finally - thanks for testing :)
[18:30] <mexchip> yes, I'm already downloading 20160323, but don't know if it included the fix
[18:30] <flocculant> yep
[18:30] <mexchip> great, I'd give a try once the download finishes
[18:30] <mexchip> thanks
[18:30] <flocculant> welcome :)
[18:30] <flocculant> mexchip: you downloading the whole iso again? 
[18:31] <flocculant> or do you know about zsync or rsync?
[18:32] <mexchip> downloading the whole iso with zsync
[18:32] <flocculant> ok - you should keep the old one and just zsync that :)
[18:32] <mexchip> I don't have the previous image, downloaded it on another machine
[18:33] <flocculant> ack
[18:33] <flocculant> just making sure you knew :)
[18:33] <mexchip> I had not used zsync before, wished I knew about it before
[18:34] <mexchip> thx
[18:35] <Nairwolf> hi everyone, I couldn't upgrade my system
[18:35] <Nairwolf> I was interrupted, I will try to do it again tonight
[18:46] <flocculant> Nairwolf: what sort of upgrade?
[18:47] <flocculant> mexchip: yea - very handy - I only use it for time to be honest, but if you're somewhere with slow net, or limited bandwidth - very useful :)
[18:54] <flocculant> bluesabre: what we going to do about the blueman crash? if there is something we can do of course ... 
[18:54] <flocculant> oh - now I look I see it's gone upstream :)
[18:54] <Nairwolf> from 14.04.4 to 16.04 with the upgrade-manager
[18:55] <Nairwolf> As I don't have so much time now before eating, I will test from 15.10 to 16.04
[18:55] <Nairwolf> what is the most urgent to test, with the upgrade-manager, or with a new iso ?
[18:55] <flocculant> Nairwolf: and did you read the mail to the dev list about upgrades specifically? 
[19:00] <flocculant> flexiondotorg: thanks for that btw
[19:05] <Nairwolf> yes, of course, flocculant
[19:05] <ochosi> bluesabre: http://git.xfce.org/xfce/xfce4-appfinder/commit/?id=4f3266b4902cc983385fbe6fee0a26db1002dcfb
[19:06] <flocculant> Nairwolf: so why tell us the upgrade is broken - when we told *you* and all :)
[19:06] <Nairwolf> it is said that the upgrade from 15.10 to 16.04 works, but I wanted to verify it again
[19:06] <ochosi> bluesabre: and meh, the upstream appicon of xfce4-notifyd is png and *crap*
[19:06] <flocculant> ochosi: evening :)
[19:07] <ochosi> bluesabre: i can try to get in touch with jeromeg to refresh it and provide more sizes... i guess we should try that for all of xfce since appstream exposes the crappy default icons now
[19:07] <ochosi> evening flocculant 
[19:07] <ochosi> just stopping by to fix some stuff
[19:07] <flocculant> :)
[19:07] <ochosi> bluesabre: i'm wondering whether meanwhile we should patch the xfce packages in our repos to ship the elementary icons instead of the unmaintained upstream crap...
[19:08] <ochosi> flocculant: now it's dinner time ;)
[19:08] <ochosi> bbabl
[19:10] <Nairwolf> flocculant, I'm not sure to understand, are you saying it's not really necessary to test upgrades with hardware ? 
[19:17] <knome> flocculant, mm
[19:48] <Unit193> migrating-upgrading.xml:228: element para: validity error : Element useinput is not declared in para list of possible children
[19:48] <Unit193> migrating-upgrading.xml:228: element useinput: validity error : No declaration for element useinput
[19:48] <Unit193> hardware-devices.xml:173: element para: validity error : Element appliation is not declared in para list of possible children
[19:49] <Unit193> hardware-devices.xml:173: element appliation: validity error : No declaration for element appliation
[19:49] <Unit193> Document fi/index.xml does not validate
[19:49] <knome> (:
[19:51] <knome> should be fixed now
[20:33] <flocculant> knome: not sure how worried you are - but today I got to the get involved slide then install done
[20:41] <Nairwolf_> upgrade from 15.10 to 16.04 is also really long...
[20:42] <flocculant> Nairwolf_: upgrading via update-manager IS long
[20:48] <knome> flocculant, not very
[20:48] <flocculant> good enough for me
[21:30] <flocculant> PaulW2U: I assume you didn't actually find bug 516237 on the livesession - but should have been 1516237 :)
[21:31] <PaulW2U> flocculant: I think you might be right  :)
[21:31] <flocculant> I edited it for you :)
[21:31] <PaulW2U> Thanks
[21:55] <flocculant> knome: draft website page done - won't touch that anymore now
[21:55] <knome> :)
[21:55]  * knome goes looking
[21:55] <flocculant> :)
[21:55] <knome> ...but only if you release the lock
[21:56] <flocculant> mmm
[21:56] <flocculant> I'm logged out ... 
[21:56] <knome> haha
[21:56]  * flocculant blames sso
[21:56] <knome> it says you are editing
[21:56] <knome> taking over..
[21:56] <flocculant> well it's seriously wrong :p
[21:56] <flocculant> k
[21:57] <flocculant> release notes are more or less finished too now - just need to sort out a few bug removals/movements depending on tracker results 
[21:57] <knome> looks good to me, added release tag
[21:57] <flocculant> and lose the BFRB
[21:57] <flocculant> knome: I always forget tags ... 
[21:57] <knome> hmm
[21:57] <knome> maybe remove the excess bold from the note
[21:57] <flocculant> like the BFRB ? 
[21:58] <knome> refresh and see
[21:58] <flocculant> refresh which the website one? 
[21:58] <knome> yes
[21:58] <knome> https://xubuntu.org/?p=3788&preview=true
[21:58] <flocculant> logging in again :p
[21:59] <flocculant> aah right from Minimal upgrade testing was undertaken during this milestone. There ... 
[21:59] <knome> yep
[21:59] <flocculant> just leaving the ... recommended 
[21:59] <flocculant> yup - works for me :)
[21:59] <knome> it felt a bit too much with the next paragraph mostly bold too
[21:59] <Nairwolf> flocculant, I can confirm that the upgrade from 15.10 to 16.04 works with a real hardware. I know that it has already been tested, but it's better to test twice than one. 
[21:59] <flocculant> yep - that's fine knome :)
[21:59] <Nairwolf> especially with different hardware
[21:59] <flocculant> Nairwolf: ack thanks :)
[21:59] <flocculant> yea ofc
[22:00] <knome> so consider an ACK from me for releasing 
[22:00] <knome> unless it happens to be me to do that
[22:00] <flocculant> Nairwolf: if I had time - and didn't start using dev almost straight away I could properly upgrade test
[22:00] <flocculant> knome: yup - thanks :)
[22:01] <flocculant> depends on time - and as infinity - likely I will be snoring :p
[22:01] <knome> heh
[22:01] <flocculant> couple of resize tests to see results for only
[22:01] <Nairwolf> flocculant: tell me if I can do something to help you
[22:01] <flocculant> and any extras of course
[22:02] <flocculant> Nairwolf: resize image tests :p
[22:02] <knome> btw, i noticed something today on the contest site...
[22:02] <flocculant> knome: ... 
[22:02] <knome> apparently for some reason you can select not to share your LP username with it
[22:02] <flocculant> orly
[22:02] <knome> it's no problem in a way
[22:02] <flocculant> never noticed that
[22:02] <knome> we will just have people's emails directly
[22:02] <Nairwolf> flocculant: what does mean "resize image tests" ? 
[22:02] <flocculant> I did go looking to see the voting bit :)
[22:03] <knome> i double-checked today; xubuntu.org always needs it, contest doesn't
[22:03] <knome> sooo..
[22:03] <flocculant> Nairwolf: http://iso.qa.ubuntu.com/qatracker/testcases/1301/info
[22:03] <flocculant> is the testcase
[22:03] <knome> (and yeah, we're using the exact same wordpress and plugin versions, so go figure)
[22:03] <flocculant> knome: odd
[22:04] <knome> oh
[22:04] <flocculant> perhaps because *anyone* can post there - unlike the rest of the site
[22:04] <knome> there was one setting thing
[22:04] <knome> maybe that helps
[22:04] <flocculant> :)
[22:04]  * knome facepalms
[22:04] <knome> i have no idea why i didn't see that before
[22:04] <knome> anyway
[22:04] <knome> it's not a biggie
[22:04] <knome> we do have their email addresses anyway for contacting
[22:04] <knome> and if they gave a bogus one... their loss
[22:05] <flocculant> Nairwolf: basically - install (making sure drives is big enough for more than one install) then reboot with the iso - install, it will ask if you want alongside install
[22:05] <flocculant> knome: yea
[22:06] <Nairwolf> okay, I will test that tomorrow I think
[22:06] <flocculant> Nairwolf: thanks :)
[22:06] <flocculant> though depends on when of course - I might have marked all ready :)
[22:07] <Nairwolf> I can't test it tonight because I'm trying tu upgrade Xubuntu from 14.04.4, as I had to stopped it this afternoon
[22:08] <flocculant> Nairwolf: if you are doing so with the update-manager - it WILL crash, you WILL have to hard reboot :)
[22:09] <flocculant> knome: voting works then :)
[22:09] <knome> mhm
[22:09] <knome> are we voting already then? P
[22:09] <knome> :P
[22:09] <flocculant> well I did to see :)
[22:09] <knome> hahah
[22:10] <Nairwolf> I just want to confirm it, flocculant, and mark that this bug is affecting me
[22:10] <Nairwolf> https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1549067
[22:10] <knome> well it should be relatively easy to wipe out the votes if needed
[22:10] <flocculant> cos first off I thought the +/- buttons were rather dim - then once voted on *something* it all became clear
[22:10] <flocculant> in more ways than one :p
[22:10] <knome> lol
[22:10] <knome> yep
[22:10] <knome> actually what i should do is add a "neutral" button there too
[22:11] <flocculant> knome: why shouldn't team vote on things as they get time? makes sense to me
[22:11] <knome> if team should vote, then we should link the team LP to as admins
[22:11] <knome> or some else new role that has voting rights
[22:11] <knome> (admin is fine though, i don't think anybody would abuse)
[22:11] <flocculant> knome: I thought of that while I was there - but then I went back to my default thinking - if not voted yay or nay - fence sitter are you :)
[22:12] <knome> it all depends how we want to do the voting
[22:12] <flocculant> knome: well yea - I still obviously think we're missing a trick on not having community votes
[22:12] <knome> as i said before, i don't have a strong preference
[22:12] <knome> we can still hook up -users to a role that can vote
[22:13] <knome> though the votes are totals
[22:13] <knome> so if we then wanted to vote between the team
[22:13] <flocculant> I'd be happy doing something like a civs for the community to whittle it down - then keep the community top vote, then team vote in 5 more 
[22:13] <flocculant> or something 
[22:13] <knome> we would have to clear votes or do it manually
[22:13] <knome> hmm
[22:13] <knome> another option is make team vote
[22:13] <knome> and then pick top X from that list
[22:13] <knome> and put the rest that have a positive score in CIVS
[22:14] <knome> so some moderation from team, but not too much
[22:14] <flocculant> or
[22:14] <flocculant> have team vote for X, keep a couple, let community pick Y from remainder
[22:14] <flocculant> or is that another way of saying what you did ... 
[22:14] <knome> yes, it's the same
[22:15] <flocculant> trouble with that is 
[22:15] <knome> so basically team decides their winners
[22:15] <knome> and the community can vote for the rest that have a positive score
[22:15] <flocculant> team might vote on 4 - we want a lot more :)
[22:15] <knome> eg. are not completely crap
[22:15] <knome> we can also figure out a list of all submissions that have at least one positive vote
[22:15] <flocculant> yea
[22:15] <knome> though at that point i would probably just let community vote on all
[22:16] <knome> because if something has +1 and -7...
[22:16] <flocculant> right
[22:16] <knome> it's as good/bad as -8
[22:16] <knome> from my POV
[22:17] <flocculant> there's a week to sort it out
[22:17] <flocculant> I know how to drag info from LP group for civs
[22:17] <flocculant> if we want to do that
[22:18] <knome> dragging stuff from the contest site to civs on the other hand...
[22:18] <knome> actually what i should do is create a template for the contest site that shows all the entries so far
[22:19] <flocculant> what's the deadline as far as release schedule goes? 
[22:19] <flocculant> Final Freeze I assume
[22:19] <knome> yes
[22:19] <knome> was my thinking that if we got voting done (early) on release week 24, we'd have a few days before FF
[22:20] <knome> so we need to make sure bluesabre is around for an upload
[22:20] <knome> and might want to do the exception paperwork early
[22:20] <flocculant> yea - if we went that way - end civs on the Thursday before week 25
[22:21] <flocculant> then we have Friday to Sunday to choose final lot
[22:21] <knome> well we can start the CIVS vote on the day the voting ends if community votes from all
[22:21] <flocculant> yea
[22:21] <knome> if we want team moderation, then it's a much tighter
[22:21] <flocculant> I'd be inclined towards community vote in 10
[22:21] <flocculant> we keep at least top 1
[22:21] <knome> i mean
[22:21] <flocculant> team votes on rest
[22:22] <knome> ultimately, if the community votes for something that is totally unacceptable
[22:22] <knome> the team can have a veto anyway
[22:22] <flocculant> yep
[22:22] <knome> so there's no reason to apply team moderation before
[22:22] <knome> in a way..
[22:22] <flocculant> well
[22:22] <flocculant> in that case why bother :)
[22:22] <flocculant> here's the ones we want you to vote on
[22:22] <knome> well okay, if we have 100 submissions, a CIVS poll is not going to be nice
[22:23] <flocculant> right
[22:23] <knome> that's my main concern
[22:23] <flocculant> and I'd not do it :p
[22:23] <knome> especially since the targets are in a different website
[22:23] <flocculant> has to be a manageable number 
[22:23] <flocculant> yea
[22:23] <knome> so i'm not really sure what the ideal way is
[22:23] <knome> as i said before, we can let the community vote on the site too
[22:23] <flocculant> maybe team should vote 12 - then let community vote 6 of those
[22:24] <knome> but also we don't have a way to separate votes from different groups...
[22:24] <flocculant> yes - but would they? 
[22:24] <knome> would they vote on CIVS?
[22:24] <flocculant> if we civs - we can do LP users
[22:24] <flocculant> well they'd get a mail
[22:24] <knome> same with the site
[22:24] <flocculant> I would if I was just bert
[22:24] <knome> we can link -users to voters
[22:25] <flocculant> right
[22:25] <knome> (currently voting is linked with the admin group, but that's easy to work around)
[22:25] <flocculant> we need to see what the rest of team thinks about it I guess
[22:26] <knome> yep
[22:26] <flocculant> if I'm the only one who thinks we're missing a trick - then *shrug*
[22:26] <knome> lol
[22:26] <flocculant> not that I'd not keep on banging the drum :D
[22:26] <knome> it's just so much easier to do team voting only
[22:26] <flocculant> of course
[22:26] <knome> well, the last time it was a subteam of team
[22:26] <knome> but now we have a better voting mechanism
[22:26] <flocculant> only have to count to 7 or so that bother to vote :p
[22:26] <knome> so no reason not to involve whole team
[22:27] <flocculant> might be best to ping people in channel rather than m/l
[22:28] <knome> mhm
[22:28] <flocculant> anyway - zebedee is about now :)
[22:28] <knome> lol
[22:28] <knome> good night :)
[22:28] <flocculant> night knome et al :)
[22:28] <knome> hello amerigena 
[22:29] <flocculant> close my eyes and hope I don't see the release note ... 
[22:29] <knome> hahah
[22:29] <knome> fair enough