Description of problem: When building a package with bm, different steps are displayed. One of these is (at beginning): processing package vosk-model-small-ru-0.15-%mkrel 2 You can note that %mkrel 2 is not expanded This is minor, but this can conduct to think that something is wrong in the spec file using this macro. I presume the problem is in rpmbuild, not bm. Version-Release number of selected component (if applicable): rpm-build-4.16.1.3-1.1.mga8
(In reply to papoteur from comment #0) > Description of problem: > When building a package with bm, different steps are displayed. > One of these is (at beginning): > processing package vosk-model-small-ru-0.15-%mkrel 2 > > You can note that %mkrel 2 is not expanded > This is minor, but this can conduct to think that something is wrong in the > spec file using this macro. > > I presume the problem is in rpmbuild, not bm. > > > Version-Release number of selected component (if applicable): > rpm-build-4.16.1.3-1.1.mga8 Assigning to the rpm stack maintainers.
CC: (none) => marja11Source RPM: (none) => rpm-build-4.16.1.3-1.1.mga8Assignee: bugsquad => rpmstack
AFAIC This is not a bug in rpm-build but in bm. /usr/lib/python3.9/site-packages/BuildManager/package.py just manually parses the spec file in _package_spec() It should explicitly try to expand macros… Assigning according to http://sophie.zarb.org/rpms/b2cc908a66112494642edb8becb5079b/changelog
Source RPM: rpm-build-4.16.1.3-1.1.mga8 => bmCC: (none) => geiger.david68210, thierry.vignaudAssignee: rpmstack => bugsquad
Assigning to the current bm maintainer.
Assignee: bugsquad => geiger.david68210CC: (none) => ftg
It's not a packaging job. I take it.
Assignee: geiger.david68210 => yves.brungard_mageia
Summary: %mkrel 2 is not expanded in rpmbuild message => %mkrel 2 is not expanded in bm message
Created attachment 12985 [details] [Patch] for bm If %mkrel is seen in the release line, use rpm for evaluating it.