Re: bin/56496: etcupdate(8) merge formatting issue

[Robert Elz <kre%munnari.OZ.AU@localhost>]

The following reply was made to PR bin/56496; it has been noted by GNATS.

From: Robert Elz <kre%munnari.OZ.AU@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: bin/56496: etcupdate(8) merge formatting issue
Date: Thu, 18 Nov 2021 03:20:06 +0700

     Date:        Wed, 17 Nov 2021 18:45:01 +0000 (UTC)
     From:        Hauke Fath <hf=40spg.tu-darmstadt.de>
     Message-ID:  <20211117184501.C31D61A923A=40mollari.NetBSD.org>
 
   =7C  There wasn't any change in the X resources. It was simply 'update =
 -9=20
   =7C  from a June build, run etcupdate, and notice negative change in fo=
 rmatting'
 
 I'm still not sure how you're actually doing this testing, it would help
 if you were clearer (I mean, the actual steps you take, rather than which=
 
 version you're trying).
 
 That is, are you taking a CD/DVD/USB-stick (or similar, including netboot=
 ing)
 to an empty system (nothing more than firmware and blank storage) and boo=
 ting
 it and continuing from there, or ???   I suspect not that, as you're upda=
 ting,
 not installing, but how exactly?   This might matter - including what the=
 
 previous system was.   It might also matter whether or not you have reboo=
 ted
 after the update before running etcupdate.   The actual sequence of event=
 s
 when you're testing the different versions (do these tests all start from=
  the
 same exact starting environment - system in identical state, etc?)
 
 Further, I wasn't suggesting that you are deliberately changing anything
 yourself, but perhaps something in the system, after the updates, could
 be different.   There might be many differences - different versions of t=
 he
 termlib database, different system startup scripts, different almost
 anything (including the default Xresources files).
 
 Something is configuring the xterm tabs in some cases, and not others.  S=
 ince
 some of us can (occasionally) see this happen, and others cannot, it is m=
 ost
 likely something in the local setup that we have - even though that somet=
 hing
 might not be obvious.
 
 It might depend upon some (seemingly unrelated) X resource setting for ex=
 ample.
 
 kre