From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: 52946@debbugs.gnu.org
Subject: [bug#52946] [PATCH 0/2] Update Audacity to 3.1.3.
Date: Tue, 04 Jan 2022 21:43:37 +0100 [thread overview]
Message-ID: <ecec8c7d1f5daa63d39c9f3485c3c9c758cf5e5d.camel@gmail.com> (raw)
In-Reply-To: <YdJ3adbtGDUitNjm@jasmine.lan>
Am Sonntag, dem 02.01.2022 um 23:11 -0500 schrieb Leo Famulari:
> On Sun, Jan 02, 2022 at 10:42:52AM +0100, Liliana Marie Prikler
> wrote:
> > This series updates wxwidgets-3.1 and thereafter audacity. Both
> > packages come with a series of adjustments to things changed in the
> > build system in newer versions.
>
> Thanks, it works for me using Guix on Debian.
Good to know.
> > Particularly concerning is that audacity relies on linux-internal
> > headers in order to do file magic. Would it be feasible to patch
> > their code so that it works in terms of the file package?
>
> I don't know about this subject, but I noticed the same thing while
> attempting this update. Do you think it's a problem?
I'd like to avoid it if possible. Audacity uses it to determine
whether a particular file system is FAT so as to determine its
limitations -- I'm sure there are better ways of doing that.
Cheers
next prev parent reply other threads:[~2022-01-04 20:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-02 9:42 [bug#52946] [PATCH 0/2] Update Audacity to 3.1.3 Liliana Marie Prikler
2021-12-30 14:23 ` [bug#52946] [PATCH 1/2] gnu: wxwidgets-3.1: Update to 3.1.5 Liliana Marie Prikler
2022-01-02 9:37 ` [bug#52946] [PATCH 2/2] gnu: audacity: Update to 3.1.3 Liliana Marie Prikler
2022-01-03 4:11 ` [bug#52946] [PATCH 0/2] Update Audacity " Leo Famulari
2022-01-04 20:43 ` Liliana Marie Prikler [this message]
2022-01-04 21:04 ` Leo Famulari
2022-01-19 20:16 ` bug#52946: " Liliana Marie Prikler
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ecec8c7d1f5daa63d39c9f3485c3c9c758cf5e5d.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=52946@debbugs.gnu.org \
--cc=leo@famulari.name \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).