Your message dated Wed, 04 Feb 2026 00:50:25 +0000
with message-id <[email protected]>
and subject line Bug#1118270: fixed in golang-gopkg-yaml.v3 3.0.4-2
has caused the Debian Bug report #1118270,
regarding upgrade from trixie has unhandled directory-turned-symlink issue
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.)


-- 
1118270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1118270
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: golang-gopkg-yaml.v3-dev
Severity: serious
Version: 3.0.4-1

Hi,

when upgrading from trixie to testing, when upgrading golang-gopkg-yaml.v3-dev gets updated from 3.0.1-3 to 3.0.4-1:

  * in 3.0.1-3 (stable), /usr/share/gocode/src/gopkg.in/yaml.v3
    is a directory.

  * in 3.0.4-1 (unstable), /usr/share/gocode/src/gopkg.in/yaml.v3
    is a symlink (to ../go.yaml.in/yaml/v3).

because golang-gopkg-yaml.v3-dev doesn't handle this in its maintainer scripts, after the upgrade from 3.0.3-1 to 3.0.4-1, this results in usr/share/gocode/src/gopkg.in/yaml.v3 being empty, leading other packages that use golang-gopkg-yaml.v3-dev as build-depends to FTBFS afterwards.

Please using dpkg-maintscript-helper to handle this, see:

https://manpages.debian.org/unstable/dpkg/dpkg-maintscript-helper.1.en.html#Switching_a_directory_to_symlink

Regards,
Daniel

--- End Message ---
--- Begin Message ---
Source: golang-gopkg-yaml.v3
Source-Version: 3.0.4-2
Done: Drew Parsons <[email protected]>

We believe that the bug you reported is fixed in the latest version of
golang-gopkg-yaml.v3, 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.
Drew Parsons <[email protected]> (supplier of updated golang-gopkg-yaml.v3 
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: SHA512

Format: 1.8
Date: Wed, 04 Feb 2026 01:12:17 +0100
Source: golang-gopkg-yaml.v3
Architecture: source
Version: 3.0.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team <[email protected]>
Changed-By: Drew Parsons <[email protected]>
Closes: 1115995 1118270
Changes:
 golang-gopkg-yaml.v3 (3.0.4-2) unstable; urgency=medium
 .
   * Team upload.
   * add preinst, postinst and postrm maintainer scripts to manage
     upgrade moving gopkg.in/yaml.v3 to a symlink to
     ../go.yaml.in/yaml/v3. Closes: #1118270, #1115995
   * Standards-Version: 4.7.3
Checksums-Sha1:
 b995b640765a82158dc32e25ac6e179e1c74d50c 2229 golang-gopkg-yaml.v3_3.0.4-2.dsc
 b023e55ce4a4caeb4ffcef8b6e20e78115563cff 5628 
golang-gopkg-yaml.v3_3.0.4-2.debian.tar.xz
Checksums-Sha256:
 ac3c70a9d2551971942e5f93b830142d5d97ddd54d406111f25fcb1a9b2d3188 2229 
golang-gopkg-yaml.v3_3.0.4-2.dsc
 cc15f85da149c068f9f7c10f8f804aa4d69ce87d23e4c45cfa61484dfc29cebe 5628 
golang-gopkg-yaml.v3_3.0.4-2.debian.tar.xz
Files:
 6334bd78d6b2e405cbf33f63488959f6 2229 golang optional 
golang-gopkg-yaml.v3_3.0.4-2.dsc
 c01b80e2f2933e8a5235a1e0cc6f65ba 5628 golang optional 
golang-gopkg-yaml.v3_3.0.4-2.debian.tar.xz

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

iQIzBAEBCgAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmmCkEUACgkQVz7x5L1a
AfrgNw/9GCYwtz4cTLam2WV0CKRY4AgDJg7PQR+/6HOFF93EyhPqiGWXj0+Pa3IO
MZozTooTb+BezvJ+omBMJOTpU9pH8FmwXz1VOMM1YZdx4LSnAT/O8PqT1nWn1kC/
gcn3sesUxM5uLguK7j41GhPYXya61nx2EJSbjlNQ5pXXw9K51W8ker/UmgyYwuF0
ogJ3dLGSuR157wJOPlIQ1pa9cbsCZSveBW/4dzaOy3OJPUqCh35ZI62bm8bT8TP8
52du/AJFfKS/Y5Mo5Y2nf9BmgkTpGJoYsN6uhqhO3K+gb9xZOUlJf0a24Jh6sake
GtP06NjBOfXZPcPsUVtkGKDY3B5IUeg8vO8xWd9BkdgGVXa9V9sxqmaVqKXhiRgE
mF6j/3lav3u8fylejXgftGCMUproaxSUTFc2xYayZn+C/kHAO8F4M4QnkP7VVKCY
ZuYuQCP3RoCD6UNqgygHaAadS1MAW4MUE/FnQyRVLgNesaElCS93mrA3M75Icl1Y
cjrT0D9SXp9eRk45QRfcKu50FGwM1CP67adzzOEzbPEgWc8IvmfA0d9bPx3dIl9t
xZCFqaq9wjK/x5n/T50d7w1nQmzwyHjpQ9MxJAKK45+SmTN+VOlikbcd820jyIuM
Zm7u/qv2Mdy87CHTWsgV5LxdXDLgZgz/qRfmmAVNIwl4zl0IA3Y=
=Ec21
-----END PGP SIGNATURE-----

Attachment: pgpMJCBJcd_z6.pgp
Description: PGP signature


--- End Message ---

Reply via email to