[git-buildpackage] A gbp workflow question re pq & patches

[Seamus de Mora]

Hello,

On Wed, May 11, 2022 at 6:23 AM Guido Günther <agx at sigxcpu.org> wrote:

>
> > My second commit will be the "fix" to 'dhcpcd' - the same fix I submitted
> > to the upstream source, and raspbian about a month ago.
> >
> > I think that means I should now begin reading `gbp-pq` in earnest, and
> > follow up when questions arise.
>
> …or put the patch into `debian/patches` and adjust the series file
> (either manually or via quilt) and commit that to git. This will allow
> you to proceed without having to learn yet another tool (gbp-pq) which
> is just there to make that task simpler.


Thank you for the suggestion. It's a good one, and I'd follow it except for
my wish to have a "baseline"  commit that matches "exactly" with the state
of the apt source package maintained by Raspbian. This may be nonsensical
reasoning, but in my present early learning phase, it strikes me as a
logical point of departure.

I've posted a "recipe" in my RPi repo on GitHub that details how to
manually repair the source code error, then build and install 'dhcpcd'.
Consequently I don't feel any urgency to get the new 'dhcpcd5' repo pushed
out. FYI - I hope to use this time to ponder a few more questions:

   - how to add support for 'buster'?
   - how to (and if I should even try) incorporating the 8.1.3 - 8.1.9
   releases from the 'dhcpcd' upstream sources?
   - linking the 'package' version # to the version # reported by 'dhcpcd' ?
   - how to verify my package complies with Debian standards?

So - a few more things to think about, but I feel I'm making progress  :)

Thnx,
~S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sigxcpu.org/pipermail/git-buildpackage/attachments/20220511/76369ea3/attachment.html>