From a6c7e5fd1684f8a7621cdf168c285319fa5c84db Mon Sep 17 00:00:00 2001 From: Sean Whitton Date: Sat, 29 Oct 2016 07:26:24 -0700 Subject: dgit-sponsorship(7): Suggest pristine-tar(1) Signed-off-by: Sean Whitton --- dgit-sponsorship.7.pod | 23 ++++++++++++++++++++--- 1 file changed, 20 insertions(+), 3 deletions(-) diff --git a/dgit-sponsorship.7.pod b/dgit-sponsorship.7.pod index 71fb205..e6c7730 100644 --- a/dgit-sponsorship.7.pod +++ b/dgit-sponsorship.7.pod @@ -110,8 +110,23 @@ in their handover email. If there are any .origs that are not in the archive already, the sponsor will need them as part of the upload. -The sponsee can put them on a suitable webserver, -or attach to an email. +The simplest approach is to +commit them with pristine-tar(1), e.g. + +=over 4 + + % pristine-tar commit ../foo_1.2.3.orig.tar.xz upstream/1.2.3 + +=back + +and be sure to push the pristine-tar branch. +If you are using git-buildpackage(1), just pass +I<--git-pristine-tar> and I<--git-pristine-tar-commit>. + +Alternatively, +the sponsee can put them on a suitable webserver, +or attach to the e-mail, +if they are small. The sponsee should quote sha256sums of the .origs in their handoff email. @@ -137,7 +152,9 @@ You should check the signature on the email. Use C to fetch the git branch prepared by your sponsee, -and obtain any .origs mentioned by the sponsee. +and obtain any .origs mentioned by the sponsee +(to extract .origs committed with pristine-tar, +you can use origtargz(1).) Check the git commit ID of the sponsee's branch tip, and the sha256sums of the .origs, -- cgit v1.2.3