From: David Elsing <david.elsing@posteo.net>
To: Andreas Enge <andreas@enge.fr>, 64114@debbugs.gnu.org
Subject: [bug#64114] Action?
Date: Tue, 07 Jan 2025 20:36:27 +0000 [thread overview]
Message-ID: <86v7uqs6no.fsf@posteo.net> (raw)
In-Reply-To: <Z0C-eGdT0T_gLdpd@jurong>
Hello Andreas,
sorry, I didn't see your reply before.
Andreas Enge <andreas@enge.fr> writes:
> I happened to come along your patch and examined the situation. It turns out
> that the fftw version has already been updated to 3.3.10.
>
> Unfortunately, lots of packages depend on it, so changing the package will
> be quite costly. Maybe it would make sense to close the bug for now (or let
> it wait) and come back to it when a new version of fftw comes out?
FFTW isn't very actively developed, so it might take a while until there
is a new release. I think it makes sense to leave the bug open until
someone applies it when a dependency for fftw is updated (e.g. in
core-updates).
Do you think I should send updated patches rebased to master or would
this just unnecessarily occupy QA?
Best,
David
prev parent reply other threads:[~2025-01-07 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 17:16 [bug#64114] [PATCH] gnu: fftw: Update to 3.3.10 and build entirely from source David Elsing
2024-01-14 15:55 ` [bug#64114] [PATCH v2 0/2] Build fftw " David Elsing
2024-01-14 15:55 ` [bug#64114] [PATCH v2 1/2] gnu: fftw: Build " David Elsing
2024-01-14 15:55 ` [bug#64114] [PATCH v2 2/2] gnu: Add fftw-documentation David Elsing
2024-11-22 17:25 ` [bug#64114] Action? Andreas Enge
2025-01-07 20:36 ` David Elsing [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=86v7uqs6no.fsf@posteo.net \
--to=david.elsing@posteo.net \
--cc=64114@debbugs.gnu.org \
--cc=andreas@enge.fr \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.