| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
|
| |
Honour $2 being the suite codename, defaulting to sid.
No functional change, since no-one passes this argument right now.
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
|
|
|
|
|
|
|
|
|
|
| |
t-archive-none now honours `suitespecs', which defaults to just
`sid:unstable'.
No overall functional change since no-one sets suitespecs to a
non-default value.
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We introduce a new `maint' possibility in to the dgit-tag-format
access cfg list, presence of which indicates that the receiver is
content to receive DEP-14-style maintainer-view (ie, non-dgit0 tags.
For now, we default this to true. However, repos handled by
dgit-repos-server cannot currently cope with this, because:
* dgit-repos-server currently tries to be compatible with old
dgits which send DEP-14-named dgit tags;
* dgit-repos-server doesn't currently permit the creation of
`extraneous' (ie, non-dgit) tags and branches.
So for Debian, we do not set this flag.
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently this is `test-dummy' (the distro the tests work with).
Have checked that after this commit
find tests -type f | xargs perl -i~ -pe 's/\$tagpfx/test-dummy/g'
puts everything back. (This does not prove I have changed the right
set of occurrences, but it does suggest that each actual change is
good.)
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>
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
The patch queue branch is not really very useful. Certainly, the
build tests will require the patch queue branch.
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
existing taints.
|
|
|
|
|
|
|
|
|
| |
We are going to introduce this option soon. It is not supposed to
actually have very much overall effect, although it will replumb the
way dgit goes about making the source package.
So the tests are just the same as the normal tests only with the
additional option.
|
| |
|
|
|
|
|
| |
Otherwise one failure causes the tests to be abandoned, which is not
usually desirable.
|
|
|
|
|
|
| |
Some of the tools we use, it turns out, do not update properly: they
overwrite in place. This can cause inadvertant changes to a tartree
opened for editing.
|
| |
|
|
|
|
| |
Simply HEAD is not displayed by gitk, which is rather a shame.
|
|
|
|
|
| |
When we unmerged some old A+B merged refs, make a note to merge them
again. This saves the user calling gitfetchinfo-merge again.
|
|
|
|
|
|
| |
* Turn on perl warnings
* Use strict
* When removing old merged refs, insist that we aren't handling A+A
|
|
|
|
|
|
|
|
|
|
|
|
| |
The sequence
gitfetchinfo-merge A B
gitfetchinfo A
gitfetchinfo-merge A B
might leave inappropriate A+B refs, because nothing would delete them.
So, have gitfetchinfo A unmerge any A+B or B+A refs. (This does mean
that the user of gitfetchinfo A is now promising that any remotes A+B
or B+A were made with gitfetchinfo-merge.)
|
|
|
|
|
|
| |
We want the commit timestamps to be predictable (ie, to depend on the
source info only), so that we don't show spurious disagreement between
two working trees. So, use the timestamp of the HEAD commit.
|
| |
|
| |
|
|
|
|
| |
Help with comparing different test case git working tree tarballs.
|
| |
|
|
|
|
|
|
| |
Soon, we are going to be stricter about detecting ambiguity about
which .changes file is intended when different build modes have been
used.
|
| |
|
|
|
|
|
| |
zealot is very slow and we need to give the other processes time to
rollback and release the lock.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This avoids most date dependencies: unless other measures are taken,
the commits and tags are identical iff they are constructed
identically. This makes the test suite more deterministic.
In drs-push-rejects test, increment them explicitly, so as to make all
of mktag's tags distinct objects.
Otherwise it can generate identical tags (now, always; previously,
only sometimes on fast computers), causing spurious variations in
behaviour (eg, things not being rejected because they do not represent
any change).
|
|
|
|
| |
Cosmetic change only.
|
|
|
|
|
| |
... due to sed not finding the log file. Instead, simply tolerate the
absence of the log file.
|
|
|
|
| |
don't need build-depends.
|
|
|
|
| |
when it succeeds
|
| |
|
| |
|