[06:22] wgrant, hi, do you have a minute regarding the libreoffice ppa? ^ [06:24] I assume it boils down to request 20gb [06:25] ricotz: I've increased the quota. [06:26] wgrant, thank you very much! [06:27] wgrant, how long is the "clean-up" cycle while old source/binary packages are purged? [06:28] ricotz: Packages which are merely superseded, not explicitly deleted, will be removed after 24-36 hous. [06:30] wgrant, and explicit deletions are faster? [06:31] ricotz: Yes, they usually occur within 12 hours. [06:33] I see, it would be nice if the superseeded packages would still appear on the deletion-site until they are actually gone, giving the maintainer the chance for a manual clean up [06:33] They do. [06:33] wgrant, no they dont ;) [06:33] You just need to filter on Superseded rather than Published. [06:33] oh [06:34] ok, no they dont appear [06:36] Oh, indeed, an optimisation on that UI last year removed them. [06:36] However, they may still be deleted through the API. [06:37] hmm, I see [08:49] Hi all. I've run across a strange issue. I'm looking at https://bugs.launchpad.net/ubuntu/+bugs?orderby=-id&start=990 which works fine. But if I click on "next" I get a strange error message. [08:50] It should be noted I'm not logged in to Launchpad at the moment. If I attempt to edit the url and change the start to, say, 1000 I'm redirected to a login screen. [08:51] My theory is that one of the bug reports (potentially the title), in this segment for some reason triggers the error, but I'm not sure why that would be. [08:53] The link is to the overview of all bugs reported in Ubuntu, so the numbers might slide a bit, though it seems the error is quite consistently triggered in this particular section. Anyone know what might cause this and whether it's a known issue? [08:53] I've got an (several in fact) OPS ID if that helps. [09:03] file a bug with the oops id in it [09:03] it will let the devs look up the details [09:07] lifeless: ok, will do. [09:20] Filed bug 1475221. (Not too happy about the title, but didn't have any better ideas) [09:20] bug 1475221 in Launchpad itself "Get an error message when attempting to access specific section of the list of bugs" [Undecided,New] https://launchpad.net/bugs/1475221 [10:25] cjwatson, hi ~ [10:25] Hello. [10:26] cjwatson, Does currently launchpad support multiple repositories in one project ? [10:26] alextu: Yes. See https://help.launchpad.net/Code/Git [10:27] You can have one marked as the default for the project (which will be what you get if you do git clone git+ssh://git.launchpad.net/PROJECT-NAME) and, if you like, one marked as the default for each owner/project combination (so that's what you get if you do git clone git+ssh://git.launchpad.net/~USER/PROJECT-NAME) [10:27] But you can also have git+ssh://git.launchpad.net/~USER/PROJECT-NAME/+git/REPOSITORY-NAME [10:28] Note, however, that pushing to other repositories in the same project won't share data with those. [10:28] So you should consider carefully whether doing that as a way to host multiple unrelated repositories is a good idea. Creating multiple projects may be wiser. [10:28] But it's possible. [10:29] oh~ I'm trying to use repo and host the sub modules as repositories on launchpad, just like gerrits [10:30] I have already created one https://code.launchpad.net/~alextu/+git [10:30] but don't know how to create others. [10:30] Why are you creating repositories in somebody else's "junk" project? [10:31] just for testing, I think junk is some kind of project. [10:31] For testing, you can create personal repositories without having to have a project context at all. [10:31] it's my launchpad account [10:32] You would push to git+ssh://git.launchpad.net/~alextu/+git/junk rather than to git+ssh://git.launchpad.net/~alextu/junk [10:32] Like I say, read https://help.launchpad.net/Code/Git - it lays out the possible URL forms [10:33] cjwatson, yes, but I would like to simulate creating repositories in on project. [10:33] alextu: Fine, and I explained that above [10:33] Do you understand? [10:33] If not, exactly which part do you not understand? [10:34] cjwatson, do you mean I just to add remote "git+ssh://git.launchpad.net/~alextu/junk" instead of lp:~alextu/junk ? [10:34] You don't understand. [10:34] not really, :( [10:35] If lp: works for you, that is because you have configured it to be identical to git+ssh://git.launchpad.net/ - so I will talk about lp: in future to avoid confusing you. [10:35] lp:~alextu/junk is the default repository for you in the "junk" project. In the normal workflow, that form is intended to be used by contributors to a project they don't maintain - for example, lp:launchpad would be the default repository for Launchpad itself, while lp:~alextu/launchpad would be where you'd hypothetically put your contributions to Launchpad itself. [10:35] That form is probably not suitable for what you're trying to do. [10:36] What you would instead push to would be lp:~alextu/junk/+git/something, lp:~alextu/junk/+git/something-else, etc. [10:37] Normally that's for special purposes such as security-embargoed repositories, but it could be used for the workflow you're suggesting as well. [10:37] Also, please don't push test-only repositories to production. You can test on qastaging. [10:37] cjwatson, yes, currently , I have a local repository called "alex_test2" [10:37] [url "git+ssh://git.qastaging.paddev.net/"] [10:37] insteadof = lpqas: [10:38] Then you can push to lpqas:something instead of lp:something, and your repositories will show up on qastaging.launchpad.net [10:38] cjwatson, now I'm trying to push it to my personal junk for testing. [10:38] And not pollute production with testing [10:38] This way you can also create a proper test project on qastaging and push things there [10:39] (qastaging repositories aren't guaranteed to be preserved, we may wipe the database, but it's fine for short-lived tests) [10:40] can you please share the command , if I have already two stand along repositories locally. Then how to push it to my person project for testing? [10:41] The commands are on https://help.launchpad.net/Code/Git [10:41] All you need is to fill in the right URLs [10:41] I've given you the examples above [10:42] cjwatson, oh~ just success to push another repository, thanks , let me study more detail. https://code.launchpad.net/~alextu/+git [10:43] Right, that looks a bit more like it. [10:47] Basically, just put "lp:~alextu/suitable-project-name/+git/" at the start of all your repository names [10:50] cjwatson, it works as my expectation! thanks a lot!! https://code.launchpad.net/~alextu/sample-project/+git [10:52] alextu: Great. But as I said, please do your testing on qastaging, not production. [10:52] At least repositories are easy to delete, unlike projects :-) [10:53] cjwatson, yes, thanks for advising, I also tried that. :) https://code.qastaging.launchpad.net/~alextu/+git [10:54] cjwatson, awesome! thanks for help :) [10:56] Great. === psivaa is now known as psivaa-afk [11:41] New Launchpad user here. How long does it take for Launchpad to generate the keys for my PPA? [11:43] Nevermind, is done now [11:44] Heh. The answer is that it's a cron job that runs every 20 minutes === zequence_ is now known as zequence === psivaa-afk is now known as psivaa