public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
To: git-commits@fedoraproject.org
Subject: [rpms/roc-toolkit] rawhide: Rebuilt for sox_ng transition
Date: Tue, 08 Sep 2026 16:06:10 GMT	[thread overview]
Message-ID: <178888357005.1.5105693178036954367.rpms-roc-toolkit-a38bef477ead@fedoraproject.org> (raw)

          A new commit has been pushed.

          Repo   : rpms/roc-toolkit
          Branch : rawhide
          Commit : a38bef477ead9581db7c062914e8f9d38e74cd68
          Author : Jaroslav Škarvada <jskarvad@redhat.com>
          Date   : 2026-09-08T18:06:01+02:00
          Stats  : +28/-2 in 2 file(s)
          URL    : https://src.fedoraproject.org/rpms/roc-toolkit/c/a38bef477ead9581db7c062914e8f9d38e74cd68?branch=rawhide

          Log:
          Rebuilt for sox_ng transition

Resolves: rhbz#2527803

---
diff --git a/roc-toolkit-0.4.0-increase-max-drivers.patch b/roc-toolkit-0.4.0-increase-max-drivers.patch
new file mode 100644
index 0000000..ea0ac6a
--- /dev/null
+++ b/roc-toolkit-0.4.0-increase-max-drivers.patch
@@ -0,0 +1,20 @@
+From: Gerald Cox <gbcox@fedoraproject.org>
+Subject: [PATCH] Increase maximum number of audio drivers
+
+SoX_ng exposes more audio formats and aliases than the original SoX,
+causing the fixed driver array to overflow during backend discovery.
+
+This matches the limit used by current upstream Roc Toolkit.
+
+diff --git a/src/internal_modules/roc_sndio/driver.h b/src/internal_modules/roc_sndio/driver.h
+--- a/src/internal_modules/roc_sndio/driver.h
++++ b/src/internal_modules/roc_sndio/driver.h
+@@ -21,7 +21,7 @@ namespace sndio {
+ class IBackend;
+ 
+ //! Maximum number of drivers.
+-static const size_t MaxDrivers = 128;
++static const size_t MaxDrivers = 512;
+ 
+ //! Driver type.
+ enum DriverType {

diff --git a/roc-toolkit.spec b/roc-toolkit.spec
index 70b9505..f6c5eaa 100644
--- a/roc-toolkit.spec
+++ b/roc-toolkit.spec
@@ -8,7 +8,7 @@
 Name:		roc-toolkit
 #Version:	0.2.1^%%{git_suffix}
 Version:	0.4.0
-Release:	7%{?dist}
+Release:	8%{?dist}
 Summary:	Real-time audio streaming
 License:	MPL-2.0 AND LGPL-2.1-or-later AND CECILL-C
 URL:		https://github.com/roc-streaming/roc-toolkit
@@ -38,7 +38,9 @@ BuildRequires:	openssl-devel
 BuildRequires:	doxygen
 BuildRequires:	libsndfile-devel
 # https://github.com/roc-streaming/roc-toolkit/issues/481
-Patch0:		roc-toolkit-0.3.0-no-explicit-cpp98.patch
+Patch:		roc-toolkit-0.3.0-no-explicit-cpp98.patch
+# https://bugzilla-attachments.redhat.com/attachment.cgi?id=2156508
+Patch:		roc-toolkit-0.4.0-increase-max-drivers.patch
 
 %description
 Roc is a toolkit for real-time audio streaming over the network.
@@ -103,6 +105,10 @@ scons test --with-openfec-includes=%{_includedir}/openfec --enable-tests
 %doc docs/html
 
 %changelog
+* Tue Sep 08 2026 Jaroslav Škarvada <jskarvad@redhat.com> - 0.4.0-8
+- Rebuilt for sox_ng transition
+  Resolves: rhbz#2527803
+
 * Thu Jul 16 2026 Fedora Release Engineering <releng@fedoraproject.org> - 0.4.0-7
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_45_Mass_Rebuild
 

             reply	other threads:[~2026-09-08 16:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08 16:06  [this message]
2026-09-10 13:12 [rpms/roc-toolkit] rawhide: Rebuilt for sox_ng transition 

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=178888357005.1.5105693178036954367.rpms-roc-toolkit-a38bef477ead@fedoraproject.org \
    --to=git-commits@fedoraproject.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