[SOLVED] Bisecting a live package?

[NilPointer]

I'm trying to help mesa developers to trace down a regression bug. They asked me to bisect the mesa, if possible. How can I do that in portage-friendly way, using mesa-9999 package? Is there any better way than manually bisecting by setting EGIT_COMMIT?

[toralf]

[Ant P.]

Start a bisect on the git repository in $PORTDIR/git3-src/mesa_mesa.git directly, and use `git bisect run` with a script that sets EVCS_OFFLINE=1 (and maybe EGIT_COMMIT="$(git describe --tags)").

[NilPointer]

Yes, Ant P., that sounds like most straightforward way. Thanks!

[shoober420]

I don’t mean to necrobump, but this post is the first result when googling “gentoo bisect 9999”.

You can also add “EGIT_COMMIT=[SHA1HASH]” to the foo-9999.ebuild, put it in your localrepo, create the manifest, and bisect that way as well.

[Hu]

You can, but that seems like a lot more trouble and less flexible than the mechanism that Ant P. proposed. If you put the candidate commit in the ebuild, you need to re-manifest the ebuild at every step. Are there advantages to setting it this way, rather than doing as Ant P. described?

[shoober420]

Yes, I needed to do a manifest after each commit change. There’s no advantage to it, but it is another way if someone doesn’t have any scripts to bisect with.