Use of 'debian/latest' in Go team as the default branch name

2025-01-23 Thread Otto Kekäläinen
Hi! Michael Stapelberg proposed in 2017 that the Go team should use 'debian/sid' as the default branch, in effort to unify with DEP-14 at the time (https://go-team.pages.debian.net/workflow-changes.html#_new_workflow_3). Turns out using 'sid' as the git HEAD wasn't a good idea, as it may lead to

Static-Built-Using (Re: Lintian warnings on unknown field)

2025-01-23 Thread Otto Kekäläinen
Hi, > I know we are using Static-Built-Using similar to the Rust Team to track > build dependencies of libraries, but it doesn't seem to be known to > lintian. Is there a proposal to add this and eliminate the warning? > > In the mean time, it is worth it to add an override to hide it? > > Even if

Bug#1093901: ITP: golang-github-google-go-tdx-guest -- wrap /dev/tdx-guest and attestation verification

2025-01-23 Thread Simon Josefsson
Package: wnpp Severity: wishlist Owner: Simon Josefsson * Package name: golang-github-google-go-tdx-guest Version : 0.3.1-1 Upstream Author : Google * URL : https://github.com/google/go-tdx-guest * License : Apache-2.0 Programming Lang: Go Description :

RFS: nwg-look

2025-01-23 Thread Maytham Alsudany
Hi Go team, I need DM access to nwg-look in order to upload a fix for #1079173. It is ready for upload at the repo[1]. Thanks, -- Maytham Alsudany Debian Maintainer [1]: https://salsa.debian.org/go-team/packages/nwg-look signature.asc Description: This is a digitally signed message part

Bug#1093838: ITP: golang-github-google-go-tpm-tools -- high-level library API for using TPMs

2025-01-23 Thread Simon Josefsson
Package: wnpp Severity: wishlist Owner: Simon Josefsson * Package name: golang-github-google-go-tpm-tools Version : 0.4.4-1 Upstream Author : Google * URL : https://github.com/google/go-tpm-tools * License : Apache-2.0 Programming Lang: Go Description :

Re: Lintian warnings on unknown field

2025-01-23 Thread Simon Josefsson
"Loren M. Lang" writes: > And a minor note, are overrides ever added for info-level lints like > spelling-error-in-binary? I usually leave info-level lintian complaints, but try to report typos upstream when I find which package a typo is coming from. Lintian errors or warnings is more problema

Bug#1093835: ITP: golang-github-google-go-configfs-tsm -- Trusted Security Module attestation reporting (library)

2025-01-23 Thread Simon Josefsson
Package: wnpp Severity: wishlist Owner: Simon Josefsson * Package name: golang-github-google-go-configfs-tsm Version : 0.3.2-1 Upstream Author : Google * URL : https://github.com/google/go-configfs-tsm * License : Apache-2.0 Programming Lang: Go Description

Lintian warnings on unknown field

2025-01-23 Thread Loren M. Lang
Hello Go Team, I know we are using Static-Built-Using similar to the Rust Team to track build dependencies of libraries, but it doesn't seem to be known to lintian. Is there a proposal to add this and eliminate the warning? In the mean time, it is worth it to add an override to hide it? Even if

Bug#1093833: ITP: golang-github-google-go-sev-guest -- attestation verification reporting via /dev/sev-guest

2025-01-23 Thread Simon Josefsson
Package: wnpp Severity: wishlist Owner: Simon Josefsson * Package name: golang-github-google-go-sev-guest Version : 0.12.1-1 Upstream Author : Google * URL : https://github.com/google/go-sev-guest * License : Apache-2.0 Programming Lang: Go Description

Bug#1093832: ITP: golang-github-google-logger -- Cross platform Go logging library.

2025-01-23 Thread Simon Josefsson
Package: wnpp Severity: wishlist Owner: Simon Josefsson * Package name: golang-github-google-logger Version : 1.1.1-1 Upstream Author : Google * URL : https://github.com/google/logger * License : Apache-2.0 Programming Lang: Go Description : Cross platf