| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We are going to change the tag name of the main signed tag used by
dgit to signal the user's intent to the archive server.
Prepare for this by changing debiantag to debiantag_old and changing
all call sites outside dgit itself.
dgit will want to be able to generate either, depending on whether
it's cooperating in an rpush with a new or old dgit so reintroduce a
wrapper called debiantag there. This will also allow us to have dgit
generate old tags for testing.
No functional change.
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
|
|
|
|
|
|
|
| |
progress, supplementary-message, previously, and param csuite, were
all missing. Document them.
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
|
|
|
|
|
| |
We now do set $split_brain, and we don't do anythig with the cached
dgit view, so we'll crash at the die, in a moment.
|
|
|
|
| |
When it finds multiple subdirs, print them.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When system(3perl) fails due to syscall error, it sets only $!. When
it succeeds it sets only $? and sometimes trashes $!. Conversely,
close of a popened filehandle always sets both in all cases.
Document this in a comment.
So when using system and relying on $?/$! (rather than looking at
system's return value), such as when about to use failedcmd, it's
necessary to initialise $? to -1.
Fix the three call sites where system might be followed by failedcmd
but this wasn't done.
|
|
|
|
|
| |
If the remote command failed, do not try to match the undef value
against the various regexps.
|
|
|
|
|
| |
failecmd wants to look at $? too and anyway the full command is not of
much interest in these cases.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Look only at dgit and Debian/Dgit.
The prompt for this is that some of our submodules seem to dynamically
load some of their components depending on what dgit does, making the
cache key unstable.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
reset from printing a confusing message about HEAD.
|
|
|
|
|
|
| |
Otherwise the cache entry's .dsc contains the hash of a fake
debian.tar.gz which has had a timestamp put in it by gzip, defeating
the cache.
|
| |
|
|
|
|
| |
Not documented yet.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Everywhere we invoke dpkg-buildpackage, check if we need to apply the
patches. And at the end of every command that might have done this,
check if we did, and unapply them if so.
We don't try to unapply patches in case of error. That seems likely
to be quite fragile.
Print a warning when we apply patches, suggesting ways to avoid the
need.
|
| |
|
|
|
|
|
| |
We use runcmd shell_cmd for gbp pq import, and the other commands not
produce undesirable output.
|
| |
|
|
|
|
| |
This can make a radical difference!
|
|
|
|
|
|
|
| |
Do the quiltify_splitbrain_needed if there _are_ patches, not if there
aren't. And if we're told it was an unapplied tree, check that HEAD
and orig are indeed the same (excluding debian/*, of course) and print
a useful message if not.
|
| |
|
|
|
|
|
| |
And, after the source build is done, copy the resulting files out into
the invocation directory's parent, where people expect to find them.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* Move the fast forward die to where we will need to make the
synthetic commit, so that the tree equality check is done on the
thing we will actually push.
* Crash if we are trying to do split brain without split build.
(This should never happen.)
* Set split build if we need split brain.
|
|
|
|
|
| |
This variable name was very confusing. Also, add a comment explaining
the semantics.
|
| |
|
| |
|
| |
|
|
|
|
| |
And explain why in a comment.
|
|
|
|
| |
This code does not work properly yet; it will be fixed soon.
|
| |
|
|
|
|
|
|
|
|
|
| |
Close our FH onto the file, and run git diff to fill it with the
actual diff. Add the file to series. Use git add and git commit to
commit the patch to the private git branch.
Now most of the code to generate the .gitignore properly is present, I
think, but not debugged.
|
|
|
|
|
| |
When we need to make the .gitignore patch, there may not yet be any
debian/patches directory.
|
|
|
|
| |
So far we still don't generate the patch.
|
|
|
|
| |
It is going to need this extra info in a moment.
|
|
|
|
|
| |
We are going to need this information to construct the substantive
diff for the .gitignores patch.
|
| |
|
| |
|
|
|
|
| |
Generate a patch header, for now. Still not finished.
|
|
|
|
|
| |
We want this to apply to any commits we use git to make, not just
gbp-pq.
|
|
|
|
|
|
| |
* Direct gbp-pq's stdout to /dev/null
* Specify GIT_COMMITER_* so that the results are reproducible
* Detect .gitignore problem
|
|
|
|
| |
We are going to want this in a moment.
|
|
|
|
|
|
|
|
| |
We are going to want this (so that we can set GIT_... variables to the
pieces to make git construct commits the way we want).
Both current call sites provide scalar context, so no functional
change.
|
|
|
|
|
|
| |
This will make it a bit easier to reuse it. Actually AFAICT it turns
out (looking at the rest of the branch) that this is not needed, but
it's nicer for the future I think.
|