[00:00] Its there.. Say something [00:00] There [00:00] Or cai post it 3 times again? [00:01] can [00:01] the *2nd* one, where it's unplugged, @Bitocoinare? [00:01] Yes [00:01] Same thing [00:01] nope didn't see it [00:01] Ok.. You want us to continue here? [00:02] nope. just paste it there [00:02] Say something there.. please [00:02] anything [00:02] you're not in there, at least not by nick, @Bitcoinare [00:03] Oh dear..lol Maybe I should have reloaded after disconnecting [00:03] I've been typing away [00:41] who's the BIOS bug person, @tsimonq2 ? [00:41] wxl: Oh, right, ypwong [01:43] @tsimonq2, and now it's when I say how proud I feel about MY TEAM, because that's what you've been all these years [01:44] but I still want my bloody beer! 😐 [01:44] Heh thanks :) [01:47] /me hands VikinRedwolf a Pils: http://www.bier1516.bayern/imagetypes/rex_lightbox/urquell.jpg [04:44] dumb question, @tsimonq2 but is 18.04 affected by this bug? should we be warning people against hardware testing? [04:44] @wxl, You might want to check with ypwong but I think it's been disabled there [04:44] also are phab emails working? did you get notification of the changes i did this morning? [04:45] Hm, no, didn't get that [04:45] so yeah you may want to check into whether mails are failing but http://phab.lubuntu.me/T1 [04:46] Hm ok [04:47] and give a think/ask around about hardware testing in 18.04, especially with alpha coming up [04:47] Ok [05:24] yes [05:32] bug 1347801 [05:32] Bug 1347801 in Ubuntu Manual Tests "No upgrade option on 'Installation type' screen" [Undecided, Fix Released] https://launchpad.net/bugs/1347801 [05:32] ignore that [05:35] hey @tsimonq2 want to talk about that GCI task for upgrading? [05:36] wxl: yea sure what's up? [05:36] looks like we have four testcases for dealing with upgrades: 2 are for LTS, 2 are not and for each of them there's an upgrade with update-manager and an upgrade with the image e.g. http://iso.qa.ubuntu.com/qatracker/milestones/384/builds/163339/testcases [05:37] so i think the task is really, well, upgrading. it doesn't exactly test every single installation possibility, but it seems like that has worked out fine [05:37] the same logic was applied with the creation of the BIOS/UEFI testcases [05:38] so you have a problem with me just making this simple? [05:38] So what would be the reason for simplifying it? [05:38] I get why the BIOS/UEFI tasks are simple [05:38] But [05:39] because that's how the testcases are written XD [05:39] Why make this simple too? [05:39] hehe [05:39] well [05:39] I mean if you can give me a good justification for it then JFDI but otherwise what's the use? :) [05:40] well it's to test if the upgrade works correctly. admittedly, tif you, e.g. managed to install with XFS correctly, the upgrade isn't going to change that [05:40] Right? [05:40] so no need to test every single installation type [05:40] but that's kind of what you had suggested before.... [05:41] oh [05:41] hm [05:41] cuz really at that point, we might want to start questioning the validity of those testcases [05:41] as written, at least [05:41] Well to be clear, we should test amd64 and i386 image and update manager LTS->LTS and Regular->LTS upgrades. [05:41] So I mean [05:41] I see the use for them [05:41] yep [05:42] ok so we're on the same page then [05:42] Are we though? [05:42] Because I see the use for them as is ;) [05:42] i do, too [05:42] ok [05:42] Then cool [05:42] but what i heard you say was that you wanted the student to do every single type of installation and then do the upgrade on all of them and that's kind of insane [05:42] No [05:42] Maybe [05:43] no :) [05:43] Did I? O_o? [05:43] (that's what I'm questioning here) [05:43] that's what i thought i read but i dunno :) [05:43] Like I'm a fan of hard labor and all but like [05:43] Don't think I said that :) [05:43] anyways [05:43] wxl: two more things I've been thinking about real quick [05:43] k [05:44] wxl: Once everybody gets back from break and all, wanna look into converting our seeds (at least for Bionic) to Git? [05:44] It's possible, I **THINK** [05:44] But we'd be doing the grunt work if not [05:44] that might be cool [05:45] I'd also like a +1 from gilir before actually doing it, but like, just a thought :) [05:45] as long as there isn't some weird bzr-only hook the canonical infrastructure has :/ [05:45] Because Bazaar is aaaaaaaaancient [05:45] bzr is alright but i'm happier with git [05:46] here was the confusing comment https://irclogs.ubuntu.com/2017/12/25/%23ubuntu-google.html#t01:30 [05:46] Well do an apt source lubuntu-meta real quick and look at that fugly update.cfg real quick [05:46] So it might be [05:47] wxl: oh? don't see how that's confusing :) [05:47] what i heard was "they need to do every installation type and try to upgrade each of them" [05:47] and yes i do see a bzr+ssh there [05:48] wxl: no but look at the structure of it [05:48] bionic/bzr [05:48] so hmm [05:48] dunno [05:48] right that too [05:48] wxl: Anyways, that's not what I meant [05:48] and check out update [05:48] exec germinate-update-metapackage --bzr [05:48] ohhhhhhhh [05:48] so we CAN use Git [05:49] coooooooooool [05:49] maybe [05:49] http://manpages.ubuntu.com/manpages/zesty/en/man1/germinate-update-metapackage.1.html [05:49] wxl: well I mean I'd like an ack from the likes of slangasek/infinity [05:49] yeah ik I just checked there, I see git XD [05:50] wxl: I'll play around it locally and I'll get an ACK/NACK once I know it's possible [05:50] the whole guessing from the uri is kind of interesting [05:50] (from all parties) [05:50] oh? [05:50] interesting, like annoying [05:50] The version control system to use is guessed from [05:50] the seed_base URL defined in the configuration file, trying git [05:50] then bzr if the URL is ambiguous. [05:50] ..although that latter clause is nice [05:50] if it can't be guess from the uri, it tries git first [05:50] Actually, let me try this now... [05:51] It may also [05:51] have a dist/vcs or dist/bzr section which can override the seed_base and [05:51] right [05:51] seed_dist values from the dist section if the --vcs or --bzr option [05:51] respectively is given. [05:51] ^^ update.cfg [05:52] so you could do [bionic/vcs] [05:53] right [05:53] then s/bzr/git/ and then you have to add the +git in there cuz ugh launchpad [05:54] right [05:54] hm [05:54] this man page is a wee confusing [05:54] wxl: Made the change locally with https://code.launchpad.net/~lubuntu-dev/ubuntu-seeds/+git/lubuntu.bionic (got it that way with git-remote-bzr <3), let's see if it crashes and burns [05:54] apparently seeds is mandatory in distribution sections, but there's not one in the dist/vcs section [05:55] so how did that no-follow-recommends test go? [05:55] There was literally little to no difference at all [05:56] So I think it went well :) [05:56] did you record the actual difference with real numbers? if not, you might want to do that :) [05:56] Might be a good idea ;) [05:57] you think? :) [05:57] k so git+ssh://git.launchpad.net/~lubuntu-dev/ubuntu-seeds/+git/lubuntu.bionic crashed and burned but it was complaining about ssh stuff, bleh, [05:57] I'll try https://git.launchpad.net/~lubuntu-dev/ubuntu-seeds/+git/ in there [05:58] er [05:58] I did a thing [05:58] brb [06:01] um [06:01] download links no existy http://iso.qa.ubuntu.com/qatracker/milestones/384/builds/163340/downloads [06:07] O_o? [06:11] wxl: ohhhh I see why it's crashing and burning [06:11] The Git autodetection sucks XD [06:12] toldya [06:12] but if it fails, it should try git first [06:14] right... [06:14] hmm [06:15] how's that? https://codein.withgoogle.com/dashboard/tasks/5709752640208896/preview/ [06:15] wxl: lgtm [06:16] wxl: OH, one more thing I want to talk to you about, while this is going [06:16] wxl: Do you have a Pi? [06:16] 3 of them XD [06:16] wxl: What model/version? [06:16] one of each of the 3 :) [06:17] wxl: How would you feel about Raspberry Pi images for Lubuntu Next being on official infra? ;) [06:17] Shouldn't be too hard to figure out [06:17] i guess we tried this before or something like it and it didn't work out too well [06:17] But I know Kylin and Budgie were wanting to do it [06:17] wxl: oh? [06:17] do tell [06:17] maybe that's because it was the older chip [06:18] armhf vs arm64? [06:18] i'm not sure... i just know there are armhf testcases laying around from the He Who Shall Not Be Named days [06:18] oh [06:18] We did a Nexus thing I think [06:18] hm yeah i dunno [06:19] wxl: But I know Ubuntu Server has official daily Pi images [06:19] Wanna piggyback? :) [06:19] yeah but huh [06:19] https://ubuntu-pi-flavour-maker.org/ [06:20] RIght [06:20] i notice he's got core and server for pi 2 up there and they have "official" support [06:20] right [06:20] so it seems that there may be some bleedover both ways [06:20] Yeah, dunno how far he got [06:20] i'd definitely want to hook martin in [06:20] But I remember discussing with him about this at one point, we were thinking this was an 18.10 thing [06:20] But eh [06:20] but yes i'm into it [06:20] Ok cooool [06:21] afaik 2/3 are both armv7 so that should be good [06:22] 3 is armv8 [06:22] wxl: well look at the archive [06:22] actually there was a late version of 2 which was, too [06:22] We have arm64 and armhf [06:22] iirc arm64 is Pi3 [06:22] don't think so [06:22] A good way to test this is to grab Debian [06:22] Throw it on there :) [06:23] Hmmmmmmmmmmmm maybe I read wrong then wxl [06:23] idk [06:23] :) [06:23] there are arm chips that are server based that are 64 [06:23] https://wiki.debian.org/ArmHardFloatPort#Supported_devices [06:23] oh maybe armv8 IS 64 [06:23] hm [06:24] oh it is :) [06:24] OHHHHHHHHHHHHHHHHHHHHHHHHHHHHH [06:25] I FIGURED THIS OUT [06:25] * Cloning branch bionic of git://git.launchpad.net/~lubuntu-dev/ubuntu-seeds/+git/lubuntu/ [06:25] OHHHHHHHHH [06:25] So [06:25] I know what I gotta do now [06:25] no ssh eh? [06:25] Nah nah nah that's irrelevant [06:25] wxl: We can just have different Git branches [06:25] No more separate repos [06:25] Just new Git branch [06:25] :D [06:25] ah [06:26] OH so I know EXACTLY what to do now [06:26] Peeeeerrrrrffffffeeeeeccccctttttttt [06:26] https://wiki.debian.org/RaspberryPi3 [06:27] wxl: "The Raspberry Pi 3 is a version of the RaspberryPi which was released in February 2016. It contains a 1.2 GHz ARM Cortex-A53 CPU and hence is the first version of the RaspberryPi to support the arm64 architecture." [06:27] So I *was* right [06:33] wxl: YESSS IT WORKS [06:33] https://git.launchpad.net/~lubuntu-dev/ubuntu-seeds/+git/lubuntu [06:38] @julienlavergne Since having our seed in Git seems to work fine with minimal config tweaks, would you be OK with us deprecating usage of the Bazaar branch once I get an ack from the Release Team? [06:44] good job, @tsimonq2. re: pi, check that page and you'll see all sorts of issues specifically related to the particular hardware on the pi, i.e. the arm64 chip ain't the only thing. [06:45] wxl: hm ok [06:45] wxl: and thanks [06:48] https://askubuntu.com/questions/984043/unable-to-make-changes-in-bios-after-17-10-installation [06:48] wxl: Link that to the guy in #ubuntu-devel but I don't think it's a good solution :/ [06:48] he'll see it [06:48] ok [06:49] i've seen this previously; ye ole update the kernel and all is well [06:49] i DON'T think that will fix all devices from what i can tell, but some [06:49] neat https://github.com/teejee2008/ukuu [06:49] wxl: And btw if you hate that the manual tests are in Bazaar, ask flocculant about a Git conversion. git-remote-bzr works well :) [06:49] heh right [06:53] however, re: ukuu as a solution for the average user, from the MainlineBuilds page: "These kernels are not supported and are not appropriate for production use. " [06:54] anyways bed calls [06:54] wxl: Ok bai, have fun :) [10:50] @agaida, yayyy! not a stout but it'll do [12:41] rbesTO_fox was added by: rbesTO_fox [12:47] @rbesTO_fox, o/ [15:20] @rbesTO_fox, Hey, welcome! Happy Holidays! [15:20] was removed by: tsimonq2 [15:29] thanks, and mine congratulations) [15:29] @tsimonq2, thanks, and mine congratulations) [15:30] @rbesTO_fox, :) === RedWolf[m] is now known as redwolf[m] [21:24] !whois redwolf [21:28] @tsimonq2, Sure, thanks for this :-) [21:28] @julienlavergne, Cool :) [22:01] @julienlavergne!! I started with the "de-branded" icons [23:19] @VikingRedwolf, Nice :-) Let me know when the images / assets are available so I can do the packaging stuff [23:36] (Audio, 127s)http://vps.tsimonq2.net:9090//file_3181.mp3 [23:40] :)