Bug 1582549 - api: missing __THROW on pub function decls
Summary: api: missing __THROW on pub function decls
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: libgfapi
Version: 4.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kaleb KEITHLEY
QA Contact: bugs@gluster.org
URL:
Whiteboard:
Depends On:
Blocks: glusterfs-4.1.0
TreeView+ depends on / blocked
 
Reported: 2018-05-25 14:33 UTC by Kaleb KEITHLEY
Modified: 2018-06-20 18:07 UTC (History)
1 user (show)

Fixed In Version: glusterfs-v4.1.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-20 18:07:14 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Kaleb KEITHLEY 2018-05-25 14:33:09 UTC
Description of problem:

missing __THROW on pub function decls needed for C++

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2018-05-25 14:38:38 UTC
REVIEW: https://review.gluster.org/20090 (api: missing __THROW on pub function decls) posted (#1) for review on release-4.1 by Kaleb KEITHLEY

Comment 2 Worker Ant 2018-05-29 14:39:29 UTC
COMMIT: https://review.gluster.org/20090 committed in release-4.1 by "Shyamsundar Ranganathan" <srangana> with a commit message- api: missing __THROW on pub function decls

missing __THROW on pub function decls needed for C++

Change-Id: Ia0ff09d311741e4cdc8ef171e07bbd56c24b9260
fixes: bz#1582549
Signed-off-by: Kaleb S. KEITHLEY <kkeithle>

Comment 3 Shyamsundar 2018-06-20 18:07:14 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-v4.1.0, please open a new bug report.

glusterfs-v4.1.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/announce/2018-June/000102.html
[2] https://www.gluster.org/pipermail/gluster-users/


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