There cannot be better model for illustrating a bad use of convention, since
such a convention could not be determined invariably as a convention.
**Proof-case**
Is assumed:
- a **non-null** _epoch_ value exits for an installed package
- user not aware of the exitence of a **non-null** _epoch_ value for an
installed package
- **non-null** _epoch_ values not reported by `rpm -q --qf %{evr} <package>`
nor any other mention reported
Then the very failure of reporting anything could not be determined either as a
consequence of a convention or as an issue.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2364#issuecomment-1403562269
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/2364/1403562...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint