All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Alexey Lukyanchuk <skif@skif-web.ru>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/zabbix: fix patch fuzz
Date: Sat, 20 Jul 2024 23:17:43 +0200	[thread overview]
Message-ID: <20240720231743.0727d3af@windsurf> (raw)
In-Reply-To: <20240720153113.1371411-1-fontaine.fabrice@gmail.com>

On Sat, 20 Jul 2024 17:31:13 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> Fix patch fuzz to avoid the following build failure raised since commit
> 8f88a644ed7d6c9ea55fd4fbe9d7f37055920016 which reduced the fuzz factor:
> 
> Applying 0002-fix-build-with-libressl-3.5.0.patch using patch:
> patching file include/zbxcomms.h
> Hunk #1 succeeded at 210 (offset -43 lines).
> patching file src/libs/zbxcomms/tls.c
> Hunk #1 FAILED at 30.
> 1 out of 1 hunk FAILED -- saving rejects to file src/libs/zbxcomms/tls.c.rej
> 
> While at it, also fix Upstream tags
> 
> Fixes: 8f88a644ed7d6c9ea55fd4fbe9d7f37055920016
>  - http://autobuild.buildroot.org/results/75dfe12312b5479669fcdfea623d93880c675e13
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>

Thanks applied. Please note that the URL from which we download this
tarball no longer works:

--2024-07-20 23:15:29--  https://cdn.zabbix.com/zabbix/sources/stable/6.2/zabbix-6.2.7.tar.gz
Resolving cdn.zabbix.com (cdn.zabbix.com)... 2606:4700:20::ac43:4504, 2606:4700:20::681a:694, 2606:4700:20::681a:794, ...
Connecting to cdn.zabbix.com (cdn.zabbix.com)|2606:4700:20::ac43:4504|:443... connected.
HTTP request sent, awaiting response... 404 Not Found

> -[Upstream status: not sent (no feedback on first patch)]
> +Upstream: not sent (no feedback on first patch)

Zabbix is one of those not really open-source projects. It's driven by
a company, released under AGPLv3 so that they can create a business
incentive for their customers to purchase a commercial license. It
looks like if you want to contribute you need to sign a Contributor
License Agreement. See the details
at https://www.zabbix.com/developers, if you're brave enough.

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-07-20 21:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-20 15:31 [Buildroot] [PATCH 1/1] package/zabbix: fix patch fuzz Fabrice Fontaine
2024-07-20 21:17 ` Thomas Petazzoni via buildroot [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=20240720231743.0727d3af@windsurf \
    --to=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=skif@skif-web.ru \
    --cc=thomas.petazzoni@bootlin.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.