[00:32] <tsimonq2> Aww :/
[00:33] <tsimonq2> Sorry everyone. I apparently don't know how to set a topic. :P
 We've been considering a 17.10 respin anyways due to some UEFI installation issues, but regardless, keep on the lookout if you're installing a Lenovo laptop.
[00:35] <tsimonq2> Better.
[00:52] <tsimonq2> wxl: I also have received a report that Toshiba laptops might be affected: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736827
[00:53] <wxl> nice
[00:53] <wxl> that's what happens when people don't follow specs
[00:53] <wxl> s/people/manufacturers/
[00:53] <tsimonq2> Right.
[03:37] <tsimonq2> wxl: https://lists.ubuntu.com/archives/ubuntu-release/2017-December/004254.html
[05:05] <Kamilion> oh? are they hitting the SPI write protection bug again?
[05:06] <Kamilion> hah.
[05:06] <Kamilion> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/comments/141
[05:06] <Kamilion> yep.
[05:07] <Kamilion> "From our investigation with ODMs, the problem is due to the SPI flash has become write protected."
[14:40] <wxl[m]> Kamilion: did you see the current theories on why it fails? Not because of the module but because of the chips not following specs well.
[15:53] <wxl> what kind of weird update is this, @VikingRedwolf ??? https://mastodon.technology/@lubuntu/99207256538835238
[15:53] <wxl> while you're fixing that you can reply to that dude giving him a link to the bug. it may not affect him.
 @wxl, They didn't request it was halted... Steve just warned us.
 It's a warning, not a hard forbiddence
[16:21] <wxl> @tsimonq2: huh?
[16:23] <wxl> oh ic now
[16:24] <wxl> i guess the question is misguided
[16:24] <wxl> it doesn't affect 17.04
[16:24] <wxl> and there's no spinning of 17.10
[16:24] <wxl> the issue is, however, that ubuntu did completely remove any easy link to the 17.10 download
[16:32] <wxl> @tsimonq2: it's worse, actually. they've removed any links at all frmo cdimage.u.c
[16:32] <wxl> some of the mirrors still have it but that's about it
[16:33] <wxl> errr but it's still on releases.u.c
 @wxl, OH I didn't know that.
[17:13] <wxl> yup
 what the hell?
 have you touched the blog for anything?
[17:14] <wxl> in fact someone just dropped this in another channel https://www.cyberciti.biz/linux-news/ubuntu-17-10-no-longer-available-for-download-due-to-lenovo-bios-getting-corrupted/
 @VikingRedwolf, No
[17:14] <wxl> ntoe too that it isn't ONLY lenovo
[17:14] <wxl> no, @VikingRedwolf
 I've tweeted though
 not connected. weird. every change to the site gets an instant replica in the Mastodon place
[17:15] <wxl> i'm not sure where i first saw that bug but i've been following it closely
 unless you deactivate the checkbox on the right ;)
[17:15] <wxl> FIX IT @VIKINGREDWOLF
[17:16] <wxl> so far only two errant changes
 naaah
[17:16] <wxl> they were 2 hours ago
 .__.
[17:16] <wxl> don't make me check the logs for who messed up :)
 O_O
 oh, it seems it was me :$
[17:17] <wxl> hm
[17:17] <wxl> so
[17:17] <wxl> surprised
 o_____o
 you should be. it's Simon who usually do strange things
 *runs*
[17:18] <wxl> https://llwproductions.files.wordpress.com/2015/12/angry-face-husky.jpg
[17:19] <wxl> true though
[17:19] <wxl> example: just found this pic of simon http://cdn.foodbeast.com.s3.amazonaws.com/content/wp-content/uploads/2012/10/dog-banana-costume.jpg
[17:19] <wxl> (honestly, that almost made me spit up my tea. that face omg)
 @VikingRedwolf Respond to the tweet as LubuntuOfficial saying the images have officially been taken down.
 Please. :)
[17:21] <wxl> s/tweet/toot/
 No
 Both
 Please
[17:21] <wxl> well i didn't see no tweet
[17:21] <wxl> but i did see a toot
 yup
[17:21] <wxl> but technically that's only for ubuntu
[17:21] <wxl> not sure if we should follow suit?
[17:22] <wxl> i think at least issuing a stern warning would be good
 I already tweeted
 Two times last night
[17:22] <wxl> i mean on our downloads page(s)
 wxl: Read the channel topic here XD
 Oh
 Yeah, follow suit
[17:23] <wxl> the problem is not the people that know how to look for information.. it's the ones that just point and click :)
[17:23] <wxl> so @VikingREdwolf that's on your todo list
[17:23] <wxl> i got a testcase to write today. we agreed on a solution
[17:23] <wxl> (re: UEFI testcases)
 huh?
