Re: Should we delete pkg-go-tools, provisioning, migrate-pkg-go-to-salsa etc?

El 12/5/25 a las 20:13, Otto Kekäläinen escribió: Having a bunch of outdated cruft adds unnecessary toil and distraction to people trying to maintain current packages, so cleaning away old stuff can help make current contributors more active. For example Santiago spent today time debugging the Go

Re: Salsa repository rename

El 11/1/25 a las 13:41, Taavi Väänänen escribió: Could someone with enough rights in Salsa please rename to golang-codeberg-emersion-go-scfg to match the new source package name? Done. Thanks.

Re: RFS: Security patch for GitHub CLI client gh

El 30/12/24 a las 19:24, Otto Kekäläinen escribió: You bypassed now both code reviews and uploaded despite failing CI. For the record: I only see failed pipelines here: https://salsa.debian.org/go-team/packages/gh/-/pipelines?page=1&scope=all so it's not as if this package suddenly had switch

Re: RFS: Security patch for GitHub CLI client gh

El 30/12/24 a las 19:24, Otto Kekäläinen escribió: I see you now tagged debian/2.46.0-2 and likely uploaded it. Yes, as a team upload. Why were you in such a hurry? Because CVE-2024-52308 seems grave enough for that, and fixing it in unstable is usually a prerequisite for a stable fix. W

Re: RFS: Security patch for GitHub CLI client gh

El 30/12/24 a las 12:52, Santiago Vila escribió: Hi. Please note that we should also find a fix for #1091585 because otherwise the package that we would upload would not propagate to testing. Hi. This is now done in gh_2.46.0-2. (I'll try to followup only to the relevant bug addresses

Re: RFS: Security patch for GitHub CLI client gh

Hi. Please note that we should also find a fix for #1091585 because otherwise the package that we would upload would not propagate to testing. Thanks.

Re: RFS: Security patch for GitHub CLI client gh

El 30/12/24 a las 11:08, Loren M. Lang escribió: I had meant to wait to upload the bookworm branch to the main go-team repo until it had undergone review and acceptance, but I had the wrong remote selected for the push. Hi. I'll try to handle your fixes with team uploads (not NMU) for bookworm

Re: Fixing tzdata bugs

Correction: The following packages build fine in unstable: golang-github-cli-go-gh golang-github-cli-go-gh-v2 So, nothing to fix in those two. Still have to check why they used to fail in trixie. Thanks.

Fixing tzdata bugs

Hello. There is a new debootstrap in trixie/sid which makes the tzdata bugs I started to report last year to be "factually RC", as they will now FTBFS in the riscv64 architecture, which is currently a release architecture. For details, see this message and the ones following them: https://bugs.

Re: Joining team

I found answers for some of my own questions: El 24/10/23 a las 1:33, Santiago Vila escribió: I guess autobuilders will not care at all, but I'm all for correctness. When creating a new branch for stable, the proper thing to do is to modify debian/gbp.conf like this, right? debian-b

Re: Joining team

El 24/10/23 a las 1:00, Nilesh Patra escribió: On Tue, Oct 24, 2023 at 12:52:18AM +0200, Santiago Vila wrote: I've just asked access to the Go team. I probably approved before you sent this email :) Thank you! :-) A minor question regarding the wormhole-william bug: I guess autobui

Joining team

Hello. I've just asked access to the Go team. I'd like to work on QA issues. Mainly FTBFS bugs, and mainly ensuring that fixes for those FTBFS bugs propagate to stable. As an example for the kind of thing I'd like to do, I would start by fixing this in stable: https://bugs.debian.org/cgi-bin/b

Re: Undeclared dependencies on tzdata

[ Adding 837...@bugs.debian.org and the submitter to Cc for the reasons explained below ]. El 22/11/22 a las 13:09, Guillem Jover escribió: So it seems to me we have a bunch of packages that are prio:required but not Essential (some have switched to Protected:yes), that should get their priori

Re: Undeclared dependencies on tzdata

El 21/11/22 a las 14:32, Shengjing Zhu escribió: On Mon, Nov 21, 2022 at 9:07 PM Santiago Vila wrote: Being "priority: required", being "essential: yes", and being build-essential are all three different things. My intent is to keep stable free from FTBFS bugs, i.e. p

Re: Undeclared dependencies on tzdata

El 21/11/22 a las 3:19, Shengjing Zhu escribió: On Mon, Nov 21, 2022 at 12:03:40AM +0100, Santiago Vila wrote: I've detected a bunch of Go packages which do not build from source because they use tzdata without a build-dependency. This will not happen if tzdata is installed by default