<eloyesp>Ok, I've just installed guix for the second time (the first time it didn't work), on an external SSD drive, mi idea was to be able use it on different computers, but the main system config seems to hardcode `/dev/sdX` on the bootloader section... I'm afraid it could overwrite the bootloader on the host machine, does anyone have any idea if there is
<sneek>s34n was in #guix 4 months ago, saying: (I think. I can't look at history right now and I'm brand-new to guix).
<Brendan[m]2>anyone else have trouble with mailto links? im in sway without a desktop environment and when a click the reply to ... button on mailman in icecat, it opens icedove but then does nothing. if i click the same button in ungoogled-chromium, it works slightly better, it opens a new mail window, the To and CC are all empty
<Brendan[m]2>im not actually sure thats a "mailto" link but some kind of post request thing
<Brendan[m]2>i wouldn't touch guix core stuff on my own. also, im not sure what is required to submit to core-updates. some people just seem to be working on it whenever so i dont know what the game plan is
<civodul>i was under the assumption that it was "being handled by someone" :-)
<Brendan[m]2>maybe it is, since people likely dont comment when there is no program and its just in the works. i pinged you and rekado about your old bug report for wrap-script. he said hed look into that one. as for the wrap-program, Danny asked a question, i clarified, and then no response since.
<Brendan[m]2>Part of the reason i wanted it in core-updates, even if it was buggy, was that i can exploit the build server to test rebuilding the world
<Brendan[m]2>otherwise id have to start burning my laptops cpu for a few days trying to do that to see if anything breaks
<leoprikler>I'm p sure wrap-program affects more than 1200 packages, so it belongs to c-u either way ;)
<ani>I am new when it comes to submitting patches through email. For my first patch, I copied all the body from the .path file and pasted in mail. Also from the subject line, I copied the subject and pasted it in the subject of my email. To be on the safer side I also attached a patch file to the email. What is the write way? I thought submitting through email is the easier way than submitting it to git email.
<civodul>and i'll be around the week before as well
<ani>yes, so I know GNU, FSF are totally different things. I started following them since my teenage. But I didn't know how to connect with it. I thought GNU is very limited and if you want to contribute then you will have to be expert at something, and I was wrong. And started exploring and using GNU and Free Software every possible time. Since then many of my friend see me as Free Software Activist. So they do ask me about Free Software and Open source etc. I have
<ani>prepared a mail for them, If you guys suggest me somethign what I need to improve in that information then that will be good.
<ani>zimoun: Yes, magit helps because emacs rocks. :)
<zimoun>civodul: no holidays when we speak about releasing. ;-)
<zimoun>ani: if you use Magit, then it is really easy to submit patches: stage (s), commit (c c and rewrite), format-patch (W c C-m b master c) and then outside “git send-email –to=… 0001-blabla.patch” with the configuration of in the Example section https://git-scm.com/docs/git-send-email
<bonz060>Hi guix! How would you get the r/ship between inputs using guix-graph? I want to find out which package has, as a dependency, some other package.
<ani>So I guess now I am ready to make R package, patch it and then send the patch. But before that I have few doubts
<zimoun>rekado_, janneke: saddly the Magit authors do not seem interested by git-send-email support. Because there are some “closed” issues asking for the support (checking before open another one). However, GitHub pull-request is now supported. :-p
<ani>zimoun: I am using building from git guide. Have downloaded latest git clone
<ani>and now did run "guix environment guix --pure"
<rekado_>#~ introduces a G-expression, #$ is like an unquote
<rekado_>when this is compiled #$nix is replaced with the prefix directory name of the built “nix” package.
<jlicht>nefix: the `rc` field of bash-home-type should be processed using mixed-text-file, so you can try file-append: (bash-configuration (rc (append default-bashrc (list "\n" (file-append nix "/etc/profile.d/nix.sh")))))
<jlicht>you do need to have the `(guix gexp)' module in scope for this to work, as well as the nix package definition in `(gnu packages package-management)'
<jlicht>nefix: rekado's #~(string-append ...) snippet is cleaner, don't forget about newlines (or ;) though
<zimoun>civodul: with this new “target” date, does the proposal of string freeze for the manual and translation is extended or transfered?
<ani>I am inside ./pre-inst-env, and now I am trying to write recipe? For that I want to build a packaged named abc so I click on that I look at its metadata, now I am using one of the package template /guix/build/r-build-system.scm to get reference and edit appropriate values
<ani>leoprikler: Yes, its for outreachy but I don't want to contribute for sake of Outreachy. So what you have suggested I will do it? That will enhance my overall knowledge of using and developing guix. What I was doing was to write recipe and then go as defined in "2.1.1 A hello world package". Like downloading source code, then signature and then doing guix package --install-from-file=my-hello.scm
<mfg>ani: -r recursively generates the package definitions for the package you specified an dit's dependencies - it doesn't know about #:prefix definitons one might have used in source files so it can't know that the license should be prefixed, you need to add that :)
<nckx>PotentialUser-35: It's used only when the source is a zip file which is rare.
<ani>mfg: So what next, shall I commit and send the patch?
<nckx>nefix: Certain types are self-evaluating (I think that's the word), so '("string" "strung") is equivalent to (list "string" "strung") but that's not true for e.g. '(sym sum) and (list sym sum). The first returns a list of symbols, the second will look up ‘sym’ and ‘sum’ as variables and will fail if they're unbound.
<mfg>ani: one good thing would be to put your packages inside cran.scm alphabetically ordered. Another thing is: guix lint your definitions.
<nckx>Sure, I guess, if you don't take that too literally. Lisp isn't C. But yes, variables are symbols that ‘point’ to values. An introduction to Scheme would do a much better job of explaining this than I am 🙂
<nckx>But the core concept here is quoting, not so much variables. You can quote entire s-expressions, as mroh illustrates, not just symbols.
<nckx>nefix: Try searching the Web for tuturials/explanations of only Scheme/Lisp quoting without other distractions. Understanding that is probably 33% of understanding Scheme, and will make it much easier to understand the code you're reading to learn the other 66%.
<nckx>civodul: I also support (but perhaps it's already a style rule?) using LIST over '() wherever possible. ‘We’ don't care, but a newcomer should not have to wonder why replacing "--foo" with (string-append "--foo=" x) in a list suddenly ‘fails’.
<roptat>zimoun`, good news I think, the issue we're experiencing with dune is actually an issue in OCaml, and it's fixed in 4.11, so we'll have to upgrade to 4.11; there are still some issues apparently, but probably unrelated to the problem we have right now
<lapin>if i specified the version i need to shange the name of my module ?
<roptat>not the name of the module, only the name of the sources
<roptat>the module can have any name, it doesn't matter
<roptat>maybe share your code (on paste.debian.net for instance) so we can better help you?
<roptat>so I'll add ocaml 4.11, then add package-with-ocaml4.09; then I'll need to figure out what to do before I can switch ocaml to 4.11 by default; then I'll see what needs to be done before I can use ocaml 4.09 instead of 4.07, and get rid of 4.07
<zimoun`>roptat: I will see next week if what is done in Haskell about parellel-build? could be mimicked.
<roptat>so we want to have a conference end of november, but we need to get presentations and everything, so the change adds a banner to the website to announce it, with a link to a blog post that explains how it's going to happen
<roptat>basically, we want to have talk proposals before next week (it's basically just filtering on what people want to talk about, to prevent off-topic), then we give them some time to prepare a video and we release them one week before the conference
<roptat>that way, people can watch them beforehand and prepare questions, we won't have a live presentation, only some Q&A and discussion (BoF)
<zimoun`>nckx: I do not know how to rename me. Since I logged with zimoun and then I do not know what happened and paf! I am zimoun`.
<nckx>I want whatever toxic metals are in the Siberian tap water.
<OriansJ>I should have the final third party health report before the end of the week
<roptat>we hope that doing it that way, we give more time to people to think about questions, and we'll have more time for Q&A than normal conferences. That's how the activitypub conference did, and I think it was great
<nckx>OriansJ: Cool. Are you trying all mirror:// URLs?
<roptat>so, haunt has its own guile, /gnu/store/18hp7flyb3yid3yp49i6qcdq0sbi5l1n-guile-3.0.2/bin/guile which seems to be the culprit (from a repl, loading (guix build utils) gives the warnings about incompatible bytecode)
<raghavgururajan>roptat: Thanks! I think you are looking at old patches. The new ones are different. :-)
<rekado_>raghavgururajan: sorry, maybe I’m missing something here
<rekado_>raghavgururajan: if gajim-next doesn’t exist yet there’s no need to rename it
<rekado_>you’d just upgrade gajim to the latest version
<raghavgururajan>rekado_: I see. The pack-def I made for gajim-next is different from the older definition. May be for the newer definition, I use the package name as "gajim" and variable name as "gajim-next"? In this way, guix install gajim installs the latest version.
<rekado_>raghavgururajan: I’m confused: why not upgrade and make all the changes necessary for the upgrade in one commit?
<joshuaBPMan>ok. Do you know the price tag on that? Shipping to the U.S. from finland is probably expensive....
***jess is now known as j
<civodul>roptat, zimoun: we should change to guile-3.0-latest in the .guix.scm file of the web site, if that's an option
<cbaines>I wonder if it would be useful to have some way of annotating Patchwork/Mumi with some details for the submitter, something to tell you if they have commit access, they've had a few patches merged, or if this is the first patch they've submitted...
<roptat>civodul, but that would rebuild guix with that other guile, no?
***j is now known as jess
<joshuaBPMan>cbaines: I'm all for that! We could have little badges: this person helped write a blog post. This person wrote a service definition. It would be a way to motivate and encourage users to contribute!
<cbaines>In this instance though, I'm thinking about patch review, so it would be helpful to know if they're a committer, as then I'll just say it's OK, and won't push it. Or if they're a first time contributor, I'll know to explain things a little more.
<civodul>roptat: we could just define a variant of haunt with guile-3.0-latest as an input
<zimoun>cbaines: cool for patchwork. How the Under Review state is done?
<cbaines>zimoun, manually by someone (me) changing it through the web interface
<cbaines>I also added a "Work in progress" state just now, as I wanted to skip over some patches that still need some work
<jonsger>uff, that is strange. I'm working on phoc, a compositor. In the test suite it compares a certain state as png with a ping in the source repo. It's almost the same but "our" mouse cursor is a bit different then the one upstream used. So the pngs differ :P
<zimoun>civodul: ah yeah. that’s make sense. :-) Is it not possible to update haunt?