Project

General

Profile

Actions

Bug #44964

closed

RPM 4.15.1 has some issues with ceph.spec

Added by Nathan Cutler about 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
% Done:

0%

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

Description

We recently started building ceph with RPM 4.15.1 and this has uncovered some minor issues:

[   50s] + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --nosignature --define '_build_create_debug 1' --define 'disturl obs://build.opensuse.org/filesystems:ceph:octopus:upstream/openSUSE_Tumbleweed/1064c1c198eb419ac208179797f1baf0-ceph' /home/abuild/rpmbuild/SOURCES/ceph.spec
[   50s] warning: line 939: It's not recommended to have unversioned Obsoletes: Obsoletes:    libcephfs1
[   51s] warning: extra tokens at the end of %endif directive in line 2329:  %endif # with selinux

Though these are warnings only, they cause the build to fail in the OBS, so they still need to be fixed.


Related issues 2 (0 open2 closed)

Copied to Ceph - Backport #45034: octopus: RPM 4.15.1 has some issues with ceph.spec ResolvedNathan CutlerActions
Copied to Ceph - Backport #45035: nautilus: RPM 4.15.1 has some issues with ceph.spec ResolvedNathan CutlerActions
Actions #1

Updated by Nathan Cutler about 4 years ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 34427
Actions #2

Updated by Kefu Chai about 4 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #3

Updated by Nathan Cutler about 4 years ago

  • Copied to Backport #45034: octopus: RPM 4.15.1 has some issues with ceph.spec added
Actions #4

Updated by Nathan Cutler about 4 years ago

  • Copied to Backport #45035: nautilus: RPM 4.15.1 has some issues with ceph.spec added
Actions #5

Updated by Nathan Cutler about 4 years ago

  • Description updated (diff)
Actions #6

Updated by Nathan Cutler about 4 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Actions

Also available in: Atom PDF