On 2024-11-15 15:15:35 +0100, Alban Browaeys wrote: > Le mardi 12 novembre 2024 à 15:48 +0100, Vincent Lefevre a écrit : > > Hi, > > > > On 2024-10-11 09:16:26 +0200, Alban Browaeys wrote: > > > Upstream in https://github.com/libunwind/libunwind/issues/672 for > > > 1.8. > > > > This is unclear. https://github.com/libunwind/libunwind/issues/672 is > > about 1.7.2, and this issue is closed as being fixed in 1.8. > > > > > It is fixed > in > https://github.com/libunwind/libunwind/commit/f35c38746d47a5159163ca9e8845a3ac8cf1bc53 > that is 1.8.1.
This was fixed in 1.8.0: "Marking this as completed since the build problems have been fixed in release 1.8.0." The bug was in 1.7.2 (and before), not in 1.8.0. > As told in the issue the bug is about newer compiler, not a code > change. So every release below 1.8.1 is affected. No, below 1.8.0. > And the current broken debian version is 1.7.2, so I am puzzled by your > statement that the fix on this github issue is about 1.7.2 so does not > apply to Debian. I did not say that this does not apply to Debian. > To me this is perfectly normal that an issue for 1.7.2 is fixed in > 1.8.1, I don't understand why you tell "This is unclear". Because you said that the issue was present in 1.8. > Upgrading to 1.8.1 would fix this bug. If it is doable let's do it. But > it might requires a migration of the packages that depends on > libunwind-18 (would it be libunwind-19) so I it might not help with > these packages depending on libunwind-18. Well, if the ABI is compatible, there is no need to rename the package. And according to the git log, no incompatibilities have been introduced. There was a soname change here: https://github.com/libunwind/libunwind/commit/108a02365df010292c582093128c305fd40641af but with AGE increased, so this is OK. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
