This crate is unmaintained

[Pr0methean]

In accordance with https://github.com/rustsec/advisory-db/blob/main/HOWTO_UNMAINTAINED.md, please create an advisory to indicate that this crate is unmaintained. If this isn't done by 2024-07-16 and I don't see any maintenance activity by then, I will create it myself. Affected users should upgrade to https://crates.io/crates/zip_next.

[a1phyr]

Hi @Plecra ! If you need help maintaining this crate, I can give a hand from time to time.

[Plecra]

zip-next looks healthy, and I'm in no hurry to revive this crate if @Pr0methean is going to be able to keep it going 😁. In its current state, zip should get unmaintained status.

Before that though - do you want to move the zip-next implementation over to the zip name? My health is only getting worse and I don't know when I'll be in a state to return to it. (I appreciate your offer a1phyr, but your effort might be better directed towards zip-next haha)

[Pr0methean]

Sure, I'd be glad to take over the `zip` name and make `zip-next` a re-export.

…

On Thu, Apr 18, 2024, 06:12 Plecra ***@***.***> wrote: zip-next looks healthy, and I'm in no hurry to revive this crate if @Pr0methean <https://github.com/Pr0methean> is going to be able to keep it going 😁. In its current state, zip should get unmaintained status. Before that though - do you want to move the zip-next implementation over to the zip name? My health is only getting worse and I don't know when I'll be in a state to return to it. (I appreciate your offer a1phyr, but your effort might be better directed towards zip-next haha) — Reply to this email directly, view it on GitHub <#446 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABF3NBPWYDPRFF6WWPTOTR3Y57BERAVCNFSM6AAAAABGMQOOMOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRTHAZTOMZYHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Pr0methean]

@Plecra Have you added me as an owner to zip? If so, I'll publish zip-next under the name zip within 24 hours, then make zip-next a wrapper and PR the RustSec advisory about zip-next within 24 hours of that. I believe the command to add me will be cargo owner --add Pr0methean, based on the following:

hennickc@f8ffc25e7f6e zip-next % cargo owner --list zip
    Updating crates.io index
mvdnes (Mathijs van de Nes)
Plecra
hennickc@f8ffc25e7f6e zip-next % cargo owner --list zip-next 
    Updating crates.io index
Pr0methean (Chris Hennick)

[Plecra]

That should be done now :)

[Pr0methean]

Published as zip, made zip_next a wrapper, and opened rustsec/advisory-db#1949 to advise of the name change.

[Pr0methean]

@Plecra May I please be an admin on this repo, so I can close issues and PRs that are addressed in mine, and archive it once none remain?

[djc]

I definitely got confused by having two seemingly active repos -- would be nice to get this archived. Maybe it makes sense to move Pr0methean/zip into zip-rs and rename this as zip-rs/zip-old?

[Plecra]

I'll leave that up to @Pr0methean

[Pr0methean]

Renaming the new repo to zip-rs/zip would cause old issue and PR links to point to the wrong item. But I'll rename this repo to zip-old once @Plecra makes me an admin.

I also agree that this repo should be archived eventually, but I'd like to at least triage the open issues and PRs first, copy over the ones that are still valid, and close them (another reason I'll need to be a repo admin). If the repo is archived with open issues and PRs, they'll become stuck open.

[RouHim]

Smells like xz, just kidding ;)