Bug#1041227: transition: suitesparse
On 2023-07-19 13:37:44 +0200, Sébastien Villemot wrote: > Le dimanche 16 juillet 2023 à 18:50 +0200, Sebastian Ramacher a écrit : > > On 2023-07-15 23:25:28 +0200, Sébastien Villemot wrote: > > > Please schedule a transition for suitesparse 7, which currently sits in > > > experimental. > > > > Please go ahead. > > Thanks for driving this transition so far. > > I have noticed the build failures of octave on 32-bit architectures > (that you reported in #1041460). > > Actually, it turns out that suitesparse 7 is partly broken on 32-bit > architectures. Contrarily to what I said previously, there is an ABI > change on 32-bit architectures. And due to the way that this ABI change > was performed, it had the unintended consequence of breaking libspqr3 > (provided by src:suitesparse) on 32-bit architectures. Upstream > realized this too late (and did not make much publicity around it, so I > was not aware of the issue before starting the transition). > > Upstream seems to be working on a fix, but at this point there is none > available. The only affected package seems to be octave, for which > there is a workaround (disabling libspqr use on 32-bit archs, which > implies that some functionalities won’t be available there). I hope > this situation is only temporary. Let's try this workaround until upstream has the fix ready. Cheers -- Sebastian Ramacher
Bug#1041227: transition: suitesparse
Le dimanche 16 juillet 2023 à 18:50 +0200, Sebastian Ramacher a écrit : > On 2023-07-15 23:25:28 +0200, Sébastien Villemot wrote: > > Please schedule a transition for suitesparse 7, which currently sits in > > experimental. > > Please go ahead. Thanks for driving this transition so far. I have noticed the build failures of octave on 32-bit architectures (that you reported in #1041460). Actually, it turns out that suitesparse 7 is partly broken on 32-bit architectures. Contrarily to what I said previously, there is an ABI change on 32-bit architectures. And due to the way that this ABI change was performed, it had the unintended consequence of breaking libspqr3 (provided by src:suitesparse) on 32-bit architectures. Upstream realized this too late (and did not make much publicity around it, so I was not aware of the issue before starting the transition). Upstream seems to be working on a fix, but at this point there is none available. The only affected package seems to be octave, for which there is a workaround (disabling libspqr use on 32-bit archs, which implies that some functionalities won’t be available there). I hope this situation is only temporary. There are two other reverse dependencies of libspqr (petsc and apbs) but so far they don’t seem to be affected (they probably are to some extent, but at least no FTBFS or autopkgtest failure in sight). Ideally I should have waited longer before starting this transition but it’s now too late (unless you think that the transition should be rolled back, though that seems a bit extreme given the limited extent of the breakage; in particular, 32-bit archs are probably not used that much for number crunching these days). -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org signature.asc Description: This is a digitally signed message part
Bug#1041227: transition: suitesparse
Le dimanche 16 juillet 2023 à 18:50 +0200, Sebastian Ramacher a écrit : > On 2023-07-15 23:25:28 +0200, Sébastien Villemot wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: transition > > X-Debbugs-Cc: suitespa...@packages.debian.org > > Control: affects -1 + src:suitesparse > > Control: forwarded -1 > > https://release.debian.org/transitions/html/auto-suitesparse.html > > Control: block -1 by 1041059 1037905 1037622 1040694 1041225 1037858 > > > > Dear Release Team, > > > > Please schedule a transition for suitesparse 7, which currently sits in > > experimental. > > Please go ahead. Thanks, it’s now uploaded and built on all release architectures. -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org signature.asc Description: This is a digitally signed message part
Bug#1041227: transition: suitesparse
Control: tags -1 confirmed On 2023-07-15 23:25:28 +0200, Sébastien Villemot wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > X-Debbugs-Cc: suitespa...@packages.debian.org > Control: affects -1 + src:suitesparse > Control: forwarded -1 > https://release.debian.org/transitions/html/auto-suitesparse.html > Control: block -1 by 1041059 1037905 1037622 1040694 1041225 1037858 > > Dear Release Team, > > Please schedule a transition for suitesparse 7, which currently sits in > experimental. Please go ahead. Cheers -- Sebastian Ramacher
Bug#1041227: transition: suitesparse
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: suitespa...@packages.debian.org Control: affects -1 + src:suitesparse Control: forwarded -1 https://release.debian.org/transitions/html/auto-suitesparse.html Control: block -1 by 1041059 1037905 1037622 1040694 1041225 1037858 Dear Release Team, Please schedule a transition for suitesparse 7, which currently sits in experimental. In this new major release, the SOVERSION of all libraries has been bumped, because some integer types part of the API have been redefined; however, this redefinition does not change anything on our release architectures. There are also a couple of other changes in headers that impact three reverse dependencies: libdogleg, siconos and octave. A fix is available for the three of them, and I stand ready to upload as needed. Four other reverse dependencies (yade, dolfin, openturns, sight) currently FTBFS for unrelated reasons. As a consequence, I could not verify that they build correctly against suitesparse 7 (but if they don’t, I’m fairly confident that they can be adapted). Thanks, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org
