[00:07] I'd think it was just my VM environment if it wasn't for the file names of the .efi files. I should also download an ISO that does ship the 32-bit EFI files and see if that works in the VM (I think Fedora does that?) [00:08] Yeah, Fedora has a "BOOTIA32.EFI" file in there along with other ia32 files. [00:09] Yeah, good idea [00:16] Fedora is trying to boot at least. It's hanging early in the boot process, but the bootloader starts and is able to load the kernel and initrd and kick off the boot process. [00:19] Sup guys [00:19] Simon Quigley (Developer): Not too bad, how 'bout you? [00:19] Simon Quigley (Developer): Fighting with an EFI bug ATM. [00:20] arraybolt3[m]: Towards the tail end of the personal stuff going on, getting there... thanks [00:20] arraybolt3[m]: Oh nice, you found the only difficult part of our Cala settings package >:P [00:20] Simon Quigley (Developer): Worse than that. Found a mess in the ISO build itself. [00:21] Last time I touched that I chugged about two or three monsters. I understood that code exactly once. I do apologize for my messiness. :P [00:21] arraybolt3[m]: Which stage? [00:21] Dan Simmons: Fedora boots with 64-bit EFI, but it at least tries to boot with 32-bit EFI. Ubuntu won't even try. [00:21] Simon Quigley (Developer): GRUB bootloader. [00:21] I guess it never worked? [00:21] Oooooooh [00:21] Weird [00:21] Simon Quigley (Developer): There aren't any 32-bit EFI files on the ISO, so 64-bit systems with a 32-bit EFI don't work. [00:22] (PCs like certain Asus EeePC's are therefore locked out of using Lubuntu.) [00:22] Which was contrary to my memory. So much for that. [00:22] Dan Simmons: I'm not sure what's wrong, but my Fedora ISO won't even boot all the way on 64-bit EFI, and I even checked it for integrity 😦 [00:23] I wonder if my VM config is messed up. [00:24] Even Lubuntu doesn't like it. OK, I botched something... [00:25] There we go, QXL graphics was the missing link. [00:27] But Fedora still doesn't work with my hybrid EFI. So I think Lubuntu is messed up, but a VM in my particular config isn't sufficient for testing this for real. [00:31] That's fair. I'd hesitate to file a bug directly due to that. However if we get somewhere further on the Discourse thread we could have the OP file one. [00:31] Too bad. I really thought this trick would work. [00:32] I thought you were on to something too. [00:33] The kernel just always hangs. Not panics, just hangs. Maybe it's something wrong with Fedora's kernel in particular, but I dunno. [00:34] (I guess maybe it's one of those situations where you have to let it sit for 10 minutes before it boots? I'll just leave it for a good long time and see if it works. I don't have high hopes, though.) [00:36] At any rate, Simon Quigley (Developer) I had a crazy night and only managed to get 1 PR properly made, but I'm on the verge of a second and third ready to be merged. [00:36] I have to go afk right now, but I'll be back to give the link in just a bit. [00:58] Simon Quigley (Developer): https://github.com/lubuntu-team/qtermwidget-packaging/pull/1 [00:58] Pull 1 in lubuntu-team/qtermwidget-packaging "Backports/jammy" [Open] [01:41] Dan Simmons: I just realized I wasn't properly following the directions for doing the EFI boot, so I'm going to try to actually do what the guide I was following said. [01:43] Nope, fail. Oh well. [01:45] Simon Quigley (Developer): https://github.com/lubuntu-team/lximage-qt-packaging/pull/1 [01:45] Pull 1 in lubuntu-team/lximage-qt-packaging "Backports/jammy" [Open] [01:46] Simon Quigley (Developer): If my PRs are bugging you, feel free to tell me to hold off and I'll just keep track locally. [01:53] "Simon Quigley (Developer): If my..." <- sleep 12h && fullsend [05:40] Just leaving this here for whoever sees it next. The LXQt stack badly needs a full copyright file audit. This is going to be the second or third package I've had to totally rebuild the copyright file of, and I suspect I've probably missed some. I don't think there's any way I'm going to manage to do the whole backport and audit before our sprint on the 7th, so I'm not going to do that yet, but it needs done eventually. [05:41] (I mean, I'm going to try to finish the backport, and I think I'll succeed, but the audit on the copyright files will need to wait.) [05:41] ack & thank you for your diligence arraybolt3[m] [05:42] No problem. Thank you! [08:08] (Something to consider, I just found a tool called FOSSology that may help immensely with copyright file updating and auditing. It's a Docker-based web app, I'm thinking of trying it out and if it works well on my end and would work well for everyone, maybe we can talk our friendly local chaotic sysadmin into setting up an instance for everyone to use?) [08:11] * guiverc smiles [12:00] Dan Simmons: Oh. My gosh. You are not going to believe this, I just got a mixed-mode EFI VM to boot. I had assigned too high of system specs (was doing 8GB RAM and 4 CPU cores), which I guess was confusing the EFI. I dropped down to 2 GB RAM and 1 CPU core, and I just got a Debian multiarch ISO to boot with 32-bit EFI on a 64-bit VM. [12:04] Oddly enough, the VM locks up if you use 2 CPUs. So mixed-mode EFI VMs have to be single-core AFAICT. But that means we can test it now, and if we can test it, we can hopefully make it work. [12:05] I've also confirmed that Lubuntu 18.10 does not work with mixed-mode EFI, even with a working VM config. [12:20] Lubuntu 19.04 also fails with mixed-mode EFI. [12:25] Interesting. [12:27] (I do find it odd that QEMU can't pull off mixed-mode EFI with more than one CPU core when the Intel Atom CPUs used in this configuration appear to be 2- and 4-core chips...) [12:27] I've got a strong feeling it will be hard to persuade folks to build iso's to support such an arrangement. [12:28] One Google search reveals that there's a lot of people out there who would benefit from having this work. Which makes me hopeful, at least. [12:30] I mean, it can't hurt to try and write a bug report, right? I could also start a conversation on #ubuntu-discuss and see what people think. [12:31] It can't hurt. [12:32] OK. I'll save it for after the sprint we're planning so I can spend more time on things that for sure matter. [12:32] * arraybolt3[m] just figured out what terminal my SSH instance was running in... 🤦‍♂️ [12:33] arraybolt3[m]: That makes sense. I am curious to see what others think too. [14:32] "sleep 12h && fullsend" <- Ready to fullsend whenever you're ready to fullreceive. [17:26] There's only 8 packages left to be backported! We're almost there! [17:26] Looking at bug 1977465, which proposes to change #debian to #lubuntu in the default configs, what about users of other variations of Ubuntu (say default Ubuntu or Kubuntu)? Do we assume that since the program is a Qt one, we can simply consider it "belongs" to Lubuntu? [17:26] Bug 1977465 in quassel (Ubuntu) "Quassel defaults to the Debian IRC server, libera.chat isn't in the configuration at all." [Undecided, Confirmed] https://launchpad.net/bugs/1977465 [17:27] nteodosio: That's a good point, Ubuntu Studio also ships with Quassel. I'm not sure if there's a separate config package or not. [17:28] There isn't. [17:28] A quick apt-cache search reveals that there does not appear to be separate config packages. [17:28] Eickmeyer: Beat me to it. [17:28] Would it be a good compromise then to connect to both #ubuntu and #lubuntu? [17:29] Or #ubuntu-studio, better said? [17:29] *#ubuntustudio [17:29] nteodosio: That's probably for Eickmeyer and Simon Quigley (Developer) to decide, they're the distro leads who ship Quassel. But having anything distro-specific shipping in Quassel seems like a bad idea to me, since people using other flavours might also install Quassel. [17:29] Easier said than done. [17:30] Random idea - create config packages for Quassel sorta like how we do for calamares-settings-ubuntu, and have each one have flavour-specific config? So have Quassel ship with #ubuntu by default and then have the config packages add #lubuntu to Lubuntu and #ubuntustudio to Ubuntu Studio? [17:31] arraybolt3: Again, easier said than done. It would have to overwrite Debian's config. [17:31] Ouch. [17:31] (That would mean we'd be looking at three additional packages at a minimum, plus an Ubuntu delta? Yikes.) [17:31] Yep. [17:32] #ubuntu supports all the flavours, and is where most of the action is, so it would probably be easiest and best to make Quassel point to #ubuntu by default. Then we only have an Ubuntu delta to manage. [17:32] And then taking over maintainership, meaning constant monitoring of the upstream. [17:33] One of the reasons Ubuntu Studio ships Quassel by default is because Konversation is hard-patched to go to #kubuntu by default. I wasn't happy about that, so Quassel it was. [17:33] arraybolt3[m]: I agree with that. TBH I think the right thing is to join no default channel. [17:34] nteodosio: I agree with that approach over the default channel approach. It's relatively trivial to add a server, and one can simply ask the upstream to add a libera configuration. [17:35] Eickmeyer: That's a good idea, that allows us to shift the responsibility for maintainership to Debian if they're willing to accept it. [17:36] (But even if they don't accept it, one tiny Ubuntu delta won't be too much to deal with, just throw it in as a Quilt patch, right? If this sounds insanely ignorant, that's because is probably is...) [17:36] Yeah, we have a tiny ubuntu delta now for whatever reason. It didn't used to be that way, but it is now. [17:36] Looks like it's due to an apparmor profile. [17:39] Eickmeyer[m]: Not sure if this is clear, but the behavior of joining #debian is in a debian/patches. If we are syncing the package from Debian, adding Libera upstream doesn't avoid a delta, does it? [17:40] It doesn't. I might be able to remove the patch (if it's a patch), but doing an SRU on something this trivial seems like a lot of work for something so silly. [17:41] I mean, as an Ubuntu Studio seeded component, I'm within my rights to do it. [17:41] Eickmeyer: We have backports. Not that that's the ideal solution, but it might be less work than a full-on SRU. [17:42] arraybolt3: Backports is kinda reserved for less-than-trivial things, like full-fledged version updates and stuff like that. [17:43] Yeah, it's a patch. That's annoying. Ugh. [17:43] Eickmeyer: Hmm. K. And we can't use PPAs - why does it seem like fixing paper-cut bugs can be like navigating the inside of an nVidia mystery... [17:43] * Eickmeyer[m] reluctantly prepares an SRU [17:44] * arraybolt3[m] yawns and goes back to fighting with the LXQt stack backport [17:45] I'm curious to find what will come into the "regressions potential" section of it :) [17:46] nteodosio: I guess it might cause the people who actually use #debian to open Quassel one day and be like, "Ey! Where'd my channel go? /join #debian" and that would be the end of it. [17:47] nteodosio: HAHAHAHAHA I've made sillier regression potential sections. I did one with a plasmoid one-line change to have it re-run a shell script in case of a failure that said, "I mean, I suppose it could completely crash Plasma, but that seems unlikely as the script literally just ran prior to being run again." [17:48] Regression potential: This could cause your computer to burst into flames, but only if there's a serious hardware fault that should have lit it up months ago. [17:48] arraybolt3[m]: Technically not a regression though, just an upset user. But I think users of IRC know better, that's why I would say the Debian patch is not warranted. [17:49] nteodosio: Well, I get the idea of making live chat support a hardwired feature. Not everyone knows what IRC is, they just know they can get chat support for their OS through it. You don't want to figure out how to configure an IRC client when your OS is busy having the time of its life without regard to what you want it to do. [17:50] Thus why I'm for including #ubuntu by default. [17:50] arraybolt3[m]: Convinced! [17:51] I get both sides though, and I could live with either. [17:51] Meh, I can change the patch to #ubuntu on libera pretty easily. [17:51] I mean, it'd be trivial. [17:51] As it is, a user goes to get live chat support, stumbles into Debian with a Lubuntu question, figures out how to register a nick, gets told to go to #ubuntu, and then has to figure out how to configure their IRC client. [17:52] Eickmeyer[m]: That what I was thought when I found the bug =P [17:52] arraybolt3[m]: Yeah, it's good to put oneself in newcomers shoes [17:53] The regression potential will be something like, "Users of Ubuntu who think they're on a Debian system might be irked they're no longer going to Debian support, but this is not likely." [17:53] nteodosio: Double take here, you found KGIII's bug, or you are KGIII? [17:54] Eickmeyer[m]: That would be like saying "Pop!_OS users might be annoyed that they're no longer being told their in the wrong channel when they come into #ubuntu." [17:54] (That's a compliment on the humor value, btw.) [17:54] Hehehe [17:55] And people who are Ubuntu users but offer Debian support in #debian should be knowledgeable enough to get their IRC client back to where it was. [17:56] arraybolt3: And to the right network (OFTC). [17:56] True. [17:56] arraybolt3[m]: Not KGIII, I found the report when I were on my way to report another one. [17:59] Eickmeyer[m]: Ha, while you are at it, you may well as see bug 1872204. [17:59] Bug 1872204 in quassel (Ubuntu) "quassel defaults to Lubuntu specific settings" [Undecided, New] https://launchpad.net/bugs/1872204 [17:59] Bottom line: There's no such thing as satisfacting everyone [18:00] WTF? [18:00] He suggested #ubuntu as the right option too. [18:01] Yeah, so, I'm going to "Won't Fix" on kubuntu-settings, lubuntu-default-settings, and dup that to the SRU I'm writing for quassel. [18:02] He's on the bug triage team too and should know better. [18:02] Of course, he's not a packager, so there's that. [18:05] Sorry, what should he know better? Are you refering to the reporter? [18:05] nteodosio: Yes, but I could be wrong. [18:06] https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/1980687 in progress [18:06] Launchpad bug 1980687 in quassel (Ubuntu Kinetic) "[SRU] Quassel should not have #debian as default channel in Ubuntu" [High, In Progress] [18:06] Sorry I am late to the party but I think #ubuntu makes sense. It is at least on the right network. [18:07] kc2bez[m]: Working on the patch/upload right now. Should have it to Kinetic soon and queued for Jammy soon as well awaiting SRU approval. [18:07] * Eickmeyer[m] is fast on these SRUs, has practice [18:11] Eickmeyer[m]: Out of curiosity, why didn't you add the SRU to the original bug report? [18:11] nteodosio: I already had the original SRU written, so it was too late, and the original bug report was against Focal, not Kinetic or Jammy. [18:12] I'm not going to SRU to Focal. [18:12] Focal has < 1 year of support left (9 months, actually). [18:15] I agree kinetic and jammy make sense [18:19] Ah, y'all are gonna fix the bug in Quassel. That'll be nice. [18:20] The config from the previous version should fix it, but I am not a developer. I just find your bugs. [18:21] kgiii: The problem is that both Ubuntu Studio and Lubuntu are seeding it, so pointing to #lubuntu doesn't cut it anymore. [18:21] So, I'm fixing it to point to #ubuntu. [18:22] It should point to Lubuntu - or it did. [18:22] It did, but again, that's not a good idea anymore. [18:22] It used to point you to #lubuntu - on the proper server. [18:23] kgiii: Ubuntu Studio ships Quassel by default, we don't want it pointing to #lubuntu:libera.chat . [18:23] kgiii: I'm the flavor lead for Ubuntu Studio. You're not reading what I'm saying, are you? [18:24] That's just a hassle all around. That's not very helpful. The user will be told to join another channel to get support. Surely there's a better choice. [18:25] kgiii: #ubuntu supports all flavours, Lubuntu and Ubuntu Studio included. [18:25] If that were accurate, we'd have no need for #lubuntu. [18:28] kgiii: Not true, many problems with Ubuntu flavours can be solved in the main chat. It's only where you get into the specifics (like a KDE issue or an LXQt issue) that the main channel starts to not be so great. If we don't want to do a boatload of work, and want to give users the best experience possible, this is the best solution. Ideal? No. But close, and it doesn't take a monumental effort. [18:31] So, rather than send 'em to the people that know Lubuntu best, you're going to waste new user's time and add confusion instead of doing a 'boatload of work'? Is it possible to package flavor-specific versions of Quassel? [18:32] kgiii: That's what I suggested, but that would be a monumental amount of work. Being in "developer-in-training" land, I just showed up here and my plate is already full up and falling over, so factoring in our own workloads is important. [18:33] kgiii: I need to remind you that everyone who works on Ubuntu Studio and Lubuntu is a volunteer; everyone is devoting their time to do it, nobody is paid to do it. Carrying an attitude like that is very offputting. We want to minimize the amount of time we have to take care of packaging things. Packaging two versions of the same application in the same archive is also not allowed. [18:34] Sorry if it's off-putting, but this hasn't been a problem for the year or so that we've had it like this. Maybe I'm underestimating the time it'd take to do this differently? [18:35] You're greatly underestimating the time and effort it takes to do this. [18:35] My main concern is the end-user's experience. I don't want them to have a bunch of friction to learn/appreciate Linux. [18:35] kgiii: It would take a lot of time initially, but then additionally, it would make us the maintainers of the extra packaging, which would result in an extra continuous workload, overall reducing the time we have for more important things and lowering the quality of the distros. No one wants that. [18:36] kgiii: I've seen plenty of Kubuntu people in #ubuntu, and things go just fine. I think I redirected one guy once. Plus, when we're pointing to the right server, switching channels is as easy as "/join #lubuntu" and you're done, as opposed to "reconfigure IRC server, reg nick, figure out what I'm looking at in the settings, then /join #lubuntu. [18:36] (And I'm not sure I should have redirected that one guy.) [18:37] If there's no other choice, there's no other choice - but it's gonna suck for at least a subset of people who are trying to get help - and not just with Lubuntu, but also with Ubuntu Studio. [18:37] kgiii: You might look at the #ubuntu support channel, it's not as bad as you think. I'm there very frequently, and things go just fine. [18:38] I think you overestimate the skills of new users and the familiarity people have with IRC. Folks aren't familiar with IRC anymore. Again, if this is how it must be then it must be. [18:38] I'm in there right now - I read it most every day. [18:38] I've done so for quite a while now. (I don't help, but I skim through.) [18:53] Here's the other thing: What if someone, other than a Lubuntu or Ubuntu Studio user, wishes to install Quassel? It's not a Lubuntu package or an Ubuntu Studio package. Neither team owns it. It should be as generic as possible. [18:53] Anyhow, kinetic and jammy packages uploaded. Kinetic should be done soon, awaiting SRU approval for Jammy. [18:54] So are some packages owned by particular teams? [18:54] In the Ubuntu world? Not really. [18:55] So the statement "neither team owns it" is always true? [18:55] Generally speaking, yes. [18:56] Is there a package that you'd say "this is Lubuntu's", apart from config ones? [18:56] However, some teams have "ownership" of certain things. Such as the Lubuntu team has the LXQt components. [18:56] Some teams do watch over certain packages more than others (for instance, Lubuntu generally babies LXQt), but anyone could install LXQt on their system if they wanted to and knew enough. [18:56] Eickmeyer: How do you keep beating me to stuff? I type 90+ WPM! [18:56] And Ubuntu Studio generally babies the Multimedia packages. [18:56] arraybolt3: I'm quick too. [18:57] LOL [18:57] Fair. [18:58] I really can't keep up with you two. Have to be really fast or the message I'm responding to drifts away [18:58] (Exaggerated, but still :) [18:59] nteodosio: If you're on Matrix, there's a little "Reply" button you can use to keep track of what you're talking about and who you're talking to. I use Element as my Matrix client. [18:59] Ah, I'm on (guess what?) Quassel [18:59] I'm a MOTU (master-of-the-universe, gives me upload privs to Universe and Multiverse), which means that, while I'm on the Ubuntu Studio team and the Kubuntu team, I can jump-in and help with other teams when I'm needed. Case in point: this quassel issue and the calameres issues from time-to-time. [19:00] Talk about a cool title! [19:00] nteodosio: Well then good luck and type fast :) [19:01] (OK, that's a joke.) [19:01] (The type fast thing, I mean.) [19:01] lol yeah I got it [19:02] Agreed, it is a cool title. I still feel weird in the middle of people who do all this stuff when I'm not even to Lubuntu Member yet (though I'm reaching for it). [19:02] Yeah, I have a few different hats/titles with Ubuntu. [19:03] arraybolt3[m]: I think everyone starts at that point [19:03] It's part of the process, right? [19:03] You've got MOTU, Simon's got Core Dev and Debian Developer, Chris has Lubuntu Council and Ubuntu News, and yet you're fine with training someone who has... Lubuntu contributor? That's not even a title. [19:03] Thank you all. [19:03] (And Dan's got Lubuntu Council and Lubuntu Developer.) [19:04] nteodosio: Yeah, but for me, who hasn't done very many big projects in life, this is huge. [19:08] Thomas and I also have Ubuntu Community Council. [19:08] Wow. That's so cool. [19:08] Eickmeyer[m]: Nerd. :P [19:09] Simon Quigley (Developer): Hey, you're here! I have 11 or 12 PRs to dump on you! [19:09] tsimonq2: Dork. [19:09] Simon and I know each other IRL. [19:09] arraybolt3[m]: Hold your horses I'm not at a computer yet ;) [19:09] Simon Quigley (Developer): Just going gung-ho on fullsend LOL. [19:10] I'm not quite ready to throw all the links out there yet either, though, I'm just finishing up with lxqt-session. [19:10] Simon Quigley (Developer): Gave everyone here a very special present: https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/1980687 [19:10] Launchpad bug 1980687 in quassel (Ubuntu Jammy) "[SRU] Quassel should not have #debian as default channel in Ubuntu" [High, In Progress] [19:12] Eickmeyer[m]: Do you have upload access to that package? [19:12] Simon Quigley (Developer): I'm a MOTU now. [19:12] Eickmeyer[m]: Since when?!? Why didn't you seek my endorsement my friend :) [19:12] I would have loved to grill you ;P [19:12] I tried, but you were crickets. [19:12] Yeah, that happened during your hiatus. [19:13] It's been about a year and a half-ish? [19:13] Eickmeyer[m]: I like to call it my partyatus :P [19:13] yes I was partying daily during that time [19:14] Clear packaging mind > partying packaging mind :P [19:14] But regardless... Congrats :) very belated [19:14] ha, thanks. teward helped me get there, a lot of credit goes to him. [19:15] Eickmeyer[m]: Wow, for a second I thought teward had actually joined Matrix when I saw that tag. [19:15] Nope. Oh well. Dead fish still incoming. [19:15] I'm glad in general that he's been able to fill in a lot of the gaps for me [19:15] So the two guys who made my two favorite operating systems are friends. That's odd, and really cool. [19:16] arraybolt3[m]: We all know each other in some way, would it surprise you to know that I actually have met vorlon in person before? [19:16] No, since I kinda read that you said that before. 🅰️ [19:17] (Why does matrix keep doing that to :-P ?) [19:17] :-P != 🅰️ [19:17] I was in Portland for exactly 48 hours and I was able to keep sign with 2 Debbie developers and 2 members of the boot to security team [19:17] #BlameElement [19:18] tsimonq2: Don't you guys love talk to text? [19:18] You mean talk to Texans. [19:18] Yeah. I was just browsing around in PC man of them cute just the other day, looking for my deli ann phials. [19:20] (Attempted to intentionally mangle text to look like talk to text, now I'm getting crickets, what happened...) [19:20] arraybolt3[m]: I just didn't see it yet [19:21] tsimonq2: I'm only just now realizing that this is talk to text, I thought "Debbie" was intentionally short for "Debian"...) [19:21] I did raise an eyebrow at "boot to security team". [19:21] arraybolt3[m]: Ubuntu Security Team [19:22] OK, so now that I've thoroughly derailed the topic of this channel... I'll be back in a few with 12 PRs ready. [19:23] I boot to security team all the time. 👀 [19:23] Eickmeyer: Yeah, who needs security? It's not like hackers exist or anything. [19:24] Nah, not at all. /s [19:24] * arraybolt3[m] uninstalls AppArmor and logs in as root [19:25] Oh, Simon Quigley (Developer) , thought you'd get a kick out of the quassel SRU regressions section: "Users of Ubuntu who think they're on a Debian system might be irked they're no longer going to Debian support, but this is not likely." [19:37] Simon Quigley (Developer): For whenever you have time, here's the PRs. I think there's only 8 or 7 packages left before the backport is complete. https://pastebin.com/J4tSNUxd [19:37] s/8/7/, s/7/8/ [19:38] (This way I don't end up afk when you're ready and messing everything up.) [19:53] Simon Quigley (Developer): Oh, also, it's been more than four days since I tried to sign up for Debian Salsa and I've still not gotten approved. I was going to send an email to salsa-admin@debian.org (which was listed as a support email address on Debian's website), and I was wondering if it would be OK to Cc you on the email so you can see what I wrote and maybe back it up. I'm happy to pastebin the email first so you can review [19:53] it before I send it if you think that would be good to do. [20:30] * ready and thus end up with me messing everything [20:39] "Simon Quigley (Developer): Oh..." <- tsimonq2@debian.org [20:40] Oh, OK, thank you. I was going to use the Ubuntu.com email, but I'll use the Debian one instead. [22:32] Thanks :)