From: Marius Bakke <mbakke@fastmail.com>
To: guix-devel@gnu.org
Subject: gtk-doc build failure
Date: Thu, 01 Dec 2016 22:01:27 +0100 [thread overview]
Message-ID: <87wpfjs6s8.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
[-- Attachment #1: Type: text/plain, Size: 1474 bytes --]
Hi,
gtk-doc is not building in current 'master'. It seems to stem from
python-build-system merge. I ran a bisect but had to skip a bunch of
commits due to subversion build failure. To save anyone else the
trouble, here is the result:
There are only 'skip'ped commits left to test.
The first bad commit could be any of:
f3b98f4fec43c951a9e28c67561395992bf190a7
00e10c6e674f0f292d5821bc4a513d48f4d1d164
5d8549328483978bf04dd2c710ef6a06614d4776
5c31f4aa7c11fcf720c0ce0e26d55788e2df1044
f54d6bacbf46f5f25d3f7a5bea578879ee865be1
e442246a2f5f73b2484adb340b53d3a0018636b1
f210e94432fcb8d6c03589287833f7594f270522
891a843d5184f696618af6fcbb9791ef6b574504
d8013ee221bd599474340899ffb5974796091955
15e57f576291d9233ab25e1614c6218579db170a
b41a05ce497d5ecc682cf46ce61aa2215193f9f6
c1019287a4aab55ebffab4710b9a85b6c9f1b7ed
f22efa0152356da4755241de3726b6a254b49d11
b002f964bb3d69c77856ea7dcadfe82383050512
e7881f3db4dfddf46c3cd61ee684a2efd629ce1b
a2ff4f0240f0fac484836bb8ffb2f86917369666
dae73d9b9a4db932e8c7c1b7607981dc6cb401a5
482d95918e2a9de05ee224d979c15759e54febf0
5f7565d190cf380b7bae2ce12dba38aff98c4eb9
328bb95d3507682f5e06fb2880c632252f59ee57
46bcdcc287ecfc1db8b7a0429e72517f407b580d
7db40bce58e149ecb541d295e01cfbfe953d39a3
f2516de2fc7459d8ceed1779f0f24840075d08d6
b3e8b4bd0f390784c710944c9962a0e13b25ed02
We cannot bisect more!
Here is a good commit for testing (the build log of the test PDF is
different): aaf75c890b5242d3ab3671766226bc53ab07049a
Digging further... :-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next reply other threads:[~2016-12-01 21:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 21:01 Marius Bakke [this message]
2016-12-01 22:51 ` gtk-doc build failure Marius Bakke
2016-12-02 13:11 ` Hartmut Goebel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wpfjs6s8.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).