[10:36] Could I have a review of a small build system fix? https://code.launchpad.net/~cjwatson/launchpad/+git/launchpad/+merge/382990 [10:41] (Might fix CSS on qastaging, not sure if it's the only thing) [10:45] Not to mention CSS on staging and API on (qa)staging, I think [10:45] ilasc: ^- maybe? [10:46] cjwatson: looking at it as we speak :) [10:47] Ta [10:48] cjwatson: looks good to me [10:48] Thanks [10:55] cjwatson: on the Edit OCI Push Rules screen, looks like with the current approach (replace credentials part of the rule with a link to the appropriate OCIRegistryCredentials:+edit view - screenshot on page 12) if User has no Push Rule defined there is no way for user to edit their Credentials [10:55] might need to do something different than just the link per rule [10:57] ilasc: Aren't we still planning a tab on the person's index page too? [11:01] yes, that's still there (Display Creds only), allow Edit Creds there was part of the first version, but we said we want to keep Edit Creds with Edit rules. Are you thinking go back to enabling Edit Creds on the Person's index page ? (that's what I'm thinking at the moment) [11:03] ilasc: I was expecting both [11:03] credentials views accessible from your index page, and also the ability to edit credentials directly from a push rule if they're linked to one [11:04] I don't think I intended to say that credentials editing should *only* be accessible from push rules [11:04] if I implied that, I apologise [11:04] ok, makes sense to do it that way [11:04] * ilasc implements both [11:05] Should just be a matter of the list view having some edit links [14:12] https://code.launchpad.net/~cjwatson/launchpad/+git/launchpad/+merge/383000 (Fix determination of bug target roles) [14:13] This is what you were discussing on #launchpad some minutes ago? [14:13] Yep [14:14] Awesome. Let me review it [14:23] Thanks [14:23] And I must owe you at least one review, so let's see [14:25] hahaha! Thanks! :) [14:47] pappacena: Speaking of which, were you planning on landing https://code.launchpad.net/~pappacena/launchpad/+git/launchpad/+merge/382233 ? Looks like it's ready to go [14:51] Is the DB patch applied to production already? [14:51] It is [14:51] Ok! I'll top-approve it. Thanks [15:05] pappacena: Conflict again, by the looks of it [15:06] Yep. Merging master into the branch here. [17:58] pappacena: (Implicit) question in Freenode/#ubuntu-release ("whoever is accepting NEW packages") - is that something your archive admin audit work should be able to answer, out of interest? [17:59] uhm, I'll join this channel. Anyway, I guess this information is present at the archive admin audit trail, yes. [18:02] pappacena: How could I view that for a given package? [18:04] At the publishing history page of that package (like https://launchpad.net/ubuntu/+source/man-db/+publishinghistory) [18:06] At the main page of the package, it shows as "Publishing details" when you click on the arrows at the bottom part too [18:06] like this https://usercontent.irccloud-cdn.com/file/67n2jGD1/image.png [18:11] pappacena: Ok thanks will take a look! [19:06] In this case it would actually be on the queue pages (https://launchpad.net/ubuntu/groovy/+queue) [19:35] pappacena: FWIW the error on buildbot is easily reproducible locally with bin/test -vvc --layer=AppServerLayer [19:35] ValueError: In version devel, IOCIRecipeBuildRequestEntry_devel.builds is a collection of IOCIRecipeBuild, but version devel of the web service does not publish IOCIRecipeBuild as an entry. (It may not be published at all.) [19:35] is the key bit [19:36] i.e. essentially the problem is that IOCIRecipeBuildRequest.builds is exported but the interface type that it's exporting a collection of isn't [19:37] Ah, got it. I'll take a look in a minute [19:37] Thanks! [19:41] wgrant: Could you DB-review https://code.launchpad.net/~cjwatson/launchpad/+git/launchpad/+merge/383021 please? === popey4 is now known as popey