Groups > linux.debian.bugs.dist > #1234189

Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields

From	Sean Whitton <spwhitton@spwhitton.name>
Newsgroups	linux.debian.bugs.dist, linux.debian.policy
Subject	Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields
Date	2025-02-20 11:40 +0100
Message-ID	<Kic8h-AwM-1@gated-at.bofh.it> (permalink)
References	(4 earlier) <KibYC-AtA-27@gated-at.bofh.it> <K0czM-4OVR-13@gated-at.bofh.it> <KibYC-AtA-25@gated-at.bofh.it> <K0czM-4OVR-13@gated-at.bofh.it> <KibYC-AtA-25@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

Hello,

On Thu 20 Feb 2025 at 11:18am +01, Simon Josefsson wrote:

> Do consumers of this field have to handle both SHA1 and SHA256 git
> object ids?

I don't believe that this has to be specified in Policy.  There isn't
any ambiguity -- SHA1 and SHA256 checksums cannot be mistaken for each
other.  Whether they have to handle both just depends on what is in the
archive; at some point that will be all SHA1, then mixed, then all
SHA256, presumably.

> OpenPGP v5 or v6 fingerprint?

Here my knowledge is lacking.  Can they be unambiguously distinguished?

> How are they supposed to behave if they cannot understand parts of the
> information in the header?

Surely that would depend on what the tool was trying to achieve and
couldn't be specified in general?

-- 
Sean Whitton

Thread

Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields Ian Jackson <ijackson@chiark.greenend.org.uk> - 2025-02-20 10:40 +0100
  Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields Sean Whitton <spwhitton@spwhitton.name> - 2025-02-20 11:10 +0100
    Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields Sean Whitton <spwhitton@spwhitton.name> - 2025-03-05 02:50 +0100
  Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields Simon Josefsson <simon@josefsson.org> - 2025-02-20 11:30 +0100
    Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields Sean Whitton <spwhitton@spwhitton.name> - 2025-02-20 11:40 +0100
    Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields Guillem Jover <guillem@debian.org> - 2025-02-20 13:00 +0100
    Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields Ian Jackson <ijackson@chiark.greenend.org.uk> - 2025-02-20 17:20 +0100
  Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields Sam Hartman <hartmans@debian.org> - 2025-02-20 17:50 +0100
    Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields Sean Whitton <spwhitton@spwhitton.name> - 2025-02-21 04:10 +0100
      Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields Ian Jackson <ijackson@chiark.greenend.org.uk> - 2025-02-21 17:30 +0100
        Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields Sean Whitton <spwhitton@spwhitton.name> - 2025-02-22 02:30 +0100
      Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields Sam Hartman <hartmans@debian.org> - 2025-02-22 00:40 +0100
        Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields Sean Whitton <spwhitton@spwhitton.name> - 2025-02-22 02:10 +0100

csiph-web