dgit push always uses the package, suite and version specified in the
debian/changelog and the .dsc, which must agree. If the command line
specifies a suite then that must match too.
dgit push always uses the package, suite and version specified in the
debian/changelog and the .dsc, which must agree. If the command line
specifies a suite then that must match too.
.TP
\fBdgit rpush\fR \fIbuild-host\fR\fB:\fR\fIbuild-dir\fR [\fIpush args...\fR]
Pushes the contents of the specified directory on a remote machine.
.TP
\fBdgit rpush\fR \fIbuild-host\fR\fB:\fR\fIbuild-dir\fR [\fIpush args...\fR]
Pushes the contents of the specified directory on a remote machine.
push will still ensure that the .dsc you upload and the git tree
you push are identical, so this option won't make broken pushes.)
.TP
push will still ensure that the .dsc you upload and the git tree
you push are identical, so this option won't make broken pushes.)
.TP
Declare that even though your git branch is not a descendant
of the version in the archive
according to the revision history,
Declare that even though your git branch is not a descendant
of the version in the archive
according to the revision history,
by those in charge of the distro,
this option may prevent that rewrite from being effective.
Also,
by those in charge of the distro,
this option may prevent that rewrite from being effective.
Also,
Tell dgit import-dsc to treat a .dsc with a Dgit field
like one without it.
The result is a fresh import,
Tell dgit import-dsc to treat a .dsc with a Dgit field
like one without it.
The result is a fresh import,