From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/ncftp: bump to version 3.2.9
Date: Thu, 3 Apr 2025 10:00:03 +0200 [thread overview]
Message-ID: <20250403100003.2cd45709@windsurf> (raw)
In-Reply-To: <CAGm1_ksE6xFtRustant2MyiSpa3moyv1L_HL0W17UNv6peZ2tQ@mail.gmail.com>
On Thu, 3 Apr 2025 09:53:52 +0200
Yegor Yefremov <yegorslists@googlemail.com> wrote:
> I have also noticed this change and already reported to the ncftp
> maintainer. He has just introduced a small change without bumping the
> version.
>
> There is also another issue with the ncftpbookmarks binary that relies
> on curses instead of ncurses. I have also reported this. Let's wait
> till Mon/Tue and if I don't get an answer from him, I'll send a patch
> fixing checksum and disabling ncftpbookmarks binary.
Fixing the hash will not work, as we have already cached the previous
tarball with the old hash. All what can be done now is for upstream to
release a new version, and us to update to this version.
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 8:00 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
2025-04-03 7:53 ` Yegor Yefremov
2025-04-03 8:00 ` Thomas Petazzoni via buildroot [this message]
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=20250403100003.2cd45709@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