2008-11-12 17:59:02 +00:00
|
|
|
#!/bin/sh
|
|
|
|
|
|
|
|
|
|
test_description='git repack works correctly'
|
|
|
|
|
|
|
|
|
|
. ./test-lib.sh
|
|
|
|
|
|
2018-04-15 15:36:13 +00:00
|
|
|
commit_and_pack() {
|
2019-11-27 19:53:45 +00:00
|
|
|
test_commit "$@" 1>&2 &&
|
2018-04-15 15:36:13 +00:00
|
|
|
SHA1=$(git pack-objects --all --unpacked --incremental .git/objects/pack/pack </dev/null) &&
|
|
|
|
|
echo pack-${SHA1}.pack
|
|
|
|
|
}
|
|
|
|
|
|
2008-11-12 17:59:05 +00:00
|
|
|
test_expect_success 'objects in packs marked .keep are not repacked' '
|
2019-11-27 19:53:47 +00:00
|
|
|
echo content1 >file1 &&
|
|
|
|
|
echo content2 >file2 &&
|
2008-11-12 17:59:02 +00:00
|
|
|
git add . &&
|
2010-04-14 22:09:57 +00:00
|
|
|
test_tick &&
|
2008-11-12 17:59:02 +00:00
|
|
|
git commit -m initial_commit &&
|
|
|
|
|
# Create two packs
|
|
|
|
|
# The first pack will contain all of the objects except one
|
|
|
|
|
git rev-list --objects --all | grep -v file2 |
|
2019-11-27 19:53:45 +00:00
|
|
|
git pack-objects pack &&
|
2008-11-12 17:59:02 +00:00
|
|
|
# The second pack will contain the excluded object
|
|
|
|
|
packsha1=$(git rev-list --objects --all | grep file2 |
|
|
|
|
|
git pack-objects pack) &&
|
2014-01-23 19:55:18 +00:00
|
|
|
>pack-$packsha1.keep &&
|
2008-11-12 17:59:02 +00:00
|
|
|
objsha1=$(git verify-pack -v pack-$packsha1.idx | head -n 1 |
|
|
|
|
|
sed -e "s/^\([0-9a-f]\{40\}\).*/\1/") &&
|
|
|
|
|
mv pack-* .git/objects/pack/ &&
|
2014-06-11 06:32:45 +00:00
|
|
|
git repack -A -d -l &&
|
2008-11-12 17:59:02 +00:00
|
|
|
git prune-packed &&
|
2019-11-27 19:53:49 +00:00
|
|
|
for p in .git/objects/pack/*.idx
|
|
|
|
|
do
|
2008-11-12 17:59:02 +00:00
|
|
|
idx=$(basename $p)
|
|
|
|
|
test "pack-$packsha1.idx" = "$idx" && continue
|
2019-11-27 19:53:49 +00:00
|
|
|
if git verify-pack -v $p | egrep "^$objsha1"
|
|
|
|
|
then
|
2008-11-12 17:59:02 +00:00
|
|
|
found_duplicate_object=1
|
|
|
|
|
echo "DUPLICATE OBJECT FOUND"
|
|
|
|
|
break
|
|
|
|
|
fi
|
|
|
|
|
done &&
|
|
|
|
|
test -z "$found_duplicate_object"
|
|
|
|
|
'
|
|
|
|
|
|
2014-06-10 20:09:23 +00:00
|
|
|
test_expect_success 'writing bitmaps via command-line can duplicate .keep objects' '
|
repack: add `repack.packKeptObjects` config var
The git-repack command always passes `--honor-pack-keep`
to pack-objects. This has traditionally been a good thing,
as we do not want to duplicate those objects in a new pack,
and we are not going to delete the old pack.
However, when bitmaps are in use, it is important for a full
repack to include all reachable objects, even if they may be
duplicated in a .keep pack. Otherwise, we cannot generate
the bitmaps, as the on-disk format requires the set of
objects in the pack to be fully closed.
Even if the repository does not generally have .keep files,
a simultaneous push could cause a race condition in which a
.keep file exists at the moment of a repack. The repack may
try to include those objects in one of two situations:
1. The pushed .keep pack contains objects that were
already in the repository (e.g., blobs due to a revert of
an old commit).
2. Receive-pack updates the refs, making the objects
reachable, but before it removes the .keep file, the
repack runs.
In either case, we may prefer to duplicate some objects in
the new, full pack, and let the next repack (after the .keep
file is cleaned up) take care of removing them.
This patch introduces both a command-line and config option
to disable the `--honor-pack-keep` option. By default, it
is triggered when pack.writeBitmaps (or `--write-bitmap-index`
is turned on), but specifying it explicitly can override the
behavior (e.g., in cases where you prefer .keep files to
bitmaps, but only when they are present).
Note that this option just disables the pack-objects
behavior. We still leave packs with a .keep in place, as we
do not necessarily know that we have duplicated all of their
objects.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2014-03-03 20:04:20 +00:00
|
|
|
# build on $objsha1, $packsha1, and .keep state from previous
|
2014-06-10 20:08:38 +00:00
|
|
|
git repack -Adbl &&
|
repack: add `repack.packKeptObjects` config var
The git-repack command always passes `--honor-pack-keep`
to pack-objects. This has traditionally been a good thing,
as we do not want to duplicate those objects in a new pack,
and we are not going to delete the old pack.
However, when bitmaps are in use, it is important for a full
repack to include all reachable objects, even if they may be
duplicated in a .keep pack. Otherwise, we cannot generate
the bitmaps, as the on-disk format requires the set of
objects in the pack to be fully closed.
Even if the repository does not generally have .keep files,
a simultaneous push could cause a race condition in which a
.keep file exists at the moment of a repack. The repack may
try to include those objects in one of two situations:
1. The pushed .keep pack contains objects that were
already in the repository (e.g., blobs due to a revert of
an old commit).
2. Receive-pack updates the refs, making the objects
reachable, but before it removes the .keep file, the
repack runs.
In either case, we may prefer to duplicate some objects in
the new, full pack, and let the next repack (after the .keep
file is cleaned up) take care of removing them.
This patch introduces both a command-line and config option
to disable the `--honor-pack-keep` option. By default, it
is triggered when pack.writeBitmaps (or `--write-bitmap-index`
is turned on), but specifying it explicitly can override the
behavior (e.g., in cases where you prefer .keep files to
bitmaps, but only when they are present).
Note that this option just disables the pack-objects
behavior. We still leave packs with a .keep in place, as we
do not necessarily know that we have duplicated all of their
objects.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2014-03-03 20:04:20 +00:00
|
|
|
test_when_finished "found_duplicate_object=" &&
|
2019-11-27 19:53:49 +00:00
|
|
|
for p in .git/objects/pack/*.idx
|
|
|
|
|
do
|
repack: add `repack.packKeptObjects` config var
The git-repack command always passes `--honor-pack-keep`
to pack-objects. This has traditionally been a good thing,
as we do not want to duplicate those objects in a new pack,
and we are not going to delete the old pack.
However, when bitmaps are in use, it is important for a full
repack to include all reachable objects, even if they may be
duplicated in a .keep pack. Otherwise, we cannot generate
the bitmaps, as the on-disk format requires the set of
objects in the pack to be fully closed.
Even if the repository does not generally have .keep files,
a simultaneous push could cause a race condition in which a
.keep file exists at the moment of a repack. The repack may
try to include those objects in one of two situations:
1. The pushed .keep pack contains objects that were
already in the repository (e.g., blobs due to a revert of
an old commit).
2. Receive-pack updates the refs, making the objects
reachable, but before it removes the .keep file, the
repack runs.
In either case, we may prefer to duplicate some objects in
the new, full pack, and let the next repack (after the .keep
file is cleaned up) take care of removing them.
This patch introduces both a command-line and config option
to disable the `--honor-pack-keep` option. By default, it
is triggered when pack.writeBitmaps (or `--write-bitmap-index`
is turned on), but specifying it explicitly can override the
behavior (e.g., in cases where you prefer .keep files to
bitmaps, but only when they are present).
Note that this option just disables the pack-objects
behavior. We still leave packs with a .keep in place, as we
do not necessarily know that we have duplicated all of their
objects.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2014-03-03 20:04:20 +00:00
|
|
|
idx=$(basename $p)
|
|
|
|
|
test "pack-$packsha1.idx" = "$idx" && continue
|
2019-11-27 19:53:49 +00:00
|
|
|
if git verify-pack -v $p | egrep "^$objsha1"
|
|
|
|
|
then
|
repack: add `repack.packKeptObjects` config var
The git-repack command always passes `--honor-pack-keep`
to pack-objects. This has traditionally been a good thing,
as we do not want to duplicate those objects in a new pack,
and we are not going to delete the old pack.
However, when bitmaps are in use, it is important for a full
repack to include all reachable objects, even if they may be
duplicated in a .keep pack. Otherwise, we cannot generate
the bitmaps, as the on-disk format requires the set of
objects in the pack to be fully closed.
Even if the repository does not generally have .keep files,
a simultaneous push could cause a race condition in which a
.keep file exists at the moment of a repack. The repack may
try to include those objects in one of two situations:
1. The pushed .keep pack contains objects that were
already in the repository (e.g., blobs due to a revert of
an old commit).
2. Receive-pack updates the refs, making the objects
reachable, but before it removes the .keep file, the
repack runs.
In either case, we may prefer to duplicate some objects in
the new, full pack, and let the next repack (after the .keep
file is cleaned up) take care of removing them.
This patch introduces both a command-line and config option
to disable the `--honor-pack-keep` option. By default, it
is triggered when pack.writeBitmaps (or `--write-bitmap-index`
is turned on), but specifying it explicitly can override the
behavior (e.g., in cases where you prefer .keep files to
bitmaps, but only when they are present).
Note that this option just disables the pack-objects
behavior. We still leave packs with a .keep in place, as we
do not necessarily know that we have duplicated all of their
objects.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2014-03-03 20:04:20 +00:00
|
|
|
found_duplicate_object=1
|
|
|
|
|
echo "DUPLICATE OBJECT FOUND"
|
|
|
|
|
break
|
|
|
|
|
fi
|
|
|
|
|
done &&
|
|
|
|
|
test "$found_duplicate_object" = 1
|
|
|
|
|
'
|
|
|
|
|
|
2014-06-10 20:09:23 +00:00
|
|
|
test_expect_success 'writing bitmaps via config can duplicate .keep objects' '
|
|
|
|
|
# build on $objsha1, $packsha1, and .keep state from previous
|
2014-06-10 20:20:30 +00:00
|
|
|
git -c repack.writebitmaps=true repack -Adl &&
|
repack: add `repack.packKeptObjects` config var
The git-repack command always passes `--honor-pack-keep`
to pack-objects. This has traditionally been a good thing,
as we do not want to duplicate those objects in a new pack,
and we are not going to delete the old pack.
However, when bitmaps are in use, it is important for a full
repack to include all reachable objects, even if they may be
duplicated in a .keep pack. Otherwise, we cannot generate
the bitmaps, as the on-disk format requires the set of
objects in the pack to be fully closed.
Even if the repository does not generally have .keep files,
a simultaneous push could cause a race condition in which a
.keep file exists at the moment of a repack. The repack may
try to include those objects in one of two situations:
1. The pushed .keep pack contains objects that were
already in the repository (e.g., blobs due to a revert of
an old commit).
2. Receive-pack updates the refs, making the objects
reachable, but before it removes the .keep file, the
repack runs.
In either case, we may prefer to duplicate some objects in
the new, full pack, and let the next repack (after the .keep
file is cleaned up) take care of removing them.
This patch introduces both a command-line and config option
to disable the `--honor-pack-keep` option. By default, it
is triggered when pack.writeBitmaps (or `--write-bitmap-index`
is turned on), but specifying it explicitly can override the
behavior (e.g., in cases where you prefer .keep files to
bitmaps, but only when they are present).
Note that this option just disables the pack-objects
behavior. We still leave packs with a .keep in place, as we
do not necessarily know that we have duplicated all of their
objects.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2014-03-03 20:04:20 +00:00
|
|
|
test_when_finished "found_duplicate_object=" &&
|
2019-11-27 19:53:49 +00:00
|
|
|
for p in .git/objects/pack/*.idx
|
|
|
|
|
do
|
repack: add `repack.packKeptObjects` config var
The git-repack command always passes `--honor-pack-keep`
to pack-objects. This has traditionally been a good thing,
as we do not want to duplicate those objects in a new pack,
and we are not going to delete the old pack.
However, when bitmaps are in use, it is important for a full
repack to include all reachable objects, even if they may be
duplicated in a .keep pack. Otherwise, we cannot generate
the bitmaps, as the on-disk format requires the set of
objects in the pack to be fully closed.
Even if the repository does not generally have .keep files,
a simultaneous push could cause a race condition in which a
.keep file exists at the moment of a repack. The repack may
try to include those objects in one of two situations:
1. The pushed .keep pack contains objects that were
already in the repository (e.g., blobs due to a revert of
an old commit).
2. Receive-pack updates the refs, making the objects
reachable, but before it removes the .keep file, the
repack runs.
In either case, we may prefer to duplicate some objects in
the new, full pack, and let the next repack (after the .keep
file is cleaned up) take care of removing them.
This patch introduces both a command-line and config option
to disable the `--honor-pack-keep` option. By default, it
is triggered when pack.writeBitmaps (or `--write-bitmap-index`
is turned on), but specifying it explicitly can override the
behavior (e.g., in cases where you prefer .keep files to
bitmaps, but only when they are present).
Note that this option just disables the pack-objects
behavior. We still leave packs with a .keep in place, as we
do not necessarily know that we have duplicated all of their
objects.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2014-03-03 20:04:20 +00:00
|
|
|
idx=$(basename $p)
|
|
|
|
|
test "pack-$packsha1.idx" = "$idx" && continue
|
2019-11-27 19:53:49 +00:00
|
|
|
if git verify-pack -v $p | egrep "^$objsha1"
|
|
|
|
|
then
|
repack: add `repack.packKeptObjects` config var
The git-repack command always passes `--honor-pack-keep`
to pack-objects. This has traditionally been a good thing,
as we do not want to duplicate those objects in a new pack,
and we are not going to delete the old pack.
However, when bitmaps are in use, it is important for a full
repack to include all reachable objects, even if they may be
duplicated in a .keep pack. Otherwise, we cannot generate
the bitmaps, as the on-disk format requires the set of
objects in the pack to be fully closed.
Even if the repository does not generally have .keep files,
a simultaneous push could cause a race condition in which a
.keep file exists at the moment of a repack. The repack may
try to include those objects in one of two situations:
1. The pushed .keep pack contains objects that were
already in the repository (e.g., blobs due to a revert of
an old commit).
2. Receive-pack updates the refs, making the objects
reachable, but before it removes the .keep file, the
repack runs.
In either case, we may prefer to duplicate some objects in
the new, full pack, and let the next repack (after the .keep
file is cleaned up) take care of removing them.
This patch introduces both a command-line and config option
to disable the `--honor-pack-keep` option. By default, it
is triggered when pack.writeBitmaps (or `--write-bitmap-index`
is turned on), but specifying it explicitly can override the
behavior (e.g., in cases where you prefer .keep files to
bitmaps, but only when they are present).
Note that this option just disables the pack-objects
behavior. We still leave packs with a .keep in place, as we
do not necessarily know that we have duplicated all of their
objects.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2014-03-03 20:04:20 +00:00
|
|
|
found_duplicate_object=1
|
|
|
|
|
echo "DUPLICATE OBJECT FOUND"
|
|
|
|
|
break
|
|
|
|
|
fi
|
|
|
|
|
done &&
|
|
|
|
|
test "$found_duplicate_object" = 1
|
|
|
|
|
'
|
|
|
|
|
|
2008-11-10 05:59:58 +00:00
|
|
|
test_expect_success 'loose objects in alternate ODB are not repacked' '
|
2008-11-10 05:59:56 +00:00
|
|
|
mkdir alt_objects &&
|
2019-11-27 19:53:47 +00:00
|
|
|
echo $(pwd)/alt_objects >.git/objects/info/alternates &&
|
|
|
|
|
echo content3 >file3 &&
|
2008-11-10 05:59:56 +00:00
|
|
|
objsha1=$(GIT_OBJECT_DIRECTORY=alt_objects git hash-object -w file3) &&
|
|
|
|
|
git add file3 &&
|
2010-04-14 22:09:57 +00:00
|
|
|
test_tick &&
|
2008-11-10 05:59:56 +00:00
|
|
|
git commit -m commit_file3 &&
|
|
|
|
|
git repack -a -d -l &&
|
|
|
|
|
git prune-packed &&
|
2019-11-27 19:53:49 +00:00
|
|
|
for p in .git/objects/pack/*.idx
|
|
|
|
|
do
|
|
|
|
|
if git verify-pack -v $p | egrep "^$objsha1"
|
|
|
|
|
then
|
2008-11-10 05:59:56 +00:00
|
|
|
found_duplicate_object=1
|
|
|
|
|
echo "DUPLICATE OBJECT FOUND"
|
|
|
|
|
break
|
|
|
|
|
fi
|
|
|
|
|
done &&
|
|
|
|
|
test -z "$found_duplicate_object"
|
|
|
|
|
'
|
|
|
|
|
|
2008-11-13 00:50:26 +00:00
|
|
|
test_expect_success 'packed obs in alt ODB are repacked even when local repo is packless' '
|
2010-10-31 07:30:58 +00:00
|
|
|
mkdir alt_objects/pack &&
|
2008-11-13 00:50:26 +00:00
|
|
|
mv .git/objects/pack/* alt_objects/pack &&
|
|
|
|
|
git repack -a &&
|
|
|
|
|
myidx=$(ls -1 .git/objects/pack/*.idx) &&
|
|
|
|
|
test -f "$myidx" &&
|
2019-11-27 19:53:49 +00:00
|
|
|
for p in alt_objects/pack/*.idx
|
|
|
|
|
do
|
2008-11-13 00:50:26 +00:00
|
|
|
git verify-pack -v $p | sed -n -e "/^[0-9a-f]\{40\}/p"
|
2019-11-27 19:53:49 +00:00
|
|
|
done | while read sha1 rest
|
|
|
|
|
do
|
|
|
|
|
if ! ( git verify-pack -v $myidx | grep "^$sha1" )
|
|
|
|
|
then
|
2008-11-13 00:50:26 +00:00
|
|
|
echo "Missing object in local pack: $sha1"
|
|
|
|
|
return 1
|
|
|
|
|
fi
|
|
|
|
|
done
|
|
|
|
|
'
|
|
|
|
|
|
2009-04-24 23:18:53 +00:00
|
|
|
test_expect_success 'packed obs in alt ODB are repacked when local repo has packs' '
|
t7700: demonstrate misbehavior of 'repack -a' when local packs exist
The ability to "...fatten [the] local repository by packing everything that
is needed by the local ref into a single new pack, including things that are
borrowed from alternates"[1] is supposed to be provided by the '-a' or '-A'
options to repack when '-l' is not used, but there is a flaw. For each
pack in the local repository without a .keep file, repack supplies a
--unpacked=<pack> argument to pack-objects.
The --unpacked option to pack-objects, with or without an argument, causes
pack-objects to ignore any object which is packed in a pack not mentioned
in an argument to --unpacked=. So, if there are local packs, and
'repack -a' is called, then any objects which reside in packs accessible
through alternates will _not_ be packed. If there are no local packs, then
no --unpacked argument will be supplied, and repack will behave as expected.
[1] http://mid.gmane.org/7v8wrwidi3.fsf@gitster.siamese.dyndns.org
Signed-off-by: Brandon Casey <casey@nrlssc.navy.mil>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2009-01-09 22:14:39 +00:00
|
|
|
rm -f .git/objects/pack/* &&
|
2019-11-27 19:53:47 +00:00
|
|
|
echo new_content >>file1 &&
|
t7700: demonstrate misbehavior of 'repack -a' when local packs exist
The ability to "...fatten [the] local repository by packing everything that
is needed by the local ref into a single new pack, including things that are
borrowed from alternates"[1] is supposed to be provided by the '-a' or '-A'
options to repack when '-l' is not used, but there is a flaw. For each
pack in the local repository without a .keep file, repack supplies a
--unpacked=<pack> argument to pack-objects.
The --unpacked option to pack-objects, with or without an argument, causes
pack-objects to ignore any object which is packed in a pack not mentioned
in an argument to --unpacked=. So, if there are local packs, and
'repack -a' is called, then any objects which reside in packs accessible
through alternates will _not_ be packed. If there are no local packs, then
no --unpacked argument will be supplied, and repack will behave as expected.
[1] http://mid.gmane.org/7v8wrwidi3.fsf@gitster.siamese.dyndns.org
Signed-off-by: Brandon Casey <casey@nrlssc.navy.mil>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2009-01-09 22:14:39 +00:00
|
|
|
git add file1 &&
|
2010-04-14 22:09:57 +00:00
|
|
|
test_tick &&
|
t7700: demonstrate misbehavior of 'repack -a' when local packs exist
The ability to "...fatten [the] local repository by packing everything that
is needed by the local ref into a single new pack, including things that are
borrowed from alternates"[1] is supposed to be provided by the '-a' or '-A'
options to repack when '-l' is not used, but there is a flaw. For each
pack in the local repository without a .keep file, repack supplies a
--unpacked=<pack> argument to pack-objects.
The --unpacked option to pack-objects, with or without an argument, causes
pack-objects to ignore any object which is packed in a pack not mentioned
in an argument to --unpacked=. So, if there are local packs, and
'repack -a' is called, then any objects which reside in packs accessible
through alternates will _not_ be packed. If there are no local packs, then
no --unpacked argument will be supplied, and repack will behave as expected.
[1] http://mid.gmane.org/7v8wrwidi3.fsf@gitster.siamese.dyndns.org
Signed-off-by: Brandon Casey <casey@nrlssc.navy.mil>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2009-01-09 22:14:39 +00:00
|
|
|
git commit -m more_content &&
|
|
|
|
|
git repack &&
|
|
|
|
|
git repack -a -d &&
|
|
|
|
|
myidx=$(ls -1 .git/objects/pack/*.idx) &&
|
|
|
|
|
test -f "$myidx" &&
|
2019-11-27 19:53:49 +00:00
|
|
|
for p in alt_objects/pack/*.idx
|
|
|
|
|
do
|
t7700: demonstrate misbehavior of 'repack -a' when local packs exist
The ability to "...fatten [the] local repository by packing everything that
is needed by the local ref into a single new pack, including things that are
borrowed from alternates"[1] is supposed to be provided by the '-a' or '-A'
options to repack when '-l' is not used, but there is a flaw. For each
pack in the local repository without a .keep file, repack supplies a
--unpacked=<pack> argument to pack-objects.
The --unpacked option to pack-objects, with or without an argument, causes
pack-objects to ignore any object which is packed in a pack not mentioned
in an argument to --unpacked=. So, if there are local packs, and
'repack -a' is called, then any objects which reside in packs accessible
through alternates will _not_ be packed. If there are no local packs, then
no --unpacked argument will be supplied, and repack will behave as expected.
[1] http://mid.gmane.org/7v8wrwidi3.fsf@gitster.siamese.dyndns.org
Signed-off-by: Brandon Casey <casey@nrlssc.navy.mil>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2009-01-09 22:14:39 +00:00
|
|
|
git verify-pack -v $p | sed -n -e "/^[0-9a-f]\{40\}/p"
|
2019-11-27 19:53:49 +00:00
|
|
|
done | while read sha1 rest
|
|
|
|
|
do
|
|
|
|
|
if ! ( git verify-pack -v $myidx | grep "^$sha1" )
|
|
|
|
|
then
|
t7700: demonstrate misbehavior of 'repack -a' when local packs exist
The ability to "...fatten [the] local repository by packing everything that
is needed by the local ref into a single new pack, including things that are
borrowed from alternates"[1] is supposed to be provided by the '-a' or '-A'
options to repack when '-l' is not used, but there is a flaw. For each
pack in the local repository without a .keep file, repack supplies a
--unpacked=<pack> argument to pack-objects.
The --unpacked option to pack-objects, with or without an argument, causes
pack-objects to ignore any object which is packed in a pack not mentioned
in an argument to --unpacked=. So, if there are local packs, and
'repack -a' is called, then any objects which reside in packs accessible
through alternates will _not_ be packed. If there are no local packs, then
no --unpacked argument will be supplied, and repack will behave as expected.
[1] http://mid.gmane.org/7v8wrwidi3.fsf@gitster.siamese.dyndns.org
Signed-off-by: Brandon Casey <casey@nrlssc.navy.mil>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2009-01-09 22:14:39 +00:00
|
|
|
echo "Missing object in local pack: $sha1"
|
|
|
|
|
return 1
|
|
|
|
|
fi
|
|
|
|
|
done
|
|
|
|
|
'
|
|
|
|
|
|
2009-03-20 03:47:51 +00:00
|
|
|
test_expect_success 'packed obs in alternate ODB kept pack are repacked' '
|
2009-03-20 03:47:50 +00:00
|
|
|
# swap the .keep so the commit object is in the pack with .keep
|
|
|
|
|
for p in alt_objects/pack/*.pack
|
|
|
|
|
do
|
2010-10-31 07:30:58 +00:00
|
|
|
base_name=$(basename $p .pack) &&
|
2009-03-20 03:47:50 +00:00
|
|
|
if test -f alt_objects/pack/$base_name.keep
|
|
|
|
|
then
|
|
|
|
|
rm alt_objects/pack/$base_name.keep
|
|
|
|
|
else
|
|
|
|
|
touch alt_objects/pack/$base_name.keep
|
|
|
|
|
fi
|
2010-10-31 07:30:58 +00:00
|
|
|
done &&
|
2009-03-20 03:47:50 +00:00
|
|
|
git repack -a -d &&
|
|
|
|
|
myidx=$(ls -1 .git/objects/pack/*.idx) &&
|
|
|
|
|
test -f "$myidx" &&
|
2019-11-27 19:53:49 +00:00
|
|
|
for p in alt_objects/pack/*.idx
|
|
|
|
|
do
|
2009-03-20 03:47:50 +00:00
|
|
|
git verify-pack -v $p | sed -n -e "/^[0-9a-f]\{40\}/p"
|
2019-11-27 19:53:49 +00:00
|
|
|
done | while read sha1 rest
|
|
|
|
|
do
|
|
|
|
|
if ! ( git verify-pack -v $myidx | grep "^$sha1" )
|
|
|
|
|
then
|
2009-03-20 03:47:50 +00:00
|
|
|
echo "Missing object in local pack: $sha1"
|
|
|
|
|
return 1
|
|
|
|
|
fi
|
|
|
|
|
done
|
|
|
|
|
'
|
|
|
|
|
|
2009-03-20 03:47:52 +00:00
|
|
|
test_expect_success 'packed unreachable obs in alternate ODB are not loosened' '
|
2009-03-20 03:47:50 +00:00
|
|
|
rm -f alt_objects/pack/*.keep &&
|
|
|
|
|
mv .git/objects/pack/* alt_objects/pack/ &&
|
|
|
|
|
csha1=$(git rev-parse HEAD^{commit}) &&
|
|
|
|
|
git reset --hard HEAD^ &&
|
2010-04-14 22:09:57 +00:00
|
|
|
test_tick &&
|
|
|
|
|
git reflog expire --expire=$test_tick --expire-unreachable=$test_tick --all &&
|
2009-03-20 03:47:50 +00:00
|
|
|
# The pack-objects call on the next line is equivalent to
|
|
|
|
|
# git repack -A -d without the call to prune-packed
|
|
|
|
|
git pack-objects --honor-pack-keep --non-empty --all --reflog \
|
|
|
|
|
--unpack-unreachable </dev/null pack &&
|
|
|
|
|
rm -f .git/objects/pack/* &&
|
|
|
|
|
mv pack-* .git/objects/pack/ &&
|
|
|
|
|
test 0 = $(git verify-pack -v -- .git/objects/pack/*.idx |
|
|
|
|
|
egrep "^$csha1 " | sort | uniq | wc -l) &&
|
2019-11-27 19:53:47 +00:00
|
|
|
echo >.git/objects/info/alternates &&
|
2009-03-20 03:47:50 +00:00
|
|
|
test_must_fail git show $csha1
|
|
|
|
|
'
|
|
|
|
|
|
2009-03-21 22:26:11 +00:00
|
|
|
test_expect_success 'local packed unreachable obs that exist in alternate ODB are not loosened' '
|
2019-11-27 19:53:47 +00:00
|
|
|
echo $(pwd)/alt_objects >.git/objects/info/alternates &&
|
2009-03-21 22:25:30 +00:00
|
|
|
echo "$csha1" | git pack-objects --non-empty --all --reflog pack &&
|
|
|
|
|
rm -f .git/objects/pack/* &&
|
|
|
|
|
mv pack-* .git/objects/pack/ &&
|
|
|
|
|
# The pack-objects call on the next line is equivalent to
|
|
|
|
|
# git repack -A -d without the call to prune-packed
|
|
|
|
|
git pack-objects --honor-pack-keep --non-empty --all --reflog \
|
|
|
|
|
--unpack-unreachable </dev/null pack &&
|
|
|
|
|
rm -f .git/objects/pack/* &&
|
|
|
|
|
mv pack-* .git/objects/pack/ &&
|
|
|
|
|
test 0 = $(git verify-pack -v -- .git/objects/pack/*.idx |
|
|
|
|
|
egrep "^$csha1 " | sort | uniq | wc -l) &&
|
2019-11-27 19:53:47 +00:00
|
|
|
echo >.git/objects/info/alternates &&
|
2009-03-21 22:25:30 +00:00
|
|
|
test_must_fail git show $csha1
|
|
|
|
|
'
|
|
|
|
|
|
2009-07-23 15:33:49 +00:00
|
|
|
test_expect_success 'objects made unreachable by grafts only are kept' '
|
2009-07-23 15:33:45 +00:00
|
|
|
test_tick &&
|
|
|
|
|
git commit --allow-empty -m "commit 4" &&
|
|
|
|
|
H0=$(git rev-parse HEAD) &&
|
|
|
|
|
H1=$(git rev-parse HEAD^) &&
|
|
|
|
|
H2=$(git rev-parse HEAD^^) &&
|
2019-11-27 19:53:47 +00:00
|
|
|
echo "$H0 $H2" >.git/info/grafts &&
|
2010-04-14 22:09:57 +00:00
|
|
|
git reflog expire --expire=$test_tick --expire-unreachable=$test_tick --all &&
|
2009-07-23 15:33:45 +00:00
|
|
|
git repack -a -d &&
|
|
|
|
|
git cat-file -t $H1
|
2018-04-15 15:36:12 +00:00
|
|
|
'
|
2009-07-23 15:33:45 +00:00
|
|
|
|
2018-04-15 15:36:13 +00:00
|
|
|
test_expect_success 'repack --keep-pack' '
|
|
|
|
|
test_create_repo keep-pack &&
|
|
|
|
|
(
|
|
|
|
|
cd keep-pack &&
|
|
|
|
|
P1=$(commit_and_pack 1) &&
|
|
|
|
|
P2=$(commit_and_pack 2) &&
|
|
|
|
|
P3=$(commit_and_pack 3) &&
|
|
|
|
|
P4=$(commit_and_pack 4) &&
|
|
|
|
|
ls .git/objects/pack/*.pack >old-counts &&
|
|
|
|
|
test_line_count = 4 old-counts &&
|
|
|
|
|
git repack -a -d --keep-pack $P1 --keep-pack $P4 &&
|
|
|
|
|
ls .git/objects/pack/*.pack >new-counts &&
|
|
|
|
|
grep -q $P1 new-counts &&
|
|
|
|
|
grep -q $P4 new-counts &&
|
|
|
|
|
test_line_count = 3 new-counts &&
|
|
|
|
|
git fsck
|
|
|
|
|
)
|
|
|
|
|
'
|
|
|
|
|
|
2019-03-14 09:12:54 +00:00
|
|
|
test_expect_success 'bitmaps are created by default in bare repos' '
|
|
|
|
|
git clone --bare .git bare.git &&
|
|
|
|
|
git -C bare.git repack -ad &&
|
|
|
|
|
bitmap=$(ls bare.git/objects/pack/*.bitmap) &&
|
|
|
|
|
test_path_is_file "$bitmap"
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'incremental repack does not complain' '
|
|
|
|
|
git -C bare.git repack -q 2>repack.err &&
|
|
|
|
|
test_must_be_empty repack.err
|
|
|
|
|
'
|
2008-11-12 17:59:02 +00:00
|
|
|
|
2019-03-14 09:12:54 +00:00
|
|
|
test_expect_success 'bitmaps can be disabled on bare repos' '
|
|
|
|
|
git -c repack.writeBitmaps=false -C bare.git repack -ad &&
|
2019-11-27 19:53:45 +00:00
|
|
|
bitmap=$(ls bare.git/objects/pack/*.bitmap || :) &&
|
2019-03-14 09:12:54 +00:00
|
|
|
test -z "$bitmap"
|
|
|
|
|
'
|
|
|
|
|
|
2019-06-29 19:13:59 +00:00
|
|
|
test_expect_success 'no bitmaps created if .keep files present' '
|
|
|
|
|
pack=$(ls bare.git/objects/pack/*.pack) &&
|
|
|
|
|
test_path_is_file "$pack" &&
|
|
|
|
|
keep=${pack%.pack}.keep &&
|
2019-07-31 05:37:36 +00:00
|
|
|
test_when_finished "rm -f \"\$keep\"" &&
|
2019-06-29 19:13:59 +00:00
|
|
|
>"$keep" &&
|
2019-07-31 05:40:56 +00:00
|
|
|
git -C bare.git repack -ad 2>stderr &&
|
|
|
|
|
test_must_be_empty stderr &&
|
2019-06-29 19:13:59 +00:00
|
|
|
find bare.git/objects/pack/ -type f -name "*.bitmap" >actual &&
|
|
|
|
|
test_must_be_empty actual
|
|
|
|
|
'
|
|
|
|
|
|
2019-07-31 05:39:27 +00:00
|
|
|
test_expect_success 'auto-bitmaps do not complain if unavailable' '
|
|
|
|
|
test_config -C bare.git pack.packSizeLimit 1M &&
|
|
|
|
|
blob=$(test-tool genrandom big $((1024*1024)) |
|
|
|
|
|
git -C bare.git hash-object -w --stdin) &&
|
|
|
|
|
git -C bare.git update-ref refs/tags/big $blob &&
|
|
|
|
|
git -C bare.git repack -ad 2>stderr &&
|
|
|
|
|
test_must_be_empty stderr &&
|
|
|
|
|
find bare.git/objects/pack -type f -name "*.bitmap" >actual &&
|
|
|
|
|
test_must_be_empty actual
|
|
|
|
|
'
|
|
|
|
|
|
2019-03-14 09:12:54 +00:00
|
|
|
test_done
|
