Switched to the "New upstream" bug, since that seems more relevant.
On Sun, Nov 05, 2023 at 02:09:20AM +0530, Nilesh Patra wrote: > On Sat, Nov 04, 2023 at 02:25:47PM -0400, James McCoy wrote: > > We can try that for the now, but it would probably be good for someone > > else to eventually take over primary maintenance of the package. > > > > https://salsa.debian.org/debian/kitty/-/merge_requests/3 is what I have > > so far for the new upstream version. Feel free to hack around with > > that. > > Cool. I have one question though: how do you sync the repo to new > upstream? It does not seem to use gbp layout so wanted to know how > exactly you're tracking/pulling the commits? I just merge the upstream tags directly and use “git deborig” to produce the orig tarball (c.f. dgit-maint-merge(7)). > OTOH, I did take a look at the errors and I see two ways. Either patch > out all the go build related code and use debian's go build toolchain > (which takes care of a bunch of things) or hack around the way upstream > builds to somehow fit out usecase (this is consuming quite some cycles). > Definitely complicated since a bunch of different functionalities have > been mixed with different languages. The former is fine with me. I took a quick look at what Fedora is doing, and it looks like they just patch setup.py to return from build_static_kittens() just before the “go build -v” line. Adding a patch for that and then adapting the rest of the Debian side of the build to do it seems reasonable. This sounds like the packaging will be carrying around a patch for a while, so I would normally switch to dgit-maint-debrebase(7) here. However, maybe it's better to align with gbp if that's what you're more comfortable with. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
