https://bugzilla.redhat.com/show_bug.cgi?id=1324590 --- Comment #30 from Doug Ledford <dledford@xxxxxxxxxx> --- Yes, the %{?dist} tag must be part of the release. What this highlights is the fact that the release tag is Fedora, RHEL, and CentOS private. It is for the distro to track their build of your upstream version. It is *not* intended for upstream to *ever* use or set. You're entire versioning system is broken. I think it's best if we simply fork to a completely separate spec file for all Red Hat products. So here's what we need from you, and all we can accept from you: A tarball - It needs to have a public URL. And it needs to be static once released. We perform an md5sum check on the tarball when we download it, and then later on, when performing automated verification of sources as part of our security protocols, we compare that md5sum against a freshly downloaded and md5sumed tarball from your URL tag. If these ever don't match, we know we've caught something happening. For that reason, once you've released a tarball as, say, 10.1, it is fixed and permanent. If you need to make changes, you need a 10.2, or 10.1.1 or something else. You should not ever expect to have any say in what the release field is or looks like. That is specifically and solely up to the distro packager. If you happen to get a Fedora account and become a Fedora packager, then you can control the release field by editing the spec file in the Fedora repo, not by editing the release field in the tarball spec file. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/package-review@xxxxxxxxxxxxxxxxxxxxxxx