<sadiq[m]>I have a few GNOME packages to be updated, but depends on glib 2.54.
<rekado>htgoebel: guix package -K foo; cd /tmp/guix-build-foo…; guix environment foo; make check
<htgoebel>rekado: I already do something similar. This works find for "simple" setups. But as soon as I need to add dependencies, it become complicated. E.g if I want to try dbus or shared-mime-info, which require additional config vars.
<rekado>htgoebel: I forgot to mention “source environment-variables”;
<rekado>all the vars that are set at build time are recorded there
<htgoebel>rekado: I just notice that you are using "guix environement". This might do the trick. I'm using plain bash
<efraim>how many of the old sun machines are sparc and how many are x86_64?
<thomasd>htgoebel: if that still doesn't work (I had this problem for kdevplatform: tests run in the "guix environment", but not in the build environment), you could also 1) build the package with guix environment 2) create a new package with (source (local-file "your/local/build" #:recursive? #t)) 3) in this new package, only run the test phase. I haven't actually tried this yet, but it should allow quick experimentation with the test phase
<thomasd>(environment variables etc). This was my next idea to finally fix those kdevplatform tests
<htgoebel>thomasd: This is a cool trick :-) I'll try that
<rekado>texlive-union should behave the same as the big texlive-texmf package, but it doesn’t
<rekado>with texlive-union it builds fixed-size font files in $HOME, but with texlive-texmf it does not.
<rekado>it shouldn’t need those files — they are not part of texlive-texmf, and all variables are set such that it can find the metafont source files as well as the compiled tfm files.
<rekado>I really don’t like texlive and how it is managed; confusing perl scripts, plain text files as databases, automatically run tools triggered by kpathsea…
<htgoebel>thomasd: For the trick with the new package I assume you deleted phases configure and build?
<thomasd>htgoebel: as I mentioned, I didn't actually try it myself yet, but yes, I'd just run 'install and 'check (for those KDE packages which will only run their tests after every object is in its target location)
<rekado>looks like even the new emacs 25.3 leaks memory in shell buffers.
<Apteryx>So I went there: ~/.cache/guix/pull/pjmkglp4t7znuugeurpurzikxq3tnlaywmisyr27shj7apsnalwq$ and issued 'git log -1'. The result is: a9925374b0691eb551b0383ec88f110fc54f9fae, which makes sense (I guix pull a day or 2 ago).
<nickdee>Has anyone reported issues with guixsd 0.13.0?
<nickdee>i tried running it twice last night per the instructions on the site, but it failed both times in different places
<nickdee>the first time, it couldn't build ghostscript because it was missing a few .o files
<nickdee>the second time, it continued past that but couldn't install grub because it couldn't find mkinfo.sh
<nickdee>(at least, I think that was the file name, it was some mk*.sh file)
<nickdee>if folks do have workarounds, i'm happy to perform them, otherwise I'll try to investigate later this week.
<nickdee>got to run, but I'll check the logs later. thanks for your help #guix!
<noob>hello i need to install grub with blockchains i have use --force option but now the computer prompt to grub rescue
<niebie>The difference for my case is that libreoffice is non functional without this package installed
<niebie>The menus themselves are missing fonts, which means you just guess at what buttons do
<niebie>I understand why you wouldn't propagate for desktop-service, since that makes no assumption on the system you are using to login
<niebie>for instance, I use dwm and don't need that font package
<niebie>but since libreoffice is usable in any desktop and requires this package to render its menus, i don't see why propagating would be bad
<wigust>niebie: If you make a package with ‘pack’ for another distro, you don't need fonts to be included.
<rekado>Apteryx: it actually leaks. Killing the buffer does not free memory.
<wigust>niebie: And as I remember ‘font-gnu-freetype-ttf’ required for other graphical applicatoins too. So it's first thing after installing GuixSD without desktop environment service.
<niebie>LibreOffice is the only application I run that required it to function
<niebie>icecat needs it for some particular web pages, but the gui works without it
<niebie>The three graphical applications I have installed right now are emacs, icecat, and libreoffice. For emacs, it doesn't need this font package at all. For icecat, it improves some webpages by having it. And libreoffice needs it for all menus.
<wigust>I think ‘lightweight-desktop-service’ for Window Managers would be great.
<wigust>Instead of propagating packages with fonts.
<niebie>So the main argument I heard against this is that you don't want to include the fonts when packaging libreoffice for other systems
<wigust>niebie: Also there was an issue with icons in GTK+ applications and dialogs. I installed Adwaita icons manually. So, again instead of propagating it everywhere in GTK+ applications, just make a ‘lightweight-desktop-service’.
<niebie>wigust: To me it makes sense that if you want a 'pack'ed package to be completely self contained that fonts would be included
<niebie>wigust: from what I understand, that is their main use - to create a completely standalone, system independent package
<Apteryx>is using gexps already supported in build package definitions?