User1: luke-jr: Your sums are wrong there - you have 4*5 builds, yes, but each build produces six binary packages (bitcoin{-qt,-tx,d}{,-dbgsym}), so that's 4*5*6=120
User2: Can I get some help with sorting out a blueprint and connecting it to status.ubuntu.com please? I never got familiar with how it works, what ACLs control what, etc. Right now we have https://blueprints.launchpad.net/ubuntu/+spec/servercloud-aa-server-core which I'd like to "take over" and hook up.
User2: Not sure who to ask.
User1: I have very much forgotten how status.ubuntu.com works
User1: One of the EMs or former EMs might remember, maybe slangasek?
User2: What's an EM?
User1: engineering manager
User2: Ah. Thanks!
User2: I guess I'll have to wait until next week (which is fine).
User1: You can configure whether those are built/published in the "Change details" page of your PPA, in case they're simply useless to you
User1: No, it's just for building; there's no defined way to propagate that to sources.list
User1: Yeah
User1: Correct
User1: If the build is otherwise exactly reproducible then you can, but there are lots of ways that might not be the case that are outside of Launchpad's control
User1: It's not specific to PPAs as such; you "just" need to control the environment well enough
User1: Nothing stopping that being done for PPAs
User1: It'd be the same basic chain of tools as https://reproducible-builds.org/ has been doing for Debian
User1: Of course any change in build-dependencies potentially invalidates it, so if you were doing that seriously then you might want to change the PPA's dependencies to use the release pocket only rather than the default (including updates), or possibly release+security for a compromise between having security updates and slowing down the rate of change
User1: It'd likely also require backporting the basic packaging toolchain changes from the Debian reproducible-builds folks (dpkg, debhelper, etc.) and using those as build-deps in the PPA in question
User1: So a certain amount of work, potentially, but nothing about PPAs prevents it
User1: It's more about what's available in Ubuntu
User3: LP git is being a bit flaky. Permission denied (publickey).
User3: fatal: Could not read from remote repository.
User3: Please make sure you have the correct access rights
User3: and the repository exists.
User3: the try to push again, and it works
User4: User3 i'm seeing the same thing
User4: i thought it was my local network
User3: User4 nope. I also got a weird error try to view a git repo in a browser. did not keep the error message though, as assumed it was a one off glitch
User3: and get this on an auto-merge cascade on our CI https://kci.pangea.pub/job/merger_akonadi/766/console
User3: push 'origin' 'kubuntu_xenial_backports' 'kubuntu_stable' 'kubuntu_unstable'  2>&1:fatal: remote error: Connection was refused by other side: 111:
 * acheronuk clicks the retry button
User4: yeah i've got both connection refused and permission denied
User4: User1 ^^
User4: having problems uploading packages too
User3: User4 an error, or the upload seems to go ok, but LP eats it without trace?
User4: Rejected:
User4: [lplibrarian-private-upload.internal:10006]: [Errno 111] Connection refused
User4: got that in an email
User3: ok. at least getting an error is better than nothing
User4: User3 also got an error on uploading.. tried again, seemed to accept it, then got that email instead of an accept email
User3: wgrant: ??? ^^^^
User1: One of our two frontends is down for upgrade to xenial, and it looks like it wasn't entirely taken out of DNS.
User3: User1 aha, thank you. I'll be patient
User1: reported to the sysadmin doing the upgrade
User3: understood. TY. :)
 * acheronuk looks for something productive to do that doesn't involve git or uploads....
User4: hehe
User4: thanks cjwatson
 * clivejo gives acheronuk a piece of rope which need untangled and unknotted
User4: alright, i got a package accepted
User5: User1 is that upgrade also what just caused `pull-lp-source git` on my system to give back a 406 from lazr?
User1: User5 yes - I was away for a while, but from internal ops channel chatter it sounds like it should be fixed now
User5: User1 yep, looks resolved, thanks!
launchpad
Ubuntu IRC