From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: "Sven Püschel" <s.pueschel@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] ntfs-3g: version bump 2022.10.3 -> 2026.9.18
Date: Tue, 6 Oct 2026 09:01:36 +0200 [thread overview]
Message-ID: <20261006070136.2793119-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260929074957.1150382-1-s.pueschel@pengutronix.de>
Thanks, applied as b52d311a31773dbeac5ef274ddf31a5692195992.
Michael
[sent from post-receive hook]
On Tue, 06 Oct 2026 09:01:36 +0200, Sven Püschel <s.pueschel@pengutronix.de> wrote:
> Some improvements and a bunch of security fixes:
>
> https://github.com/tuxera/ntfs-3g/releases/tag/2026.2.25
> https://github.com/tuxera/ntfs-3g/releases/tag/2026.7.7
> https://github.com/tuxera/ntfs-3g/releases/tag/2026.9.18
>
> The README changed due to the addition of newer Windows versions.
>
> Signed-off-by: Sven Püschel <s.pueschel@pengutronix.de>
> Message-Id: <20260929074957.1150382-1-s.pueschel@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/ntfs-3g.make b/rules/ntfs-3g.make
> index ee0eb181caf1..0926d85957a7 100644
> --- a/rules/ntfs-3g.make
> +++ b/rules/ntfs-3g.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_NTFS_3G) += ntfs-3g
> #
> # Paths and names
> #
> -NTFS_3G_VERSION := 2022.10.3
> -NTFS_3G_SHA256 := f20e36ee68074b845e3629e6bced4706ad053804cbaf062fbae60738f854170c
> +NTFS_3G_VERSION := 2026.9.18
> +NTFS_3G_SHA256 := bcf3cf301a79e42d330128ffb52d4cf615bd1d30c10a92d9d8d14f2bb4fcd9bf
> NTFS_3G := ntfs-3g_ntfsprogs-$(NTFS_3G_VERSION)
> NTFS_3G_SUFFIX := tgz
> NTFS_3G_URL := https://download.tuxera.com/opensource/$(NTFS_3G).$(NTFS_3G_SUFFIX)
> @@ -23,7 +23,7 @@ NTFS_3G_SOURCE := $(SRCDIR)/$(NTFS_3G).$(NTFS_3G_SUFFIX)
> NTFS_3G_DIR := $(BUILDDIR)/$(NTFS_3G)
> NTFS_3G_LICENSE := GPL-2.0-or-later AND LGPL-2.0-only
> NTFS_3G_LICENSE_FILES := \
> - file://README;startline=37;endline=44;md5=692018652fb43fb27bfde6a919c68388 \
> + file://README;startline=37;endline=44;md5=1b0233b9858fc6047c15fdeb8b88beb7 \
> file://COPYING;md5=59530bdf33659b29e73d4adb9f9f6552 \
> file://COPYING.LIB;md5=f30a9716ef3762e3467a2f62bf790f0a
>
prev parent reply other threads:[~2026-10-06 7:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 7:49 [ptxdist] [PATCH] " Sven Püschel
2026-10-06 7:01 ` Michael Olbrich [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=20261006070136.2793119-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=s.pueschel@pengutronix.de \
/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