https://bugzilla.redhat.com/show_bug.cgi?id=2221356
--- Comment #7 from Petr Menšík <[email protected]> --- Adding at least test list is a good idea! Spec URL: https://gitlab.isc.org/pemensik/DNS-Compliance-Testing/-/raw/fedora/packaging/rpm/DNS-Compliance-Testing.spec SRPM URL: https://pemensik.fedorapeople.org/srpm/DNS-Compliance-Testing-0%5e20230708git4aea40b-1.fc39.src.rpm But fixing warnings emitted by compilation should not block review. I have pushed a) MR: https://gitlab.isc.org/isc-projects/DNS-Compliance-Testing/-/merge_requests/19 But that should be optional. Fixing b) would take more time, when there is Patch1 required to even compile on recent distribution. Yes, the source code is not in a perfect shape, but still I don't know about any other equivalent, which would be better maintained. I think having working package is better than nothing at all, even if it emits warnings during compilation. I think that should be addressed at upstream eventually. As should be a request to create proper release, so it does not need a git snapshot. Are there any other issues blocking review pass? -- You are receiving this mail because: You are always notified about changes to this product and component You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2221356 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202221356%23c7 _______________________________________________ package-review mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
