Project

General

Profile

Actions

Bug #42303

closed

ceph-14.2.4-0.el7.src.rpm Build rpm error

Added by Jiang Yu over 4 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
build
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Hello everyone,
When I build rpm, there is a dependency problem.

Build step:
[root@community-ceph-1 ~]# rpmbuild -ba ~/rpmbuild/SPECS/ceph.spec
error: Failed build dependencies:
python3-Cython is needed by ceph-2:14.2.3-0.el7.x86_64

[root@community-ceph-1 ~]# rpm -qa | grep ceph
python-cephfs-14.2.4-0.el7.x86_64
ceph-radosgw-14.2.4-0.el7.x86_64
ceph-mgr-diskprediction-local-14.2.4-0.el7.noarch
ceph-mds-14.2.4-0.el7.x86_64
python-ceph-argparse-14.2.4-0.el7.x86_64
libcephfs2-14.2.4-0.el7.x86_64
ceph-common-14.2.4-0.el7.x86_64
ceph-selinux-14.2.4-0.el7.x86_64
ceph-osd-14.2.4-0.el7.x86_64
ceph-mgr-14.2.4-0.el7.x86_64
ceph-mgr-dashboard-14.2.4-0.el7.noarch
ceph-14.2.4-0.el7.x86_64
ceph-base-14.2.4-0.el7.x86_64
ceph-mon-14.2.4-0.el7.x86_64
ceph-grafana-dashboards-14.2.4-0.el7.noarch

Question:
Why does he rely on ceph-2: 14.2.3-0.el7.x86_64 instead of ceph-14.2.4-0.el7.x86_64

Actions #1

Updated by Jiang Yu over 4 years ago

system info:
[root@community-ceph-1 ~]# cat /etc/redhat-release
CentOS Linux release 7.6.1810 (Core)
[root@community-ceph-1 ~]# uname -a
Linux community-ceph-1.novalocal 3.10.0-957.el7.x86_64 #1 SMP Thu Nov 8 23:39:32 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
[root@community-ceph-1 ~]# pip list | grep Cython
Cython 0.29.13

Actions #2

Updated by Brad Hubbard over 4 years ago

  • Assignee set to Brad Hubbard

This is fixed by https://github.com/ceph/ceph/commit/3b15a62ffb211bd0901c80de94c966a4777d291f in the meantime you can just change the relevant line manually to get the build to work.

Question:
Why does he rely on ceph-2: 14.2.3-0.el7.x86_64 instead of ceph-14.2.4-0.el7.x86_64

Not sure, I see this.

# rpmbuild -ba SPECS/ceph.spec                                                                                                                                                                                   
error: Failed build dependencies:
        python3-Cython is needed by ceph-2:14.2.4-0.el7.x86_64

What does the following return?

# rpm --eval %dump --specfile SPECS/ceph.spec 2>&1|grep 14.2.3
Actions #3

Updated by Brad Hubbard over 4 years ago

  • Status changed from New to 15
Actions #4

Updated by Brad Hubbard over 4 years ago

  • Status changed from 15 to Need More Info
Actions #5

Updated by Jiang Yu over 4 years ago

Brad Hubbard wrote:

This is fixed by https://github.com/ceph/ceph/commit/3b15a62ffb211bd0901c80de94c966a4777d291f in the meantime you can just change the relevant line manually to get the build to work.

Question:
Why does he rely on ceph-2: 14.2.3-0.el7.x86_64 instead of ceph-14.2.4-0.el7.x86_64

Not sure, I see this.

[...]

What does the following return?

[...]

I think it is because some packages of centos7.6 have been updated. My same operation is no problem on centos7.4.

Can the Ceph community test it based on different operating system versions?

Actions #6

Updated by Brad Hubbard over 4 years ago

Jiang Yu wrote:

Brad Hubbard wrote:

This is fixed by https://github.com/ceph/ceph/commit/3b15a62ffb211bd0901c80de94c966a4777d291f in the meantime you can just change the relevant line manually to get the build to work.

Question:
Why does he rely on ceph-2: 14.2.3-0.el7.x86_64 instead of ceph-14.2.4-0.el7.x86_64

Not sure, I see this.

[...]

What does the following return?

[...]

I think it is because some packages of centos7.6 have been updated. My same operation is no problem on centos7.4.

Can the Ceph community test it based on different operating system versions?

I used 7.6.1810, exactly the same release as you so it is something in your environment. The most likely explanation is there is some artefact of a previous build left over. Try running rpmdev-wipetree to clean the environment and then install the source rpm again and retry the build.

Actions #7

Updated by Jiang Yu over 2 years ago

The problem has been resolved, I think it can be closed.

Actions #8

Updated by Brad Hubbard over 2 years ago

  • Status changed from Need More Info to Closed

Thanks for the update.

Actions

Also available in: Atom PDF