1 # SOME DESCRIPTIVE TITLE
2 # Copyright (C) YEAR Free Software Foundation, Inc.
3 # This file is distributed under the same license as the PACKAGE package.
4 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
9 "Project-Id-Version: PACKAGE VERSION\n"
10 "POT-Creation-Date: 2020-02-02 16:50+0000\n"
11 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
12 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
13 "Language-Team: LANGUAGE <LL@li.org>\n"
16 "Content-Type: text/plain; charset=UTF-8\n"
17 "Content-Transfer-Encoding: 8bit\n"
20 #: ../dgit.1:2 ../dgit.7:1
26 #: ../dgit.1:2 ../dgit.7:1
28 msgid "Debian Project"
32 #: ../dgit.1:3 ../dgit.7:2 ../dgit-user.7.pod:1 ../dgit-nmu-simple.7.pod:1
33 #: ../dgit-maint-native.7.pod:1 ../dgit-maint-merge.7.pod:1
34 #: ../dgit-maint-gbp.7.pod:1 ../dgit-maint-debrebase.7.pod:1
35 #: ../dgit-downstream-dsc.7.pod:1 ../dgit-sponsorship.7.pod:1
36 #: ../dgit-maint-bpo.7.pod:1 ../git-debrebase.1.pod:1 ../git-debrebase.5.pod:1
37 #: ../git-debpush.1.pod:1
44 msgid "dgit - git integration with the Debian archive"
48 #: ../dgit.1:6 ../git-debpush.1.pod:5
56 "B<dgit> [I<dgit-opts>] B<clone> [I<dgit-opts>] I<package> [I<suite>] [B<./"
62 msgid "B<dgit> [I<dgit-opts>] B<fetch>|B<pull> [I<dgit-opts>] [I<suite>]"
68 "B<dgit> [I<dgit-opts>] B<build>|B<sbuild>|B<build-source> [I<build-opts>]"
73 msgid "B<dgit> [I<dgit-opts>] B<pbuilder>|B<cowbuilder> [I<debbuildopts>]"
78 msgid "B<dgit> [I<dgit-opts>] B<push>|B<push-source> [I<dgit-opts>] [I<suite>]"
84 "B<dgit> [I<dgit-opts>] B<rpush> I<build-host>B<:>I<build-dir> [I<push args..."
90 msgid "B<dgit> [I<dgit-opts>] I<action> ..."
94 #: ../dgit.1:33 ../git-debpush.1.pod:9
102 "B<dgit> allows you to treat the Debian archive as if it were a git "
103 "repository. Conversely, it allows Debian to publish the source of its "
104 "packages as git branches, in a format which is directly useable by ordinary "
110 msgid "This is the command line reference. Please read the tutorial(s):"
122 msgid "for users: edit, build and share packages"
128 msgid "dgit-nmu-simple(7)"
134 msgid "for DDs: do a straightforward NMU"
140 msgid "dgit-maint-native(7)"
146 msgid "for maintainers of Debian-native packages"
152 msgid "dgit-maint-debrebase(7)"
158 msgid "for maintainers: a pure-git rebasish workflow"
164 msgid "dgit-maint-merge(7)"
170 msgid "for maintainers: a pure-git merging workflow"
176 msgid "dgit-maint-gbp(7)"
182 msgid "for maintainers already using git-buildpackage"
188 msgid "dgit-sponsorship(7)"
194 msgid "for sponsors and sponsored contributors"
200 msgid "dgit-downstream-dsc(7)"
206 msgid "setting up dgit push for a new distro"
212 "See B<dgit(7)> for detailed information about the data model, common "
213 "problems likely to arise with certain kinds of package, etc."
225 msgid "B<dgit clone> I<package> [I<suite>] [B<./>I<dir|>B</>I<dir>]"
231 "Consults the archive and dgit-repos to construct the git view of history for "
232 "I<package> in I<suite> (B<sid> by default) in a new directory (named B<./"
233 ">I<package> by default); also, downloads any necessary orig tarballs."
239 "The suite's git tip is left on the local branch B<dgit/>I<suite> ready for "
240 "work, and on the corresponding dgit remote tracking branch. The B<origin> "
241 "remote will be set up to point to the package's dgit-repos tree for the "
242 "distro to which I<suite> belongs."
248 "I<suite> may be a combination of several underlying suites in the form "
249 "I<mainsuite>B<,>I<subsuite>...; see COMBINED SUITES in dgit(7)."
255 "For your convenience, the B<vcs-git> remote will be set up from the "
256 "package's Vcs-Git field, if there is one - but note that in the general case "
257 "the history found there may be different to or even disjoint from dgit's "
258 "view. (See also dgit update-vcs-git.)"
264 msgid "B<dgit fetch> [I<suite>]"
270 "Consults the archive and git-repos to update the git view of history for a "
271 "specific suite (and downloads any necessary orig tarballs), and updates the "
272 "remote tracking branch B<remotes/dgit/dgit/>I<suite>. If the current branch "
273 "is B<dgit/>I<suite> then dgit fetch defaults to I<suite>; otherwise it "
274 "parses debian/changelog and uses the suite specified there. suite may be a "
275 "combined suite, as for clone."
281 msgid "B<dgit pull> [I<suite>]"
287 "Does dgit fetch, and then merges the new head of the remote tracking branch "
288 "B<remotes/dgit/dgit/>I<suite> into the current branch."
294 msgid "B<dgit checkout> I<suite>"
299 msgid "Checks out the local branch B<dgit/>I<suite>."
305 "If the branch does not exist, dgit checkout creates it, and sets it up the "
306 "same way as dgit clone would. In that case, if the archive remote tracking "
307 "branch does not exist, dgit checkout will do a dgit fetch first."
313 "NB: dgit checkout will only do a fetch if it has to. If you already have "
314 "the suite branch, and want to merge your branch with updates from the "
315 "archive, use dgit pull."
321 "dgit checkout will normally need to access the archive server, to "
322 "canonicalise the provided suite name. The exception is if you specify the "
323 "canonical name, and the branch (or tracking branch) already exists."
329 msgid "B<dgit build> ..."
335 "Runs B<dpkg-buildpackage> with some suitable options. Options and arguments "
336 "after build will be passed on to dpkg-buildpackage. It is not necessary to "
337 "use dgit build when using dgit; it is OK to use any approach which ensures "
338 "that the generated source package corresponds to the relevant git commit."
342 #: ../dgit.1:148 ../dgit.1:200 ../dgit.1:240
343 msgid "Tagging, signing and actually uploading should be left to dgit push."
349 "dgit's build operations access the network, to get the -v option right. See "
356 msgid "B<dgit build-source> ..."
362 "Builds the source package, and a changes file for a prospective source-only "
363 "upload, using B<dpkg-source>. The output is left in "
364 "I<package>B<_>I<version>B<.dsc> and I<package>B<_>I<version>B<_source."
371 "Tagging, signing and actually uploading should be left to dgit push-source, "
378 msgid "B<dgit clean>"
384 "Cleans the current working tree (according to the --clean= option in force)."
390 msgid "B<dgit update-vcs-git> [I<suite>|B<.>] [B<-->] [I<git fetch options>]"
396 msgid "B<dgit update-vcs-git> [I<suite|>B<.>] B<->"
402 "Sets up, or updates the url of, the vcs-git remote, and (unless B<-> was "
403 "specified) runs git fetch on it."
409 "By default, the Vcs-Git field of the .dsc from Debian sid is used, as that "
410 "is probably most up to date. Another suite may be specified, or B<.> to "
411 "indicate that the Vcs-Git of the cwd's debian/control should be used instead."
421 #: ../dgit.1:185 ../dgit.1:1278
422 msgid "Print a usage summary."
428 msgid "B<dgit sbuild> ..."
434 "Constructs the source package, uses B<sbuild> to do a binary build, and uses "
435 "mergechanges to merge the source and binary changes files. Options and "
436 "arguments after sbuild will be passed on to sbuild. The output is left in "
437 "I<package>B<_>I<version>B<_multi.changes>."
443 "Note that by default sbuild does not build arch-independent packages. You "
444 "probably want to pass -A, to request those."
450 msgid "B<dgit pbuilder> [I<debbuildopts>]"
456 "Constructs the source package, uses B<pbuilder> to do a binary build, and "
457 "uses mergechanges to merge the source and binary changes files. The output "
458 "is left in I<package>B<_>I<version>B<_multi.changes>."
464 "You should ensure that your dgit --build-products-dir setting matches your "
465 "pbuilder --buildresult."
471 "The I<debbuildopts> are passed to pbuilder using its --debbuildopts option. "
472 "If you want to pass other options to pbuilder, use the B<--pbuilder:> dgit "
473 "option as described below (remember that dgit options should appear between "
474 "B<dgit> and B<pbuilder>)."
480 "You should ensure that in your pbuilderrc you do B<not> have the setting "
481 "B<SOURCE_ONLY_CHANGES=yes> as this may cause trouble."
487 msgid "B<dgit cowbuilder> [I<debbuildopts>]"
492 msgid "Like B<dgit pbuilder>, but uses B<cowbuilder> instead of B<pbuilder.>"
498 msgid "B<dgit gbp-build> ..."
504 "Runs B<git-buildpackage> with some suitable options. Options and arguments "
505 "after gbp-build will be passed on to git-buildpackage."
511 "By default this uses --quilt=gbp, so HEAD should be a git-buildpackage style "
512 "branch, not a patches-applied branch."
518 msgid "B<dgit push> [I<suite>]"
524 "Does an `upload', pushing the current HEAD to the archive (as a source "
525 "package) and to dgit-repos (as git commits). The package must already have "
526 "been built ready for upload, with the .dsc and .changes left in the parent "
527 "directory. It is normally best to do the build with dgit too (eg with dgit "
528 "sbuild): some existing build tools pass unhelpful options to dpkg-source et "
529 "al by default, which can result in the built source package not being "
530 "identical to the git tree."
536 "In more detail: dgit push checks that the current HEAD corresponds to the ."
537 "dsc. It then pushes the HEAD to the suite's dgit-repos branch, adjusts the ."
538 "changes to include any .origs which the archive lacks and exclude .origs "
539 "which the archive has (so -sa and -sd are not needed when building for dgit "
540 "push), makes a signed git tag, edits the .dsc to contain the dgit metadata "
541 "field, runs debsign to sign the upload (.dsc and .changes), pushes the "
542 "signed tag, and finally uses dput to upload the .changes to the archive."
548 "dgit push always uses the package, suite and version specified in the debian/"
549 "changelog and the .dsc, which must agree. If the command line specifies a "
550 "suite then that must match too."
556 "When used on a git-debrebase branch, dgit calls git-debrebase to prepare the "
557 "branch for source package upload and push."
563 msgid "B<dgit push-source> [I<suite>]"
569 "Without B<-C>, builds a source package and dgit pushes it. Saying B<dgit "
570 "push-source> is like saying \"update the source code in the archive to match "
571 "my git HEAD, and let the autobuilders do the rest.\""
577 "With B<-C>, performs a dgit push, additionally ensuring that no binary "
578 "packages are uploaded."
584 msgid "B<dgit rpush> I<build-host>B<:>I<build-dir> [I<push args...>]"
590 "Pushes the contents of the specified directory on a remote machine. This is "
591 "like running dgit push on build-host with build-dir as the current "
592 "directory; however, signing operations are done on the invoking host. This "
593 "allows you to do a push when the system which has the source code and the "
594 "build outputs has no access to the key:"
598 #: ../dgit.1:286 ../dgit-maint-merge.7.pod:479
606 msgid "Clone on build host (dgit clone)"
610 #: ../dgit.1:287 ../dgit-maint-merge.7.pod:483
618 msgid "Edit code on build host (edit, git commit)"
622 #: ../dgit.1:288 ../dgit-maint-merge.7.pod:488
630 msgid "Build package on build host (dgit build)"
642 msgid "Test package on build host or elsewhere (dpkg -i, test)"
654 msgid "Upload by invoking dgit rpush on host with your GPG key."
660 "However, the build-host must be able to ssh to the dgit repos. If this is "
661 "not already the case, you must organise it separately, for example by the "
662 "use of ssh agent forwarding."
668 "The remaining arguments are treated just as dgit push would handle them."
674 "build-host and build-dir can be passed as separate arguments; this is "
675 "assumed to be the case if the first argument contains no : (except perhaps "
676 "one in [ ], to support IPv6 address literals)."
682 "You will need similar enough versions of dgit on the build-host and the "
683 "invocation host. The build-host needs gnupg installed, with your public key "
684 "in its keyring (but not your private key, obviously)."
690 msgid "B<dgit setup-new-tree>"
696 "Configure the current working tree the way that dgit clone would have set it "
697 "up. Like running B<dgit setup-useremail>, B<setup-mergechangelogs> and "
698 "B<setup-gitattributes> (but only does each thing if dgit is configured to do "
699 "it automatically). You can use these in any git repository, not just ones "
700 "used with the other dgit operations. Does B<not> run B<update-vcs-git> (as "
701 "that requires Debian packaging information)."
707 msgid "B<dgit setup-useremail>"
713 "Set the working tree's user.name and user.email from the distro-specific "
714 "dgit configuration (B<dgit-distro.>I<distro>B<.user-name> and B<.user-"
715 "email>), or DEBFULLNAME or DEBEMAIL."
721 msgid "B<dgit setup-mergechangelogs>"
727 "Configures a git merge helper for the file B<debian/changelog> which uses "
728 "B<dpkg-mergechangelogs>."
734 msgid "B<dgit setup-gitattributes>"
740 "Set up the working tree's B<.git/info/attributes> to disable all "
741 "transforming attributes for all files. This is done by defining a macro "
742 "attribute, B<dgit-defuse-attrs,> and applying it to B<*>. For why, see "
743 "B<GITATTRIBUTES> in B<dgit(7)>. Note that only attributes affecting the "
744 "working tree are suppressed. git-archive may remain exciting."
750 "If there is an existing macro attribute line B<[attr]dgit-defuse-attrs> in ."
751 "git/info/attributes, but it is insufficient, because it was made by an "
752 "earlier version of dgit and git has since introduced new transforming "
753 "attributes, this modifies the macro to disable the newer transformations."
759 "(If there is already a macro attribute line B<[attr]dgit-defuse-attrs> in ."
760 "git/info/attributes which does what dgit requires (whatever files it "
761 "effects), this operation does nothing further. This fact can be used to "
762 "defeat or partially defeat dgit setup-gitattributes and hence dgit setup-new-"
769 msgid "B<dgit quilt-fixup>"
775 "`3.0 (quilt)' format source packages need changes representing not only in-"
776 "tree but also as patches in debian/patches. dgit quilt-fixup checks whether "
777 "this has been done; if not, dgit will make appropriate patches in debian/"
778 "patches and also commit the resulting changes to git."
783 msgid "This is normally done automatically by dgit build and dgit push."
789 "dgit will try to turn each relevant commit in your git history into a new "
790 "quilt patch. dgit cannot convert nontrivial merges, or certain other kinds "
791 "of more exotic history. If dgit can't find a suitable linearisation of your "
792 "history, by default it will fail, but you can ask it to generate a single "
793 "squashed patch instead."
799 "When used with a git-debrebase branch, dgit will ask git-debrebase to "
800 "prepare patches. However, dgit can make patches in some situations where "
801 "git-debrebase fails, so dgit quilt-fixup can be useful in its own right. To "
802 "always use dgit's own patch generator instead of git-debrebase make-patches, "
803 "pass --git-debrebase=true to dgit."
808 msgid "See B<FORMAT 3.0 (QUILT)> in B<dgit(7)>."
814 msgid "B<dgit import-dsc> [I<sub-options>] I<../path/to/.dsc> [B<+>|B<..>]branch"
820 "Import a Debian-format source package, specified by its .dsc, into git, the "
821 "way dgit fetch would do."
827 "This does about half the work of dgit fetch: it will convert the .dsc into a "
828 "new, orphan git branch. Since dgit has no access to a corresponding source "
829 "package archive or knowledge of the history it does not consider whether "
830 "this version is newer than any previous import or corresponding git "
831 "branches; and it therefore does not make a pseudomerge to bind the import "
832 "into any existing git history."
838 "Because a .dsc can contain a Dgit field naming a git commit (which you might "
839 "not have), and specifying where to find that commit (and any history rewrite "
840 "table), import-dsc might need online access. If this is a problem (or "
841 "dgit's efforts to find the commit fail), consider --no-chase-dsc-distro or --"
842 "force-import-dsc-with-dgit-field."
847 msgid "There is only one sub-option:"
853 "B<--require-valid-signature> causes dgit to insist that the signature on "
854 "the .dsc is valid (using the same criteria as dpkg-source -x). Otherwise, "
855 "dgit tries to verify the signature but the outcome is reported only as "
856 "messages to stderr."
862 "If I<branch> is prefixed with B<+> then if it already exists, it will be "
863 "simply overwritten, no matter its existing contents. If I<branch> is "
864 "prefixed with B<..> then if it already exists and dgit actually imports the "
865 "dsc (rather than simply reading the git commit out of the Dgit field), dgit "
866 "will make a pseudomerge so that the result is necessarily fast forward from "
867 "the existing branch. Otherwise, if I<branch> already exists, dgit will stop "
868 "with an error message."
873 msgid "If I<branch> does not start with refs/, refs/heads/ is prepended."
879 msgid "B<dgit version>"
884 msgid "Prints version information and exits."
890 msgid "B<dgit clone-dgit-repos-server>I< destdir>"
896 "Tries to fetch a copy of the source code for the dgit-repos-server, as "
897 "actually being used on the dgit git server, as a git tree."
903 msgid "B<dgit print-dgit-repos-server-source-url>"
909 "Prints the url used by dgit clone-dgit-repos-server. This is hopefully "
910 "suitable for use as a git remote url. It may not be useable in a browser."
916 msgid "B<dgit print-dpkg-source-ignores>"
922 "Prints the -i and -I arguments which must be passed to dpkg-souce to cause "
923 "it to exclude exactly the .git directory and nothing else. The separate "
924 "arguments are unquoted, separated by spaces, and do not contain spaces."
930 msgid "B<dgit print-unapplied-treeish>"
936 "Constructs a tree-ish approximating the patches-unapplied state of your 3.0 "
937 "(quilt) package, and prints the git object name to stdout. This requires "
938 "appropriate .orig tarballs. This tree object is identical to your .origs as "
939 "regards upstream files. The contents of the debian subdirectory is not "
940 "interesting and should not be inspected; except that debian/patches will be "
941 "identical to your HEAD."
947 "To make this operate off-line, the access configuration key which is used to "
948 "determine the build-products-dir is the uncanonicalised version of the suite "
949 "name from the changelog, or (of course) dgit.default.build-products-dir. "
950 "See ACCESS CONFIGURATION, below."
955 msgid "This function is primarily provided for the benefit of git-debrebase."
959 #: ../dgit.1:496 ../git-debrebase.1.pod:477
967 msgid "B<--dry-run> | B<-n>"
973 "Go through the motions, fetching all information needed, but do not actually "
974 "update the output(s). For push, dgit does the required checks and leaves "
975 "the new .dsc in a temporary file, but does not sign, tag, push or upload."
981 msgid "B<--damp-run> | B<-L>"
987 "Go through many more of the motions: do everything that doesn't involve "
988 "either signing things, or making changes on the public servers."
994 msgid "B<-k>I<keyid>"
1000 "Use I<keyid> for signing the tag and the upload. The default comes from the "
1001 "distro's B<keyid> config setting (see CONFIGURATION, below), or failing "
1002 "that, the uploader trailer line in debian/changelog."
1008 msgid "B<--no-sign>"
1013 msgid "does not sign tags or uploads (meaningful only with push)."
1019 msgid "B<-p>I<package>"
1025 "Specifies that we should process source package I<package> rather than "
1026 "looking in debian/control or debian/changelog. Valid with dgit fetch and "
1033 msgid "B<--clean=git> | B<-wg>"
1039 "Use B<git clean -xdf> to clean the working tree, rather than running the "
1040 "package's rules clean target."
1046 "This will delete all files which are not tracked by git. (Including any "
1047 "files you forgot to git add.)"
1053 "B<--clean=>I<...> options other than dpkg-source are useful when the "
1054 "package's clean target is troublesome, or to avoid needing the build-"
1061 "dgit will only actually clean the tree if it needs to (because it needs to "
1062 "build the source package or binaries from your working tree). Otherwise it "
1063 "will just check that there are no untracked unignored files. See --"
1064 "clean=git[-ff],always, below."
1070 msgid "B<--clean=git-ff> | B<-wgf>"
1076 "Use B<git clean -xdff> to clean the working tree. Like git clean -xdf but "
1077 "it also removes any subdirectories containing different git trees (which "
1078 "only unusual packages are likely to create)."
1084 msgid "B<--clean=git>[B<-ff>]B<,always> | B<-wga> | B<-wgfa>"
1090 "Like --clean=git, but always does the clean and not just a check, deleting "
1091 "any untracked un-ignored files."
1097 msgid "B<--clean=check> | B<--clean=check,ignores> | B<-wc> | B<-wci>"
1103 "Merely check that the tree is clean (does not contain uncommitted files). "
1104 "Avoids running rules clean, and can avoid needing the build-dependencies."
1110 "With B<,ignores> or B<-wci>, untracked files covered by .gitignore are "
1111 "tolerated, so only files which show up as B<?> in git status (ie, ones you "
1112 "maybe forgot to git add) are treated as a problem."
1118 msgid "B<--clean=none> | B<-wn>"
1124 "Do not clean the tree, nor check that it is clean. Avoids running rules "
1125 "clean, and can avoid needing the build-dependencies. If there are files "
1126 "which are not in git, or if the build creates such files, a subsequent dgit "
1133 msgid "B<--clean=dpkg-source>[B<-d>] | B<-wd> | B<-wdd>"
1139 "Use dpkg-buildpackage to do the clean, so that the source package is cleaned "
1140 "by dpkg-source running the package's clean target. --clean=dpkg-source is "
1146 msgid "Without the extra B<d>, requires the package's build dependencies."
1152 "With B<...>-d or B<-wdd>, the build-dependencies are not checked (due to "
1153 "passing B<-d> to dpkg-buildpackage), which violates policy, but may work in "
1160 "The rules clean target will only be run if it is needed: when dgit is going "
1161 "to build source or binary packages from your working tree, rather than from "
1162 "your git branch (for example because of --include-dirty or because the "
1163 "binary package build uses your working tree)."
1169 "In all cases, dgit will check that there are (after rules clean, if "
1170 "applicable) no untracked un-ignored files, in case these are files you "
1171 "forgot to git add. (Except that this check is not done for a `3.0 (quilt)' "
1172 "package when dgit has to apply patches, dirtily, to the working tree.) If "
1173 "your package does not have a good .gitignore you will probably need --"
1174 "clean=dpkg-source,no-check aka -wdn."
1180 msgid "B<--clean=dpkg-source>[B<-d>]B<,no-check> | B<-wdn> | B<-wddn>"
1186 "Like --clean=dpkg-source, but does not care about untracked un-ignored files."
1192 msgid "B<--clean=dpkg-source>[B<-d>]B<,all-check> | B<-wda> | B<-wdda>"
1198 "Like --clean=dpkg-source, but fails even on ignored untracked files. This "
1199 "could perhaps be used to detect bugs in your rules clean target."
1205 msgid "B<-N> | B<--new>"
1211 "The package is or may be new in this suite. Without this, dgit will refuse "
1212 "to push. It may (for Debian, will) be unable to access the git history for "
1213 "any packages which have been newly pushed and have not yet been published."
1219 msgid "B<--include-dirty>"
1225 "Do not complain if the working tree does not match your git HEAD, and when "
1226 "building, include the changes from your working tree. This can be useful "
1227 "with build, if you plan to commit later. (dgit push will still ensure that "
1228 "the .dsc you upload and the git tree you push are identical, so this option "
1229 "won't make broken pushes.)"
1235 "Note that this does B<not> prevent dgit from cleaning your tree, so if the "
1236 "changes in your working tree are in the form of untracked files, those might "
1237 "still be deleted, especially with --clean=git. If you want to include "
1238 "untracked files in the build, you can use --clean=none or --clean=dpkg-"
1239 "source[-d] in addition to --include-dirty. Note that this combination can "
1240 "fail if the untracked files are under I<debian/patches/>."
1246 msgid "B<--ignore-dirty>"
1251 msgid "Deprecated alias for --include-dirty."
1257 msgid "B<--overwrite>[=I<previous-version>]"
1263 "Declare that your HEAD really does contain all the (wanted) changes from all "
1264 "versions listed in its changelog; or, all (wanted) changes from I<previous-"
1265 "version>. This promise is needed when your git branch is not a descendant "
1266 "of the version in the archive according to the git revision history."
1272 "It is safer not to specify I<previous-version>, and usually it's not "
1273 "needed. Just say B<--overwrite>, unless you know what you are doing."
1279 "This option is useful if you are the maintainer, and you have incorporated "
1280 "NMU changes into your own git workflow in a way that doesn't make your "
1281 "branch a fast forward from the NMU. It can also be useful when there was an "
1282 "upload made without dgit since the most recent upload made with dgit."
1288 "This option is also usually necessary the first time a package is pushed "
1289 "with dgit push to a particular suite. See B<dgit-maint->I<*>B<(7)>."
1295 "If I<previous-version> is not specified, dgit will check that the version in "
1296 "the archive is mentioned in your debian/changelog. (This will avoid losing "
1297 "changes, even with B<--overwrite>, unless someone committed to git a "
1298 "finalised changelog entry, and then made later changes to that version.) If "
1299 "I<previous-version> is specified, it ought to be the version currently in "
1306 "dgit push --overwrite will, if necessary, make a pseudo-merge (that is, "
1307 "something that looks like the result of git merge -s ours) to stitch the "
1308 "archive's version into your own git history, so that your push is a fast "
1309 "forward from the archive."
1315 "(In quilt mode B<gbp>, B<dpm>, B<unpatched> or B<baredebian>*, implying a "
1316 "split between the dgit view and the maintainer view, the pseudo-merge will "
1317 "appear only in the dgit view.)"
1323 msgid "B<--delayed>=I<days>"
1328 msgid "Upload to a DELAYED queue."
1334 "B<WARNING:> If the maintainer responds by cancelling your upload from the "
1335 "queue, and does not make an upload of their own, this will not rewind the "
1336 "git branch on the dgit git server. Other dgit users will then see your push "
1337 "(with a warning message from dgit) even though the maintainer wanted to "
1338 "abolish it. Such users might unwittingly reintroduce your changes."
1344 "If this situation arises, someone should make a suitable dgit push to update "
1345 "the contents of dgit-repos to a version without the controversial changes."
1351 msgid "B<--no-chase-dsc-distro>"
1357 "Tells dgit not to look online for additional git repositories containing "
1358 "information about a particular .dsc being imported. Chasing is the default."
1364 "For most operations (such as fetch and pull), disabling chasing means dgit "
1365 "will access only the git server for the distro you are directly working "
1366 "with, even if the .dsc was copied verbatim from another distro. For import-"
1367 "dsc, disabling chasing means dgit will work completely offline."
1373 "Disabling chasing can be hazardous: if the .dsc names a git commit which has "
1374 "been rewritten by those in charge of the distro, this option may prevent "
1375 "that rewrite from being effective. Also, it can mean that dgit fails to "
1376 "find necessary git commits."
1382 msgid "B<--save-dgit-view=>I<branch>|I<ref>"
1388 "Specifies that when split view is in operation, and dgit calculates (or "
1389 "looks up in its cache) a dgit view corresponding to your HEAD, the dgit "
1390 "view will be left in I<ref>. The specified ref is unconditionally "
1391 "overwritten, so don't specify a branch you want to keep."
1397 "This option is effective only with the following operations: quilt-fixup; "
1398 "push; all builds. And it is only effective when split view is actually in "
1405 "If ref does not start with refs/ it is taken to be a branch - i.e. refs/"
1406 "heads/ is prepended."
1411 msgid "B<--dgit-view-save> is a deprecated alias for --save-dgit-view."
1417 msgid "B<--deliberately->I<something>"
1423 "Declare that you are deliberately doing I<something>. This can be used to "
1424 "override safety catches, including safety catches which relate to distro-"
1425 "specific policies. The use of --deliberately is declared and published in "
1426 "the signed tags generated for you by dgit, so that the archive software can "
1427 "give effect to your intent, and for the benefit of humans looking at the "
1428 "history. The meanings of I<something>s understood in the context of Debian "
1429 "are discussed below:"
1435 msgid "B<--deliberately-not-fast-forward>"
1441 "Declare that you are deliberately rewriting history. This could be because "
1442 "your branch is not fast forward from the dgit server history, or not fast "
1443 "forward from a locally-synthesised dsc import."
1449 "When pushing to Debian, use this only when you are making a renewed upload "
1450 "of an entirely new source package whose previous version was not accepted "
1451 "for release from NEW because of problems with copyright or "
1452 "redistributibility; or, exceptionally, for the very first upload with dgit."
1458 "When split view is in operation, this also prevents the construction by dgit "
1459 "of a pseudomerge to make the dgit view fast forwarding. Normally only one "
1460 "of --overwrite (which creates a suitable pseudomerge) and --deliberately-"
1461 "not-fast-forward (which suppresses the pseudomerge and the fast forward "
1462 "checks) should be needed; --overwrite is usually better."
1468 msgid "B<--deliberately-include-questionable-history>"
1474 "Declare that you are deliberately including, in the git history of your "
1475 "current push, history which contains a previously-submitted version of this "
1476 "package which was not approved (or has not yet been approved) by the "
1477 "ftpmasters. When pushing to Debian, only use this option after verifying "
1478 "that: none of the rejected-from-NEW (or never-accepted) versions in the git "
1479 "history of your current push, were rejected by ftpmaster for copyright or "
1480 "redistributability reasons."
1486 msgid "B<--deliberately-fresh-repo>"
1492 "Declare that you are deliberately rewriting history and want to throw away "
1493 "the existing repo. Not relevant when pushing to Debian, as the Debian "
1494 "server will do this automatically when necessary."
1498 #: ../dgit.1:831 ../git-debpush.1.pod:114
1500 msgid "B<--quilt=linear>"
1506 "When fixing up source format `3.0 (quilt)' metadata, insist on generating a "
1507 "linear patch stack: one new patch for each relevant commit. If such a stack "
1508 "cannot be generated, fail. This is the default for Debian."
1514 "HEAD should be a series of plain commits (not touching debian/patches/), and "
1515 "pseudomerges, with as ancestor a patches-applied branch."
1519 #: ../dgit.1:843 ../git-debpush.1.pod:126
1521 msgid "B<--quilt=auto>"
1527 "When fixing up source format `3.0 (quilt)' metadata, prefer to generate a "
1528 "linear patch stack (as with --quilt=linear) but if that doesn't seem "
1529 "possible, try to generate a single squashed patch for all the changes made "
1530 "in git (as with --quilt=smash). This is not a good idea for an NMU in "
1535 #: ../dgit.1:852 ../git-debpush.1.pod:120
1537 msgid "B<--quilt=smash>"
1543 "When fixing up source format `3.0 (quilt)' metadata, generate a single "
1544 "additional patch for all the changes made in git. This is not a good idea "
1545 "for an NMU in Debian."
1551 "(If HEAD has any in-tree patches already, they must apply cleanly. This "
1552 "will be the case for any trees produced by dgit fetch or clone; if you do "
1553 "not change the upstream version nor make changes in debian/patches, it will "
1558 #: ../dgit.1:863 ../git-debpush.1.pod:131
1560 msgid "B<--quilt=nofix>"
1566 "Check whether source format `3.0 (quilt)' metadata would need fixing up, "
1567 "but, if it does, fail. You must then fix the metadata yourself somehow "
1568 "before pushing. (NB that dpkg-source --commit will not work because the "
1569 "dgit git tree does not have a B<.pc> directory.)"
1575 msgid "B<--quilt=nocheck> | B<--no-quilt-fixup>"
1581 "Do not check whether source format `3.0 (quilt)' metadata needs fixing up. "
1582 "If you use this option and the metadata did in fact need fixing up, dgit "
1589 msgid "B<-->[B<quilt=>]B<gbp> | B<-->[B<quilt=>]B<dpm> | B<--quilt=unapplied> | B<-->[B<quilt=>]B<baredebian>[B<+git>|B<+tarball>]"
1595 "Tell dgit that you are using a nearly-dgit-compatible git branch, aka a "
1596 "B<maintainer view>, and do not want your branch changed by dgit."
1602 "These quilt modes are known as B<splitting quilt modes>. See --split-view, "
1609 "B<--gbp> (short for B<--quilt=gbp>) is for use with git-buildpackage. Your "
1610 "HEAD is expected to be a patches-unapplied git branch, except that it might "
1611 "contain changes to upstream .gitignore files. This is the default for dgit "
1618 "B<--dpm> (short for B<--quilt=dpm>) is for use with git-dpm. Your HEAD is "
1619 "expected to be a patches-applied git branch, except that it might contain "
1620 "changes to upstream .gitignore files."
1626 "B<--quilt=unapplied> specifies that your HEAD is a patches-unapplied git "
1627 "branch (and that any changes to upstream .gitignore files are represented as "
1628 "patches in debian/patches)."
1634 "B<--quilt=baredebian> (or its alias B<--quilt=baredebian+git>) specifies "
1635 "that your HEAD contains only a debian/ directory, with any changes to "
1636 "upstream files represented as patches in debian/patches. The upstream "
1637 "source must be available in git, by default, in a suitably named git tag; "
1638 "see --upstream-commitish. In this mode, dgit cannot check that all edited "
1639 "upstream files are properly represented as patches: dgit relies on debian/"
1640 "patches being correct."
1646 "B<--quilt=baredebian+tarball> is like --quilt=baredebian, but is used when "
1647 "there is no appropriate upstream git history. To construct the dgit view, "
1648 "dgit will import your orig tarballs' contents into git. In this mode, dgit "
1649 "cannot check that the upstream parts of your upload correspond to what you "
1650 "intend: dgit relies on the right orig tarball(s) existing, and debian/"
1651 "patches being correct."
1657 "With --quilt=gbp|dpm|unapplied|baredebian*, dgit push (or precursors like "
1658 "quilt-fixup and build) will automatically generate a conversion of your git "
1659 "branch into the right form. dgit push will push the dgit-compatible form "
1660 "(the B<dgit view>) to the dgit git server. The dgit view will be visible "
1661 "to you in the dgit remote tracking branches, but your own branch will not be "
1662 "modified. dgit push will create a tag B<debian/>I<version> for the "
1663 "maintainer view, and the dgit tag B<archive/debian/>I<version> for the dgit "
1664 "view. dgit quilt-fixup will merely do some checks, and cache the maintainer "
1671 "B<If you have a branch like this it is essential to specify the appropriate "
1672 "--quilt= option!> This is because it is not always possible to tell: a "
1673 "patches-unapplied git branch of a package with one patch, for example, looks "
1674 "very like a patches-applied branch where the user has used git revert to "
1675 "undo the patch, expecting to actually revert it. However, if you fail to "
1676 "specify the right --quilt option, and you aren't too lucky, dgit will notice "
1677 "the problem and stop, with a useful hint."
1683 msgid "B<-d>I<distro> | B<--distro=>I<distro>"
1689 "Specifies that the suite to be operated on is part of distro I<distro>. "
1690 "This overrides the default value found from the git config option B<dgit-"
1691 "suite.>I<suite>B<.distro>. The only effect is that other configuration "
1692 "variables (used for accessing the archive and dgit-repos) used are B<dgit-"
1693 "distro.>I<distro>B<.*>."
1699 "If your suite is part of a distro that dgit already knows about, you can use "
1700 "this option to make dgit work even if your dgit doesn't know about the "
1701 "suite. For example, specifying B<-ddebian> will work when the suite is an "
1702 "unknown suite in the Debian archive."
1708 "To define a new distro it is necessary to define methods and URLs for "
1709 "fetching (and, for dgit push, altering) a variety of information both in the "
1710 "archive and in dgit-repos. How to set this up is not yet documented."
1716 msgid "B<--split-view=auto>|B<always>|B<never>"
1722 "Controls whether dgit operates a split view, separating your own branch (as "
1723 "Debian maintainer) from that shown to users of dgit clone and dgit fetch."
1729 "When split view is in operation dgit will not make or merge any commits onto "
1730 "your own branch. Specifically, only the dgit view will contain dgit's "
1731 "pseudomerges, which bring into the git history previous uploads made with "
1732 "dgit push, and any commits in debian/patches required to make a correct `3.0 "
1733 "(quilt)' source package."
1739 "B<auto> is the default, and splits the view only when needed: i.e., when you "
1740 "are working with a `3.0 (quilt)' source package and a splitting quilt mode: "
1741 "--[quilt=]gbp, dpm, unpatched or baredebian*."
1747 "B<always> splits the view regardless of the source format and the quilt mode."
1752 msgid "B<never> will cause dgit to fail if split view is needed."
1758 "When split view is in operation, the dgit view is visible in your local git "
1759 "clone, but only in refs specific to dgit: notably B<remotes/dgit/dgit/"
1760 ">I<suite> and B<archive/>I<distro>B</>I<version>."
1766 "Note that split view does not affect dgit fetch, and is not compatible with "
1773 msgid "B<-C>I<changesfile>"
1779 "Specifies the .changes file which is to be uploaded. By default dgit push "
1780 "looks for a single .changes file in the parent directory whose filename "
1781 "suggests it is for the right package and version."
1787 "If the specified I<changesfile> pathname contains slashes, the directory "
1788 "part is also used as the value for B<--build-products-dir>; otherwise, the "
1789 "changes file is expected in that directory (by default, in B<..>)."
1795 msgid "B<--upstream-commitish=>I<upstream>"
1801 "For use with --quilt=baredebian only. Specifies the commit containing the "
1802 "upstream source. This commit must be identical to your .orig tarball. The "
1803 "default is to look for one of the git tags I<U>B< v>I<U>B< upstream/>I<U> "
1804 "(in that order), where U is the upstream version."
1810 msgid "B<--rm-old-changes>"
1816 "When doing a build, delete any changes files matching "
1817 "I<package>B<_>I<version>B<_*.changes> before starting. This ensures that "
1818 "dgit push (and dgit sbuild) will be able to unambiguously identify the "
1819 "relevant changes files from the most recent build, even if there have been "
1820 "previous builds with different tools or options. The default is not to "
1821 "remove, but B<--no-rm-old-changes> can be used to override a previous --rm-"
1822 "old-changes or the .rm-old-changes configuration setting."
1828 "Note that B<dgit push-source> will always find the right .changes, "
1829 "regardless of this option."
1835 msgid "B<--build-products-dir=>I<directory>"
1841 "Specifies where to find and create tarballs, binary packages, source "
1842 "packages, .changes files, and so on."
1847 msgid "By default, dgit uses the parent directory (B<..>)."
1853 "Changing this setting may necessitate moving .orig tarballs to the new "
1854 "directory, so it is probably best to use the B<dgit.default.build-products-"
1855 "dir> configuration setting (see CONFIGURATION, below) which this command "
1856 "line option overrides)."
1862 msgid "B<--no-rm-on-error>"
1867 msgid "Do not delete the destination directory if clone fails."
1873 msgid "B<--dep14tag>"
1879 "Generates a DEP-14 tag (eg B<debian/>I<version>) as well as a dgit tag (eg "
1880 "B<archive/debian/>I<version>). This is the default."
1886 msgid "B<--no-dep14tag>"
1891 msgid "Do not generate a DEP-14 tag, except when split view is in operation."
1897 msgid "B<--always-dep14tag>"
1902 msgid "Obsolete alias for --dep14tag, retained for compatibility."
1914 "Prints debugging information to stderr. Repeating the option produces more "
1915 "output (currently, up to -DDDD is meaningfully different)."
1921 msgid "B<-c>I<name>B<=>I<value>"
1927 "Specifies a git configuration option, to be used for this run. dgit itself "
1928 "is also controlled by git configuration options."
1934 msgid "B<-v>I<version>|B<_> | B<--since-version=>versionI<|>B<_>"
1940 "Specifies the B<-v>I<version> option to pass to dpkg-genchanges, during "
1941 "builds. Changes (from debian/changelog) since this version will be included "
1942 "in the built changes file, and hence in the upload. If this option is not "
1943 "specified, dgit will query the archive and use the latest version uploaded "
1944 "to the intended suite."
1950 "Specifying B<_> inhibits this, so that no -v option will be passed to dpkg-"
1951 "genchanges (and as a result, only the last stanza from debian/changelog will "
1952 "be used for the build and upload)."
1958 msgid "B<-m>I<maintaineraddress>"
1963 msgid "Passed to dpkg-genchanges (eventually)."
1969 msgid "B<--ch:>I<option>"
1975 "Specifies a single additional option to pass, eventually, to dpkg-genchanges."
1981 "Options which are safe to pass include B<-C> (and also B<-si -sa -sd> "
1982 "although these should never be necessary with Debian since dgit "
1983 "automatically calculates whether .origs need to be uploaded.)"
1988 msgid "For other options the caveat below applies."
1994 msgid "B<--curl:>I<option> | B<--dput:>I<option> |..."
2000 "Specifies a single additional option to pass to B<curl>, B<dput>, "
2001 "B<debsign>, B<dpkg-source>, B<dpkg-buildpackage>, B<dpkg-genchanges>, "
2002 "B<sbuild>, B<pbuilder>, B<cowbuilder>, B<ssh>, B<dgit>, B<git-debrebase>, "
2003 "B<apt-get>, B<apt-cache>, B<gbp-pq>, B<gbp-build>, or B<mergechanges>. Can "
2004 "be repeated as necessary."
2010 "Use of this ability should not normally be necessary. It is provided for "
2011 "working around bugs, or other unusual situations. If you use these options, "
2012 "you may violate dgit's assumptions about the behaviour of its subprograms "
2013 "and cause lossage."
2019 "For dpkg-buildpackage, dpkg-genchanges, mergechanges and sbuild, the option "
2020 "applies only when the program is invoked directly by dgit. Usually, for "
2021 "passing options to dpkg-genchanges, you should use B<--ch:>I<option>."
2027 "Specifying --git is not effective for some lower-level read-only git "
2028 "operations performed by dgit, and also not when git is invoked by another "
2029 "program run by dgit."
2034 msgid "See notes below regarding ssh and dgit."
2040 "NB that --gpg:option is not supported (because debsign does not have that "
2041 "facility). But see B<-k> and the B<keyid> distro config setting."
2047 msgid "B<--curl!:>I<option> | B<--dput!:>I<option> |..."
2053 "Specifies an option to remove from the command line for a program called by "
2054 "dgit, as for B<-->I<program>B<:>I<option> (and the same caveats apply)."
2060 "Any options or arguments exactly identical to I<option> are removed. (It is "
2061 "not an error if there were none.)"
2067 "This can only be used to delete options which are always passed by default "
2068 "by dgit, or to undo a previous B<-->I<program>B<:>I<option>. It cannot be "
2069 "used to override option(s) dynamically decided on by dgit."
2075 msgid "B<--curl=>I<program> | B<--dput=>I<program> |..."
2081 "Specifies alternative programs to use instead of B<curl>, B<dput>, "
2082 "B<debsign>, B<dpkg-source>, B<dpkg-buildpackage>, B<dpkg-genchanges>, "
2083 "B<sbuild>, B<pbuilder>, B<cowbuilder>, B<gpg>, B<ssh>, B<dgit>, B<git-"
2084 "debrebase>, B<apt-get>, B<apt-cache>, B<git>, B<gbp-pq>, B<gbp-build>, or "
2091 "For B<dpkg-buildpackage>, B<dpkg-genchanges>, B<mergechanges> and B<sbuild>, "
2092 "this applies only when the program is invoked directly by dgit."
2098 "For B<dgit>, specifies the command to run on the remote host when dgit rpush "
2099 "needs to invoke a remote copy of itself. (dgit also reinvokes itself as the "
2100 "EDITOR for dpkg-source --commit; this is done using argv[0], and is not "
2101 "affected by --dgit=)."
2107 "B<gbp-build>'s value is used instead of gbp build or git-buildpackage. (The "
2108 "default is the latter unless the former exists on PATH.) B<gbp-pq>'s value "
2109 "is used instead of gbp pq. In both cases, unusually, the specified value is "
2110 "split on whitespace to produce a command and possibly some options and/or "
2117 "For pbuilder and cowbuilder, the defaults are B<sudo -E pbuilder> and B<sudo "
2118 "-E cowbuilder> respectively. Like with gbp-build and gbp pq, the specified "
2119 "value is split on whitespace."
2125 "For B<ssh>, the default value is taken from the B<DGIT_SSH> or B<GIT_SSH> "
2126 "environment variables, if set (see below). And, for ssh, when accessing the "
2127 "archive and dgit-repos, this command line setting is overridden by the git "
2128 "config variables B<dgit-distro.>I<distro>B<.ssh> and B<.dgit.default.ssh> "
2129 "(which can in turn be overridden with -c). Also, when dgit is using git to "
2130 "access dgit-repos, only git's idea of what ssh to use (eg, B<GIT_SSH>) is "
2137 msgid "B<--existing-package=>I<package>"
2143 "dgit push needs to canonicalise the suite name. Sometimes, dgit lacks a way "
2144 "to ask the archive to do this without knowing the name of an existing "
2145 "package. Without --new we can just use the package we are trying to push. "
2146 "But with --new that will not work, so we guess B<dpkg> or use the value of "
2147 "this option. This option is not needed with the default mechanisms for "
2148 "accessing the archive."
2154 msgid "B<-h>|B<--help>"
2160 msgid "B<--initiator-tempdir=>I<directory>"
2166 "dgit rpush uses a temporary directory on the invoking (signing) host. This "
2167 "option causes dgit to use I<directory> instead. Furthermore, the specified "
2168 "directory will be emptied, removed and recreated before dgit starts, rather "
2169 "than removed after dgit finishes. The directory specified must be an "
2170 "absolute pathname."
2176 msgid "B<--force->I<something>"
2182 "Instructs dgit to try to proceed despite detecting what it thinks is going "
2183 "to be a fatal problem. B<This is probably not going to work.> These options "
2184 "are provided as an escape hatch, in case dgit is confused. (They might also "
2185 "be useful for testing error cases.)"
2191 msgid "B<--force-import-dsc-with-dgit-field>"
2197 "Tell dgit import-dsc to treat a .dsc with a Dgit field like one without it. "
2198 "The result is a fresh import, discarding the git history that the person who "
2199 "pushed that .dsc was working with."
2205 msgid "B<--force-reusing-version>"
2211 "Carry on even though this involves reusing a version number of a previous "
2212 "push or upload. It is normally best to give different versions different "
2213 "numbers. Some servers (including, usually, the Debian server) will reject "
2214 "attempts to reuse or replace already-pushed versions."
2220 msgid "B<--force-uploading-binaries>"
2226 "Carry on and upload binaries even though dgit thinks your distro does not "
2233 msgid "B<--force-uploading-source-only>"
2239 "Carry on and do a source-only upload, without any binaries, even though dgit "
2240 "thinks your distro does not permit that, or does not permit that in this "
2247 msgid "B<--force-unrepresentable>"
2253 "Carry on even if dgit thinks that your git tree contains changes (relative "
2254 "to your .orig tarballs) which dpkg-source is not able to represent. Your "
2255 "build or push will probably fail later."
2261 msgid "B<--force-changes-origs-exactly>"
2267 "Use the set of .origs specified in your .changes, exactly, without regard to "
2268 "what is in the archive already. The archive may well reject your upload."
2274 msgid "B<--force-unsupported-source-format>"
2280 "Carry on despite dgit not understanding your source package format. dgit "
2281 "will probably mishandle it."
2287 msgid "B<--force-dsc-changes-mismatch>"
2293 "Do not check whether .dsc and .changes match. The archive will probably "
2294 "reject your upload."
2300 msgid "B<--force-import-gitapply-absurd> | B<--force-import-gitapply-no-absurd>"
2306 "Force on or off the use of the absurd git-apply emulation when running gbp "
2307 "pq import when importing a package from a .dsc. See Debian bug #841867."
2313 msgid "B<--for-push>"
2319 "Override the dgit-distro.distro.readonly configuration setting, to specify "
2320 "that we have read/write access and should use the corresponding git and "
2321 "achieve access approach even if the operation is a read-only one."
2325 #: ../dgit.1:1352 ../dgit-downstream-dsc.7.pod:150
2327 msgid "CONFIGURATION"
2333 "dgit can be configured via the git config system. You may set keys with git-"
2334 "config (either in system-global or per-tree configuration), or provide B<-"
2335 "c>I<key>B<=>I<value> on the dgit command line."
2340 msgid "Settings likely to be useful for an end user include:"
2346 msgid "B<dgit.default.build-products-dir>"
2352 "Specifies where to find the built files to be uploaded, when --build-"
2353 "products-dir is not specified. The default is the parent directory (B<..>)."
2357 #: ../dgit.1:1366 ../dgit-downstream-dsc.7.pod:286
2359 msgid "B<dgit-suite.>I<suite>B<.distro> I<distro>"
2365 "Specifies the distro for a suite. dgit keys off the suite name (which "
2366 "appears in changelogs etc.), and uses that to determine the distro which is "
2367 "involved. The config used is thereafter that for the distro."
2372 msgid "I<suite> may be a glob pattern."
2378 msgid "B<dgit.default.distro>I< distro>"
2383 msgid "The default distro for an unknown suite."
2389 "This is only used if no B</usr/share/distro-info/>I<somedistro>B<.csv> "
2390 "mentions the specified suite."
2396 msgid "B<dgit.default.default-suite>I< suite>"
2401 msgid "The default suite (eg for clone)."
2407 msgid "B<dgit.default.>*"
2413 "for each B<dgit-distro.>I<distro>B<.>*, the default value used if there is "
2414 "no distro-specific setting."
2420 msgid "B<dgit-distro.>I<distro>B<.clean-mode>"
2426 "One of the values for the command line --clean= option; used if --clean is "
2433 msgid "B<dgit-distro.>I<distro>B<.clean-mode-newer>"
2439 "Like .clean-mode, but ignored if the value is unknown to this version of "
2440 "dgit. Setting both .clean-mode and .clean-mode-newer is useful to provide a "
2441 "single git config compatible with different dgit versions."
2447 msgid "B<dgit-distro.>I<distro>B<.quilt-mode>"
2453 "One of the values for the command line --quilt= option; used if --quilt is "
2460 msgid "B<dgit-distro.>I<distro>B<.split-view>"
2466 msgid "B<dgit-distro.>I<distro>B<.rm-old-changes>"
2472 "Boolean, used if neither --rm-old-changes nor --no-rm-old-changes is "
2473 "specified. The default is not to remove."
2479 msgid "B<dgit-distro.>I<distro>B<.readonly> B<auto>|B<a> | B<true>|B<t>|B<y>|B<1> | B<false>|B<f>|B<n>|B<0>"
2485 "Whether you have push access to the distro. For Debian, it is OK to use "
2486 "auto, which uses readonly mode if you are not pushing right now; but, "
2487 "setting this to false will avoid relying on the mirror of the dgit git "
2488 "repository server."
2494 msgid "B<dgit-distro.>I<distro>B<.keyid>"
2499 msgid "See also B<-k>."
2505 msgid "B<dgit-distro.>I<distro>B<.mirror>I< url>"
2511 msgid "B<dgit-distro.>I<distro>B<.username>"
2516 msgid "Not relevant for Debian."
2520 #: ../dgit.1:1425 ../dgit-downstream-dsc.7.pod:242
2522 msgid "B<dgit-distro.>I<distro>B<.upload-host>"
2527 msgid "Might be useful if you have an intermediate queue server."
2533 msgid "B<dgit-distro.>I<distro>B<.user-name>I< >B<dgit-distro.>I<distro>B<.user-email>"
2539 "Values to configure for user.name and user.email in new git trees. If not "
2540 "specified, the DEBFULLNAME and DEBEMAIL environment variables are used, "
2541 "respectively. Only used if .setup-usermail is not disabled."
2547 msgid "B<dgit-distro.>I<distro>B<.setup-useremail>"
2553 "Whether to set user.name and user.email in new git trees. True by default. "
2554 "Ignored for dgit setup-useremail, which does it anyway."
2560 msgid "B<dgit-distro.>I<distro>B<.setup-mergechangelogs>"
2566 "Whether to set up a merge driver which uses dpkg-mergechangelogs for debian/"
2567 "changelog. True by default. Ignored for dgit setup-mergechangelogs, which "
2574 msgid "B<dgit-distro.>I<distro>B<.setup-gitattributes>"
2580 "Whether to configure .git/info/attributes to suppress checkin/checkout file "
2581 "content transformations in new git trees. True by default. Ignored for "
2582 "dgit setup-gitattributes, which does it anyway."
2588 msgid "B<dgit-distro.>I<distro>B<.cmd->I<cmd>"
2593 msgid "Program to use instead of I<cmd>. Works like B<-->I<cmd>B<=>... ."
2599 msgid "B<dgit-distro.>I<distro>B<.opts->I<cmd>"
2605 "Extra options to pass to I<cmd>. Works like B<-->I<cmd>B<:>... . To pass "
2606 "several options, configure multiple values in git config (with git config --"
2607 "add). The options for B<dgit.default.opts->I<cmd> and B<dgit-distro."
2608 ">I<distro>B</push.opts->I<cmd> are all used, followed by options from dgit's "
2615 msgid "ACCESS CONFIGURATION"
2621 "There are many other settings which specify how a particular distro's "
2622 "services (archive and git) are provided. These should not normally be "
2623 "adjusted, but are documented for the benefit of distros who wish to adopt "
2630 msgid "B<dgit-distro.>I<distro>B<.nominal-distro>"
2635 msgid "Shown in git tags, Dgit fields, and so on."
2641 msgid "B<dgit-distro.>I<distro>B<.alias-canon>"
2646 msgid "Used for all access configuration lookup."
2652 msgid "B<dgit-distro.>I<distro>B</push.>*"
2658 "If set, overrides corresponding non B</push> config when B<readonly=false>, "
2659 "or when pushing and B<readonly=auto>."
2665 msgid "B<dgit-distro.>I<distro>B<.git-url>"
2671 msgid "B<dgit-distro.>I<distro>B<.git-url>[B<-suffix>]"
2677 msgid "B<dgit-distro.>I<distro>B<.git-proto>"
2683 msgid "B<dgit-distro.>I<distro>B<.git-path>"
2689 msgid "B<dgit-distro.>I<distro>B<.git-check> B<true>|B<false>|B<url>|B<ssh-cmd>"
2695 msgid "B<dgit-distro.>I<distro>B<.git-check-suffix>"
2701 msgid "B<dgit-distro.>I<distro>B<.diverts.divert> B<new-distro>|B</>I<distro-suffix>"
2707 msgid "B<dgit-distro.>I<distro>B<.git-create>I< >B<ssh-cmd>I<|>B<true>"
2713 msgid "B<dgit-distro.>I<distro>B<.archive-query> B<ftpmasterapi:> | B<madison:>I<distro> | B<dummycat:>I</path> | B<sshpsql:>I<user>B<@>I<host>B<:>I<dbname>B< >|B< aptget:>"
2719 msgid "B<dgit-distro.>I<distro>B<.archive-query->(B<url>|B<tls-key>|B<curl-ca-args>)"
2725 msgid "B<dgit-distro.>I<distro>B<.madison-distro>"
2731 msgid "B<dgit-distro.>I<distro>B<.archive-query-default-component>"
2737 msgid "B<dgit-distro.>I<distro>B<.dgit-tag-format>"
2743 msgid "B<dgit-distro.>I<distro>B<.dep14tag> B<want>|B<no>[|B<always>]"
2749 msgid "B<dgit-distro.>I<distro>B<.ssh>"
2755 msgid "B<dgit-distro.>I<distro>B<.sshpsql-dbname>"
2761 msgid "B<dgit-distro.>I<distro>B<.>(B<git>|B<sshpsql>)B<->(B<user>|B<host>|B<user-force>)"
2767 msgid "B<dgit-distro.>I<distro>B<.backports-quirk>"
2773 msgid "B<dgit-distro.>I<distro>B<.rewrite-map-enable>"
2779 msgid "B<dgit-distro.>I<distro>B<.source-only-uploads> B<ok>|B<always>|B<never>|B<not-wholly-new>"
2785 msgid "B<dgit.default.old-dsc-distro>"
2791 msgid "B<dgit.dsc-url-proto-ok.>I<protocol>"
2797 msgid "B<dgit.dsc-url-proto-ok.bad-syntax>"
2803 msgid "B<dgit.default.dsc-url-proto-ok>"
2809 msgid "B<dgit.vcs-git.suites> I<suite>[B<;>...]"
2815 msgid "ENVIRONMENT VARIABLES"
2821 msgid "B<DGIT_SSH>, B<GIT_SSH>"
2827 "specify an alternative default program (and perhaps arguments) to use "
2828 "instead of ssh. DGIT_SSH is consulted first and may contain arguments; if "
2829 "it contains any whitespace will be passed to the shell. GIT_SSH specifies "
2830 "just the program; no arguments can be specified, so dgit interprets it the "
2831 "same way as git does. See also the --ssh= and --ssh: options."
2837 msgid "B<DEBEMAIL>, B<DEBFULLNAME>"
2843 "Default git user.email and user.name for new trees. See B<dgit setup-new-"
2850 msgid "B<gpg>, B<dpkg->..., B<debsign>, B<git>, [B<lib>]B<curl>, B<dput>"
2856 "and other subprograms and modules used by dgit are affected by various "
2857 "environment variables. Consult the documentation for those programs for "
2870 "There should be a `dgit rebase-prep' command or some such to turn a fast-"
2871 "forwarding branch containing pseudo-merges back into a rebasing patch "
2872 "stack. It might have to leave a note for a future dgit push."
2878 "If the dgit push fails halfway through, it is not necessarily restartable "
2879 "and idempotent. It would be good to check that the proposed signing key is "
2880 "available before starting work."
2886 "dgit's build functions, and dgit push, may make changes to your current "
2887 "HEAD. Sadly this is necessary for packages in the `3.0 (quilt)' source "
2888 "format. This is ultimately due to what I consider design problems in quilt "
2895 "--dry-run does not always work properly, as not doing some of the git "
2896 "fetches may result in subsequent actions being different. Doing a non-dry-"
2897 "run dgit fetch first will help. --damp-run is likely to work much better."
2901 #: ../dgit.1:1575 ../dgit.7:23 ../dgit-user.7.pod:447
2902 #: ../dgit-nmu-simple.7.pod:137 ../dgit-maint-native.7.pod:126
2903 #: ../dgit-maint-merge.7.pod:524 ../dgit-maint-gbp.7.pod:136
2904 #: ../dgit-maint-debrebase.7.pod:782 ../dgit-downstream-dsc.7.pod:352
2905 #: ../dgit-sponsorship.7.pod:321 ../dgit-maint-bpo.7.pod:140
2906 #: ../git-debrebase.1.pod:634 ../git-debrebase.5.pod:678
2907 #: ../git-debpush.1.pod:261
2915 "B<dgit>(7), B<dgit-*>(7), B<curl>(1), B<dput>(1), B<debsign>(1), B<git-"
2916 "config>(1), B<git-buildpackage>(1), B<dpkg-buildpackage>(1),"
2921 msgid "https://browse.dgit.debian.org/"