[17:24] <wxl> also @VikingRedwolf if you could delete those errant toots, that would be good too
[17:24] <wxl> @VikingRedwolf, here's your todo list:
[17:24] <wxl> 1. change any download pages we have to match what ubuntu did to theirs with 17.10 https://www.ubuntu.com/download/desktop
[17:25] <wxl> 2. delete these toots https://mastodon.technology/@lubuntu/99207261937112809 https://mastodon.technology/@lubuntu/99207256538835238
[17:25] <wxl> 3. reply to this toot saying that downloads have been obfuscated https://mastodon.rocks/@miwilc/99207284447154504
[17:26] <wxl> @tsimonq2: where's that tweet?
 Read it. :l
 *:)
[17:26] <wxl> @tsimonq2: also you should include an explicit mention of it in the release notes with a link to the longer description in the ubuntu release notes
[17:26] <wxl> i
[17:26] <wxl> see it
 toots erased
[17:26] <wxl> don't
 @wxl, I will man, but I'm at school
[17:27] <wxl> ok
[17:27] <wxl> 4. reply to whatever tweet @tsimonq2 has whenever he decides to link us to it
 I'll add a "discouragement" message as well
[17:28] <wxl> yes i think that would be wise
 also, please Simon, can you tell if the "mobile bug" looks fine now? the menu on top o f the content, I mean
 @wxl, Seriously?
[17:30] <wxl> huh?
[17:30] <tsimonq2> wxl: The is.gd link.
[17:30] <tsimonq2> Go there.
[17:30] <tsimonq2> It's linked there.
[17:30] <wxl> ah so @VikingRedwolf what you need to do is reply to that tweet with the new info
 @wxl, As LubuntuOfficial, right
 @wxl, I'm still doing the WARNING thing .__.
[17:31] <wxl> you have all the time in the world @VikingRedwolf
[17:32] <wxl> (not really)
 omg omg omg so much stress
 @VikingRedwolf, Go faster. .__.
 (I'm messing with you}
 (Document) http://vps.tsimonq2.net:9090//file_3085.mp4
[17:34] <wxl> i'm going to un-beginner task the lubuntu qa task
[17:35] <wxl> students can only do 2 beginner tasks
[17:35] <wxl> i think that's why we're not getting any of them done
 @VikingRedwolf, Lol
 @wxl, OK, and create a task for testing the 17.10 ISOs so by the time the task is approved, it's time
[17:36] <wxl> but how can we test the fix, @tsimonq2 ?
[17:37] <wxl> unless you have the hardware
[17:37] <wxl> and even then you run the risk of bricking
[17:37] <wxl> my guess is they'll only smoketest and call it good
 @wxl, Well it will also pull in literally every update released to Artful since then.
 So we need general testing yoom
[17:38] <wxl> not necessarily
[17:38] <wxl> it *could*
 Urgh
 *too
 @wxl, Then why do we test the final images if we test the final beta images? :P
 http://lubuntu.me/downloads/
 I can also add a skull icon and a symbol of BIOHAZARD  o___o
[17:42] <wxl> oh i like that
 the biohazard symbol? O_o
[17:43] <wxl> unicode is always justified :)
 XD
[17:43] <wxl> MAYBE BOTH
[17:43] <wxl> what about the like electrocution warning?
 🍺 <- best emoji ever
[17:44] <wxl> don't use that one
[17:44] <wxl> https://emojipedia.org/high-voltage-sign/
 Hahahahahaha
 you're a bsolutely right, sorry, I'll look for the GUINNESS EMOJI o__o
[17:44] <wxl> https://emojipedia.org/fire/
[17:45] <wxl> https://emojipedia.org/radioactive-sign/
 that flame describes me
 .__.
 you could reply the toot though
 you are the mastodon guy!
[17:45] <wxl> no you will
[17:45] <wxl> you're already logged in
 smsmshmm
[17:45] <wxl> TOO LATE I CALLED IT YOU"RE IT NO TAG BACKS LOVE YOU BYE
 O__O
[17:46] <wxl> actually i'm late for work, so no luck anyways XD
 you'll get skinny
[17:46] <wxl> i wish..
[17:46] <wxl> seriously, bai
 o/
 @wxl, eeewww
[18:16] <wxl> @tsimonq2: i'm sure you saw this but:
[18:17] <wxl> 0954 < slangasek:#ubuntu-release> wxl: also, investigation is still in progress of a runtime recovery
[18:17] <wxl>                                   of the issue.  If we get one, then there's no need to respin the
[18:17] <wxl>                                   images after all
[18:17] <wxl> but if you are right that we will need full release testing if that doesn't happen
[18:17] <wxl> @VikingRedwolf is your list done? :)
 aye
[18:18] <wxl> good boy
 toss me beer!
[18:19] <wxl> actualy i can't yet
[18:19] <wxl> there's still the front page
 that'll look ugly if I use the same warning code
[18:20] <wxl> maybe just disable that section temporarily?
 anyways, the frontpage leads you to the downloads, and the message
