[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1057304: marked as done (nmu: ros2-performance-test-fixture_0.2.0-1)

Your message dated Fri, 5 Jan 2024 22:16:44 +0100
with message-id <ZZhxvGS-Gp7O5mKG@ramacher.at>
and subject line Re: Bug#1057304: nmu: ros2-performance-test-fixture_0.2.0-1
has caused the Debian Bug report #1057304,
regarding nmu: ros2-performance-test-fixture_0.2.0-1
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 owner@bugs.debian.org
immediately.)


-- 
1057304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057304
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: ros2-performance-test-fixture@packages.debian.org, team+robotics@tracker.debian.org
Control: affects -1 + src:ros2-performance-test-fixture

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

nmu ros2-performance-test-fixture_0.2.0-1 . ANY . unstable . -m "Rebuild against benchmark (Closes: #1054676)"

benchmark 1.8.3 apparently dropped an exported symbol, which causes an 
undefined reference to `benchmark::internal::Benchmark::Benchmark(char 
const*)' when linking against ros2-performance-test-fixture.

A binNMU seems to be the simplest fix for that.


Cheers
Timo


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

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmVruXkACgkQ+C8H+466
LVn5WAv/WyQ9BfZxjG9e6vDx2lGKvkTUSE0WnZ/V2wvwZXn1qytJDdKlsRuMuGTZ
9BE5usD35IKv2yuPnPjYNxB8cRfKZX2O5iDTVNf3WZ9puRpe7X5f2ydQevfsW7j0
foq+VZ5/dkWyNHskrOUXCZHewI59XNkrILgpRIel6A3aa0Nb13d6pn00775df244
zSrgB9eGzLH9fbZNI4TE63/re/CJAWBjS316qO5og7aAimELHldhxK2/RP+mZ2Av
O0BGXl9d6j69L8CvpG0mSSH1iQ9ucbANM/4eUB5dKHMv24dLw+WV24Cy2J67scta
B2ZJCnlSnxQ2l+MNCLPtakPHURuqEdDhMsVld3vcSiR6OawfAtG9v5W5AdVwGFRs
abBLuUd+UaVS4zFBzQMKGoPXvvD5NVZWjj53Et5QziF37HkHuf9uw+V0MeVrNUfu
8ZiuOgk+BXZ2bF/oplASBqkr8aqtVWBMXkON15UXSrKLoUnL0Fmwk0HUL2B7fByH
mX/9FT/J
=g67D
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
On 2023-12-03 10:45:38 +0100, Sebastian Ramacher wrote:
> Control: tags -1 moreinfo
> 
> On 2023-12-03 00:10:52 +0100, Timo Röhling wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian.org@packages.debian.org
> > Usertags: binnmu
> > X-Debbugs-Cc: ros2-performance-test-fixture@packages.debian.org, team+robotics@tracker.debian.org
> > Control: affects -1 + src:ros2-performance-test-fixture
> > 
> > nmu ros2-performance-test-fixture_0.2.0-1 . ANY . unstable . -m "Rebuild against benchmark (Closes: #1054676)"
> > 
> > benchmark 1.8.3 apparently dropped an exported symbol, which causes an 
> > undefined reference to `benchmark::internal::Benchmark::Benchmark(char 
> > const*)' when linking against ros2-performance-test-fixture.
> 
> If benchmark drops a symbol from its shared library without a SONAME
> bump, that's a serious bug in benchmark. Please clarify the situation
> with the benchmark maintainers.
> 
> > A binNMU seems to be the simplest fix for that.
> 
> That would just hide a serious bug in benchmark.

benchmark got fixed.

Cheers
-- 
Sebastian Ramacher

--- End Message ---
Reply to: