it becomes public (ie, make the repo available much more promptly when
the package passes NEW). Closes:#849789.
- Documentation [Sean Whitton]:
- * dgit-maint-merge(7): Use git-deborig(1). Closes:#850953.
+ Documentation:
+ * dgit-maint-merge(7): Use git-deborig(1).
+ [Sean Whitton] Closes:#850953.
+ * dgit-user(7): Fix some typos.
Test suite:
* infra: mirroring and policy hooks: Improve some debugging output.
they may modify files which are also committed to git,
or leave outputs and teporary files not covered by C<.gitignore>.
-Kf you always commit,
+If you always commit,
you can use
=over 4
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 verseion is controlled by C<debian/changelog> - see above).
This is not ideal because it makes it hard to tell what is installed,
-because it will mislead and confuse apt.
+and because it will mislead and confuse apt.
With the "same number" approach you may still get errors like