Your message dated Fri, 01 Nov 2024 08:54:21 +0000
with message-id <e1t6nqd-001jb4...@fasolo.debian.org>
and subject line Bug#1085860: fixed in zabbix 1:7.0.5+dfsg-1
has caused the Debian Bug report #1085860,
regarding zabbix: FTBFS after golang library updates
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 ow...@bugs.debian.org
immediately.)


-- 
1085860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085860
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zabbix
Version: 1:7.0.3+dfsg-1
Severity: serious
Justification: FTBFS
Tags: sid ftbfs patch
Affects: src:golang-github-go-logr-logr src:golang-github-go-sql-driver-mysql 
src:golang-github-mattn-go-sqlite3

  Recently a couple golang libraries were updated, and unfortunately
they're causing zabbix to FTBFS. This wasn't caught due to another
package which was FTBFS and masked the zabbix build failure.

  Thankfully, it's a trivial matter to fix the build; I've attached a
patch. (There's quite a list of modules, with various required golang
versions; you might want to consider bumping them all up to 1.23 to
match the version of go currently in unstable.)

  I would like to upload a newer version of golang-github-mattn-go-
sqlite3, but will hold off until it won't cause an additional build
failure for zabbix.

Thanks,
Mathias
diff --git a/vendor/modules.txt b/vendor/modules.txt.new
index 210be56..a3d1d70 100644
--- a/vendor/modules.txt
+++ b/vendor/modules.txt.new
@@ -87,14 +87,14 @@ github.com/go-ldap/ldap
 ## explicit; go 1.17
 github.com/go-logfmt/logfmt
 # github.com/go-logr/logr v1.2.3
-## explicit; go 1.16
+## explicit; go 1.18
 github.com/go-logr/logr
 # github.com/go-ole/go-ole v1.2.6
 ## explicit; go 1.12
 github.com/go-ole/go-ole
 github.com/go-ole/go-ole/oleutil
 # github.com/go-sql-driver/mysql v1.7.1
-## explicit; go 1.13
+## explicit; go 1.18
 github.com/go-sql-driver/mysql
 # github.com/goburrow/modbus v0.1.0
 ## explicit
@@ -149,7 +149,7 @@ github.com/mailru/easyjson/buffer
 github.com/mailru/easyjson/jlexer
 github.com/mailru/easyjson/jwriter
 # github.com/mattn/go-sqlite3 v1.14.19
-## explicit; go 1.16
+## explicit; go 1.18
 github.com/mattn/go-sqlite3
 # github.com/mediocregopher/radix/v3 v3.8.1
 ## explicit; go 1.13

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
--- Begin Message ---
Source: zabbix
Source-Version: 1:7.0.5+dfsg-1
Done: Dmitry Smirnov <only...@debian.org>

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 1085...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Smirnov <only...@debian.org> (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 ftpmas...@ftp-master.debian.org)


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

Format: 1.8
Date: Fri, 01 Nov 2024 18:11:40 +1100
Source: zabbix
Architecture: source
Version: 1:7.0.5+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov <only...@debian.org>
Changed-By: Dmitry Smirnov <only...@debian.org>
Closes: 1080985 1085860
Changes:
 zabbix (1:7.0.5+dfsg-1) unstable; urgency=medium
 .
   * New upstream release.
   * rules: removed "--no-start" to enable server's auto-restart on upgrade 
