Bug 1528975 - Fedora 28 (Rawhide) renamed the pyxattr package to python2-pyxattr
Summary: Fedora 28 (Rawhide) renamed the pyxattr package to python2-pyxattr
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: packaging
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-25 13:34 UTC by Niels de Vos
Modified: 2018-03-15 11:24 UTC (History)
2 users (show)

Fixed In Version: glusterfs-4.0.0
Clone Of:
Environment:
Last Closed: 2018-03-15 11:24:00 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Niels de Vos 2017-12-25 13:34:17 UTC
Emails sent to the glusterfs-owner alias:

glusterfs has broken dependencies in the rawhide tree:
On x86_64:
    glusterfs-server-3.13.1-1.fc28.x86_64 requires pyxattr
On armhfp:
    glusterfs-server-3.13.1-1.fc28.armv7hl requires pyxattr
On ppc64le:
    glusterfs-server-3.13.1-1.fc28.ppc64le requires pyxattr
On aarch64:
    glusterfs-server-3.13.1-1.fc28.aarch64 requires pyxattr
On ppc64:
    glusterfs-server-3.13.1-1.fc28.ppc64 requires pyxattr
On s390x:
    glusterfs-server-3.13.1-1.fc28.s390x requires pyxattr
On i386:
    glusterfs-server-3.13.1-1.fc28.i686 requires pyxattr
Please resolve this as soon as possible.

Comment 1 Worker Ant 2017-12-25 13:42:53 UTC
REVIEW: https://review.gluster.org/19074 (rpm: Fedora 28 has renamed pyxattr) posted (#1) for review on master by Niels de Vos

Comment 2 Worker Ant 2017-12-26 12:19:48 UTC
COMMIT: https://review.gluster.org/19074 committed in master by \"Niels de Vos\" <ndevos> with a commit message- rpm: Fedora 28 has renamed pyxattr

Change-Id: Ifa60b394986b9c107792a7c2a4baa335d44dc6f7
BUG: 1528975
Signed-off-by: Niels de Vos <ndevos>

Comment 3 Bruce Jerrick 2017-12-27 21:08:50 UTC
Same problem with yum-3.4.3-515.fc28.noarch -- see RHBZ#1529361 .

Comment 4 Shyamsundar 2018-03-15 11:24:00 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-4.0.0, please open a new bug report.

glusterfs-4.0.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-March/000092.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.