Log Message:
guile-git: Update to 0.5.2

Changelog from https://gitlab.com/guile-git/guile-git/-/releases

Changes in 0.5.2
Bug fix
    Fix crash when fetching multiple sub-modules
    This bug was reported at https://issues.guix.gnu.org/48855.  It
    could lead to crashes via SIGSEGV or SIGILL while fetching
    multiple sub-modules in a row.

Changes in 0.5.1
Bug fix
    Fix crash when using config-foreach or config-fold
    This bug was reported at https://issues.guix.gnu.org/47808.  It
    could lead to segmentation faults in tests/config.scm while
    running make check.

Changes in 0.5.0
New functionality
    New diff bindings in (git diff)
    These bindings allow you to compute and print a diff between two
    different trees.

    New configuration parsing support in (git config)
    This new module provides an interface to obtain configuration
    value as you would do on with the git config command.  As a
    corollary, it introduces an incompatible change: the internal
    module previously known as (git config) has been renamed to (git
    configuration).  It is not meant to be used directly by
    applications though, so you should not notice it.

    New tag procedures: ‘tag-fold’, ‘tag-foreach’

    New tree procedures: ‘tree-entry-byname’, ‘tree-entry-type’

    New remote procedures: ‘remote-url’, ‘remote-set-url!’

    Submodule interface changes
    The submodule-update procedure accepts the new #:allow-fetch? and
    #:fetch-options arguments.  The latter allows you to specify
    “fetch options”, such as the URL of an HTTP/HTTPS proxy.  There’s
    also a new submodule-set-url! procedure.

Bug fixes
    commit: Prevent dangling repository references
    Fix “make check” for tests involving SSH

Changes in 0.4.0
New Functionality
    Support for HTTP and HTTPS proxies
    One can now specify the HTTP and HTTPS via the #:proxy-url
    parameter of make-fetch-options.  Those fetch options must then be
    passed to fetch, or they can be added to the clone options passed
    to clone.

    Support for progress report
    Clones and fetches can take some time and you may want to tell
    users what’s going on.  To help with that, make-fetch-options now
    takes a #:transfer-progress option; it should be either #f or a
    one-argument procedure that will be called with an
    <indexer-progress> record every time progress is made.  This
    record contains information about the total number of objects
    being processed, the number of objects already retrieved, and the
    number of objects already indexed.

Bug Fixes
    Fix typo that made repository-index and repository-refdb unusable