=== giraffe is now known as Guest29863 [06:38] pitti: hiho, what is actually the convention on the autopkgtest users password (if ther is any) [06:39] for a test that runs with needs-root anyway (so I know I'm root) [06:39] I'd need to know its PW [06:39] I could of course just set one via e.g. usermod -p - if that is allowed and not breaking the test [06:39] cpaelzer: there isn't any really [06:39] IIRC we get the special root access via the tty [06:39] and that is it [06:40] so no policy beyond that special access via the tty then? [06:40] cpaelzer: if you need a password, the test should set it by itself (and declare breaks-testbed) [06:40] yep I'll do so [06:40] cpaelzer: special access via tty is only for qemu; there you of course need to specify the password on the CLI (but not in the test!) [06:40] I just didn't find a doc clearly stating on or the other, so I wanted to ask [06:40] thanks pitti! [06:41] cpaelzer: but setup-testbed actually creates a systemd unit that just offers a root shell on ttyS1 :) [06:41] which avoids knowing any password [06:41] so are we dropping support for running native i386 in 18.10? [06:48] seems not decided yet [06:48] I liked the "heavily warn, but allow it up until the next LTS" method. [06:51] seems safer to not allow it at all now, to avoid getting people stuck on short-lived releases [06:52] yeah, I'd drop it from 18.10 [07:02] pitti: Given that some LTSes are only 3 years, one really doesn't gain time. [07:15] still longer than "until next lts" [07:15] besides, kernel support is shared by all [07:16] Sure, just personally I'd prefer to roll with the normal releases until then. I do have some 32bit only stuff still. :3 [07:38] Unit193: what happened to 5 years? [07:38] pitti: Eg, Xubuntu never did that. Only 3. [07:38] Same with a few other flavors. [07:40] and what does that mean exactly? that they don't provide fixes to the desktop packages? everything else in main will still get updates [07:40] Except that all of Xfce is in universe, soo.. [07:40] so? [07:41] I said main, which has a lot of libraries I bet the xubuntu bits depend on [07:41] Of course they do. [07:43] and looks like it uses firefox as the browser, which is probably the most security sensitive app on it [07:43] Arguably openssl, I'd say. :> [07:43] still supported [07:44] I'm aware, yes. Point isn't "What's an LTS mean?" though. === caravena_ is now known as caravena [14:15] bdmurray: hey, any update on https://code.launchpad.net/~didrocks/ubuntu-release-upgrader/add_telemetry/+merge/345088? I added more metrics after our last week discussion with j_ibel [14:23] didrocks: Oh, I didn't see the updates. I'm not clear on the answer about the "From" distro. [14:23] didrocks: and when I said From I meant "To" [14:23] bdmurray: look at the README on https://github.com/Ubuntu/ubuntu-report [14:24] bdmurray: you have a lot more information reported than installer or upgrader one [14:24] one of them is "Version", which is basically the "To" [14:24] didrocks: What if it crashes before the upgrade completes? [14:25] bdmurray: no Upgrade telemetry file present [14:25] if the user can still boot a bionic session, they will have the other info [14:25] but not upgrader specific ones [14:30] didrocks: I'm sorry but I'm not following. Why would the upgrade telemetry file not be present? [14:30] bdmurray: well, you mentioned if "it" crashes, I think you meant "it" being do-release-upgrader [14:31] didrocks: I did [14:31] if do-release-upgrader crashes, then, the upgrade file isn't present as it's saved whenthe upgrade completes… [14:32] didrocks: So we'll only have information on succceses? [14:32] bdmurray: we send the information after first login on a new release for the user [14:32] so if the upgrade or install fails, we don't send those possibly corrupted metrics [14:32] this is where whoopsie should trigger and report the crash [14:33] but completely unrelated to hardware and other report info [14:33] Okay, and are you looking for me to just approve the MP? [14:34] bdmurray: yes, if you don't spot any obvious issue or typos :) [14:34] didrocks: Okay, thanks for talking it through with me! [14:35] thanks for the review! ;) [19:02] infinity, kees, stgraber, mdeslaur: TB posers meeting? [19:33] wxl: *nudge* [19:33] * wxl awakens from his slumber [19:34] wxl: Can you apply another month or two of "democracy, what democracy?" to https://launchpad.net/~techboard/+members ? [19:34] wxl: We're also chasing down the whole election business, promise. :P [19:34] ok [19:37] wxl: Thanks! [19:37] np [19:38] supposedly owners are supposed to get those messages but it didn't come. i'll mail the cc so they're informed [19:38] slangasek: We're good through Aug 03, if you can manage to get someone's attention about an election before then. :) [19:38] infinity: k [19:40] infinity: slangasek: to be clear, what's lacking? what resources do you need? can we/i help? [19:42] wxl: someone with authority needs to call for candidates and run an election. That's ultimately probably only sabdfl, but perhaps the CC can help [19:44] slangasek: i'll ask the cc about that and get back to you [19:44] slangasek: anything else? [19:47] wxl: that's all, thanks :) [20:08] slangasek: infinity: do you have an easy way of generating emails to send to the appropriate ubuntu developers for the tb elections? [20:09] wxl: I do not [20:09] oh nevermind [20:09] i found it [22:22] is anyone here an admin or moderator for the ubuntu mailing lists? [22:22] I cant subscribe to ubuntu-bugs to save my life [22:23] ive tried to send emails to subscribe to the mailman system, ive tried emailing the admin of the list. nothing [22:23] ive checked my junk, spam, everything. I'm not getting emails from the list [22:23] and, i cant subscribe to any ubuntu list [22:24] did you use the form elim_garak https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs ? [22:24] yes [22:24] never get the confirmation email [22:24] was hoping an admin or mod could manually add me or test sending me something [22:24] well tht wasn't one of the things you mentioned above :) [22:24] i'd advise checking with #canonical-sysadmin as that sounds like a general issue that may affect more than your ability to subscribe [22:26] ty will do