Hi!
> > > I think it would be a good idea to use the script at [1] to update all
> > > the Go team repos, after it's updated to account for the
> > > "%{project_path}" variable, as well as replacing
> > > "github.com/xanzy/go-gitlab" with its new import path.
> > >
> > > It also needs to be update
Hi
Regarding golang-github-jackc-pgx
https://tracker.debian.org/pkg/golang-github-jackc-pgx
it seems stuck at v4 which has some open security bugs (although they
are resolved in v4.18.2).
I also noticed that trillian 1.7.0 started to use v5 as a build
dependency.
Do you have any thoughts on ho
Package: wnpp
Severity: wishlist
Owner: Simon Josefsson
* Package name: golang-github-jackc-pgerrcode
Version : 0.0~git20240316.6e2875d-1
Upstream Author : Jack Christensen
* URL : https://github.com/jackc/pgerrcode
* License : Expat
Programming Lang: Go
De
All,
I have uploaded a pair of CertStream-related projects: one self-hosted
server written in Go and a Python library and client tool.
What do they do? It allows you to watch the stream of newly minted
certificates published into various certificate transparency logs.
Please let me know if you
Hi,
> Does this mean that maintaining upstream Git history will be standard in
> the Go team?
Yes, it means that you can git blame on upstream code (outside of
debian/) and see what was introduced when, and you can run gbp switch
--force and git cherry-pick -x to backport fixes
from newer upstre
Package: wnpp
Severity: wishlist
Owner: Simon Josefsson
* Package name: certstream-server-go
Version : 1.7.0-1
Upstream Author : Rico
* URL : https://github.com/d-Rickyy-b/certstream-server-go
* License : Expat
Programming Lang: Go
Description : aggrega
Hi Otto,
On Sun, 2025-01-05 at 14:08 -0800, Otto Kekäläinen wrote:
> > I think it would be a good idea to use the script at [1] to update all
> > the Go team repos, after it's updated to account for the
> > "%{project_path}" variable, as well as replacing
> > "github.com/xanzy/go-gitlab" with its
