Bug#1041230: onetbb 2021.9.0-1 FTBFS on multiple release architectures
Control: fixed -1 2021.9.0-2 I agree. On Thu, 2023-08-03 at 00:32 +0200, Petter Reinholdtsen wrote: > [M. Zhou] > > The issue still exists with armel: > > https://buildd.debian.org/status/package.php?p=onetbb > > If so, this is a duplicate of > https://bugs.debian.org/1042009 >, which is about the armel > issue, > and should be closed. >
Bug#1041230: onetbb 2021.9.0-1 FTBFS on multiple release architectures
[M. Zhou] > The issue still exists with armel: > https://buildd.debian.org/status/package.php?p=onetbb If so, this is a duplicate of https://bugs.debian.org/1042009 >, which is about the armel issue, and should be closed. -- Happy hacking Petter Reinholdtsen
Bug#1041230: onetbb 2021.9.0-1 FTBFS on multiple release architectures
The issue still exists with armel: https://buildd.debian.org/status/package.php?p=onetbb On Wed, 2023-08-02 at 22:46 +0200, Petter Reinholdtsen wrote: > [M. Zhou] > > I'm aware of this issue. I'm slightly faster than buildd for > > toolchain > > upgrades. The issue will automatically disappear once our amd64 > > buildd > > migrates to gcc-13. The gcc-12 will lead to the FTBFS you see now. > > Is this still an issue?
Bug#1041230: onetbb 2021.9.0-1 FTBFS on multiple release architectures
[M. Zhou] > I'm aware of this issue. I'm slightly faster than buildd for toolchain > upgrades. The issue will automatically disappear once our amd64 buildd > migrates to gcc-13. The gcc-12 will lead to the FTBFS you see now. Is this still an issue? -- Happy hacking Petter Reinholdtsen
Bug#1041230: onetbb 2021.9.0-1 FTBFS on multiple release architectures
Source: onetbb Version: 2021.9.0-1 Severity: serious I'm aware of this issue. I'm slightly faster than buildd for toolchain upgrades. The issue will automatically disappear once our amd64 buildd migrates to gcc-13. The gcc-12 will lead to the FTBFS you see now. Local sbuild with gcc-13 has no issue.
