Project

General

Profile

Actions

Bug #5346

open

osmo-release.sh doesn't work with %{sover} macro in spec.in

Added by laforge about 2 years ago. Updated about 2 years ago.

Status:
New
Priority:
Low
Assignee:
Category:
-
Target version:
-
Start date:
12/09/2021
Due date:
% Done:

0%

Spec Reference:

Description

When trying to release a new version of osmo-remsim, I run into the following error:

 make REL=major release               415/0/0
Releasing 0.2.2.126-7382 -> 1.0.0...
OK: dependency specific versions in configure.ac and debian/control match
OK: dependency specific versions in configure.ac and contrib/*.spec.in match
OK: Found matching debian/lib*2.install for LIBVERSION=2:0:0
OK: Found 'Package: lib*2' in debian/control for LIBVERSION=2:0:0
ERROR: Found no matching '%files -n lib*2' in contrib/*.spec.in for LIBVERSION=2:0:0
make: *** [osmo-release.mk:9: release] Error 1

this seems to relate to the spec.in file using a %{sover} macro. This seems to be the case ever since this spec file was introduced to osmo-remsim, so I suppose the check in osmo-release.sh is more recent and didn't consider this situation?

Actions #1

Updated by laforge about 2 years ago

  • Priority changed from Normal to Low

ALLOW_NO_LIBVERSION_RPM_MATCH can be used as workaround, reducing priority.

Actions #2

Updated by pespin about 2 years ago

I was indeed not aware of such %{sover} when I wrote the support to validate RPM spec files.
I guess I'd have to check if %{sover} is used and in that case print a WARN or similar, and continue execution.

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)