I don't think that answers the OP's question (why was it archived
after apparently passing checks/being published)?
I do get one error (reproduced below) when I `R CMD check --as-cran`
on Linux with r-devel.
I would say that the path of least resistance would be: (1) fix the
error (assuming you can reproduce it ...); (2) bump the version number
to 1.0.9 (or 1.0.8.1, whatever); (3) (re)submit to CRAN.
[24s/43s] ERROR
Running the tests in ‘tests/testthat.R’ failed.
Last 13 lines of output:
'test_saveDataframesAsFiles.R:11:3', 'test_saveDataframesAsFiles.R:37:3',
'test_saveDataframesAsFiles.R:62:3'
══ Failed tests
════════════════════════════════════════════════════════════════
── Failure ('test_print.summary.nprcgenekeeprErr.R:29:3'):
print.summary.nprcgenekeeprErr prints expected output ──
Expected failure message to match regexp "produced output".
Actual message:
✖ │ Expected `print(summary(qcStudbook(pedOne, reportErrors =
TRUE)))` to produce no output.
│ Actual output:
│ Error: The animal listed as a sire and also listed as a female
is: s1.\nError: The animal listed as a dam and also listed as a male
is: d1.\n\nPlease check and correct the pedigree file.\n \nAnimal
records where parent records are suspicous because of dates.\nOne or
more parents appear too young at time of birth.\n dam sire id sex
birth recordStatus exit sireBirth damBirth sireAge\n2 d2 s1 o2
F 2009-03-17 original <NA> 2000-07-18 2015-09-16 8.66\n3 d2
s2 o3 F 2012-04-11 original <NA> 2006-06-19 2015-09-16
5.81\n4 d2 s2 o4 M 2006-04-13 original <NA> 2006-06-19
2015-09-16 -0.18\n damAge\n2 -6.5\n3 -3.4\n4 -9.4
[ FAIL 1 | WARN 0 | SKIP 24 | PASS 861 ]
Error:
! Test failures.
Execution halted
On Thu, Jan 15, 2026 at 1:13 PM Henrik Bengtsson
<[email protected]> wrote:
>
> Sorry to hear. From https://cran.r-project.org/src/contrib/PACKAGES.in (*):
>
> "Package: nprcgenekeepr
> X-CRAN-Comment: Archived on 2025-07-29 as issues were not corrected in time.
> .
> Tested elapsed times.
> X-CRAN-History: Archived on 2022-11-03 as check problems were not corrected
> despite reminders.
> Unarchived on 2025-04-24."
>
> (*) That file is a hard-yo-remember "internal" URL. You can find it via
> https://www.cranhaven.org/.
>
>
> How this helps,
>
> Henrik
>
> On Thu, Jan 15, 2026, 09:52 R. Mark Sharp <[email protected]> wrote:
>
> > I submitted an update based on needing to make some changes due to
> > dependencies. As appended below, I received a message July 25, 2025 that
> > the updated package (1.0.8) was on its way to CRAN. I checked shortly after
> > July 25th and the package was published. However, it appears 1.0.8 was
> > removed on July 29th. I do not see a problem on
> > https://cran-archive.r-project.org/web/checks/2025/2025-07-29_check_results_nprcgenekeepr.html
> >
> > I have contacted [email protected] <mailto:
> > [email protected]> to find out what I need to do to rectify
> > this but have not gotten a response. Suggestions are welcome.
> >
> > Mark
> > R. Mark Sharp, Ph.D.
> > 7526 Meadow Green St.
> > San Antonio, TX 78251
> > mobile: 210-218-2868
> > [email protected]
> >
> >
> >
> >
> > Begin forwarded message:
> >
> > From: [email protected]
> > Subject: [CRAN-pretest-publish] CRAN Submission nprcgenekeepr 1.0.8
> > Date: July 25, 2025 at 10:56:10 PM CDT
> > To: [email protected]
> > Cc: [email protected]
> > Reply-To: [email protected]
> >
> > Dear maintainer,
> >
> > thanks, package nprcgenekeepr_1.0.8.tar.gz is on its way to CRAN.
> >
> > Best regards,
> > CRAN teams' auto-check service
> > Flavor: r-devel-linux-x86_64-debian-gcc, r-devel-windows-x86_64
> > Check: *, Result: OK
> > ______________________________________________
> > [email protected] mailing list
> > https://stat.ethz.ch/mailman/listinfo/r-package-devel
> >
>
> [[alternative HTML version deleted]]
>
> ______________________________________________
> [email protected] mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel
______________________________________________
[email protected] mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