(Closes: #1080985).
     Thanks, Maximilian Stein.
   * New patch to fix FTBFS (Closes: #1085860).
     Thanks, Mathias Gibbens <gib...@debian.org>.
Checksums-Sha1:
 9016bafb89f1a2ae7845cb7f52347e7468ae0adf 4143 zabbix_7.0.5+dfsg-1.dsc
 06d702035b7cf713ebf87b82c8be7b74deaae97f 14943664 
zabbix_7.0.5+dfsg.orig-templates.tar.xz
 8ec8686c6c7cb5246bf9d1f40420e4612bb29fff 826688 
zabbix_7.0.5+dfsg.orig-vendor.tar.xz
 58ed6eaafbd7a03458342438ad799c51c97921db 24958424 zabbix_7.0.5+dfsg.orig.tar.xz
 d96f2ca587d0660c93242ebef4ee65ec2cb1845c 142800 
zabbix_7.0.5+dfsg-1.debian.tar.xz
 741c576160f7547601928a911b8d021daa1b3cf6 21929 
zabbix_7.0.5+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 b17abf73a52032fb368acc45b1d28dec6aaed43d3f6afd16821406e549bf9de5 4143 
zabbix_7.0.5+dfsg-1.dsc
 9b6d55fa324f584ba355516240f4a2db3c5c5dc275a56f7ef4bc651e037f4878 14943664 
zabbix_7.0.5+dfsg.orig-templates.tar.xz
 1b166346c800795f8ae5f875a27efe3c0c4e6eef2f196f4527f26b35e4f0642f 826688 
zabbix_7.0.5+dfsg.orig-vendor.tar.xz
 5a6110903544575fefbd71019072842930c73005c7a1d47bd54c52366a6d7773 24958424 
zabbix_7.0.5+dfsg.orig.tar.xz
 0bb033f77310e835bc7edeab70f2f6d2052d8f9a00f98b3d9c8105650a41a0d7 142800 
zabbix_7.0.5+dfsg-1.debian.tar.xz
 63eaf8aed50814353396943bcb08ede484fd4b8ae4138e8af0ee0e847547cedd 21929 
zabbix_7.0.5+dfsg-1_amd64.buildinfo
Files:
 f764f08e8bbbbb5b1378aae43a7c6695 4143 net optional zabbix_7.0.5+dfsg-1.dsc
 c16332f9f8766fecc789dc21c79c7658 14943664 net optional 
zabbix_7.0.5+dfsg.orig-templates.tar.xz
 20dd2a3c0e06a918ee6ac8b867aedcb9 826688 net optional 
zabbix_7.0.5+dfsg.orig-vendor.tar.xz
 bda1bf654a33376ef503dcf7c4b7cab5 24958424 net optional 
zabbix_7.0.5+dfsg.orig.tar.xz
 aca0f6637cebf3532b84f60b9bfbf84c 142800 net optional 
zabbix_7.0.5+dfsg-1.debian.tar.xz
 cf2b9bb3972cd05f0f4f82812d6ba4f2 21929 net optional 
zabbix_7.0.5+dfsg-1_amd64.buildinfo

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

iQIzBAEBCAAdFiEEULx8+TnSDCcqawZWUra72VOWjRsFAmckiM4ACgkQUra72VOW
jRuN8BAAgX/OT9/wwPtrM5JI9m6X7YSMrMbV5kVsaCNjyTctJdnDXAuL0lL59/7+
ClEytPRfSPtlGASHMlJELtTiMT1iAMtvN5K5mt/jaLiMFfOcfQ0K9HUKT0Hz4Eix
48ajYBye6fNn/SQUE7CLq9somUPl+1aaYtlFUnwJ3rCcdx1BH7VVqltzHvObLPKC
sZNpfN89myqX8kORiutAA2vZA5Xmd2r0Y0JxpkJwlTPg9guiUfR7OGmHdOT1ehaR
k87EzYU2wLXwcYN7YfZv+o2jCI/H+UFJjRhRYg3T4+mrgh3JS24pDo7L/EHHGhRJ
6Muw+lClyHLIxtSSxZJrnM92O1C8JbNyiKdM+70/EooPaHVR3vOMDSG8XcVe2kdD
yCghZBETA8/Hz55AA6QG0NEojlrWNYFkLeDK5RR1KFcTGIlnhPP2ESXdR6pSDNhQ
gWrL06kbDm5F4+5FbAs08pXruQtPpy26rnYHNV6RqaC0ZlxHA1/JcTRFcez1Cwtr
U35uKvvzZXyHPFcR22346g51YBji2zFzkqqrxCi4hDt7QWT6AVJSiE2RNW/AfU+3
VTQ7pUL+IZfxevdQUQXn/sLycBCl4LuYRlYque/jQ6OLMvVgqWngyL802hr7RsUy
2wqXoi5WkOvaRSvnQvbw/4/MpgAns7GtNrqsT0B0jr85zf8yVeA=
=rsg4
-----END PGP SIGNATURE-----

Attachment: pgpvnv54rDaYc.pgp
Description: PGP signature


--- End Message ---

Reply via email to