emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#65302: closed ([PATCH] gnu: profanity: Update to 0.14.0.)


From: GNU bug Tracking System
Subject: bug#65302: closed ([PATCH] gnu: profanity: Update to 0.14.0.)
Date: Tue, 29 Aug 2023 13:06:02 +0000

Your message dated Tue, 29 Aug 2023 14:04:02 +0100
with message-id <87a5uagft4.fsf@cbaines.net>
and subject line Re: [bug#65302] [PATCH] gnu: profanity: Update to 0.14.0.
has caused the debbugs.gnu.org bug report #65302,
regarding [PATCH] gnu: profanity: Update to 0.14.0.
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
65302: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=65302
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: [PATCH] gnu: profanity: Update to 0.14.0. Date: Tue, 15 Aug 2023 00:16:00 -0400
* gnu/packagex/messaging.scm (profanity): Update to 0.14.0.
---

guix lint says that profanity might be vulnerable to CVE-2022-40769, but that's 
for a different profanity.
I'm not sure quite the best way to solve that as I don't know if profanity has 
a preferred cpe-name.

 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 f47e1ac0f3..5fccbc8d07 100644
--- a/gnu/packages/messaging.scm
+++ b/gnu/packages/messaging.scm
@@ -2129,7 +2129,7 @@ (define-public libstrophe
 (define-public profanity
   (package
     (name "profanity")
-    (version "0.13.0")
+    (version "0.14.0")
     (source
      (origin
        (method url-fetch)
@@ -2138,7 +2138,7 @@ (define-public profanity
                        version ".tar.gz"))
        (sha256
         (base32
-         "14n45zwc6fxjargqhwqan8fyb7x0ql0hmw56rbjkjfkhpba2qmks"))))
+         "0zygsxxwdxmpppr7vyzi2r7d854yjl6918w0lrs7k41iib9zy8zx"))))
     (build-system glib-or-gtk-build-system)
     (arguments
      `(#:configure-flags

base-commit: 82407391f74dc491662736f03ef031d31ca3913c
-- 
2.41.0




--- End Message ---
--- Begin Message --- Subject: Re: [bug#65302] [PATCH] gnu: profanity: Update to 0.14.0. Date: Tue, 29 Aug 2023 14:04:02 +0100 User-agent: mu4e 1.10.5; emacs 28.2
Jack Hill <jackhill@jackhill.us> writes:

> * gnu/packagex/messaging.scm (profanity): Update to 0.14.0.
> ---
>
> guix lint says that profanity might be vulnerable to CVE-2022-40769, but 
> that's for a different profanity.
> I'm not sure quite the best way to solve that as I don't know if profanity 
> has a preferred cpe-name.
>
>  gnu/packages/messaging.scm | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

This looks good to me, I've pushed it to master as
456790c29953d15f164e0f55dc8f566b40952530.

Attachment: signature.asc
Description: PGP signature


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]