[09:42] <dgr_nick> Hi, I have received a message that I created an OAuth token consumer on launchpad, but I do not remember that I did so..
[10:12] <ondrej> cjwatson: wow, that's cool! (and kudos to the team that made armhf builds so much faster now)
[12:03] <ondrej> cjwatson: by any chance is there a way how to trigger a new architecture rebuild without having to bump a revision and rebuild for all archs?
[12:15] <cjwatson> ondrej: has it already been built for that arch, or does the build record not exist yet?
[12:17] <ondrej> cjwatson: nope, it hasn't
[12:18] <ondrej> cjwatson: I enabled arm64, and now I need to rebuild some deps for the new arch (arm64); new PHP was just released, so it's just a couple of packages, but generally I had the same problem when I enabled armhf
[12:19] <cjwatson> ondrej: right, so it's not obvious, but you can use the "Copy packages" UI for that PPA to copy the packages in question over the top of themselves, selecting "Copy existing binaries"
[12:19] <cjwatson> ondrej: that will generally be a no-op but it has the useful side-effect of creating the missing build records
[12:21] <ondrej> cjwatson: hmm, I tried some combination of this before, but I probably missed this combination :)
[12:21] <cjwatson> ondrej: let me know if it doesn't work and I'll have a more detailed look
[12:22] <ondrej> cjwatson: cool! it works :), that's a relief
[12:22] <cjwatson> excellent
[12:23] <ondrej> cjwatson: one more question about "Change the details" -> how does "Build & publish debug symbols" play with dbgsym packages?
[13:05] <cjwatson> ondrej: "Build debug symbols" causes dbgsym packages to be built at all; "Publish debug symbols" causes them to be published on ppa.launchpad.net, not just downloadable from LP
[13:05] <cjwatson> ondrej: if dbgsym packages are useful to you then you probably just want to check both, although note that they will count towards the archive quota
[13:22] <rbanffy> Hi folks. Some time ago I was playing with LP's CSS to make some listings easier do navigate, but I never managed to properly integrate those changes to LP's official CSSs and propose a merge. I'd, however, appreciate input on a Chrome extension I built for playing with that CSS: https://github.com/rbanffy/launchpad_tweaks.
[13:23] <rbanffy> If you want to play, you will need to download the source and use developer mode.
[13:23] <cjwatson> rbanffy: So, it's actually much harder to review a Chrome extension than it would be if you simply pushed more commits to your branch addressing my review comments there.
[13:23] <cjwatson> I'm unlikely to get round to doing anything with a Chrome extension, but I very likely would get round to it if you addressed my review feedback on your branch.
[13:24] <rbanffy> cjwatson, true, but I couldn't make the other listing (the one you mentioned) look right.
[13:24] <rbanffy> cjwatson, this allows anyone to test the CSS on top of the live LP site
[13:25] <rbanffy> for my patches I was pasting them on top of the live website using the developer tools within the browser.
[13:25] <cjwatson> OK, but I guess that will have to be somebody else then.  Sorry.
[13:25] <rbanffy> cjwatson, no problem. I completely understand.
[13:26] <cjwatson> I get that it may be an easier way to develop it, but it's not an easy way to review it. :-/
[13:26] <rbanffy> cjwatson, once we have a reasonable set of patches (not something that's grafted on top of the live CSS) we can mode on with a proper patch.
[13:27] <rbanffy> cjwatson, s/mode/move/
[13:28] <cjwatson> rbanffy: I think you said you'd at least addressed some of my comments.  Do you think that you could at least push that subset of changes to your branch?
[13:46] <rbanffy> cjwatson, certainly.