From: Kei Kebreau <kkebreau@posteo.net>
To: Leo Famulari <leo@famulari.name>
Cc: 34036@debbugs.gnu.org
Subject: [bug#34036] [PATCH] gnu: irssi: Update to 1.1.2 [fixes CVE-2019-5882].
Date: Thu, 10 Jan 2019 16:08:19 -0500 [thread overview]
Message-ID: <87lg3sdxvg.fsf@posteo.net> (raw)
In-Reply-To: <20190110200501.GA14234@jasmine.lan> (Leo Famulari's message of "Thu, 10 Jan 2019 15:05:01 -0500")
[-- Attachment #1: Type: text/plain, Size: 660 bytes --]
Oh, it's not an auto-generated tarball! In that case I've attached the
much simpler update patch.
Leo Famulari <leo@famulari.name> writes:
> On Thu, Jan 10, 2019 at 01:03:20PM -0500, Kei Kebreau wrote:
>> * gnu/packages/irc.scm (irssi): Update to 1.1.2.
>> [source]: Use 'git-fetch'.
>> [arguments]: Add 'patch-scripts' phase.
>> [native-inputs]: Add autoconf, automake, and libtool.
>
> Thanks!
>
> But why switch to git-fetch when they offer a tarball? All else being
> equal, we should stick to tarballs when they are offered by upstream.
>
> Specifically, let's use this one:
>
> https://github.com/irssi/irssi/releases/download/1.1.2/irssi-1.1.2.tar.xz
[-- Attachment #2: 0001-gnu-irssi-Update-to-1.1.2-fixes-CVE-2019-5882.patch --]
[-- Type: text/plain, Size: 1462 bytes --]
From c954fe6622660f1511ced2be955c35acfb8b124a Mon Sep 17 00:00:00 2001
From: Kei Kebreau <kkebreau@posteo.net>
Date: Thu, 10 Jan 2019 12:56:04 -0500
Subject: [PATCH] gnu: irssi: Update to 1.1.2 [fixes CVE-2019-5882].
* gnu/packages/irc.scm (irssi): Update to 1.1.2.
---
gnu/packages/irc.scm | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/gnu/packages/irc.scm b/gnu/packages/irc.scm
index ba31d36b9..ec1c4aae9 100644
--- a/gnu/packages/irc.scm
+++ b/gnu/packages/irc.scm
@@ -126,15 +126,15 @@ irssi, but graphical.")
(define-public irssi
(package
(name "irssi")
- (version "1.1.1")
+ (version "1.1.2")
(source (origin
- (method url-fetch)
- (uri (string-append "https://github.com/irssi/irssi/"
- "releases/download/" version "/irssi-"
- version ".tar.xz"))
- (sha256
- (base32
- "1gx1flfh4a09nb3b5pvf0ygnbl7rry3l4gph8wij29dsl7khfj3q"))))
+ (method url-fetch)
+ (uri (string-append "https://github.com/irssi/irssi/"
+ "releases/download/" version "/irssi-"
+ version ".tar.xz"))
+ (sha256
+ (base32
+ "0clppwqhllrmqjg1dd47v9v1qiqx7cf9afm81bm1pscllf4jpk2w"))))
(build-system gnu-build-system)
(arguments
`(#:phases
--
2.20.1
next prev parent reply other threads:[~2019-01-10 21:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 18:03 [bug#34036] [PATCH] gnu: irssi: Update to 1.1.2 [fixes CVE-2019-5882] Kei Kebreau
2019-01-10 20:05 ` Leo Famulari
2019-01-10 21:08 ` Kei Kebreau [this message]
2019-01-10 21:15 ` Leo Famulari
2019-01-10 21:33 ` bug#34036: " Kei Kebreau
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=87lg3sdxvg.fsf@posteo.net \
--to=kkebreau@posteo.net \
--cc=34036@debbugs.gnu.org \
--cc=leo@famulari.name \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.