From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: yegorslists@googlemail.com
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/ncftp: bump to version 3.2.9
Date: Thu, 3 Apr 2025 09:44:30 +0200 [thread overview]
Message-ID: <20250403094430.08d9b2f1@windsurf> (raw)
In-Reply-To: <20250326080506.3467586-1-yegorslists@googlemail.com>
Hello Yegor,
On Wed, 26 Mar 2025 09:05:06 +0100
yegorslists@googlemail.com wrote:
> From: Yegor Yefremov <yegorslists@googlemail.com>
>
> Remove upstreamed patches.
>
> Autoreconf is broken. Hence, use the configure script directly.
>
> Fixes:
> https://autobuild.buildroot.org/results/60c3dbe02af354ff9820258ffd00eec088114d69/
>
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
This somehow breaks the build, but not your fault: it looks like
upstream changed the tarball. Indeed, on sources.buildroot.net we know
have in cache the tarball that matches the hash you have submitted in
this patch. But the tarball available on the official website now has a
different hash.
See the build failure at:
https://autobuild.buildroot.net/results/d18/d18191dbb1fb8d7fe64ee547ca9b97c133434ea2/build-end.log
Could you have a look perhaps?
Best regards,
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
next prev parent reply other threads:[~2025-04-03 7:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 8:05 [Buildroot] [PATCH] package/ncftp: bump to version 3.2.9 yegorslists
2025-03-26 20:16 ` Julien Olivain
2025-04-03 7:44 ` Thomas Petazzoni via buildroot [this message]
2025-04-03 7:53 ` Yegor Yefremov
2025-04-03 8:00 ` Thomas Petazzoni via buildroot
2025-04-03 8:03 ` Yegor Yefremov
2025-04-16 21:15 ` Arnout Vandecappelle via buildroot
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=20250403094430.08d9b2f1@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=yegorslists@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox