largefiles: use 'default' instead of 'default-push' when pulling (issue3584) This only applies to downloading largefiles, and only when no source for the pull is explicitly provided. The repository itself was properly being pulled via 'default' previously. Using --all-largefiles is not necessary on a bare pull to test this (this existing test is merely a convenience), but it is required to test pulling on the rebase path. Note that the errors generated in the --rebase case are because the repo specified doesn't have the largefiles in its cache (though they are in the user cache), so the errors are misleading. Specifying --all-largefiles when cloning to 'b' fixes this, but instead of errors, it reports caching only 5 largefiles instead of the 9 that come up missing. Likely this is because the largefile download procedure tries to download missing files for each rev, and some of the files have standins in more than one rev that gets pulled.

     1

# Disable the $CAP wire protocol capability.

     2

     3

if test -z "$CAP"

     4

then

     5

    echo "CAP environment variable not set."

     6

fi

     7

     8

cat > notcapable-$CAP.py << EOF

     9

from mercurial import extensions, peer, localrepo

    10

def extsetup():

    11

    extensions.wrapfunction(peer.peerrepository, 'capable', wrapcapable)

    12

    extensions.wrapfunction(localrepo.localrepository, 'peer', wrappeer)

    13

def wrapcapable(orig, self, name, *args, **kwargs):

    14

    if name in '$CAP'.split(' '):

    15

        return False

    16

    return orig(self, name, *args, **kwargs)

    17

def wrappeer(orig, self):

    18

    # Since we're disabling some newer features, we need to make sure local

    19

    # repos add in the legacy features again.

    20

    return localrepo.locallegacypeer(self)

    21

EOF

    22

    23

echo '[extensions]' >> $HGRCPATH

    24

echo "notcapable-$CAP = `pwd`/notcapable-$CAP.py" >> $HGRCPATH