Bug#988725: libzmq3-dev: cppzmq headers aren't actually from version 4.7.0

Lukas K.

unread,

May 18, 2021, 2:30:03 PM5/18/21

to

Package: libzmq3-dev
Version: 4.3.4-1
Severity: important
X-Debbugs-Cc: deb...@0x83.eu

Dear Maintainer,

The zeromq package includes the zmq.hpp header from the cppzmq project: https://github.com/zeromq/cppzmq

The version reported by CPPZMQ_VERSION_MAJOR/MINOR/PATCH is 4.7.0, so it should include zmq::sockopt. However, it doesn't and this breaks software that expects it to be there if the version is 4.7.0 or greater.

This is how this most likely came to be:

cppzmq updated the version to 4.7.0 on Jan 17, 2020 https://github.com/zeromq/cppzmq/commit/70d059bd0a8376435ce8999d0d16b43cc42850f3

Debian Changelog:
* Sync zmq.hpp from cppzmq (closes: #951135).
* Update Standards-Version to 4.5.0 .

-- Laszlo Boszormenyi (GCS) <g...@debian.org> Thu, 20 Feb 2020 20:12:19 +0000

cppzmq adds zmq::sockopt on Mar 24, 2020 https://github.com/zeromq/cppzmq/commit/a3e5b54c3cad9dc1c4e86555e47365c2d3950e63

Sep 30, 2020, cppzmq 4.7.0 is released

The most appropriate fix is updating zmq.hpp and zmq_addon.hpp to the
released version from 4.7.0.

Long-term, I think it'd be good to put cppzmq in its own package, as
discussed in #972785.

Best Regards,

Lukas

-- System Information:
Debian Release: bullseye/sid
APT prefers testing-security
APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.11.16-arch1-1 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages libzmq3-dev depends on:
ii libbsd-dev 0.11.3-1
ii libkrb5-dev 1.18.3-5
ii libnorm-dev 1.5.9+dfsg-2
ii libpgm-dev 5.3.128~dfsg-2
ii libsodium-dev 1.0.18-1
ii libzmq5 4.3.4-1

libzmq3-dev recommends no packages.

libzmq3-dev suggests no packages.

-- no debconf information

Timo Röhling

unread,

Dec 15, 2021, 5:00:04 AM12/15/21

to

Control: affects 988725 src:open3d

Hi,

On Tue, 18 May 2021 18:16:29 +0000 "Lukas K." <deb...@0x83.eu> wrote:
> The version reported by CPPZMQ_VERSION_MAJOR/MINOR/PATCH is 4.7.0,
> so it should include zmq::sockopt. However, it doesn't and this
> breaks software that expects it to be there if the version is
> 4.7.0 or greater.

This bug prevents me from packaging open3d 0.14.1, which requires
version 4.7.0 or greater to build.

Cheers
Timo

--
⢀⣴⠾⠻⢶⣦⠀ ╭────────────────────────────────────────────────────╮
⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │
⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄⠀⠀⠀⠀ ╰────────────────────────────────────────────────────╯

signature.asc

Lukas K.

unread,

Dec 19, 2021, 7:10:03 AM12/19/21

to

Hi,

I've had a look on packages.debian.org and as far a I can tell the bug
only got fixed in unstable. Will this fix be backported to bullseye?
There, it probably makes the most sense to use version 4.7.0 rather tan
4.8.1.

Best Regards,

Lukas

On 16.12.21 09:36, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the libzmq3-dev package:
>
> #988725: libzmq3-dev: cppzmq headers aren't actually from version 4.7.0
>
> It has been closed by Debian FTP Masters <ftpm...@ftp-master.debian.org> (reply to Laszlo Boszormenyi (GCS) <g...@debian.org>).
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Debian FTP Masters <ftpm...@ftp-master.debian.org> (reply to Laszlo Boszormenyi (GCS) <g...@debian.org>) by
> replying to this email.
>
>

László Böszörményi

unread,

Dec 19, 2021, 8:00:03 AM12/19/21

to

Hi Lukas,

On Sun, Dec 19, 2021 at 1:09 PM Lukas K. <deb...@0x83.eu> wrote:
> I've had a look on packages.debian.org and as far a I can tell the bug
> only got fixed in unstable. Will this fix be backported to bullseye?

It is only fixed in Sid as usual. Stable releases like Bullseye are
updated if the bug impact several users and/or being security
relevant.
How many users / use cases does this affect in Bullseye?

> There, it probably makes the most sense to use version 4.7.0 rather tan
> 4.8.1.

As I know, it doesn't really matter. Its upstream, Luca noted:
"Upstream we generally try our best to keep the hpp header forward and
backward compatible, so there should be no surprises".

Cheers,
Laszlo/GCS