=== davmor2_ is now known as davmor2 === Aurora is now known as Guest89558 [09:01] Hi there - Quick Question : Cud we have #bounty as a tag on launchpad, please ? [09:04] Hello ? anyone there ? [09:06] Guest89558: You can set any tag you like; nobody needs to create it. [09:07] Guest89558: "Official" tags are maintained by the maintainers of individual projects, not by Launchpad staff. [09:07] ok cheers - How do I find bugs listed under "bounty" ? [09:07] Can you give me the link , please ? [09:08] Guest89558: https://bugs.launchpad.net/bugs/+bugs?advanced=1 lets you search by whatever terms you want [09:08] cheers. === pavlushka_ is now known as pavlushka [12:24] so again, is there a working way to fetch all git repository names though the API? If I run [12:24] print(len(lp.git_repositories.getRepositories(target=lp.projects['kubuntu-packaging']))) [12:24] I get 292 repositories (correct). But if I loop through that, I get several repositories twice and today only 224 (yesterday it was 236) distinct repositories (while it's still 292 in total) [12:25] it feels like pushing something to the repository prevents the API from seeing it... [12:25] the repository target was changed once through the API if that matters [12:43] There may be a missing DISTINCT somewhere. [12:44] Are there actually any repositories missing from that collection, though? [12:45] Also iterating over large collections always has some chance of errors due to races, since the collection is fetched in multiple batches, so clients need to tolerate that. [12:45] A 292 vs. 224 discrepancy suggests a missing DISTINCT though. [12:47] Were it only so simple. [12:47] cjwatson: In this case the batching race doesn't exist, as it's a named operation. [12:47] The 224 is consistent. [12:47] The web UI says 292 and at least some of the duplicates are present only once. [12:48] Oh I think I read yofel's commentary backwards. [12:48] getRepositories returns 292 repositories, same as the web UI. [12:48] But the API's set of 292 contains only 224 distinct repositories. [12:51] Hm, yes, the web UI has no dups. [12:51] cjwatson: ok, nevermind then, I'll sort this out in the packages that keeps failing even on rebuilds; [12:53] wgrant: Not sure what you mean about batching not being a problem. It's fetched in four batches. [12:54] The obvious difference is that the web UI uses order_by_date=True while the API doesn't. [13:13] hm, bummer [13:13] I tried caching the collection as I know the there's issues with fetching a collection over a long timespan, but that gives me the same result [13:14] should I open a bug? [13:16] yes please [13:25] cjwatson: lp 1578205 [13:25] Launchpad bug 1578205 in Launchpad itself "API returns git repository list with missing items and duplicates" [Undecided,New] https://launchpad.net/bugs/1578205 [13:52] Er indeed, the batching race does of course still apply here. [14:20] how easily do you give away s390x support for PPAs? I'm 4 days into a pypy test build on zelenka.d.o, and getting annoyed :P [14:25] tumbleweed: I'm afraid we can't give that to non-Canonical employees right now as there's no sandboxing. [14:25] tumbleweed: Hopefully we'll have s390x scalingstack support soonish. [14:26] neat. It has just gained JIT support for s390x, so presumably somebody out there will find this useful [14:26] (Don't have a very specific date though; my guess would be months rather than weeks or years) [17:49] Is there still the notion of +junk in the launchpad git support? [17:55] lazyPower: it's just pushing an arbitrary repo to your +git i think [17:56] oh so git doesn't have the same project structure requirements? [17:56] i thought that was implemented system wide in launchpad [17:56] #TIL [17:57] yes/no. afaik repositories that are push under projects appear for the listing on those projects, but there isn't a special case of "+junk" [20:26] lazyPower: The equivalent of +junk is the "personal" repository structure defined in https://help.launchpad.net/Code/Git . [20:27] dobey: Please refer to the above documentation. [20:28] ~OWNER/+git/REPOSITORY is very nearly a direct analogue of ~OWNER/+junk/BRANCH, eqxcept that a repository can contain multiple branches. [20:28] right [20:28] And the project and package namespaces are similar to those for Bazaar except that they don't have series. [20:29] didn't think of help.lp.net at the time [20:29] So for the most part, git in Launchpad *does* have the same "project structure requirements" as Bazaar, but with some simplifications and changes. [20:30] Mainly to avoid repeating some mistakes that were made when designing Bazaar in Launchpad - basically, stealing too much namespace. [20:30] right, that's what i was saying, but perhaps i sucked at making it as clear :) [20:30] (And +junk ought to have been renamed ages ago, but nobody ever quite got around to it ...) [20:31] sorry if i was confusing [20:32] Fair enough :) But I did want to point oiut that there in fact *is* a special case of +junk, just spelled differently. [20:32] Or at least it's just as special for git as it is for Bazaar. [20:36] cjwatson: my understanding was that +git was a part of the URL in both personal and project branches. but i guess the position of +git in the URL is a bit different [20:37] The URLs are written out differently, but in both cases there are three namespaces: project, package, and personal. [20:37] The rest is just a matter of spelling, in the git case motivated by avoiding ambiguity. [20:37] or is +git in the lp web URL for a repository somewhat different from the +git in the git remote URL? [20:37] We ended up (after much discussion) putting +git in the URLs for all git repositories, indeed. [20:38] One of the reasons for that was so that we could safely arrange for the URL paths on code.launchpad.net and git.launchpad.net to be the same for any repository. [20:39] But ~OWNER/PROJECT/+git/REPOSITORY and ~OWNER/+git/REPOSITORY (for instance) are still quite different things, despite +git being in both. [20:39] +git is just there to avoid confusion with other URL traversals. [20:42] For example, without +git in the project namespace case, it would be ambiguous whether ~cjwatson/launchpad/feature referred to a Bazaar branch or a git repository; for a project transitioning between the two VCSes, it's quite possible that both could exist with the same name. [20:43] sure