Your message dated Wed, 09 Aug 2023 09:19:34 +0000
with message-id <[email protected]>
and subject line Bug#1031351: fixed in golang-defaults 2:1.21~1
has caused the Debian Bug report #1031351,
regarding Make golang-any have determinate Depends
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.)


-- 
1031351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031351
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: golang-any
Severity: normal
X-Debbugs-Cc: [email protected]

While reply https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031330#22
I realize we have similar problem when building Go programs in experimental
and backports. The aspcud resolver for unknown reason that prefers gccgo-go
on arch where golang-go is available. That causes unexpected build failures,
especially annoying for backports.

While it's good to keep packages buildable with gccgo, the reality is only
golang-go is tested on sid. So we can't know the build failures in advance.

So we should remove the alternative Depends in golang-any, to have a determinate
result.

I think we previously use "golang-go | gccgo-go" because it's easies to
write debian/control file. Can we have different Depends for different arch?
Can we reduce the duplication of arch list with golang-go?

--- End Message ---
--- Begin Message ---
Source: golang-defaults
Source-Version: 2:1.21~1
Done: Shengjing Zhu <[email protected]>

We believe that the bug you reported is fixed in the latest version of
golang-defaults, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Shengjing Zhu <[email protected]> (supplier of updated golang-defaults package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Wed, 09 Aug 2023 16:45:21 +0800
Source: golang-defaults
Architecture: source
Version: 2:1.21~1
Distribution: experimental
Urgency: medium
Maintainer: Debian Go Compiler Team <[email protected]>
Changed-By: Shengjing Zhu <[email protected]>
Closes: 1031351
Changes:
 golang-defaults (2:1.21~1) experimental; urgency=medium
 .
   * Team upload
   * Make golang-any depends on determinate package (Closes: #1031351)
   * Update to Go 1.21 (src:golang-1.21)
Checksums-Sha1:
 246357c66f7c18b5e286941db410e9978871800c 1708 golang-defaults_1.21~1.dsc
 87bd5a9fd68e584163443e144c61604a42716fe4 30896 golang-defaults_1.21~1.tar.xz
 b71f4da597cd51aa19f2d5b88e9ede8f90dc8502 6450 
golang-defaults_1.21~1_amd64.buildinfo
Checksums-Sha256:
 42b9dad203118d0a0f97cc93e6f42440e10039b8c27a6fb111ef53e190da80fa 1708 
golang-defaults_1.21~1.dsc
 cd161d7db248a967748f4f6464e1ddf1065cf69348e178e5ac5fa8d598afd91d 30896 
golang-defaults_1.21~1.tar.xz
 afcd450d343d61561aa00554796b14296186ae5a4545bc249ce7056ade7ccd73 6450 
golang-defaults_1.21~1_amd64.buildinfo
Files:
 b415c55dcde1d024ca9eb7283592b604 1708 golang optional 
golang-defaults_1.21~1.dsc
 3f96ba29f36d123c2822584e33f3661f 30896 golang optional 
golang-defaults_1.21~1.tar.xz
 9deae159d1782cff1663bff3e067c075 6450 golang optional 
golang-defaults_1.21~1_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQSRhdT1d2eu7mxV1B5/RPol6lUUywUCZNNTGgAKCRB/RPol6lUU
y39QAP4qXhqw9LqvTwJSUP58bVe5KySeXY0JHyVawMBBjGacBAEAhAdExK6TrNH5
5jpGxq3XQwL5tAeM+pt1vZFwpxTfTwg=
=74wp
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to