https://bugzilla.redhat.com/show_bug.cgi?id=1806219 --- Comment #4 from Nikola Forró <nforro@xxxxxxxxxx> --- > This spec file was generated with go2rpm. I'm aware, but that doesn't make any of my points invalid. In fact, go2rpm on my end generates: "Release: 1%{?dist}" > However, I found interesting the fact that we already have a ccat. > I need to see how to procedure in this case. You can rename the binary, or you can convince ccrypt to rename theirs (perhaps they would be ok with it, since AFAICS ccat is just a convenience alias to ccrypt --cat). I don't think there is any other option, as ccat from ccrypt has a completely different purpose, so you can't use alternatives or similar mechanism to deal with the conflict. -- 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 To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx
