From: Zheng Junjie <zhengjunjie@iscas.ac.cn>
To: 74570@debbugs.gnu.org
Cc: kiasoc5@disroot.org
Subject: [bug#74570] [PATCH] gnu: xterm: Update to 395.
Date: Fri, 29 Nov 2024 17:59:43 +0800 [thread overview]
Message-ID: <87h67qtl68.fsf@iscas.ac.cn> (raw)
In-Reply-To: <e5dbfe05d754bbf9e50a5504844f0d105f991764.1732749716.git.kiasoc5@disroot.org> (kiasoc's message of "Thu, 28 Nov 2024 00:19:14 -0500")
[-- Attachment #1: Type: text/plain, Size: 1315 bytes --]
kiasoc5 via Guix-patches via <guix-patches@gnu.org> writes:
> * gnu/packages/xorg.scm (xterm): Update to 395.
>
> Change-Id: If8434c5d5055fa0a3163a7018b4c0ba5e5280935
> ---
> gnu/packages/xorg.scm | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/gnu/packages/xorg.scm b/gnu/packages/xorg.scm
> index 554dc21ba7..470e8f1bc3 100644
> --- a/gnu/packages/xorg.scm
> +++ b/gnu/packages/xorg.scm
> @@ -5969,7 +5969,7 @@ (define-public xmessage
> (define-public xterm
> (package
> (name "xterm")
> - (version "390")
> + (version "395")
> (source
> (origin
> (method url-fetch)
> @@ -5979,7 +5979,7 @@ (define-public xterm
> (string-append "ftp://ftp.invisible-island.net/xterm/"
> "xterm-" version ".tgz")))
> (sha256
> - (base32 "03wwdwnpj5dg1ah5sfp00ppzawjd81lnw47g4p20jjhpqly7q4bm"))
> + (base32 "1j1x16c1789w845hgs49wsmgx7b2cwan49r8427f7siqb6m3qvi8"))
> (patches
> (search-patches "xterm-370-explicit-xcursor.patch"))))
> (build-system gnu-build-system)
>
> base-commit: c6d15cf27a137051ccd8f301330a70dd0eecc3d4
Now the xvfb-run test depends on xterm, so we can't simply update xterm,
we might add a new xterm package and hide the original xterm for
xvfb-run only.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2024-11-29 10:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 5:19 [bug#74570] [PATCH] gnu: xterm: Update to 395 kiasoc5 via Guix-patches via
2024-11-29 9:59 ` Zheng Junjie [this message]
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=87h67qtl68.fsf@iscas.ac.cn \
--to=zhengjunjie@iscas.ac.cn \
--cc=74570@debbugs.gnu.org \
--cc=kiasoc5@disroot.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 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.