unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "J. R. Haigh (re. Guix)" <JRHaigh+ML.GNU.Guix@Runbox.com>
To: help-guix@gnu.org
Subject: Repeated build failure of GDK-Pixbuf 2.38.1
Date: Tue, 28 Jan 2020 05:02:10 +0000	[thread overview]
Message-ID: <20200128050210.73aaead7@jrhaighs-debian-x200> (raw)

Hi all,
	I've been having the following build failure during ‘guix upgrade’:
[…]
building /gnu/store/js4ix1yhhhk2j184bc19ynq3cap1f3a5-gdk-pixbuf-2.38.1.drv...
building /gnu/store/qjnfwlnhs8x4dn23wzsa0815fc4kknms-llvm-7.0.1.drv...
\builder for `/gnu/store/js4ix1yhhhk2j184bc19ynq3cap1f3a5-gdk-pixbuf-2.38.1.drv' failed with exit code 1
build of /gnu/store/js4ix1yhhhk2j184bc19ynq3cap1f3a5-gdk-pixbuf-2.38.1.drv failed
View build log at '/var/log/guix/drvs/js/4ix1yhhhk2j184bc19ynq3cap1f3a5-gdk-pixbuf-2.38.1.drv.bz2'.
cannot build derivation `/gnu/store/crrrvbdh0bhg305l70fxyx04mwpz5ff7-gdk-pixbuf+svg-2.38.1.drv': 1 dependencies couldn't be built
building /gnu/store/wyib6fc7l9y6rgs66mpj9x3dpblkx93z-wayland-protocols-1.17.tar.xz.drv...
building /gnu/store/5nfc4y0i7bgz65fdcsfwvrmn113gr3yl-xauth-1.0.10.tar.bz2.drv...
cannot build derivation `/gnu/store/8h7ps1kdf6glgf0wags3ywsxg9d266gv-gajim-1.1.3.drv': 1 dependencies couldn't be built
guix upgrade: error: build of `/gnu/store/8h7ps1kdf6glgf0wags3ywsxg9d266gv-gajim-1.1.3.drv' failed
[…]

I think that this has been the case for all but the most recent pull generation that I haven't GC'd, as my only package generation is the one that remained after a GC that I did early December:
Generation 37	Dec 09 2019 01:44:33	(current)
  glibc-utf8-locales	2.28	out	/gnu/store/94k5w17z54w25lgp90czdqfv9m4hwzhq-glibc-utf8-locales-2.28
  tiled	1.2.3	out	/gnu/store/pijdpwzmk27xxi9ay6h0n5069m8x4lfx-tiled-1.2.3
  gajim	1.1.3	out	/gnu/store/7ba6j1r1ns2fa71dnba4m3lvi3s2hll5-gajim-1.1.3
  nss-certs	3.43	out	/gnu/store/6w65nzbc3ah30y5kr4zx9rcgknpjr1f5-nss-certs-3.43
  youtube-dl	2019.04.30	out	/gnu/store/idg86l68r4qia0l0qs2r0w7vg7gf2189-youtube-dl-2019.04.30
  darcs	2.14.2	out	/gnu/store/f9zs0z6kmd4j60p8443ki2dgw07gwm7x-darcs-2.14.2
  gajim-omemo	2.6.28	out	/gnu/store/sz4fryksqlcihz8ln4j05dpm3jzf9jc5-gajim-omemo-2.6.28

I'm pretty sure that no ‘guix upgrade’ since that GC has succeeded, else I'd have more than 1 package generation. ‘guix pull’ has been succeeding as I have several pull generations:

$ guix pull --list-generations 2>/dev/null | sed --regexp-extended --quiet -- "s/^    (commit: .*)$/\1/p"
commit: bc587eb178799ccb9bd051f8f46569e1673a9991
commit: e3388d6361dedabb2f6df9cdd5cc98e6cac7f457
commit: 8c5cde2546b8bcca2285d5fa6545adeb5076b74e
commit: 762867313cb26bee32fafb6821a7ef7584c537c2
commit: 704719edade1368f798c9301f3a8197a0df5c930
commit: d63e0ee78d00ff1ccef9f74307b237b7e46ea15d
commit: 47ea2ad196a41a3c3de3e5fa970b6881495c0e8f
commit: fcb510c541e83291ea6682cba87020a913c64914
commit: 7ee8acbb76bd440a8985a4b2a20b75521c6853ed

If I understand correctly then the GDK Pixbuf build regression was introduced between commits bc587eb178799ccb9bd051f8f46569e1673a9991 and e3388d6361dedabb2f6df9cdd5cc98e6cac7f457, sometime between Wednesday 11th December and Wednesday 22nd January, which narrows down to 6 weeks where I didn't use Guix.
	I hope the detail helps you fix the regression.

Regards,
James R. Haigh.
-- 
4 days, 3 hours, and 58 minutes left until FOSDEM 2020 (Saturday)!
5 days, 3 hours, and 58 minutes left until FOSDEM 2020 (Sunday)!
Wealth doesn't bring happiness, but poverty brings sadness.
https://wiki.FSFE.org/Fellows/JRHaigh
Sent from Debian with Claws Mail, using email subaddressing as an alternative to error-prone heuristical spam filtering.

             reply	other threads:[~2020-01-28  5:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-28  5:02 J. R. Haigh (re. Guix) [this message]
2020-01-28  8:06 ` Repeated build failure of GDK-Pixbuf 2.38.1 Efraim Flashner

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=20200128050210.73aaead7@jrhaighs-debian-x200 \
    --to=jrhaigh+ml.gnu.guix@runbox.com \
    --cc=help-guix@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.
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).