[Bug 1159131] New: icu: follow upstream soname again?
http://bugzilla.suse.com/show_bug.cgi?id=1159131 Bug ID: 1159131 Summary: icu: follow upstream soname again? Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: jengelh@inai.de Reporter: lnussel@suse.com QA Contact: qa-bugs@suse.de CC: qzhao@suse.com Found By: --- Blocker: --- according to bug 824262 from 2013 icu was switched to a custom soname as upstream was not considered reliable enough to get it right. Looks like meanwhile it's safe when they release a .something version: https://abi-laboratory.pro/?view=timeline&l=icu4c So can we go back to using the upstream soname? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1159131 http://bugzilla.suse.com/show_bug.cgi?id=1159131#c1 --- Comment #1 from Jan Engelhardt <jengelh@inai.de> --- You make a case for icu-versioning.diff, but not icu-susevers.diff, which still requires a custom SONAME. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1159131 http://bugzilla.suse.com/show_bug.cgi?id=1159131#c2 --- Comment #2 from Ludwig Nussel <lnussel@suse.com> --- yes I considered filing a separate bug for the utf8 issue but got distracted. Any chance to get upstream to change the behavior there? Forcing UTF8 even if the locale says different doesn't seem correct either. If not, maybe put utf8 in the name of the lib rather than suse? Don't want to imply suse modifications requiring that change. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1159131 http://bugzilla.suse.com/show_bug.cgi?id=1159131#c3 --- Comment #3 from Jan Engelhardt <jengelh@inai.de> ---
maybe put utf8 in the name of the lib
That brings no improvement to my table. Unlike the ICU hack we are doing here, wxWidgets for example has around 300 *official* configure switches that influence the ABI, and no one is suggesting they encode those choices into the filename. It would become ridicolously long. So no one does that. There is still the matter that different vendors produce different ABIs, so it seems natural to use a tag that includes the vendor's name. Such is reasonably unique and is not going to get used willingly by another vendor. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1159131 http://bugzilla.suse.com/show_bug.cgi?id=1159131#c4 --- Comment #4 from Ludwig Nussel <lnussel@suse.com> --- looks like in wxwidgets that is expected and it has a vendor switch. Still ugly IMO but seems the way it's made. In ICU OTOH those soname changes on ICU are downstream hacks. I'm not sure the whole thing is a good idea anymore. Looks like the change to UTF was very intentional: https://sourceforge.net/p/icu/mailman/message/36171327/ https://unicode-org.atlassian.net/browse/ICU-13519 https://bugs.chromium.org/p/chromium/issues/detail?id=772655#c12 So there are actually programs that may crash in non-UTF8 and I don't think we actually support or test that mode in any way anymore. Catering for this one guy who insists in latin for whatever reason seems questionable. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1159131 http://bugzilla.suse.com/show_bug.cgi?id=1159131#c5 --- Comment #5 from Ludwig Nussel <lnussel@suse.com> --- btw, the only binary incompatibility between utf8 and non utf8 versions seem to be the removal of uprv_getDefaultCodepage(). Not sure if that is meant to be a private function though. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1159131 Jan Engelhardt <jengelh@inai.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lopa@mailbox.org -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1159131 http://bugzilla.suse.com/show_bug.cgi?id=1159131#c7 --- Comment #7 from Swamp Workflow Management <swamp@suse.de> --- This is an autogenerated message for OBS integration: This bug (1159131) was mentioned in https://build.opensuse.org/request/show/785383 Factory / icu -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1159131 https://bugzilla.suse.com/show_bug.cgi?id=1159131#c15 --- Comment #15 from Swamp Workflow Management <swamp@suse.de> --- openSUSE-SU-2021:4063-1: An update that contains security fixes and contains one feature can now be installed. Category: security (important) Bug References: 1158955,1159131,1161007,1162882,1167603,1182252,1182645 CVE References: JIRA References: SLE-17893 Sources used: openSUSE Leap 15.3 (src): icu.691-69.1-7.3.2 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1159131 https://bugzilla.suse.com/show_bug.cgi?id=1159131#c16 --- Comment #16 from Swamp Workflow Management <swamp@suse.de> --- SUSE-SU-2021:4063-1: An update that contains security fixes and contains one feature can now be installed. Category: security (important) Bug References: 1158955,1159131,1161007,1162882,1167603,1182252,1182645 CVE References: JIRA References: SLE-17893 Sources used: SUSE Linux Enterprise Module for Basesystem 15-SP3 (src): icu.691-69.1-7.3.2 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.
participants (2)
-
bugzilla_noreply＠novell.com -
bugzilla_noreply＠suse.com