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.

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

Submit to CRAN to fix Debian check failure #582

Closed
sfirke opened this issue Nov 18, 2024 · 2 comments · Fixed by #584
Closed

Submit to CRAN to fix Debian check failure #582

sfirke opened this issue Nov 18, 2024 · 2 comments · Fixed by #584
Assignees
Milestone

Comments

@sfirke
Copy link
Owner

sfirke commented Nov 18, 2024

From CRAN today 11/18:

Dear maintainer,

Please see the problems shown on
<https://cran.r-project.org/web/checks/check_results_janitor.html>.

The errors on the Debian check systems are from a recent system upgrade
to tzdata 2024b which did

   Names present only for compatibility with UNIX System V
   (last released in the 1990s) have been moved to 'backward'.

which includes CET, CST6CDT, EET, EST*, HST, MET, MST*, PST8PDT, and
WET.

Debian ships the names in 'backward' in a separate package tzdata-legacy
which is not installed "by default".

The comments in the tzdata 'backward' file say

# Although this file is optional and tzdb will work if you omit it by
# building with 'make BACKWARD=', in practice downstream users
# typically use this file for backward compatibility.

so clearly one cannot unconditionally assume that the backward
compatibility names will work.

Can you please change your code (typically tests) so that they do not
fail when the backward compatibility names are not available?

Please correct before 2024-12-09 to safely retain your package on CRAN.

Best wishes,
The CRAN Team
@sfirke sfirke self-assigned this Nov 18, 2024
@sfirke sfirke added this to the v2.3 milestone Nov 18, 2024
@billdenney
Copy link
Collaborator

I can take a look at this. I'd also like to get the PR queue into 2.3, if possible.

@sfirke
Copy link
Owner Author

sfirke commented Nov 19, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants