Your message dated Mon, 3 Mar 2025 19:51:50 +0100
with message-id <[email protected]>
and subject line Re: Bug#1090796: golang-golang-x-tools-dev: please upload new 
upstream for txtar.FS API
has caused the Debian Bug report #1090796,
regarding golang-golang-x-tools-dev: please upload new upstream for txtar.FS API
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1090796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1090796
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: golang-golang-x-tools-dev

Hi!  I'm working on golang-github-cue-lang-cue which uses the txtar.FS
API coming from golang-golang-x-tools-dev, however it doesn't exist in
the Debian v0.23.0 release but was added later in upstream:

commit 2fb3ebe9d9a972bcf38aeff7413d9ddaae97193a
Author: Tim King <[email protected]>
Date:   Tue Jul 16 15:53:06 2024 -0700

    txtar: implement fs.FS

How about a new upstream upload?  Any reason to hold back on this?  I
may look into this eventually too.

/Simon

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
Version: 1:0.25.0+ds-1

Hi!

On Thu, 2024-12-19 at 12:25:32 +0100, Simon Josefsson wrote:
> Package: golang-golang-x-tools-dev

> Hi!  I'm working on golang-github-cue-lang-cue which uses the txtar.FS
> API coming from golang-golang-x-tools-dev, however it doesn't exist in
> the Debian v0.23.0 release but was added later in upstream:
> 
> commit 2fb3ebe9d9a972bcf38aeff7413d9ddaae97193a
> Author: Tim King <[email protected]>
> Date:   Tue Jul 16 15:53:06 2024 -0700
> 
>     txtar: implement fs.FS
> 
> How about a new upstream upload?  Any reason to hold back on this?  I
> may look into this eventually too.

This was fixed with the just uploaded release, but we missed adding the
bug closure (which I've now done retroactively on the git repo). This is
the relevant changelog entry:

 golang-golang-x-tools (1:0.25.0+ds-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Nicolas Peugnet ]
   * New upstream version. Closes: #1090796
   * Make gbp import-orig automatically link to upstream's tags.
   * internal/imports: adjust TestStdlibSelfImports pkg.
   * Enable GO111MODULE for some more tests.
   * Backport upstream patch to fix copylock tests with go1.24.
     Closes: #1082974
 .
   [ Guillem Jover ]
   * Switch to Standards-Version 4.7.2 (no changes needed).
   * Terminate make variable lists with an EOL comment.
   * Add debian/upstream/metadata file.
   * Sort fields in the same order as dh-make-golang produces them.
   * Update copyright years.

Thanks,
Guillem

--- End Message ---

Reply via email to