Closed #572.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/572#event-2281818977___
Rpm-maint mailing list
Rpm-maint@lists.rpm
I think this has been long enough in waiting-for-info state. Closing.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/572#issuecomment-483968638___
@nim-nim , a reproducer is not a link to some random site somewhere, like
@jasontibbitts notes we're not going to chase around stuff like that. Provide a
minimal reproducer in this ticket if you want this to be looked at.
--
You are receiving this because you are subscribed to this thread.
Repl
It would be far more useful if you could simply provide a few short specfiles
which illustrate the problem you are having. I don't think you can reasonably
expect the upstream RPM developers (or anyone else, really) to dig through that
copr URL to try and figure out what in there might actually
You have 3 reproducers in
https://copr.fedorainfracloud.org/coprs/nim/rpm.572/builds/
The problem test is on line 80 of the macros.fonts file shipped in
fonts-rpm-macros built as part of fontpackages.
copr logs are not interesting, the fact rpmbuild -bs fails makes copr
completely blow up. copr
If you want us to look stuff like this, provide an actual reproducer. There are
so many subtle details that a textual description doesn't even begin to cover
them.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://git
RPM version 4.14.2
rpmbuild has a safety feature where it checks if Name/Summary/Source0 is
defined while processing a spec. Unfortunately, the check is not placed
correctly in the control flow.
So if you have a rpm macro that does something like:
```specfile
%{lua:
-- If %{name} does not exi