ffmpeg-sys vs ffmpeg-sys-next

[soloturn]

Problem

if one owner archives his repo which produces ffmpeg-sys, another one can produce ffmpeg-sys-next. new owner cannot continue to produce ffmpeg-sys?

Steps

No response

Possible Solution(s)

No response

Notes

No response

Version

No response

[weihanglo]

What did you mean by produce? Could you clarify the question?

[soloturn]

produce means put a binary here:
https://crates.io/crates/ffmpeg-sys

old owner left it. fork meant a renaming of the crate.

[weihanglo]

If I understand correctly, you want to "publish" new version of ffmpeg-sys to crates.io. That means you need to either have the publish permission or take over the ownership of https://crates.io/crates/ffmpeg-sys. Per crates.io's policy, you'll need to contact the author by yourself or ask crates.io team for help with that if they haven't replied for a long while.

The alternative solution is using [patch], though it has a limitation that you cannot patch a crates.io dependency over the other also from crates.io. You might want to subscribe this issue #9227.

Close as ownership of crates is controlled by crates.io team and services, not Cargo the tool.