unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Wilko Meyer <w@wmeyer.eu>
To: 71957@debbugs.gnu.org
Cc: Wilko Meyer <w@wmeyer.eu>
Subject: [bug#71957] [PATCH] gnu: znc: Update to 1.9.1.
Date: Sat,  6 Jul 2024 00:49:26 +0200	[thread overview]
Message-ID: <dda68708fc73de11bc68bb5346b907cc621e394d.1720219766.git.w@wmeyer.eu> (raw)

* gnu/packages/messaging.scm (znc): Update to 1.9.1.

Change-Id: I08b70f2afb721b28e4fd25fa4e370b11407f45df
---
Hi Guix,

Noticed znc was outdated by a major version, so I updated it
accordingly. Builds successfully on my machine:

successfully built /gnu/store/6m4zac57wzi9mil0wzh3j5bp6lqnch8m-znc-1.9.1.drv
/gnu/store/jkhylxf6x3nrxkjk4yi08p6yia8qjv7n-znc-1.9.1

Cheers!

 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 9ba83c0712..f87c8c9f6b 100644
--- a/gnu/packages/messaging.scm
+++ b/gnu/packages/messaging.scm
@@ -1091,14 +1091,14 @@ (define-public pidgin-otr
 (define-public znc
   (package
     (name "znc")
-    (version "1.8.2")
+    (version "1.9.1")
     (source (origin
               (method url-fetch)
               (uri (string-append "https://znc.in/releases/archive/znc-"
                                   version ".tar.gz"))
               (sha256
                (base32
-                "03fyi0j44zcanj1rsdx93hkdskwfvhbywjiwd17f9q1a7yp8l8zz"))))
+                "0g2gi7207lydmm7zdq52ivw0vhvbnmhsybi89q5m3bcsw60cz9z8"))))
     (build-system cmake-build-system)
     (arguments
      `(#:configure-flags

base-commit: e725e47a695c82305fa65e63e54477c6a210f53d
-- 
2.41.0





             reply	other threads:[~2024-07-05 22:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-05 22:49 Wilko Meyer [this message]
2024-07-21 11:43 ` bug#71957: [PATCH] gnu: znc: Update to 1.9.1 宋文武 via Guix-patches via

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dda68708fc73de11bc68bb5346b907cc621e394d.1720219766.git.w@wmeyer.eu \
    --to=w@wmeyer.eu \
    --cc=71957@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).