https://bugzilla.redhat.com/show_bug.cgi?id=2277389 Fabio Valentini <decathorpe@xxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|nobody@xxxxxxxxxxxxxxxxx |decathorpe@xxxxxxxxx Flags| |fedora-review? CC| |decathorpe@xxxxxxxxx --- Comment #3 from Fabio Valentini <decathorpe@xxxxxxxxx> --- I think I can solve the mystery about how something that's not in the git history ended up being published: The commit that was published to crates.io (according to .cargo_vcs_info.json) is e5550fd4a136c60ab41c3be81209dd5539aa392d, which is no longer part of the upstream git repo: https://github.com/SteadBytes/bisection/commit/e5550fd4a136c60ab41c3be81209dd5539aa392d It looks like the commit that's the current git HEAD was force-pushed *after* publishing to crates.io, so the commit that's associated with the 0.1.0 release on crates.io is no longer present in the commit history. While this isn't necessary a cause for skepticism, I would still be good to compare whether there's any meaningful divergence between what's published and what's now at git HEAD. -- 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=2277389 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202277389%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
