Hello, On Tue, May 3, 2022 at 4:19 AM Guido Günther <[email protected]> wrote:
> > FWIW, I experimented with my local .dsc file. 'man gbp-import-dsc' suggests > > usage of a local .dsc as follows: > > 'gbp import-dsc ../hello_2.10-1.dsc' > > Which implied to me that the folder should be created, then descend into it > > before running this command. > > this is true when you run it inside an existing repo as it assume you > update. If you run from a outside repo it creates one, that's why the > log says: > > gbp:info: No git repository found, creating one. To recap, I have apparently successfully created a git repo that matches the source package I obtained using 'apt-get source dhcpcd5'. I now have a question(s) re. the 'incorporation' of my pristine upstream source into the repo. When I pulled the dhcpcd5 source repo (using 'apt-get source dhcpcd5'), I got a tarball named 'dhcpcd5_8.1.2.orig.tar.xz'. AIUI, this is called the 'pristine' upstream source, and during the build process it serves as a "quality check" on the integrity of the package. 'man gbp-import-dsc' defines these options: - "--pristine-tar => Generate pristine-tar delta file." - "--upstream-branch=branch_name => The branch in the Git repository the upstream sources are put onto. Default is upstream" I'm confused on the purpose of these options - could you explain how they are used? Let me try to explain where I'm confused: - The 'dhcpcd5' repo I created using 'gbp import-dsc' contains a branch called 'upstream'. Does this branch contain/represent the same sources that are in the 'dhcpcd5_8.1.2.orig.tar.xz' tarball? - If so, why can't the 'pristine-tar delta file' be computed from the 'upstream' branch in the repo? Thnx, ~S
_______________________________________________ git-buildpackage mailing list [email protected] http://lists.sigxcpu.org/mailman/listinfo/git-buildpackage
