Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
But for many packages the real git history
does not exist,
or has not been published in a dgitish form.
But for many packages the real git history
does not exist,
or has not been published in a dgitish form.
-So yuu may find that the history is a rather short
+So you may find that the history is a rather short
history invented by dgit.
dgit histories often contain automatically-generated commits,
history invented by dgit.
dgit histories often contain automatically-generated commits,
is to build the package for all the architectures you
have enabled.
You'll need a chroot for each of the secondary architectures.
is to build the package for all the architectures you
have enabled.
You'll need a chroot for each of the secondary architectures.
-This iw somewhat tiresome,
+This is somewhat tiresome,
even though Debian has excellent tools for managing chroots.
C<sbuild-createchroot> from the sbuild package is a
good starting point.
even though Debian has excellent tools for managing chroots.
C<sbuild-createchroot> from the sbuild package is a
good starting point.
your desperate last resort is to try
using the same version number
as the official package for your own package.
your desperate last resort is to try
using the same version number
as the official package for your own package.
-(The verseion is controlled by C<debian/changelog> - see above).
+(The version is controlled by C<debian/changelog> - see above).
This is not ideal because it makes it hard to tell what is installed,
and because it will mislead and confuse apt.
This is not ideal because it makes it hard to tell what is installed,
and because it will mislead and confuse apt.