#1053316 polymake: Causes FTBFS for gap-polymaking by failing tests

Package:
polymake
Source:
polymake
Description:
Tool for algorithmic discrete geometry
Submitter:
Joachim Zobel
Date:
2023-11-22 18:57:05 UTC
Severity:
normal
#1053316#5
Date:
2023-10-01 15:11:41 UTC
From:
To:
Dear Maintainer,

The package polymake causes a FTBFS in its GAP interface package gap-polymaking
when building for trixie.
line 1785: Can't load shared module /usr/lib/polymake/lib/ideal.so:
libsingular-Singular-4.3.1.so: cannot open shared object file: No such file or
directory

The reason is that libsingular-Singular-4.3.1.so is not present, only
libsingular-Singular-4.3.2.so is.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052949
The package gap-hapcryst is also affected:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052974








*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***
#1053316#10
Date:
2023-10-01 18:30:22 UTC
From:
To:
Joachim Zobel <jz-2016@heute-morgen.de> writes:

I'm currently waiting to see what happens with

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042521

before putting much effort into debugging polymake issues.

d
#1053316#15
Date:
2023-10-02 06:46:08 UTC
From:
To:
Am Sonntag, dem 01.10.2023 um 15:30 -0300 schrieb David Bremner:

The discussion done in the inncluded link boils down to "won't fix,
wait for Julia". Is there any timeline for this?

Sincerely,
Joachim
#1053316#20
Date:
2023-10-02 09:10:11 UTC
From:
To:
surprised if we can get this to work without perl within a year.

Regarding the current issue:
This seems like a rebuild of polymake against the new singular version
might help.
The libsingular package seems to have a very strict soname which is not
reflected in the package name, i.e.
libsingular4m3n0 version 4.3.1 contains libsingular-Singular-4.3.1.so
libsingular4m3n0 version 4.3.2 contains libsingular-Singular-4.3.2.so
But for each of these packages the soname contains the full version
(full filename).

I am not really sure how to handle this, do we need to pin singular to a
specific patch version to make this work?

Benjamin
#1053316#25
Date:
2023-11-22 17:13:53 UTC
From:
To:
Joachim Zobel <jz-2016@heute-morgen.de> writes:

Control: fixed -1 4.11-2

I have marked this fixed (for now) in 4.11-2, but I have not followed in
detail enough to know if the fix is permanent or just fluke.

d