=== chihchun is now known as chihchun_afk === jamespage_ is now known as jamespage === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === LocutusO- is now known as LocutusOfBorg === Ionic is now known as Guest79890 [09:43] The "reset password" page that I reach after I've entered my e-mail and gotten the reset link doesn't let me submit the new password. Clicking the button just does nothing. I'm not sure where else to report this. [09:44] I get "An invalid form control with name='email' is not focusable." in the js console. [09:47] Tried in both Firefox and Chrome. Didn't check the js console in Firefox, but the behaviour is the same. [09:57] soren: that's an SSO problem rather than LP as such - can you email as many details as possible to isd-support@canonical.com so that it goes into the SSO support queue? [09:58] cjwatson: Will do. Thanks :D === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun [13:58] Hello, i have a ppa question [13:58] I have a personal ppa [13:58] Is it possible to allow others to upload to it [13:59] or, if i create a different ppa, auto-migrate users to it? [14:00] No way to auto-migrate. There is an undocumented command-line-only way to add extra upload ACLs [14:01] cjwatson: oh, spill the secrets! [14:02] lp:ubuntu-archive-tools, edit-acl -A ppa:OWNER/ubuntu/PPANAME -p NEWUPLOADER -t upload add [14:02] IIRC [14:02] sweet [14:03] thanks === chihchun is now known as chihchun_afk [14:51] So, I'm actually super lame at .deb packaging and ubuntu in general, but I'm maintaining a PPA, and I'd like to do so a bit less ad-hoc. [14:52] What is the current state of the art for how to maintain a ppa [14:52] Like, can i host a git repo at launchpad and use some PR workflow thing for updates which gets auto-built into the ppa? [14:56] It sounds like https://help.launchpad.net/Packaging/SourceBuilds may be what you're looking for [14:57] Though some people do this sort of thing with Jenkins jobs or whatever, depending on the rest of their CI workflow [14:57] Well, i have a CI workflow for the upstream [14:57] All i want to automate is the ubuntu packaging [14:58] (but that involves having the CI system having upload creds, which isn't necessarily great) [14:58] (this being flatpak ftr) [14:58] Like, i don't want this to build a .deb each upstream commit [14:58] right, so the recipes feature linked above can do that sort of thing based on an LP git repo (which you can in turn automatically import from somewhere else) [14:58] But, when there is a new release i want to be able to push to a repo and have it build a new release [14:58] you could have it build from a particular branch which isn't upstream master [14:59] https://help.launchpad.net/Code/Git#Mirroring_repositories_from_other_sites is the auto-import feature for git repos [14:59] Ok, so lets say i create a git repo on launchpad, importing the upstream github repo [14:59] then i create a branch for each ubuntu release and add the debian/ dir? [15:01] I'd be happy to help in more detail tomorrow; today we're trying to do an Ubuntu release which is kind of consuming all my attention [15:01] maybe have a look through the help pages in the meantime? [15:01] oh, no worries :) [15:01] I kinda expected there to be some good example project i could just steal the setup from [15:01] Can't be a completely unexplored area [16:23] LP admins, do you have a list of mail server hostnames/IPs which Launchpad uses to write the emails for bug comment messages? I.E. if I add a comment to a bug, others on the bug get an email from my address (which will fail SPF and DKIM checks currently) [22:43] a bug/incompatibility in how LP sends out emails with regards to the "from" field would be a bug filed against LP itself, correct? [22:43] just want to make sure I am remembering things proper :P [22:43] *before* filing a bug that is [22:48] teward: LP emails have a canonical.com envelope sender so don't fail SPF or DKIM checks. But some domains have very restrictive DMARC policies which impose SPF and DKIM restrictions on the From address, which isn't what they were originally intended for. https://bugs.launchpad.net/launchpad/+bug/1589693 is the relevant bug. [22:48] Ubuntu bug 1589693 in Launchpad itself "Make Launchpad DMARC Compliant to avoid Launchpad mail considered spam" [Undecided,New] [22:52] wgrant: you mean like mine. [22:52] i was about to open a bug, thanks. I have a completely evil suggestion as to solve the problem, but not the coding expertise to actually solve it [22:53] and I have a prime example of "Noncompliance" here today - do you want me to add my specific case/details to the bug, and carve out the relevant email headers? [22:53] (to include for technical information/reasons) [23:08] wgrant: I can say this with some certainty: a larger and larger number of companies' IT Security teams are implementing DMARC, including financial institutions and governments (at least here in the USA) [23:09] and LP is noncompliant in DMARC handling, because of this. A fun fact to note is that ListServ systems are prime examples of the noncompliant systems. (I expanded on this in my comment on the bug, by the way, with some more technical details) [23:09] teward: We are completely aware of the problems that DMARC causes. [23:09] ack