From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 3/3] spandsp: Ship due to sobump from libtiff
Date: Mon, 09 Jan 2023 10:12:49 +0000 [thread overview]
Message-ID: <62F36E07-B99E-4799-8D8C-CA71AFE5560A@ipfire.org> (raw)
In-Reply-To: <20230108214138.3637483-3-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1593 bytes --]
Hello Adolf,
Actually, since we dropped Asterisk, there is probably no need for spendsp any more.
It is a library that emulates digital sound processors that were used to send and received faxes in Asterisk.
Would you like to submit a patch to drop this? Nobody should be affected by this at all.
Best,
-Michael
> On 8 Jan 2023, at 21:41, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
> lfs/spandsp | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lfs/spandsp b/lfs/spandsp
> index 5d609cb06..ffd8c7d02 100644
> --- a/lfs/spandsp
> +++ b/lfs/spandsp
> @@ -1,7 +1,7 @@
> ###############################################################################
> # #
> # IPFire.org - A linux based firewall #
> -# Copyright (C) 2007-2018 IPFire Team <info(a)ipfire.org> #
> +# Copyright (C) 2007-2023 IPFire Team <info(a)ipfire.org> #
> # #
> # This program is free software: you can redistribute it and/or modify #
> # it under the terms of the GNU General Public License as published by #
> @@ -34,7 +34,7 @@ DL_FROM = $(URL_IPFIRE)
> DIR_APP = $(DIR_SRC)/$(THISAPP)
> TARGET = $(DIR_INFO)/$(THISAPP)
> PROG = spandsp
> -PAK_VER = 6
> +PAK_VER = 7
>
> DEPS =
>
> --
> 2.39.0
>
prev parent reply other threads:[~2023-01-09 10:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 21:41 [PATCH 1/3] libtiff: Update to version 4.5.0 Adolf Belka
2023-01-08 21:41 ` [PATCH 2/3] cups-filters: Ship due to sobump from libtiff Adolf Belka
2023-01-08 21:41 ` [PATCH 3/3] spandsp: " Adolf Belka
2023-01-09 10:12 ` Michael Tremer [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=62F36E07-B99E-4799-8D8C-CA71AFE5560A@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/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