https://bugzilla.redhat.com/show_bug.cgi?id=2282430
--- Comment #25 from Sandro <[email protected]> --- (In reply to Sandro from comment #23) > > - I would have added a spec-file comment explaining how the downstream > > keycert.pem file was generated, but this isn’t mandatory. > > That sounds like a good idea and I should have done that right from the > start. Now I will need to scratch my head hard and dig around my browser's > history to figure out what the issue was exactly and what guide / hint I > followed to solve it. I'll try... It turns out this is no longer required. Upstream shipped a re-generated cert in 1.5.10: https://github.com/giampaolo/pyftpdlib/commit/99b055b6e9fcfffccb1e4e7c71cef0ca96f37c3e Thanks for making me poke around and discover that. ;) -- 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=2282430 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202282430%23c25 -- _______________________________________________ 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
