Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Is this crate maintained? #197

Open
qtfkwk opened this issue Mar 13, 2024 · 4 comments
Open

Is this crate maintained? #197

qtfkwk opened this issue Mar 13, 2024 · 4 comments

Comments

@qtfkwk
Copy link

qtfkwk commented Mar 13, 2024 •
edited
Loading

If not, I believe that this repository and crate should either be transferred or a fork should replace it.

If you anyone is available, can you please respond with any preferences as to how you'd prefer this crate be treated?

Thanks!
@qtfkwk qtfkwk mentioned this issue Mar 13, 2024
Closed
@Ethiraric
Copy link

I have tried contacting the author on that matter on the 23rd of January but have not yet received a response.

I have also contacted crates.io (out of curiosity) to know whether this issue had already happen and if an action was taken. They will not transfer ownership of a crate without approval of the author (which is understandable), and they suggested development to be revived through a new crate (whether a fork or not) and that people should update their dependencies.

@qtfkwk
Copy link
Author

qtfkwk commented Mar 13, 2024

Hi @Ethiraric! Thanks for the quick response!

@davvid
Copy link

davvid commented Mar 20, 2024

Dupe of #160 and #192

@github-actions github-actions bot mentioned this issue Mar 25, 2024
Open
@nikarh nikarh mentioned this issue Mar 25, 2024
Closed
This was referenced Mar 25, 2024
Closed
Open
Closed
Open
Open
Open
Open
Open
Open
Open
Open
Open
Open
Closed
Open
Open
Open
Open
Closed
Open
Closed
Open
Open
Open
This was referenced Mar 27, 2024
Open
Open
Open
Open
Open
Closed
Open
Open
Open
Open
nazmulidris added a commit to r3bl-org/r3bl-open-core that referenced this issue Apr 15, 2024
@nazmulidris
[core, tui] Fix doc links errors, update Cargo.lock, update CHANGELOG.md
6222434 
`yaml-rust` crate is unmaintained

1) `syntect` author won't update this dep to a fork of it due to lack
of trust concerns with this new fork:
trishume/syntect#526

2) cargo-deny produces this output:

error[unmaintained]: yaml-rust is unmaintained.
    ┌─ /home/nazmul/github/r3bl-open-core/Cargo.lock:295:1
    │
