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.