<marusich>dftxbs3e, my pleasure! By the way, I just committed the changes you made, to wip-ppc64le. I made minor additions (a comment, and copyright lines); you can see with "git diff" from your own repo, if you're curious. Other than that, it all looked good. You don't need to put things like #f in quotation marks in commit messages, but it seems different people quote things differently in the git logs anyway, so there is little precedent...
<sneek>Welcome back marusich, you have 4 messages!
<sneek>marusich, dftxbs3e says: the "guix" package failure is weird, certainly looks like a bug in the test suite. It may be because powerpc64le-linux isnt a "supported" one (needs --with-courage)
<marusich>In other words: 1) Make changes to guix.m4 etc. so we "officially" support powerpc64le. 2) Run make update-guix-package (and commit any changes). 3) Run make guix-binary.powerpc64le-linux.tar.xz
<marusich>Awesome that we were able to build guix in that way! Hopefully soon we can get the "make guix-binary.powerpc64le-linux.tar.xz" command to work, since I believe that is the standard way a release binary is made.
<marusich>I noticed a test failure in Guix, but I haven't investigated it yet. tests/containers.scm, I believe it was. Something about the procedure that should run something in a container, always returning #f.
<marusich>Regarding guile-static-stripped, that's unfortunate. Do you have more details? Could you open a bug report?
<marusich>vagrantc_, the name "powerpc64le-linux" is the "guix system" name, which is basically an arbitrary string, but by convention in Guix (and Nix, I think) we try to make it sound like the GNU triplet.
<marusich>It is not the same as the GNU triplet. I believe the actual triplet used in gnu-build-system builds is generally powerpc64le-unknown-linux-gnu.
<marusich>but it took me a while to understand that the choice of nix system name is arbitrary, and that we could call it anything, really. So if we ever built a powerpc64 port that used a different abi, I guess we'd have to give it a different name, like ppc64wtf-linux
<marusich>I still find the triplets to be a bit confusing, but i have come to learn and accept that many different packages and bits of code are all participating in loose coordination, and that they are not generally referring to some single list of authoritative names.
<marusich>i thought at first that these names were defined somewhere clearly
<marusich>it seems like that is not true, although I'm sure there are places in glibc or elsewhere that happen to list parts of these names
<sneek>hapster, nckx says: hapster: I'm afraid the Nix importer is prone to bitrot, and might require a running & configured nix-service-type to even work. In short it's probably the most temperamental of the mainline importers.
<hapster>nckx: thanks, good to know about the nix importer, always thought I was miserably failing at some point ;-)
<hapster>when I create a package, there need be a license thing in the beginning (in which I insert "my" copyright). Is there an emacs "M-x guix-" command for this?
<efraim>I went down a package upgrade rabbit hole, turns out I'm the last person to touch jrnl, back in march 2016
<efraim>I don't know if that counts as stable or abandoned
<pkill9>does anyone know of a wayland compositor that is closer to an emacs interface? basically somethign as close as exwm for wayland
<esper>Hi, I installed Guix System with default installer. Chose my language but now LibreOffice and IceCat menus are still in English. They have dictionaries for my language but menus are still in English so I am confused.
<pkill9>and I can write it in guile or common lisp or whatever
<cage_>Hi! I am trying using guix for a common lisp software that uses asdf and autotools to build and install the package, i am using gnu-build-system and the process fails the phase when building the executable with sbcl the compiler says that can not find asdf (the CL building system), any idea?
<dftxbs3e>cage_, try exploring existing packages in GNU Guix repo, I don't know how to do that.
<cage_>dftxbs3e, thank you! i tried chacking stumpwm and pgloader, in fact this was very useful to write the package definition file but i am just stuck with this issue that i believe is the last one :)
<brown121407>How do you guys test a new system service you added somewhere in gnu/services/... ? I'm not having any luck with the -L option for `guix system reconfigure' or doing a reconfigure from ./pre-inst-env, but maybe I'm doing it wrong...
<mdevos>the printer is booting. I also have access to a non-colour printer. In case the colour printer doesn't work, would a non-colour printer be ok?
<wdkrnls>For my intended usage I need to print photos. I saw that Ricardo Wurmus was using a Brother laser printer quite successfully and I used to be able to use a Samsung SCX-4200 laser printer with Guix, but that broke down.
<mdevos>Any idea how to resolve this: ‘Printer ‘HP-Photosmart-Wireless-B109n-z' requires the '/gnu/store/[snip]-cups-2.3.3/lib/cups/filter/hpcups' program but it is not curently installed. Please install it before using this printer.'? I have added (extensions
<mdevos> (list cups-filters escpr hplip brlaser) to cups-service-type
<wdkrnls>The HP support page suggests that your b109n printer should have worked out of box with hplip 3.9.10 and above :(
<wdkrnls>One thing I'm confused about is "driverless" printers. It seems like it should be possible to use "modern printers" without installing drivers by communicating using a protocol called IPP and that this is supported by CUPS.
<wdkrnls>What are the foomatic-filters and should they be included into your extensions list? I was reading that they were used to automatically generate PPD files for some printers.
<wdkrnls>I don't know why that would have anything to do with hpcups, though which looks like it has a lot to do with borderless printing which would be essential for printing photos.
<wdkrnls>but anyway, thanks again for looking into this mdevos :)
<bdju>to whoever packaged bpytop: thank you, but where are the themes?! there is only 1 instead of 14 like on my other machines. I thought they were part of the main package. the guix bashtop package also has the themes
<lf94>bdju: sometimes package definitions have multiple outputs, maybe it's in another package?
<lf94>(Search for bpytop brought up nothing for me!)
<lf94>Can someone tell me if this line of thinking is sound? I have a "project" I want to package: it's a wiki. This project just consists of the actual content and the index generator which is a shell script. Would I just use the gnu-build-system? So I would just create a Makefile for my project just to run the index generator?
<mroh>bdju: I haven't packaged bpytop (but bashtop). The package doesn't have themes inside, so I think that's a bug. I will try to take a look, if you don't mind, please make a bug report.
<lf94>I would then want to "deploy" this project to my VPS - certainly I *wouldnt* use guix deploy for this, but probably a custom channel?...
<lf94>(Or maybe something simpler like guix copy IIRC, whatever the command is to install a package on another system which is local)
<bdju>mroh: what are you saying exactly? file a bug because the bashtop themes are there and they shouldn't be..? not gonna do that. I have both bashtop and bpytop installed, fyi, so if you didn't package bpytop, someone else did. was a recently added (last few days) package.
<bdju>or maybe you're saying in your bashtop you don't see the other themes
<bdju>looks like I have 10 themes in bashtop on guix
<lfam>The grafting workflow is like this: in a single commit, create a new variable postgresql-13.2 that inherits from postgresql-13 but changes the version and source. Add a replacement field to postgresql-13 that uses postgresql-13.2
<lfam>There isn't a schedule for staging at this point. We just finished the last staging cycle
<lfam>I would guess it will be a few months at least. Maybe we'll combine it with core-updates. It kind of depends on the state of the build farm and how many people want to work on it
<bdju>anyone around that's used qmk on guix? I'm having issues building the default keymap for my keyboard. I've only used the web configurator before now so my qmk-related stuff isn't all working right yet, I guess.
<fnstudio>(not sure why i linked to that website instead of the official guix channel, but anyway)
<fnstudio>i think i understand why the executables need to be wrapped but i'm not sure i follow all the steps in that section and i was wondering if there could be any more standard, slightly simpler way of doing all this
<fnstudio>where "all this" = creating a guile library, make it a CLI app, package everything in a autotools project, make it installable via guix
<fnstudio>the problem is (if i understand it correctly) that .go files get installed in /usr/local/lib/guile/3.0/site-ccache
<fnstudio>and .scm files in /usr/local/lib/guile/3.0
<fnstudio>which, by default, are not in the GUILE_LOAD_COMPILED_PATH and GUILE_LOAD_PATH