Bug#1053316: polymake: Causes FTBFS for gap-polymaking by failing tests
Joachim Zobel writes: Control: fixed -1 4.11-2 > Package: polymake > Version: 4.6-5+b2 > Severity: important > > Dear Maintainer, > > The package polymake causes a FTBFS in its GAP interface package > gap-polymaking > when building for trixie. > >> Architecture: x86_64-pc-linux-gnu-default64-kv8 >> >> testing: /<>/debian/gaproot/pkg/\ >> polymaking/tst/example.tst >> polymake: upgrading /tmp/gaptempdirKvYo8c/poly1318 from old plain file format >> polymake: ERROR: "/usr/share/polymake/perllib/Polymake/Core/CPlusPlus.pm", 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
Bug#1053316: polymake: Causes FTBFS for gap-polymaking by failing tests
On 02/10/2023 08.46, Joachim Zobel wrote: Am Sonntag, dem 01.10.2023 um 15:30 -0300 schrieb David Bremner: 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. The discussion done in the inncluded link boils down to "won't fix, wait for Julia". Is there any timeline for this? Unfortunately there is really no timeline for this and I would be 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
Bug#1053316: polymake: Causes FTBFS for gap-polymaking by failing tests
Am Sonntag, dem 01.10.2023 um 15:30 -0300 schrieb David Bremner: > 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. The discussion done in the inncluded link boils down to "won't fix, wait for Julia". Is there any timeline for this? Sincerely, Joachim
Bug#1053316: polymake: Causes FTBFS for gap-polymaking by failing tests
Joachim Zobel writes: > Package: polymake > Version: 4.6-5+b2 > Severity: important > > Dear Maintainer, > > The package polymake causes a FTBFS in its GAP interface package > gap-polymaking > when building for trixie. > 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
Bug#1053316: polymake: Causes FTBFS for gap-polymaking by failing tests
Package: polymake Version: 4.6-5+b2 Severity: important Dear Maintainer, The package polymake causes a FTBFS in its GAP interface package gap-polymaking when building for trixie. > Architecture: x86_64-pc-linux-gnu-default64-kv8 > > testing: /<>/debian/gaproot/pkg/\ > polymaking/tst/example.tst > polymake: upgrading /tmp/gaptempdirKvYo8c/poly1318 from old plain file format > polymake: ERROR: "/usr/share/polymake/perllib/Polymake/Core/CPlusPlus.pm", 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 *** -- System Information: Debian Release: 12.1 APT prefers oldstable-security APT policy: (500, 'oldstable-security'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-10-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages polymake depends on: ii libbliss2 0.73-5 ii libc6 2.36-9+deb12u1 ii libcdd0d094m-1 ii libflint17 2.9.0-5 ii libgcc-s1 12.2.0-14 ii libgmp102:6.2.1+dfsg1-1.1 ii libgomp112.2.0-14 ii liblrs1 0.71b-2 ii libmpfr64.2.0-1 ii libpolymake-dev-common 4.6-5 ii libppl141:1.2-8.1+b1 ii libsingular4m3n01:4.3.1-p3+ds-2 ii libstdc++6 12.2.0-14 ii ninja-build 1.11.1-1 ii perl5.36.0-7 ii perl-base [perlapi-5.36.0] 5.36.0-7 ii polymake-common 4.6-5 Versions of packages polymake recommends: ii chromium 117.0.5938.62-1~deb11u1 ii gfan 0.6.2-6+b1 ii graphviz 2.42.2-7+b3 ii xdg-utils 1.1.3-4.1 Versions of packages polymake suggests: pn povray ii texlive-latex-extra 2022.20230122-4 ii texlive-pictures 2022.20230122-3 -- debconf-show failed
