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

Bug#1108185: bookworm-pu: package prody/2.3.1+dfsg-3+deb12u1



On Sat, Jul 05, 2025 at 05:32:15PM +0100, Adam D. Barratt wrote:
> On Sat, 2025-07-05 at 17:27 +0100, Adam D. Barratt wrote:
> > On Sun, 2025-06-22 at 17:49 +0200, Santiago Vila wrote:
> > > This fixes Bug #1028722 prody: FTBFS: AssertionError: 3205 != 3211
> > > 
> > > [ Impact ]
> > > Anybody trying to build the package from source may unexpectedly
> > > find that the package does not build depending on particular
> > > hardware.
> > > 
> > > [ Tests ]
> > > I've tested that the package builds ok again on the systems where
> > > it used to fail.
> > 
> > Although they obviousy aren't the result of the change in this bug,
> > for the record the package still fails to build on i386 with several
> > test failures. Two of the three test failures seen in p-u also appear
> > in the current unstable packages.
> 
> This appears to be #1058454, which has been open for a while now. :-(

Yes, that's what it seems, but additionally the package currently in unstable
does not build for other reasons (for example, #1071807).

Would it be acceptable in this case if we fix the i386 build issue
in stable first? (considering that the package is not and will not
be in trixie).

If yes, can it still be versioned as 2.3.1+dfsg-3+deb12u1, or it should be
deb12u2?

My current plan would be to follow the idea of Andrius Merkys (in the CC)
of relaxing the tolerance for those floating point equality comparisons.

Thanks.


Reply to: