=== pleia2_ is now known as pleia2 === axino` is now known as axino === cmars` is now known as cmars === geser_ is now known as geser [11:12] I noticed that if I sign a changes file for a PPA upload, I have to (theoretically) treat the changes file as a secret because someone else could use it to upload to Ubuntu. [11:12] Does the same apply to a changes file intended for an upload to Ubuntu? [11:13] I'm pondering about storing a signed changes file in a git tag. Then the importer would be able to do an upload itself. But a consequence of this is that all changes files corresponding to Ubuntu uploads made this way would be public forever. [11:14] (there are other issues with this, such as getting binary-identical source package files out of the git repo, so this has the same issues as pristine-tar of course) === dpm_ is now known as dpm [11:19] Yes, changes files are signed instructions to the upload machinery. If you publish them you have to strip the signature [11:19] Unfortunately the format of the changes file wasn't very well-considered when PPAs were invented [11:20] They don't specify the target archive, so it is possible to reuse a signed changes file to upload to a different target archive [11:23] dgit has "dgit push", why not use/follow that? [11:23] (If your importer isn't dgit-compatible, I think that may be a mistake) [11:58] I'll look into that, thanks. === lamont` is now known as lamont === dpm is now known as dpm-afk === dpm-afk is now known as dpm [18:02] cjwatson: thanks for the suggestions! the importer is ... still just an importer. We're not working on the tooling on top of it for merges/dev and being dgit-compatible is a great suggestion [18:16] are there issues with the system and serving of packages from PPAs? [18:16] getting reports that one of the PPAs I work on isn't serving arm64 packages [18:17] and Launchpad says it's there [18:20] teward: not afaik, you'll need to give specifics [18:21] cjwatson: getting reports that Xenial packages in arm64 on this are not being picked up by apt: https://launchpad.net/~nginx/+archive/ubuntu/stable/+packages [18:21] https://answers.launchpad.net/nginx/+question/295378 [18:21] it's seeing 'nginx' and 'nginx-common' but not the flavors [18:21] so it fails to install [18:22] teward: hrm, i don't see any arm builds? [18:22] teward: well, sure, that PPA doesn't build for arm64 [18:23] *arm64 [18:23] teward: nor does the ~teward/ubuntu/nginx-stable-testing PPA that you copied the most recent packages from [18:23] teward: so the arm64 binaries that exist are in fact just the Architecture: all binaries, which are published for all architectures [18:24] teward: you can enable arm64 on https://launchpad.net/~teward/+archive/ubuntu/nginx-stable-testing/+edit if you like [18:24] hrm [18:25] cjwatson: that's... unusual I thought I had selected arm64 [18:26] i've queued arm64 builds now [18:26] * teward shrugs [18:28] cjwatson: thanks [18:29] np [18:56] cjwatson: ping [19:01] any LP staff here who could bump the size of the following PPA - https://launchpad.net/~acheron/+archive/ubuntu/qt5test/ [19:02] doing a Qt test build and need the packages all together [20:43] clivejo: bizarrely HUGE -dbg packages is part of it I think? [21:17] clivejo,acheronuk: bumped to 8GiB [21:17] cjwatson: Thank you :) [21:23] thanks cjwatson