=== bage is now known as bastian-germann [12:08] I have just tried to log in to launchpad with my new Ubuntu One account and got an Oops! with Error ID: OOPS-a911ca3b7dc0337b0d533ca736d1d0cf [12:08] Browser: Firefox 102.6.0esr (if that matters) [13:23] bastian-germann: LP was a bit confused because it had seen your email address before in a package upload and so needed us to do a bit of conflict resolution. I've fixed your account now, so you should be able to log in. [13:24] okay, thanks! [20:47] I just noticed that one of my git -> bazaar imports randomly broke some time ago and I wasn't notified [20:47] Any idea what this is about? http://launchpadlibrarian.net/637162956/tatokis-alarm-clock-master.log [22:13] KitsuWhooa: https://bugs.launchpad.net/bzr-git/+bug/1313861 which is an awful slog. Can I ask what the purpose of the import is? Is it possible that a git-to-git import would do the job nowadays, or is the bzr import there for translations? [22:13] -ubottu:#launchpad- Launchpad bug 1313861 in Bazaar Git Plugin "git: AssertionError: Invalid sha for : ..." [Undecided, Triaged] [22:14] Yeah, the bzr import is there for the translations [22:14] Ugh [22:15] I guess I should really unearth that cscvs test container and see if I can remember what the problems with it were [22:16] I already had to delete the repo and recreate it once, but I thought that was because of a force push I did [22:16] (didn't do such a thing again, so it just broke on its own) [22:17] I think there is some semi-coincidental thing related to that bug that can sometimes be very temporarily helped by delete/recreate until it breaks again. But I don't think I ever got precise details of exactly what the fix was, other than being somewhere in the bzr-to-breezy diff [22:18] ah... [22:20] For what it's worth, I probably wouldn't bother with bazaar if translations worked on git [22:21] but I am sure that's a whole other can of worms [22:30] I'm genuinely not sure which is easier :) [22:31] I started on the prerequisites for that one a while back but there are certainly a number of other bits to do [22:31] Ideally I'd like us to fix both [22:31] I mean, we can't stay on bzr forever because Python 2 [22:31] But using git end-to-end is generally much easier to support [22:44] understood [22:46] If the bazaar - breezy diff is a series of commits, perhaps it can be bisected with the broken repo to find out what fixes it [22:48] Oh also, one more quick question. Is there a limit to how often packages are built from a recipe on a PPA? [22:48] I pushed a commit to see if it fixed something packaging related, manually ran an import on LP, and it still hasn't been built [22:50] > 10 minutes ago Successfully built [22:50] nevermind about that I guess, but the question still stands [23:13] The thing that polls for whether the recipe is "stale" and needs to be rebuilt runs every 15 minutes; it also doesn't do anything if the same recipe has been auto-built in the last day or so [23:13] But you can always press the "Build now" button on the recipe [23:14] (well, at least you can if the recipe is stale, i.e. has had a commit since the last auto-build) [23:21] Ah, I see. I didn't see a build now button [23:22] Last build was on the same day though, so it makes sense. Thanks!