[MacPorts] #47815: xorg-server-devel 1.17 displays in false colours on PPC Tiger and Leopard (Mac OS X 10.4.11/10.5.8)

[MacPorts]

#47815: xorg-server-devel 1.17 displays in false colours on PPC Tiger and Leopard
(Mac OS X 10.4.11/10.5.8)
--------------------------------+--------------------------------
  Reporter:  Peter_Dyballa@…    |      Owner:  macports-tickets@…
      Type:  defect             |     Status:  new
  Priority:  Normal             |  Milestone:
 Component:  ports              |    Version:  2.3.3
Resolution:                     |   Keywords:
      Port:  xorg-server-devel  |
--------------------------------+--------------------------------

Comment (by jeremyhu@…):

 Replying to [comment:8 Peter_Dyballa@…]:
 > Replying to [comment:6 ryandesign@…]:
 > > Well before you can install and launch it, you have to configure and
 compile it, like MacPorts would,
 >
 > This is quite clear. And if I can't find out how port would do this job,
 I can simply force port to start again and copy&paste environment
 settings, the configure invocation, and then start to make the same
 target.
 >
 > > or you have to use the commit hashes `git bisect` tells you to modify
 the portfile to use that hash, then use MacPorts to rebuild the port.
 >
 > I have no idea what to do with a "hash"… except maybe in Perl! But this
 "modify the portfile" sounds very interesting. This would allow me to just
 invoke `port install xorg-server-devel` over and over again, after each
 launch of the X server and decision to classify the build as good or bad.
 How does this actually work? Is there some log of such a session
 available?

 See my discussion about how do do this in
 https://lists.macosforge.org/pipermail/xquartz-dev/2015-March/003866.html
 which includes the commands you would need to invoke.  In that example,
 the commit has is 35dc7c75150733dbcef8a18b6796f49a7c48ebee and you would
 set it on the git.branch line in the Portfile.

 From the email:

 > git clone ssh://git.freedesktop.org/git/xorg/xserver.git
 > cd xserver
 > git bisect start
 > git bisect bad e572bcc7f4236b7e0f23ab762f225b3bce37db59
 > git bisect good cff12936275db2f71f6d24f9ea0985a0d14af454
 >
 > It will then report something like this:
 >
 > Bisecting: 169 revisions left to test after this (roughly 8 steps)
 > [35dc7c75150733dbcef8a18b6796f49a7c48ebee] Merge branch 'modesetting-
 import' into master

 Hope fully the above is clear

 > So try 35dc7c75150733dbcef8a18b6796f49a7c48ebee and then run 'git bisect
 good' or 'git bisect bad' as appropriate and try the next one until you've
 determined what commit introduced the problem.

 I assume this is what you don't understand.

 Starting with a checkout of 1.16.99.1_2 or 1.16.99.1_3 (try one; if
 patches don't apply, try the other one), edit the Portfile and change the
 git.branch line to 35dc7c75150733dbcef8a18b6796f49a7c48ebee.  Then build
 and install the port:
 {{{
 sudo port -v -s -n upgrade --force xorg-server-devel
 }}}

 Depending on if it works or not, run 'git bisect good' or 'git bisect bad'
 in your git checkout to get the next commit hash to try.  If there are
 *other* errors that prevent you from testing that version (eg: build
 failures you don't know how to fix or crashes that happen before you get
 to test), use 'git bisect skip' to mark that hash as unknown.

-- 
Ticket URL: <https://trac.macports.org/ticket/47815#comment:10>
MacPorts <https://www.macports.org/>
Ports system for OS X