|
From: | GNU bug Tracking System |
Subject: | bug#38970: closed ([PATCH 21/22] gnu: pjproject-jami: Apply a missing patch.) |
Date: | Mon, 06 Jan 2020 18:28:03 +0000 |
Your message dated Mon, 6 Jan 2020 19:05:57 +0100 with message-id <address@hidden> and subject line Closing the broken patch has caused the debbugs.gnu.org bug report #38970, regarding [PATCH 21/22] gnu: pjproject-jami: Apply a missing patch. to be marked as done. (If you believe you have received this mail in error, please contact address@hidden.) -- 38970: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=38970 GNU Bug Tracking System Contact address@hidden with problems
--- Begin Message ---Subject: [PATCH 21/22] gnu: pjproject-jami: Apply a missing patch. Date: Mon, 6 Jan 2020 02:11:51 +0100 --- gnu/packages/jami.scm | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/gnu/packages/jami.scm b/gnu/packages/jami.scm index ea66bed8a5..22c86e9b5b 100644 --- a/gnu/packages/jami.scm +++ b/gnu/packages/jami.scm @@ -165,7 +165,8 @@ "fix_ebusy_turn" "ignore_ipv6_on_transport_check" "fix_turn_connection_failure" - "disable_local_resolution")) + "disable_local_resolution" + "fix_assert_on_connection_attempt")) #t))) ;; TODO: We could use substitute-keyword-arguments instead of ;; repeating the phases from pjproject, but somehow it does -- 2.24.1
--- End Message ---
--- Begin Message ---Subject: Closing the broken patch Date: Mon, 6 Jan 2020 19:05:57 +0100 I broke the whole patch series, sorry, hope this solves everything. I got smtp error and thought patches didn't send. Jan Wielkiewicz
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |