Your message dated Wed, 06 May 2026 12:19:17 +0000
with message-id <[email protected]>
and subject line Bug#1114525: fixed in zabbix 1:7.0.22+dfsg-1.1
has caused the Debian Bug report #1114525,
regarding zabbix: Please update vendoring logic for golang-github-go-ldap-ldap
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.)
--
1114525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1114525
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: zabbix
Version: 1:7.0.10+dfsg-2
Severity: important
Affects: src:golang-github-go-ldap-ldap
I am working on updating the packaging for golang-github-go-ldap-
ldap, including fixing its import path from an ancient
"gopkg.in/ldap.v2" to the proper "github.com/go-ldap/ldap".
zabbix does something in its build process to recreate the contents
of the "vendor" directory, including creating a symlink to ldap.v2 that
no longer exists with the changes.
I've pushed the packaging updates to
https://salsa.debian.org/go-team/packages/golang-github-go-ldap-ldap.
Could you make whatever changes are necessary to zabbix and let me know
when you're ready to do an upload so I can coordinate the upload of the
new ldap package?
Thanks,
Mathias
> $ readlink src/go/vendor/github.com/go-ldap/ldap
> ../../gopkg.in/ldap.v2
> $ ls src/go/vendor/gopkg.in/
> asn1-ber.v1 check.v1 ldap.v2 mgo.v2 tomb.v2 yaml.v3
>
> go build -v [snip] golang.zabbix.com/agent2/cmd/zabbix_agent2
> plugins/net/tcp/tcp.go:29:2: cannot find module providing package
> github.com/go-ldap/ldap: import lookup disabled by -mod=vendor
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: zabbix
Source-Version: 1:7.0.22+dfsg-1.1
Done: Adrian Bunk <[email protected]>
We believe that the bug you reported is fixed in the latest version of
zabbix, 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.
Adrian Bunk <[email protected]> (supplier of updated zabbix 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: Tue, 21 Apr 2026 13:58:26 +0300
Source: zabbix
Architecture: source
Version: 1:7.0.22+dfsg-1.1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov <[email protected]>
Changed-By: Adrian Bunk <[email protected]>
Closes: 1114525
Changes:
zabbix (1:7.0.22+dfsg-1.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Add patch from Mathias Gibbens for newer golang-github-go-ldap-ldap.
(Closes: #1114525)
Checksums-Sha1:
7e71ccd015230056cfd9d36167978d06086bcb67 4209 zabbix_7.0.22+dfsg-1.1.dsc
dc4efdc46ef4a1ae6b1df56b3017ff8cd27a60af 145116
zabbix_7.0.22+dfsg-1.1.debian.tar.xz
Checksums-Sha256:
8439438abd00ae7b427eb5fcdc0be7ab2e4a673650782fb345a988c432d927a3 4209
zabbix_7.0.22+dfsg-1.1.dsc
2c3a60301e79ff77c2d7a142ea6a4b017cc8aafa3d4595a35fd5036cbccdb73e 145116
zabbix_7.0.22+dfsg-1.1.debian.tar.xz
Files:
779ad2cd1d3a70363b60722f9e83b8cd 4209 net optional zabbix_7.0.22+dfsg-1.1.dsc
a475c04db6c5e905716e1b4cde830141 145116 net optional
zabbix_7.0.22+dfsg-1.1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmnnWwoACgkQiNJCh6LY
mLHoOQ/7BGEzSwvxeHc2ikCi2JgsZGyxKGeIyC4JuhbHfaX0b1salCw7Az44chRY
LUtHM+JLZKorbkxV3oFCZqL/vYu6o97OpUBs8mQrEM2goDiycEICc22RWdFmH7Xq
cirRqlQvFpvZkxhxv+HyPS4uTgH4i46Z7TbM3mDcQQ5Xd2NxeN5BkZJ6uDG2mqYB
uwZ5vs+9eWkw3E0WkqZw2DJcW5RyddlMavWH6kJGfU7f/9IpOtxljSR8qz72yCN0
8qkkuXB8UKd1NaMKFJ8m0AMKfqnxYJUYZt3D2QAvD/rQkbvdQTlrD9lOtTW26IlB
xUXB1yXN2nrgq8xHnDzjoAJyTegUrmSAWG+IJa6Ra2dqgWcs4jdS+Wg0c46VFDMz
pfFINwc+dHdzvijDEEGF65NZXK+t84p9FdbbOXTjx6m7SfxVcyLfGHdSojgU+hx4
UNyuTij3gl1m7I5wm1679fMSFe2Di+sAPUTmlYD4z3Z08EDeZ2ztvj2MtnsioKIy
AUkgoCKWJ9hDHgAZU6v6f0tykN7IEFD+w7TGSBB/OL+ZNymwchMBBG4gI/jSqNEz
AE9uHqwF+TV37Bw3NGDhPihQiLf9OtIj8936UdoATPjba1ig7a/d/Zl1i7ts71RM
uJse27jfwMU8BToU8SvbA+Y+rLAAmOcpmaFJTXxBkV2MNslE3CA=
=JPRN
-----END PGP SIGNATURE-----
pgp42u8U3hnvk.pgp
Description: PGP signature
--- End Message ---
