+++ This bug was initially created as a clone of Bug #1536186 +++ Description of problem: See $Summary. Other Linux distributions are doing the same; some others already have. Switch to libtirpc(-devel) and unbundled rpcgen packages. For now rpcgen is still provided by the glibc-rpcgen RPM, but rpcsvc-proto's rpcgen subpackage is available now but will not be used until glibc-rpcgen is retired. (note, rpcsvc-proto's rpcgen is just named rpcgen-...rpm. I.e. not rpcsvc-proto-rpcgen.) Right now either one will satisfy the BuildRequires: rpcgen. Also, when a .spec file has BuildRequires: foo-devel it is not necessary to also have: BuildRequires: foo or even: BuildRequires: foo foo-devel The foo-devel package has a dependency on foo, which will install foo automatically. It's usually also not necessary to have a corresponding Requires: foo as the rpmbuild process will also automatically determine the install-time dependencies. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/19236 (build: glibc has removed rpc headers and rpcgen in Fedora28, use libtirpc) posted (#1) for review on release-3.13 by Kaleb KEITHLEY
Updated blocks 3.13.2 as we are handling this in the packaging and will get the fix into the code by 3.13.3.
COMMIT: https://review.gluster.org/19236 committed in release-3.13 by "Kaleb KEITHLEY" <kkeithle> with a commit message- build: glibc has removed rpc headers and rpcgen in Fedora28, use libtirpc Other Linux distributions are doing the same; some have already done so. Switch to libtirpc(-devel) and unbundled rpcgen packages. For now rpcgen is still provided by the glibc-rpcgen RPM, but rpcsvc-proto's rpcgen subpackage is available now; it will not be used until glibc-rpcgen is retired. (note, rpcsvc-proto's rpcgen is just named rpcgen-...rpm. I.e. not rpcsvc-proto-rpcgen-...rpm.) Either one will satisfy the BuildRequires: rpcgen. Also, when a .spec file has BuildRequires: foo-devel it is not necessary to also have: BuildRequires: foo or even: BuildRequires: foo foo-devel The foo-devel package has a dependency on foo, which will install foo automatically. It's usually also not necessary to have a corresponding Requires: foo as the rpmbuild process will also automatically determine the install-time dependencies. See also Change-Id: I4a8292de2eddad16137df5998334133fc1e11261 and/or https://review.gluster.org/19311 and Change-Id: I97dc39c7844f44c36fe210aa813480c219e1e415 and/or https://review.gluster.org/#/c/19330/ Change-Id: I86f847dfda0fef83e22c6e8b761342d652a2d9ba BUG: 1536187 Signed-off-by: Kaleb S. KEITHLEY <kkeithle>
This bug reported is against a version of Gluster that is no longer maintained (or has been EOL'd). See https://www.gluster.org/release-schedule/ for the versions currently maintained. As a result this bug is being closed. If the bug persists on a maintained version of gluster or against the mainline gluster repository, request that it be reopened and the Version field be marked appropriately.