=== ijohnson|lunch is now known as ijohnson === ilasc changed the topic of #launchpad to: Help contact: ilasc (09:00-18:00 UTC Mon-Fri) | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support and spam reporting: https://answers.launchpad.net/launchpad [15:05] Why can't my `bzr` invocation do `git-build-recipe`? https://paste.ubuntu.com/p/sxCGZszSBh/ [15:06] Why would it? [15:06] git-build-recipe is a git-build-recipe thing, not a bzr dailydeb thing :) [15:06] They're similar but not identical [15:06] because this? https://help.launchpad.net/Packaging/SourceBuilds/Recipes [15:07] That doesn't tell you to run bzr dailydeb on a git recipe though ... [15:07] https://help.launchpad.net/Packaging/SourceBuilds/GettingStarted [15:07] You have to use the command that matches the kind of recipe you're writing [15:08] Okay, granted. How _do_ I test the recipe I've written? [15:09] "Things are similar for git, but use git-build-recipe instead of bzr dailydeb" [15:09] Ah, tricksy documentation. [15:12] The pedant in me wants to point out that, while `git-build-recipe` matches the first-line declaration, `bzr dailydeb` does _not_ match the `bzr-builder` declaration. But I won't mention it. :D [15:13] Yeah, that bit was before my time [15:14] cjwatson: how long have you been with Canonical, if I might ask? You're everywhere I look. [15:16] realtime-neil: about 16.5 years [15:17] I meant before my time on the Launchpad team, in this case :) [15:17] (which is coming up on 6 years) [15:21] goodbye launchpad builders... [15:22] LocutusOfBorg: I find your lack of details disturbing. What happen? [15:23] realtime-neil, its a crypting message for IS team :) [15:23] https://launchpad.net/builders looks like 179 builders are "manual", so not processing new stuff [15:23] not sure if this is intended or not, maybe they need just a long enough stick [15:32] LocutusOfBorg: We're just fiddling with their job queue, they'll be back in a bit [15:32] (Redeploying that rabbitmq-server on focal rather than trusty so that it hopefully stops leaking kernel memory over time) [15:34] "Manual" there is always intentional [15:34] Okay, I changed the declaration to `bzr-builder` and I'm getting "This operation is not supported by the Git smart server protocol." : https://paste.ubuntu.com/p/5pf2PkMDPf/ [15:44] realtime-neil: That seems like the wrong way round. You can't build git-based recipes using bzr dailydeb. You'll need to change the recipe header back to git-build-recipe, and then use git-build-recipe to build it. [15:44] realtime-neil: bzr dailydeb doesn't understand the git-flavoured variant of the recipe format. [15:45] cjwatson: okay going back to that [15:47] I don't see any `run` verbs documented for `git-build-recipe`. How would I override the default packaging actions? [15:47] realtime-neil, https://code.launchpad.net/~videolan/+recipe/master-daily [15:47] does this help you? [15:48] this one has two different git nested https://code.launchpad.net/~costamagnagianfranco/+recipe/boinc-upstream-daily [15:48] thanks Colin for the help [15:48] LocutusOfBorg: I'm seeing that, but there's no `run` actions in the recipe. [15:49] Am I supposed to add the packaging bits in another repo and merge that just before building? [15:49] realtime-neil, I don't get the question [15:50] in boinc-upstream-daily, the upstream code has no "debian directory" so I added one in another git, and nested it inside after the checkout [15:51] LocutusOfBorg: you showed me an example of a repository that merges things before (I assume) running the default build commands --- which is great, and thanks for the link --- but this assumes that I want to create a repository for packaging bits. [15:51] I'd much rather override the default packaging commands to generate the `debian` directory in the checkout. [16:18] git-build-recipe has "run", though it's disabled on LP production [16:19] Overriding the default packaging commands to generate the debian directory is not really how everyone else uses recipes I'm afraid [16:19] If I'm understanding you correctly [16:19] We generally regard the debian/ directory as (at least in substantial part) code and therefore it's best stored in revision control [16:37] (builders should all be back now, BTW) [16:41] cjwatson: you do understand me correctly, and okay, I'll work with what I'm given [16:42] cjwatson: I really need to get good with git-buildpackage and release repos === ijohnson is now known as ijohnson|lunch === ijohnson|lunch is now known as ijohnson [21:20] Another build that failed becuase new upstream broke the merge with my build-fix repo. When a simple patch would easily handle the task. https://launchpadlibrarian.net/509579667/buildlog.txt.gz [21:45] Wouldn't have broken if I could just apply a simple patch instead of merging a git repo. [22:35] I don't speak for Launchpad bug I'm curious to know what situation git can't merge when a patch works. [22:35] Did upstream do a non-fast-forward update to your source branch? That's the only situation I can think of. [23:17] I don't know, it's happened to me a bunch of times. [23:18] https://launchpad.net/~darxus/+archive/ubuntu/linux-firmware-amdgpu-daily/+recipebuild/2690520 [23:20] https://launchpad.net/~darxus/+archive/ubuntu/linux-firmware-daily/+recipebuild/2690515 [23:24] I'd love a better understanding of the problem, so we can work on fixing it.