CRAN Package Check Results for Package dpkg

Last updated on 2026-01-20 15:49:42 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.6.1 1.96 33.18 35.14 ERROR
r-devel-linux-x86_64-debian-gcc 0.6.1 1.35 24.86 26.21 ERROR
r-devel-linux-x86_64-fedora-clang 0.6.1 3.00 51.62 54.62 ERROR
r-devel-linux-x86_64-fedora-gcc 0.6.1 3.00 49.31 52.31 ERROR
r-devel-windows-x86_64 0.6.1 5.00 52.00 57.00 NOTE
r-patched-linux-x86_64 0.6.1 2.05 28.02 30.07 NOTE
r-release-linux-x86_64 0.6.1 1.74 28.38 30.12 NOTE
r-release-macos-arm64 0.6.1 NOTE
r-release-macos-x86_64 0.6.1 1.00 42.00 43.00 NOTE
r-release-windows-x86_64 0.6.1 4.00 50.00 54.00 NOTE
r-oldrel-macos-arm64 0.6.1 OK
r-oldrel-macos-x86_64 0.6.1 2.00 40.00 42.00 OK
r-oldrel-windows-x86_64 0.6.1 5.00 60.00 65.00 OK

Check Details

Version: 0.6.1
Check: DESCRIPTION meta-information
Result: NOTE Missing dependency on R >= 4.1.0 because package code uses the pipe |> or function shorthand \(...) syntax added in R 4.1.0. File(s) using such syntax: ‘dpkg_release_gh.R’ ‘read_dpkg.Rd’ ‘stow.R’ ‘stow.Rd’ Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-devel-windows-x86_64, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64, r-release-windows-x86_64

Version: 0.6.1
Check: tests
Result: ERROR Running ‘testthat.R’ [6s/8s] Running the tests in ‘tests/testthat.R’ failed. Complete output: > # This file is part of the standard setup for testthat. > # It is recommended that you do not modify it. > # > # Where should you do additional test configuration? > # Learn more about the roles of various files in: > # * https://r-pkgs.org/testing-design.html#sec-tests-files-overview > # * https://testthat.r-lib.org/articles/special-files.html > > library(testthat) > library(dpkg) > > test_check("dpkg") Saving _problems/test-read_dpkg-37.R [ FAIL 1 | WARN 0 | SKIP 1 | PASS 41 ] ══ Skipped tests (1) ═══════════════════════════════════════════════════════════ • On CRAN (1): 'test-dpkg.R:1:1' ══ Failed tests ════════════════════════════════════════════════════════════════ ── Failure ('test-read_dpkg.R:22:3'): read_dpkg() and read_dpkg_metadata() works ── Expected `the_md` to be identical to `list(...)`. Differences: `actual$hash`: "d1b5a065f1a8ba36dd163b29d9a382ac" `expected$hash`: "502c9e71f62f79debf7e769e071df0b4" [ FAIL 1 | WARN 0 | SKIP 1 | PASS 41 ] Error: ! Test failures. Execution halted Flavor: r-devel-linux-x86_64-debian-clang

Version: 0.6.1
Check: tests
Result: ERROR Running ‘testthat.R’ [3s/4s] Running the tests in ‘tests/testthat.R’ failed. Complete output: > # This file is part of the standard setup for testthat. > # It is recommended that you do not modify it. > # > # Where should you do additional test configuration? > # Learn more about the roles of various files in: > # * https://r-pkgs.org/testing-design.html#sec-tests-files-overview > # * https://testthat.r-lib.org/articles/special-files.html > > library(testthat) > library(dpkg) > > test_check("dpkg") Saving _problems/test-read_dpkg-37.R [ FAIL 1 | WARN 0 | SKIP 1 | PASS 41 ] ══ Skipped tests (1) ═══════════════════════════════════════════════════════════ • On CRAN (1): 'test-dpkg.R:1:1' ══ Failed tests ════════════════════════════════════════════════════════════════ ── Failure ('test-read_dpkg.R:22:3'): read_dpkg() and read_dpkg_metadata() works ── Expected `the_md` to be identical to `list(...)`. Differences: `actual$hash`: "d1b5a065f1a8ba36dd163b29d9a382ac" `expected$hash`: "502c9e71f62f79debf7e769e071df0b4" [ FAIL 1 | WARN 0 | SKIP 1 | PASS 41 ] Error: ! Test failures. Execution halted Flavor: r-devel-linux-x86_64-debian-gcc

Version: 0.6.1
Check: tests
Result: ERROR Running ‘testthat.R’ [8s/36s] Running the tests in ‘tests/testthat.R’ failed. Complete output: > # This file is part of the standard setup for testthat. > # It is recommended that you do not modify it. > # > # Where should you do additional test configuration? > # Learn more about the roles of various files in: > # * https://r-pkgs.org/testing-design.html#sec-tests-files-overview > # * https://testthat.r-lib.org/articles/special-files.html > > library(testthat) > library(dpkg) > > test_check("dpkg") Saving _problems/test-read_dpkg-37.R [ FAIL 1 | WARN 0 | SKIP 1 | PASS 41 ] ══ Skipped tests (1) ═══════════════════════════════════════════════════════════ • On CRAN (1): 'test-dpkg.R:1:1' ══ Failed tests ════════════════════════════════════════════════════════════════ ── Failure ('test-read_dpkg.R:22:3'): read_dpkg() and read_dpkg_metadata() works ── Expected `the_md` to be identical to `list(...)`. Differences: `actual$hash`: "d1b5a065f1a8ba36dd163b29d9a382ac" `expected$hash`: "502c9e71f62f79debf7e769e071df0b4" [ FAIL 1 | WARN 0 | SKIP 1 | PASS 41 ] Error: ! Test failures. Execution halted Flavor: r-devel-linux-x86_64-fedora-clang

Version: 0.6.1
Check: tests
Result: ERROR Running ‘testthat.R’ [8s/21s] Running the tests in ‘tests/testthat.R’ failed. Complete output: > # This file is part of the standard setup for testthat. > # It is recommended that you do not modify it. > # > # Where should you do additional test configuration? > # Learn more about the roles of various files in: > # * https://r-pkgs.org/testing-design.html#sec-tests-files-overview > # * https://testthat.r-lib.org/articles/special-files.html > > library(testthat) > library(dpkg) > > test_check("dpkg") Saving _problems/test-read_dpkg-37.R [ FAIL 1 | WARN 0 | SKIP 1 | PASS 41 ] ══ Skipped tests (1) ═══════════════════════════════════════════════════════════ • On CRAN (1): 'test-dpkg.R:1:1' ══ Failed tests ════════════════════════════════════════════════════════════════ ── Failure ('test-read_dpkg.R:22:3'): read_dpkg() and read_dpkg_metadata() works ── Expected `the_md` to be identical to `list(...)`. Differences: `actual$hash`: "d1b5a065f1a8ba36dd163b29d9a382ac" `expected$hash`: "502c9e71f62f79debf7e769e071df0b4" [ FAIL 1 | WARN 0 | SKIP 1 | PASS 41 ] Error: ! Test failures. Execution halted Flavor: r-devel-linux-x86_64-fedora-gcc

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.
Health stats visible at Monitor.