package archived in CRAN

[harshvardhaniimi]

The package isn't available on CRAN anymore because of some outdated packages. Please check if something could be done about it.
Also, please add a list of all functions - something like documentation. That'd really help. Great work by the way!

[andodet]

Not the mantainer here. You can find documentation here or by ??spotifyr in your R console.

[harshvardhaniimi]

There are more functions than what are mentioned on the blog you mentioned. Also ??spotifyr doesn't work.

[andodet]

My bad for not checking thoroughly. That documentation is compiled with {pkgdown} outside of github so I have no idea when was the last time it was updated.

CRAN is probably complaining for some dplyr deprecation warnings I've encountered as well when working on a fork.

@charlie86 It'd be probably good to move it on a gh-pages branch with a simple Github Action for simple deployment (here for more on this) to avoid having to do it manually each time docs are update or a function is added.

[harshvardhaniimi]

Sorry for the late reply: I downloaded the source codes of the package and thankfully they were detailed enough. That worked for me.

[niessen]

The problem which led to archiving has been resolved ( #112), so this issue could probably be fixed by resubmitting to CRAN.

[andodet]

@charlie86 Looping you in this one as I believe that resubmitting spotifyr to CRAN would benefit many users and avoid workarounds for applications depending on it.

[r-leyshon]

As on the CRAN website

"Archived on 2020-05-03 as requires archived package 'genius'."

Keen to know if this will be remedied any time soon.

[antaldaniel]

@JosiahParry , is a hard dependency necessary, cannot genius only be suggested?

[JosiahParry]

@antaldaniel It can be suggested. No hard requirement. Was it taken off of CRAN?

[antaldaniel]

@JosiahParry Yes, it was. It's been a long time since the last release, and I think that the most labourous issue is broken links in the documentation. But also, if a dependency is taken down from CRAN, it pulls down all downstream packages, and therefore only actively maintained packages should remain hard dependencies. (I think it was not genius that pulled down spotifyr, but ggjoy in the README, which is superseded by ggridges; but anyway, you either maintain actively genius, or it shoudl be suggested.)

I am not sure how much effort it will take to get the package back to CRAN, by the way. The biggest challenge is that they do not accept \dontrun{} anymore, only \donttest{}, and all the examples require Spotify Web API authorization. But I am looking into how other API wrapper packages solve this.

[JosiahParry]

Yes, that issue was resolved nearly a year ago.

I presently maintain genius. I too am going through the challenges associated with changes to CRAN.

All examples in spotifyr should be wrapped in donttest{}. This will ensure that CRAN checks do not try and test the functions and error with non-zero exit.

[JosiahParry]

Addtionally, I'd recommend that the README be included in the .Rbuildignore.

[antaldaniel]

@JosiahParry Thanks, I was just working on updating the genius functions. They are heavily affected by changes in tibble, and the .Rbuildignore is updated. I'd like to get in touch with you about genius. I'll send you message or leave a note there.

[JosiahParry]

@antaldaniel please do open an issue if you find any issues. There are none related to tibble presently that I am aware of.