[00:16] <bluesabre> knome: confirmed
[00:17] <bluesabre> knome: but I think that's related to how planet is configured
[00:18] <bluesabre> knome: https://wiki.ubuntu.com/PlanetUbuntu#Adding_Your_Blog
[00:19] <knome> bluesabre, but the link points to the xubuntu site, and it has worked before
[00:19]  * bluesabre shrugs
[00:20] <bluesabre> just a thought, nothing more
[00:20] <bluesabre> :D
[00:21] <knome> o.O
[00:21] <knome> http://release-blog.ubuntu.com/?feed=rss2
[00:21] <knome> see what happens when you access that url.
[00:27] <bluesabre> knome: looks fine to me
[00:27] <knome> not
[00:27] <knome> see the location
[00:28] <bluesabre> oh
[00:28] <knome> yeah
[00:28] <bluesabre> I see....
[00:28] <knome> pointed this out to the IS
[00:28] <knome> and i got the http request to work
[00:28] <bluesabre> release-blog goes to xubuntu.org
[00:28] <knome> yes
[00:28] <knome> the IS vanguard is working on it :)
[00:28] <bluesabre> :D
[00:29] <bluesabre> going out to get some food, bbabl
[00:30] <knome> bon appetit
[00:42] <knome> ...oh
[00:42] <knome> launchpad isn't giving us etag results for the stuff we're requesting in the http headers
[00:43] <knome> only in the json
[00:43] <knome> that's why they never match
[04:32] <sidi> Having some fun with Firejail. http://sidi.mupuf.org/files/xfce-workspace-sandbox.ogv
[04:32] <sidi> There's a Wily/Vivid PPA for the curious ones among you at https://code.launchpad.net/~ucl-cs-study-devs/+archive/ubuntu/multitasking-study. Needless to say, use at your own risk.
[04:32] <sidi> http://i.imgur.com/YfZS9SC.png is the list of options :]
[04:33] <sidi> Feedback is welcome, though at this stage this is alpha, and I will not attempt to merge it into any project whatsoever.
[04:40] <bluesabre> sidi: neat!
[09:51] <flocculant> !team | anyone awake? 
[09:51] <ubottu> anyone awake?: bluesabre, dkessel, flocculant, jjfrv8, knome, krytarik, micahg, Noskcaj, ochosi, pleia2, slickymaster and Unit193
[10:00] <dkessel> hey flocculant !
[10:00] <flocculant> dkessel: morning - you're just the man :)
[10:01] <flocculant> you got a minute to read a short draft for me? 
[10:01] <dkessel> flocculant: sure
[10:02] <flocculant> dk@ubuntu.com? 
[10:02] <flocculant> dkessel: ^^ 
[10:04] <flocculant> sent to what I assume is your ubuntu address
[10:11] <dkessel> I think it is good. It emphasizes exactly what is needed
[10:11] <flocculant> cheers Daniel - I'll send it now then :)
[10:21] <dkessel> np :)
[10:39] <flocculant> this is going to be painful ... 
[11:05] <bluesabre> morning
[11:56] <dkessel> hello bluesabre :)
[12:19] <Nairwolf> hi flocculant, I've read your mail. I should able to make the two tests for amd64 with hardware
[12:28] <flocculant> hi bluesabre :)
[12:29] <flocculant> Nairwolf: thanks :)
[12:29] <bluesabre> hey flocculant , dkessel, Nairwolf
[12:33] <flocculant> bluesabre: how's Saturday - I guess really early :p
[12:34] <bluesabre> flocculant: very early indeed
[12:34] <flocculant> oh good lord :|
[12:34] <bluesabre> my first "morning" was immediately followed by being dragged back to bed because it was too early
[12:35] <flocculant> downloaded what I thought was 14.04.4 - seems I need 400Mb of updates :(
[12:35] <flocculant> bluesabre: ha ha 
[12:37] <Nairwolf> I have on my working computer an image of xubuntu 14.04.1. Don't you think it's important to test this upgrade also ? 
[12:39] <bluesabre> Nairwolf: if its a machine you depend on, I'd recommend not testing upgrades on it at this time
[12:40] <flocculant> bluesabre: why in the world would a mirror keep 14.04,.1,.2,.3 as well as having something that's actually up to date :|
[12:40] <Nairwolf> bluesabre: yes, I wouldn't do it directly. I think I will firstly clone my system in a "test-computer"
[12:41] <bluesabre> flocculant: posterity?
[12:41] <flocculant> Nairwolf: how do you have .1 ?
[12:42]  * flocculant makes sure to zsync the right one for 64 bit ... 
[12:43] <flocculant> ha - it's only 60% wrong then :p
[12:44] <flocculant> glad I have FFTH ... 
[12:49] <Nairwolf> flocculant: I've installed xubuntu when 14.04.1 was the most recent version of the LTS
[12:49] <Nairwolf> Something like August 2014
[12:50] <flocculant> yea - but not upgraded since then?
[12:50] <Nairwolf> I'm still with linux 3.13 and I've heard on 14.04.4 the kernel version is higher
[12:50] <Nairwolf> no, I wanted to stay on a LTS version
[12:51] <flocculant> upgrading packages ... 
[12:51] <flocculant> anyway - whatever - as far as the mails goes - I'm after 14.04.4 to 16.04 upgrades
[12:51] <flocculant> so - vm if necessary
[12:52] <Nairwolf> what do you mean by "upgrading packages" ? I'm running "sudo apt install && dist-upgrade" everyday
[13:02] <flocculant> that'll get you 14.04.4 with the old kernel
[13:02] <flocculant> trying the upgrade with the HWE stack (I hope)
[13:17] <flocculant> that's a good start ... 
[13:19] <flocculant> won't authenticate a package - with continue? in the title - no option to continue :p
[13:32] <bluesabre> oh nice
[13:36] <flocculant> module-init-tools
[13:36] <flocculant> moving on to 15.10 :p
[14:55] <flocculant> which at least got further
[14:56] <knome> 16:54 notice < queuebot:#ubuntu-release: New binary: lxpanel [i386] (xenial-proposed/universe) [0.8.2-1ubuntu1] (lubuntu, ubuntustudio, xubuntu)
[14:56] <knome> wut? lxpanel and xubuntu?
[14:59] <flocculant> nice
[15:08] <bluesabre> knome: its because lxpanel plugins are built from xfce4-power-manager
[15:46] <knome> aha
[15:49] <cm2> bluesabre: but why does that imply that lxpanel needs to be in xubuntu?
[15:56] <flocculant> 15.10 upgraded to 16.04 \o/
[16:01] <flocculant> half way through today's 
[16:02] <knome> :)
[16:02] <flocculant> I'd like to be able to at least give our testers some pointers :)
[16:02] <flocculant> like - try that - confirm the fail please :p
[16:07] <flocculant> knome: btw #bbbbbb appears to be ok after a few days 
[16:20] <mikodo> Hi. Just trying to learn. Not doing the testing now. On the daily digest now from flocculant "Subject: Xenial Upgrade Testing week" states if one can use  hardware for release-upgrade it would be preferred.. Question: If one has an usb install with "persistence" for testing, like with mkusb, could that be used for testing and reporting?
[16:22] <flocculant> mikodo: to be completely honest - I'm not at all sure whether you can or can't
[16:22] <mikodo> Okay, I'll guess I find out in the future. Thanks.
[16:22] <flocculant> I would hazard a guess that if you *could* and it had bugs doing so - then the bugs would get marked invalid - they're probably more likely to care about hardware or vm upgrades
[16:24] <mikodo> Sorry, I don't understand. Does ^^ that mean it would most likely not be helpful?
[16:24] <flocculant> yea - or at least that's how I would see it logically 
[16:24] <flocculant> we aren't the ones who'd fix upgrade fails - canonical people would
[16:25] <flocculant> so I can't really see them being overly bothered about a persisent usb install
[16:25] <mikodo> flocculant, Okay
[16:25] <flocculant> that's not to say that I'm right of course :)
[16:25] <mikodo> :)
[16:25] <flocculant> :)
[16:26] <mikodo> flocculant, Can I bother you for one more question. Would the persistent usb install of testing images generally be helpful for other testing other than this do you think?
[16:27] <flocculant> mikodo: it's not something that I've given a great deal of thought to up to now
[16:28] <mikodo> flocculant, I think I will ask that to sudodus the author or mkusb. Thanks1
[16:28] <flocculant> and it's never a bother either :)
[16:28] <mikodo> author of ...
[16:30] <flocculant> mikodo: just so you know - hot off the press and all that - trusty to xenial upgrades are failing, wily to xenial are passing
[16:31] <mikodo> Yea, I was getting that impression from reading the digest notes, you sent or, something like that was happening
[16:31] <flocculant> well - we didn't test for the trusty point release at all - so this is catch up :)
[16:31] <flocculant> but the one failing was doing so a while back when I looked
[16:32] <mikodo> I just started reading the digest this week, but I new their was not the degree of testing done this release as before
[16:34] <mikodo> Man my spelling sucks if I don't read what I typed! Thanks.
[16:34] <flocculant> testing has been quiet since the testing done for Trusty 
=== pleia2_ is now known as pleia2
[16:46] <pleia2> hey, people pay attention to us http://news.softpedia.com/news/xubuntu-16-04-lts-probably-won-t-come-with-a-default-media-manager-installed-501067.shtml
[16:47] <pleia2> social media-ing the upgrade testing stuff
[16:49] <flocculant> nice and also thanks :)
[16:50] <mikodo> 'Tis on the Xubuntu wiki right?
[16:50] <flocculant> mikodo: that is yea 
[16:50] <mikodo> I understand, getting the word out. Thanks!
[16:51] <pleia2> flocculant: btw, if you could always provide a link to the iso tracker in these emails, it would help :) (if someone sees a tweet for the first time, what's an iso tracker?)
[16:51] <pleia2> for fb and G+ I manually add it in the text, twitter has not enough characters
[16:51] <flocculant> pleia2: yep ok 
[16:52] <flocculant> I guess that this one I'd mentally aimed at people who normally test for us :) 
[16:52] <mikodo> ^^ +1 I was wondering about that but, thought I would figure it out when the time came for me to test.
[16:55] <flocculant> mikodo: http://iso.qa.ubuntu.com/
[16:56] <mikodo> Thanks, I'll have a look. :)
[16:57] <flocculant> I've just mailed the direct links to our stuff
[16:57] <flocculant> postifx is failing to update in xenial today too :)
[16:58] <pleia2> https://skitterman.wordpress.com/2016/02/26/postfix-3-0-woes/
[16:58] <pleia2> so, yeah
[16:59] <flocculant> aaah - it'll catch up then 
[17:00] <flocculant> not even sure what postfix is and why I need it - or indeed why I need it updating :D
[17:00] <pleia2> mailserver, it's used by default to send local messages to users on the system
[17:00] <pleia2> error logs go to root, etc, that weird "You have mail." when you log in :)
[17:00] <flocculant> right - so not something I'd want really
[17:01] <flocculant> wonder why I have it :)
[17:01] <pleia2> it's important for those who use it
[17:01] <flocculant> yea of course - I understand that - now I have more idea what it is :p
[17:01] <pleia2> I have a cold, so I'm going back to bed now
[17:01] <pleia2> have fun
[17:02] <flocculant> oh dear :(
[17:43] <jjfrv8> flocculant, confirmed the trusty upgrade bug. Working on xenial.
[17:47] <flocculant> jjfrv8: cool - thanks :)
[17:47] <flocculant> nice to know it's not just local
[19:35] <bluesabre> cm2: that doesn't mean it's in xubuntu, but rather that it is in the xubuntu packageset (and therefore able to be uploaded by us)
[20:34] <mikodo> re: mkusb https://help.ubuntu.com/community/mkusb  See responses following my question on using it for testing: http://ubuntuforums.org/showthread.php?t=1958073&page=35&p=13447113#post13447113
[20:35] <mikodo> actully just before my link response to the questions.
[20:38] <mikodo>  "Actually the responses just before my linked to response to the answers.
[20:57] <flocculant> so - that implies I was right then :)
[21:04] <mikodo> flocculant, Yes, that is correct! :)
=== SwissBot_ is now known as SwissBot
[22:17] <cm2> bluesabre: ah. i see. thanks!