Your message dated Sun, 28 Aug 2022 17:18:04 +0200
with message-id <ywuhlmh89qfcd...@ramacher.at>
and subject line Re: Bug#1017705: transition: benchmark
has caused the Debian Bug report #1017705,
regarding transition: benchmark
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.)
--
1017705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017705
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: transition
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Dear release team,
I'd like to transition benchmark after upstream broke ABI compatibility
with their latest release. The tracker at
https://release.debian.org/transitions/html/auto-benchmark.html
looks good.
My test rebuilds on amd64 had the following outcomes:
- - openrct2 has an unrelated FTBFS [1] but builds OK if worked around
the issue by dropping -Werror
- - ros2-performance-text-fixture builds OK
- - pytorch fails to build, but is RC-buggy and not in testing
Most packages depend on benchmark for build tests only and do not ship
any binaries linked against it. I did a few random rebuilds without
issues, but did not test the archive comprehensively.
Cheers
Timo
[1] https://bugs.debian.org/1017596
-----BEGIN PGP SIGNATURE-----
iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmL/RrIACgkQ+C8H+466
LVkn7AwAwhU1yxPb1cVlUtKpP51yaLBuxDP79tkW+XCMorfUeQ52R0Rnllhr83uy
WyVAQ5R7J8ItvBvq2n8ZzfI8zhxO/2itRMw0FO8/M6ol4ZUhI7ZIMGhRgajD6TFm
WWWt50cDBRBflNH9gDlzdhEoBfMgaLFYaR3dsKBkHUnVarTIlX+sy7Cz4DuSPXU6
wdCNhyeSB04R9ow8oZJKwsbfszvBTl3r+aijFzb3KXIejbZIRFolAakzS1xihyF8
DLgjYNnB4/Aiyg4j+uZ3skVw+MZfSc5DrDzFxTf3QnRy1Ee4Zl9xPuJDL59smuEY
K2yglx3mc+L093MJIQjRfq2LGsW8dQ1zveJ781Cl2WR+3Sb54jQSYrhyQAIoZhP6
w5orDpERbf0uOZpmBszIHayDoyMovnSnM/PXtsgPwxEjVtscUwmGUPEqDJIhDDdF
lwBSFQCmfvcIyDWn7UnR8SVe5/mt6h+wdtM9uQC6MV+Z49bJkh0B9cViwjnOqLPf
+IJFNlWX
=bEYb
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On 2022-08-21 19:06:45 +0200, Sebastian Ramacher wrote:
> Control: tags -1 confirmed
>
> On 2022-08-19 10:15:50 +0200, Timo Röhling wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian....@packages.debian.org
> > Usertags: transition
> >
> > Dear release team,
> >
> > I'd like to transition benchmark after upstream broke ABI compatibility
> > with their latest release. The tracker at
> > https://release.debian.org/transitions/html/auto-benchmark.html
> > looks good.
> >
> > My test rebuilds on amd64 had the following outcomes:
> > - openrct2 has an unrelated FTBFS [1] but builds OK if worked around
> > the issue by dropping -Werror
> > - ros2-performance-text-fixture builds OK
> > - pytorch fails to build, but is RC-buggy and not in testing
> >
> > Most packages depend on benchmark for build tests only and do not ship
> > any binaries linked against it. I did a few random rebuilds without
> > issues, but did not test the archive comprehensively.
>
> Please go ahead
The old binary packages got removed from testing.
Cheers
--
Sebastian Ramacher
--- End Message ---
