/srv/irclogs.ubuntu.com/2015/05/12/#launchpad-dev.txt

cjwatsonwgrant: So here's a problem with the approach taken in https://code.launchpad.net/~cjwatson/launchpad/bpph-source/+merge/25507000:11
cjwatsonwgrant: chaenomeles/launchpad-access60.log:91.189.89.30 - "91.189.90.217" "api.launchpad.net" [11/May/2015:16:55:19 +0000] "GET /devel/~ubuntu-security/+archive/ubuntu/ppa/+build/7403388?ws.op=getLatestSourcePublication HTTP/1.1" 401 480 14 0.106685876846 626 191 "Anonymous" "BinaryPackageBuild:EntryResource:getLatestSourcePublication" "" "lazr.restfulclient 0.12.0; oauth_consumer="ddeb-retriever""00:12
cjwatsonthat's a build from a private archive copied into the primary Ubuntu archive; we can't do BPPH.build.getLatestSourcePublication() because that's constrained to return an SPPH in the same archive as the build, and that archive is private00:13
cjwatsonI wonder, though, if we should have a similar exception for SPPH visibility as there is for BPB visibility00:15
cjwatsonThat is, if you can see the SPR you might as well be able to see the other thing00:15
cjwatsonThough it might be a problem that SPPH URLs are under their archive00:17
cjwatsonWe should find some solution for this soon, as it's blocking ddeb-retriever right now00:17
cjwatson(Though fortunately ddeb-retriever can now catch up in a way that was awkward before)00:17
wgrantbigjools: We could change the default if you know you're going to be exceeding it.00:23
wgrantcjwatson: ugh, indeed, we really should just fix this to not be completely and utterly broken model-wise at some point :/00:23
cjwatsonSo we could just implement your suggestion from that MP of exporting the source name as a stopgap00:27
cjwatsonIn the specific case of ddeb-retriever that's all it actually needs today00:27
cjwatsonThere are probably other users that will have issues, but ...00:27
cjwatsonIt's independently irritating that the source on https://launchpad.net/~ubuntu-security/+archive/ubuntu/ppa/+build/7403388 isn't linked, but that has nothing to do with privacy, it's because we never make that a link if the context archive is a PPA.  Though in this case you don't get to see the archive either.00:30
wgrantYeah, I have a partially implemented fix for all that, but it's a reasonable amount of work.00:33
wgrant(see my ArchiveBinaryPackageBuild series)00:33
cjwatsonAh yes, I think I've seen that before00:44
wgrantFixes a lot of performance issues as well.00:49
cjwatsonIn the short term I think exporting BPB.source_package_name is likely to be most practical, though.00:51
wgrantYep.00:54
wgrantMost awkward bit is ensuring the correct preloading.00:54
cjwatsonwgrant: self.source_package_release.name is already used by BPB.title, which is exported, so I don't think it needs anything new.00:57
blrwgrant: cjwatson: what are your thoughts on changing the "Configure project branch" label under Config Progress to "Configure project code" or something that suits both git and bzr.00:57
cjwatsonblr: Sounds sensible00:57
cjwatson"Code" is a reasonable term in existing use that covers both.00:58
blrsounds good, thanks.00:58
wgrantcjwatson: Ah, of course.00:59
wgrantsettings00:59
wgrantsettings dammit.00:59
wgrantNone of this "Change details"00:59
wgrantOr "Configure"00:59
wgrantgod. damn. settings.00:59
cjwatsonI was just thinking that "Configure ... code" does sound a bit like ./configure00:59
wgrantIt's also awkward and long :)01:00
wgrantI think "settings" is the usual word nowadays just about everywhere else.01:00
blrwe certainly like saying configure a fair bit -> "Configuration progress ... Configuration options... Configure bug tracker"01:01
wgrantIndeed.01:02
blrwe could drop configuration from everything save Configuration progress and it would all still make sense01:02
wgrantIn that portlet it probably makes sense, indeed. I'm not sure where else those links are used, though.01:02
wgrantOther places (eg. https://blueprints.launchpad.net/launchpad) need something like the current text.01:03
wgrant(or "settings"!)01:03
wgrantThe config portlet probably does want to override it.01:04
blrit "options" even the right word in that portlet, they seems more like 'steps'01:04
blrgranted they are optional.01:04
cjwatsonExcept you don't have to carry them out in order.01:04
wgrantAnd they never go away :/01:04
cjwatsonOr at all.01:04
blrheh01:04
wgrantThe whole thing needs to be redesigned, but I'd be tempted to just have links named after the tabs without saying configure configure configure.01:05
blryep, let's do that for now.01:05
* blr wanders off to de-yodawg.01:06
blrwill also add something to the UI asana board about the entire process being clunky generally01:07
wgrantA good idea.01:07
wgrantIt's the first impression you get of LP (other than the adventure of finding out how to create a project, and then fill in the eleven thousand fields on ProjectSet:+new, which keeps going across multiple steps each with variants of the same fields), and it's a little dodgy.01:08
blrright, I think if we could address this config process _and_ add more visibility to +new that would help new users a great dela.01:09
blror deal even.01:09
cjwatsonAlthough careful with pushing ProjectSet:+new because people often hit that when they really meant to create a PPA.01:10
cjwatsonDespite the warnings.01:10
cjwatsonIt's not clear whether it's really easier to find ProjectSet:+new than Person:+create-ppa, or if we just don't hear about the latter because you can do self-service PPA deletion.01:11
blrsounds like another task for the UI board :)01:11
cjwatsonwgrant: https://code.launchpad.net/~cjwatson/launchpad/bpb-source-package-name/+merge/25882001:30
wgrantcjwatson: You'll probably also need to fix xx-builds.txt01:34
cjwatsonsassenfrassendoctests01:34
cjwatsonyeah01:34
* cjwatson lands that and sleeps01:46
bigjoolscjwatson: I had completely forgotten about the hidden copy-packages link!01:48
wgrantcjwatson: buildd branches fixed.02:04
blrhave changed the order of the configuration options to reflect the top menu as well, code coming first.02:36
blrwgrant: what's the best way to render the links on Bugs/Blueprints/Translations etc? They should still read 'Configure foo' on those views.02:38
wgrantblr: I'd rather customise the links rendered by pillar-involvement-portlet.pt02:41
wgrantblr: ProductInvolvementView.configuration_links already changes things up a bit.02:42
blrah I see, I'll leave the configure_foo methods as they are in that case.02:46
blrwgrant: why is blueprints commented?03:04
wgrantblr: I'm not quite sure. The revision that disabled it added the progress bar.03:14
wgrant3220eba or r11189.1.503:15
wgrantBut no rationale provided.03:15
blrweird, seems a little odd not to have it enabled, given we're still supporting blueprints.03:19
wgrantIndeed.03:21
wgrantblr: Are you landing that DB branch?05:22
blrwgrant: no, I'm still not entirely sure about windows. There's no hurry, I need the corresponding setup/setbranch branch working for it be of any use, unless it is useful for you or colin.05:30
wgrantblr: What do you mean about windows?05:39
wgrantblr: The column is useful even without the setbranch rework.05:39
blrwgrant: windows for landing a db patch.05:40
blrcolin landed the last patch I wrote - can I lp-land it now?05:41
wgrantblr: Yep, you can land as soon as there are no deployment blockers (eg. code on prod that depends on a column that you're removing).05:42
wgrantThere are traditionally *deployment* windows, but we tend to ignore them nowadays if that would be convenient.05:42
blrok, will do that after dinner. thanks :)05:42
blrwgrant: ok to land the patch with no-qa?06:31
wgrantblr: Yep06:40
blrwgrant: assuming for the API export, vcs should be a Choice, but presumably that requires the creation of a new vocabulary?06:46
wgrantblr: No, you can give Choice an enum directly.06:48
wgrantFor simple cases like this.06:48
wgrantNo filtering or restrictions required.06:48
blrah good06:48
blrwgrant: fixed up the api export - regenerated the api docs which seem correct.07:30
wgrantblr: Thanks, will look in a bit.08:07
cjwatsonwgrant: buildd> r=me, thanks09:56
wgrantcjwatson: Thanks.09:57
=== danilos` is now known as danilos
cjwatsonHm, are we OK with CSS3 selectors in LP?12:33
cjwatsonI guess that not() is in use in several other places.12:33
beunocjwatson, I think it's been a few years to be ok with them!12:44
cjwatsonspot the person with a distro developer background, not web dev. :-)12:48
wgrantcjwatson: http://caniuse.com/12:50
wgrantcjwatson: IE8 doesn't support it, but everything else of significance does.12:50
beunocjwatson, beowulf is my go-to guy for these questions, FWIW12:51
wgrantAnd we don't particularly care about IE8 any more, particularly for something so trivial.12:51
beunohe's usually happy to help12:51
beunoand in the UK12:51
beunowe'll soon get another FE-focused person on board in the CI team as well12:52
beunodisclaimer, he's on a mission to move away from YUI wherever possible/cheap/sensible12:53
cjwatsonIn this case it was just for https://code.launchpad.net/~rbanffy/launchpad/highlight_listing_tr/+merge/258766 rather than anything deeply involved13:02
cjwatsonhttps://code.launchpad.net/~cjwatson/launchpad/git-activereviews/+merge/258910 - phew.  EOD time.17:32
cjwatson(modulo team meeting)17:32

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!