Commit modifications to the emdebian patch files back to Emdebian SVN without rebuilding, e.g. once a failed build has been repaired. Requires a subversion working directory which can be provided by unpacking the source with emsource. The working copy must have been checked out with developer access. emsource will use developer access if a valid Emdebian SVN username is available.

Note that the build log will need to be added to svn and checked in separately.

--svn-only is disabled when using machine:variant customisation patches via emsource -m.

Read the debian/xcontrol file (if any) and parse the list of Build-Cross-Depends: and call apt-cross to install the cross dependencies.

See emdebuild support for debian/xcontrol.

Override the default architecture (set by dpkg-cross).

Increment the emdebian version before building. Note that, in most cases, it is advisable to edit debian/changelog and add an explanatory message before uploading the built package. emdebuild merely adds a very brief comment.

When building a package that has been updated upstream, the -n option can be used to restore the effect of a default Emdebian version if the emdebian-changelog.patch could not be applied.

Commit modifications to the emdebian patch files back to Emdebian SVN upon a successful build. Requires a subversion working directory which can be provided by unpacking the source with emsource. The working copy must have been checked out with developer access. emsource will use developer access if a valid Emdebian SVN username is available.

If the build fails, emdebuild can be restarted and the patches committed to Emdebian SVN once the build has been fixed using the -svn-only option.

--svn will abort the SVN commit when using machine:variant customisation patches via emsource -m.

Sign the changes file created by the underlying dpkg-buildpackage. Many repositories require changes files to be signed with an authorised GnuPG key. If ~/.devscripts is configured so that DEBUILD_DPKG_BUILDPACKAGE_OPTS options specify that dpkg-buildpackage should not sign the changes file directly, this option can be used to call debsign with the generated changes file at the end of the build. Experience has shown that even when dpkg-buildpackage is unable to sign the changes file, running debsign directly succeeds.

be verbose - repeat once for extra verbosity. Most users are highly recommended to use at least one level of verbosity.

be quiet. emdebuild will be very quiet with this option, only essential warnings and messages from the build process itself are output. Intended for automated buildd purposes.

print the usage message and exit.

print the usage message and exit.