X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=dgit.git;a=blobdiff_plain;f=dgit.1;h=f7f8dad50b43bf452cf7abee96a8593e285ed925;hp=81786315c4366c30f6550f07902369d65f2b3ba3;hb=ce6eee9d419bcac712d3ddbb084619d3c02681bd;hpb=18e3479f8737622d5e3ff964652dade72f82c897 diff --git a/dgit.1 b/dgit.1 index 81786315..f7f8dad5 100644 --- a/dgit.1 +++ b/dgit.1 @@ -155,6 +155,9 @@ the built source package not being identical to the git tree. In more detail: dgit push checks that the current HEAD corresponds to the .dsc. It then pushes the HEAD to the suite's dgit-repos branch, +adjusts the .changes to include any .origs which the archive lacks +and exclude .origs which the archive has +(so -sa and -sd are not needed when building for dgit push), makes a signed git tag, edits the .dsc to contain the dgit metadata field, runs debsign to sign the upload (.dsc and .changes), pushes the signed tag, and finally uses dput to upload the .changes to the @@ -591,7 +594,11 @@ Specifies a single additional option to pass, eventually, to dpkg-genchanges. Options which are safe to pass include -.BR "-si -sa -sd -C" . +.BR -C +(and also +.BR "-si -sa -sd" +although these should never be necessary with Debian since dgit +automatically calculates whether .origs need to be uploaded.) For other options the caveat below applies. .TP @@ -740,6 +747,16 @@ Your build or push will probably fail later. .B --force-unsupported-source-format Carry on despite dgit not understanding your source package format. dgit will probably mishandle it. +.TP +.B --force-dsc-changes-mismatch +Do not check whether .dsc and .changes match. +The archive will probably reject your upload. +.TP +.BR --force-import-gitapply-absurd " | " --force-import-gitapply-no-absurd +Force on or off the use of the absurd git-apply emulation +when running gbp pq import +when importing a package from a .dsc. +See Debian bug #841867. .SH WORKFLOW - SIMPLE It is always possible with dgit to clone or fetch a package, make changes in git (using git-commit) on the suite branch