Taxize Package Listed as Orphaned on CRAN

[derek-corcoran-barrios]

Hello,

I am developing a package called SpeciesPoolR, and during a recent check on CRAN, I encountered an issue related to the taxize package. Specifically, the CRAN test returns the following error:

* checking package namespace information ... OK
* checking package dependencies ... WARNING
Warning: Requires orphaned package: ‘taxize’

This warning indicates that taxize is listed as an orphaned package on CRAN. Indeed, the CRAN page for taxize (link) confirms its orphaned status. However, I noticed that the taxize GitHub repository shows recent activity, with updates made in the last three months. This discrepancy is confusing since it suggests the package is still being actively maintained.

To provide some context, I have been developing my package for several weeks, and this issue only appeared yesterday. It was not present during prior checks.

Could this be a temporary issue or oversight on CRAN's part? Any guidance on how to proceed would be greatly appreciated.

Thank you for your help and for maintaining this useful package.

Best regards,
Derek Corcoran

[RobLBaker]

I also am having this same issue. Build checks on packages with taxize dependencies don't work. This does not seem to be a problem when running build checks locally with devtools::check() but does cause all build checks to fail for if you are using github actions to do build checks.

I see that the latest CRAN publication was two days ago. Perhaps the maintainer was inadvertently left off?

[zachary-foster]

Sorry about taxize being orphaned. I must have missed an email while I was on vacation. I will try to get this fixed.

[derek-corcoran-barrios]

Thanks @zachary-foster your package is great, and I am glad it is not orphaned

[dcuadrac]

Hi, read comments that taxize will no longer be ablet to take data from rredlist: #937 (comment)
This is because iucn is changing to api v.4. So, my question is: Is taxize going to be updated to api v.4? I guess right now everything is still working with api v.3, right?

[willgearty]

The IUCN functionality in taxize will break with the upcoming version of rredlist (since it uses functions in rredlist to interface with the IUCN Red List API). For that reason, I'm holding off from publishing the new version of rredlist for a reasonable amount of time, and hopefully @zachary-foster can work with me to maintain some (or all) of the IUCN functionality in taxize. Note that if you don't install the new version of rredlist, the functionality in taxize will not change.

That being said, discussions about the new version of rredlist should be had in #937, not here.