public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Gwyn Ciesla <limburgher@gmail.com>
To: git-commits@fedoraproject.org
Subject: [rpms/transmission] epel10: Patch for fdlimits.
Date: Mon, 20 Jul 2026 20:37:30 GMT	[thread overview]
Message-ID: <178457985088.1.12948779811160895360.rpms-transmission-8ecc3bf11fc0@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/transmission
Branch : epel10
Commit : 8ecc3bf11fc018d950f87c36fd9e1db53049b95a
Author : Gwyn Ciesla <limburgher@gmail.com>
Date   : 2018-01-11T09:58:42-06:00
Stats  : +31/-1 in 2 file(s)
URL    : https://src.fedoraproject.org/rpms/transmission/c/8ecc3bf11fc018d950f87c36fd9e1db53049b95a?branch=epel10

Log:
Patch for fdlimits.

---
diff --git a/transmission-fdlimits.patch b/transmission-fdlimits.patch
new file mode 100644
index 0000000..42b6061
--- /dev/null
+++ b/transmission-fdlimits.patch
@@ -0,0 +1,25 @@
+--- libtransmission/fdlimit.c.orig	2018-01-10 20:21:41.933611849 +0100
++++ libtransmission/fdlimit.c	2018-01-10 20:22:02.367013913 +0100
+@@ -365,22 +365,6 @@
+       fileset_construct (&i->fileset, FILE_CACHE_SIZE);
+       session->fdInfo = i;
+ 
+-#ifndef _WIN32
+-      /* set the open-file limit to the largest safe size wrt FD_SETSIZE */
+-      struct rlimit limit;
+-      if (!getrlimit (RLIMIT_NOFILE, &limit))
+-        {
+-          const int old_limit = (int) limit.rlim_cur;
+-          const int new_limit = MIN (limit.rlim_max, FD_SETSIZE);
+-          if (new_limit != old_limit)
+-            {
+-              limit.rlim_cur = new_limit;
+-              setrlimit (RLIMIT_NOFILE, &limit);
+-              getrlimit (RLIMIT_NOFILE, &limit);
+-              tr_logAddInfo ("Changed open file limit from %d to %d", old_limit, (int)limit.rlim_cur);
+-            }
+-        }
+-#endif
+     }
+ }
+ 

diff --git a/transmission.spec b/transmission.spec
index d59d2cb..8d18e26 100644
--- a/transmission.spec
+++ b/transmission.spec
@@ -2,7 +2,7 @@
 
 Name:           transmission
 Version:        2.92
-Release:        9%{?dist}
+Release:        10%{?dist}
 Summary:        A lightweight GTK+ BitTorrent client
 
 Group:          Applications/Internet
@@ -14,6 +14,7 @@ Source0:        http://download.transmissionbt.com/files/transmission-%{version}
 Source1:        https://raw.githubusercontent.com/gnome-design-team/gnome-icons/master/apps-symbolic/Adwaita/scalable/apps/transmission-symbolic.svg
 #Patch0:         transmission-2.84-overshoot.patch
 Patch1:		transmission-libsystemd.patch
+Patch2:		transmission-fdlimits.patch
 
 BuildRequires:  compat-openssl10-devel >= 0.9.4
 BuildRequires:  glib2-devel >= 2.32.0
@@ -93,6 +94,7 @@ exit 0
 
 #%%patch0 -p0
 %patch1 -p0
+%patch2 -p0
 
 # fix icon location for Transmission Qt
 sed -i 's|Icon=%{name}-qt|Icon=%{name}|g' qt/%{name}-qt.desktop
@@ -228,6 +230,9 @@ EOF
 %doc %{_mandir}/man1/transmission-qt.*
 
 %changelog
+* Wed Jan 10 2018 Heiko Reese <fedora@heiko-reese.de> - 2.92-10
+- Removed hardcoded fdlimit of 1024
+
 * Sat Jan 06 2018 Igor Gnatenko <ignatenkobrain@fedoraproject.org> - 2.92-9
 - Remove obsolete scriptlets
 

                 reply	other threads:[~2026-07-20 20:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=178457985088.1.12948779811160895360.rpms-transmission-8ecc3bf11fc0@fedoraproject.org \
    --to=limburgher@gmail.com \
    --cc=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