Perhaps a dumb question, but I am new at this - so please bear with me.
Here is a brief description of the situation:
I recently learned of a significant, long-standing bug in
dhcpcd- the default network manager for RPi OS. Coincidentally, someone submitted a pull request to the
dhcpcdGitHub site that was committed recently.
The RPi organization does not publish their
dhcpcdsources on GitHub, but they are available via
apt-get source dhcpcd5. This yielded a new folder (
.dscfile (with several inaccuracies), and a compressed
dhcpcd5_8.1.2.orig.tar.xz) - there was no
diff.gzfile/folder. I have incorporated the simple source code correction (one single line of code), and learned enough to successfully build a new
.debfile. I have installed and tested the
.debfile on 3 of my systems; it resolves the issue & I've found no side-effects
I've advised an individual in the RPi organization of my findings some time ago, but have gotten no feedback. Apparently there is no venue for submitting user-proposed changes to the Debian package source files - no pull request mechanism iow.
I'd like to share my effort. It has occurred to me that there may (should?) be a method whereby I can effectively create a git repo from the contents of the Debian package
dhcpcd source files. I know enough
git to upload the contents of
~/dhcpcd5-8.1.2 into a GitHub repo; but my questions are these:
~/dhcpcd5-8.1.2contains some binary files. I think those files were created during the
debuildprocess. How do I purge binaries from the sources in
There are several patches in
dhcpcd5-8.1.2/debian/patches; can I safely rely on these answers from 2016 to ensure all the patches are applied to the source code?
As I don't know enough to ask any further questions, I'll ask instead: "Will this work?" Meaning that if all the binaries are removed, and the current change & all previous patches are applied -- will someone with no specific expertise be able to clone the GitHub repo I want to create, and build it using
debuild -b -uc -us?