Your message dated Fri, 21 Jan 2022 20:04:14 +0100
with message-id <5bf144c0a4327d53a1513595b7ebb99cf495298e.ca...@bzed.de>
and subject line Fixed a long time ago....
has caused the Debian Bug report #873717,
regarding collectd: FTBFS with libsigrok4
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.)
--
873717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: collectd
Version: 5.7.2-1
Tags: upstream
I have recently uploaded an up-to-date version of libsigrok to
experimental, which bumps the library soname to 4. The only package
that's not part of the sigrok suite which depends on libsigrok is
collectd. However a simple attempt to rebuild against the updated
library failed as the configure script checks to ensure the version is <
0.4. Removing this check unsurprisingly resulted in a build failure due
to changes in the libsigrok API. Upstream are tracking this at:
https://github.com/collectd/collectd/issues/1574
but there's been no progress in over a year. I may have time to
investigate in a few weeks if no one gets there first, but no promises.
J.
--
/-\ | If I want to hear the pitter
|@/ Debian GNU/Linux Developer | patter of little feet, I'll put
\- | shoes on my cats.
--- End Message ---
--- Begin Message ---
Version: 5.6.0-1
Thanks,
Bernd
--
Bernd Zeimetz Debian GNU/Linux Developer
http://bzed.de http://www.debian.org
GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
--- End Message ---