295 │ yaml-rust 0.4.5 registry+https://github.com/rust-lang/crates.io-index
    │ --------------------------------------------------------------------- unmaintained advisory detected
    │
    = ID: RUSTSEC-2024-0320
    = Advisory: https://rustsec.org/advisories/RUSTSEC-2024-0320
    = The maintainer seems [unreachable](chyh1990/yaml-rust#197).

      Many issues and pull requests have been submitted over the years
      without any [response](chyh1990/yaml-rust#160).

      ## Alternatives

      Consider switching to the actively maintained `yaml-rust2` fork of the original project:

      - [yaml-rust2](https://github.com/Ethiraric/yaml-rust2)
      - [yaml-rust2 @ crates.io](https://crates.io/crates/yaml-rust2))
    = Announcement: rustsec/advisory-db#1921
    = Solution: No safe upgrade is available!
    = yaml-rust v0.4.5
      └── syntect v5.1.0
          └── r3bl_tui v0.5.2
              └── r3bl-cmdr v0.0.11
nazmulidris added a commit to r3bl-org/r3bl-open-core that referenced this issue Apr 15, 2024
@nazmulidris
[core, tui] Fix doc links errors, update Cargo.lock, update CHANGELOG.md
29ff8e8 
`yaml-rust` crate is unmaintained

1) `syntect` author won't update this dep to a fork of it due to lack
of trust concerns with this new fork:
trishume/syntect#526

2) cargo-deny produces this output:

error[unmaintained]: yaml-rust is unmaintained.
    ┌─ /home/nazmul/github/r3bl-open-core/Cargo.lock:295:1
    │
295 │ yaml-rust 0.4.5 registry+https://github.com/rust-lang/crates.io-index
    │ --------------------------------------------------------------------- unmaintained advisory detected
    │
    = ID: RUSTSEC-2024-0320
    = Advisory: https://rustsec.org/advisories/RUSTSEC-2024-0320
    = The maintainer seems [unreachable](chyh1990/yaml-rust#197).

      Many issues and pull requests have been submitted over the years
      without any [response](chyh1990/yaml-rust#160).

      ## Alternatives

      Consider switching to the actively maintained `yaml-rust2` fork of the original project:

      - [yaml-rust2](https://github.com/Ethiraric/yaml-rust2)
      - [yaml-rust2 @ crates.io](https://crates.io/crates/yaml-rust2))
    = Announcement: rustsec/advisory-db#1921
    = Solution: No safe upgrade is available!
    = yaml-rust v0.4.5
      └── syntect v5.1.0
          └── r3bl_tui v0.5.2
              └── r3bl-cmdr v0.0.11
@danielbcorreia danielbcorreia mentioned this issue Apr 16, 2024
Open
This was referenced Apr 24, 2024
Open
Open
This was referenced May 5, 2024
Open
Open
@github-actions github-actions bot mentioned this issue May 25, 2024
Open
tkmcmaster added a commit to FamilySearch/pewpew that referenced this issue Jun 3, 2024
@tkmcmaster
Updated yaml-rust to use yaml-rust2 due to deprecation
b9c4991 
- chyh1990/yaml-rust#197
- chyh1990/yaml-rust#160 (comment)
@tkmcmaster tkmcmaster mentioned this issue Jun 3, 2024
Merged
tkmcmaster added a commit to FamilySearch/pewpew that referenced this issue Jun 3, 2024
@tkmcmaster
Update Rust Dependencies 2024-05-29 (#226)
c716994 
* Moved deprecated .cargo/config to config.toml

* Ignore clippy warning

* Updated body_reader and channel dependencies

* Updated config-wasm and hdr-histogram dependencies

* Updated additional dependencies

- Held back hyper, http, and yansi due to major changes

* Updated Yansi to latest version

- Converted Paint::disable to Yansi::disable
- Removed Windows specific code. Yansi now will try to enable on Windows and automatically disables if it can't activate.

* Added build test-server to the PR script and workflow

* Fix dependency loop with ahash on itself

- tkaitchuck/aHash#95 (comment)
- rustwasm/wasm-bindgen#3031 (comment)

* Updated yaml-rust to use yaml-rust2 due to deprecation

- chyh1990/yaml-rust#197
- chyh1990/yaml-rust#160 (comment)

* Updated cargo deny to remove deprecated entries

- EmbarkStudios/cargo-deny#611
- https://embarkstudios.github.io/cargo-deny/checks/licenses/cfg.html#the-clarify-field-optional

* Updated cargo lock file

* Updated code for deprecations

- Added tests for create_date_diff, then updated deprecated calls and confirmed tests still passed

* Added clippy ignore large results and errors

* Fixed tests to validate to UTC

- Since the PR flow runs on UTC, updated the local PR script to also run UTC
- Updated the create_date_diff test to validate UTC and print a warning to run UTC if it fails
tkmcmaster added a commit to FamilySearch/pewpew that referenced this issue Jun 3, 2024
@tkmcmaster
Update Rust Dependencies 2024-05-29 (#226) (#229)
4e96359 
* Moved deprecated .cargo/config to config.toml

* Ignore clippy warning

* Updated body_reader and channel dependencies

* Updated config-wasm and hdr-histogram dependencies

* Updated additional dependencies

- Held back hyper, http, and yansi due to major changes

* Updated Yansi to latest version

- Converted Paint::disable to Yansi::disable
- Removed Windows specific code. Yansi now will try to enable on Windows and automatically disables if it can't activate.

* Added build test-server to the PR script and workflow

* Fix dependency loop with ahash on itself

- tkaitchuck/aHash#95 (comment)
- rustwasm/wasm-bindgen#3031 (comment)

* Updated yaml-rust to use yaml-rust2 due to deprecation

- chyh1990/yaml-rust#197
- chyh1990/yaml-rust#160 (comment)

* Updated cargo deny to remove deprecated entries

- EmbarkStudios/cargo-deny#611
- https://embarkstudios.github.io/cargo-deny/checks/licenses/cfg.html#the-clarify-field-optional

* Updated cargo lock file

* Updated code for deprecations

- Added tests for create_date_diff, then updated deprecated calls and confirmed tests still passed

* Added clippy ignore large results and errors

* Fixed tests to validate to UTC

- Since the PR flow runs on UTC, updated the local PR script to also run UTC
- Updated the create_date_diff test to validate UTC and print a warning to run UTC if it fails
This was referenced Jul 2, 2024
Open
Open
@github-actions github-actions bot mentioned this issue Jul 18, 2024
Open
@github-actions github-actions bot mentioned this issue Jul 27, 2024
Open
@vicanso vicanso mentioned this issue Aug 22, 2024
Open
This was referenced Sep 7, 2024
Open
Closed
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@davvid @Ethiraric @qtfkwk @cxw620