https://bugzilla.redhat.com/show_bug.cgi?id=2283309 --- Comment #3 from Ben Beasley <code@xxxxxxxxxxxxxxxxxx> --- (In reply to Ben Beasley from comment #2) > This is reasonable (there are no tests that can run without snapbox, and the > tests use APIs introduced in snapbox 0.5), but please try to remember to > re-enable the tests when snapbox is updated. The tests can run with the > current release of snapbox by only loosening the version bound (no code > changes > required). I just noticed that this blocks bug 2263408 for updating snapbox, and that this appears to be a test dependency for the snapbox crate. If there is a circular dependency with snapbox, then keeping the tests disabled in this crate to avoid bootstrapping would be justifiable, but the comment should probably be amended to say so. -- 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=2283309 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202283309%23c3 -- _______________________________________________ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
