<Guest30>vivien: if the web services you're using have nothing to do with `info.at`, it might be a local configuration issue causing *.eu to be appended to the request. The reason you're hitting that IP is beacuse `info.at` is a TLD registrat for *.eu, and has `org.eu` (the domain name, not tld) set to wildcard redirect to their site
<vivien>Guest30, I suspect that, but it’s weird that it only happens for git.savannah.gnu.org and not savannah.gnu.org.
<vivien>(the final dot is here to end the sentence)
<Guest30>can you try a few other "*.org" domains? Preferably with 2 subdomains, like git.savannah.gnu.org?
<vivien>Maybe that’s because I query git.savannah.gnu.org a lot and it gets cached in weird places
<pkill9>why does guix create sooo many grafts when you're updating etc?
<vagrantc>Fare: you might have to get fiddly defining modules in your initrd ... upstream linux tends to change those names around all the time between major versions and guix initrd doesn't dynmically probe kernel modules
<nckx>(There's a ‘statistics’ action that does, if you're interested.)
<Fare>vagrantc: I'm failing to boot into the image from guix.gnu.org. I tried cross-installing from debian, but the reconfigure fails towards the end. Do you have a working recipe to share?
<lechner>vivien / do you have a /etc/resolv.conf from the router?
<vagrantc>Fare: i could dig up a config that worked last year ...
<Fare>I was hoping to turn the pinephone into my "secure device".
<Fare>But I can't even get it to boot into a decent console.
<apteryx>mbakke: I think I've gotten to grips with modify-defconfig & thus probably customize-linux
<apteryx>long story short: it's defconfig-centric, and if you use CONFIGS you must carefully replicate the changes that menuconfig would have made, taking care of dependencies (make savedefconfig to compare)
<AwesomeAdam54321>I think the IceCat --with-system patches are very useful for other systems and should be applied to the source
<apteryx>nckx: you have to pass a table to invalidate to the invalidate nscd action I think
<apteryx>we should put bash completion to all our shepherd services
<AwesomeAdam54321>It's most likely one of the things that needs to be done for IceCat 102 to be released officially
<vagrantc>apteryx: i don't understand c04528d2a2597d79278833f3607c806278253446 where you renamed u-boot-am335x-boneblack ... there used to be a u-boot-am335x-boneblack configuration upstream, and this package adapted that one to fit in the same space as the old upstream one
<vagrantc>apteryx: adding the -evm in the name just makes it a whole new thing, rather than a stand-in for an old thing ...
<vagrantc>though honestly, i'd be surprised anyone could usefully use the beaglebone black with guix, has no more than 500MB ram...
<vagrantc>maybe something in the way the raspberry pi patches refactored some of those packages made it strange?
<Parnikkapore_m>Hi, I'm running Guix on a foreign distro and am using fish as the default shell. How should I patch config.fish etc. to initialize $PATH etc.
<tex_milan>Hello, how to get path to installed package in shell? I know I could ls /gnu/store/*PACKAGE*/ but that lists all incarnations, not the one really used. I'd like some simple command like guix show-path PACKAGE. Any idea?
<unmatched-paren>Parnikkapore_m: you probably shouldn't use fish as the default shell with guix
<flypaper-ultimat>rpana: if you want to use it in your manifest file, the info page `info "(guix) Defining Package Variants"` is useful, especiall the the part about `options->tranformations`. There you'd do in place of `with-branch`, `with-commit`.
<rpana>:flypaper-ultimat: thanks for the advice, very useful
<AwesomeAdam54321>How do I use old style inputs with new style inputs? All the examples of including patches as (native-)inputs have all of them listed in the old style
<AwesomeAdam54321>I got an error that rust was an invalid input for icecat because it's in the new style while the patches that came before were in the deprecated style
<lechner>axet / Guix is so isolated, you probably do not need chroot
<lechner>AwesomeAdam54321 / i think you just list the variables, instead of the labels plus
<efraim>rekado: that machine is long gone. I could probably spin up a VM with the liquorix kernel and test it out there.
<efraim>well the machine physically is in my drawer but doesn't boot anymore, and I've repurposed the OS drive since then
<winter>anyone know how I'd change the Linux build in the install image so that it's built with CONFIG_EFI_STUB? not really sure where to begin
<winter>(it doesn't boot under GRUB+aarch64 otherwise)
<lechner>i am surprised we do not build it like that already
<lechner>but you should not need the EFI stub with Grub; only with something like rEFInd
<winter>GRUB checks for the existence of a few magic numbers
<axet>@lechner I need chroot not for isolation, but for installing fresh OS. That the way I install debian: using debootstrap
<lightbulb>axet: Error: "lechner" is not a valid command.
<winter>which we currently don't build it with the flags to get them
<winter>lechner: i have absolutely no clue, i'm building on aarch64 for aarch64.
<rpana>Another question, how can I make this simple guix-home config https://paste.debian.net/1264839/ pull my Emacs configuration from a git repo? I assume using a function alternative to `local-file`?
<nckx>lechner: Could the global parsing of @-‘commands’ be disabled? Newcomers mistakenly typing ‘@nick’ is too common.
<rpana>Or in other words, is there a function to clone a remote with guix? Something like the `fetchFromGithub` from Nix...
<lechner>yeah, sorry about that. it's my first time running a bot
<pkill9>does anyone know how to possibly fix the fact that gnome-shell needs to be restarted for launchers to update after changes to the guix profile? i'm guessing gnome-shell watches the real path from symlinks, instead of just watching the symlinks themselves
<lechner>plus, as i mentioned yesterday, Limnoria loads plugins dynamically. i believe it means i have to create a custom package definition to make sure that the SOAP module needed by the plugin (but not available in the bot as we ship it) is available http://paste.debian.net/1264845
<lechner>in addition, the recommended way to configure Limnoria is via online commands, which is not declarative at all
<rekado>lechner: FYI you can use the graphql endpoint on issues.guix.gnu.org to fetch issue info
<lechner>rekado / maybe this is not the time to mention it, but after years of responding to bugs in another distro i have two suggestions. first, any chance, guix might embrace bug identifiers in base64 or a similar encoding? second, can we pick another shorthand notation besides #XXX?
<lechner>i.e. another symbol, or set of symbols like /XXX/
<rekado>lechner: this is outside of our control. The numbers are what debbugs provides and uses internally.
<rekado>there’s no good reason why these should be numbers only (debbugs treats them as opaque identifiers), but that’s not something we can change.
<rekado>(we = downstream users of a shared debbugs instance)
<lechner>there is a one-to-one mapping we could use unilaterally, and i am hoping we may not use debbugs indefinitely
<rekado>currently mumi’s database is not precious; it is generated entirely from debbugs messages. As long as we’re using it just as a frontend I’d rather not introduce precious data that we have to keep safe.
<rekado>especially for bug URLs we want to guarantee that identifiers never disappear
<rekado>mumi is not currently set up for this kind of operation.
<rekado>if mumi ever handles incoming email it may introduce different identifiers, but until then I’d rather keep it stupid.
<nckx>winter: It took a while to build (QEMU), but I really can't find any evidence of the kernel lacking EFI stub support. GRUB not booting kernels without it is also extremely implausible. I think you're barking up the wrong tree.
<itd>civodul: Interesting, thanks! Can R packages depend on another R package of a specific version (range)? (From a quick glance at the repo it looks like "no". I find that surprising.)
<efraim>jbv1[m]: "random binaries/libraries" downloaded from the internet don't work with Guix, so we need to use our own binaries so they know what to link against. Also we want to provide our own binaries and not use "magic binaries" provided by someone else.
<efraim>by replacing them we get rid of that possibility. Also I don't remember looking at Overrides.toml before
<jbv1[m]>I meant that we could use overrides.toml to point the binaries to /gnu/store instead of patching the wrappers
<abhicherath[m]1>heya! I'm using guix on a foreign distro (debian), and after something a bunch of my icons are broken. I narrowed it down to debian's libc being too old for guix's librsvg (from journalctl /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /gnu/store/cq4i5h2lnz143y66lfsm3662b9nx13x9-librsvg-2.50.7/lib/librsvg-2.so.2)
<abhicherath[m]1>I'm not fully sure how to solve this problem. the first approach I considered was to find and get rid of whatever package I have in my profile with gdk-pixbuf as a propagated input
<abhicherath[m]1>but i have like 30-40 packages, and I don't know guile well enough yet to figure out how to check if any of them propagates it
<abhicherath[m]1>and I'm not entirely certain that that's the source of the issue anyway
<lechner>Also, I was conservative with the versions being updated to because the golang ecosystem is developing rapidly and our build system is still at 1.17. Should I reach for the highest possible versions? May I see somewhere if any of the 919 rebuilds fail? If not, how do I run them at home, please?
<morganw>Is there a good beginner guide to update (just bumping a package version and testing it) a Guix package on an existing Guix system that has that same package installed?
<lechner>morganw / we will help you here. which package, please?
<morganw>emacs-org-msg, it has been a version behind for some time
<morganw>When I have dabbled with a guix checkout and geiser before I have managed to lockup the machine whilst it tried to compile the checkout.
<lechner>morganw / how do you use Guix, please? Are you on a foreign distro, or do you use Guix Home?
<morganw>Guix as the OS, pretty much all packages installed through Guix Home.
<lechner>great! how do you start Emacs? Do you use EXWM?
<morganw>EXWM but no display manager. I'm just starting an X session with `sx`.
<lechner>great. that's all very similar to what i have, btw
<lechner>except that i never got sx to work. are you using any tricks?
<lechner>morganw / thanks for that; i will try it later
<morganw>I mainly worried about accidentally triggering recompilation. I can run `make` in the checkout in advance and let it run for a while though, if that is what everyone else is doing. But it seems a bit strange to do that when I'm only interested in one package.
<lechner>i do not currently use a lot of the Emacs packages that come with Guix. I am trying to decide how to make sure emacs-org-msg is available to your Emacs. maybe we worry about that later.
<lechner>what do you mean by "triggering recompilation" please?
<civodul>nckx, lechner: changing links to ftpmirror LGTM, please go ahead :-)
<lechner>morganw / just copy the (define-public ...) stanza into a file called guix.scm. That file should be located in a convenient place
<attila_lendvai>civodul, hi, i think something has changed in shepherd. a call to INVOKE (which calls SYSTEM) that used to work, now doesn't find the executable anymore. i suspect somehow the PATH environment is not propagated somewhere.
<morganw>lechner: OK. Bear with me, I just need to get something to eat so I'll probably be back in 15 minutes.
<attila_lendvai>the reason is that if it'll get in quickly, then i don't need to duplicate the change in my channel, which is not easy because of how the macro-level stuff and packages interact. i need to copy the whole machinery, not just the changed macros.
<attila_lendvai>if it's not probable to get in fast, then i'll need to think about how to proceed
<lechner>morganw / yes! to avoid confusion at this this stage, i also recommend to prefix the variable (but not the "name" field) with "my-". please also enter the name of that variable starting with my- at the end, so the file evaluates to it
<lechner>morganw / then you can run guix build -f guix.scm insert the "actual hash" from the error message into the appropriate place in your file, and run the build command again
<morganw>It is suggesting I need to add (use-modules (guix packages)) on the first invocation. Should I add it?
<lechner>yes. you will actually need a bunch of those to cover all the prerequisites, as well. sorry
<lechner>nckx / should i prepare a merge request? I'd like to appear proactive
<jas4711[m]>hi guix! i'm looking for some help packaging a new perl module. i've written a package description that works with 'guix build' but I had to use (arguments `(#:tests? #f)) to make it build. if I remove that, the 'make test' phase fails because it can't find the newly built perl module (I think). Ideas? The guix package definition is here: https://gitlab.com/-/snippets/2475459
<lechner>jas4711[m] / will you please post the error?
<jas4711[m]>the error message i get is this: t/test.t .. Failed to load PCSC library at /mnt/jas/src/pcsc-perl-1.4.14/Card/../blib/lib/Chipcard/PCSC.pm line 247.
<jas4711[m]>i'm not sure what it is searching for, maybe the perl module or the shared library?
<jas4711[m]>re perl-pcsc: the package builds some C code that tries to load the libpcsc shared library I think. So this is probably a search path issue
<lechner>jas4711[m] / yeah, those are a common issue
<morganw>lechner: the package is now built with the updated hash
<lechner>morganw / okay, congratulation! you graduated from the package builder class. now the challenge is to make that package available to your emacs
<jas4711[m]>lechner: yes, I found it is a dlopen call that fails. is there some other perl package that has this? i'll try to find one to look at
<nckx>I got one ‘invalid’ TLS certificate whilst testing. I wasn't running verbosely, so I didn't see which server. It was almost certainly because I pick my own roots, but let's keep an ear out for any reports of ‘failed downloads’ in the coming days.
<lechner>jas4711[m] / does the call use an absolute path, or does it rely on LD_LIBRARY_PATH being set elsewhere in the build system?
<lechner>morganw / my top choice would probably be to reconfigure your home environment to use your updated package. the reason is that you rely on Emacs so early on and cannot easily use 'guix shell' to bracket the invocation
<lechner>jas4711[m] / are you doing this inside a guix shell that makes the library available?
<lechner>morganw / you can do this by cutting and pasting your update package definition into your home.scm. just install the package together with the others. i do not use the ->specification mechanism and refer to the variables instead. how is your file set up, please?/
<efraim>jas4711[m]: we normally add the package as an input and patch the dlopen to give it the full path so we don't have to rely on pcsc-lite being installed somewhere
<jas4711[m]>lechner: i tried 'guix shell pcsc-lite -- guix build -f security-token.scm' but same error.
<jas4711[m]>efraim: do you have a pointer to some other perl package that does this?
<lechner>jas4711[m] / efraim may be better positioned to help you from here, especially because i have to bolt soon
<jas4711[m]>efraim: thanks! i found it and will try to learn how it works
<morganw>lechner: I've just got a list of strings for package names, following (map (compose list specification->package+output)...
<lechner>morganw / yeah, i think you may have to append my-... to the list created by 'map', but i'm not sure
<morganw>I can try to start a new emacs instance inside emacs after updating the home configuration. Do you think that is feasible?
<lechner>morganw / you may be more experienced with Emacs than I. that sort of thing has not worked out well for me in the past. i personally might start Emacs in a text terminal instead, i.e. without 'sx' except I would to so inside a guix shell -f guix.scm
<nckx>You can then use the F5 (up) & F6 (down) keys to switch tabs.
<nckx>I'm sure that was well received & understood.
<johnabs[m]>Guest30: No, it does not. And yeah, I restarted emacs, and even ran pkill to make sure no daemon process was running. Interestingly, certain things show up in `C-h f ` for guix, such as guix-about, but when I press enter, I get the same "No such file or directory" error for guix-about. Do you think I need to use (use-package! (or require) guix-emacs) in my config as well?
<Guest30>probably should have been but 3 lines isn't too bad on spam :-)
<johnabs[m]>Oh okay, good :) (Also, did it not show up as 3 separate lines? It looks like that on my end, but i'm using element to connect to the IRC channel, which may be doing some weird stuff with formatting)
<johnabs[m]>(Oh, or did you mean use Enter, rather than Shift-Enter, so it showed up as 3 separate messages?)
<Guest30>nah your 3 lines came through separately, you're good
<johnabs[m]>Hmm, similar bug now that I've installed emacs-cider, actually
<Guest30>johnabs[m]: anything weird going on in your init.el?
<Guest30>only difference between our machines is I'm running Emacs 29
<johnabs[m]>Guest30: Actually, I think I may have found the issue, but we'll see. I'm using doom emacs, and I found a bug when trying to sync, which may be interfering with my other packages, give me a hot second to try to fix that, and I'll be back xD
<paul_j>Evening all! Is there anything I should be aware of when it comes to installing quicklisp on guix? I have installed it as I would on other distos, and allowed the .sbclrc to be modified to initialise it each time. When I use sbcl from the command line, it works, but in my (functioning on other systems) stumpwm config it is saying "package QL does not exist" during the initialisation
<paul_j>I can't see quicklisp as a package available in guix directly, although there are other packages used for processing the download stats.
<lechner>paul_j / your stumpwm may not have the QL package as an "input"
<lechner>the packages that do work may not be same ones that are installed in your profile, i.e. they could be different store paths
<paul_j>lechner: do you mean when I install stumpwm?
<lechner>yeah, Guix is different from most other operating systems
<paul_j>It is currently in a list of packages installed in the base profile
<lechner>yeah, they may not see each other's prerequisites. all of them are tied down to the versions with which the packages were built, and no other
<paul_j>How do I make quicklisp and input for it? I didn't do anything specific for sbcl (installed at the same time as stumpwm), apart from the usual install of quicklisp in my user profile, and that works as expected.
<lechner>the sbcl in your user profile and the one used by stump is not necessarily the same. even if it is, not all installed modules may be visible from each. multiple versions of all those things may be installed. they are only accessible via their absolute path, via symbolic links in your profile, or via some special environment variables (such as $PATH)
<paul_j>So I understand the basic structure of guix and the way it links files, but I am surprised that there may more than one version of sbcl installed. I am not currently using any manifest, and install everything for the system in one file. Therefore everything is updated at the same time, and *should* be consistent (IMHO!)
<paul_j>I have had guix on a laptop for around 12 months. My aim is to make this my primary laptop, so I can stop using gentoo on my other laptop. I have gentoo on my desktop, and will consider changing that as well in the future, but I need to have a better grasp of how guix works before I make that step.
<lechner>or if that yields too many modules ls -ald /gnu/store/*-sbcl-*/bin/sbcl
<paul_j>As I said, I get that these are in the store, but I don't get that the sbcl version used by stumpwm may be different from that invoked in a terminal since I update them all at the same time currently. If I was using manifests, and updated these at different times I can agree. I guess I am back at my original question, since even if I have different versions of sbcl being invoked, I still have one .sbclrc and one quicklisp install in my
<paul_j>home directory, so everything should work as expected with stumpwm. Hence my original question about the best way to install quicklisp in guix, since it isn't currently a guix package (as far as I can tell).
<lechner>sorry, i cannot help you with quicklisp, and you are likely correct that your sbcl versions are the same
<paul_j>Or, should I not be using quicklisp, but installing the packages directly through guix. Similar to avoiding use-package in emacs for installing packages, installing them directly instead.
<paul_j> I had better go and check the cookbook - there might be more in there...
<lechner>you may be able do to either, but it may be hard to mix the installations. i personally prefer official packages when possible. i even package and maintain my own stuff, which is trivial in Guix. In never run sudo curl | bash but will work with cabal or npm for a little while when needed
<paul_j>I'm quite happy to do it "the guix way" - just sometimes you need to dig to find what that way actually is :). I packaged my own configuration of dwm in a personal channel, and like very much the approach. I am hoping to get enough free time this holiday period to finally get the laptop in a fully usable state, and then make use of it in the new year.
<paul_j>Anyway - I need to go and walk the dog! Thanks for your help lechner - I'll catch you round again, I'm sure!