Re: [qubes-users] qubes-builder failing to build template

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Fri, May 27, 2016 at 01:34:35PM -0700, patie...@terminalmoronicy.com wrote:
> I'm trying to build an installation ISO based on Qubes R3.1, but with the
> kernel swapped out (I'm using a qubes- patched 4.5.5 kernel).
>
> I have successfully built installation ISOs before, but not with v4.5
> kernels.
>
> Qubes builder keeps failing in template-local-fc23. The tail of
> build-logs/template-fc23.log looks like:
>
> $ tail build-logs/template-fc23.log
> Package dnf-1.1.9-1.fc23.noarch is already installed, skipping.
> Dependencies resolved.
> Nothing to do.
> Complete!
> -> Installing package groups...
> 28 files removed
> Last metadata expiration check: 0:00:14 ago on Fri May 27 18:50:16 2016.
> Error: libreoffice-math
> Makefile:47: recipe for target 'rootimg-build' failed
> make[1]: *** [rootimg-build] Error 1
>
> If I rerun "make template-local-fc23" repeatedly, it keeps failing on
> different packages (i.e. "libreoffice-math" became "libreoffice-impress"
> after another attempt) - I'm assuming it is making some progress each time.

This is upstream bug (triggered by recent dnf update - 1.1.9-1):
https://bugzilla.redhat.com/show_bug.cgi?id=1339742

Just pushed workaround for it:
https://github.com/marmarek/qubes-builder-fedora/commit/1b6ea836d0556437946e94a4835f0ee3f962f498

Theoretically it should be fixed by dnf 1.1.9-2 (they've reverted the
change triggering the bug), but haven't tested it yet.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXTWWHAAoJENuP0xzK19cs7r8H/RK9mYFX4jU3MOoDmiN+RYlA
d9PrLgR34TDaDfH17GmZsZozHNczfJ/EyiD+8Fqc/A6s9nMOCN3Q/VikeBL2vOgA
ZuNnHYuCUnPQ6Md4b5JMZ8tavP7Gm2Sqir9FaEi8Q+bmnI1yLZKAisXWVqyuN/oU
w31i6oSIysF/BVPiZiGpoDQR2esXj9opnXxTk4zKQErnG1RLXPm/ltZdc1FmBczq
emTHcNsfeVW5AOaLkOfqmu//nTM+piX3ng80kDOtMyXxuOJOgIhwtQS0JbPDEzpx
em/agF3LnsDo9RICtY9jGZTs3sXsGnjDChl/1JMspKDsVUMU4mjDlRLmroCN/tc=
=Gaxe
-----END PGP SIGNATURE-----

[patie...@terminalmoronicy.com]

The problem didn't resolve by re-trying the build (which maybe would be expected to pick up the new dnf?), but I can confirm your workaround did the job - thanks!

-tom