From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: eid-mw: update to 5.0.23
Date: Mon, 14 Jun 2021 13:26:57 +0200 [thread overview]
Message-ID: <20210614112657.ozcYDY7IW1SNF8cO18TnX4_P8mTVY-CSJF7-zysHqn0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31477@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1902 bytes --]
There's a merged pull request on the void-packages repository
eid-mw: update to 5.0.23
https://github.com/void-linux/void-packages/pull/31477
Description:
Right after the PR for the 5.0.22 update got merged, I heard [this](https://github.com/Fedict/eid-mw/pull/142#issuecomment-860584295) from the eid-mw maintainer:
> Side note though: 5.0.22 contains a small, but critical, bug in the validation code of the eid-viewer, which means that under certain circumstances, cards with corrupt data may be considered valid eID cards. The bug was fixed in 5.0.23. Please update to that :-)
Sorry for the inconvenience.
-----
<!-- Mark items with [x] where applicable -->
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [x] I built this PR locally for my native architecture, (x86_64-glibc)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [x] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
prev parent reply other threads:[~2021-06-14 11:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 10:54 [PR PATCH] " PoroCYon
2021-06-14 11:26 ` ericonr
2021-06-14 11:26 ` ericonr [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210614112657.ozcYDY7IW1SNF8cO18TnX4_P8mTVY-CSJF7-zysHqn0@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).