From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Bakke Subject: bug#32458: Acknowledgement (SDL SEGFAULTs on foreign distro) Date: Mon, 15 Oct 2018 21:19:09 +0200 Message-ID: <87woqjggr6.fsf@fastmail.com> References: <4990ca3b-560e-6049-4f54-d597bf8a2dc4@yahoo.de> <87ftz8pxde.fsf@fastmail.com> <87a7npiks2.fsf@fastmail.com> <28717b9b-bf01-cfe2-56d8-6be1cbbb1da8@yahoo.de> <875zyci980.fsf@fastmail.com> <8e38e782-a577-bcbd-0838-0efbc42a5f21@yahoo.de> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58153) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gC8PN-0007wb-Hn for bug-guix@gnu.org; Mon, 15 Oct 2018 15:20:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gC8PK-0007Jq-CR for bug-guix@gnu.org; Mon, 15 Oct 2018 15:20:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:47191) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gC8PK-0007Jh-61 for bug-guix@gnu.org; Mon, 15 Oct 2018 15:20:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gC8PJ-0001LY-Sr for bug-guix@gnu.org; Mon, 15 Oct 2018 15:20:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <8e38e782-a577-bcbd-0838-0efbc42a5f21@yahoo.de> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Tim Gesthuizen , 32458@debbugs.gnu.org --=-=-= Content-Type: text/plain Tim Gesthuizen writes: > On 22.08.2018, Tim Gesthuizen wrote: >> This bisect passed without a single skip. It reports that the bug was >> first introduced by 5318b103ff277efbac248a066d162589a9083baa (which is >> the first commit after a larger merge). > > Maybe you missed that mail. The problem is that reverting the commit > does not solve the bug on the current master branch. So I am searching > for a good way of finding another bug through bisecting. This would mean > that I would need to apply a patch of some form to make sure that the > libepoxy problem is fixed before running the bisect script again. > This is why I tried to rebase the master branch to not include commits > updating libepoxy. Oh, I see! Sorry for the confusion. One thing you can try to narrow down the search space is to try reverting that commit at different points in the repository. For example, I believe 5318b103f was merged in 49b6dc2b4. If reverting on top of 49b6dc2b4 does not work, it means the (other) problem was introduced somewhere between 5318b103f^..49b6dc2b4. For starters, can you try to revert 49b6dc2b4 on top of 0d6f84aab and e0c9aed82? My gut feeling says the first should work and the second not :-) > I hope my problem is more clear now. Maybe there is another way that is > just too obvious and simple. If you don't have a good idea on how to do > it, I will do the bisect again and do an input rewriting for the package > I am building to use the old libepoxy and not the one of that revision. > This will probably involve tons of package rebuilding so I am open for > other approaches. Input rewriting seems like a great workaround, however tedious. It would be good to provide better tooling for these kinds of cases (maybe even "guix bisect"). --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQTck4iltADvsyxsIHHh9++BT5KhDgUCW8ToLQAKCRDh9++BT5Kh DlOmAQDNn3MRTIogtAqs3l943IlNoyfo9pA5CAD02OmXk47uKgEAkoNDiB79M4XF H3yviHnr5tTE8m4Sxq62tniyQ400tgA= =C4ty -----END PGP SIGNATURE----- --=-=-=--