summaryrefslogtreecommitdiff
path: root/pcr/java-cdi-api
diff options
context:
space:
mode:
authorDenis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>2021-11-21 04:43:11 +0100
committerDenis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>2021-11-21 05:05:34 +0100
commitc1d2d927da8a5ff798b478ef5f056cab6a181838 (patch)
tree9704041da36ab401228062eee7e8ed39128acf3c /pcr/java-cdi-api
parent02c4384f1077233b0f07bbf69417603e30676b43 (diff)
downloadabslibre-c1d2d927da8a5ff798b478ef5f056cab6a181838.tar.gz
abslibre-c1d2d927da8a5ff798b478ef5f056cab6a181838.tar.bz2
abslibre-c1d2d927da8a5ff798b478ef5f056cab6a181838.zip
libre: asciidoc: bump package revision to workaround expired key
Without that fix, we have the following error while installing or upgrading asciidoc: | > error: asciidoc: signature from "bill-auger <bill-auger@peers.community>" is unknown trust | > :: File /var/cache/pacman/pkg/asciidoc-8.6.10-2.parabola1-any.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)). | > Do you want to delete it? [Y/n] error: failed to commit transaction (invalid or corrupted package) This is because the corresponding gpg key is expired. Key expirations often happen when because there are conflicting best security practices with key expiration dates: for long term software releases, it's better if the key don't have too short expiration dates, especially if users can't easily update the key, but short key expirations help a lot for security and for uses cases like mail, if you loose your key, having a short expiration date will ensure that people will (shortly) stop sending you mail that you can't decrypt. In addition keeping a key always up to date can in some case be very complex. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Diffstat (limited to 'pcr/java-cdi-api')
0 files changed, 0 insertions, 0 deletions