| === pleia2_ is now known as pleia2 | ||
| === axino` is now known as axino | ||
| === cmars` is now known as cmars | ||
| === geser_ is now known as geser | ||
| rbasak | 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 |
|---|---|---|
| rbasak | Does the same apply to a changes file intended for an upload to Ubuntu? | 11:12 |
| rbasak | 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:13 |
| rbasak | (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) | 11:14 |
| === dpm_ is now known as dpm | ||
| cjwatson | Yes, changes files are signed instructions to the upload machinery. If you publish them you have to strip the signature | 11:19 |
| cjwatson | Unfortunately the format of the changes file wasn't very well-considered when PPAs were invented | 11:19 |
| cjwatson | 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:20 |
| cjwatson | dgit has "dgit push", why not use/follow that? | 11:23 |
| cjwatson | (If your importer isn't dgit-compatible, I think that may be a mistake) | 11:23 |
| rbasak | I'll look into that, thanks. | 11:58 |
| === lamont` is now known as lamont | ||
| === dpm is now known as dpm-afk | ||
| === dpm-afk is now known as dpm | ||
| nacc | 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:02 |
| teward | are there issues with the system and serving of packages from PPAs? | 18:16 |
| teward | getting reports that one of the PPAs I work on isn't serving arm64 packages | 18:16 |
| teward | and Launchpad says it's there | 18:17 |
| cjwatson | teward: not afaik, you'll need to give specifics | 18:20 |
| teward | 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 |
| teward | https://answers.launchpad.net/nginx/+question/295378 | 18:21 |
| teward | it's seeing 'nginx' and 'nginx-common' but not the flavors | 18:21 |
| teward | so it fails to install | 18:21 |
| nacc | teward: hrm, i don't see any arm builds? | 18:22 |
| cjwatson | teward: well, sure, that PPA doesn't build for arm64 | 18:22 |
| nacc | *arm64 | 18:23 |
| cjwatson | teward: nor does the ~teward/ubuntu/nginx-stable-testing PPA that you copied the most recent packages from | 18:23 |
| cjwatson | teward: so the arm64 binaries that exist are in fact just the Architecture: all binaries, which are published for all architectures | 18:23 |
| cjwatson | teward: you can enable arm64 on https://launchpad.net/~teward/+archive/ubuntu/nginx-stable-testing/+edit if you like | 18:24 |
| teward | hrm | 18:24 |
| teward | cjwatson: that's... unusual I thought I had selected arm64 | 18:25 |
| teward | i've queued arm64 builds now | 18:26 |
| * teward shrugs | 18:26 | |
| teward | cjwatson: thanks | 18:28 |
| cjwatson | np | 18:29 |
| clivejo | cjwatson: ping | 18:56 |
| clivejo | any LP staff here who could bump the size of the following PPA - https://launchpad.net/~acheron/+archive/ubuntu/qt5test/ | 19:01 |
| clivejo | doing a Qt test build and need the packages all together | 19:02 |
| acheronuk | clivejo: bizarrely HUGE -dbg packages is part of it I think? | 20:43 |
| cjwatson | clivejo,acheronuk: bumped to 8GiB | 21:17 |
| acheronuk | cjwatson: Thank you :) | 21:17 |
| clivejo | thanks cjwatson | 21:23 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!