From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Source URL for zabbix_agentd?
Date: Fri, 12 May 2023 07:03:00 +0000 [thread overview]
Message-ID: <39f4d9b9-1b4b-8069-ca6c-1dfb3606531a@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 612 bytes --]
Hello Robin,
with regards to your Zabbix patchset, where did the source tarball come from?
I'm currently struggling to find a download URL that provides a tarball with
the same checksum as the LFS file. There does not seem to be away to download
only the Zabbix agent from the vendor's homepage (or I missed it).
Thanks for giving me a hint. Will include the URL in the LFS file as a comment
then, to avoid bothering you a second time.
Thanks, and best regards,
Peter Müller
P.S.: And yes, I should have checked this before amending your patch, but my
under-caffeinated self missed that the other day. :-/
reply other threads:[~2023-05-12 7:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=39f4d9b9-1b4b-8069-ca6c-1dfb3606531a@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@lists.ipfire.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