Hi,
On 2023-11-06 14:17, Santiago Vila wrote:
Note: I'd like to see this fixed in stable, but RMs require
(rightly so) that this is fixed in unstable first.
Thanks. You may look into disabling prody's part which uses biopython,
maybe this will make it easier to fix the comparison issue in
Note: I'd like to see this fixed in stable, but RMs require
(rightly so) that this is fixed in unstable first.
Thanks. You may look into disabling prody's part which uses biopython, maybe
this will make it easier to fix the comparison issue in unstable. I don't know
whether this is possible,
Hi Santiago,
On 2023-11-02 01:14, Santiago Vila wrote:
El 13/10/23 a las 8:04, Andrius Merkys escribió:
To summarize: The failing test is buggy because when it fails
it does not necessarily mean that the package was misbuilt,
and in my opinion the best thing to do would be to disable it,
both
El 13/10/23 a las 8:04, Andrius Merkys escribió:
To summarize: The failing test is buggy because when it fails
it does not necessarily mean that the package was misbuilt,
and in my opinion the best thing to do would be to disable it,
both in stable and unstable.
Trivial patch in the second
Hello,
On 2023-10-12 21:22, Santiago Vila wrote:
To summarize: The failing test is buggy because when it fails
it does not necessarily mean that the package was misbuilt,
and in my opinion the best thing to do would be to disable it,
both in stable and unstable.
Trivial patch in the second
tags 1028722 + patch
thanks
Hello.
I asked Drew Parsons to look at this bug because he reported a similar
bug with severity:serious here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053265
In both cases the failure happens while comparing floating
point numbers using the equality
Hello,
On 2023-09-30 15:11, Drew Parsons wrote:
There seems to be ambiguity about the reproducibility of this bug.
That's possibly consistent with problems with rounding, though the bug
here seems to be more than an issue with floating point precision.
Upstream has made a new release. I
Source: prody
Followup-For: Bug #1028722
There seems to be ambiguity about the reproducibility of this bug.
That's possibly consistent with problems with rounding, though the bug
here seems to be more than an issue with floating point precision.
Upstream has made a new release. I suggest
Hi,
On 27/01/23 at 14:31 +0200, Andrius Merkys wrote:
> Control: severity -1 important
> Control: tags -1 + moreinfo unreproducible
>
> Hello,
>
> On 2023-01-27 13:40, Adrian Bunk wrote:
> > On Sat, Jan 14, 2023 at 01:42:10PM +0100, Lucas Nussbaum wrote:
> > > Source: prody
> > > Version:
Control: severity -1 important
Control: tags -1 + moreinfo unreproducible
Hello,
On 2023-01-27 13:40, Adrian Bunk wrote:
On Sat, Jan 14, 2023 at 01:42:10PM +0100, Lucas Nussbaum wrote:
Source: prody
Version: 2.3.1+dfsg-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User:
On Sat, Jan 14, 2023 at 01:42:10PM +0100, Lucas Nussbaum wrote:
> Source: prody
> Version: 2.3.1+dfsg-3
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20230113 ftbfs-bookworm
>
> Hi,
>
> During a rebuild of all packages in sid,
11 matches
Mail list logo