[bug#70656] [PATCH python-team 0/4] Use git-minimal/pinned for some Python packages

[bug#70656] [PATCH python-team 0/4] Use git-minimal/pinned for some Python packages

[Christopher Baines]

[-- Attachment #1: Type: text/plain, Size: 507 bytes --]

This reduces the direct dependencies on git, making it easier to update.

Christopher Baines (4):
  gnu: python-gitpython: Use git-minimal/pinned.
  gnu: python-gitdb: Use git-minimal/pinned.
  gnu: python-pbr: Use git-minimal/pinned.
  gnu: python-versioneer: Use git-minimal/pinned.

 gnu/packages/python-xyz.scm      | 4 ++--
 gnu/packages/version-control.scm | 6 +++---
 2 files changed, 5 insertions(+), 5 deletions(-)


base-commit: 3bd8d238aba718bf949691d0e37fa310e2cfc12a
-- 
2.41.0

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

[bug#70656] [PATCH python-team 1/4] gnu: python-gitpython: Use git-minimal/pinned.

[Christopher Baines]

This helps reduce the dependencies on git, as I think it's find to build with
a slightly older git, at least during periods when git-minimal/pinned needs
updating.

* gnu/packages/version-control.scm (python-gitpython)[arguments,inputs]: Use
git-minimal/pinned.

Change-Id: Id4325fe58a62bafce58b74828fa5823621166c55
---
 gnu/packages/version-control.scm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gnu/packages/version-control.scm b/gnu/packages/version-control.scm
index 0c7c496c82..c340d5fdc8 100644
--- a/gnu/packages/version-control.scm
+++ b/gnu/packages/version-control.scm
@@ -1438,10 +1438,10 @@ (define-public python-gitpython
                       (substitute* "git/cmd.py"
                         (("git_exec_name = \"git\"")
                          (string-append "git_exec_name = \""
-                                        (assoc-ref inputs "git")
+                                        (assoc-ref inputs "git-minimal")
                                         "/bin/git\""))))))))
     (inputs
-     (list git))
+     (list git-minimal/pinned))
     (propagated-inputs
      (list python-gitdb python-typing-extensions))
     (native-inputs

base-commit: 3bd8d238aba718bf949691d0e37fa310e2cfc12a
-- 
2.41.0

[bug#70656] [PATCH python-team 2/4] gnu: python-gitdb: Use git-minimal/pinned.

[Christopher Baines]

This helps reduce the dependencies on git, as I think it's find to build with
a slightly older git, at least during periods when git-minimal/pinned needs
updating.

* gnu/packages/version-control.scm (python-gitdb)[native-inputs]: Use
git-minimal/pinned.

Change-Id: Ib9e65383d18a234567a36824ad3e08dc21eff200
---
 gnu/packages/version-control.scm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gnu/packages/version-control.scm b/gnu/packages/version-control.scm
index c340d5fdc8..c2ff4040fb 100644
--- a/gnu/packages/version-control.scm
+++ b/gnu/packages/version-control.scm
@@ -1409,7 +1409,7 @@ (define-public python-gitdb
     (propagated-inputs
      (list python-smmap))
     (native-inputs
-     (list git python-nose))
+     (list git-minimal/pinned python-nose))
     (home-page "https://github.com/gitpython-developers/gitdb")
     (synopsis "Python implementation of the Git object database")
     (description
-- 
2.41.0

[bug#70656] [PATCH python-team 3/4] gnu: python-pbr: Use git-minimal/pinned.

[Christopher Baines]

This helps reduce the dependencies on git, as I think it's find to build with
a slightly older git, at least during periods when git-minimal/pinned needs
updating.

* gnu/packages/version-control.scm (python-pbr)[propagated-inputs]: Use
git-minimal/pinned.

Change-Id: Ib90056a1a603e06a99b5c601f9fcba7375dc24ac
---
 gnu/packages/python-xyz.scm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gnu/packages/python-xyz.scm b/gnu/packages/python-xyz.scm
index f22b891ba5..16b47d0aa7 100644
--- a/gnu/packages/python-xyz.scm
+++ b/gnu/packages/python-xyz.scm
@@ -5128,7 +5128,7 @@ (define-public python-pbr
     (arguments
      `(#:tests? #f)) ;; Most tests seem to use the Internet.
     (propagated-inputs
-      (list git)) ;; pbr actually uses the "git" binary.
+      (list git-minimal/pinned)) ;; pbr actually uses the "git" binary.
     (native-inputs
       `(("python-fixtures" ,python-fixtures-bootstrap)
         ;; discover, coverage, hacking, subunit
-- 
2.41.0

[bug#70656] [PATCH python-team 4/4] gnu: python-versioneer: Use git-minimal/pinned.

[Christopher Baines]

This helps reduce the dependencies on git, as I think it's find to build with
a slightly older git, at least during periods when git-minimal/pinned needs
updating.

* gnu/packages/version-control.scm (python-versioneer)[propagated-inputs]: Use
git-minimal/pinned.

Change-Id: Id537baa8228afeb3b84161ecb5fea0d131b45442
---
 gnu/packages/python-xyz.scm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gnu/packages/python-xyz.scm b/gnu/packages/python-xyz.scm
index 16b47d0aa7..b5a2197a0a 100644
--- a/gnu/packages/python-xyz.scm
+++ b/gnu/packages/python-xyz.scm
@@ -31915,7 +31915,7 @@ (define-public python-versioneer
                 (invoke "pycodestyle" "--max-line-length=88"
                         "git_version.py" "versioneer.py")))))))
     (native-inputs
-     (list git python-flake8 python-pycodestyle python-pyflakes))
+     (list git-minimal/pinned python-flake8 python-pycodestyle python-pyflakes))
     (propagated-inputs
      (list python-tomli))
     (home-page "https://github.com/python-versioneer/python-versioneer")
-- 
2.41.0

[bug#70656] [PATCH python-team 3/4] gnu: python-pbr: Use git-minimal/pinned.

[Lars-Dominik Braun]

Hi,

> This helps reduce the dependencies on git, as I think it's find to build with
> a slightly older git, at least during periods when git-minimal/pinned needs
> updating.

this one is used on the repository cloned during build. As far as I see
we use git-minimal for cloning. Do we know whether the on-disk structures
of git are stable, i.e. can a clone of git version A be read by a git
version B with B < A?

Lars

[bug#70656] [PATCH python-team 3/4] gnu: python-pbr: Use git-minimal/pinned.

[Greg Hogan]

On Sat, May 4, 2024 at 4:14 AM Lars-Dominik Braun <lars@6xq.net> wrote:
>
> Hi,
>
> > This helps reduce the dependencies on git, as I think it's find to build with
> > a slightly older git, at least during periods when git-minimal/pinned needs
> > updating.
>
> this one is used on the repository cloned during build. As far as I see
> we use git-minimal for cloning. Do we know whether the on-disk structures
> of git are stable, i.e. can a clone of git version A be read by a git
> version B with B < A?

Why do we use git-minimal for cloning instead of git-minimal/pinned?