| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
By passing $patterns= [ ... ]. No functional change yet as no call
site does this.
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
|
|
|
|
|
|
|
| |
Provide debiantag_new as well as debiantag_old. Change the docs
and an important comment.
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
| |
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
|
|
|
|
| |
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
Use `confess' which produces a stack trace. And don't forget to use
Data::Dumper;
Bug introduced in e6ce71a87a1c "Move various useful functions into
Dgit.pm [...]".
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.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This test does not yet do all that we want, but it does some things
and then exits 0.
The current intent for the future is written in prose in the rest of
the file.
|
|
|
|
| |
Otherwise pushes will necessarily (spuriously) fail.
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
The patch queue branch is not really very useful. Certainly, the
build tests will require the patch queue branch.
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
This updates "Test suite: When sbuild fails, do not crash", to arrange
that in this situation we do leave a message in the $bmlog, where it
will be reported (eg) by diff. This makes debugging less confusing in
cases where the log is indeed missing.
|
|
|
|
|
| |
This function is useful for setting up a test case --quilt=gbp working
tree and corresponding archive contents, ready for substantive tests.
|
|
|
|
| |
This will allow other tests to check dgit sbuild.
|
|
|
|
|
| |
Teach bm-guess-e-source-e-targets about sbuild, so this knowledge can
be reused.
|
|
|
|
|
| |
Teach bm-guess-e-source-e-targets about dgit build-source, so this
knowledge can be reused.
|
|
|
|
|
| |
We are going to want to run some build modes tests on other exciting
trees.
|
|
|
|
|
|
|
| |
This working tree has some patch queues etc. in it, which will be
useful for testing --quilt=gbp.
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
|
| |
|
|
|
|
|
| |
Utility script for invoking gbp pq. I think I will want to swallow
this into a t-* function in tests/lib.
|
| |
|
| |
|
|
|
|
|
| |
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.
|