[18:21] <wxl> except for what's under that link
[18:22] <wxl> bottom half of https://share.riseup.net/#QOei8uNoscs4Fx7gTdVFbw
[18:22] <wxl> i'm suggesting to disable that particular section
[18:22] <wxl> leave the download link at the top
[18:22] <wxl> for that matter, i think it might be best not to litter the front page with download links at all, no?
[18:35] <Kamilion> *perk via highlight*
[18:36] <Kamilion> wxl: doesn't suprise me, gigadevice has been known to be weird in the past.
[18:38] <Kamilion> https://lwn.net/Articles/741913/
[18:38] <Kamilion> i'm amused at the fourth comment
[18:39] <wxl> yeah it's really not a lenovo issue. it just so happens that they seem to use a lot of the bad chips :)
[18:45] <wxl> Kamilion: it's kind of like the time i happened to have a motherboard from a manufacturer that was afflicted by the capacitor plague
[18:45] <wxl> at least it didn't catch fire XD
[18:45] <wxl> https://en.wikipedia.org/wiki/Capacitor_plague#/media/File:Brand_auf_Platine.jpg
[18:46] <wxl> it was surprisingly usable for as many capitors were bulging on it
[18:46] <Kamilion> well, yeah, the capacitance was only off by a little until they went boom
[18:46] <Kamilion> it was the possibility of a sudden venting that would cause problems and schmoo all over
[18:47] <Kamilion> nasty brown/black tar and paper tatters
[18:47] <Kamilion> thankfully, not as hard to clean up as a burst battery, like on amigas and various arcade machines
[18:47] <Kamilion> that shit's actually acidic and will eat away at the traces
 @wxl, I doubt we'll be able to avoid a respin.
 And wxl, this was exactly my point: slangasek> wxl: the images will have to be built with all the SRUs since release; we should plan for full release testing
[20:17] <wxl> @tsimonq2: "doubt" is no certainty
[20:18] <wxl> @tsimonq2: in other news be prepared to let's encrypt all of lubuntu.me next month https://letsencrypt.org/2017/07/06/wildcard-certificates-coming-jan-2018.html
 @wxl, That's your task. 😉
 Unless you teach me how!
[20:27] <wxl> i've never done it before and besides you run phab so there :þ
 @wxl, no way!
 :D
[20:40] <wxl> @VikingRedwolf: whey
 I did with my own server
 but I must admit that ubuntu servers are easier to configure
[20:41] <wxl> what are you using on your server??
 letsencrypt
 ubuntu server 16.04
[20:41] <wxl> uh
[20:41] <wxl> oh
[20:41] <wxl> now i get it :)
 :)
[20:41] <wxl> well i think @tsimonq2's machinery is ubuntu too
 look at this: https://certbot.eff.org/
 easy steps
[20:42] <wxl> then where is it hard?
[20:42] <wxl> um
[20:42] <wxl> s/hard/difficult/
 it is not with certbot
[20:42]  * wxl glowers at @VikingRedwolf
 I could do it, and remember... I'm blonde!
 buuuut I f*cked it up a couple times
 question: is everything in the same server / host?
[20:45]  * agaida think: certs are boring, lets_encrypt is boring and wildcard certs take away all the fun of being a nerd ...
 are wildcards already supported?
[20:45] <agaida> no - not yet
 and can certbot / letsencrypt create certificates across hosts?
 I don't think so, so our Phab instance might not be https
[20:47] <agaida> why - use a standard cert in that case - wildcard certs may be convinient but ...
[20:47] <redwolf> standard cert? paid ones?
[20:48] <agaida> aka register phab.domain.tld with exactly that domain to the machine  - thats possible
[20:48] <redwolf> the domain is in Gandi, so we could buy one for all sub-sites
[20:48] <redwolf> but I don't think certbot can do that
[20:48] <redwolf> or, more likely I have no idea how to do that
[20:49] <redwolf> wxl: https://certbot.eff.org/#ubuntuxenial-apache
[20:51] <agaida> redwolf: i have letsencrypt certs for misc subdomains on different machines - like on dev-host: https://pb.5id.eu/3wcW
[20:52] <redwolf> really? nice! but that's beyond my skills :(
[20:53] <agaida> and on our normal webserver https://pb.5id.eu/form/
[20:53] <agaida> thats easy - the certs are bound to the machine
[20:54] <agaida> in combination with the (sub).domain.tld - so the mechanism is easy
[20:55] <redwolf> I though the script literally looked for folders in the server
[20:55] <agaida> i issue a certificate from a certain machine - letsencrypt resolve the issued domain/subdomain and deliver the cert exactly to this machine
[20:55] <agaida> done
[20:56] <agaida> you might notice that i use right now the standalone certbot with a start and a stop hook
[20:58] <agaida> that means - $webserver is terminated, certbot took over and provide port 80 and receive the possible certs and updates - and start the $webserver with the new certs
[20:59] <agaida> old script - reason was the old nginx that can't do this on the fly
[20:59] <agaida> but the 10s all three days don't hurt, so i leave it that way
[20:59] <agaida> just lazy