https://bugzilla.redhat.com/show_bug.cgi?id=2305930
Cristian Le <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Cristian Le <[email protected]> --- Not in the packaging guidelines, but please make sure there is a communication channel with upstream. I believe in this case it is your own fork, so consider opening issues. Some other notes: - name os the spec file/srpm should be python-btrfs-backup-ng - testing wise, understandibly this can be quite tricky, but maybe with `tmt` and `testing-farm` it would be possible to provision test environments with empty disk and then prepare the btrfs disk to do functional tests. Would be quite a task, not going to sugarcoat it. - are the Requires field sufficient? Don't you need a dependency on what provides `btrfs`? -- 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=2305930 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202305930%23c2 -- _______________________________________________ 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
