summaryrefslogtreecommitdiffstats
path: root/tests/arch_is_concerned.sh
diff options
context:
space:
mode:
authorPatrick McDermott <patrick.mcdermott@libiquity.com>2019-07-21 19:28:43 (EDT)
committer Patrick McDermott <patrick.mcdermott@libiquity.com>2019-07-21 19:31:59 (EDT)
commitfb1cd5d9a0894eab954a47f3e9e0e8d0c8d4d359 (patch)
treef6de0b7d2694d581ddde6af33c9d94f751d4f050 /tests/arch_is_concerned.sh
parentd88109911f14edbfdf063f6c90ffff330206f2a3 (diff)
opkg-cert: Don't blame clock for bootstrap to invalid cert
When a mirror has an expired certificate, prokit and opkg-cert print: prokit: Using architecture amd64-linux-glibc prokit: Using platform dev prokit: Using mirror http://files.proteanos.com/pub/proteanos/ prokit: Setting up root... prokit: Configuring opkg and retrieving Packages files... opkg-cert: Invalid certificate from <http://files.proteanos.com/pub/proteanos//archive.cert>! opkg-cert: Clock incorrect The second message from opkg-cert is wrong and confusing.
Diffstat (limited to 'tests/arch_is_concerned.sh')
0 files changed, 0 insertions, 0 deletions