public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Craig Andrews" <candrews@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-p2p/deluge/files/
Date: Mon, 21 Oct 2019 13:25:40 +0000 (UTC)	[thread overview]
Message-ID: <1571664335.b35463dac1ca31fc012ec04e93f0fc30ae45cd65.candrews@gentoo> (raw)

commit:     b35463dac1ca31fc012ec04e93f0fc30ae45cd65
Author:     Michael Mair-Keimberger <m.mairkeimberger <AT> gmail <DOT> com>
AuthorDate: Sat Oct 19 08:22:36 2019 +0000
Commit:     Craig Andrews <candrews <AT> gentoo <DOT> org>
CommitDate: Mon Oct 21 13:25:35 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b35463da

net-p2p/deluge: remove unused patch

Signed-off-by: Michael Mair-Keimberger <m.mairkeimberger <AT> gmail.com>
Closes: https://github.com/gentoo/gentoo/pull/13341
Signed-off-by: Craig Andrews <candrews <AT> gentoo.org>

 .../files/deluge-1.3.12-fix_scheduler_plugin.patch | 22 ----------------------
 1 file changed, 22 deletions(-)

diff --git a/net-p2p/deluge/files/deluge-1.3.12-fix_scheduler_plugin.patch b/net-p2p/deluge/files/deluge-1.3.12-fix_scheduler_plugin.patch
deleted file mode 100644
index fda64aa2b39..00000000000
--- a/net-p2p/deluge/files/deluge-1.3.12-fix_scheduler_plugin.patch
+++ /dev/null
@@ -1,22 +0,0 @@
-From cdf301601fe71bd697f3796cf0a5656d437d140e Mon Sep 17 00:00:00 2001
-From: Calum Lind <calumlind+deluge@gmail.com>
-Date: Wed, 16 Sep 2015 15:11:56 +0100
-Subject: [Scheduler] Revert erroneous fix backported from develop branch
-
- * The issue this was intended to fix only occurs on develop branch
----
- deluge/plugins/scheduler/scheduler/core.py | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/deluge/plugins/scheduler/scheduler/core.py b/deluge/plugins/scheduler/scheduler/core.py
-index 9fb81df..f0e2392 100644
---- a/deluge/plugins/scheduler/scheduler/core.py
-+++ b/deluge/plugins/scheduler/scheduler/core.py
-@@ -127,7 +127,7 @@ class Core(CorePluginBase):
-         """
-         core_config = deluge.configmanager.ConfigManager("core.conf")
-         for setting in CONTROLLED_SETTINGS:
--            component.get("PreferencesManager").do_config_set_func(setting, core_config[setting])
-+            core_config.apply_set_functions(setting)
-         # Resume the session if necessary
-         component.get("Core").session.resume()


             reply	other threads:[~2019-10-21 13:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21 13:25 Craig Andrews [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-06-05 23:03 [gentoo-commits] repo/gentoo:master commit in: net-p2p/deluge/files/ Conrad Kostecki
2020-04-30 18:46 Andreas Sturmlechner
2020-04-27 13:48 Mikle Kolyada
2017-12-20 22:13 Kristian Fiskerstrand
2016-03-10 10:34 Patrice Clement
2016-03-10 10:34 Patrice Clement
2016-03-10 10:34 Patrice Clement
2016-03-04  8:44 Ian Delaney
2016-02-28 20:38 Kristian Fiskerstrand
2016-02-28 20:38 Kristian Fiskerstrand
2016-02-28 20:38 Kristian Fiskerstrand
2016-02-16 18:21 Kristian Fiskerstrand
2016-02-16 18:21 Kristian Fiskerstrand
2016-02-16 18:21 Kristian Fiskerstrand
2016-02-16 18:21 Kristian Fiskerstrand

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=1571664335.b35463dac1ca31fc012ec04e93f0fc30ae45cd65.candrews@gentoo \
    --to=candrews@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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