https://bugzilla.redhat.com/show_bug.cgi?id=2519638
--- Comment #6 from Ben Beasley <[email protected]> --- Thank you for the review! > I do not know whether a change like this would be acceptable for upstream, > but this is *how* you *could* fix this issue upstream. I have had some success getting changes like this merged upstream, https://github.com/unicode-org/icu4x/pull/5537, but there is some nuance with how this interacts with their publication process and limitations in cargo itself, with a full discussion in https://github.com/unicode-org/icu4x/issues/7196. While simple cases like this one could probably be “fixed” straightforwardly upstream, there are enough traps and intractable cases around that I’ve generally stopped trying to fix “missing” dev-dependencies in ICU4X crates. -- 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=2519638 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202519638%23c6 -- _______________________________________________ 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://forge.fedoraproject.org/infra/tickets/issues/new
