Bug 1467997 - upgrade liberasurecode and pyeclib libraries to 1.5.0
Summary: upgrade liberasurecode and pyeclib libraries to 1.5.0
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: liberasurecode
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: beta
: 12.0 (Pike)
Assignee: Jon Schlueter
QA Contact: Mike Abrams
URL:
Whiteboard:
Depends On: 1468002
Blocks: 1518834
TreeView+ depends on / blocked
 
Reported: 2017-07-05 18:23 UTC by Thiago da Silva
Modified: 2023-09-14 04:00 UTC (History)
7 users (show)

Fixed In Version: liberasurecode-1.5.0-1.el7ost python-pyeclib-1.5.0-1.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1468002 1518834 (view as bug list)
Environment:
Last Closed: 2017-12-13 21:39:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Description Thiago da Silva 2017-07-05 18:23:10 UTC
new liberasurecode and pyeclib rpms should be built and included in Pike. Release 1.5.0 was released last week:

liberasurecode: https://github.com/openstack/liberasurecode/releases/tag/1.5.0

pyeclib: https://github.com/openstack/pyeclib/releases/tag/1.5.0

Comment 1 Jon Schlueter 2017-07-05 20:41:40 UTC
RDO bug for rebase filed and being worked on.  Once builds are in RDO these will make their way into OSP 12

Comment 2 Pete Zaitcev 2017-07-06 01:15:06 UTC
Well, good luck with that. So far, I hit a couple of problems:

- Cannot build 1.5.0 on a system that already has 1.4.0 installed. It will then include system headers sometimes and pull the wrong version.

- Koji blows up with
/builddir/build/BUILD/liberasurecode-1.5.0/test/.libs/lt-liberasurecode_test: error while loading shared libraries: liberasurecode.so.1: cannot open shared object file: No such file or directory

Of course you can just disable the %check step, but generally 1.5.0
seems like rife with regressions. At least we don't yet have the CRC32
debacle in.

Comment 10 errata-xmlrpc 2017-12-13 21:39:17 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:3462

Comment 12 Red Hat Bugzilla 2023-09-14 04:00:40 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.