Actually I think that I understand now. It evaluated as ternary operator now.
Therefore the `%{?load:%{SOURCE4}} expression is now evaluated as `%{false ?
load : %{SOURCE4}}`.
Nevertheless, I don't understand why the previous functionality was removed.
The question mark was useful for backward
RPM and DNF have several differences in CLI and API. In long term it will be
nice to improve consistency between similar or related components. As an
example I can use handling of epoch. See `rpm -q dnf` and `dnf repoquery dnf`.
Also the output for `--queryformat="%{epoch}"` differs. DNF shows
I Initially submitted this bug at
[bugzilla.redhat.com](https://bugzilla.redhat.com/show_bug.cgi?id=1953372).
**Description of problem:**
On my Arch Linux (5.10.16-arch1-1) I cannot build a simple spec file (see
attachment at the bottom) depending the directory from which the package is
being
As the original author of repoquery (in the yum era), certain differences were
quite intentional.
For `--queryformat="%{epoch}" ` 0 vs none difference the issue is rpm showing
the *real* situation whereas createrepo turns a non-existent epoch to zero
making it impossible to differentiate.
> I'd love to hear real explanation first, because I think that the report you
> have made was misunderstood
@voxik for your above comment on our chat about my report here, I think it's
better to explain it here. Dees the real explanation mean @pmatilai 's answer
about why the RPM project
Panu, is it possible to reopen this ticket until we find a fix of a friction
between us?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Install4j has fixed the issue on version 9.0.2 and higher. But not a free
upgrade for many.
Software that uses the install4j installer often also includes a .sh download
that can be run with -q to run it without the UI.
--
You are receiving this because you are subscribed to this thread.
