'core2' dependency is now unmaintained and yanked from crates.io

[xanarin]

core2 is no longer supported and all of its published versions to crates.io have been yanked. It might be worth considering switching the dependency to core, as recommended in the core2 README.

core is still missing a lot of what is provided by core2/std::io, so an alternative no_std crate that provides an API similar to io will probably be required.

[LockedThread]

Temporarily you can patch it to the previous commit before the yank:

[patch.crates-io]
core2 = { git = "https://github.com/bbqsrc/core2", rev = "545e84bcb0f235b12e21351e0c69767958efe2a7" }

Validate the revision yourself at https://github.com/bbqsrc/core2/tree/545e84bcb0f235b12e21351e0c69767958efe2a7

[xanarin]

It seems like no_std_io might be an (almost) drop-in replacement, given that it's originally forked from core2, but still "officially" maintained.

[abraemer]

In my PR #86 I replaced core2 with no_std_io2 which is a fork of no_std_io

[xanarin]

Looks like no_std_io2 is more maintained than no_std_io; good choice

[LockedThread]

Related hackyderm thread.

https://hachyderm.io/@piecritic/116404790999620656

[sile]

Thank you for creating this issue.
I will review the PR within a week.

[sile]

I will start reviewing the PR soon.

BTW, I recently prefer to develop library crates with as few dependencies as possible (e.g., nojson, noargs).
So, I started developing noflate (a no-deps DEFLATE library) in the same spirit.
That said, using no_std_io2 seems a reasonable choice for this issue. As a long-term solution, switching to noflate might be one option worth considering, though it is not API-compatible with libflate.

[sile]

Merged the PR and published libflate v2.3.0.
This was an unfortunate situation, so thank you very much for reporting it and helping address it.