GNU bug report logs - #48969
[PATCH] gnu: prosody: Update to 0.11.9.

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Solene Rapenne <solene <at> perso.pw>
Subject: bug#48969: closed (Re: bug#48969: [PATCH] gnu: prosody: Update to
 0.11.9.)
Date: Sun, 13 Jun 2021 21:10:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#48969: [PATCH] gnu: prosody: Update to 0.11.9.

which was filed against the guix-patches package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 48969 <at> debbugs.gnu.org.

-- 
48969: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=48969
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Ludovic Courtès <ludo <at> gnu.org>
To: Solene Rapenne <solene <at> perso.pw>
Cc: 48969-done <at> debbugs.gnu.org
Subject: Re: bug#48969: [PATCH] gnu: prosody: Update to 0.11.9.
Date: Sun, 13 Jun 2021 23:09:01 +0200

Hi,

Solene Rapenne <solene <at> perso.pw> skribis:

> Prosody 0.11.3 was released in september 2019, I sincerely hope nobody
> is using it on Guix because it's clearly outdated and unsecure. From
> 0.11.3 to 0.11.9 there are no breaking changes to my knowledge and the
> update should be smooth for current users.
>
> I didn't try the runtime because it's not that easy without a
> configured server.
>
>
> * gnu/packages/messaging.scm (prosody): Update to 0.11.9.

“make check-system TESTS=prosody” passes, so I went ahead and applied it.

Please add comments after the “--” line so that they’re not part of the
commit log when applying the patch.

Thanks!

Ludo’.

[Message part 3 (message/rfc822, inline)]

From: Solene Rapenne <solene <at> perso.pw>
To: guix-patches <at> gnu.org
Subject: [PATCH] gnu: prosody: Update to 0.11.9.
Date: Sat, 12 Jun 2021 09:42:29 +0200

Prosody 0.11.3 was released in september 2019, I sincerely hope nobody
is using it on Guix because it's clearly outdated and unsecure. From
0.11.3 to 0.11.9 there are no breaking changes to my knowledge and the
update should be smooth for current users.

I didn't try the runtime because it's not that easy without a
configured server.


* gnu/packages/messaging.scm (prosody): Update to 0.11.9.
---
 gnu/packages/messaging.scm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gnu/packages/messaging.scm b/gnu/packages/messaging.scm
index 7b91284b10..9ff45026e1 100644
--- a/gnu/packages/messaging.scm
+++ b/gnu/packages/messaging.scm
@@ -1275,14 +1275,14 @@ default.")
 (define-public prosody
   (package
     (name "prosody")
-    (version "0.11.3")
+    (version "0.11.9")
     (source (origin
               (method url-fetch)
               (uri (string-append "https://prosody.im/downloads/source/"
                                   "prosody-" version ".tar.gz"))
               (sha256
                (base32
-                "11xz4milv2962qf75vrdwsvd8sy2332nf69202rmvz5989pvvnng"))))
+                "02gzvsaq0l5lx608sfh7hfz14s6yfsr4sr4kzcsqd1cxljp35h6c"))))
     (build-system gnu-build-system)
     (arguments
      `(#:tests? #f                      ;tests require "busted"
-- 
2.32.0

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.