Okay it looks like I solved the problem myself, but figured that I
should recored it in the list for posterity. The first problem I had
(even before the current question), was that I got errors that all
started with:
"dpkg-source: error: cannot represent change to ..."
This seemed to have to do with binary files that were created, but now
removed. In this case they were all *.pyc, *.o, *.so files. I removed
them by running:
$ for file in $(find . -name '*.pyc'); do rm -v $file; done
$ for file in $(find . -name '*.o'); do rm -v $file; done
$ for file in $(find . -name '*.so'); do rm -v $file; done
After that it produced the error output in my last email. At that point
I did as it asked. I.e. I executed this:
$ dpkg-source --commit
I called the commit "trash" and then didn't add a commit message.
However this now left the commit applied to the code which I did not
want. So then I ran
$ quilt delete
which deleted that last applied commit (i.e. "trash"). This seems to
have put me back where I started (on my own final commit which I
actually did want).
This seems to work, but it seems odd that it's necessary. Possibly
there's something smarter?
Cheers,
Thomas
