<ulfvonbelow>how much storage do you reckon that a full-source distribution of guix would take? That is, a guix checkout, and the source of every package it could ever try building, including the hex0 bootstrap binary
<luke-jr>ulfvonbelow: well, I'm not going continuously, but I just started on it today
<luke-jr>I'm also doing it *fully* from source... no seed binaries
<ulfvonbelow>I don't know how you can get much more "fully from source" than the full-source bootstrap rooted in that 357-byte program, but best of luck
<luke-jr>I did try that first, but couldn't get anywhere
<luke-jr>maybe it just lacks documentation on how to use it, idk
<ulfvonbelow>Is it possible to run a (small-scale) software heritage archive locally? That sounds kind of like what I'm after
<lilyp>at the very least you can run your own cuirass which will be queried before the actual SWH
<lilyp>as for cloning SWH, I think you'd have to ask them on how to do that
<lilyp>(interestingly there is #swh, but it appears quite empty)
<ulfvonbelow>I know there have been times in the past where I used 'guix download' to download something and put it in the store, and then when an origin with the same hash was needed it re-downloaded it, presumably because the name used was different.
<andreas-e>The configure flags look suspicious. There is nothing one could install into /gnu/store/lib or /etc. Although this is not precisely what the error message complains about.
<impulse2000>Its because we cant modify other packages, once they are installed. i was just wondering if there was a way i could have the evolution-data-server pick up on the libraries. maybe a symlink?
<andreas-e>What do you mean by "pick up on the libraries"? Adding packages as an input is usually enough so that newly compiled binaries can link with their libraries.
<impulse2000>how evolution-ews works and the dataserver is that the dataserver needs the path to the evolution-ews package libraries in its /gnu/store/rsrqi4bbvc0c6ps8jzzs8n13gbsha999-evolution-data-server-3.46.4/lib/evolution-data-server/addressbook-backends/ folder.
<impulse2000>So i was just thinking i need to modify the script to copy the files within its own namespace. instead of trying to overwrite the evolution-data-server.
<andreas-e>Okay I see. Somehow you try to write to the folder belonging to a different package. This is indeed not possible.
<impulse2000>Yea, so i am trying to make it only write the libraries to its namespace. i am using the nix package as a guide:
<jpoiret>roptat, pukkamustard: I've been looking at the coq patches (sorry for taking my sweet time). If we're dropping the coq-core coq-stdlib modularity, then we can also drop the env variables and the custom patch on coq I think.
<jpoiret>Also, I've been packaging coq-lsp, and for that I need to update some jane street ppx packages. Is there a policy of updating all jane street packages at the same time? I'm extremely unfamiliar with ocaml and its ecosystem
<Rovanion>pinoaffe: In 65 the comments "There has been no new release tag since july 2022" should probably be ammended with a timestamp of when you checked.
<nckx>jpoiret: Could you ELI5 what the problem is with those gexps? I'm quite ignorant about this stuff. My expectation is that it would pull all compressor packages into only those builders that import (gnu build compression). Is that correct? Naive?
<nckx>Also, I'm looking at (gnu build chromium-extension). Should I be wary of its example?
<jpoiret>it shouldn't be too bad to add support in guix graph to graph modules directly not just packages
<jpoiret>nckx: i'd say it's naive. Basically the rule of thumb is that build-side modules should not use g-exps, because g-exps is an abstraction that's only available in the host Guix
<jpoiret>in the build side, you just have bare Guile
<jpoiret>g-exp are for staging code, but the code that runs in the builder is *already* the staged code
<hwpplayer1>Does GNU Guix have a category like mentors like Debian ?
<jpoiret>in the builder you should rather only reference the executables themselves, and ensure that if some builder code calls them, that the compressors should be available in the environment
<jpoiret>that's why I was advocating for a bit of a rewrite, where you'd provide the functions in (gnu build compression) with the list of compressors it may use (with their paths), and also add some g-exps in (gnu compression) that wrap around that by providing something like #~(do-something-with-compressors #$(default-set-of-compressors)) and the
<jpoiret>possibility to tweak them depending on what you want
<jpoiret>that's a bit more involved than just moving stuff around though :p
<jpoiret>hwpplayer1: there is a mentor team, if that's what you're asking
<nckx>So modifying the running udev binary/package isn't enough?
<lechner>after reconfiguring the SAS cards in my server, the equipment refused to start properly. i think one issue was that opensmtp uses the interface name in its config. the issue was that the BIOS had assigned another interface number (eno2 or so). upon reflection, i found that the use of BIOS-enumerated interfaces names is inconsistent with the declarative configuration we celebrate in Guix. To my surprise, we do not support MAC-based
<nckx>At first I read it as ‘whether to use “listen ::” or “listen enospc1” is an irrelevant matter of taste’ but then as ‘even if that would work [and be more robust] it's a matter of principle to support this use case’.
<nckx>Re: duplication: you know you can use ‘VAR = value’ and ‘$VAR’ in smtpd.conf? It has some annoying limitations, like not working in quoted strings AFAIK (no ‘pki foo cert "/etc/tls/$DOMAIN.pem"’ ☹) but is still handy.
<rekado>I always compile after rebase, because I don’t trust myself
<apteryx>mirai: we have time; you can send ot upstream first then we can apply a v3 :-)
<lechner>does wip-postfix still drop HAS_DEV_URANDOM? it probably should use it instead of /dev/random, since it's likely to run on equipment without a lot of user events
<janneke>i don't have a (pressing) need for running mailman and exim is working great, so...
<tricon>lechner: you have me curious re: OpenSMTPd as someone that used to run Postfix (w/ Dovecot as MDA).
<mirai>apteryx: right, its just that the last enblend release was years ago
<mirai>though the repo seems to be getting activity I don't expect the situation to change anytime soon (there's also that their README says that autotools is the “standard” build-system and cmake is experimental yet cmake is what's getting the most attention)
<mirai>I'm guessing they're planning to switch to cmake sometime in the future
<mirai>nckx: re listening on an ip, there's one class of addresses you would be leaving out: the scoped/link-local ipv6 ones
<podiki>welcome! you can search for some commits that added it for other packages (off the top of my head is a simple one I did a while ago, rofi, look for rofi or rofi-calc)
<podiki>wone: failure of ansel i believe is because the custom phases of darktable now need to be modified (name change); doing that it builds, i'll update my definition and should just submit it here finally
<apteryx>mirai: doesn't matter the amount of activity, what is important is to get the issue out there and add a reference to it :-)
<apteryx>lilyp: is there anything I can do to help make Emacs 29 happen in Guix?
<lechner>tricon / i'd be happy to help you to possibly convert to OpenSMTPd, if you like. the configurations are super short and super clean, plus i have not seen any unexpected behavior---with minimal mental overhead for a year and a half, on six pieces of equipment
<tricon>lechner: that's quite kind of you. i may take you up on that and pick your brain. i actually get to start from scratch since hackers wiped my VPS providers systems (tiny host overseas). going to self host now with some mini-PCs and multiple locations.
<lechner>congrats! i just got rid of my final linode on Aug 31
<tricon>lechner: very nice! my current approach is to build these mini PC servers for friends to host and to offer a trade in the form of setting up offsite backups for them. do you have redundancy with your new setup?
<ngz>sneek later tell andreas-e: I have an idea. At the moment it is not possible for `guix shell' to extend a TEXMF tree without providing a full tree. For example `guix shell texlive-foo -- pdflatex file.tex' will not add `texlive-foo' to the available packages. However `guix shell texlive-bin texlive-foo -- pdflatex file.tex' will. My suggestion is to add `texlive-libkpathsea' as a propagated input for all TeX Live packages.
<mirai>name it as online-pharmacy-cialis.tar.rar and see how far it will go
<cage>Hi! I am trying to write a package definition but the upstream source needs a lot of tuning to works, I have found some patch files from debian that should fix the issues, my question is, there is a way (an is good practice) to apply the patches during the package building and where to store them?
<apteryx>cage: hi! if the patch is useful and hasn't been merged upstream yet (has it been forwarded to them?) then it makes sense to carry it
<apteryx>the <origin> record can take a 'patches' field
<nckx>I'd love to but the machine is currently unreachable. This likely due to being at my parent's house behind a crappy SOHO router, not due to mdraid 😉
<nckx>I'll poke about in git but I don't think I have it there.
<lechner>what happens when you boot with a drive missing, please?
<nckx>Ah, well. In my case, the drive vanishes after a few months and gets kicked out, but it ‘reappears’ on reboot so that's not something I've personally tested.
<nckx>I suspect you'll tell me it fails because Guix sets suboptimal options, and I'll eagerly believe you if so.
<nckx>(There are also some bad sectors in the exact same spot on all 6 drives that were somehow *created* by Linux, because they are on a swap partition boundary, just to keep things weird. I have no idea how.)
<lechner>bad sectors get remapped automatically unless that's an IDE drive from 1995
<nckx>It's how bcachefs denotes multi-device file systems, and it's a ‘file’ that doesn't exist. Guix used to really not like this. I've patched out the worst, now it merely demands ‘--skip-checks’ when reconfiguring. Sorry, this is becoming irrelevant to your point.
<vagrantc>if i run "guix time-machine" ... and then run it again ... should it cache the results? it seems to always "Computing Guix derivation for ..." regardless of weather anything has changed between invocations
<cage>my plan is to patch the debian sources with their patches, then modify the include directives (for zlib and i suspect for all the other libraries the package uses like libjpeg) and generate a new patch, finally try again with building
<cage>but it is a lot of work and i am a bit tired now :)
<lechner>i was going to say thank you for all that hard work
<lechner>those bundle removals should really be a configuration option from upstream
<Sleep_Walker>is it possible to configure channels in system configuration so it can be used in `operating-system`?
<Guest69>Docker works but it seems that docker-compose is broken. I get "docker.errors.DockerException: Error while fetching server API version: HTTPConnection.request() got an unexpected keyword argument 'chunked'". Do you have that problem as well?
<the_tubular>You should give Podman a try if you're facing issue with Docker.
<the_tubular>Or you could try tcpdump and check what's in that packet that the API doesn't like