"evr" is a defined strategy for creating a string summarizing a package's
critical details as a string, which the user can query. `(none)` is just a
special value the `rpm` cli uses to represent the nonexistence of a tag. I
would not expect an EVR to ever look like `(none):4.18.0-1.fc37`, that would be
leaking details about how information is displayed in the CLI backwards into
the tag query mechanism.
In other words, when you query the "evr" you're not querying the epoch, version
and release and asking the CLI to display them. You're asking the CLI to
display the "evr" value as generated by `rpm`. And there is no reason for that
to ever contain `(none)`.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2364#issuecomment-1409469650
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/2364/1409469...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
