Hi! > fwiw, I'm also not using git-buildpackage and I don't want to. (Step learning > curve, too much magic, hard to debug and I dont see benefits for the packages > I maintain.) I'm also not a beginner. And I love gbp-dch.
I think git-buildpackage is great, and I am a happy user. However, it took me quite a while to figure out what is the optimal way to use it, as it has so many options. Can you elaborate what is the specific action/workflow you think git-buildpackage you were frustrated with? Perhaps I can help you discover the optimal workflow and you can skip the learning curve? > please dont enforce git-buildpackage on everyone. I am not enforcing git-buildpackage on everyone. I am accelerating the convergence of workflows so that it is easier for maintainers to collaborate, so we can have more code reviews, more new maintainers, and in the long run perhaps decrease the number of single-maintainer packages for packages where the maintainer does not want to be the sole maintainer. Currently the learning curve on how to contribute prevents many people from doing it. As part of this I help people make the most out of git-buildpackage, which is by far the most popular tool for this, and to my knowledge the only tool that supports having upstream branch in the same repository, cherry-picking upstream commits easily, rebasing Debian patches on upstream, tracking supply-chain from upstream git tags and tarballs (or both) to Debian releases and so forth. There is a debian/gbp.conf in 13573 packages in Debian, and probably twice as many in total use git-buildpackage already. Almost all team policies I read have converged on git-buildpackage. If we don't converge on what the majority is already using, what then? > emacs might be better than nano for many usecases, but not all. if someone > would force me to use emacs, I'd be out. (FWIW, i'm a vim user, this is an > analogy.) The analogy with an editor does not work, as the editor is your personal tool. A better analogy would be interactive pair-programming, and in such a setting would need to agree with your pair to use for example Pulsar or Zed so that there is a common system that shows on your screens what the other person is typing. If you had bad experiences with git-buildpackage, please share them with me, I can help you find the optimal workflow, and you can perhaps give git-buildpackage a second chance?
