Pyparsing upstream finally made the v3.1.2 release the other day with the
fix. So I guess once that lands in unstable it should be ok.
On Sat, Apr 6, 2024 at 12:30 AM Antoine Beaupré wrote:
> On 2023-07-27 13:04:22, Riccardo Coccioli wrote:
> > I've checked the issue and opened a bug upstream
On 2023-07-27 13:04:22, Riccardo Coccioli wrote:
> I've checked the issue and opened a bug upstream to pyparsing [1] as this
> is indeed a regression.
> Running CI on cumin I've also found that pylint is reporting new issues
> related to pyparsing code, for which I've opened a separate bug
I've checked the issue and opened a bug upstream to pyparsing [1] as this
is indeed a regression.
Running CI on cumin I've also found that pylint is reporting new issues
related to pyparsing code, for which I've opened a separate bug upstream
[2].
[1]
This seems to be caused by the version change of python3-pyparsing
fom 3.0.9-1 in bookworm to 3.1.0-1 in trixie/sid.
At first sight it looks like that this minor version change in pyparsing
has caused some backward incompatibility.
I'll have a look in the next few days at what changed and try to
Source: cumin
Version: 4.2.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh
5 matches
Mail list logo