From noreply at release.debian.org Tue Nov 10 04:39:11 2026 From: noreply at release.debian.org (Debian testing watch) Date: Tue, 10 Nov 2026 04:39:11 +0000 Subject: [pkg-go] golang-github-backblaze-blazer REMOVED from testing Message-ID: FYI: The status of the golang-github-backblaze-blazer source package in Debian's testing distribution has changed. Previous version: 0.6.1-4 Current version: (not in testing) Hint: # 1148962 The script that generates this mail tries to extract removal reasons from comments in the britney hint files. Those comments were not originally meant to be machine readable, so if the reason for removing your package seems to be nonsense, it is probably the reporting script that got confused. Please check the actual hints file before you complain about meaningless removals. -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. From noreply at release.debian.org Tue Nov 10 04:39:12 2026 From: noreply at release.debian.org (Debian testing watch) Date: Tue, 10 Nov 2026 04:39:12 +0000 Subject: [pkg-go] golang-github-oklog-ulid 2.1.2-1 MIGRATED to testing Message-ID: FYI: The status of the golang-github-oklog-ulid source package in Debian's testing distribution has changed. Previous version: 2.0.2+ds-2 Current version: 2.1.2-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. From noreply at release.debian.org Tue Nov 10 04:39:18 2026 From: noreply at release.debian.org (Debian testing watch) Date: Tue, 10 Nov 2026 04:39:18 +0000 Subject: [pkg-go] restic REMOVED from testing Message-ID: FYI: The status of the restic source package in Debian's testing distribution has changed. Previous version: 0.19.1-1 Current version: (not in testing) Hint: # 1148962 in golang-github-backblaze-blazer The script that generates this mail tries to extract removal reasons from comments in the britney hint files. Those comments were not originally meant to be machine readable, so if the reason for removing your package seems to be nonsense, it is probably the reporting script that got confused. Please check the actual hints file before you complain about meaningless removals. -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. From noreply at release.debian.org Tue Nov 10 04:40:03 2026 From: noreply at release.debian.org (Debian testing autoremoval watch) Date: Tue, 10 Nov 2026 04:40:03 +0000 Subject: [pkg-go] acmetool is marked for autoremoval from testing Message-ID: acmetool 0.2.2-3 is marked for autoremoval from testing on 2026-12-15 It (build-)depends on packages with these RC bugs: 1152784: golang-gopkg-square-go-jose.v1: Don't include in forky https://bugs.debian.org/1152784 1152786: golang-gopkg-square-go-jose.v2: Don't include in forky https://bugs.debian.org/1152786 For more information on the autoremoval process, including hints to prevent autoremoval can be found on the wiki: https://wiki.debian.org/Autoremoval This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl From owner at bugs.debian.org Tue Nov 10 23:33:02 2026 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Tue, 10 Nov 2026 23:33:02 +0000 Subject: [pkg-go] Processed: Re: Bug#1148962: golang-defaults breaks golang-github-backblaze-blazer autopkgtest on ppc64el References: Message-ID: Processing control commands: > reassign -1 golang-defaults Bug #1148962 [src:golang-defaults, src:golang-github-backblaze-blazer] golang-defaults breaks golang-github-backblaze-blazer autopkgtest on ppc64el Bug reassigned from package 'src:golang-defaults, src:golang-github-backblaze-blazer' to 'golang-defaults'. No longer marked as found in versions golang-defaults/2:1.27~1 and golang-github-backblaze-blazer/0.6.1-4. Ignoring request to alter fixed versions of bug #1148962 to the same values previously set -- 1148962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1148962 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From zeha at debian.org Tue Nov 10 23:30:59 2026 From: zeha at debian.org (Chris Hofstaedtler) Date: Wed, 11 Nov 2026 00:30:59 +0100 Subject: [pkg-go] Bug#1148962: golang-defaults breaks golang-github-backblaze-blazer autopkgtest on ppc64el In-Reply-To: References: Message-ID: Control: reassign -1 golang-defaults On Fri, Sep 25, 2026 at 08:26:26PM +0200, Paul Gevers wrote: > Source: golang-defaults, golang-github-backblaze-blazer > Control: found -1 golang-defaults/2:1.27~1 > Control: found -1 golang-github-backblaze-blazer/0.6.1-4 > Severity: serious > Tags: sid forky > User: debian-ci at lists.debian.org > Usertags: breaks needs-update > > Dear maintainer(s), > > With a recent upload of golang-defaults the autopkgtest of > golang-github-backblaze-blazer fails in testing on ppc64el when that > autopkgtest is run with the binary packages of golang-defaults from > unstable. It passes when run with only packages from testing. In tabular > form: > > pass fail > golang-defaults from testing 2:1.27~1 > golang-github-backblaze-blazer from testing 0.6.1-4 > all others from testing from testing > > I copied some of the output at the bottom of this report. > > Currently this regression is blocking the migration of golang-defaults to > testing [1]. Due to the nature of this issue, I filed this bug report > against both packages. Can you please investigate the situation and reassign > the bug to the right package? > https://ci.debian.net/data/autopkgtest/testing/ppc64el/g/golang-github-backblaze-blazer/76037956/log.gz Seems likely that this could be https://github.com/golang/go/issues/81842