=== maclin1 is now known as maclin === NikitaKonovalov2 is now known as NikitaKonovalov === funnel_ is now known as funnel === FourDollars_ is now known as FourDollars === Tristit1a is now known as Tristitia [09:42] Hi, I have received a message that I created an OAuth token consumer on launchpad, but I do not remember that I did so.. === Odd_Blok1 is now known as Odd_Bloke [10:12] cjwatson: wow, that's cool! (and kudos to the team that made armhf builds so much faster now) === clivejo_ is now known as clivejo === lool- is now known as lool [12:03] 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] ondrej: has it already been built for that arch, or does the build record not exist yet? [12:17] cjwatson: nope, it hasn't [12:18] 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] 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] ondrej: that will generally be a no-op but it has the useful side-effect of creating the missing build records [12:21] cjwatson: hmm, I tried some combination of this before, but I probably missed this combination :) [12:21] ondrej: let me know if it doesn't work and I'll have a more detailed look [12:22] cjwatson: cool! it works :), that's a relief [12:22] excellent [12:23] cjwatson: one more question about "Change the details" -> how does "Build & publish debug symbols" play with dbgsym packages? [13:05] 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] 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] 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] If you want to play, you will need to download the source and use developer mode. [13:23] 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] 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] cjwatson, true, but I couldn't make the other listing (the one you mentioned) look right. [13:24] cjwatson, this allows anyone to test the CSS on top of the live LP site [13:25] for my patches I was pasting them on top of the live website using the developer tools within the browser. [13:25] OK, but I guess that will have to be somebody else then. Sorry. [13:25] cjwatson, no problem. I completely understand. [13:26] I get that it may be an easier way to develop it, but it's not an easy way to review it. :-/ [13:26] 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] cjwatson, s/mode/move/ [13:28] 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] cjwatson, certainly. === Pici` is now known as Pici === beuno_ is now known as beuni === beuni is now known as beuno === icey_ is now known as icey