<Kabouik>For another program made by the same developer, I have https://0x0.st/HtR1.txt in the package definition. I don't understand it, but since the program is in the same language, maybe I can try that and hope that the dev used the same tests.
<Andronikos>I honestly don't know either. I am new as well. But it looks like at least to me the right way. Replacing the phase and instead execute that script with the test argument.
<Andronikos>I think you can skip the tests to be honest. It seems that it is not implemented. It just looks up if TESTS env is set to 1 and returns true.
<Kabouik>I see. Could you please show me how exactly I should modify the packge definition to add #:tests #f? I'm not sure where/how to nest that in the arguments exactly.
<ekaitz>i guess it's ok to add myself to a Guix team right?
<Kabouik>I submitted a few patches when I first started using Guix, some of which got merged, but the most important was nmail and it was not merged. nchat is from the same dev, so once I get rid of my laziness I'll update my nmail patch and submit nchat at the same time.
<Kabouik>I ended up adding nmail in a private channel because I needed it in my daily workflow and couldn't wait.
<singpolyma>Kabouik: guixrus is a good high velocity channel for submitting stuff like that
<Andronikos>That channel feature is really nice. Just like many other features Guix has to offer.
<Kabouik>Oh, it's used for the syntax. Makes sense then, thank.
<Andronikos>You need that because of the new syntax for the arguments field. Those #~ can be done only if that module is imported (G-Expression is it called)
<Andronikos>It should be the same hash and not even try to build
<Kabouik>Actually I have another silly question concerning the build phase that I am not sure how to build. The default cmake procedure takes >5GB of RAM to build, and will fail on any machine that has less available. There is a way to make it 1.5GB only if setting env variables before cmake to CC=/usr/bin/clang CXX=/usr/bin/clang++. How would I do that in Guix? This would be a better default than the faster build that fails on some machines.
<Kabouik>But I guess hardcoding paths to clang and clang++ is not a good idea in Guix, and would I need new inputs?
<saravia>roptat: for example if I have a not dbus distro, adding guix, I'll install dbus functionality?
<saravia>beacose if I'll install dbus and pulseaudio <-- maybe with that is posible go near to 160MB of ram but with guix like a VENNON package respository
<saravia>^ I say vennon for the movie xD!! : P guix package repository make me thnink in some similar to vennon fiction sciens
<Kabouik>Is there a package providing clang++? I need to use it as a compiler for a package definition, and tried to add clang-toolchain and set CXX env var in the.scm, but it fails with this: https://0x0.st/Ht7R.txt
<Kabouik>Thanks lilyp, then there is something wrong in the arguments I tried in my package definition when I was just adding llvm as input
<Kabouik>Maybe that was my mistake actually, adding llvm instead of clang as input
<lilyp>yep, you shouldn't need more than clang (and perhaps lld)
<Kabouik>The package is building (not over yet) when I just put clang instead of llvm, but I am not sure yet if the CC and CXX env vars were properly taken into account. Here's the package: https://0x0.st/Ht7h.scm
<roptat>Kabouik, if it's building, it didn't take your env vars into account, they point to an inexistant binary
<roptat>clang and clang++ are in clang, not in llvm
<roptat>also, you can probably specify (setenv "CC" "clang") instead of the full path
<Kabouik>I actually pasted the wrong version of the package, my bad. But I'll try what you said, sounds simpler.
<Kabouik>Does that mean I could just removes lines 51-52 and only keep the three setenv after the lambda line?
<Kabouik>To clarify, I pasted the wrong package version above. The one that's building is https://0x0.st/Ht7F.scm and I think the clang full paths should be correct in that one
<futurile>cool - be interesting how the experience has changed in the last few years
<Franciman>another thing i couldn't deal with [because of my inexpertise, to be honest] was that i use kakoune as my main text editor and wanted to have parinfer-rust for editing scheme. I was not able to package it, because i had to package all the single rust dependencies it had
<Franciman>so it was a rabbit hole thing i couldn't manage to get to the bottom of
<Franciman>now i see that parinfer-rust is already packaged :D
<futurile>Franciman: yeah I've run into that, for me - I missed Spotify a lot - and so landed up packaging SpotifyD which was about 60 Rust crates when I started - hilariously annoying.
<futurile>Franciman: one thing to be aware of is `guix shell` with the FHS option - as then you can run binaries compiled for 'normal' Linux in Guix - it's a way to get around having to package things immediately
<futurile>Franciman: just makes transitioning that much easier really
<Franciman>thanks for the spotifyd tip, i was not aware of it, looks awesome. Oh great
<Kabouik>roptat I edited the package definition to only use (setenv "CC" "clang") (setenv "CXX" "clang++") and the build proceeeds, but I don't think the env var are taken into account because it still uses 5GB of RAM instead of the 1.5 it should use if that was working. Also, its says here (https://0x0.st/Hthp.png) that the CXX compiler detection was skipped, why?
<roptat>Kabouik, looks like it found clang++, but not sure why it says "skipped"
<roptat>probably since you specified it, it skips checking it works?
<Kabouik>Hum, so maybe the skipped part is no issue. It still seems to consume more RAM than it should if it was using clang and clang++. I showed the package definition to the developer. He doesn't know Guix/Scheme but maybe will figure out what is wrong.
<Rovanion>My /boot/efi has a UUID of just 8 characters (D653-845A) according to lsblk but guix's `uuid` doesn't accept that. Any ideas?
<Rovanion>The manual mentions that uuids are used in the way they are shown by tune2fs, which doesn't work on fat filesystems.
<Rovanion>Looking at examples I find you can pass a special last argument `'fat` to `uuid` for it to accept fat uuids. Why not just have it accept both types by default?
<Franciman>ok I installed guix system! Working like a charm so far, just a question. guix pull and system reconfigure takes A LOT of time when computing the derivations
<Franciman>but A LOT of time on my laptop, which has an intel i5 4300M
<Franciman>is there something I am missing or it's expected that it takes quite a bit to compute them?
<Kabouik>It's very l.long for me too on an i7 11th generation, unfortunately.
<Franciman>okay, thanks! I'll have to get used to it then :)
<nutcase_>futurile: as promised, I wrote something down about Java @Guix. For most of you, the information available at https://github.com/nuthub/guix-shell-examples is probably nothing new. However, sometimes newbies like me find it difficult to find information on some issues in the web. Feel free to correct things, if they don't look good to you.
<voroskoi>oh, so it is not my config, just debbugs can not handle this
<voroskoi>ok, i clean up the issue tracker, thanks
<lilyp>thankfully, messaging email@example.com is as simple as getting the mail wrong :)
<Kabouik>Say I dd-ed my encrypted Guix system SSD to another (larger) SSD. How can I proceed to boot from it? My config.scm has the partitions mapped by their UUID (https://0x0.st/HtCZ.scm), which obviously are invalid for that disk. Can I decrypt it while plugged externally, chroot into it, edit UUIDs and then run guix system reconfigure?
<ieure>nckx, The entire Go ecosystem is incredibly horked.
<ieure>It is a terrible language. Had a job programming it for 2.5 years, it was excruciating.
<lilyp>I mean, they only had the job of taking over Java's naming scheme and making it worse. What could happen?
<zamfofex>ieure: Perhaps this better fits #guix-offtopic, but what do you think was bad about the language itself? (Bar the tooling and package naming.)
<ieure>This is the funniest thing to me about Go. It's so clearly a reactionary anti-Java, yet they find themselves making the same mistakes as the thing they hate (like: not including generics from the get-go).
<nckx>I try not to judge it too much since I don't 'use' it (although I've played with it), but honestly if you look at something from the outside and all 5 angles look like shit, mayhaps the emperor isn't wearing anything after all.
<solene>hello, I'm trying to figure why my freshly installed guix has a 6.0.10-gnu kernel while a newer version exists in git linux.scm file... I tried to use "guix pull" to update, do I need to do something special to use the latest kernel available?
<solene>the computer has relatively new hardware, I'd like to see if it improves the gpu compatibility
<zamfofex>solene: Did you ‘sudo guix system reconfigure’?
<voroskoi>ieure: this is the intended behaviour: Your home profile is separated from the "default" profile
<voroskoi>whenever You run guix home reconfigure it will install/remove what necessary
<ieure>voroskoi, I understand that it's separate. I don't understand a) Why Guix Home doesn't set my shell configs to use the Guix Home profile b) Why manually activating that profile fails to show the packages that Guix Home has installed.
<Andronikos>Since git email-send is used, I need also to define [sendemail] with my server credentials in the Git config?
<zamfofex>ieure: What do you mean by “doesn't set my shell configs to use the Guix Home profile”? If you mean “without having to close and reopen a terminal window”, it’s because it can’t modify your shell’s variables for you. That’s just not possible.
<ieure>zamfofex, I mean: I open a new shell (or log into the text console), and `GUIX_PROFILE` is not set, and `guix package -I` doesn't show any of the packages declared in my home config.
<zamfofex>‘guix package -I’ is meant to show packages managed by ‘guix package’. It is meant to be separate from ‘guix home’.
<nckx>solene: At the risk of pointing out what you might find obvious, run 'guix pull' before reconfiguring.
<Andronikos>ieure: Do you use the bash service from guix home? This sets your env for guix home or else you need to do it manually.
<nckx>Andronikos: Sorry for the late answer but yes, configure your mail that way.
<Andronikos>nckx: I am new to this and needed some help. Maybe this could be added to the manual itself to make it easier for people like me? Also, I sent a patch about 10 minutes ago. The manual says that first time patches take a bit for acknowledgement. Does it take that long?
<Andronikos>Oh and git send-email gave me this question "Which 8bit encoding should I declare [UTF-8]? " and I pressed enter. Is that the expected way to do it?
<Andronikos>nckx: Ah good to know. I thought that is the case.
<nckx>But the moderation affects only the mailing list part (sending mail to all subscribers), not the tracker Web sites.
<nckx>I'll let you know if I approve anything tonight.
<Andronikos>nckx: Okay, thank you. Does that mean it is normal to take maybe a day? Since I would add this to the manual.
<Andronikos>git send-email had Result: 250, which means everything went fine? Since if it works I would work on updating the description of browserpass.
<nckx>Honestly, it's extremely variable, and there are multiple variables. For example, it can take several seconds to a day (rarely more) to even hit the moderation queue. Then you wait for a human (I try to review daily, sometimes more, seldom less). Then it should be instant, but who knows.
<Andronikos>I think you CPU is just to modern to run on 3D accel with libre firmware
<ieure>I'm linting some package recipes before I submit patches, and `guix lint` is complaining: "tabulation on line 31363, column 0". The info docs say "Warn about obvious source code formatting issues: trailing white space, use of tabulations, etc."
<kbtdr>I am starting a guix home configuration and am trying to customise the bash prompt. I have followed the simple service example in the manual and have created a two line PS1 and a PS2 with a continue statement ("PS2" . "continue-> "). In each case the second line printed has a prompt symbol @ at the start. Why is this?
<solene>Andronikos: I think so too, thanks for confirming
<zamfofex>ieure: “Tab” in this context is short for “tabulate”. They are literally called “tabulation” in both ASCII and Unicode.
<zamfofex>Tabulation characters are used to tabulate text.
<mwette>I have a form like that inside one my channel rtems.scm file and the packages with that form don't show up in `guix search rtems'
<ieure>The Guix manual says to run this command to get a patch series to contribute: `git format-patch -NUMBER_COMMITS -o outgoing --cover-letter --base=auto`
<ieure>This does not work, and I think it's because of `-NUMBER_COMMITS`, which isn't a format-patch option. Is this supposed to stand in for something else, like am I supposed to put the number of commits I want to send in there? Or is it just wrong?
<ieure>git-format-patch can take a bunch of numbering-related options: [-n | --numbered | -N | --no-numbered] [--start-number <n>] [--numbered-files]
<ieure>Passing it -NUMBER_COMMITS gets parsed as -N -U MBER_COMMITS or something similar to that, and complains that the argument to -U needs to be numeric.
<nckx>ACTION looks at 'info guix' — no it's not clear.
<ieure>Git is wild and wooly and it's entirely possible there's something that takes -FOO_BLAH argument syntax; and the Guix documentation says _nothing_ about what NUMBER_COMMITS is, not does it set it off as an obvious thing for me to be filling in, nor make it clear what value would go there.
<freakingpenguin>I have a system configuration that's written as a module and inherits an os-config from another module/file. Is it possible for both files to appear in /run/current-system for, say, auto-update purposes?
<ieure>zamfofex, What makes it difficult? The manual is unclear. Have to configure Git to be able to send emails. Linter gives weird errors. Have to stop and ask at pretty much every step. I'm sure it gets easier, but going from zero to submitted patch is arduous.
<Andronikos>ieure: Run guix build --help Everything in UPPERCASE should be replaced. You can see this behaviour everywhere in the GNU world. At least I always saw this pattern
<Andronikos>ieure: I did my first contribution today. Except configuring git send-email (which was easy to figure it by searching elsewhere) I don't had much trouble. I did not even contribute to Emacs. First time having to deal with this workflow.
<ieure>Andronikos, Yes, common there. Also common: explaining what the value you should put in actually is. "-s, --system=SYSTEM attempt to build for SYSTEM--e.g., "i686-linux""
<ieure>If the Guix manual was like that, I'd have no issue.
<zamfofex>ieure: I feel like you have been having difficulties with things that most people wouldn’t. E.g. most people contributing to Guix would know what a tabulation character is. I guess the “number of commits” thing could be more clear, but I haven’t seen anyone get hang up on that.
<Andronikos>ieure: What you want is that the manual is writting by technical writers with a consistent style guide. As a perfectionist I want this as well, doubt FSF has the money for it.
<ieure>No, what I want is for the manual to convey the information I need in order to accomplish basic tasks, as a novice to Guix.
<nckx>The in-line explanation makes sense to me. Defining Guix-specific typography that diverges from all other info manuals not so much.
<ieure>nckx, I didn't say it had to diverge, and have *repeatedly* said that the specific convention doesn't matter.
<zamfofex>ieure: My first few contributions to Guix were just sending “git diff” output as an attachment from my email GUI. I’ve heard it makes it more difficult to maintainers (so I’ve learned to do it more correctly thereafter), but for simple patches, I think that would work fine to get started. (Though if it really is a big hassle for anyone, feel free to correct me.)
<zamfofex>ieure: The convention is capitals+italics. It’s already there, but you said you didn’t find it clear enough.
<nckx>ieure: You already said above that the convention doesn't matter.
<ieure>zamfofex, It wasn't clear enough for the reasons I stated: My info reader didn't show it in italics, and even if it had, it didn't say what value would be reasonable for NUMBER_COMMITS, the `-3' convention used isn't documented in the git-format-patch man page.
<Andronikos>btw. is that -vREVISION bug still present in Git?
<ieure>Ha, these are getting cc'd to a former coworker. Katherine Cox-Buday.
<Andronikos>ieure: Because it is Git documentation and not GNU documentation. Only GNU does this stuff with UPPERCASE is something you need replace (which makes sense, don't know why not more people adopt it)
<ieure>We used to work at Simple, the online bank.
<ieure>Andronikos, Yes, I understand, also man/info conventions are different. I'm not searching for NUMBER_COMMIT in the git-format-patch man page.
<zamfofex>Andronikos: I think a simple reason is that it there are options that are in uppercase.
<Andronikos>My english is getting more and more broken. Guess it is time to go to bed.
<nckx>podiki, zamfofex: Noo, that way madness lies, trust me. Or at least a wasted afternoon.
<podiki>preview looks clean and since I'm touching mostly things that won't be chagned in master it should stay that way I think...
<nckx>You'll have twe perfect pager but at what cost.
<podiki>Andronikos: the build is quick, tests take a bit longer; in total maybe 5 minutes on say 12 fast cores? but it may want a lot of memory, I forget
<nckx>podiki: If git didn't complain you are *likely* safe.
<podiki>line numbers and colors looks like a nice easy addition though :) it is because i haven't tweaked my emacs recently that the itch needs scratching
<Andronikos>podiki: 12 fast cores, well not for me. I thought you meant building. Currently running "guix time-machine --branch=mesa-updates -- guix build skia --rounds=3"
<podiki>nckx: thanks, that's what I'm banking on. I don't see much in the way of commit messages for these either, other than git default
<nckx>Sure. And then you start smoking the lesspipe.
<podiki>Andronikos: thanks! I will try later too, it failed locally for me too but then i guess at some point worked? and on bordeaux. my attempts at restarting on CI keep getting same segfault on a test though
<nckx>podiki: Sure, no changelog or anything here. (Imagine...)
<Andronikos>podiki: I will report in some time. I only have 4 cores that run on 3.5GHz. (yep, that is a 10 year old CPU)
<podiki>while I have mesa-updates on topic; please do check weather/CI builds for anything; been noticing some tests failures and some build failures after ungrafts
<podiki>I'll send an update to guix-devel this weekend too; hopefully merge it to master soon (x86_64 looks pretty good already)
<Andronikos>What is better for compiling. More cores on lower frequency or less cores but higher frequency?
<podiki>i think more cores; most builds I see scale quite well with more threads
<ieure>Okay, two questions: Firstly, can someone share a working git-send-email setup? I installed the package and set up all the Git config, then ran `git send-email outgoing/0000-cover-letter.patch --annotate'
<ieure>I got back this error: Unable to initialize SMTP properly. Check config and use --smtp-debug. VALUES: server=localhost encryption= hello=l0p.u37.divs.atomized.org port=25 at /gnu/store/4zsf7lwf0lpjwc5ba1bna43cn1zcgw0m-git-2.41.0-send-email/libexec/git-core/.git-gsend-email-real line 1717.
<ieure>I think the issue here is that it's looking for a server of localhost, which is wrong.
<ieure>In my git config, I have: sendemail.smtpserver=smtp.fastmail.com
<ieure>Last question, is there some way to integrate the git send-email stuff with my pass(1) setup? That's where I have my credentials, and it's annoying to have to fetch them manually to tell git about.
<podiki>I think you can use a pass command instead of putting in your password in the config?
<ieure>podiki, git has this git-credential thing it uses. I'm not sure it even supports putting password in the config (which is good).
<Andronikos>ieure: If you find out, please tell me. Asked this question myself, too.