<lfam>Weird, it just succeeded after several failures
<NiAsterisk>cmake complained about: CMake Error: The source directory "/tmp/guix-build-panopticon-0.13.0.drv-0/panopticon-0.13.0" does not appear to contain CMakeLists.txt. but, the repo and 0.13.0.tar.gz contains a CMakeList.txt in the folder "doc". I think I can instruct cmake to use CMakeList.txt in that folder?
<lfam>NiAsterisk: Did you try grepping for something like 'CMakeList' in gnu/packages? Maybe case insensitively?
<mark_weaver>so what happens is this: two different cairo packages are built: first one is built without poppler, then poppler is built using that first cairo, and then the final cairo is built based on that poppler.
<rekado>roelj: we decided on the details of a configuration and have an offer but there's a delay due to issues with SATA initialisation on the board. As soon as these issues have been solved by the supplier we can make the order.
<mark_weaver>the hydra-server processes get bloated and need to be killed periodically, but when I kill them, if they were in the middle of serving a NAR, a truncated NAR ends up in the nginx cache :-(
<bavier>but it says pyc files are created as part of installation?
<bavier>or is it the C extensions that are binary distributed?
<paroneayea>I think they're binary distributed but I'm not sure
<paroneayea>> Python needs a package format that is easier to install than sdist. Python's sdist packages are defined by and require the distutils and setuptools build systems, running arbitrary code to build-and-install, and re-compile, code just so it can be installed into a new virtualenv. This system of conflating build-install is slow, hard to maintain, and hinders innovation in both build systems and installers.
<paroneayea>> Wheel attempts to remedy these problems by providing a simpler interface between the build system and the installer. The wheel binary package format frees installers from having to know about the build system, saves time by amortizing compile time over many installations, and removes the need to install a build system in the target environment.
<bavier>I wonder what a package checkoff list for guix would look like
<bavier>might be difficult to get the popularity list
<paroneayea>maybe autotools would have made some of the same mistakes back in the early 90s, but there was no reliable general public access to the internet back then, so you couldn't just assume you could pull down the source on the fly :)
<lfam>I do think we recently broke something in our VM tools though. The QEMU images are being created with a filesystem label, meaning that if you don't set the label on first boot, you can't boot again
<mark_weaver>but I guess we should try updating libssh2 to 0.7.3, add libssh2-0.6 for use by guile-ssh, and also temporarily keep a version of libssh2 identical to the current one (such that a rebuild is not needed) for use by curl until we can get hydra to do the 3000+ rebuilds needed for that.
<lfam>mark_weaver: For libssh, I think we should update libssh to 0.7.3, and find the latest version of libssh that guile-ssh can use and create that. For libssh2, we should update it to 1.7.0, while keeping the old version to smooth out the transition.