From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: WIP: clamav: update to 1.2.0.
Date: Sun, 17 Sep 2023 08:25:28 +0200 [thread overview]
Message-ID: <20230917062528.51vcwIVlABWWXV7EfSjUvkWH6lqBDjESlc6IzU2VYyo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46041@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 669 bytes --]
There's a merged pull request on the void-packages repository
WIP: clamav: update to 1.2.0.
https://github.com/void-linux/void-packages/pull/46041
Description:
- [x] Builds locally on x86_64-musl
- [x] Builds locally on x86_64
- [ ] Builds locally on i686
- [x] Builds locally on aarch64-musl _crossbuild_
- [x] Builds locally on aarch64 _crossbuild_
- [ ] Builds locally on armv7l-musl _crossbuild_
- [ ] Builds locally on armv7l _crossbuild_
- [ ] Builds locally on armv6l-musl _crossbuild_
- [ ] Builds locally on armv6l _crossbuild_
- [ ] Test on x86_64-musl
- [ ] Test on x86_64
- [ ] Cleanup/patch the configuration files
- [ ] Add service files
next prev parent reply other threads:[~2023-09-17 6:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 9:39 [PR PATCH] clamav: update to 1.0.3, adopt nsudsgaard
2023-09-13 9:42 ` [PR PATCH] [Updated] " nsudsgaard
2023-09-13 20:54 ` r-ricci
2023-09-14 2:26 ` nsudsgaard
2023-09-14 3:47 ` classabbyamp
2023-09-14 3:53 ` [PR PATCH] [Updated] " nsudsgaard
2023-09-14 3:54 ` clamav: update to 1.0.3 nsudsgaard
2023-09-14 7:02 ` r-ricci
2023-09-14 7:04 ` r-ricci
2023-09-14 7:05 ` r-ricci
2023-09-14 10:55 ` nsudsgaard
2023-09-14 14:46 ` WIP: clamav: update to 1.2.0 nsudsgaard
2023-09-17 6:22 ` [PR PATCH] [Updated] " nsudsgaard
2023-09-17 6:25 ` Johnnynator [this message]
2023-09-18 9:20 ` jcgruenhage
2023-09-18 12:39 ` nsudsgaard
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=20230917062528.51vcwIVlABWWXV7EfSjUvkWH6lqBDjESlc6IzU2VYyo@z \
--to=johnnynator@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).