Your message dated Wed, 21 Jan 2026 17:49:14 +0000
with message-id <[email protected]>
and subject line Bug#1120588: fixed in libgit2 1.9.2+ds-4
has caused the Debian Bug report #1120588,
regarding src:libgit2: Please enable sha256 features (causes library transition)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1120588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1120588
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libgit2
Version: 1.9.1+ds-1
Severity: wishlist
Control: affects -1 + gitg

Please enable the "experimental sha256" feature, and produce a variant
of the library with it.  This means passing -DEXPERIMENTAL_SHA256=ON to
cmake.

As noted in the libgit2 README.md, this is an api-incompatible change,
which suggests it would need to be a library transition in debian.

There are a couple different ways it could be done in debian, including
some sort of library rename for the package when built with this
enabled, shipping both variants at once and letting dependencies choose
which one to build against, etc.

We could also use experimental to try this out, so that we can provide
feedback for any dependencies that might need to do a rebuild.

I recognize that this might be a big ask, but we are long overdue to get
the migration process rolling for the git ecosystem, and this kind of
work could help move it along.

If you have any suggestions about the way it should be done, i'm happy
to consider and review.

          --dkg

# Background:

Currently, gitg fails to recognize a git repository that uses sha256
object formats:


```
0 dkg@bob:/tmp/cdtemp.Ybpesp$ git init --object-format=sha256
Initialized empty Git repository in /tmp/cdtemp.Ybpesp/.git/
0 dkg@bob:/tmp/cdtemp.Ybpesp$ touch foo
0 dkg@bob:/tmp/cdtemp.Ybpesp$ git add foo
0 dkg@bob:/tmp/cdtemp.Ybpesp$ git commit -m 'added foo'
[main (root-commit) 2812c0d] added foo
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 foo
0 dkg@bob:/tmp/cdtemp.Ybpesp$ git log 
commit 2812c0d8244c651e025a0d0786dba9c9d5653842d51a72370d69da9084b80c1c (HEAD 
-> main)
Author: Daniel Kahn Gillmor <[email protected]>
Date:   Tue Nov 11 14:54:58 2025 -0500

    added foo
0 dkg@bob:/tmp/cdtemp.Ybpesp$ gitg
Error: not able to open repository “unknown object format 'sha256'”.
0 dkg@bob:/tmp/cdtemp.Ybpesp$ 
```

I mentioned this to gitg upstream at
https://gitlab.gnome.org/GNOME/gitg/-/issues/502 and they pointed me to
their libgit2 dependency.


-- System Information:
Debian Release: forky/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing'), (200, 
'unstable-debug'), (200, 'unstable'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.16.12+deb14+1-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
Source: libgit2
Source-Version: 1.9.2+ds-4
Done: Timo Röhling <[email protected]>

We believe that the bug you reported is fixed in the latest version of
libgit2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Timo Röhling <[email protected]> (supplier of updated libgit2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 21 Jan 2026 18:33:15 +0100
Source: libgit2
Architecture: source
Version: 1.9.2+ds-4
Distribution: unstable
Urgency: medium
Maintainer: Utkarsh Gupta <[email protected]>
Changed-By: Timo Röhling <[email protected]>
Closes: 1120588 1125517
Changes:
 libgit2 (1.9.2+ds-4) unstable; urgency=medium
 .
   * Switch to llhttp as HTTP parser backend (Closes: #1125517)
 .
 libgit2 (1.9.2+ds-3) experimental; urgency=medium
 .
   * Enable experimental SHA-256 support (Closes: #1120588)
   * Mark autopkgtest as superficial
Checksums-Sha1:
 fb26a6a0eb11cc2c3d1984c49e9507d289427b0b 2772 libgit2_1.9.2+ds-4.dsc
 305f978f55f8979c7a7f2714cb53f579cc0e70d9 18952 libgit2_1.9.2+ds-4.debian.tar.xz
Checksums-Sha256:
 e40579f3932b9eb2263127a5739dafcd3ff46c0b9792ee75a7b080a84472c4f7 2772 
libgit2_1.9.2+ds-4.dsc
 dda28bd5534479763f47973387724d8827aad05420c74e3ecd6da7cd2a536fc4 18952 
libgit2_1.9.2+ds-4.debian.tar.xz
Files:
 e7ac7b14475da1f1ff7cc00ab9a6d010 2772 libs optional libgit2_1.9.2+ds-4.dsc
 bd0d245956dd5f576f78c333b84f8f75 18952 libs optional 
libgit2_1.9.2+ds-4.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEmwPruYMA35fCsSO/zIxr3RQD9MoFAmlxD1gACgkQzIxr3RQD
9MqbLQ//ZVgICLjIXoR3xG8tusAzO8qPwxuPuBJd6OYryYoqHAjpqOxk6XFzgCxI
6w3zv+FfFUwnBy7ohiXvNtaq0cSVgagQ/jiySmhAQblRyXC8xUxjmvHTwHnRnoa0
YznF/0AhURf1JL9CERKP/ZG/4aBgiECVHRe5VijYeiSwKhRngLaeiNGPwQJcxXrk
Ic8DtxRlzPxA5f2Nyr4+TDlOb/QQXoYu2L0cCH+sBbrE73H33wfa+GTG0zqZas4j
yUJgjvA6jHHGE+gvL+VSr4esUv//5N/KY6khczVVEE36rlLTQq9TW7ASONlN10F3
w6ITbM22BDZIxPwtSCxuGWA7gqG1o5Pec3CIUMB9DLp0Yj+SC/PmsnRdbIBXIZvs
JvEilZgum5x5gnXbSu8j2PCxR4bzgb8Ba9WAKG3wNOe1Pb5w3d+b3cJXQtzOp21f
B9asQWE+ui1feUbz9jpKxR1Tt4WumkL21DGMLNChum+OcefTZLVODIOSDi06oAxd
z41LnaWKR7Uxl8J7qCnRgC7iRBHqqcqpbMxPuYWhrMlO6xdHKLmLL/KbTerdgkmI
B8FurVXRcy/RkQniJGjw2ONkIWc2r8pfXE/RxgF9A3+2vpSctzWd2lmKzwFklmkd
c0YpivxhgHqbGNsMH+Q9AtP62G7JMlxEPTlLkqyMiKPXAZtGwjU=
=mMVU
-----END PGP SIGNATURE-----

Attachment: pgpjxosT2QMXw.pgp
Description: PGP signature


--- End Message ---

Reply via email to