|
Bugzilla – Full Text Bug Listing |
| Summary: | libicu53_1 should be available for Leap as was for 13.2 | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Martin Koller <kollix> |
| Component: | Basesystem | Assignee: | Dirk Mueller <dmueller> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | jengelh, maint-coord, qantas94heavy |
| Version: | Leap 42.1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Martin Koller
2016-01-05 16:05:02 UTC
How do you want to add this to Leap? >When I want to install the package also for the newer Leap 42.1 I can't do so since Leap only has the older libicu52_1.
You have to rebuild the software in any case, since any particular distribution and version thereof can have different ABIs of ICU. Tumbleweed for example has "56_1", Debian "56".
With an instance of Open Build Service, once set up, you can easily build for different distributions and versions.
(In reply to Dirk Mueller from comment #2) > How do you want to add this to Leap? Preferably it's available in one of the default repositories, so a customer of our software would just have to install Leap, then zypper install our_software.rpm In other openSuse distributions there were e.g. compat* packages for older libstdc++ etc. libs. Having something like this would be great. (In reply to Jan Engelhardt from comment #3) > >When I want to install the package also for the newer Leap 42.1 I can't do so since Leap only has the older libicu52_1. > > You have to rebuild the software in any case, since any particular > distribution and version thereof can have different ABIs of ICU. Tumbleweed > for example has "56_1", Debian "56". > > With an instance of Open Build Service, once set up, you can easily build > for different distributions and versions. of course we could build the software for a multitude of Linux distributions, however you can imagine how much effort that would be (don't forget testing, patching, support, documentation, ...) So we try to stick with currently 2 different distributions: RHEL and openSuse Since our release cycle is not aligned with any of these, we have now the situation that we built the latest version with the latest openSuse at this point in time, but now even the download of an openSuse 13.2 ISO is very well hidden (you can't find it!), which is very sad! I was really hoping that software developed and built for 13.2 would install without hassle with the next version. >I was really hoping that software developed and built for 13.2 would install without hassle with the next version.
Binary compatibility is in the hands of upstream. glibc libc.so.6, libGL.so.1, libX11.so.6, you name it. But not everyone does their job.
I think its not an unreasonable request to have a distribution be backward compatible to some extend to previous releases. >I think its not an unreasonable request to have a distribution be backward compatible to some extend to previous releases.
Though possible, problems with having two different library versions in the program address space (can happen if you link to an "old" libX and a "still-fresh" libY that is linked against a "new" libX) are well described.
It gets worse. On Debian 9, libraries even retained their SONAME, but an "old" program (D7/D8) passing a struct{std::string} to libX which passes the string to libY which plays with it, crashes (because std::string changed).
That latter may be an isolated case, but it shows just how bad things can turn.
(In reply to Martin Koller from comment #0) > Our (commercial) software is built for openSuse 13.2, which uses libicu53_1. > When I want to install the package also for the newer Leap 42.1 I can't do > so since Leap only has the older libicu52_1. > It would really be helpful to at least have the one which is in the older > openSuse version available also for Leap Even though Leap 42.1 was released after 13.2, some packages are older in Leap (it's based on SLE-12 code stream, which is older than 13.2). If your software can be built against icu52, I suggest to create builds specifically for Leap 42.1 instead of using the same packages for 13.2. If it really needs features from icu53, you could create a compat-icu53 package and submit it to Factory. From there it could be then added to Leap. The package name would be "icu-53", not compat-icu53. However, if there is anything wanting a newer ICU, we would just submit the TW version into Leap, alleviating the need for a separate icu-53 package. There won't be any more releases in the Leap 42.x series, so this won't be implemented. Leap 15 should provide a newer version of ICU. |