I am under the impression that the gbp-import-dsc command in git-buildpackage (gbp) is designed to translate or convert (import) a *traditional* Debian source repository into a structure/format suitable for deployment and distribution using git (locally) and (for example) GitLab and GitHub as a remote, publicly available repository. If I've gotten this wrong, please let me know.
Some background on my objective: I discovered a bug in a program I use frequently on Raspberry Pi: *dhcpcd*. The *dhcpcd* upstream sources are in this GitHub repo <https://github.com/NetworkConfiguration/dhcpcd>. I submitted a PR against the upstream sources, and the author accepted it, but informed me that it would not get to the downstream repos. The *dhcpcd* source package used by the Raspberry Pi organization is not under 'git' version control - nor is it available on their GitHub site. I worked with the sources I downloaded using the 'apt-get source dhcpcd5' command. I have learned enough of the basics to make the source modifications, and build a new package (.deb) for installation & testing. My objective now is to put this *dhcpcd* code under 'git' version control, and share it; i.e. publish it on my GitHub site, and potentially make additional changes to it. I'm under the assumption that gbp can help me do that, and that the first step is *gbp-import-dsc*. I have tried this, but get only error messages so far. I suspect that the issue may be the current construction of the *dsc* file used for RPi's *dhcpcd*, but I need some help in sorting that. Am I in the right place to ask these questions?
_______________________________________________ git-buildpackage mailing list [email protected] http://lists.sigxcpu.org/mailman/listinfo/git-buildpackage
