=== pieq-afk is now known as pieq [10:01] I'm making plans to "reimport" all the git-ubuntu branches with their final versions. On qastaging it looks like if I force push all branches, existing MPs will remain. Is this correct? [10:02] Only my test MP seems to be having its preview diff regenerated, which is confusing. [10:02] I also got OOPS-82e235e545a60a1f77a42487a22e9aa8 on my first push attempt [10:02] https://oops.canonical.com/?oopsid=OOPS-82e235e545a60a1f77a42487a22e9aa8 [10:02] (the first attempt to force push master to change it under the MP, that is) [10:03] rbasak: They'll remain though the "conversation" may be a bit confusing on each [10:03] The oops is a timeout because qastaging runs on potatoes [10:03] Seven seconds to select from FeatureFlag, seriously [10:04] That sounds good enough to me. Thanks! [10:05] Oh, one further question. I want to split ~usd-import-team apart, since right now we're conflating the team that maintains the git-ubuntu code base with the team (really just one bot) that maintains the imported branches themselves. [10:05] I think the easiest way to do this would be to create a new team for the bot. But then the branches need to move across. [10:05] I was going to do that at the same time as the reimport. [10:06] If I make sure that the default repository for each distribution source package target points to the ~usd-import-team repos, then when I push to the new team, tree objects should be shared with the old ones, so shouldn't cause double storage issues, right? [10:07] So I was going to make sure the pointers are all correctly pointing to the old repos, then as I import each replacement, push it to the new team and switch the default repository. [10:07] Will this work for you? [10:13] Um [10:13] Why not just change the owner of the existing repos? [10:14] Oh. I can I do that? [10:14] I can do that? [10:15] owner_link (writeable) [10:15] So I can [10:15] Thanks [10:20] Clients won't notice unless they've explicitly cloned lp:~usd-import-team/ubuntu/+source/foo/+git/bar rather than lp:ubuntu/+source/foo. But that doesn't seem very likely and is easily fixed on the client end anyway. [10:27] As it happens, they have, because that's what "git ubuntu clone" does, because it predates us taking the prime spot. But I will change that very soon. [10:28] Another minor issue is that the importer bot itself doesn't have permission to change the default repository, so that's done from a separate script that we only run infrequently. So new repositories won't appear until that's done. [10:28] "appear" [14:36] when doing binary package copy, can i choose architectures to copy? [14:36] cause i think at the moment i will try to do binary copy & then remove binaries I do not want. [14:39] You cannot [14:39] IIRC anyway [14:45] thanks