From: nsudsgaard <nsudsgaard@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: WIP: clamav: update to 1.0.1.
Date: Tue, 12 Dec 2023 06:12:42 +0100 [thread overview]
Message-ID: <20231212051242.zD1S883O8K5WH1hyFaz3tZBHQdaaVwFykGlYaSTe_18@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41188@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 725 bytes --]
New comment by nsudsgaard on void-packages repository
https://github.com/void-linux/void-packages/pull/41188#issuecomment-1725014546
Comment:
I have updated the above patch to include service files for `clamd`, `clamonacc` and `freshclam`. However, I have not tested it except that it installs.
TODO:
- [x] Builds locally on x86_64-musl
- [x] Builds locally on x86_64
- [x] Builds locally on i686
- [x] Builds locally on aarch64-musl
- [x] Builds locally on aarch64
- [x] Builds locally on armv7l-musl
- [x] Builds locally on armv7l
- [x] Builds locally on armv6l-musl
- [x] Builds locally on armv6l
- [x] Test on x86_64-musl
- [x] Test on x86_64
- [ ] Test clamd
- [ ] Test clamonacc
- [ ] Test freshclam
next prev parent reply other threads:[~2023-12-12 5:12 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 18:17 [PR PATCH] WIP: clamav: update to 1.0.0 jcgruenhage
2022-12-19 18:18 ` [PR PATCH] [Updated] " jcgruenhage
2022-12-19 20:04 ` jcgruenhage
2022-12-19 20:07 ` jcgruenhage
2022-12-21 23:29 ` jcgruenhage
2023-04-01 1:52 ` github-actions
2023-04-02 9:37 ` [PR PATCH] [Updated] WIP: clamav: update to 1.0.1 jcgruenhage
2023-04-02 9:38 ` jcgruenhage
2023-05-23 21:46 ` r-ricci
2023-05-25 22:21 ` r-ricci
2023-05-26 21:41 ` r-ricci
2023-05-31 20:55 ` r-ricci
2023-08-30 1:44 ` github-actions
2023-09-04 9:57 ` jcgruenhage
2023-09-04 10:02 ` [PR PATCH] [Updated] " jcgruenhage
2023-09-05 20:24 ` [PR REVIEW] " r-ricci
2023-09-06 23:48 ` r-ricci
2023-09-19 7:20 ` nsudsgaard
2023-09-19 7:43 ` nsudsgaard
2023-09-19 7:56 ` nsudsgaard
2023-09-19 7:57 ` nsudsgaard
2023-09-19 8:00 ` nsudsgaard
2023-09-19 8:01 ` nsudsgaard
2023-09-22 12:00 ` nsudsgaard
2023-09-22 12:00 ` nsudsgaard
2023-09-22 12:00 ` nsudsgaard
2023-09-22 12:00 ` nsudsgaard
2023-09-22 12:00 ` nsudsgaard
2023-09-22 12:00 ` nsudsgaard
2023-09-22 12:00 ` nsudsgaard
2023-09-22 12:00 ` nsudsgaard
2023-09-23 1:44 ` nsudsgaard
2023-09-23 2:45 ` nsudsgaard
2023-09-23 3:30 ` nsudsgaard
2023-09-23 5:51 ` nsudsgaard
2023-12-12 5:12 ` nsudsgaard
2023-12-12 5:12 ` nsudsgaard [this message]
2023-12-12 5:12 ` nsudsgaard
2023-12-12 5:12 ` nsudsgaard
2023-12-12 5:12 ` nsudsgaard
2024-03-12 1:44 ` github-actions
2024-03-14 11:46 ` jcgruenhage
2024-03-14 11:46 ` [PR PATCH] [Closed]: " jcgruenhage
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=20231212051242.zD1S883O8K5WH1hyFaz3tZBHQdaaVwFykGlYaSTe_18@z \
--to=nsudsgaard@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).