[Git][xorg-team/app/xterm][debian-unstable] 3 commits: Prefer luit over x11-utils in Recommends

Sven Joachim pushed to branch debian-unstable at X Strike Force / app / xterm

Commits:

f2c55ccc
by Sven Joachim at 2022-03-02T20:25:34+01:00
```
Prefer luit over x11-utils in Recommends
```

f922e023

by Sven Joachim at 2022-03-02T20:27:50+01:00

Update copy of XTerm FAQ to revision 1.407 (dated 2021/12/20)

61564260
by Sven Joachim at 2022-03-02T20:32:17+01:00
```
Update years in debian/copyright
```

Changes:

debian/changelog

@@ -3,6 +3,9 @@ xterm (371-1) UNRELEASED; urgency=medium
    * New upstream release.
      - Fix errata in manual page (Closes: #988221).
    * Drop patch from 370-2, applied upstream.
 +  * Prefer luit over x11-utils in Recommends (Closes: #904572).
 +  * Update copy of XTerm FAQ to revision 1.407 (dated 2021/12/20).
 +  * Update years in debian/copyright.
   -- Sven Joachim <svenjoac@gmx.de>  Fri, 25 Feb 2022 19:06:55 +0100

debian/control

@@ -122,7 +122,7 @@ Depends:
   xbitmaps,
   ${shlibs:Depends},
   ${misc:Depends},
 -Recommends: x11-utils
 +Recommends: luit | x11-utils (<< 7.7+6~)
  Suggests: xfonts-cyrillic
  Provides: x-terminal-emulator
  Description: X terminal emulator
@@ -134,7 +134,7 @@ Description: X terminal emulator
   This package provides four commands: xterm, which is the traditional
   terminal emulator; uxterm, which is a wrapper around xterm that is
   intelligent about locale settings (especially those which use the UTF-8
 - character encoding), but which requires the luit program from the x11-utils
 + character encoding), but which requires the luit program from the luit
   package; koi8rxterm, a wrapper similar to uxterm for locales that use the
   KOI8-R character set; and lxterm, a simple wrapper that chooses which of the
   previous commands to execute based on the user's locale settings.

debian/copyright

@@ -4,7 +4,7 @@ This package was debianized by first time by David Martinez Moreno
  Upstream sources: http://invisible-island.net/xterm/xterm.html
 -Copyright 1997-2021 by Thomas E. Dickey
 +Copyright 1997-2022 by Thomas E. Dickey
  Copyright 1999-2000 by Steve Wall
  Copyright 2013,2014 by Ross Combs

debian/local/xterm.faq.html

@@ -19,7 +19,7 @@
   * ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF   *
   * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.            *
   *****************************************************************************
 -  $XTermId: xterm.faq.html,v 1.402 2021/09/05 19:50:30 tom Exp $
 +  $XTermId: xterm.faq.html,v 1.407 2021/12/20 23:57:10 tom Exp $
    -->
  <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
  <html>
@@ -769,17 +769,31 @@
      control.</li>
    </ol>
 -  <p>The control sequences document lists a few controls which
 -  xterm does not (completely) implement, e.g.,</p>
 +  <p>The <a href="">"ctlseqs/ctlseqs.html">control sequences</a>
 +  document lists a few controls which xterm does not (completely)
 +  implement, e.g.,</p>
    <ul>
 -    <li>key-repeat</li>
 +    <li><a href="">
 +    "ctlseqs/ctlseqs.html#h4-Functions-using-CSI-_-ordered-by-the-final-character-lparen-s-rparen:CSI-?-Pm-h:Ps-=-8.1E68">
 +    key-repeat</a></li>
 -    <li>enabling LEDs other than scroll-lock</li>
 +    <li><a href="">
 +    "ctlseqs/ctlseqs.html#h4-Functions-using-CSI-_-ordered-by-the-final-character-lparen-s-rparen:CSI-Ps-q.1CB1">
 +    enabling LEDs</a> other than scroll-lock</li>
    </ul>
 -  <p>None of the other terminal emulators implements those
 -  either.<br></p>
 +  <p>Those are not implemented in xterm because all X applications
 +  share the same keyboard (see <a href="">
 +  "manpage/xterm.html#h2-EMULATIONS">manpage</a>), and <a href="">
 +  "https://www.x.org/releases/current/doc/man/man1/xset.1.xhtml">xset</a>
 +  is the proper tool for changing auto-repeat. The <a href="">
 +  "https://github.com/ThomasDickey/old-xterm/blob/d448c6d7373c3bc3df4c75e815baa1e645462893/charproc.c#L1048">
 +  X10R4</a> xterm did implement key-repeat, but the feature was
 +  removed in <a href="">
 +  "https://github.com/ThomasDickey/old-xterm/blob/6bf1714f13b7811c3e28d186bfc9942d971edd9b/charproc.c#L1048">
 +  X11R1</a>. None of the other terminal emulators implements those
 +  either.</p>
    <table border="1" summary=
    "Comparing against the control sequences document">
@@ -3503,7 +3517,7 @@ keycode 22 = 0xff08
    "/xterm/xterm.log.html#xterm_271">patch #271</a>), and does not
    have this problem.</p>
 -  <p>As of February 2014, I am able to verify that AIX and HPUX
 +  <p>As of February 2014, I was able to verify that AIX and HPUX
    have updated to modern xterm, e.g.,</p>
    <ul>
@@ -5429,7 +5443,7 @@ Shift &lt;KeyPress&gt; Insert:insert-selection(SELECT, CUT_BUFFER0) \n\
      &ndash; both by the display and the selection logic.</li>
    </ul>
 -  <p>As of 2010, a few other terminals do implement this feature.
 +  <p>As of 2010, a few other terminals did implement this feature.
    But the reason that it's been low-priority is that it's of very
    limited usefulness when copying between terminal sessions (and
    for that matter, from other clients).</p>
@@ -6257,12 +6271,12 @@ configure --disable-imake --disable-narrowproto
    <h4><a name="compiz_bugs" id="compiz_bugs">Why is the text in the
    wrong place?</a></h4>
 -  <p>Are you using Ubuntu? This is a frequently-reported problem
 -  for Ubuntu users. With other systems, it can occur (as of
 -  September 2012), but is less frequent. But it has been an issue
 -  with Ubuntu since 2008.</p>
 +  <p>Are you using Ubuntu? This was a frequently-reported problem
 +  for Ubuntu users. With other systems, it could occur (as of
 +  September 2012), but is less frequent. But it was an issue with
 +  Ubuntu since 2008.</p>
 -  <p>There are several related symptoms, e.g.,</p>
 +  <p>There ware several related symptoms, e.g.,</p>
    <ul>
      <li>text may be the wrong size</li>
@@ -6349,34 +6363,37 @@ configure --disable-imake --disable-narrowproto
      Ubuntu #1007722 - xterm doesn't display all the information</a></li>
    </ul>
 -  <p>Since the problem is not in xterm, all I can do is to help
 +  <p>Since the problem was not in xterm, all I could do is to help
    forward those bug-reports to whatever package owns
 -  <code>compiz</code>. What these have in common is that someone
 -  has written code which is tested against only a small subset of
 -  the X protocol.</p>
 +  <code>compiz</code>. What these had in common is that someone
 +  wrote code which was tested against only a small subset of the X
 +  protocol.</p>
 -  <p>Looking for solutions (since compiz is not being fixed), it is
 -  possible to disable compiz. The means for doing this vary with
 -  time. Aside from pointing to the root cause of the problem, there
 -  is little advice that is useful.</p>
 +  <p>Looking for solutions (since compiz was not being fixed), it
 +  was possible to disable compiz. The means for doing this varied
 +  with time. Aside from pointing to the root cause of the problem,
 +  there was little advice that was useful.</p>
    <ul>
      <li>For instance, <a href="">
      "http://force.subcritical.org/xterm_under_compiz/">this
 -    comment</a> by Eric Williams suggests that the problem can be
 -    worked around by setting xterm's <code>borderWidth</code>
 +    comment</a> by Eric Williams suggested that the problem could
 +    be worked around by setting xterm's <code>borderWidth</code>
      resource to zero.</li>
 -    <li>other comments suggest turning off the "desktop effects" or
 -    "animation".</li>
 +    <li>other comments suggested turning off the "desktop effects"
 +    or "animation".</li>
      <li>On my machines using the default <em>Ubuntu</em> desktop, I
 -    can see misbehavior easily in Ubuntu 12.04 using <a href="">
 +    could see misbehavior easily in Ubuntu 12.04 using <a href="">
      "/vttest/vttest.html">vttest</a>. However, Ubuntu 12.04
 -    provides <em>Ubuntu&nbsp;2D</em>, which does not show those
 -    problems (and is noticeably faster).</li>
 +    provided <em>Ubuntu&nbsp;2D</em>, which did not show those
 +    problems (and was noticeably faster).</li>
    </ul>
 +  <p>Ubuntu dropped <em>compiz</em> in 2017. Its replacement (GNOME
 +  shell) has fewer bugs.</p>
++
    <h3 id="my_xdefaults-id"><a name="my_xdefaults" id=
    "my_xdefaults">Sample .Xdefaults Color-Settings for XTerm</a></h3>
@@ -7124,7 +7141,7 @@ Warning: Actions not found: ignore, scroll-back, scroll-forw
    <p>Revisiting in 2018 &mdash;</p>
 -  <p>Regarding documentation, the situation is not as good as
 +  <p>Regarding documentation, the situation was not as good as
    reported earlier. The problematic documentation was not even part
    of the "official" GNOME Terminal, but was an add-on by a Debian
    developer, adapted from GNOME Terminal's online help. The
@@ -7239,7 +7256,7 @@ There are no docs for the gnome-terminal command line options.
    </blockquote>
    <p>The assertion about GNOME-Terminal's support for
 -  &ldquo;any&rdquo; persists in its <a href="">
 +  &ldquo;any&rdquo; persisted in its <a href="">
    "https://packages.debian.org/sid/gnome-terminal">package
    description</a> in Debian as of 2018:</p>
@@ -8388,9 +8405,8 @@ configure --help
    compiler warnings. For gcc, that is done with the "gcc-stricter"
    script which you can find <a href="">
    "/scripts/readme.html">here</a>. The X libraries have a
 -  longstanding issue which has been ignored so far (as of
 -  mid-2012). To work around this (and get useful warnings), I apply
 -  this patch:</p>
 +  longstanding issue had been ignored (as of mid-2012). To work
 +  around this (and get useful warnings), I applied this patch:</p>
    <blockquote>
      <pre class="code-block">
@@ -8428,6 +8444,11 @@ configure --help
    "http://lists.x.org/archives/xorg-devel/2010-May/009052.html">mailing
    list</a>, but as you can see, there was no response.</p>
 +  <p>Finally, I spent the requisitve time to integrate the
 +  change&mdash;and complete the process of transforming the
 +  <a href="">"xtoolkit/"><em>X Toolkit</em></a> documentation from
 +  nroff to docbook/xml.</p>
++
    <h2 id="report_bugs-id"><a name="report_bugs" id=
    "report_bugs">How do I report bugs?</a></h2>