Joey Hess writes ("Bug#720895: build with dirty work tree"):
> Package: dgit
> Version: 0.11
> Severity: minor
>
> Is it necessary for dgit build to check the work tree is clean of
> uncommitted changes before
> allowing a build to run?
Not in principle, no. However, if you run the build with uncommited
changes the push will fail unless you commit them later because the
.dsc is generated from the working tree, not the git commit. Also,
build may need to do the quilt fixup step and that can't sanely be
done with a dirty working tree.
There should IMO be an option "--clean=perfect" which generates the
.dsc from the git HEAD.
> My personal preferred workflow is to make changes, build them, test
> them, and only once I am satisfied, commit them. This is particularly
> the case when using UNRELEASED in the changelog, since if if commit a
> s/UNRELEASED/unstable/ before I actually make the release, I may
> forget that I've not released it.
Hmmm. So you'd be satisfied with an option to suppress the clean
check. It would have to suppress the quilt fixup too, which would run
the risk, with a quilty package, of failing the push.
Ian.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
