=== tomwardill_ is now known as tomwardill
=== lukedashjr is now known as luke-jr
=== tolecnal_ is now known as tolecnal
[12:49]  * cjwatson files https://bugzilla.mozilla.org/show_bug.cgi?id=1739992 for the "Bad bot, go away!" errors that several people have reported with Firefox 94
[13:34] <cpaelzer> hi, is it possible that currently our ppc64 builders are sometimes ppc9 (https://launchpad.net/builders/bos02-ppc64el-016) and sometimes ppc8 (https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4703/+build/22384104)?
[13:34] <cpaelzer> wrong link for the latter
[13:34] <cpaelzer> https://launchpad.net/builders/bos02-ppc64el-002
[13:35] <cpaelzer> Both say they are "ppc64el (virtual)" but with software that needs new CPU I got on the latter "ERROR: Problem encountered: Compiler does not support POWER8 platform" 
[13:37] <cjwatson> cpaelzer: Yes.  We're trialling the power9 builders with the expectation of turning off the power8 ones in a week or two
[13:38] <cpaelzer> ok cjwatson, good to know - that explains why I get one or the other result here
[13:38] <cpaelzer> thanks!
[13:38] <cpaelzer> (that or other things in the archive changed between now and this morning)
[13:39] <cjwatson> cpaelzer: Individual builders (e.g. bos02-ppc64el-016) aren't pinned to any particular compute node, though
[13:39] <cjwatson> It'll be different from build to build
[13:40] <cjwatson> cpaelzer: "Compiler does not support POWER8 platform" seems like a weird error.  Have you checked with toolchain maintainers to see if that's expected?
[13:40] <cjwatson> I would expect POWER9 CPUs to still be able to build for POWER8
[13:40] <cpaelzer> cjwatson: I only started to see the error, haven't checked in detail yet or talked to foundations
[13:42] <cjwatson> Foundations should be aware of the hardware changes but I don't know how much they've dug into this sort of thing yet
=== cpaelzer_ is now known as cpaelzer
[14:19] <axino> hello
[14:21] <axino> s/!!/
[14:22] <axino> hello
[14:22] <axino> it looks like emails sent by Launchpad with subject "PPA access cancelled for <ppa>" are sent with a bad enveloppe "From" (root@localhost)
[14:29] <cjwatson> axino: I can't see an obvious reason for that (though am in a meeting) - is it possible that ackee's MTA is messing with that?
[14:57] <seb128> cristiangsp, hey, what's the status of jammy translations opening now, following https://answers.launchpad.net/launchpad/+question/699114
[15:01] <cristiangsp> seb128: waiting on the first run of the crons this week to check that everything is fine. Said that there has been a couple of things done already: jammy translations are not hidden now and the translation focus has been changes to "ubuntu jammy"
[15:17] <seb128> cristiangsp, right, why reading the wiki was the end of the opening process so I was wondering if that meant someone forgot to email the translators
[15:19] <cristiangsp> yeah, the last bits I mentioned were not done by us so before sending the final communication I was waiting to do the check after the first ones are generated and checked
[15:19] <cristiangsp> said that, probably we would want this one merged too: https://code.launchpad.net/~seb128/langpack-o-matic/jammy-map-update/+merge/410547
[15:21] <seb128> cristiangsp, thanks for the remainder, I merged that one now
[15:21] <cristiangsp> thanks
=== lukedashjr is now known as luke-jr
[23:29] <chaslinux> So I tried to create a launchpad account for my work email last Friday in order to report bugs, but I didn't seem to get a verification email. I checked our mail server and it looks like nothing reached our server. I even whitelisted noreply@ubuntu.com on the server and nothing. Wondering if we somehow got on an old blacklist that ubuntu is using?
[23:42] <guiverc> trying to login to launchpad (bug report) & getting "Bad bot, go away! Request aborted" on testbox (after clicking "Yes, log me in" page)